Moving MCAST.NET into the ARPA infrastructure top level domain
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

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.

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.”

This Internet-Draft will expire on December 16, 2010.

Copyright Notice

Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.

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 may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this 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

1.  Introduction
2.  Terminology
3.  The ARPA top level domain
4.  Current Use
5.  Registration Policy
5.1.  Names and Addresses eligible for Registration in MCAST.ARPA
5.2.  Subdomains of MCAST.ARPA
5.3.  Corresponding Reverse Mapping
5.3.1.  Reverse Mapping for 224/4
5.3.2.  Reverse Mapping for FF0::/12
6.  Migration Issues
6.1.  Migration Strategies
6.1.1.  Freeze
6.1.2.  Phase Out
6.1.3.  Continue
7.  Security Considerations
8.  IANA Considerations
9.  Acknowledgements
10.  References
10.1.  Normative References
10.2.  Informative References
Appendix A.  Document Revision History
A.1.  Changes from -01 to -02
A.2.  Changes from -00 to -01
A.3.  Initial Document
§  Authors' Addresses

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.

2.  Terminology

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] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).

3.  The ARPA top level domain

[RFC3172] (Huston, G., “Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa"),” September 2001.) 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 set out in section 2.1 of [RFC3172] (Huston, G., “Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa"),” September 2001.). However, there is no standards track document explicitly designating this domain to a multicast group name to multicast group address mapping.

[RFC5771] (Cotton, M., Vegoda, L., and D. Meyer, “IANA Guidelines for IPv4 Multicast Address Assignments,” March 2010.) defines the IPv4 multicast address assignment policy.

[RFC4291] (Hinden, R. and S. Deering, “IP Version 6 Addressing Architecture,” February 2006.) defines the IPv6 multicast address assignment policy.

4.  Current Use

Currently the zone MCAST.NET reflects the contents of parts the IANA 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 and 224.0.1/24 are listed in MCAST.NET. Addresses outside 224/8 do not appear at all.

5.  Registration Policy

Names within MCAST.ARPA will consist of one additional label and MUST adhere to the hostname syntax requirements of [RFC1123] (Braden, R., “Requirements for Internet Hosts - Application and Support,” October 1989.). These names MUST own a single A RR, a single AAAA RR, or both. Addresses will be in the IPv4 or IPv6 multicast address space.

5.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.

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 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 [RFC5226] (Narten, T. and H. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs,” May 2008.).

5.3.  Corresponding Reverse Mapping

The DNS Reverse Mapping for those multicast groups that appear as addresses in MCAST.ARPA MUST be kept consistent with the forward namespace.

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 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] (Meyer, D. and P. Lothberg, “GLOP Addressing in 233/8,” September 2001.) should be designed and implemented.

5.3.2.  Reverse Mapping for FF0::/12

[How to deal with IPv6 multicast reverse mapping is TBD.]

6.  Migration Issues

The current content of the MCAST.NET zone MUST 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] (Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, “SIP: Session Initiation Protocol,” June 2002.) and [RFC3678] (Thaler, D., Fenner, B., and B. Quinn, “Socket Interface Extensions for Multicast Source Filters,” January 2004.).

An updated multicast address architecture appears in [I‑D.ietf‑mboned‑addrarch] (Savola, P., “Overview of the Internet Multicast Addressing Architecture,” August 2009.).

6.1.  Migration Strategies

After the move, several options are available for the future handling of MCAST.NET.

[[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, deletions or changes to the content (apart from those necessary for maintenance, e.g. SOA and NS RRs) would be performed. New registrations would only be available in MCAST.ARPA, so this could be an incentive for querying clients to alter their behavior as well.

6.1.2.  Phase Out

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 ...

6.1.3.  Continue

MCAST.NET could be further operated in parallel, either by operational habit or per DNAME RR, as described in [RFC2672] (Crawford, M., “Non-Terminal DNS Name Redirection,” August 1999.).

7.  Security Considerations

The usual Security Considerations for the DNS [RFC3833] (Atkins, D. and R. Austein, “Threat Analysis of the Domain Name System (DNS),” August 2004.)apply.

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.

There is no Security Problem associated with the migration itself. XXX keeping MCAST.NET.

{This section needs more work.}

8.  IANA Considerations

This document amends [RFC5771] (Cotton, M., Vegoda, L., and D. Meyer, “IANA Guidelines for IPv4 Multicast Address Assignments,” March 2010.) 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.

9.  Acknowledgements

The authors would like to thank David Conrad and Joe Abley for their input.

10.  References

10.1. Normative References

10.2. Informative References

Appendix A.  Document Revision History

This section is to be removed should the draft be published.

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 name now restricted to 224.0.0/24 and 224.0.1/24. Stronger requirement for MCAST.ARPA subdomains.

A.3.  Initial Document

First draft, taking over with only little changes from draft-koch-mboned-mcast-arpa-00.txt

Authors' Addresses