RFC 7429 on Distributed Mobility Management: Current Practices and Gap Analysis

rfc-editor@rfc-editor.org Fri, 23 January 2015 04:28 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 969311A016C; Thu, 22 Jan 2015 20:28:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 G5mWFwJ8EBct; Thu, 22 Jan 2015 20:28:08 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id AD8951A0169; Thu, 22 Jan 2015 20:28:08 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 14078187E26; Thu, 22 Jan 2015 20:27:44 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7429 on Distributed Mobility Management: Current Practices and Gap Analysis
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150123042744.14078187E26@rfc-editor.org>
Date: Thu, 22 Jan 2015 20:27:44 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/PQhBwSfSWitvKxhhLm5TJtzKhuk>
Cc: drafts-update-ref@iana.org, dmm@ietf.org, 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: Fri, 23 Jan 2015 04:28:10 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7429

        Title:      Distributed Mobility Management: Current Practices 
                    and Gap Analysis 
        Author:     D. Liu, Ed., JC. Zuniga, Ed.,
                    P. Seite, H. Chan, CJ. Bernardos
        Status:     Informational
        Stream:     IETF
        Date:       January 2015
        Mailbox:    liudapeng@chinamobile.com, 
                    JuanCarlos.Zuniga@InterDigital.com, 
                    pierrick.seite@orange.com,
                    h.a.chan@ieee.org, 
                    cjbc@it.uc3m.es
        Pages:      34
        Characters: 80973
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dmm-best-practices-gap-analysis-09.txt

        URL:        https://www.rfc-editor.org/info/rfc7429

This document analyzes deployment practices of existing IP mobility
protocols in a distributed mobility management environment.  It then
identifies existing limitations when compared to the requirements
defined for a distributed mobility management solution.

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