| recharter_old.txt | recharter_new_jari2.txt | |||
|---|---|---|---|---|
| Network-Based Mobility Extensions (netext) | Mobility Extensions (netext) | |||
| Last Modified: 2009-06-18 | Last Modified: 2010-01-19 | |||
| Additional information is available at tools.ietf.org/wg/netext | Additional information is available at tools.ietf.org/wg/netext | |||
| Chair(s): | Chair(s): | |||
| * Rajeev Koodli <rkoodli@starentnetworks.com> | * Rajeev Koodli <rkoodli@starentnetworks.com> | |||
| * Basavaraj Patil <basavaraj.patil@nokia.com> | * Basavaraj Patil <basavaraj.patil@nokia.com> | |||
| Internet Area Director(s): | Internet Area Director(s): | |||
| skipping to change at line 62 | skipping to change at line 62 | |||
| LMA Redirection: a specification for allowing an LMA to redirect a MAG | LMA Redirection: a specification for allowing an LMA to redirect a MAG | |||
| to another LMA. This is primarily needed as a way to perform load | to another LMA. This is primarily needed as a way to perform load | |||
| balancing. This functionality is complementary to implementation | balancing. This functionality is complementary to implementation | |||
| techniques that allow distributed MAG implementations to move tasks | techniques that allow distributed MAG implementations to move tasks | |||
| around without a visible impact at the protocol level, and the | around without a visible impact at the protocol level, and the | |||
| initial LMA discovery work in the NETLMM WG. An applicability statement | initial LMA discovery work in the NETLMM WG. An applicability statement | |||
| describing the situations where the new functionality is or is not | describing the situations where the new functionality is or is not | |||
| applicable has to be included in the specification. | applicable has to be included in the specification. | |||
| Hiding access technology changes from host IP layer: Proxy mobility is | ||||
| based on the assumption that changes in host IP stacks are | ||||
| undesirable. However, link layer implementations can hide the | ||||
| actually used physical interfaces from the IP stack. For instance, a | ||||
| single interface might transmit packets over different media, as is | ||||
| common practice in certain radio networks. This can be used to achieve | ||||
| inter-access handovers or flow mobility, i.e., the movement of | ||||
| selected flows from one access technology to another. The | ||||
| specification of any actual link layer mechanisms is outside the scope | ||||
| of the working group, but the group works on the following: | ||||
| - Informational applicability statement that analyzes the issues | ||||
| involved with this approach and characterizes the contexts in which | ||||
| such use is or is not appropriate. | ||||
| - The working group will determine if protocol extensions are required | ||||
| between the Proxy Mobile IPv6 network nodes (MAGs and LMAs) to | ||||
| support the ability for a single host interface to transmit packets | ||||
| over different media and the ability to distribute specific traffic | ||||
| flows on different media components of that single interface. The | ||||
| relevant protocol extensions will be developed as necessary. The WG | ||||
| will assume that there the host has an interface that is capable of | ||||
| employing multiple media. | ||||
| Radius Extensions to PMIP6: In order to enable network based | ||||
| mobility using PMIP6, the policy profile needs to signal a set of | ||||
| attributes and policies to the MAG and LMA. New Radius attributes | ||||
| need to be specified that are relevant to PMIP6 based | ||||
| mobility. This work item will specify Radius extensions and | ||||
| attributes specific to PMIP6. | ||||
| The work in this charter is entirely internal to the network and does | The work in this charter is entirely internal to the network and does | |||
| not affect hosts in any way (except perhaps through impacting packet | not affect host IP stack operation in any way (except perhaps through | |||
| forwarding capacity visible to the hosts). | impacting packet forwarding capacity visible to the hosts). The working | |||
| group is not allowed to specify new IP layer protocol mechanisms to signal | ||||
| mobility related events between the host and the network. | ||||
| The proposed activity will be complementary to the existing IETF Working | The proposed activity will be complementary to the existing IETF Working | |||
| Groups, notably the NETLMM and MEXT WGs. The NETEXT working group will | Groups, notably the NETLMM and MEXT WGs. The NETEXT working group will | |||
| also act as the primary forum where new extensions on top of the Proxy | also act as the primary forum where new extensions on top of the Proxy | |||
| Mobile IPv6 protocol can be developed. The addition of such new | Mobile IPv6 protocol can be developed. The addition of such new | |||
| extensions to the working group involves addition of the extension to | extensions to the working group involves addition of the extension to | |||
| this charter through the normal rechartering process. | this charter through the normal rechartering process. | |||
| This initial charter excludes a number of possible work items that were | ||||
| discussed in the March 2009 BOF. The working group should continue the | ||||
| discussion about a possible update of its charter and principles under | ||||
| which the new work items must operate under. The completion of the work | ||||
| items in the initial charter is not a requirement for the rechartering | ||||
| to become possible. | ||||
| Goals and Milestones: | Goals and Milestones: | |||
| May 2009 WG chartered | May 2009 WG chartered | |||
| Jul 2009 Initial WG draft on Bulk Refresh | Jul 2009 Initial WG draft on Bulk Refresh | |||
| Jul 2009 Decision on the inclusion of possible additional work items | Jul 2009 Decision on the inclusion of possible additional work items | |||
| Sep 2009 Initial WG draft on LMA Redirection | Sep 2009 Initial WG draft on LMA Redirection | |||
| Nov 2009 Initial WG draft on Route Optimization | Sep 2009 Initial WG draft on Localized Routing | |||
| Dec 2009 Submit Bulk Refresh to IESG for publication as a Proposed Standard RFC | Dec 2009 Submit Bulk Refresh to IESG for publication as a Proposed Standard RFC | |||
| Jan 2010 Submit LMA Redirection to IESG for publication as a Proposed Standard RFC | Jan 2010 Submit LMA Redirection to IESG for publication as a Proposed Standard RFC | |||
| Apr 2010 Submit Route Optimization to IESG for publication as a Proposed Standard RFC | Mar 2010 Initial WG document on RADIUS extensions to PMIP6 | |||
| Apr 2010 Submit Localized Routing to IESG for publication as a Proposed Standard RFC | ||||
| May 2010 Initial WG document on Applicability Statement on Multiple Media on One Interface | ||||
| Jun 2010 WG decision on what Proxy Mobile IPv6 support is needed to support multiple media on one interface | ||||
| Sep 2010 Initial WG document(s) on Proxy Mobile IPv6 Extensions to Support Multiple Media on One Interface | ||||
| Oct 2010 Submit RADIUS extensions to PMIP6 to IESG for publication as a Proposed Standard | ||||
| Dec 2010 Submit Applicability Statement on Multiple Media on One Interface to IESG for publication as Informational RFC | ||||
| Feb 2011 Submit Proxy Mobile IPv6 Extensions to Support Multiple Media on One Interface for publication as Proposed Standard RFC(s) | ||||
| End of changes. 7 change blocks. | ||||
| 12 lines changed or deleted | 38 lines changed or added | |||
This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/ | ||||