draft-ietf-dnsext-ipv6-addresses-00.txt   draft-ietf-dnsext-ipv6-addresses-01.txt 
DNSEXT Working Group Randy Bush (ed.) DNSEXT Working Group Randy Bush (ed.)
Alain Durand (ed.) Alain Durand (ed.)
Bob Fink (ed.) Bob Fink (ed.)
Olafur Gudmundsson (ed.) Olafur Gudmundsson (ed.)
Tony Hain (ed.) Tony Hain (ed.)
<draft-ietf-dnsext-ipv6-addresses-00.txt> <draft-ietf-dnsext-ipv6-addresses-01.txt>
Updates: RFC 1886, RFC 2673, RFC 2874 Updates: RFC 1886, RFC 2673, RFC 2874
Representing IPv6 addresses in DNS. Representing IPv6 addresses in DNS.
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Comments should be sent to the authors or the DNSEXT WG mailing list Comments should be sent to the authors or the DNSEXT WG mailing list
namedroppers@ops.ietf.org namedroppers@ops.ietf.org
This draft expires on March 25, 2002. This draft expires on September 1, 2002.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All rights reserved. Copyright (C) The Internet Society (2002). All rights reserved.
Abstract Abstract
This document clarifies and updates the standards status of RFCs that This document clarifies and updates the standards status of RFCs that
define direct and reverse map of IPv6 addresses in DNS. This document define direct and reverse map of IPv6 addresses in DNS. This document
moves the A6 and Bit label specifications to experimental status. moves the A6 and Bit label specifications to experimental status.
1 - Introduction 1 - Introduction
The IETF had begun the process of standardizing two different address The IETF had begun the process of standardizing two different address
skipping to change at page 4, line 25 skipping to change at page 4, line 25
defined since RFC 1035[RFC1035]. Since the development of 2673 it has defined since RFC 1035[RFC1035]. Since the development of 2673 it has
been learned that deployment of a new type is difficult since DNS been learned that deployment of a new type is difficult since DNS
servers that do not support bitlabels reject queries containing bit servers that do not support bitlabels reject queries containing bit
labels as being malformed. The community has also indicated that this labels as being malformed. The community has also indicated that this
new label type is not needed for mapping reverse addresses. new label type is not needed for mapping reverse addresses.
3.1 Rationale 3.1 Rationale
The hexadecimal text representation of IPv6 addresses appears to be The hexadecimal text representation of IPv6 addresses appears to be
capable of expressing all of the delegation schemes that we expect to capable of expressing all of the delegation schemes that we expect to
be used in the DNS reverse tree, since we do not ever expect to see be used in the DNS reverse tree.
delegation in the least significant possible hexadecimal label. That
is, we do not ever expect to see an IPv6 address architecture that
advocates address delegation in the least significant four bits of an
IPv6 address.
3.2 Recommended standard action 3.2 Recommended standard action
RFC 2673 standard status is to be changed from Proposed to RFC 2673 standard status is to be changed from Proposed to
Experimental. Future standardization of these documents is to be done Experimental. Future standardization of these documents is to be done
by the DNSEXT working group or its successor. by the DNSEXT working group or its successor.
4 DNAME in IPv6 reverse tree 4 DNAME in IPv6 reverse tree
The issues for DNAME chaining in the reverse tree are substantially The issues for DNAME chaining in the reverse tree are substantially
skipping to change at page 5, line 13 skipping to change at page 5, line 13
document is that use of DNAME RRs in the reverse tree be deprecated. document is that use of DNAME RRs in the reverse tree be deprecated.
5 Acknowledgments 5 Acknowledgments
This document is based on input from many members of the various IETF This document is based on input from many members of the various IETF
working groups involved in this issues. Special thanks go to the working groups involved in this issues. Special thanks go to the
people that prepared reading material for the joint DNSEXT and people that prepared reading material for the joint DNSEXT and
NGTRANS working group meeting at the 51st IETF in London, Rob NGTRANS working group meeting at the 51st IETF in London, Rob
Austein, Dan Bernstein, Matt Crawford, Jun-ichiro itojun Hagino, Austein, Dan Bernstein, Matt Crawford, Jun-ichiro itojun Hagino,
Christian Huitema. Number of other people have made number of Christian Huitema. Number of other people have made number of
comments on mailing lists about this issue including Robert Elz , comments on mailing lists about this issue including Andrew W.
Johan Ihren , Bill Manning Barclay, Robert Elz, Johan Ihren, Edward Lewis, Bill Manning, Pekka
Savola, Paul Vixie.
6 - Security Considerations: 6 - Security Considerations:
As this document specifies a course of action, there are no direct As this document specifies a course of action, there are no direct
security considerations. There is an indirect security impact of the security considerations. There is an indirect security impact of the
choice, in that the relationship between A6 and DNSSEC is not well choice, in that the relationship between A6 and DNSSEC is not well
understood throughout the community, while the choice of AAAA does understood throughout the community, while the choice of AAAA does
leads to a model for use of DNSSEC in IPv6 networks which parallels leads to a model for use of DNSSEC in IPv6 networks which parallels
current IPv4 practice. current IPv4 practice.
skipping to change at page 6, line 15 skipping to change at page 6, line 15
Editors Address Editors Address
Randy Bush <randy@psg.com> Randy Bush <randy@psg.com>
Alain Durand <alain.durand@sun.com> Alain Durand <alain.durand@sun.com>
Bob Fink <fink@es.net> Bob Fink <fink@es.net>
Olafur Gudmundsson <ogud@ogud.com> Olafur Gudmundsson <ogud@ogud.com>
Tony Hain <hain@tndh.net> Tony Hain <hain@tndh.net>
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/