…ence with CIDR. RFC 1886 is currently listed as a Proposed Standard. RFC 2874 [ RFC2874 ] specified enhanced mechanisms to support IPv6 addresses in the DNS. These mechanisms provide new features that make it possible for an IPv6 address stored in the DNS to be broken up into mul…

…ne an IPv6 address by using multiple DNS records. Here is an example taken from RFC2874 : HAGINO Expires: January 19, 2002 [Page 2] DRAFT Comparison of AAAA and A6 July 2001 $ORIGIN X.EXAMPLE. N A6 64 ::1234:5678:9ABC:DEF0 SUBNET-1.IP6 SUBNET-1.IP6 A6 48 0:0:0:1:: IP6 IP6 A6 48 0…

…034, RFC1035 ], DNS Security Extensions [ RFC2535 ], EDNS0 [ RFC2671 ] and A6 [ RFC2874 ] is helpful. STD 13, RFC 1035 Section 2.3.4 requires that DNS messages over UDP have a data payload of 512 octets or less. Most DNS software today will not accept larger UDP datagrams. Any an…

…RPA domain be used for address to DNS name mapping for the IPv6 address space [ RFC2874 ]. 2 . Obsoleted Usage This document deprecates references to IP6.INT in [ RFC1886 ] section 2.5 , [RFC2553] section 6.2.3 , [RFC2766] section 4.1 , [RFC2772] section 7.1 .c, and [RFC2874] sec…

…zing two different address formats for IPv6 addresses AAAA [ RFC1886 ] and A6 [ RFC2874 ] and both are at proposed standard. This had led to confusion and conflicts on which one to deploy. It is important for deployment that any confusion in this area be cleared up, as there is a…

…for the address-to-name mapping of all of them. And, using the conventions of [ RFC2874 ], it can roll the reverse mapping data into the "forward" (name-keyed) zone. Specific advantages of the fixed boundary being at /48 include - To leave open the technical option of retro-fitti…

…zing two different address formats for IPv6 addresses AAAA [ RFC1886 ] and A6 [ RFC2874 ] and both are at proposed standard. This had led to confusion and conflicts on which one to deploy. It is important for deployment that any confusion in this area be cleared up, as there is a…

…for the address-to-name mapping of all of them. And, using the conventions of [ RFC2874 ], it can roll the reverse mapping data into the "forward" (name-keyed) zone. Specific advantages of the fixed boundary being at /48 include - To leave open the technical option of retro-fitti…