<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc6830 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6830.xml">
]>

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc toc="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc rfcedstyle="yes"?>
<?rfc autobreaks="yes"?>
<?rfc docmapping="yes"?>

<rfc category="info" docName="draft-mi-lisp-high-capacity-00" ipr="trust200902">


  <front>
    
    <title abbrev="">A High-capacity and Real-time LISP Mapping Framework</title>

    <author fullname="Wei Mi" role="editor" surname="Wei Mi">
      <organization>IIE/Chinese Academy of Sciences</organization>

      <address>
        <postal>
          <street>No.89 Minzhuang Road, Haidian District</street>
          <city>Beijing</city>
          <code>100190</code>
          <country>CN</country>
        </postal>

        <phone>+86 10-82546356</phone>

        <email>miwei@iie.ac.cn</email>

       </address>
    </author>


    <author fullname="Jingguo Ge" surname="Jingguo Ge">
      <organization>IIE/Chinese Academy of Sciences</organization>
      <address>
    <postal>
      <street>No.89 Minzhuang Road, Haidian District</street>
      <city>Beijing</city>
      <code>100190</code>
      <country>CN</country>
    </postal>

    <phone>+86 10-82546559</phone>
    <email>gejingguo@iie.ac.cn</email>
      </address>
    </author>

    <date month="December" year="2020" />

    <area>General</area>

    <workgroup>LISP</workgroup>

    <keyword>high-capacity, real-time, mapping framework</keyword>

    <abstract>
      <t>This draft describes how the LISP mapping framework designed to be have the capability to provide efficient, real-time, high concurrent services when guarantee the scale. </t>
   
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>There are billions of mobile users and devices accommodated in the current network. With the rapid development of Internet of Things (IoT) technology, the global device number accessed to the network will increase to hundreds of billions by 2030, and these devices will generate data and contents at quadrillion magnitude.</t>
      
      <t>The LISP architecture and protocols  <xref target="RFC6830"></xref> introduces two new numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators (RLOCs) which is intended to provide overlay network functionality. Therefore, the LISP mapping framework is required to have a very large scale and capacity to provide services for all network entities.</t>
      
      <t>This document introduces a high-capacity and real-time LISP mapping framework, which consider the scalability and incremental deployment to meet the challenges, and have the capability to provide efficient, real-time, high concurrent services when guarantee the scale.</t>

    </section>

 <section title="Requirements of High-capacity and Real-time LISP Mapping Framework">   

 <section title="Functional Requirements">   

<t>Identifiers management </t>
        <t>It is required to have the capacity to manage the information of all named entities in the network, including: <list style="letters">
<t>Store the information of each named entity, and each record item may includes registration (attribute) information and mapping information between indentifiers and locators. </t>
<t>Maintain the record information, including: add items of newly registered indentifiers; delete the outdated and invalid items; update the mapping information when locators of named entities changes. </t>
<t>Provide query service for record information. </t>
     </list></t>

<t>Mapping resolution </t>
<t>It is required to provide efficient, real-time mapping service to support mobility and scalable routing. </t>

              </section>
<section title="Service Requirements">   
<t>Large scale and high capacity</t>

<t>It is required to have the capacity of serving all named entities in the network at an acceptable cost.</t>


<t>Scalability and incremental deployment</t>

<t>It is required to have a flexible and scalable architecture design which can adapt to the contraction and expansion of the ID space.</t>


<t>Real-time and high concurrent</t>

<t>It is required to have the capability to provide real-time, high concurrent services to meet the requirements of network applications.</t>

  </section>
        </section>
   
      <section title="The High-capacity and Real-time LISP Mapping Architecture">
<t>The high-capacity and real-time LISP mapping has a tiered architecture and each tier consists of multiple service nodes. <list style="letters">     
        
        <t>Tier 0: Tier 0 is the top tier in architecture, which is designed based on the principles of federalism and equal autonomy. Tier 0 consists of T0 nodes which are connected to each other in a fully meshed topology. Each autonomous domain (AD) has one T0 node.  The key function of T0 nodes is mapping resolution request information routing in Inter-AD and Intra-AD, no mapping resolution.</t>
        
        <t>Tier 1: Tier 1 is the medium tier in architecture, which consists of T1 nodes. T1 nodes are connected to the T0 nodes of their own AD, and divide the AD into resolution domains (RDs). The key function of T1 nodes are maping resolution and mapping resolution request information routing in Inter-RD.</t>
        
        <t>Tier 2: Tire 2 is at the bottom of architecture, which consists of T2 nodes. T2 nodes are connected to the T1 nodes of their own mapping resolution domain, and furtherly divide the RD into local domains (LDs). The key function of T2 nodes are mapping registration and resolution. Authoritative registration and resolution information are stored in T2 nodes.</t>
  
        </list></t>
  

 <section title="Key Functions">
     <t>Service nodes of different tiers of architecture have different functions. <list style="letters"> 

        <t>Key functions of T0 nodes.</t>
        
         <t>Key functions of T1 nodes.</t>
 <t>Key functions of T2 nodes.</t>
  
        </list></t> 

        </section>

<section title="Interfaces">
     <t>The interfaces between service nodes of different tiers are introduced.</t>
    </section>

 <section title="Service Procedures">
     
    </section>  

 </section>

    
  
    
    
   <section title="Acknowledgements">
      <t></t>
    </section>

    <!-- Possibly a 'Contributors' section ... -->

    <section anchor="IANA" title="IANA Considerations">
      <t>This memo includes no request to IANA.</t>

    </section>

    <section anchor="Security" title="Security Considerations">
      <t>All drafts are required to have a security considerations section.</t>
    </section>
    
  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>
    <references title="Informative References">
           <!--RFC 6830-->

      &rfc6830;
      
                           
    </references>
  
  </back>
</rfc>
