draft-ietf-dnsext-unknown-rrs-02.txt   draft-ietf-dnsext-unknown-rrs-03.txt 
INTERNET-DRAFT Andreas Gustafsson INTERNET-DRAFT Andreas Gustafsson
draft-ietf-dnsext-unknown-rrs-02.txt ISC draft-ietf-dnsext-unknown-rrs-03.txt Nominum Inc.
November 2001 June 2002
Handling of Unknown DNS RR Types Handling of Unknown DNS RR Types
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 RFC2026. all provisions of Section 10 of RFC2026.
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 3, line 50 skipping to change at page 3, line 50
Zero or more words of hexadecimal data encoding Zero or more words of hexadecimal data encoding
the actual RDATA field, each containing an even the actual RDATA field, each containing an even
number of hexadecimal digits. number of hexadecimal digits.
If the RDATA is of zero length, the text representation contains only If the RDATA is of zero length, the text representation contains only
the \# token and the single zero representing the length. the \# token and the single zero representing the length.
An implementation MAY also choose to represent some RRs of known type An implementation MAY also choose to represent some RRs of known type
using the above generic representations for the type, class and/or using the above generic representations for the type, class and/or
RDATA, which carries the benefit of making the resulting master file RDATA, which carries the benefit of making the resulting master file
portable to servers where these types are unknown. portable to servers where these types are unknown. Using the generic
representation for the RDATA of an RR of known type can also be
useful in the case of an RR type where the text format varies
depending on a version, protocol, or similar field (or several)
embedded in the RDATA when such a field has a value for which no text
format is known, e.g., a LOC RR [RFC1876] with a VERSION other than
0.
Even though an RR of known type represented in the \# format is Even though an RR of known type represented in the \# format is
effectively treated as an unknown type for the purpose of parsing the effectively treated as an unknown type for the purpose of parsing the
RDATA text representation, all further processing by the server MUST RDATA text representation, all further processing by the server MUST
treat it as a known type and take into account any applicable type- treat it as a known type and take into account any applicable type-
specific rules regarding compression, canonicalization, etc. specific rules regarding compression, canonicalization, etc.
The following are examples of RRs represented in this manner, The following are examples of RRs represented in this manner,
illustrating various combinations of generic and type-specific illustrating various combinations of generic and type-specific
encodings for the different fields of the master file format: encodings for the different fields of the master file format:
skipping to change at page 5, line 39 skipping to change at page 5, line 45
[RFC1034] - Domain Names - Concepts and Facilities, P. Mockapetris, [RFC1034] - Domain Names - Concepts and Facilities, P. Mockapetris,
November 1987. November 1987.
[RFC1035] - Domain Names - Implementation and Specifications, P. [RFC1035] - Domain Names - Implementation and Specifications, P.
Mockapetris, November 1987. Mockapetris, November 1987.
[RFC1123] - Requirements for Internet Hosts -- Application and [RFC1123] - Requirements for Internet Hosts -- Application and
Support, R. Braden, Editor, October 1989. Support, R. Braden, Editor, October 1989.
[RFC1876] - A Means for Expressing Location Information in the Domain
Name System, C. Davis, P. Vixie, T. Goodwin, I. Dickinson, January
1996.
[RFC2052] - A DNS RR for specifying the location of services (DNS [RFC2052] - A DNS RR for specifying the location of services (DNS
SRV), A. Gulbrandsen, P. Vixie, October 1996. Obsoleted by RFC2782. SRV), A. Gulbrandsen, P. Vixie, October 1996. Obsoleted by RFC2782.
[RFC2119] - Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] - Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2136] - Dynamic Updates in the Domain Name System (DNS UPDATE). [RFC2136] - Dynamic Updates in the Domain Name System (DNS UPDATE).
P. Vixie, Ed., S. Thomson, Y. Rekhter, J. Bound, April 1997. P. Vixie, Ed., S. Thomson, Y. Rekhter, J. Bound, April 1997.
[RFC2535] - Domain Name System Security Extensions. D. Eastlake, [RFC2535] - Domain Name System Security Extensions. D. Eastlake,
skipping to change at page 6, line 11 skipping to change at page 6, line 23
[RFC2782] - A DNS RR for specifying the location of services (DNS [RFC2782] - A DNS RR for specifying the location of services (DNS
SRV). A. Gulbrandsen, P. Vixie, L. Esibov, February 2000. SRV). A. Gulbrandsen, P. Vixie, L. Esibov, February 2000.
[RFC2929] - Domain Name System (DNS) IANA Considerations. D. [RFC2929] - Domain Name System (DNS) IANA Considerations. D.
Eastlake, E. Brunner-Williams, B. Manning, September 2000. Eastlake, E. Brunner-Williams, B. Manning, September 2000.
Author's Address Author's Address
Andreas Gustafsson Andreas Gustafsson
ISC Nominum Inc.
950 Charter Street 2385 Bay Rd
Redwood City, CA 94063 Redwood City, CA 94063
USA USA
Phone: +1 650 779 7004 Phone: +1 650 381 6004
Email: Andreas_Gustafsson@isc.org Email: gson@nominum.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001 - 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 implmentation may be prepared, copied, published and or assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are 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/