One document matched: draft-liu-dmm-mobility-api-01.xml

<?xml version="1.0" encoding="US-ASCII"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
    <!ENTITY RFC2119 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5014.xml'>
 ]>



<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?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="std" updates="5014" docName="draft-liu-dmm-mobility-api-01" ipr="trust200902">
  <front>
    <title abbrev="draft-liu-dmm-mobility-api-01">Mobility API Extension for
    Distributed Mobility Management</title>

    <author fullname="Dapeng Liu" initials="D." surname="Liu">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <street>32 Xuanwumen West Street</street>
          <city>Beijng</city>
          <code>100053</code>
          <region>Xicheng District</region>
          <country>China</country>
        </postal>
        <phone>+86-13911788933</phone>
        <email>liudapeng@chinamobile.com</email>
      </address>
    </author>

    <author fullname="Hui Deng" initials="H." surname="Deng">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <street>32 Xuanwumen West Street</street>
          <city>Beijng</city>
          <region>Xicheng District</region>
          <code>100053</code>
          <country>China</country>
        </postal>
        <phone></phone>
        <facsimile></facsimile>
        <email>denghui@chinamobile.com</email>
        <uri></uri>
      </address>
    </author>

    <date day="8" month="July" year="2013" />

    <area>Internet Area</area>

    <workgroup>Distributed Mobility Managment Working Group</workgroup>

    <keyword>DMM</keyword>

    <abstract>
      <t><xref target="RFC5014"/> specifies extension to socket API 
      to allow application to specify the preference among multiple 
      source addresses. <xref target="I-D.draft-korhonen-6man-prfix-properties"/>
      and <xref target="I-D.draft-bhandari-dhc-class-based-prefix-04"/> 
      propose to extend router advertisment to carry the prefix property 
      and class information. The mobile node can learn the prefix 
      property and class information from the router advertisment
      message. This document proposes an extension to <xref target="RFC5014"/> 
      to enable the application to select the distributed mobility
      management related prefixes.</t>

      <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>
    </abstract>
  </front>

  <middle>
    <section title="Proposed Extension of RFC 5014">
      <t><xref target="RFC5014"/>defines socket API extension used for 
      IPv6 source address selection. Application can use this API to 
      override the default source address selection mechanism for IPv6. 
      Currently, <xref target="RFC5014"/> defines the
      following types of source address selection preference:</t>

      <t>IPV6_PREFER_SRC_HOME /* Prefer Home address as source */</t>

      <t>IPV6_PREFER_SRC_COA /* Prefer Care-of address as source */</t>

      <t>IPV6_PREFER_SRC_TMP /* Prefer Temporary address as source */</t>

      <t>IPV6_PREFER_SRC_PUBLIC /* Prefer Public address as source */</t>

      <t>IPV6_PREFER_SRC_CGA /* Prefer CGA address as source */</t>

      <t>IPV6_PREFER_SRC_NONCGA /* Prefer a non-CGA address as source */</t>

      <t>This document proposes to extend the above definition to add two new
      flags:</t>

      <t>IPV6_PREFER_SRC_LOCAL_HNP:</t>

      <t>Prefer to use locally allocated home network prefix.</t>

      <t>IPV6_PREFER_SRC_REMOTE_HNP:</t>

      <t>Prefer to use the home network prefix that allocated by other access
      router instead of the one that the MN currently attach.</t>
      <!-- Note: Whether the flags should comply with draft-korhonen-6man-prfix-properties-->
    </section>

    <section title="Usage Example">
      <t>This section gives usage example for this API extension.</t>
      
      <t>
      	<xref target="I-D.draft-ietf-dmm-best-practices-gap-analysis-01"/> and
      	<xref target="I-D.draft-seite-dmm-dma-06"/>
      	discuss the distributed mobility management practice. It introduces
      	dynamic anchoring concept: the mobile node can have multiple
      	mobility anchor points and the mobile node select the locally
      	allocated IP address for the newly started application for optimized
      	routing. The mobile node can continue to use the IP address
      	allocated by previous anchor point for the on going session.
      	When the on going session terminate, the mobile node will
      	release the previous anchor point allocated IP address.
      </t>
      
      <t>
      	In the dynamic anchoring scenario, for the newly started application,
      	it should use the IP address allocated by the local mobility anchor.
      	The application can use IPV6_PREFER_SRC_LOCAL_HNP flag to select
      	the local allocated IP address. For the on going session, the
      	application can use IPV6_PREFER_SRC_REMOTE_HNP flag to select
      	the previous mobility anchor allocated home address to gurantee
      	the session continuity.
      </t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This document makes no request of 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>TBD</t>
    </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>
      	TBD
      </t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.2119"?>
      <?rfc include="reference.RFC.5014"?>
    </references>

    <references title="Informative References">
      
      <reference anchor="I-D.draft-seite-dmm-dma-06">
        <front>
          <title>Distributed Mobility Anchoring</title>

          <author fullname="P. Seite, P. Bertin ">
            <organization></organization>
          </author>
          <date day="9" month="January" year="2013" />
        </front>
        	<seriesInfo name="Internet-Draft" value="draft-seite-dmm-dma-06"/>
    			<format type="TXT" target="http://tools.ietf.org/html/draft-seite-dmm-dma-06"/>
      </reference>
      
      <reference anchor="I-D.draft-korhonen-6man-prfix-properties">
        <front>
          <title> IPv6 Prefix Properties</title>

          <author fullname="J. Korhonen etc.">
            <organization></organization>
          </author>
          <date day="25" month="February" year="2013" />
        </front>
        	<seriesInfo name="Internet-Draft" value="draft-korhonen-6man-prfix-properties"/>
    			<format type="TXT" target="http://tools.ietf.org/html/draft-korhonen-6man-prfix-properties-02"/>
      </reference>
      
      <reference anchor="I-D.draft-bhandari-dhc-class-based-prefix-04">
        <front>
          <title> DHCPv6 class based prefix </title>

          <author fullname="G. Halwasia etc.">
            <organization></organization>
          </author>
          <date day="18" month="February" year="2013" />
        </front>
        	<seriesInfo name="Internet-Draft" value="draft-bhandari-dhc-class-based-prefix-04"/>
    			<format type="TXT" target="http://tools.ietf.org/html/draft-bhandari-dhc-class-based-prefix-04"/>  
      </reference>
      
      <reference anchor="I-D.draft-ietf-dmm-best-practices-gap-analysis-01">
        <front>
          <title> Distributed Mobility Management: Current practices and gap analysis </title>

          <author fullname="D. Liu etc.">
            <organization></organization>
          </author>
          <date day="17" month="June" year="2013" />
        </front>
        	<seriesInfo name="Internet-Draft" value="draft-ietf-dmm-best-practices-gap-analysis-01"/>
    			<format type="TXT" target="http://tools.ietf.org/html/draft-ietf-dmm-best-practices-gap-analysis-01"/>  
      </reference>
      
    </references>
  </back>
</rfc>