One document matched: draft-droms-6man-multicast-scopes-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
     which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
     There has to be one entity for each item to be referenced. 
     An alternate method (rfc include) is described in the references. -->

<!ENTITY RFC4291 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4291.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), 
     please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
     (Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="no"?>
<!-- generate a ToC -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space 
     (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="std" docName="draft-droms-6man-multicast-scopes-00.txt" ipr="trust200902" updates="RFC 4291">
  <!-- category values: std, bcp, info, exp, and historic
     ipr values: full3667, noModification3667, noDerivatives3667
     you can add the attributes updates="NNNN" and obsoletes="NNNN" 
     they will automatically be output with "(if approved)" -->

  <!-- ***** FRONT MATTER ***** -->

  <front>
    <!-- The abbreviated title is used in the page header - it is only necessary if the 
         full title is longer than 39 characters -->

    <title abbrev="IPv6 Multicast Address Scopes">IPv6 Multicast Address Scopes</title>

    <!-- add 'role="editor"' below for the editors if appropriate -->

    <!-- Another author who claims to be an editor -->

    <author fullname="Ralph Droms" initials="R."
            surname="Droms">
      <organization>Cisco</organization>

      <address>
        <postal>
          <street>1414 Massachusetts Avenue</street>

          <!-- Reorder these if your country does things differently -->

          <city>Boxborough</city>

          <region>MA</region>

          <code>01719</code>

          <country>US</country>
        </postal>

        <phone>+1 978 936 1674</phone>

        <email>rdroms@cisco.com</email>

        <!-- uri and facsimile elements may also be added -->
      </address>
    </author>

    <date year="2013" />

    <!-- If the month and year are both specified and are the current ones, xml2rfc will fill 
         in the current day for you. If only the current year is specified, xml2rfc will fill 
	 in the current day and month for you. If the year is not the current one, it is 
	 necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the 
	 purpose of calculating the expiry date).  With drafts it is normally sufficient to 
	 specify just the year. -->

    <!-- Meta-data Declarations -->

    <area>Internet</area>

    <workgroup>Internet Engineering Task Force</workgroup>

    <!-- WG name at the upperleft corner of the doc,
         IETF is fine for individual submissions.  
	 If this element is not present, the default is "Network Working Group",
         which is used by the RFC Editor as a nod to the history of the IETF. -->

    <keyword>IPv6 multicast address scopes</keyword>

    <!-- Keywords will be incorporated into HTML output
         files in a meta tag but they have no effect on text or nroff
         output. If you submit your draft to the RFC Editor, the
         keywords will be used for the search engine. -->

    <abstract>
      <t>This document updates the definitions of IPv6 multicast scopes.</t>
    </abstract>
  </front>

  <middle>
    <?rfc needLines="12" ?>
    <section title="Definition of IPv6 Multicast Address Scopes">
      <t><xref target="RFC4291">RFC 4291</xref> defines values
      and semantics for the scope field in IPv6 multicast addresses.
      The following table updates those definitions:</t>

      <t><list style="hanging">
	<t hangText="0">reserved</t>
	<t hangText="1">Interface-Local scope</t>
	<t hangText="2">Link-Local scope</t>
	<t hangText="3">Network-Specific scope, greater than
	Link-Local scope, defined automatically from the network
	topology</t> 
	<t hangText="4">Admin-Local scope</t>
	<t hangText="5">Site-Local scope</t>
	<t hangText="6">(unassigned)</t>
	<t hangText="7">(unassigned)</t>
	<t hangText="8">Organization-Local scope</t>
	<t hangText="9">(unassigned)</t>
	<t hangText="A">(unassigned)</t>
	<t hangText="B">(unassigned)</t>
	<t hangText="C">(unassigned)</t>
	<t hangText="D">(unassigned)</t>
	<t hangText="E">Global scope</t>
	<t hangText="F">reserved</t>
      </list></t>
    </section>

    <section title="Definition of Network-Specific scopes">
      <t>The definition of any Network-Specific scope for a particular network
      technology should be published in an RFC.  For example, such a
      scope definition would be appropriate for publication in an
      "IPv6-over-foo" RFC.</t>

      <t>Any RFCs that include the definition of a Network-Specific
      scope will be listed in the IANA "IPv6 Multicast Address Scopes"
      registry.</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">

      <t>IANA is asked to establish a sub-registry titled "IPv6
      Multicast Address Scopes" in the existing "Internet Protocol
      version 6 (IPv6) Multicast Address Allocations" registry.  The
      "IPv6 Multicast Address Scopes" is to be populated with the
      scope values given in section 1, with a note associated with
      scope 3 listing all RFCs that define Network-Specific scoping
      rules that use scope 3.</t>

    </section>

    <section anchor="Security" title="Security Considerations">
      <t>This document has no security considerations beyond those in
      <xref target="RFC4291">RFC 4291</xref>.</t> 
    </section>
  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>
    <!-- References split into informative and normative -->

    <!-- There are 2 ways to insert reference entries from the citation libraries:
     1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
     2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
        (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")

     Both are cited textually in the same manner: by using xref elements.
     If you use the PI option, xml2rfc will, by default, try to find included files in the same
     directory as the including file. You can also define the XML_LIBRARY environment variable
     with a value containing a set of directories to search.  These can be either in the local
     filing system or remote ones accessed by http (http://domain/dir/... ).-->

    <references title="Normative References">
      <!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
      &RFC4291;
    </references>
  </back>
</rfc>