One document matched: draft-jhlee-dmm-dnpp-00.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 PUBLIC '' 
  'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
]>

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

<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no"?>
<?rfc strict="yes"?>
<?rfc compact="yes" ?> 
<?rfc subcompact="yes" ?>

<rfc category="std" ipr="trust200902" docName="draft-jhlee-dmm-dnpp-00">

<front>
<title abbrev="Deprecated Network Prefix Provision">Deprecated Network Prefix Provision</title>

<author initials="J" surname="Lee" fullname="Jong-Hyouk Lee">
  <organization>Sangmyung University</organization>
    <address>
    <postal>
    <street>31, Sangmyeongdae-gil, Dongnam-gu</street>
    <city>Cheonan 330-720</city>
    <country>Republic of Korea</country>
  </postal>
  <email>jonghyouk@smu.ac.kr</email>
  </address>
</author>

<author initials="Z" surname="Yan" fullname="Zhiwei Yan">
  <organization>CNNIC</organization>
    <address>
    <postal>
    <street>No.4 South 4th Street, Zhongguancun</street>
    <city>Beijing 100190</city>
    <country>China</country>
  </postal>
  <email>yanzhiwei@cnnic.cn</email>
  </address>
</author>



<date year="2015"></date>
<area></area>
<workgroup>Distributed Mobility Management (DMM)</workgroup>

<abstract>
<t>
This document introduces new extensions to router advertisement and router solicitation messages. The extensions are used to provide a mobile node's deprecated network prefix information to an access router. This document updates  <xref target="RFC4861"/>.
</t>
</abstract>
</front>

<middle>

<!-- Introduction -->

<section anchor="intro" title="Introduction">

<t>
Router advertisement and router solicitation messages defined in <xref target="RFC4861"/> are used during stateless IPv6 autoconfiguration. A mobile node listens for router advertisement messages that are periodically sent by access routers on the local link or are explicitly requested by the mobile node using a router solicitation message. The router advertisement message contains information to allow the mobile node configures a global unicast IPv6 address. The provided information by the router advertisement message is, for instance, network prefix(es), default router address(es), hop limit, etc.
</t>

<t>
The router advertisement message is used by an access router to provide the network prefix information required for stateless IPv6 autoconfiguration, whereas the router solicitation message is used by a mobile node to quickly receive the router advertisement message from the access router. In other words, the current specification of Neighbor Discovery for IP version 6 does not specifies how the access router obtains the deprecated network prefix information (e.g., previous network prefix information) from the mobile node keeping deprecated IPv6 address(es) that are for instance global unicast IPv6 address(es) generated and used at previous access networks.
</t>

<t>
This document introduces new extensions to router advertisement and router solicitation messages to allow a mobile node provides its deprecated network prefix information to an access router.
</t>

</section>
<!-- Motivation (begin section) -->
<section title="Motivation">
<t>
A mobile node changes its point of attachment from a previous network to a new network while keeping its global unicast IPv6 address for communications with a correspondent node. The mobile node configures a new global unicast IPv6 address at the new network and uses the new address for new communications. The mobile node also may use the deprecated address (i.e., the previously configured address at the previous network) for the communications with the correspondent node.
</t>
<t>
Nowadays ingress filtering is widely used to prevent source address spoofing. In this case, when the mobile node sends packets with the deprecated address as a source address, the packets will be filtered unless a rule of ingress filtering is updated in advance.
</t>
<t>
An access router at the new network may need to obtain the mobile node's deprecated network prefix information. For instance, the new access router needs to establish a bidirectional tunnel with the previous access router of the mobile node for the communications associated with the deprecated address of the mobie node <xref target="Paper-Distributed.Mobility" />. 
</t>
</section>

<!-- Option Formats (begin section) -->
<section title="Option Formats">

<t>
A router solicitation message is extended to include the deprecated network prefix information. A router advertisement message is extended to include a flag that requests the mobile node to send a router solicitation message including the deprecated network prefix information. 
</t>

<!-- Network Prefix Provision in Router Solicitations (begin sub-section) -->
<section anchor="sec:rs" title="Network Prefix Provision in Router Solicitations">
<t>
A new flag is defined to indicate that a router solicitation message includes the deprecated network prefix information of a mobile node in the prefix information option.

</t>
<t><figure>
<artwork><![CDATA[
 4 5 6 7 8 9 0 1  
+-+-+-+-+-+-+-+-+ 
|L|A|D|Reserved1| 
+-+-+-+-+-+-+-+-+ 
]]></artwork>
</figure>
</t>
<t>
D:   1-bit "Deprecated network prefix" flag. It indicates that the prefix included in this prefix information option is the deprecated network prefix of the mobile node.
</t>
<t>
When the mobile node wants to send the deprecated prefix to the new access router, the prefix information option is used to carry the deprecated network prefix and the D flag is set to 1. 
</t>
<!-- Network Prefix Provision in Router Solicitations (end sub-section) -->
</section>


<!-- Network Prefix Provision in Router Advertisements (begin sub-section) -->
<section anchor="sec:ra" title="Network Prefix Provision in Router Advertisements">

<t>
A new flag is defined to request the deprecated network prefix information in a sourter solicitation message.
</t>
<t><figure>
<artwork><![CDATA[
 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+
|M|O|D|Reserved |
+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>
D:   1-bit "Deprecated network prefix" flag. It indicates that the deprecated network prefix of the mobile node is needed by an access router.
</t>
<t>
When a mobile node receives the router advertisement message containing the D flag set to 1, the mobile node should respond with a router solicitation message carring the prefix information option and with D flag set to 1 in the option. In the prefix information option, the deprecated network prefix of the mobile node is contained.
</t>
<t>
After the new access router learns the previous prefix of the specific mobile node, it updates the rule of ingress filter. Afterwards, the D flag in the following Routrer Advertisement message sent to this mobile node will be set to 0 and the mobile node will recognize that its previous prefix has been recorded by the access router. Then the mobile node will not feedback with Router Soliciation message.
</t>
<t>
This extension is not supported by the access router if the D flag is not influded in the Router Advertisement message and then the mobile node should not send Router Solicitation message accordingly.
</t>
<!-- Network Prefix Provision in Router Advertisements (end sub-section) -->
</section>

<!-- Option Formats (end section) -->
</section>



<section anchor="security" title="Security Considerations">
<t>TBD</t>
</section>

<section title="IANA Considerations">
<t>TBD</t>
</section>

</middle>


<back>

<references title="Normative References">

<?rfc include="reference.RFC.4861.xml" ?>

</references>

<references title="Informative References">

<?rfc include="reference.RFC.7333.xml"?>

<reference anchor="Paper-Distributed.Mobility">
<front>
<title>Distributed IP Mobility Management from the Perspective of the IETF: Motivations, Requirements, Approaches, Comparison, and Challenges</title>
<author initials="J" surname="Lee">
<organization />
</author>
<author initials="J" surname="Bonnin">
<organization />
</author>
<author initials="P" surname="Seite">
<organization />
</author>
<author initials="H" surname="Chan">
<organization />
</author>
<date month="October" year="2013" />
</front>
<seriesInfo name="" value="IEEE Wireless Communications" />
</reference>




</references>



</back>
</rfc>