Re: [DMM] I-D Action: draft-ietf-dmm-distributed-mobility-anchoring-08.txt

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Fri, 02 March 2018 19:05 UTC

Return-Path: <sgundave@cisco.com>
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 45107126C25 for <dmm@ietfa.amsl.com>; Fri, 2 Mar 2018 11:05:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 apxXCB-qHqk1 for <dmm@ietfa.amsl.com>; Fri, 2 Mar 2018 11:05:17 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B09A31242F5 for <dmm@ietf.org>; Fri, 2 Mar 2018 11:05:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2672; q=dns/txt; s=iport; t=1520017517; x=1521227117; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=v4X9Ru2ZUSjiGR5L/z4mq0oP5vS4tiqH0q6U6ikI/Gg=; b=V9nUbAD8O+8ufYhrz68KlBddjlNk/p7Yfl+ikNRb6sU8bArwdSRQ7Ack jMvVenCFV1ELu2FQ57SmXTMYIb0yooJhOBouCuKoH/Fokv1DVyIz6X2RY svemj4yS75cgw/fTdeUHNP90Y/RhECV0uk6AQaMwAn5Jt0CcNlB8eHoMU 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D0AABNn5la/5hdJa1eGQEBAQEBAQEBAQEBAQcBAQEBAYNQZnAoCo1tjXmDGJQtghUKGA2FCwKCYSE0GAECAQEBAQEBAmscC4UkAgQBATg0GwIBCDYQJwslAgQThRsQrD6EcoN0giuFLIIpgVeFE4MuAQECAQEXgVaFbQSaXgkChlCKK4FnToNniFyJfIcsAhEZAYEtAR44gVJwFRkhgkMJgigcgXt3iy+BGAEBAQ
X-IronPort-AV: E=Sophos;i="5.47,413,1515456000"; d="scan'208";a="77969932"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Mar 2018 19:05:17 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w22J5GZP012074 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dmm@ietf.org>; Fri, 2 Mar 2018 19:05:16 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 2 Mar 2018 13:05:16 -0600
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1320.000; Fri, 2 Mar 2018 13:05:16 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] I-D Action: draft-ietf-dmm-distributed-mobility-anchoring-08.txt
Thread-Index: AQHTsllmWCuR0VweaESd6/JYJDX0CA==
Date: Fri, 02 Mar 2018 19:05:15 +0000
Message-ID: <D6BEDFE0.2AB347%sgundave@cisco.com>
References: <152001452248.15759.10503474068105207448@ietfa.amsl.com>
In-Reply-To: <152001452248.15759.10503474068105207448@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.188.60]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6C388573061E9A4F9B9FD585424A5C21@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/zGN7D4QtwVghFVZ0A_-bcTcqC9k>
Subject: Re: [DMM] I-D Action: draft-ietf-dmm-distributed-mobility-anchoring-08.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 02 Mar 2018 19:05:19 -0000

Hi Carlos/Anthony/Authors,

Thanks for the updates. Please summarize the changes that went into -08
version, and also let the WG know on the open issues.

Sri



On 3/2/18, 10:15 AM, "dmm on behalf of internet-drafts@ietf.org"
<dmm-bounces@ietf.org on behalf of internet-drafts@ietf.org> wrote:

>
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
>This draft is a work item of the Distributed Mobility Management WG of
>the IETF.
>
>        Title           : Distributed Mobility Anchoring
>        Authors         : H. Anthony Chan
>                          Xinpeng Wei
>                          Jong-Hyouk Lee
>                          Seil Jeon
>                          Carlos J. Bernardos
>	Filename        : draft-ietf-dmm-distributed-mobility-anchoring-08.txt
>	Pages           : 15
>	Date            : 2018-03-02
>
>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 the
>   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 a new IP address configured from the new IP prefix
>   which is anchored to the new network.  The mobility functions and
>   their operations and parameters are general for different
>   configurations.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-dmm-distributed-mobility-ancho
>ring/
>
>There are also htmlized versions available at:
>https://tools.ietf.org/html/draft-ietf-dmm-distributed-mobility-anchoring-
>08
>https://datatracker.ietf.org/doc/html/draft-ietf-dmm-distributed-mobility-
>anchoring-08
>
>A diff from the previous version is available at:
>https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-distributed-mobility-anch
>oring-08
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>dmm mailing list
>dmm@ietf.org
>https://www.ietf.org/mailman/listinfo/dmm