<?xml version="1.0" encoding="US-ASCII"?>
<!-- This is built from a template for a generic Internet Draft. Suggestions for
     improvement welcome - write to Brian Carpenter, brian.e.carpenter @ gmail.com 
     This can be converted using the Web service at http://xml.resource.org/ -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<!-- You want a table of contents -->
<!-- Use symbolic labels for references -->
<!-- This sorts the references -->
<!-- Change to "yes" if someone has disclosed IPR for the draft -->
<!-- This defines the specific filename and version number of your draft (and inserts the appropriate IETF boilerplate -->
<?rfc sortrefs="yes"?>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc topblock="yes"?>
<?rfc comments="no"?>
<rfc category="info" docName="draft-yu-v6ops-split6-00" ipr="trust200902">
  <front>
    <title abbrev="SPLIT6">Separation Protocol of Locator and Identifier Towards IPv6</title>


    <author fullname="Haisheng Yu" initials="H." surname="Yu">
      <organization>BIIGroup</organization>

      <address>
        <postal>
          <street/>

          <city>Beijing</city>

          <code/>

          <country>China</country>
        </postal>

        <email>hsyu@biigroup.cn</email>
      </address>
    </author>

   


    <!---->

    <date day="29" month="june" year="2021"/>

    <area>Networking</area>

    <workgroup>Network Working Group</workgroup>
    
    <keyword>SPLIT6</keyword>


    <abstract>
       <t>In the current TCP/IP architecture, the IPv6 address has a dual meaning in semantics. It not only represents the topological location of the network node, but also the identity of the node, which is usually referred to as the semantic overload problem of the IP address. The semantically overloaded IP address represents the topological position of the network, and the topological position of the network generally does not move, so the device entering the new network environment needs to replace the new identity IP to adapt to the change of the topological position. The semantic overload of IP addresses is not conducive to supporting mobility and user identity authentication, resulting in tight storage space for routing equipment, lack of unified communication identification for network equipment, and difficulties in network traceability and management. In order to solve the problem of IP address semantic overload, this project focuses on the separation technology SPLIT6 of IP address identity and location.</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"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here. </t>
    </note>
  </front>

  <middle>
    <section title="Introduction">
<t>In the current Internet architecture, the IPv6 address carries too much semantics. The network layer protocol uses the IPv6 address as the location identifier of the user terminal, and the transport layer protocol uses the IPv6 address as the identity identifier of the user terminal. This dual identity of the IPv6 address cannot satisfy the Internet's increasing mobility and security requirements.
</t>

<t>In order to solve these problems caused by the semantic overload of IPv6 addresses, separating the location information and identity information of IPv6 addresses has become an important research direction.   </t>

    </section>

<section anchor="Security" title="Security Considerations"></section>

<section anchor="IANA" title="IANA Considerations"><t>This document does not include an IANA request.</t></section>

<section title="Acknowledgements">
 <t>The authors would like to acknowledge XXX for their valuable review and comments.</t>
</section>

 </middle>


   <back>

<references title="Normative References">
<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?>
<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8174.xml"?>
</references>
<references title="Informative References">
	<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2460.xml"?>
</references>

  </back>
</rfc>
