RFC 7333 on Requirements for Distributed Mobility Management
rfc-editor@rfc-editor.org Thu, 21 August 2014 01:40 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0365C1A014B for <ietf-announce@ietfa.amsl.com>; Wed, 20 Aug 2014 18:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level:
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 bFUw_e68HDF5 for <ietf-announce@ietfa.amsl.com>; Wed, 20 Aug 2014 18:40:20 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id C99011A00BE for <ietf-announce@ietf.org>; Wed, 20 Aug 2014 18:40:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 97252180090; Wed, 20 Aug 2014 18:40:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7333 on Requirements for Distributed Mobility Management
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140821014017.97252180090@rfc-editor.org>
Date: Wed, 20 Aug 2014 18:40:17 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/j-gdqzyRDGiA92-hYxEl_KymdSU
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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: Thu, 21 Aug 2014 01:40:22 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7333
Title: Requirements for Distributed Mobility Management
Author: H. Chan, Ed.,
D. Liu, P. Seite,
H. Yokota, J. Korhonen
Status: Informational
Stream: IETF
Date: August 2014
Mailbox: h.a.chan@ieee.org,
liudapeng@chinamobile.com,
pierrick.seite@orange.com,
hidetoshi.yokota@landisgyr.com,
jouni.nospam@gmail.com
Pages: 24
Characters: 50110
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dmm-requirements-17.txt
URL: https://www.rfc-editor.org/rfc/rfc7333.txt
This document defines the requirements for Distributed Mobility
Management (DMM) at the network layer. The hierarchical structure in
traditional wireless networks has led primarily to centrally deployed
mobility anchors. As some wireless networks are evolving away from
the hierarchical structure, it can be useful to have a distributed
model for mobility management in which traffic does not need to
traverse centrally deployed mobility anchors far from the optimal
route. The motivation and the problems addressed by each requirement
are also described.
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/rfc.html
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