Lines Matching full:ipv6
15 1. IPv6
35 1.12 IPv4 mapped address and IPv6 wildcard socket
68 3.2 IPv6-to-IPv4 header translator
81 6. Mobile IPv6
84 6.3 Old Mobile IPv6 code
88 1. IPv6
92 The KAME kit conforms, or tries to conform, to the latest set of IPv6
106 RFC1886: DNS Extensions to support IPv6
108 RFC1981: Path MTU Discovery for IPv6
109 RFC2080: RIPng for IPv6
114 RFC2292: Advanced Sockets API for IPv6
118 RFC2373: IPv6 Addressing Architecture
121 RFC2374: An IPv6 Aggregatable Global Unicast Address Format
123 RFC2375: IPv6 Multicast Address Assignments
125 RFC2428: FTP Extensions for IPv6 and NATs
128 RFC2460: IPv6 specification
129 RFC2461: Neighbor discovery for IPv6
131 RFC2462: IPv6 Stateless Address Autoconfiguration
133 RFC2463: ICMPv6 for IPv6 specification
135 RFC2464: Transmission of IPv6 Packets over Ethernet Networks
136 RFC2465: MIB for IPv6: Textual Conventions and General Group
137 * Necessary statistics are gathered by the kernel. Actual IPv6 MIB
139 RFC2466: MIB for IPv6: ICMPv6 group
140 * Necessary statistics are gathered by the kernel. Actual IPv6 MIB
142 RFC2467: Transmission of IPv6 Packets over FDDI Networks
143 RFC2472: IPv6 over PPP
144 RFC2492: IPv6 over ATM Networks
146 RFC2497: Transmission of IPv6 packet over ARCnet Networks
147 RFC2545: Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing
156 RFC2675: IPv6 Jumbograms
158 RFC2710: Multicast Listener Discovery for IPv6
159 RFC2711: IPv6 router alert option
160 RFC2732: Format for Literal IPv6 Addresses in URL's
163 RFC2874: DNS Extensions to Support IPv6 Address Aggregation and Renumbering
167 RFC2893: Transition Mechanisms for IPv6 Hosts and Routers
173 RFC2894: Router renumbering for IPv6
174 RFC3041: Privacy Extensions for Stateless Address Autoconfiguration in IPv6
175 RFC3056: Connection of IPv6 Domains via IPv4 Clouds
178 draft-itojun-ipv6-transition-abuse-01.txt
180 RFC3142: An IPv6-to-IPv4 transport relay translator
185 the ip6.arpa domain (with the nibble format) for IPv6 reverse
187 RFC3484: Default Address Selection for IPv6
190 RFC3493: Basic Socket Interface Extensions for IPv6
191 * IPv4 mapped address (3.7) and special behavior of IPv6 wildcard bind
199 RFC3542: Advanced Sockets API for IPv6 (revised)
203 RFC4007: IPv6 Scoped Address Architecture
208 draft-ietf-ipngwg-icmp-name-lookups-09: IPv6 Name Lookups Through ICMP
209 draft-ietf-ipv6-router-selection-07.txt:
214 A revised version of RFC2362, which includes the IPv6 specific
220 draft-ietf-ipngwg-icmp-v3-02.txt: ICMPv6 for IPv6 specification (revised)
222 draft-itojun-ipv6-tcp-to-anycast-01.txt:
223 Disconnecting TCP connection toward IPv6 anycast address
224 draft-ietf-ipv6-rfc2462bis-06.txt: IPv6 Stateless Address
226 draft-itojun-ipv6-transition-abuse-01.txt:
227 Possible abuse against IPv6 transition technologies (expired)
235 draft-itojun-ipv6-flowlabel-api-01.txt: Socket API for IPv6 flow label field
246 Duplicated Address Detection (DAD) will be performed when an IPv6 address
259 uniquely assigned (e.g., EUI-64 for an Ethernet interface), IPv6
263 structure for the interface. Every IPv6 I/O operation in the kernel
265 being sent to the "disabled" interface. Whether the IPv6 operation is
295 IPv6 on-link determination rule (RFC2461) is quite different from
307 consider a destination that has both IPv4 and IPv6 addresses but is
308 only reachable via IPv4. Since our getaddrinfo(3) prefers IPv6 by
310 tries to connect to the IPv6 address. If we turn on RFC 2461 6.3.6
395 IPv6 uses scoped addresses. It is therefore very important to
397 site index for a site-local address) with an IPv6 address. Without a
398 zone index, a scoped IPv6 address is ambiguous to the kernel, and
429 embedded into the 2nd 16bit-word (the 3rd and 4th bytes) in the IPv6
437 implementation). The embedded index enables us to identify IPv6
613 * otherwise, sorry but you lose. Please rush the IETF IPv6
620 will return IPv6 addresses with the 2nd 16bit-word filled in. The
625 getaddrinfo(3) and getnameinfo(3) support an extended numeric IPv6
638 Most of user applications now support the extended numeric IPv6
644 the IPv6 default route by hand, you can type like
665 The KAME kit implements most of the IPv6 stateless address
675 IPv6 link-local address is generated from IEEE802 address (ethernet MAC
676 address). Each of interface is assigned an IPv6 link-local address
695 If an interface is not capable of handling IPv6 (such as lack of multicast
709 In IPv6 specification, nodes are separated into two categories:
715 is in operation. IPv6 specification defines behavior for "host" and "router"
745 Note that the IPv6 specification assumes the following items and that
805 If you would like to configure an IPv4-in-IPv6 tunnel with gif interface,
806 read gif(4) carefully. You may need to remove IPv6 link-local address
892 KAME supports the Jumbo Payload hop-by-hop option used to send IPv6
910 The IPv6 specification requires that the Jumbo Payload option must not
916 If KAME kernel receives an IPv6 packet, it checks the frame length of
918 length field of the IPv6 header or in the value of the Jumbo Payload
947 IPv6 header + link-layer header. Therefore, it must be expanded to at least
952 - We mistakingly check for ip6_plen field of IPv6 header for packet payload
960 IPv6 specification allows arbitrary number of extension headers to
961 be placed onto packets. If we implement IPv6 packet processing
969 (including the IPv6 header) in each incoming packet, in order to
978 number of IPsec headers, kernel stack may blow up. IPsec-over-IPv6 is okay.
1004 For userland programming, we support IPv6 socket API as specified in
1007 TCP/UDP over IPv6 is available and quite stable. You can enjoy "telnet",
1009 independent. That is, they automatically chooses IPv4 or IPv6
1019 if_output() since routers must not divide IPv6 packets into fragments.
1061 1.12 IPv4 mapped address and IPv6 wildcard socket
1064 of IPv6 wildcard bind socket (3.8). The spec allows you to:
1074 between IPv4 and IPv6. You can perform wildcard bind on both of the address
1114 If a server application would like to accept IPv4 and IPv6 connections,
1120 and IPv6 connections will be accepted by AF_INET6 socket (NOTE: KAME/BSDI4
1123 If you try to support IPv6 traffic only and would like to reject IPv4
1132 Advise to application implementers: to implement a portable IPv6 application
1133 (which works on multiple IPv6 kernels), we believe that the following
1140 - Some of the IPv6 stack is shipped with buggy getaddrinfo(). Ship a minimal
1143 If you would like to use AF_INET6 socket for both IPv4 and IPv6 outgoing
1147 it does not handle scoped IPv6 addresses at all. For IPv6 name resolution
1245 which was derived from NRL IPv6/IPsec stack. We guess it supports IPv4 mapped
1266 which was derived from NRL IPv6/IPsec stack.
1297 - If a protocol on top of IPv4 is defined differently with IPv6, we need to be
1304 use EPSV/EPRT or LPSV/LPRT; /*IPv6*/
1313 use EPSV/EPRT or LPSV/LPRT; /*IPv6*/
1320 servers on the kernel can be hosed by IPv6 native packet that has IPv4
1321 mapped address in IPv6 header source, and can generate unwanted IPv4 packets.
1322 draft-itojun-ipv6-transition-abuse-01.txt, draft-cmetz-v6ops-v4mapped-api-
1329 This is to avoid malicious use of IPv4 mapped address in IPv6 native
1344 (1) SIIT translators require end nodes in the SIIT cloud to be IPv6-only.
1347 dual stack network. (3) KAME stack filters out IPv6 packets with IPv4
1353 things. For example, SIIT document asks IPv6-only (meaning no IPv4 code)
1355 construct IPv4 IPsec headers, that is not an IPv6-only node, it is a dual-stack
1387 If you look at multiple IPv6 implementations, you will be able to see
1400 Some of IPv6 transition technologies embed IPv4 address into IPv6 address.
1407 To name a few, these address ranges can be used to hose an IPv6 implementation,
1410 IPv4 address (if they are in IPv6 native packet header, they are malicious)
1419 IPv4 address (if they are in IPv6 native packet header, they are malicious).
1427 If we see IPv6 packets with IPv4 mapped address (::ffff:0.0.0.0/96) in the
1431 IPv6 specifications do not talk very much about IPv6 unspecified address (::)
1432 in the IPv6 source address field. Clarification is in progress.
1434 - IPv6 unspecified address can be used in IPv6 source address field, if and
1436 include, but may not be limited to, (1) MLD while no IPv6 address is assigned
1438 - If IPv6 TCP packet has IPv6 unspecified address, it is an attack attempt.
1442 consensus among ipngwg for those. (1) Mobile IPv6 home address option,
1447 KAME kernel will reject packets with certain source/destination address in IPv6
1448 base header, or IPv6 routing header. Also, KAME default configuration file
1451 draft-itojun-ipv6-transition-abuse-01.txt, draft-cmetz-v6ops-v4mapped-api-
1457 RFC2373 section 2.8 talks about required addresses for an IPv6
1526 Background: RFC2292 document is based on RFC1883 IPv6, and it uses
1527 strict/loose bitmap. RFC3542 document is based on RFC2460 IPv6, and it has
1529 RFC2460 IPv6, and lacks support for strict/loose bitmap.
1545 - IPv6 transport support (queries/responses over IPv6). Most of BSD official
1729 We categorize IPv4/IPv6 translator into 4 types.
1732 it possible to establish a connection from an IPv6 host in an IPv6
1737 ocean to an IPv6 host in an IPv6 island.
1741 to an IPv6 host in the IPv6 ocean.
1744 possible to establish a connection from an IPv6 host in the IPv6 ocean
1753 FAITH will reserve an IPv6 address prefix, and relay TCP connection
1756 For example, if the reserved IPv6 prefix is 3ffe:0501:0200:ffff::, and
1757 the IPv6 destination for TCP connection is 3ffe:0501:0200:ffff::163.221.202.12,
1765 | IPv6 TCP toward 3ffe:0501:0200:ffff::163.221.202.12
1766 source IPv6 node
1772 3.2 IPv6-to-IPv4 header translator
1787 to replace it. IPv6 support for IPsec is, therefore, lacking on KAME/OpenBSD.
1829 IPsec module is implemented as "hooks" to the standard IPv4/IPv6
1855 - Path MTU discovery does not work across IPv6 IPsec tunnel gateway due to
1988 IPv4 TOS field (or, IPv6 traffic class field) will be copied from inner
2109 ???: IPv6 scope zone is kept the same
2121 ???: IPv6 scope zone is likely to be different from the real ethernet
2207 ALTQ in KAME supports IPv6.
2226 6. Mobile IPv6