Network-Based Mobility Extensions (netext) Internet Drafts

      
 Logical-interface Support for Multi-access enabled IP Hosts
 
 draft-ietf-netext-logical-interface-support-14.txt
 Date: 13/03/2016
 Authors: Telemaco Melia, Sri Gundavelli
 Working Group: Network-Based Mobility Extensions (netext)
 Formats: txt
A Logical-interface is a software semantic internal to the host operating system. This semantic is available in all popular operating systems and is used in various protocol implementations. The Logical-interface support is required on the mobile node attached to a Proxy Mobile IPv6 domain, for leveraging various network-based mobility management features such as inter-technology handoffs, multihoming and flow mobility support. This document explains the operational details of Logical-interface construct and the specifics on how the link-layer implementations hide the physical interfaces from the IP stack and from the network nodes on the attached access networks. Furthermore, this document identifies the applicability of this approach to various link-layer technologies and analyzes the issues around it when used in conjunction with various mobility management features.
 Proxy Mobile IPv6 Extensions to Support Flow Mobility
 
 draft-ietf-netext-pmipv6-flowmob-18.txt
 Date: 18/03/2016
 Authors: Carlos Bernardos
 Working Group: Network-Based Mobility Extensions (netext)
 Formats: txt
Proxy Mobile IPv6 allows a mobile node to connect to the same Proxy Mobile IPv6 domain through different interfaces. This document describes extensions to the Proxy Mobile IPv6 protocol that are required to support network based flow mobility over multiple physical interfaces. This document updates RFC 5213. The extensions described in this document consist of the operations performed by the local mobility anchor and the mobile access gateway to manage the prefixes assigned to the different interfaces of the mobile node, as well as how the forwarding policies are handled by the network to ensure consistent flow mobility management.

Network-Based Mobility Extensions (netext)

Last Modified: 2009-06-18

Additional information is available at tools.ietf.org/wg/netext

Chair(s):

  • Rajeev Koodli <rkoodli@starentnetworks.com>

  • Basavaraj Patil <basavaraj.patil@nokia.com>

    Internet Area Director(s):

  • Ralph Droms <rdroms@cisco.com>
  • Jari Arkko <jari.arkko@piuha.net>

    Internet Area Advisor:

  • Jari Arkko <jari.arkko@piuha.net>

    Mailing Lists:

    General Discussion: netext@ietf.org
    To Subscribe: https://www.ietf.org/mailman/listinfo/netext
    Archive: http://www.ietf.org/mail-archive/web/netext/current/maillist.html

    Description of Working Group:

    Proxy Mobile IPv6, specified in RFC 5213, is a network-based mobility
    protocol. It uses a Mobile Access Gateway (MAG) and a Local Mobility
    Anchor (LMA) to allow hosts to move around within a domain while keeping
    their address or address prefix stable. Proxy Mobile IPv6 has been
    incorporated into a number of products and deployments are starting.
    Certain deployment considerations, including localized routing and bulk
    refresh of lifetime are already emerging.

    The working group will focus on the following topics relevant for
    network-based mobility:

    Localized Routing: a specification for routing traffic between the
    MAG(s) without involving the LMA. That is, allow the MAGs to route
    traffic between hosts from one MAG to another, without being tunneled
    all the way to the LMA. This reduces latency and backhaul load.
    Applications such as voice can benefit from the reduced latency.

    Bulk Refresh: a specification of improving the signaling load for
    binding lifetime refresh. The current specifications call for the
    handling of each mobility session independent of each other. When a
    large number of hosts are served by a single MAG, a periodic refresh of
    the binding lifetimes can lead to a signaling storm. The purpose of the
    Bulk Refresh feature is to construct a protocol feature that allows such
    refreshes to occur on a per-MAG basis.

    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
    balancing. This functionality is complementary to implementation
    techniques that allow distributed MAG implementations to move tasks
    around without a visible impact at the protocol level, and the
    initial LMA discovery work in the NETLMM WG. An applicability statement
    describing the situations where the new functionality is or is not
    applicable has to be included in the specification.

    The work in this charter is entirely internal to the network and does
    not affect hosts in any way (except perhaps through impacting packet
    forwarding capacity visible to the hosts).

    The proposed activity will be complementary to the existing IETF Working
    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
    Mobile IPv6 protocol can be developed. The addition of such new
    extensions to the working group involves addition of the extension to
    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:

    May 2009  WG chartered
    Jul 2009  Initial WG draft on Bulk Refresh
    Jul 2009  Decision on the inclusion of possible additional work items
    Sep 2009  Initial WG draft on LMA Redirection
    Nov 2009  Initial WG draft on Route Optimization
    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
    Apr 2010  Submit Route Optimization to IESG for publication as a Proposed Standard RFC

    No Current Internet-Drafts

    No Request For Comments

    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.