<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" []>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<?rfc iprnotified="no" ?>

<rfc category="std"
     docName="draft-petrescu-6man-ll-32-ietf-iana-request-00"
     ipr="trust200902"
     updates="RFC4291">

  <!-- category values: std, bcp, info, exp, and historic ipr values:
       trust200902, noModificationTrust200902,
       noDerivativesTrust200902, or pre5378Trust200902 you can add the
       attributes updates="NNNN" and obsoletes="NNNN" they will
       automatically be output with "(if approved)" -->

  <front>

    <title abbrev="IPv6-LL-plen">
      A request to IETF / IANA to Allocate a 32bit Link-Local Prefix
    </title>

    <author initials='A.' surname="Petrescu" fullname='Alexandre Petrescu'>
      <organization>CEA, LIST</organization>
      <address>
        <postal>
          <street>
            CEA Saclay
          </street>
          <city>
            Gif-sur-Yvette
          </city>
          <region>
            Ile-de-France
          </region>
          <code>
            91190
          </code>
          <country>
            France
          </country>
        </postal>
        <phone>
          +33169089223
        </phone>
        <email>
          Alexandre.Petrescu@cea.fr
        </email>
      </address>
    </author>

    <date year='2019'/>

    <!-- Meta-data Declarations -->

    <area>Internet</area>

    <workgroup>6MAN Working Group</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, link-local, subnet, IANA, fe80
    </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 draft requests IETF / IANA to assign the link local
	prefix fe80:1::/32.
      </t>
    </abstract>
  </front>

  <middle>
    <section title="Definitions and Statements">
      <t>
	The prefix of an IP address is formed by the n leftmost bits
	of the address.  (in a left-to-right writing system).
      </t>
    </section>
    
    <section title="Terminology"
	     anchor='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">RFC 2119</xref>.
      </t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>
	There can be security risks in the use of link-local addressed
	packets if they are not protected by tecnologies like IPsec.
	The risks are valid to all kinds of link-local addresses, be
	them fe80::/10 or fe80::/64.
      </t>
    </section>    

    <section anchor="IANA" title="IANA Considerations">
      <t>
	IANA is requested to assign fe80:1::/32.
      </t>
    </section>

    <section anchor="Contributors"
             title="Contributors">
      <t>
	Listed from 6man WG discussion.
      </t>
    </section>

    <section anchor="Acknowledgements"
             title="Acknowledgements">
    </section>

  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>
    <references title="Normative References">
      <?rfc
        include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119"
      ?>
    </references>

    <!-- <references title="Informative References"> -->
    <!-- </references> -->

    <section anchor='changelog'
             title='ChangeLog'>
      <t>
        The changes are listed in reverse chronological order, most
        recent changes appearing at the top of the list.
      </t>
    </section>

  </back>
</rfc>
