draft-ietf-mboned-mcast-arpa-01.txt   draft-ietf-mboned-mcast-arpa-02.txt 
Network Working Group P. Koch Network Working Group P. Koch
Internet-Draft DENIC eG Internet-Draft DENIC eG
Intended status: Best Current July 9, 2007 Intended status: BCP L. Vegoda
Practice Expires: December 16, 2010 ICANN
Expires: January 10, 2008 June 14, 2010
Moving MCAST.NET into the ARPA infrastructure top level domain Moving MCAST.NET into the ARPA infrastructure top level domain
draft-ietf-mboned-mcast-arpa-01 draft-ietf-mboned-mcast-arpa-02
Abstract
This document proposes to migrate the MCAST.NET domain into the ARPA
top level domain that is dedicated to infrastructure support. It
also provides for a maintenance policy for the new MCAST.ARPA domain
and covers migration issues and caveats. This document updates RFC
5771 and forms part of BCP 51.
XXX reverse mapping
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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.
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). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on December 16, 2010.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 10, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
Abstract This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document proposes to migrate the MCAST.NET domain into the ARPA This document may contain material from IETF Documents or IETF
top level domain that is dedicated to infrastructure support. It Contributions published or made publicly available before November
also provides for a maintenance policy and covers migration issues 10, 2008. The person(s) controlling the copyright in some of this
and caveats. This document updates RFC 3171. material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . 3
1.1. The ARPA top level domain . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . 3
2. Current Use . . . . . . . . . . . . . . . . . . . . . . 3 3. The ARPA top level domain . . . . . . . . . . . . . . . 3
3. Registration Policy . . . . . . . . . . . . . . . . . . 3 4. Current Use . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Names and Addresses eligible for Registration in 5. Registration Policy . . . . . . . . . . . . . . . . . . 3
MCAST.ARPA . . . . . . . . . . . . . . . . . . . . . . 3 5.1. Names and Addresses eligible for Registration in
3.2. Subdomains of MCAST.ARPA . . . . . . . . . . . . . . . 4 MCAST.ARPA . . . . . . . . . . . . . . . . . . . . . . 4
3.3. Corresponding Reverse Mapping . . . . . . . . . . . . . 4 5.2. Subdomains of MCAST.ARPA . . . . . . . . . . . . . . . 4
4. Migration Issues . . . . . . . . . . . . . . . . . . . 4 5.3. Corresponding Reverse Mapping . . . . . . . . . . . . . 4
4.1. Migration Strategies . . . . . . . . . . . . . . . . . 4 5.3.1. Reverse Mapping for 224/4 . . . . . . . . . . . . . . . 4
4.1.1. Freeze . . . . . . . . . . . . . . . . . . . . . . . . 4 5.3.2. Reverse Mapping for FF0::/12 . . . . . . . . . . . . . 4
4.1.2. Phase Out . . . . . . . . . . . . . . . . . . . . . . . 5 6. Migration Issues . . . . . . . . . . . . . . . . . . . 4
4.1.3. Continue . . . . . . . . . . . . . . . . . . . . . . . 5 6.1. Migration Strategies . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . 5 6.1.1. Freeze . . . . . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . 5 6.1.2. Phase Out . . . . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . 5 6.1.3. Continue . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . 5 7. Security Considerations . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . 5 8. IANA Considerations . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . 6 9. Acknowledgements . . . . . . . . . . . . . . . . . . . 6
Appendix A. Document Revision History . . . . . . . . . . . . . . . 6 10. References . . . . . . . . . . . . . . . . . . . . . . 6
A.1. Changes from -00 to -01 . . . . . . . . . . . . . . . . 6 10.1. Normative References . . . . . . . . . . . . . . . . . 6
A.2. Initial Document . . . . . . . . . . . . . . . . . . . 7 10.2. Informative References . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . 7 Appendix A. Document Revision History . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . 8 A.1. Changes from -01 to -02 . . . . . . . . . . . . . . . . 7
A.2. Changes from -00 to -01 . . . . . . . . . . . . . . . . 7
A.3. Initial Document . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
This document describes a maintenance policy and migration strategy This document describes a maintenance policy and migration strategy
for the MCAST.NET (MCAST.ARPA) domain that contains names for a for the MCAST.NET (MCAST.ARPA) domain that contains names for a
subset of the multicast groups assigned by the IANA. subset of the multicast groups assigned by the IANA.
Comments should be sent to the mboned working group. 2. Terminology
1.1. The ARPA top level domain The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, [RFC2119].
3. The ARPA top level domain
[RFC3172] designates the ARPA top level domain as "Address and [RFC3172] designates the ARPA top level domain as "Address and
Routing Parameters Area" to be used for infrastructure applications. Routing Parameters Area" to be used for infrastructure applications.
The MCAST.NET second level domain fulfills the criteria layed out in The MCAST.NET second level domain fulfills the criteria set out in
section 2.1 of [RFC3172]. However, there is no standards track section 2.1 of [RFC3172]. However, there is no standards track
document explicitly designating this domain to a multicast group name document explicitly designating this domain to a multicast group name
to multicast group address mapping. to multicast group address mapping.
[RFC3171] defines the multicast address assignment policy. [RFC5771] defines the IPv4 multicast address assignment policy.
2. Current Use [RFC4291] defines the IPv6 multicast address assignment policy.
Currently the zone MCAST.NET reflects the contents of the IANA 4. Current Use
multicast address registry. However, some names are missing from the
DNS zone and some names used differ from the description that appears Currently the zone MCAST.NET reflects the contents of parts the IANA
in the registry file. IPv4 multicast address registry. However, some names are missing
from the DNS zone and some names used differ from the description
that appears in the registry file. Entries in the IPv6 multicast
address registry are not reflected in the MCAST.NET zone.
With few exceptions, only multicast group addresses from 224.0.0/24 With few exceptions, only multicast group addresses from 224.0.0/24
and 224.0.1/24 are listed in MCAST.NET. Addresses outside 224/8 do and 224.0.1/24 are listed in MCAST.NET. Addresses outside 224/8 do
not appear at all. not appear at all.
3. Registration Policy 5. Registration Policy
Names within MCAST.ARPA will consist of one additional label and will Names within MCAST.ARPA will consist of one additional label and MUST
adhere to the hostname syntax requirements of [RFC1123]. These names adhere to the hostname syntax requirements of [RFC1123]. These names
will own a single A RR, a single AAAA RR, or both. Addresses will be MUST own a single A RR, a single AAAA RR, or both. Addresses will be
in the IPv4 or IPv6 multicast address space. in the IPv4 or IPv6 multicast address space.
3.1. Names and Addresses eligible for Registration in MCAST.ARPA 5.1. Names and Addresses eligible for Registration in MCAST.ARPA
Only IANA multicast address registrations are eligible for being Only IANA multicast address registrations are eligible for being
listed in MCAST.ARPA. listed in MCAST.ARPA.
For IPv4, only multicast groups from 224.0.0/24 (Local Network For IPv4, only multicast groups from 224.0.0/24 (Local Network
Control Block) and 224.0.1/24 (Internetwork Control Block) will have Control Block) and 224.0.1/24 (Internetwork Control Block) will have
names assigned. names assigned.
3.2. Subdomains of MCAST.ARPA For IPv6, only multicast groups from FF01::/16 (Node-Local Scope
Multicast Addresses) and FF02::/16 (Link-Local Scope Multicast
Addresses) will have names assigned.
5.2. Subdomains of MCAST.ARPA
The namespace under MCAST.ARPA is considered flat, i.e., all direct The namespace under MCAST.ARPA is considered flat, i.e., all direct
descendants of MCAST.ARPA are leaves in the DNS tree. Future descendants of MCAST.ARPA are leaves in the DNS tree. Future
extensions might want to define subdomains that serve special extensions might want to define subdomains that serve special
purposes. Any such designation needs IETF consensus [RFC2434]. purposes. Any such designation needs IETF consensus [RFC5226].
3.3. Corresponding Reverse Mapping 5.3. Corresponding Reverse Mapping
The DNS Reverse Mapping for those multicast groups that appear as The DNS Reverse Mapping for those multicast groups that appear as
addresses in MCAST.ARPA is to be kept consistent with the forward addresses in MCAST.ARPA MUST be kept consistent with the forward
namespace. A single DNS PTR record will be entered at the namespace.
corresponding owner within the 224.IN-ADDR.ARPA domain that points to
the multicast group name name within MCAST.ARPA. 5.3.1. Reverse Mapping for 224/4
A single DNS PTR record will be entered at the corresponding owner
within the 224.IN-ADDR.ARPA domain that points to the multicast group
name within MCAST.ARPA.
The zones 225.IN-ADDR.ARPA through 239.IN-ADDR.ARPA will be delegated The zones 225.IN-ADDR.ARPA through 239.IN-ADDR.ARPA will be delegated
but shall remain empty (except necessary infrastructure RRs). but MUST remain empty (except necessary infrastructure RRs). The one
exception is 233.IN-ADDR.ARPA. A mechanism for the delegation of
reverse mapping for GLOP space [RFC3180] should be designed and
implemented.
5.3.2. Reverse Mapping for FF0::/12
[How to deal with IPv6 multicast reverse mapping is TBD.] [How to deal with IPv6 multicast reverse mapping is TBD.]
4. Migration Issues 6. Migration Issues
The current content of the MCAST.NET zone shall be brought in line The current content of the MCAST.NET zone MUST be brought in line
with the multicast address registry. with the multicast address registry.
Since legacy systems may use MCAST.NET for quite some time, there Since legacy systems may use MCAST.NET for quite some time, there
needs to be a mapping/forwarding solution to answer those queries in needs to be a mapping/forwarding solution to answer those queries in
a useful manner without discouraging migration. a useful manner without discouraging migration.
RFCs mentioning MCAST.NET are [RFC3261] and [RFC3678]. RFCs mentioning MCAST.NET are [RFC3261] and [RFC3678].
An updated multicast address assignment policy appears in An updated multicast address architecture appears in
[I-D.ietf-mboned-addrarch]. [I-D.ietf-mboned-addrarch].
4.1. Migration Strategies 6.1. Migration Strategies
After the move, several options are available for the future handling After the move, several options are available for the future handling
of MCAST.NET. of MCAST.NET.
4.1.1. Freeze [[The working group needs to choose one of the options.]]
6.1.1. Freeze
The current MCAST.NET zone could be frozen, so that no additions, The current MCAST.NET zone could be frozen, so that no additions,
deletions or changes to the content (apart from those necessary for deletions or changes to the content (apart from those necessary for
maintenance, e.g. SOA and NS RRs) would be perfomed. New maintenance, e.g. SOA and NS RRs) would be performed. New
registrations would only be available in MCAST.ARPA, so this could be registrations would only be available in MCAST.ARPA, so this could be
an incentive for querying clients to alter their behavior as well. an incentive for querying clients to alter their behavior as well.
4.1.2. Phase Out 6.1.2. Phase Out
MCAST.NET would only see deletions. MCAST.NET would only see deletions. Even after the last record will
have been deleted, the domain should be kept registered by the IANA
to prevent redelegation ...
4.1.3. Continue 6.1.3. Continue
MCAST.NET could be further operated in parallel, either by MCAST.NET could be further operated in parallel, either by
operational habit or per DNAME RR. operational habit or per DNAME RR, as described in [RFC2672].
5. Security Considerations 7. Security Considerations
The usual Security Considerations for the DNS apply. The usual Security Considerations for the DNS [RFC3833]apply.
There is no Security Problem associated with the migration itself. The MCAST.ARPA., MCAST.NET., and the Reverse mapping zones mentioned
in this document SHALL be DNSSEC signed by the IANA under direction
from the IAB.
MCAST.ARPA. should be signed with DNSSEC as soon as the ARPA zone is There is no Security Problem associated with the migration itself.
signed. XXX keeping MCAST.NET.
{This section needs more work.} {This section needs more work.}
6. IANA Considerations 8. IANA Considerations
This document amends [RFC3171] to add a mandatory entry in the This document amends [RFC5771] to add a mandatory entry in the
MCAST.ARPA domain and a corresponding reverse mapping entry. The MCAST.ARPA domain and a corresponding reverse mapping entry. The
officially registered multicast group name is made subject to DNS officially registered multicast group name is made subject to DNS
hostname syntax rules. hostname syntax rules.
7. Acknowledgements 9. Acknowledgements
The author would like to thank David Conrad for his input. The authors would like to thank David Conrad and Joe Abley for their
input.
8. References 10. References
8.1. Normative References 10.1. Normative References
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities", [RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
STD 13, RFC 1034, November 1987. 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.
[RFC1123] Braden, R., "Requirements for Internet Hosts - Application [RFC1123] Braden, R., "Requirements for Internet Hosts - Application
and Support", STD 3, RFC 1123, October 1989. and Support", STD 3, RFC 1123, October 1989.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
IANA Considerations Section in RFCs", BCP 26, RFC 2434, Requirement Levels", BCP 14, RFC 2119, March 1997.
October 1998.
[RFC3171] Albanna, Z., Almeroth, K., Meyer, D., and M. Schipper,
"IANA Guidelines for IPv4 Multicast Address Assignments",
BCP 51, RFC 3171, August 2001.
[RFC3172] Huston, G., "Management Guidelines & Operational [RFC3172] Huston, G., "Management Guidelines & Operational
Requirements for the Address and Routing Parameter Area Requirements for the Address and Routing Parameter Area
Domain ("arpa")", BCP 52, RFC 3172, September 2001. Domain ("arpa")", BCP 52, RFC 3172, September 2001.
8.2. Informative References [RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8",
BCP 53, RFC 3180, September 2001.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for
IPv4 Multicast Address Assignments", BCP 51, RFC 5771,
March 2010.
10.2. Informative References
[I-D.ietf-mboned-addrarch] [I-D.ietf-mboned-addrarch]
Savola, P., "Overview of the Internet Multicast Addressing Savola, P., "Overview of the Internet Multicast Addressing
Architecture", draft-ietf-mboned-addrarch-05 (work in Architecture", draft-ietf-mboned-addrarch-06 (work in
progress), October 2006. progress), August 2009.
[RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For [RFC2672] Crawford, M., "Non-Terminal DNS Name Redirection",
Values In the Internet Protocol and Related Headers", RFC 2672, August 1999.
BCP 37, RFC 2780, March 2000.
[RFC2908] Thaler, D., Handley, M., and D. Estrin, "The Internet [RFC2908] Thaler, D., Handley, M., and D. Estrin, "The Internet
Multicast Address Allocation Architecture", RFC 2908, Multicast Address Allocation Architecture", RFC 2908,
September 2000. September 2000.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
[RFC3678] Thaler, D., Fenner, B., and B. Quinn, "Socket Interface [RFC3678] Thaler, D., Fenner, B., and B. Quinn, "Socket Interface
Extensions for Multicast Source Filters", RFC 3678, Extensions for Multicast Source Filters", RFC 3678,
January 2004. January 2004.
[RFC3833] Atkins, D. and R. Austein, "Threat Analysis of the Domain
Name System (DNS)", RFC 3833, August 2004.
Appendix A. Document Revision History Appendix A. Document Revision History
This section is to be removed should the draft be published. This section is to be removed should the draft be published.
A.1. Changes from -00 to -01 A.1. Changes from -01 to -02
Added text about v6 multicast.
Added text about GLOP space
Added terminology section and RFC 2119 language
A.2. Changes from -00 to -01
Added text about DNS reverse mapping. Eligibility for an MCAST.ARPA Added text about DNS reverse mapping. Eligibility for an MCAST.ARPA
name now restricted to 224.0.0/24 and 224.0.1/24. Stronger name now restricted to 224.0.0/24 and 224.0.1/24. Stronger
requirement for MCAST.ARPA subdomains. requirement for MCAST.ARPA subdomains.
A.2. Initial Document A.3. Initial Document
First draft, taking over with only little changes from First draft, taking over with only little changes from
draft-koch-mboned-mcast-arpa-00.txt draft-koch-mboned-mcast-arpa-00.txt
Author's Address Authors' Addresses
Peter Koch Peter Koch
DENIC eG DENIC eG
Wiesenhuettenplatz 26 Kaiserstrasse 75-77
Frankfurt 60329 Frankfurt 60329
DE DE
Phone: +49 69 27235 0 Phone: +49 69 27235 0
Email: pk@DENIC.DE Email: pk@DENIC.DE
Full Copyright Statement Leo Vegoda
Internet Corporation for Assigned Names and Numbers
Copyright (C) The IETF Trust (2007). 4676 Admiralty Way, Suite 330
Marina del Rey 90292
This document is subject to the rights, licenses and restrictions United States of America
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF Phone: +1-310-823-9358
Administrative Support Activity (IASA). Email: leo.vegoda@icann.org
URI: http://www.iana.org/
 End of changes. 55 change blocks. 
147 lines changed or deleted 178 lines changed or added

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