import latest version from kame.

- update scoped address syntax to the latest
- I-D/RFC # cleanups

1 files changed, 29 insertions, 15 deletions

diff --git a/sys/netinet6/IMPLEMENTATION b/sys/netinet6/IMPLEMENTATION
index 208adf50cf3..f6151601f58 100644
--- a/sys/netinet6/IMPLEMENTATION
+++ b/sys/netinet6/IMPLEMENTATION
@@ -1,4 +1,4 @@
-$OpenBSD: IMPLEMENTATION,v 1.3 2000/02/09 12:29:28 itojun Exp $
+$OpenBSD: IMPLEMENTATION,v 1.4 2000/02/25 07:34:26 itojun Exp $
 
 # NOTE: this is from original KAME distribution.
 # Some portion of this document is not applicable to the code merged into
@@ -8,7 +8,7 @@ $OpenBSD: IMPLEMENTATION,v 1.3 2000/02/09 12:29:28 itojun Exp $
 
 			KAME Project
 			http://www.kame.net/
-			KAME Date: 2000/02/08 15:29:50
+			KAME Date: 2000/02/24 16:53:19
 
 1. IPv6
 
@@ -100,11 +100,11 @@ draft-ietf-dhc-dhcpv6-14.txt: DHCPv6
 draft-ietf-dhc-v6exts-11.txt: Extensions for DHCPv6
     * kame/dhcp6 has test implementation, which will not be compiled in
       default compilation.
-draft-itojun-ipv6-tcp-to-anycast-00:
+draft-itojun-ipv6-tcp-to-anycast-00.txt:
 	Disconnecting TCP connection toward IPv6 anycast address
-draft-yamamoto-wideipv6-comm-model-00
+draft-yamamoto-wideipv6-comm-model-00.txt
     * See 1.6 in this document for details.
-draft-ietf-ipngwg-scopedaddr-format-00.txt:
+draft-ietf-ipngwg-scopedaddr-format-??.txt:
 	An Extension of Format for IPv6 Scoped Addresses
 draft-ietf-ngtrans-tcpudp-relay-00.txt:
 	An IPv6-to-IPv4 transport relay translator
@@ -216,9 +216,9 @@ Programs that use these APIs have to be prepared about differences
 in kernels anyway.
 
 getaddrinfo(3) and getnameinfo(3) are modified to support extended numeric
-IPv6 syntax, as documented in draft-ietf-ipngwg-scopedaddr-format-00.txt.
+IPv6 syntax, as documented in draft-ietf-ipngwg-scopedaddr-format-??.txt.
 You can specify outgoing link, by using name of the outgoing interface
-like "ne0%fe80::1".  This way you will be able to specify link-local scoped
+like "fe80::1%ne0".  This way you will be able to specify link-local scoped
 address without much trouble.
 To use this extension in your program, you'll need to use getaddrinfo(3),
 and getnameinfo(3) with NI_WITHSCOPEID.
@@ -231,9 +231,9 @@ scope identifier.
 1.3.3 Interaction with users (command line)
 
 Some of the userland tools support extended numeric IPv6 syntax, as
-documented in draft-ietf-ipngwg-scopedaddr-format-00.txt.  In this case,
+documented in draft-ietf-ipngwg-scopedaddr-format-??.txt.  In this case,
 you can specify outgoing link, by using name of the outgoing interface like
-"ne0%fe80::1".
+"fe80::1%ne0".
 
 When you specify scoped address to the command line, NEVER write the
 embedded form (such as ff02:1::1 or fe80:2::fedc).  This is not supposed
@@ -245,8 +245,8 @@ This may seem to be opposite from IPv6's premise to support "dentist office"
 situation.  We believe that specifications need some improvements for this.
 
 The only exception to the above rule would be when you configure routing table
-manually by route(8).  Gateway portion of IPv6 routing entry must be an
-link-local address (otherwise ICMPv6 redirect will not work), and in this
+manually by route(8), or ndp(8).  Gateway portion of IPv6 routing entry must
+be an link-local address (otherwise ICMPv6 redirect will not work), and in this
 case you'll need to configure it by putting interface index into the address:
 	# route add -inet6 default fe80:2::9876:5432:1234:5678
 	(when interface index for outgoing interface = 2)
@@ -274,8 +274,8 @@ Here is an output of netstat command:
 
 Internet6:
 Destination                   Gateway                   Flags      Netif Expire
-ed0%fe80::/64                 link#1                    UC           ed0
-ep0%fe80::/64                 link#2                    UC           ep0
+fe80::%ed0/64                 link#1                    UC           ed0
+fe80::%ep0/64                 link#2                    UC           ep0
 
 Interfaces that has no IEEE802 address (pseudo interfaces like tunnel
 interfaces, or ppp interfaces) will borrow IEEE802 address from other
@@ -994,7 +994,7 @@ Here is a list of FreeBSD 3.x-RELEASE drivers and its conditions:
 	---	---		---		---
 	(Ethernet)
 	fe	ok		ok		yes
-	fxp	ok		ok		yes
+	fxp	?(**)
 	wi	ok		ok		yes
 	lnc	?		ok		-
 	cnw	ok		ok		-(*)
@@ -1005,6 +1005,7 @@ Here is a list of FreeBSD 3.x-RELEASE drivers and its conditions:
 
 (*) These drivers are distributed with PAO as PAO3
     (http://www.jp.freebsd.org/PAO/).
+(**) there are trouble reports with multicast filter initialization.
 
 More drivers will just simply work on KAME FreeBSD 3.x-RELEASE but have not
 been checked yet.
@@ -1086,6 +1087,19 @@ For more details, consult kame/kame/faithd/README.
 
 3.2 IPv6-to-IPv4 header translator
 
-(to be written)
+# removed since it is not imported to OpenBSD-current
+
+4. IPsec
+
+# removed since KAME IPsec is not imported to OpenBSD-current
+# (OpenBSD IPsec is available)
+
+5. ALTQ
+
+# removed since it is not imported to OpenBSD-current
+
+6. mobile-ip6
+
+# removed since it is not imported to OpenBSD-current
 
 						 <end of IMPLEMENTATION>