One document matched: draft-jabley-eui48-eui64-doc-addr-00.xml

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
  <!ENTITY rfc2119 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
  <!ENTITY rfc5342 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5342.xml'>
  <!ENTITY rfc5737 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5737.xml'>
]>

<rfc category="bcp" ipr="trust200902"
  docName="draft-jabley-eui48-eui64-doc-addr-00">

  <?rfc toc="yes" ?>
  <?rfc symrefs="yes" ?>
  <?rfc sortrefs="yes"?>
  <?rfc iprnotified="no" ?>
  <?rfc strict="yes" ?>

  <front>
    <title abbrev="EUI-48 and EUI-64 Documentation Addresses">EUI-48 and
      EUI-64 Address Assignments for use in Documentation</title>

    <author initials='J.' surname="Abley" fullname='Joe Abley'>
      <organization>TekSavvy Solutions, Inc.</organization>
      <address>
        <postal>
          <street>470 Moore Street</street>
          <city>London</city>
          <region>ON</region>
          <code>N6C 2C2</code>
          <country>Canada</country>
        </postal>
        <phone>+1 519 670 9327</phone>
        <email>jabley@teksavvy.ca</email>
      </address>
    </author>

    <date day="21" month="March" year="2013"/>

    <abstract>
      <t>48-bit Extended Unique Identifiers (EUI-48) and 64-bit
        Extended Unique Identifiers (EUI-64) are address formats
	specified by the IEEE for use in various layer-2 networks,
	e.g. ethernet.</t>

      <t>This document describes an allocation of EUI-48 and EUI-64
        addresses under the IANA Organisationally Unique Identifier (OUI)
        to be used for the purposes of documentation.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t><xref target="EUI48">48-bit Extended Unique Identifiers
	(EUI-48)</xref> and <xref target="EUI64">64-bit Extended
	Unique Identifiers (EUI-64)</xref> are address formats
	specified by the IEEE for use in various layer-2 networks,
	e.g. ethernet.</t>

      <t>This document describes an allocation of EUI-48 and EUI-64
        addresses under the IANA Organisationally Unique Identifier (OUI)
	to be used for the purposes of documentation, in accordance
	with the guidelines and requirements for such allocations
	described in <xref target="RFC5342"/>.</t>

      <t>As noted in <xref target="RFC5737"/>, the use of designated
	address ranges for documentation and examples reduces the
	likelihood of conflicts and confusion arising from the use
	of addresses assigned for some other purpose.</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 <xref target="RFC2119"/>.</t>
    </section>

    <section title="EUI-48 Addresses for use in Documentation"
        anchor="eui48">
      <t>The 256 unicast identifiers from 00-00-5E-XX-XX-XX to
        00-00-5E-XX-XX-XX have been allocated for use in documentation.</t>

      <t>The 256 multicast idenrifiers from 01-00-5E-XX-XX-XX to
        01-00-5E-XX-XX-XX have been allocated for use in documentation.</t>
    </section>

    <section title="EUI-64 Addresses for use in Documentation"
        anchor="eui64">
      <t>The 256 unicast identifiers from 00-00-5E-XX-XX-XX-XX-XX to
	00-00-5E-XX-XX-XX-XX-XX have been allocated for use in
	documentation.</t>

      <t>The 256 multicast idenrifiers from 01-00-5E-XX-XX-XX-XX-XX to
	01-00-5E-XX-XX-XX-XX-XX have been allocated for use in
	documentation.</t>
    </section>

    <section title="Guidance for Document Authors">
      <t>Documents which include literal EUI-48 or EUI-64 addresses,
	as examples or for other reasons, SHOULD choose addresses
	within the ranges described in <xref target="eui48"/> and
	<xref target="eui64"/>.</t>

      <t>Where literal EUI-48 or EUI-64 addresses in a document are
	required to be part of a different allocation, e.g. for
	reasons specific to a particular protocol, authors MAY use
	addresses from ranges other than those specified in <xref
	target="eui48"/> and <xref target="eui64"/>.</t>
    </section>

    <section title="Operational Implications">
      <t>Addresses within the ranges described in
	<xref target="eui48"/> and <xref target="eui64"/> SHOULD
	NOT be used for any purpose other than documentation.</t>
    </section>

    <section title="IANA Considerations">
      <t>The IANA is directed to document the allocations described in
        <xref target="eui48"/> and <xref target="eui64"/> in the
        appropriate IANA Ethernet Numbers subregistry.</t>

      <section title="IANA Unicast 48-bit MAC Addresses">
        <texttable>
          <ttcol>Addresses</ttcol>
          <ttcol>Usage</ttcol>
          <ttcol>Reference</ttcol>

          <c>XX-XX-XX to XX-XX-XX</c>
          <c>Documentation</c>
          <c>this document</c>
        </texttable>
      </section>

      <section title="IANA Multicast 48-bit MAC Addresses">
        <texttable>
          <ttcol>Addresses</ttcol>
          <ttcol>Usage</ttcol>
          <ttcol>Reference</ttcol>

          <c>XX-XX-XX to XX-XX-XX</c>
          <c>Documentation</c>
          <c>this document</c>
        </texttable>
      </section>

      <section title="IANA 64-bit MAC Addresses">
        <texttable>
          <ttcol>Addresses</ttcol>
          <ttcol>Usage</ttcol>
          <ttcol>Reference</ttcol>

          <c>XX-XX-XX-XX-XX to XX-XX-XX-XX-XX</c>
          <c>Documentation</c>
          <c>this document</c>
        </texttable>
      </section>
    </section>

    <section title="Security Considerations">
      <t>The specification presented in this document presents no
        additional threat to the Internet.</t>
    </section>

    <section title="Acknowledgements">
      <t><xref target="RFC5737"/>, concerning the allocation of IPv4
        address blocks for documentation, provided a useful reference
        in the preparation of this document.</t>

      <t>"EUI-48" and "EUI-64" are registered trademarks of the
        Institute of Electrical and Electronics Engineers (IEEE).</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      &rfc2119;
      &rfc5342;
      &rfc5737;

      <reference anchor="EUI48">
        <front>
          <title>Guidelines for use of a 48-bit Extended Unique
            Identifier (EUI-48)</title>
          <author>
            <organization>IEEE</organization>
            <address/>
          </author>
        </front>
        <format type="PDF" target="http://standards.ieee.org/develop/regauth/tut/eui48.pdf"/>
      </reference>

      <reference anchor="EUI64">
        <front>
          <title>Guidelines for use of a 64-bit Extended Unique
            Identifier (EUI-64)</title>
          <author>
            <organization>IEEE</organization>
            <address/>
          </author>
        </front>
        <format type="PDF" target="http://standards.ieee.org/develop/regauth/tut/eui64.pdf"/>
      </reference>
    </references>

    <section title="Editorial Notes">
      <t>This section (and sub-sections) to be removed prior to
        publication.</t>

      <section title="EUI-48/EUI-64 Identifier or Identifier Block Template">
        <figure>
          <artwork>
      Applicant Name:

        Joe Abley

      Applicant Email:

        jabley@teksavvy.ca

      Applicant Telephone: (starting with country code)

        +1 519 670 9327

      Use Name: (brief name of Parameter use such as "Foo Protocol")

        Docuemntation

      Document: (ID or RFC specifying use to which the identifier or
      block of identifiers will be put.)

        draft-jabley-eui48-eui64-doc-addr

      Specify whether this is an application for EUI-48 or EUI-64
      identifiers:

        Both EUI-48 and EUI-64

      Size of Block requested: (must be a power-of-two-sized block, can
      be a block of size one (2**0))

        256 EUI-48 addresses
        256 EUI-64 addresses

      Specify multicast, unicast, or both:

        Both
          </artwork>
        </figure>
      </section>

      <section title="Change History">
        <t>
          <list style="hanging">
            <t hangText="00">Initial idea, circulated for the purposes of
              entertainment.</t>
	  </list>
	</t>
      </section>
    </section>
  </back>
</rfc>