<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="info" docName="draft-matsuhira-m46a-16" ipr="trust200902">
  <front>
    <title abbrev="M46A">Multiple IPv4 - IPv6 mapped IPv6 address
    (M46A)</title>

    <author fullname="Naoki Matsuhira" initials="N." surname="Matsuhira">
      <organization>Neptela</organization>

      <address>
        <postal>
          <street/>

          <city/>

          <code/>

          <region/>

          <country>Japan</country>
        </postal>

        <phone/>

        <email>matsuhira.ietf@gmail.com</email>
      </address>
    </author>

    <date day="4" month="April" year="2024"/>

    <area/>

    <workgroup/>

    <keyword>IPv6</keyword>

    <keyword>Draft</keyword>

    <abstract>
      <t>This document specifies Multiple IPv4 - IPv6 mapped IPv6
      address(M46A) spefification. M46A is an IPv4-mapped IPv6 address with a
      plane ID. Unique allocation of plane id value enables IPv4 private
      address unique in IPv6 address space. This address may use IPv4 over
      IPv6 encapsulation and IPv4 - IPv6 translation.</t>
    </abstract>

    <note title="Requirements Language">
      <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>
    </note>
  </front>

  <middle>
    <section anchor="Sec-Introduction" title="Introduction">
      <t>This document specifies Multiple IPv4 - IPv6 mapped IPv6
      address(M46A) spefification. M46A is an IPv4-mapped IPv6 address with a
      plane ID. Unique allocation of plane ID value enables IPv4 private
      address unique in IPv6 address space.</t>

      <t>This address may use IPv4 over IPv6 encapsulation such as Multiple
      IPv4 - IPv6 mapping encapsulation - fixed prefix (M46E-FP) <xref
      target="I-D.draft-matsuhira-m46e-fp">M46E-FP</xref>, Multiple IPv4 -
      IPv6 mapping encapsulation - prefix resolution (M46E-PR)<xref
      target="I-D.draft-matsuhira-m46e-pr">M46E-PR</xref>, Multiple IPv4 -
      IPv6 mapping encapsulation - prefix translator (M46E-PT)<xref
      target="I-D.draft-matsuhira-m46e-pt">M46E-PT</xref> and IPv4 - IPv6
      translation such as Multiple IPv4 - IPv6 mapping translator (M46T)<xref
      target="I-D.draft-matsuhira-m46t">M46T</xref>.</t>
    </section>

    <section title="M46A architecture">
      <t/>

      <t><xref target="Fig-M46Eaddr-arch"/> shows M46A architecture.</t>

      <t><figure anchor="Fig-M46Eaddr-arch">
          <artwork><![CDATA[
 |      96 - m bits      |          m bits          |     32 bits  |
 +-----------------------+--------------------------+--------------+
 |      M46A prefix      |  IPv4 network plane ID   | IPv4 address |
 +-----------------------+--------------------------+--------------+
]]></artwork>
        </figure></t>

      <t/>

      <t>M46A consists of three parts as follows.</t>

      <t><list style="hanging">
          <t hangText="M46A prefix"><vspace blankLines="1"/>M46A prefix. This
          value is fixed value with M46E-FP, and non fixed value with
          M46E-PR.</t>

          <t hangText="IPv4 network plane ID"><vspace blankLines="1"/>IPv4
          network plane ID is the network identification of the IPv4 network
          plane.</t>

          <t hangText="IPv4 address"><vspace blankLines="1"/>IPv4 address</t>
        </list></t>

      <t/>

      <t/>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This document does not request IANA.</t>

      <t>Note to RFC Editor: this section may be removed on publication as an
      RFC.</t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t/>
    </section>
  </middle>

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

      <reference anchor="I-D.draft-matsuhira-m46e-fp">
        <front>
          <title>Multiple IPv4 - IPv6 mapping encapsulation - fixed
          prefix</title>

          <author fullname="N. Matsuhira" initials="N" surname="Matsuhira">
            <organization/>
          </author>

          <date day="1" month="June" year="2019"/>
        </front>
      </reference>

      <reference anchor="I-D.draft-matsuhira-m46e-pr">
        <front>
          <title>Multiple IPv4 - IPv6 address mapping encapsulation - prefix
          resolution</title>

          <author fullname="N. Matsuhira" initials="N" surname="Matsuhira">
            <organization/>
          </author>

          <date day="1" month="June" year="2019"/>
        </front>
      </reference>

      <reference anchor="I-D.draft-matsuhira-m46e-pt">
        <front>
          <title>Multiple IPv4 - IPv6 mapping encapsulation - prefix
          translator</title>

          <author fullname="N. Matsuhira" initials="N" surname="Matsuhira">
            <organization>Mats</organization>
          </author>

          <date day="1" month="June" year="2019"/>
        </front>
      </reference>

      <reference anchor="I-D.draft-matsuhira-m46t">
        <front>
          <title>Multiple IPv4 - IPv6 mapping translator</title>

          <author fullname="N. Matsuhira" initials="N" surname="Matsuhira">
            <organization/>
          </author>

          <date day="1" month="June" year="2019"/>
        </front>
      </reference>

      <?rfc ?>

      <?rfc ?>
    </references>
  </back>
</rfc>
