[DMM] RFC 8818 on Distributed Mobility Anchoring
rfc-editor@rfc-editor.org Mon, 19 October 2020 19:48 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A10ED3A083B; Mon, 19 Oct 2020 12:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktGpxsiDAdyx; Mon, 19 Oct 2020 12:48:22 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B05013A084B; Mon, 19 Oct 2020 12:48:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3FA0CF4071E; Mon, 19 Oct 2020 12:48:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dmm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20201019194820.3FA0CF4071E@rfc-editor.org>
Date: Mon, 19 Oct 2020 12:48:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/6aIeEK0HPfCUH_4JdTVrWyQ_C4I>
Subject: [DMM] RFC 8818 on Distributed Mobility Anchoring
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2020 19:48:26 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8818
Title: Distributed Mobility Anchoring
Author: H. Chan, Ed.,
X. Wei,
J. Lee,
S. Jeon,
CJ. Bernardos, Ed.
Status: Informational
Stream: IETF
Date: October 2020
Mailbox: h.a.chan@ieee.org,
weixinpeng@huawei.com,
jonghyouk@sejong.ac.kr,
seiljeon.ietf@gmail.com,
cjbc@it.uc3m.es
Pages: 18
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dmm-distributed-mobility-anchoring-15.txt
URL: https://www.rfc-editor.org/info/rfc8818
DOI: 10.17487/RFC8818
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, depending on the network's needs. 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 restarted 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.
This document is a product of the Distributed Mobility Management Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC