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

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Wed, 07 March 2018 16:27 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 4036812D87A for <dmm@ietfa.amsl.com>; Wed, 7 Mar 2018 08:27:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, 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 vKgcDzKS0fpx for <dmm@ietfa.amsl.com>; Wed, 7 Mar 2018 08:27:39 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E67412D7E6 for <dmm@ietf.org>; Wed, 7 Mar 2018 08:27:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5023; q=dns/txt; s=iport; t=1520440059; x=1521649659; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=IKV9lSYEL7yJrhXEmfe0B6xRbtIMgPSAabgTKRTvM/M=; b=ccVMiN4BNRMpNxT8C4pB6whDP/Rp6pbqjeCjf+9sRY67PLwGsQHBGyUI p2JdCDWPCyqNeXz5UT9uWtc02K8nxvvSB/mIhSeWloPivK/s86wBcgab6 LzwM4aivirE6NyNFm3DRtOTGIXDYUjZEz0tGsc1saMLE3sWusWOIaoS/O Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DQAABUEqBa/4kNJK1eGQEBAQEBAQEBAQEBAQcBAQEBAYMjLWZwKAqNbo17ggKBFpQ0ghUKGAuFDQKDCiE0GAECAQEBAQEBAmsnhSQBAQQBAWwbAgEIGC4nCyUCBAESG4UAEKsKhHKDcoIhhTGCLoFXgWaDLYMuAQECAQEXgSIOAyOFbQSOOIUQhx8JAoZSiiuBZ06DaYhciX6HLAIRGQGBLQEeOIFScBUZIYJDCYIoHIEEAQhud4lBgTCBGAEBAQ
X-IronPort-AV: E=Sophos;i="5.47,436,1515456000"; d="scan'208";a="80073679"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Mar 2018 16:27:38 +0000
Received: from XCH-RCD-009.cisco.com (xch-rcd-009.cisco.com [173.37.102.19]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w27GRcZg027148 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 7 Mar 2018 16:27:38 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-009.cisco.com (173.37.102.19) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 7 Mar 2018 10:27:37 -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; Wed, 7 Mar 2018 10:27:37 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: "cjbc@it.uc3m.es" <cjbc@it.uc3m.es>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] I-D Action: draft-ietf-dmm-distributed-mobility-anchoring-08.txt
Thread-Index: AQHTtjE0K5NvDl+GoUOrKoz3tG58Aw==
Date: Wed, 07 Mar 2018 16:27:37 +0000
Message-ID: <D6C55260.2ABD71%sgundave@cisco.com>
References: <152001452248.15759.10503474068105207448@ietfa.amsl.com> <D6BEDFE0.2AB347%sgundave@cisco.com> <1520372414.3784.7.camel@it.uc3m.es>
In-Reply-To: <1520372414.3784.7.camel@it.uc3m.es>
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="iso-8859-1"
Content-ID: <F8E9AA71721D46479C9A007B7E9D31E6@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/W9yllOny8T2gldOZh0Js21F9_Ng>
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: Wed, 07 Mar 2018 16:27:42 -0000

Hi Carlo,

Thank you.

> - Drastic shortening of the document, aiming at reducing its complexity
>and length. We have shortened from ~45 pages to ~15 pages.

Incredible! 

This is exactly what I hoped for. I never understood why there was so much
of text and what it was saying. This helps in IESG reviews. Given that its
a significant re-write, we unfortunately require some good amount of new
reviews. But, this is progress.


Sri





On 3/6/18, 1:40 PM, "Carlos Jesús Bernardos Cano" <cjbc@it.uc3m.es> wrote:

>Hi Sri,
>
>Apologies for the delayed reaction. We were busy with the last minute
>I-D submission.
>
>Regarding the changes that went into -08, this is my summary:
>
>- Drastic shortening of the document, aiming at reducing its complexity
>and length. We have shortened from ~45 pages to ~15 pages.
>
>- Simplification of the terminology and associated drawings, to just
>focus on data plane anchors (control plane is mentioned, but the
>document is about anchoring, so it is about data plane).
>
>- Removal of parts about hierarchical networks and NEMO.
>
>- Minimization of all the part about anchor mobility, as there is no
>solution that the WG has identified as viable. We limit the doc to
>anchor switching and anchor selection.
>
>- Keep the focus on the document being informational (it is not
>normative, so no solution is specified).
>
>Regarding open issues, I'd like to request some volunteers in the WG to
>take a look (even a first quick one) to provide some feedback about
>whether we are on the right track or not. It'd be really ideal if we
>could have some discussion before the f2f in London, so we could try to
>close/decide on open issues by the London meeting.
>
>Thanks!
>
>Carlos
>
>On Fri, 2018-03-02 at 19:05 +0000, Sri Gundavelli (sgundave) wrote:
>> 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-mobilit
>> > y-ancho
>> > ring/
>> > 
>> > There are also htmlized versions available at:
>> > https://tools.ietf.org/html/draft-ietf-dmm-distributed-mobility-anc
>> > horing-
>> > 08
>> > https://datatracker.ietf.org/doc/html/draft-ietf-dmm-distributed-mo
>> > bility-
>> > anchoring-08
>> > 
>> > A diff from the previous version is available at:
>> > https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-distributed-mobili
>> > ty-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
>> 
>> _______________________________________________
>> dmm mailing list
>> dmm@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmm