Network Working Group P. Koch
Internet-Draft DENIC eG
Intended status: Best Current July 9, 2007
Practice
Expires: January 10, 2008
Moving MCAST.NET into the ARPA infrastructure top level domain
draft-ietf-mboned-mcast-arpa-01
Status of this Memo
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
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 (C) The IETF Trust (2007).
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 and covers migration issues
and caveats. This document updates RFC 3171.
Koch Expires January 10, 2008 [Page 1]
Internet-Draft Rehoming MCAST.NET July 2007
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . 3
1.1. The ARPA top level domain . . . . . . . . . . . . . . . 3
2. Current Use . . . . . . . . . . . . . . . . . . . . . . 3
3. Registration Policy . . . . . . . . . . . . . . . . . . 3
3.1. Names and Addresses eligible for Registration in
MCAST.ARPA . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Subdomains of MCAST.ARPA . . . . . . . . . . . . . . . 4
3.3. Corresponding Reverse Mapping . . . . . . . . . . . . . 4
4. Migration Issues . . . . . . . . . . . . . . . . . . . 4
4.1. Migration Strategies . . . . . . . . . . . . . . . . . 4
4.1.1. Freeze . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1.2. Phase Out . . . . . . . . . . . . . . . . . . . . . . . 5
4.1.3. Continue . . . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . 6
Appendix A. Document Revision History . . . . . . . . . . . . . . . 6
A.1. Changes from -00 to -01 . . . . . . . . . . . . . . . . 6
A.2. Initial Document . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . 8
Koch Expires January 10, 2008 [Page 2]
Internet-Draft Rehoming MCAST.NET July 2007
1. Introduction
This document describes a maintenance policy and migration strategy
for the MCAST.NET (MCAST.ARPA) domain that contains names for a
subset of the multicast groups assigned by the IANA.
Comments should be sent to the mboned working group.
1.1. The ARPA top level domain
[RFC3172] designates the ARPA top level domain as "Address and
Routing Parameters Area" to be used for infrastructure applications.
The MCAST.NET second level domain fulfills the criteria layed out in
section 2.1 of [RFC3172]. However, there is no standards track
document explicitly designating this domain to a multicast group name
to multicast group address mapping.
[RFC3171] defines the multicast address assignment policy.
2. Current Use
Currently the zone MCAST.NET reflects the contents of the IANA
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.
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
not appear at all.
3. Registration Policy
Names within MCAST.ARPA will consist of one additional label and will
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
in the IPv4 or IPv6 multicast address space.
3.1. Names and Addresses eligible for Registration in MCAST.ARPA
Only IANA multicast address registrations are eligible for being
listed in MCAST.ARPA.
For IPv4, only multicast groups from 224.0.0/24 (Local Network
Control Block) and 224.0.1/24 (Internetwork Control Block) will have
names assigned.
Koch Expires January 10, 2008 [Page 3]
Internet-Draft Rehoming MCAST.NET July 2007
3.2. Subdomains of MCAST.ARPA
The namespace under MCAST.ARPA is considered flat, i.e., all direct
descendants of MCAST.ARPA are leaves in the DNS tree. Future
extensions might want to define subdomains that serve special
purposes. Any such designation needs IETF consensus [RFC2434].
3.3. Corresponding Reverse Mapping
The DNS Reverse Mapping for those multicast groups that appear as
addresses in MCAST.ARPA is to be kept consistent with the forward
namespace. 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 name within MCAST.ARPA.
The zones 225.IN-ADDR.ARPA through 239.IN-ADDR.ARPA will be delegated
but shall remain empty (except necessary infrastructure RRs).
[How to deal with IPv6 multicast reverse mapping is TBD.]
4. Migration Issues
The current content of the MCAST.NET zone shall be brought in line
with the multicast address registry.
Since legacy systems may use MCAST.NET for quite some time, there
needs to be a mapping/forwarding solution to answer those queries in
a useful manner without discouraging migration.
RFCs mentioning MCAST.NET are [RFC3261] and [RFC3678].
An updated multicast address assignment policy appears in
[I-D.ietf-mboned-addrarch].
4.1. Migration Strategies
After the move, several options are available for the future handling
of MCAST.NET.
4.1.1. Freeze
The current MCAST.NET zone could be frozen, so that no additions,
deletions or changes to the content (apart from those necessary for
maintenance, e.g. SOA and NS RRs) would be perfomed. New
registrations would only be available in MCAST.ARPA, so this could be
an incentive for querying clients to alter their behavior as well.
Koch Expires January 10, 2008 [Page 4]
Internet-Draft Rehoming MCAST.NET July 2007
4.1.2. Phase Out
MCAST.NET would only see deletions.
4.1.3. Continue
MCAST.NET could be further operated in parallel, either by
operational habit or per DNAME RR.
5. Security Considerations
The usual Security Considerations for the DNS apply.
There is no Security Problem associated with the migration itself.
MCAST.ARPA. should be signed with DNSSEC as soon as the ARPA zone is
signed.
{This section needs more work.}
6. IANA Considerations
This document amends [RFC3171] to add a mandatory entry in the
MCAST.ARPA domain and a corresponding reverse mapping entry. The
officially registered multicast group name is made subject to DNS
hostname syntax rules.
7. Acknowledgements
The author would like to thank David Conrad for his input.
8. References
8.1. Normative References
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
STD 13, RFC 1034, November 1987.
[RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987.
[RFC1123] Braden, R., "Requirements for Internet Hosts - Application
and Support", STD 3, RFC 1123, October 1989.
Koch Expires January 10, 2008 [Page 5]
Internet-Draft Rehoming MCAST.NET July 2007
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
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
Requirements for the Address and Routing Parameter Area
Domain ("arpa")", BCP 52, RFC 3172, September 2001.
8.2. Informative References
[I-D.ietf-mboned-addrarch]
Savola, P., "Overview of the Internet Multicast Addressing
Architecture", draft-ietf-mboned-addrarch-05 (work in
progress), October 2006.
[RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For
Values In the Internet Protocol and Related Headers",
BCP 37, RFC 2780, March 2000.
[RFC2908] Thaler, D., Handley, M., and D. Estrin, "The Internet
Multicast Address Allocation Architecture", RFC 2908,
September 2000.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002.
[RFC3678] Thaler, D., Fenner, B., and B. Quinn, "Socket Interface
Extensions for Multicast Source Filters", RFC 3678,
January 2004.
Appendix A. Document Revision History
This section is to be removed should the draft be published.
A.1. Changes from -00 to -01
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
requirement for MCAST.ARPA subdomains.
Koch Expires January 10, 2008 [Page 6]
Internet-Draft Rehoming MCAST.NET July 2007
A.2. Initial Document
First draft, taking over with only little changes from
draft-koch-mboned-mcast-arpa-00.txt
Author's Address
Peter Koch
DENIC eG
Wiesenhuettenplatz 26
Frankfurt 60329
DE
Phone: +49 69 27235 0
Email: pk@DENIC.DE
Koch Expires January 10, 2008 [Page 7]
Internet-Draft Rehoming MCAST.NET July 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
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
Administrative Support Activity (IASA).
Koch Expires January 10, 2008 [Page 8]