| draft-ietf-dnsext-5395bis-01.txt | draft-ietf-dnsext-5395bis-02.txt | |||
|---|---|---|---|---|
| INTERNET-DRAFT Donald Eastlake 3rd | INTERNET-DRAFT Donald Eastlake 3rd | |||
| Obsoletes: 5395 Stellar Switches | Obsoletes: 5395 Stellar Switches | |||
| Updates: 1183, 3597 | Updates: 1183, 3597 | |||
| Intended status: Best Current Practice | Intended status: Best Current Practice | |||
| Expires: May 10, 2011 November 11, 2010 | Expires: May 25, 2011 November 26, 2010 | |||
| Domain Name System (DNS) IANA Considerations | Domain Name System (DNS) IANA Considerations | |||
| <draft-ietf-dnsext-5395bis-01.txt> | <draft-ietf-dnsext-5395bis-02.txt> | |||
| Abstract | Abstract | |||
| Internet Assigned Number Authority (IANA) parameter assignment | Internet Assigned Number Authority (IANA) parameter assignment | |||
| considerations are specified for the allocation of Domain Name System | considerations are specified for the allocation of Domain Name System | |||
| (DNS) resource record types, CLASSes, operation codes, error codes, | (DNS) resource record types, CLASSes, operation codes, error codes, | |||
| DNS protocol message header bits, and AFSDB resource record subtypes. | DNS protocol message header bits, and AFSDB resource record subtypes. | |||
| Status of This Memo | Status of This Memo | |||
| skipping to change at page 14, line 18 | skipping to change at page 14, line 18 | |||
| general DNS parameters, not security. See [RFC4033], [RFC4034], and | general DNS parameters, not security. See [RFC4033], [RFC4034], and | |||
| [RFC4035] for secure DNS considerations. | [RFC4035] for secure DNS considerations. | |||
| 5. IANA Considerations | 5. IANA Considerations | |||
| This document consists entirely of DNS IANA Considerations. | This document consists entirely of DNS IANA Considerations. | |||
| IANA shall establish a process for accepting Annex A templates, | IANA shall establish a process for accepting Annex A templates, | |||
| selecting an Expert from those appointed to review such template form | selecting an Expert from those appointed to review such template form | |||
| applications, and archive and make available all approved RRTYPE | applications, and archive and make available all approved RRTYPE | |||
| allocation templates. It is the duty of the selected Expert to post | allocation templates. It is the duty of the applicant to post the | |||
| the formal application template to the dns-rrtype- | formal application template to the dns-rrtype-applications@ietf.org | |||
| applications@ietf.org mailing list. See Section 3.1 and Annex A for | mailing list. See Section 3.1 and Annex A for more details. | |||
| more details. | ||||
| Annex A: RRTYPE Allocation Template | Annex A: RRTYPE Allocation Template | |||
| DNS RRTYPE PARAMETER ALLOCATION TEMPLATE | DNS RRTYPE PARAMETER ALLOCATION TEMPLATE | |||
| When ready for formal consideration, this template is to be submitted | When ready for formal consideration, this template is to be submitted | |||
| to IANA for processing by emailing the template to dns-rrtype- | to IANA for processing by emailing the template to dns-rrtype- | |||
| applications@ietf.org. | applications@ietf.org. | |||
| A. Submission Date: | A. Submission Date: | |||
| skipping to change at page 18, line 5 | skipping to change at page 17, line 14 | |||
| Annex B: Changes From RFC 5395 | Annex B: Changes From RFC 5395 | |||
| Replace "namedroppers@ops.ietf.org" with "dnsext@ietf.org". | Replace "namedroppers@ops.ietf.org" with "dnsext@ietf.org". | |||
| Drop description of changes from RFC 2929 to RFC 5395 since those | Drop description of changes from RFC 2929 to RFC 5395 since those | |||
| changes have already happened and we don't need to do them again. | changes have already happened and we don't need to do them again. | |||
| Updates to boilerplate text. | Updates to boilerplate text. | |||
| Fix Section 5 to say that it is the duty of the applicant, not the | ||||
| expert, to post the application to dns-rrtype-applications@ietf.org. | ||||
| Normative References | Normative References | |||
| [RFC1034] - Mockapetris, P., "Domain names - concepts and | [RFC1034] - Mockapetris, P., "Domain names - concepts and | |||
| facilities", STD 13, RFC 1034, November 1987. | facilities", STD 13, RFC 1034, November 1987. | |||
| [RFC1035] - Mockapetris, P., "Domain names - implementation and | [RFC1035] - Mockapetris, P., "Domain names - implementation and | |||
| specification", STD 13, RFC 1035, November 1987. | specification", STD 13, RFC 1035, November 1987. | |||
| [RFC1996] - Vixie, P., "A Mechanism for Prompt Notification of Zone | [RFC1996] - Vixie, P., "A Mechanism for Prompt Notification of Zone | |||
| Changes (DNS NOTIFY)", RFC 1996, August 1996. | Changes (DNS NOTIFY)", RFC 1996, August 1996. | |||
| End of changes. 4 change blocks. | ||||
| 6 lines changed or deleted | 8 lines changed or added | |||
This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||