[src/trunk]: src/share/man/man4 improve scoped ip6 address issues.

[itojun <itojun%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/e8cc967124f0
branches:  trunk
changeset: 480175:e8cc967124f0
user:      itojun <itojun%NetBSD.org@localhost>
date:      Thu Jan 06 02:22:31 2000 +0000

description:
improve scoped ip6 address issues.
refer ip6.4.

diffstat:

 share/man/man4/inet6.4 |  68 +++++++++++++++++++++++++++++++++++--------------
 1 files changed, 48 insertions(+), 20 deletions(-)

diffs (104 lines):

diff -r 1412a775a9c5 -r e8cc967124f0 share/man/man4/inet6.4
--- a/share/man/man4/inet6.4    Thu Jan 06 02:06:41 2000 +0000
+++ b/share/man/man4/inet6.4    Thu Jan 06 02:22:31 2000 +0000
@@ -25,8 +25,8 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.\"    $NetBSD: inet6.4,v 1.5 1999/07/17 06:57:59 itojun Exp $
-.\"    KAME Id: inet6.4,v 1.1.2.2 1999/07/03 05:20:58 itojun Exp
+.\"    $NetBSD: inet6.4,v 1.6 2000/01/06 02:22:31 itojun Exp $
+.\"    KAME Id: inet6.4,v 1.4 2000/01/06 02:20:16 itojun Exp
 .\"
 .Dd January 29, 1999
 .Dt INET6 4
@@ -109,36 +109,55 @@
 field into 0, or by using the address contained in variable
 .Dv in6addr_any .
 .Pp
-IPv6 defines scoped address such as link-local or site-local address.
-To manipulate link-local addresses properly from the userland,
+IPv6 specification defines scoped address,
+like link-local or site-local address.
+A scoped address is ambiguous to the kernel, 
+if it is specified without scope identifier.
+To manipulate scoped addresses properly from the userland,
 programs must use advanced API defined in RFC2292.
-Otherwise, the address is ambiguous to the kernel and error will be generated.
-Scoped address is not for daily use at this moment both from specification
-and implementation point of view.
-Most of normal userland program
+Compact description on the advanced API is available in
+.Xr ip6 4 .
+If scoped addresses are specified without explicit scope,
+the kernel may raise error.
+Note that scoped addresses are not for daily use at this moment,
+both from specification and implementation point of view.
+.Pp
+KAME implementation supports extended numeric IPv6 address notation
+for link-local addresses,
 like
+.Dq Li fe80::1@de0
+to specify
+.Do
+.Li fe80::1
+on
+.Li de0
+interface
+.Dc .
+The notation is supported by
+.Xr getaddrinfo 3
+and
+.Xr getnameinfo 3 .
+Some of normal userland programs, such as
 .Xr telnet 1
 or
-.Xr telnetd 8
-cannot handle scoped address properly.
-Only special programs,
+.Xr ftp 8 ,
+are able to use the notation.
+With special programs
 like
 .Xr ping6 8 ,
-supports scoped address.
-For example,
-.Xr ping6 8
-has special option for specifying outgoing interface
+you can specify outgoing interface by extra command line option
 to disambiguate scoped addresses.
 .Pp
 Scoped addresses are handled specially in the kernel.
-Scoped addresses will have its interface index embedded into the address,
-in routing table or interface structure.
+In the kenrel structures like routing tables or interface structure,
+scoped addresses will have its interface index embedded into the address.
 Therefore,
 the address on some of the kernel structure is not the same as that on the wire.
-The embedded index will be visible on
+The embedded index will become visible on
 .Dv PF_ROUTE
-socket and results from
-.Xr ifconfig 8 ,
+socket, kernel memory accesses via 
+.Xr kvm 3
+and some other occasions.
 HOWEVER, users should never use the embedded form.
 For details please consult
 .Pa sys/netinet6/IMPLEMENTATION .
@@ -279,6 +298,15 @@
 .Xr inet 4
 and
 .Nm inet6 .
+.Sh STANDARDS
+.Rs
+.%A Tatsuya Jinmei
+.%A Atsushi Onoe
+.%T "An Extension of Format for IPv6 Scoped Addresses"
+.%R internet draft
+.%N draft-ietf-ipngwg-scopedaddr-format-00.txt
+.%O work in progress material
+.Re
 .Sh HISTORY
 The
 .Nm