One document matched: draft-ietf-mboned-mcast-arpa-02.xml

<?xml version='1.0'?>
<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>

<!-- $Id: draft-mcast-arpa.xml,v 1.7 2007/10/06 21:07:18 pk Exp pk $ -->

<?rfc comments='yes'?>
<?rfc inline='no'?>
<?rfc compact='yes'?>
<?rfc editing='no'?>
<?rfc linkmailto='no'?>
<?rfc symrefs='yes'?>
<?rfc sortrefs='yes'?>
<?rfc subcompact='no'?>
<?rfc toc='yes'?>
<?rfc tocindent='no'?>

<rfc category="bcp" docName="draft-ietf-mboned-mcast-arpa-02" ipr="pre5378Trust200902">
<front>
<title abbrev="Rehoming MCAST.NET">Moving MCAST.NET into the ARPA infrastructure top level domain</title>

  <author initials='P.' surname='Koch' fullname='Peter Koch'>
    <organization>DENIC eG</organization>
    <address>
      <postal>
        <street>Kaiserstrasse 75-77</street>
        <city>Frankfurt</city> <code>60329</code>
        <country>DE</country>
      </postal>
      <phone>+49 69 27235 0</phone>
      <email>pk@DENIC.DE</email>
    </address>
  </author>

  <author initials="L." surname="Vegoda" fullname="Leo Vegoda">
    <organization abbrev="ICANN">
      Internet Corporation for Assigned Names and Numbers
    </organization>
    <address>
      <postal>
        <street>4676 Admiralty Way, Suite 330</street>
        <code>90292</code> <city>Marina del Rey</city>
        <country>United States of America</country>
      </postal>
      <phone>+1-310-823-9358</phone>
      <email>leo.vegoda@icann.org</email>
      <uri>
        http://www.iana.org/
      </uri>
    </address>
  </author>
  
<date month='June' year='2010' />

<abstract>
  <t>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.</t>
<t>XXX reverse mapping</t>
</abstract>

</front>

<!-- ============================================================ -->

<middle>
<section title='Introduction'>

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

</section>
  
<section title="Terminology">
    
    <t>
      
      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, <xref target="RFC2119"/>.
      
    </t>
    
</section>

<section title='The ARPA top level domain'>
<t><xref target='RFC3172'/> designates the ARPA top level domain as
"Address and Routing Parameters Area" to be used for infrastructure
applications.</t>
<t>The MCAST.NET second level domain fulfills the criteria set out in section
2.1 of <xref target='RFC3172'/>. However, there is no standards track
document explicitly designating this domain to a multicast group name to
multicast group address mapping.</t>
<t><xref target='RFC5771'/> defines the IPv4 multicast address assignment policy.</t>
<t><xref target='RFC4291'/> defines the IPv6 multicast address assignment policy.</t>
</section>

<section title='Current Use'>
<t>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.</t>
<t>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.</t>
</section>

<section title='Registration Policy'>

  <t>Names within MCAST.ARPA will consist of one additional label and MUST
  adhere to the hostname syntax requirements of <xref target='RFC1123'/>.
  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.</t>

  <section title='Names and Addresses eligible for Registration in MCAST.ARPA'>

  <t>Only IANA multicast address registrations are eligible for being listed
  in MCAST.ARPA.</t>
  <t>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.</t>
    <t>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.</t>
  </section>

  <section title='Subdomains of MCAST.ARPA'>

  <t>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 <xref target='RFC5226'/>.</t>
  </section>

  <section title='Corresponding Reverse Mapping'>

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

    <section title='Reverse Mapping for 224/4'>

    <t>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.</t>
    <t>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 <xref target='RFC3180'/> should be designed and implemented.</t>
    
    </section>

    <section title='Reverse Mapping for FF0::/12'>

    <t>[How to deal with IPv6 multicast reverse mapping is TBD.]</t>
    </section>

  </section>

</section>

<section title='Migration Issues'>

<t>The current content of the MCAST.NET zone MUST be brought in line
   with the multicast address registry.
</t>
<t>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.</t>

<t>RFCs mentioning MCAST.NET are <xref target='RFC3261'/>
and <xref target='RFC3678'/>.</t>

<t>An updated multicast address architecture appears in
<xref target='I-D.ietf-mboned-addrarch'/>.</t>

<section title='Migration Strategies'>
<t>After the move, several options are available for the future handling of
MCAST.NET.</t>
<t>[[The working group needs to choose one of the options.]]</t>
  <section title='Freeze'>
  <t>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.</t>
  </section>
  <section title='Phase Out'>
  <t>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 ...</t>
  </section>
  <section title='Continue'>
  <t>MCAST.NET could be further operated in parallel, either by operational
    habit or per DNAME RR, as described in <xref target='RFC2672'/>.</t>
  </section>
</section>
</section>

<!-- ============================================================ -->

<section title='Security Considerations'>
<t>The usual Security Considerations for the DNS <xref target='RFC3833'/>apply.</t>

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

<t>There is no Security Problem associated with the migration itself.
   XXX keeping MCAST.NET.</t>

<t>{This section needs more work.}</t>
</section>

<section title='IANA Considerations'>
	<t>This document amends <xref target='RFC5771'/> 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.</t>
</section>

<!-- ============================================================ -->

<section title='Acknowledgements'>
<t>The authors would like to thank David Conrad and Joe Abley for their input.</t>
</section>
</middle>

<!-- ============================================================ -->

<back>
<references title="Normative References">
   <?rfc include="reference.RFC.1034.xml"?>
   <?rfc include="reference.RFC.1035.xml"?>
   <?rfc include="reference.RFC.1123.xml"?>
   <?rfc include="reference.RFC.2119.xml"?>  
   <?rfc include="reference.RFC.3172.xml"?>
   <?rfc include="reference.RFC.3180.xml"?>
   <?rfc include="reference.RFC.4291.xml"?>
   <?rfc include="reference.RFC.5226.xml"?>
   <?rfc include="reference.RFC.5771.xml"?>

</references>

<references title="Informative References">
<!--   <?rfc include="reference.RFC.2780.xml"?> <!-- XXX -->
   <?rfc include="reference.RFC.2908.xml"?>
   <?rfc include="reference.RFC.3261.xml"?>
   <?rfc include="reference.RFC.2672.xml"?>
   <?rfc include="reference.RFC.3678.xml"?>
   <?rfc include="reference.RFC.3833.xml"?>
   <?rfc include="reference.I-D.ietf-mboned-addrarch.xml"?>
</references>

<section title='Document Revision History'>
<t>This section is to be removed should the draft be published.</t>
<pre>$Id: draft-mcast-arpa.xml,v 1.7 2007/10/06 21:07:18 pk Exp pk $</pre>

  <section title='Changes from -01 to -02'>
  <t>Added text about v6 multicast.</t>
  <t>Added text about GLOP space</t>
  <t>Added terminology section and RFC 2119 language</t>
  </section>

  <section title='Changes from -00 to -01'>
  <t>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.</t>
  </section>

  <section title='Initial Document'>
  <t>First draft, taking over with only little changes
     from draft-koch-mboned-mcast-arpa-00.txt</t>
  </section>
</section>
</back>
</rfc>