draft-ietf-dnsext-nsid-01.txt   draft-ietf-dnsext-nsid-02.txt 
Network Working Group R. Austein Network Working Group R. Austein
Internet-Draft ISC Internet-Draft ISC
Expires: July 15, 2006 January 11, 2006 Expires: December 22, 2006 June 20, 2006
DNS Name Server Identifier Option (NSID) DNS Name Server Identifier Option (NSID)
draft-ietf-dnsext-nsid-01 draft-ietf-dnsext-nsid-02
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 33 skipping to change at page 1, line 33
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
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.
This Internet-Draft will expire on July 15, 2006. This Internet-Draft will expire on December 22, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
With the increased use of DNS anycast, load balancing, and other With the increased use of DNS anycast, load balancing, and other
mechanisms allowing more than one DNS name server to share a single mechanisms allowing more than one DNS name server to share a single
IP address, it is sometimes difficult to tell which of a pool of name IP address, it is sometimes difficult to tell which of a pool of name
skipping to change at page 2, line 17 skipping to change at page 2, line 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Reserved Words . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Reserved Words . . . . . . . . . . . . . . . . . . . . . . 3
2. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Resolver Behavior . . . . . . . . . . . . . . . . . . . . 4 2.1. Resolver Behavior . . . . . . . . . . . . . . . . . . . . 4
2.2. Name Server Behavior . . . . . . . . . . . . . . . . . . . 4 2.2. Name Server Behavior . . . . . . . . . . . . . . . . . . . 4
2.3. The NSID Option . . . . . . . . . . . . . . . . . . . . . 4 2.3. The NSID Option . . . . . . . . . . . . . . . . . . . . . 4
2.4. Presentation Format . . . . . . . . . . . . . . . . . . . 5 2.4. Presentation Format . . . . . . . . . . . . . . . . . . . 5
3. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. The NSID Payload . . . . . . . . . . . . . . . . . . . . . 6 3.1. The NSID Payload . . . . . . . . . . . . . . . . . . . . . 6
3.2. NSID Is Not Transitive . . . . . . . . . . . . . . . . . . 8 3.2. NSID Is Not Transitive . . . . . . . . . . . . . . . . . . 8
3.3. User Interface Issues . . . . . . . . . . . . . . . . . . 8 3.3. User Interface Issues . . . . . . . . . . . . . . . . . . 9
3.4. Truncation . . . . . . . . . . . . . . . . . . . . . . . . 9 3.4. Truncation . . . . . . . . . . . . . . . . . . . . . . . . 9
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.1. Normative References . . . . . . . . . . . . . . . . . . . 13 7.1. Normative References . . . . . . . . . . . . . . . . . . . 14
7.2. Informative References . . . . . . . . . . . . . . . . . . 13 7.2. Informative References . . . . . . . . . . . . . . . . . . 14
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 15
Intellectual Property and Copyright Statements . . . . . . . . . . 15 Intellectual Property and Copyright Statements . . . . . . . . . . 16
1. Introduction 1. Introduction
With the increased use of DNS anycast, load balancing, and other With the increased use of DNS anycast, load balancing, and other
mechanisms allowing more than one DNS name server to share a single mechanisms allowing more than one DNS name server to share a single
IP address, it is sometimes difficult to tell which of a pool of name IP address, it is sometimes difficult to tell which of a pool of name
servers has answered a particular query. servers has answered a particular query.
Existing ad-hoc mechanisms allow an operator to send follow-up Existing ad-hoc mechanisms allow an operator to send follow-up
queries when it is necessary to debug such a configuration, but there queries when it is necessary to debug such a configuration, but there
skipping to change at page 6, line 13 skipping to change at page 6, line 13
See Section 3.3 for discussion. See Section 3.3 for discussion.
3. Discussion 3. Discussion
This section discusses certain aspects of the protocol and explains This section discusses certain aspects of the protocol and explains
considerations that led to the chosen design. considerations that led to the chosen design.
3.1. The NSID Payload 3.1. The NSID Payload
The syntax and semantics of the content of the NSID option is The syntax and semantics of the content of the NSID option is
deliberately left outside the scope of this specification. This deliberately left outside the scope of this specification.
section describe some of the kinds of data that server administrators
might choose to provide as the content of the NSID option, and Chosing the NSID content is a prerogative of the server
explains the reasoning behind choosing a simple opaque byte string. administrator. The server server administrator might chose to encode
the NSID content in such a way that the server operator (or clients
authorized by the server operator) can decode the NSID content to
obtain more information than other clients can. Alternatively, the
server operator might choose unencoded NSID content that is equally
meaningful to any client.
This section describe some of the kinds of data that server
administrators might choose to provide as the content of the NSID
option, and explains the reasoning behind specifying a simple opaque
byte string in Section 2.3.
There are several possibilities for the payload of the NSID option: There are several possibilities for the payload of the NSID option:
o It could be the "real" name of the specific name server within the o It could be the "real" name of the specific name server within the
name server pool. name server pool.
o It could be the "real" IP address (IPv4 or IPv6) of the name o It could be the "real" IP address (IPv4 or IPv6) of the name
server within the name server pool. server within the name server pool.
o It could be some sort of pseudo-random number generated in a o It could be some sort of pseudo-random number generated in a
skipping to change at page 12, line 7 skipping to change at page 13, line 7
Section 3.1 discusses a number of different kinds of information that Section 3.1 discusses a number of different kinds of information that
a name server operator might choose to provide as the value of the a name server operator might choose to provide as the value of the
NSID option. Some of these kinds of information are security NSID option. Some of these kinds of information are security
sensitive in some environments. This specification deliberately sensitive in some environments. This specification deliberately
leaves the syntax and semantics of the NSID option content up to the leaves the syntax and semantics of the NSID option content up to the
implementation and the name server operator. implementation and the name server operator.
6. Acknowledgements 6. Acknowledgements
Joe Abley, Harald Alvestrand, Mark Andrews, Roy Arends, Steve Joe Abley, Harald Alvestrand, Dean Anderson, Mark Andrews, Roy
Bellovin, Randy Bush, David Conrad, Johan Ihren, Daniel Karrenberg, Arends, Steve Bellovin, Alex Bligh, Randy Bush, David Conrad, John
Peter Koch, Mike Patton, Mike StJohns, Paul Vixie, Sam Weiler, and Dickinson, Johan Ihren, Daniel Karrenberg, Peter Koch, William
Suzanne Woolf. Apologies to anyone inadvertently omitted from the Leibzon, Ed Lewis, Thomas Narten, Mike Patton, Geoffrey Sisson,
above list. Andrew Sullivan, Mike StJohns, Paul Vixie, Sam Weiler, and Suzanne
Woolf, none of whom are responsible for what the author did with
their comments and suggestions. Apologies to anyone inadvertently
omitted from the above list.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, March 1997. Requirement Levels", RFC 2119, BCP 14, March 1997.
[RFC2671] Vixie, P., "Extension Mechanisms for DNS (EDNS0)", [RFC2671] Vixie, P., "Extension Mechanisms for DNS (EDNS0)",
RFC 2671, August 1999. RFC 2671, August 1999.
 End of changes. 7 change blocks. 
21 lines changed or deleted 34 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/