Last Call: <draft-ietf-dmm-distributed-mobility-anchoring-13.txt> (Distributed Mobility Anchoring) to Informational RFC

The IESG <iesg-secretary@ietf.org> Mon, 30 September 2019 13:04 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D355120236; Mon, 30 Sep 2019 06:04:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-dmm-distributed-mobility-anchoring-13.txt> (Distributed Mobility Anchoring) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
CC: Dapeng Liu <maxpassion@gmail.com>, draft-ietf-dmm-distributed-mobility-anchoring@ietf.org, maxpassion@gmail.com, dmm-chairs@ietf.org, dmm@ietf.org, suresh@kaloom.com
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <156984864037.507.11409433147422790992.idtracker@ietfa.amsl.com>
Date: Mon, 30 Sep 2019 06:04:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dQDXF24jWY8-77_wWSGgqOn-pO8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2019 13:04:00 -0000

The IESG has received a request from the Distributed Mobility Management WG
(dmm) to consider the following document: - 'Distributed Mobility Anchoring'
  <draft-ietf-dmm-distributed-mobility-anchoring-13.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2019-10-14. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   This document defines distributed mobility anchoring in terms of the
   different configurations and functions to provide IP mobility
   support.  A network may be configured with distributed mobility
   anchoring functions for both network-based or host-based mobility
   support according to the needs of mobility support.  In a distributed
   mobility anchoring environment, multiple anchors are available for
   mid-session switching of an IP prefix anchor.  To start a new flow or
   to handle a flow not requiring IP session continuity as a mobile node
   moves to a new network, the flow can be started or re-started using
   an IP address configured from the new IP prefix anchored to the new
   network.  If the flow needs to survive the change of network, there
   are solutions that can be used to enable IP address mobility.  This
   document describes different anchoring approaches, depending on the
   IP mobility needs, and how this IP address mobility is handled by the
   network.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dmm-distributed-mobility-anchoring/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-dmm-distributed-mobility-anchoring/ballot/

The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/3030/