draft-ietf-dnsext-2929bis-05.txt   draft-ietf-dnsext-2929bis-06.txt 
INTERNET-DRAFT Donald E. Eastlake 3rd INTERNET-DRAFT Donald E. Eastlake 3rd
Obsoletes RFC 2929 Motorola Laboratories Obsoletes RFC 2929 Motorola Laboratories
Updates RFCs 1183 and 3597 Updates RFCs 1183 and 3597
Expires: February 2008 August 2007
Domain Name System (DNS) IANA Considerations Domain Name System (DNS) IANA Considerations
------ ---- ------ ----- ------------------- ------ ---- ------ ----- -------------------
<draft-ietf-dnsext-2929bis-05.txt> <draft-ietf-dnsext-2929bis-06.txt>
Status of This Document Status of This Document
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.
Distribution of this draft is unlimited. It is intended to become Distribution of this draft is unlimited. It is intended to become
the new BCP 42 obsoleting RFC 2929. Comments should be sent to the the new BCP 42 obsoleting RFC 2929. Comments should be sent to the
skipping to change at page 11, line 45 skipping to change at page 11, line 45
0x00FF - QCLASS * (ANY) [RFC1035]. 0x00FF - QCLASS * (ANY) [RFC1035].
256 - 32,767 256 - 32,767
0x0100 - 0x7FFF - Assigned by IETF Consensus. 0x0100 - 0x7FFF - Assigned by IETF Consensus.
32,768 - 57,343 32,768 - 57,343
0x8000 - 0xDFFF - Assigned for data CLASSes only based on 0x8000 - 0xDFFF - Assigned for data CLASSes only based on
Specification Required as defined in [RFC2434]. Specification Required as defined in [RFC2434].
57,344 - 65,279 57,344 - 65,279
0xE000 - 0XFEFF - Assigned for QCLASSes and meta-CLASSes only based 0xE000 - 0xFEFF - Assigned for QCLASSes and meta-CLASSes only based
on Specification Required as defined in [RFC2434]. on Specification Required as defined in [RFC2434].
65,280 - 65,534 65,280 - 65,534
0xFF00 - 0xFFFE - Private Use. 0xFF00 - 0xFFFE - Private Use.
65,535 65,535
0xFFFF - Reserved, can only be assigned by an IETF Standards Action. 0xFFFF - Reserved, can only be assigned by an IETF Standards Action.
3.3 Label Considerations 3.3 Label Considerations
skipping to change at page 13, line 19 skipping to change at page 13, line 19
affects the registry currently at affects the registry currently at
http://www.iana.org/assignments/dns-parameters and its subregistries. http://www.iana.org/assignments/dns-parameters and its subregistries.
1. In the Domain Name System "Resource record (RR) TYPES and QTYPEs" 1. In the Domain Name System "Resource record (RR) TYPES and QTYPEs"
registry, it changes most "IETF Consensus" and all "Specification registry, it changes most "IETF Consensus" and all "Specification
Required" allocation policies for RRTYPEs to be "DNS TYPE Required" allocation policies for RRTYPEs to be "DNS TYPE
Allocation Policy" and changes the policy for RRTYPE 0xFFFF to be Allocation Policy" and changes the policy for RRTYPE 0xFFFF to be
"IETF Standards Action". It also specifies the "DNS TYPE "IETF Standards Action". It also specifies the "DNS TYPE
Allocation Policy" which is based on Expert Review with additional Allocation Policy" which is based on Expert Review with additional
provisions and restrictions, including the sending of a completed provisions and restrictions, including the sending of a completed
copy of the template in Annex A to <iana@iana.org>, in most cases, copy of the template in Annex A to <TBD@iana.org>, in most cases,
and requires "IETF Standards Action as modified by [RFC4020]" in and requires "IETF Standards Action as modified by [RFC4020]" in
other cases. IANA shall establish a process for accepting such other cases. IANA shall establish a process for accepting such
templates, posting them to the namedroppers@ops.ietf.org mailing templates, posting them to the namedroppers@ops.ietf.org mailing
list, selecting one of such Experts as have been appointed to list, selecting one of such Experts as have been appointed to
review such template form applications, and archive and make review such template form applications, and archive and make
available all approved RRTYPE allocation templates. See Section available all approved RRTYPE allocation templates. See Section
3.1 and Annex A for more details. 3.1 and Annex A for more details.
2. For Opcodes (see Section 2.2), it changes "IETF Standards Action" 2. For Opcodes (see Section 2.2), it changes "IETF Standards Action"
allocation requirements to add "as modified by [RFC4020]". allocation requirements to add "as modified by [RFC4020]".
skipping to change at page 14, line 26 skipping to change at page 14, line 26
Email Address: Email Address:
International telephone number: International telephone number:
Other contact handles: Other contact handles:
C. Motivation for the new RRTYPE application? C. Motivation for the new RRTYPE application?
Please keep this part at a high level to inform the Expert and Please keep this part at a high level to inform the Expert and
reviewers about uses of the RRTYPE. Remember most reviewers reviewers about uses of the RRTYPE. Remember most reviewers
will be DNS experts that may have limited knowledge of your will be DNS experts that may have limited knowledge of your
application space. application space.
D. Description of the new RRTYPE, including any special processing D. Description of the proposed RR type. This description can be
for it by applications or DNS resolvers as well as servers. provided in-line in the template, as an attachment or with a
This description can be provided in-line in the template, as an publicly available URL:
attachment or with a publicly available URL:
E. What existing RRTYPE or RRTYPEs come closest to filling that E. What existing RRTYPE or RRTYPEs come closest to filling that
need and why are they unsatisfactory? need and why are they unsatisfactory?
F. What mnemonic is requested for the new RRTYPE (optional)? F. What mnemonic is requested for the new RRTYPE (optional)?
Note: this can be left blank and the mnemonic decided after the Note: this can be left blank and the mnemonic decided after the
template is accepted. template is accepted.
G. Does the requested RRTYPE make use of any existing IANA G. Does the requested RRTYPE make use of any existing IANA
Registry or require the creation of a new IANA Registry and if Registry or require the creation of a new IANA Registry and if
so what is that registry or registries? so what is that registry or registries?
If a new registry is needed, specify allocation policy for it If a new registry is needed, specify allocation policy for it
and initial contents. and initial contents.
H. Does the proposal require/expect any changes in DNS H. Does the proposal require/expect any changes in DNS
servers/resolvers that prevent the new type from being servers/resolvers that prevent the new type from being
processed as an unknown RRTYPE? processed as an unknown RRTYPE (see [RFC3597])?
I. Comments: I. Comments:
Additional IPR Provisions Additional IPR Provisions
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
skipping to change at page 19, line 17 skipping to change at page 19, line 17
Donald E. Eastlake 3rd Donald E. Eastlake 3rd
Motorola Laboratories Motorola Laboratories
155 Beaver Street 155 Beaver Street
Milford, MA 01757 USA Milford, MA 01757 USA
Telephone: +1-508-786-7554 (w) Telephone: +1-508-786-7554 (w)
email: Donald.Eastlake@motorola.com email: Donald.Eastlake@motorola.com
Expiration and File Name Expiration and File Name
This draft expires January 2008. This draft expires February 2008.
Its file name is draft-ietf-dnsext-2929bis-05.txt. Its file name is draft-ietf-dnsext-2929bis-06.txt.
Disclaimer Disclaimer
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 8 change blocks. 
11 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/