draft-ietf-dnsop-attrleaf-fix-06.txt   draft-ietf-dnsop-attrleaf-fix-07.txt 
dnsop D. Crocker dnsop D. Crocker
Internet-Draft Brandenburg InternetWorking Internet-Draft Brandenburg InternetWorking
Updates: 2782, 3263, 3529, 3620, 3832, November 3, 2018 Updates: 2782, 3263, 3529, 3620, 3832, November 20, 2018
3887, 3958, 4120, 4227, 4386, 3887, 3958, 4120, 4227, 4386,
4387, 4976, 5026, 5328, 5389, 4387, 4976, 5026, 5328, 5389,
5415, 5518, 5555, 5617, 5679, 5415, 5518, 5555, 5617, 5679,
5766, 5780, 5804, 5864, 5928, 5766, 5780, 5804, 5864, 5928,
6120, 6186, 6376, 6733, 6763, 6120, 6186, 6376, 6733, 6763,
7208, 7489, 8145 (if approved) 7208, 7489, 8145 (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: May 7, 2019 Expires: May 24, 2019
DNS Attrleaf Changes: Fixing Specifications with Underscored Node Name DNS Attrleaf Changes: Fixing Specifications with Underscored Node Name
Use Use
draft-ietf-dnsop-attrleaf-fix-06 draft-ietf-dnsop-attrleaf-fix-07
Abstract Abstract
Original uses of an underscore character as a domain node name Original uses of an underscore character as a domain node name
prefix, which creates a space for constrained interpretation of prefix, which creates a space for constrained interpretation of
resource records, were specified without the benefit of an IANA resource records, were specified without the benefit of an IANA
registry. This produced an entirely uncoordinated set of name- registry. This produced an entirely uncoordinated set of name-
creation activities, all drawing from the same namespace. A registry creation activities, all drawing from the same namespace. A registry
now has been defined. However the existing specifications that use now has been defined. However the existing specifications that use
underscore naming need to be modified, to be in line with the new underscore naming need to be modified, to be in line with the new
skipping to change at page 1, line 48 skipping to change at page 1, line 48
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on May 7, 2019. This Internet-Draft will expire on May 24, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 37 skipping to change at page 2, line 37
3. Underscored Template Specifications . . . . . . . . . . . . . 6 3. Underscored Template Specifications . . . . . . . . . . . . . 6
3.1. SRV Specification Changes . . . . . . . . . . . . . . . . 6 3.1. SRV Specification Changes . . . . . . . . . . . . . . . . 6
3.2. URI Specification Changes . . . . . . . . . . . . . . . . 7 3.2. URI Specification Changes . . . . . . . . . . . . . . . . 7
3.3. DNSSEC Signaling Specification Changes . . . . . . . . . 9 3.3. DNSSEC Signaling Specification Changes . . . . . . . . . 9
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1. Normative References . . . . . . . . . . . . . . . . . . 10 6.1. Normative References . . . . . . . . . . . . . . . . . . 10
6.2. References -- Informative . . . . . . . . . . . . . . . . 10 6.2. References -- Informative . . . . . . . . . . . . . . . . 10
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 13 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 14 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
Original uses of an underscore character as a domain node name Original uses of an underscore character as a domain node name
[RFC1035] prefix, which creates a space for constrained [RFC1035] prefix, which creates a space for constrained
interpretation of resource records, were specified without the interpretation of resource records, were specified without the
benefit of an [IANA-reg] registry. This produced an entirely benefit of an [IANA-reg] registry. This produced an entirely
uncoordinated set of name-creation activities, all drawing from the uncoordinated set of name-creation activities, all drawing from the
same namespace. A registry has been now defined, and that document same namespace. A registry has been now defined, and that document
discusses the background for underscored domain name use [Attrleaf]. discusses the background for underscored domain name use [Attrleaf].
skipping to change at page 12, line 21 skipping to change at page 12, line 21
Namespace for the Digital Video Broadcasting Project Namespace for the Digital Video Broadcasting Project
(DVB)", RFC 5328, September 2008. (DVB)", RFC 5328, September 2008.
[RFC5389] Rosenberg, Mahy, Matthews, and Wing, "Session Traversal [RFC5389] Rosenberg, Mahy, Matthews, and Wing, "Session Traversal
Utilities for NAT (STUN)", RFC 5389, October 2008. Utilities for NAT (STUN)", RFC 5389, October 2008.
[RFC5415] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley, [RFC5415] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley,
Ed., "Control And Provisioning of Wireless Access Points Ed., "Control And Provisioning of Wireless Access Points
(CAPWAP) Protocol Specification", RFC 5415, March 2009. (CAPWAP) Protocol Specification", RFC 5415, March 2009.
[RFC5509] Loreto, S., "Internet Assigned Numbers Authority (IANA)
Registration of Instant Messaging and Presence DNS SRV RRs
for the Session Initiation Protocol (SIP)", RFC 5509,
DOI 10.17487/RFC5509, April 2009,
<https://www.rfc-editor.org/info/rfc5509>.
[RFC5518] Hoffman, P., Levine, J., and A. Hathcock, "Vouch By [RFC5518] Hoffman, P., Levine, J., and A. Hathcock, "Vouch By
Reference", RFC 5518, April 2009. Reference", RFC 5518, April 2009.
[RFC5555] Soliman, H., Ed., "Mobile IPv6 Support for Dual Stack [RFC5555] Soliman, H., Ed., "Mobile IPv6 Support for Dual Stack
Hosts and Routers", RFC 5555, June 2009. Hosts and Routers", RFC 5555, June 2009.
[RFC5617] Sendmail, Inc., Cisco Systems, Inc., Yahoo! Inc., and [RFC5617] Sendmail, Inc., Cisco Systems, Inc., Yahoo! Inc., and
Taughannock Networks, "DomainKeys Identified Mail (DKIM) Taughannock Networks, "DomainKeys Identified Mail (DKIM)
Author Domain Signing Practices (ADSP)", RFC 5617, August Author Domain Signing Practices (ADSP)", RFC 5617, August
2009. 2009.
skipping to change at page 13, line 22 skipping to change at page 13, line 16
Protocol (XMPP): Core", RFC 6120, March 2011. Protocol (XMPP): Core", RFC 6120, March 2011.
[RFC6186] Daboo, C., "Use of SRV Records for Locating Email [RFC6186] Daboo, C., "Use of SRV Records for Locating Email
Submission/Access Services", RFC 6186, March 2011. Submission/Access Services", RFC 6186, March 2011.
[RFC6376] Crocker, D., Ed., Hansen, T., Ed., and M. Kucherawy, Ed., [RFC6376] Crocker, D., Ed., Hansen, T., Ed., and M. Kucherawy, Ed.,
"DomainKeys Identified Mail (DKIM) Signatures", STD 76, "DomainKeys Identified Mail (DKIM) Signatures", STD 76,
RFC 6376, DOI 10.17487/RFC6376, September 2011, RFC 6376, DOI 10.17487/RFC6376, September 2011,
<https://www.rfc-editor.org/info/rfc6376>. <https://www.rfc-editor.org/info/rfc6376>.
[RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
Ed., "Diameter Base Protocol", RFC 6733,
DOI 10.17487/RFC6733, October 2012,
<https://www.rfc-editor.org/info/rfc6733>.
[RFC6763] Cheshire, S. and M. Krochmal, "DNS-Based Service [RFC6763] Cheshire, S. and M. Krochmal, "DNS-Based Service
Discovery", RFC 6763, DOI 10.17487/RFC6763, February 2013, Discovery", RFC 6763, DOI 10.17487/RFC6763, February 2013,
<https://www.rfc-editor.org/info/rfc6763>. <https://www.rfc-editor.org/info/rfc6763>.
[RFC7208] Kitterman, S., "Sender Policy Framework (SPF) for [RFC7208] Kitterman, S., "Sender Policy Framework (SPF) for
Authorizing Use of Domains in E-Mail, Version 1", Authorizing Use of Domains in E-Mail, Version 1",
RFC 7208, April 2014. RFC 7208, April 2014.
[RFC7489] Kucherawy, M., Ed. and E. Zwicky, Ed., "Domain-based [RFC7489] Kucherawy, M., Ed. and E. Zwicky, Ed., "Domain-based
Message Authentication, Reporting, and Conformance Message Authentication, Reporting, and Conformance
(DMARC)", RFC 7489, March 2015. (DMARC)", RFC 7489, March 2015.
[RFC7671] Dukhovni, V. and W. Hardaker, "The DNS-Based
Authentication of Named Entities (DANE) Protocol: Updates
and Operational Guidance", RFC 7671, DOI 10.17487/RFC7671,
October 2015, <https://www.rfc-editor.org/info/rfc7671>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
Appendix A. Acknowledgements Appendix A. Acknowledgements
Thanks go to Bill Fenner, Dick Franks, Tony Hansen, Peter Koch, Olaf Thanks go to Bill Fenner, Dick Franks, Tony Hansen, Peter Koch, Olaf
Kolkman, and Andrew Sullivan for diligent review of the (much) Kolkman, and Andrew Sullivan for diligent review of the (much)
earlier drafts. For the later enhancements, thanks to: Tim Wicinski, earlier drafts. For the later enhancements, thanks to: Tim Wicinski,
John Levine, Bob Harold, Joel Jaeggli, Ond&#345;ej Sury and Paul John Levine, Bob Harold, Joel Jaeggli, Ond&#345;ej Sury and Paul
 End of changes. 8 change blocks. 
21 lines changed or deleted 5 lines changed or added

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