<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="ipv6-interface-ids.xsl"?>
<?xml-model href="ipv6-interface-ids.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="ipv6-interface-ids">
  <title>Reserved IPv6 Interface Identifiers</title>
  <created>2008-12-24</created>
  <updated>2014-02-13</updated>
  <registry id="ipv6-interface-ids-1">
    <title>Reserved IPv6 Interface Identifiers</title>
    <xref type="rfc" data="rfc5453"/><xref type="rfc" data="rfc7136"/>
    <registration_rule>Standards Action</registration_rule>
    <note>Full deployment of a new reserved IID value would require updates to 
IID generation code in every deployed IPv6 stack, so the technical 
justification for such a Standards Action would need to be extremely 
strong.
    </note>
    <record>
      <value>0000:0000:0000:0000</value>
      <description>Subnet-Router Anycast</description>
      <xref type="rfc" data="rfc4291"/>
      <date>2008-12-24</date>
    </record>
    <record>
      <value>0200:5EFF:FE00:0000-0200:5EFF:FE00:5212</value>
      <description>Reserved IPv6 Interface Identifiers corresponding to the IANA Ethernet Block</description>
      <xref type="rfc" data="rfc4291"/>
    </record>
    <record>
      <value>0200:5EFF:FE00:5213</value>
      <description>Proxy Mobile IPv6</description>
      <xref type="rfc" data="rfc6543"/>
    </record>
    <record>
      <value>0200:5EFF:FE00:5214-0200:5EFF:FEFF:FFFF</value>
      <description>Reserved IPv6 Interface Identifiers corresponding to the IANA Ethernet Block</description>
      <xref type="rfc" data="rfc4291"/>
    </record>
    <record>
      <value>FDFF:FFFF:FFFF:FF80-FDFF:FFFF:FFFF:FFFF</value>
      <description>Reserved Subnet Anycast Addresses</description>
      <xref type="rfc" data="rfc2526"/>
      <date>2008-12-24</date>
    </record>
  </registry>
  <people/>
</registry>
