
From nobody Thu Jun  1 14:16:30 2017
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dmm@ietf.org
Delivered-To: dmm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 90F66126B7E; Thu,  1 Jun 2017 14:16:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, max.ldp@alibaba-inc.com, suresh.krishnan@gmail.com, dmm-chairs@ietf.org, dmm@ietf.org, Dapeng Liu <max.ldp@alibaba-inc.com>, draft-ietf-dmm-lma-controlled-mag-params@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <149635177550.22095.17830690730534529977.idtracker@ietfa.amsl.com>
Date: Thu, 01 Jun 2017 14:16:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/LpFzSe9ZTKoTKBUeot4wQVcjm9g>
Subject: [DMM] Protocol Action: 'LMA Controlled MAG Session Parameters' to Proposed Standard (draft-ietf-dmm-lma-controlled-mag-params-05.txt)
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 01 Jun 2017 21:16:16 -0000

The IESG has approved the following document:
- 'LMA Controlled MAG Session Parameters'
  (draft-ietf-dmm-lma-controlled-mag-params-05.txt) as Proposed Standard

This document is the product of the Distributed Mobility Management
Working Group.

The IESG contact persons are Suresh Krishnan and Terry Manderson.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-lma-controlled-mag-params/





Technical Summary

   This specification defines a new extension, LMA-Controlled-MAG-
   Session-Params to Proxy Mobile IPv6.  This option can be used by the
   LMA in PMIPv6 signaling for notifying the MAG to conform to various
   parameters contained in this extension.

Working Group Summary

  There was nothing noteworthy in the WG process.   There is consensus in the WG to publish this document.

Document Quality

  This document has been reviewed by PMIPv6 experts in the DMM working group.
  There are at least two operators that working on this document and believe this
  mechanism is useful for large scale deployment.

Personnel

  The document Shepherd is WG co-chair Dapeng Liu. The Responsible
  Area Director is Suresh Krishnan. 


From nobody Thu Jun  1 14:27:07 2017
Return-Path: <h.anthony.chan@huawei.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 E98F81250B8 for <dmm@ietfa.amsl.com>; Thu,  1 Jun 2017 14:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 s0f-tKz0qU_q for <dmm@ietfa.amsl.com>; Thu,  1 Jun 2017 14:27:03 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBC3E1241FC for <dmm@ietf.org>; Thu,  1 Jun 2017 14:27:01 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DOG14021; Thu, 01 Jun 2017 21:26:59 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 1 Jun 2017 22:26:57 +0100
Received: from DGGEMA401-HUB.china.huawei.com (10.3.20.42) by nkgeml414-hub.china.huawei.com (10.98.56.75) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 2 Jun 2017 05:26:54 +0800
Received: from DGGEMA505-MBX.china.huawei.com ([169.254.1.179]) by DGGEMA401-HUB.china.huawei.com ([10.3.20.42]) with mapi id 14.03.0301.000; Fri, 2 Jun 2017 05:26:53 +0800
From: h chan <h.anthony.chan@huawei.com>
To: "cjbc@it.uc3m.es" <cjbc@it.uc3m.es>, "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, dmm <dmm@ietf.org>
CC: Marco Liebsch <Marco.Liebsch@neclab.eu>, Dapeng Liu <maxpassion@gmail.com>, Seil Jeon <seiljeon@gmail.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, "Byju Pularikkal (byjupg)" <byjupg@cisco.com>
Thread-Topic: Distributed Mobility Anchoring - Draft Review Request
Thread-Index: AQHSrh9WAf4H7G3dsUy5jyuSwK7YYqG3beAAgDbe6nCAAEu0gIAiRJFA
Date: Thu, 1 Jun 2017 21:26:53 +0000
Message-ID: <6E31144C030982429702B11D6746B98C770EA3F5@DGGEMA505-MBX.china.huawei.com>
References: <D50A57EA.266603%sgundave@cisco.com> <1491464022.4390.9.camel@it.uc3m.es> <6E31144C030982429702B11D6746B98C770D4F89@DGGEMA505-MBX.china.huawei.com> <1494496831.3363.34.camel@it.uc3m.es>
In-Reply-To: <1494496831.3363.34.camel@it.uc3m.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.218.137.242]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.593086A3.01A3, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.1.179, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 0dfaa45876e0b7783a453e9d05202cbe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/SVOY8_b-eDep-cF32lEWAr-PvzE>
Subject: Re: [DMM] Distributed Mobility Anchoring - Draft Review Request
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: Thu, 01 Jun 2017 21:27:06 -0000

Q2FybG9zLA0KSWYgeW91IGhhZCBhbHJlYWR5IHN0YXJ0ZWQgdG8gcmV2aWV3IHZlcnNpb24gMywg
SSB3b25kZXIgaWYgaXQgbWlnaHQgd29yayBmYXN0ZXIgdG8gc2VuZCB0aG9zZSBjb21tZW50cyBm
aXJzdC4gDQpJIHRoaW5rIHRoZSBkaWZmZXJlbmNlcyBiZXR3ZWVuIHZlcnNpb24gMyBhbmQgdmVy
c2lvbiA1IGFyZSBtb3N0bHkgbm90IGluIG1ham9yIHRlY2huaWNhbCBpc3N1ZXMuIA0KDQpILiBB
bnRob255IENoYW4NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IENhcmxvcyBK
ZXPDunMgQmVybmFyZG9zIENhbm8gW21haWx0bzpjamJjQGl0LnVjM20uZXNdIA0KU2VudDogVGh1
cnNkYXksIE1heSAxMSwgMjAxNyA1OjAxIEFNDQpUbzogaCBjaGFuOyBTcmkgR3VuZGF2ZWxsaSAo
c2d1bmRhdmUpOyBkbW0NCkNjOiBNYXJjbyBMaWVic2NoOyBEYXBlbmcgTGl1OyBTZWlsIEplb247
IFN1cmVzaCBLcmlzaG5hbjsgQnlqdSBQdWxhcmlra2FsIChieWp1cGcpDQpTdWJqZWN0OiBSZTog
RGlzdHJpYnV0ZWQgTW9iaWxpdHkgQW5jaG9yaW5nIC0gRHJhZnQgUmV2aWV3IFJlcXVlc3QNCg0K
SGkgQW50aG9ueSwNCg0KTXkgYXBvbG9naWVzIGZvciBteSBkZWxheSBoYW5kbGluZyB0aGlzLiBJ
IHN0YXJ0ZWQgdG8gcmV2aWV3IHZlcnNpb24gMyBhIHdoaWxlIGFnbyBhbmQgdGhlbiBnb3Qgc3R1
Y2sgd2l0aCBhbm90aGVyIHRhc2suIEJ1dCBJJ2xsIGNoZWNrIHZlcnNpb24gNSBhbmQgcHJvdmlk
ZSBteSBjb21tZW50cyBpbiB0aGUgbmV4dCBmZXcgZGF5cy4NCg0KVGhhbmtzLA0KDQpDYXJsb3MN
Cg0KT24gV2VkLCAyMDE3LTA1LTEwIGF0IDIyOjI2ICswMDAwLCBoIGNoYW4gd3JvdGU6DQo+IENh
cmxvcywNCj4gDQo+IEkgaGF2ZSBhbHJlYWR5IHVwbG9hZGVkIHZlcnNpb24gNS4gVmVyc2lvbiA0
IGhhcyB0aGUgY29ycmVjdGlvbnMgZnJvbSANCj4gRGlyaywgYW5kIHZlcnNpb24gNSBoYXMgbWFu
eSBvZiB0aGUgY29ycmVjdGlvbnMgZnJvbSBCeWp1IGFuZCANCj4gUGllcnJpY2suDQo+IA0KPiBI
b3dldmVyIGlmIHlvdSBoYWQgYWxyZWFkeSBzdGFydGVkIHdyaXRpbmcgY29tbWVudHMgb24gdGhl
IGVhcmxpZXIgDQo+IHZlcnNpb24gKDMgb3IgNCksIHBsZWFzZSBmZWVsIGZyZWUgdG8gc2VuZCBh
bnkgcGFydGlhbCBjb3JyZWN0aW9ucyBhbmQgDQo+IGNvbW1lbnRzIG9uIHRoZSBlYXJsaWVyIHZl
cnNpb24gaWYgaXQgaXMgbW9yZSBjb252ZW5pZW50IHRvIHlvdS4NCj4gSWYgdGhlIGNvbW1lbnQg
aXMgb24gYSBwYXJ0aWN1bGFyIHBhZ2UgaW4gYW4gZWFybGllciB2ZXJzaW9uLCBJIHdpbGwgDQo+
IGZpZ3VyZSBvdXQgd2hlcmUgaXQgYXBwbGllcyB0byB0aGUgbGF0ZXN0IHZlcnNpb24uDQo+IA0K
PiBILiBBbnRob255IENoYW4NCj4gDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZy
b206IENhcmxvcyBKZXPDunMgQmVybmFyZG9zIENhbm8gW21haWx0bzpjamJjQGl0LnVjM20uZXNd
DQo+IFNlbnQ6IFRodXJzZGF5LCBBcHJpbCAwNiwgMjAxNyAyOjM0IEFNDQo+IFRvOiBTcmkgR3Vu
ZGF2ZWxsaSAoc2d1bmRhdmUpOyBkbW0NCj4gQ2M6IE1hcmNvIExpZWJzY2g7IERhcGVuZyBMaXU7
IGggY2hhbjsgU2VpbCBKZW9uOyBTdXJlc2ggS3Jpc2huYW47IA0KPiBCeWp1IFB1bGFyaWtrYWwg
KGJ5anVwZykNCj4gU3ViamVjdDogUmU6IERpc3RyaWJ1dGVkIE1vYmlsaXR5IEFuY2hvcmluZyAt
IERyYWZ0IFJldmlldyBSZXF1ZXN0DQo+IA0KPiBIaSBTcmksDQo+IA0KPiBTdXJlLCBubyBwcm9i
LCBidXQgSSBtaWdodCBuZWVkIG9uZSBhZGRpdGlvbmFsIHdlZWsgYXMgbmV4dCB3ZWVrIEknbSAN
Cj4gb2ZmIG9uIHZhY2F0aW9uLiBIb3BlIHRoYXQncyBmaW5lLg0KPiANCj4gVGhhbmtzLA0KPiAN
Cj4gQ2FybG9zDQo+IA0KPiBPbiBXZWQsIDIwMTctMDQtMDUgYXQgMTU6MTQgKzAwMDAsIFNyaSBH
dW5kYXZlbGxpIChzZ3VuZGF2ZSkgd3JvdGU6DQo+ID4gSGkgTWFyY28sIENhcmxvcywgU2VpbCAm
IEJpanUsDQo+ID4gDQo+ID4gSSBiZWxpZXZlIHlvdSBoYXZlIGFsbCBraW5kbHkgYWdyZWVkIHRv
IHJldmlldyB0aGUgYmVsb3cgZHJhZnQgYW5kIA0KPiA+IHBvc3QgeW91ciBmZWVkYmFjayB0byB0
aGUgbGlzdC4gwqBXaWxsIGJlIGdyZWF0IGlmIHlvdSBjYW4gZG8gdGhhdCBpbiANCj4gPiB0aGUg
bmV4dCAyIHdlZWtzIChDT0I6IDE5dGggb2YgQXByaWwsIDIwMTcpLg0KPiA+IA0KPiA+IFdlIHdh
bnQgdG8gd3JhcCB1cCB0aGlzIHdvcmsgc29vbiwgYnV0IHdhbnQgdG8gbWFrZSBzdXJlIHRoZSBk
cmFmdCANCj4gPiBpcyB0ZWNobmljYWxseSBjb3JyZWN0LiDCoEVkaXRvcmlhbCBpc3N1ZXMgY2Fu
IGJlIGZpeGVkLCBidXQgDQo+ID4gbWluaW1hbGx5IHRoZSBkcmFmdCBzaG91bGQgYmUgdGVjaG5p
Y2FsbHkgY29ycmVjdCBhbmQgd2Ugd2FudCB0byANCj4gPiBoZWFyIHRoYXQgZnJvbSB0aGUgZ3Jv
dXAuDQo+ID4gDQo+ID4gwqBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1k
bW0tZGlzdHJpYnV0ZWQtbW9iaWxpdHktYW4NCj4gPiBjaA0KPiA+IG9yaW5nLTAzDQo+ID4gDQo+
ID4gQW55IG90aGVyIGV4cGVydHMsIHBsZWFzZSByZXZpZXcgYW5kIHBvc3QgeW91ciBmZWVkYmFj
ay4NCj4gPiANCj4gPiBBbnRob255IOKAkyBQbGVhc2Ugd29yayB3aXRoIHRoZSByZXZpZXdlcnMu
DQo+ID4gDQo+ID4gDQo+ID4gDQo+ID4gwqDigJTigJTigJTigJTigJTigJQtDQo+ID4gwqANCj4g
PiAxMDowMMKgwqDCoMKgwqDCoCBUaXRsZTogRGlzdHJpYnV0ZWQgTW9iaWxpdHkgQW5jaG9yaW5n
DQo+ID4gwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBQcmVzZW50ZXI6IEggQW50aG9ueSBDaGFuDQo+
ID4gwqDCoMKgwqDCoMKgwqDCoMKgwqAgwqBUaW1lOiAxMCBtaW51dGVzDQo+ID4gwqDCoMKgwqDC
oMKgwqDCoMKgwqDCoCBEcmFmdDogaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWll
dGYtZG1tLWRpc3RyDQo+ID4gaWINCj4gPiB1dGVkLW1vYmlsaXR5LWFuY2hvcmluZy0wMw0KPiA+
IMKgDQo+ID4gwqANCj4gPiBBbnRob255IHN1bW1hcml6ZXMgdXBkYXRlLg0KPiA+IENvbW1lbnQg
ZnJvbSBBbGV4IGFib3V0IG5lbW8gbWlzc2VkLg0KPiA+IERpZmZlcmVudCBtb2RlcywgbW92ZSB0
byBuZXcgbmV0d29yayBhbmQga2VlcC9naXZlIHVwIG9sZCBJUCANCj4gPiBhZGRyZXNzLg0KPiA+
IFJlc3Qgb2Ygd29yayBmb3IgV0cgdG8gcmV2aWV3IGFuZCBjb21tZW50Lg0KPiA+IMKgDQo+ID4g
U3JpOiB3ZSBuZWVkIGdvb2QgcmV2aWV3cyBvbiB0aGlzIGRvY3VtZW50LiBFZGl0b3JpYWwgYnV0
IGFsc28gDQo+ID4gdGVjaG5pY2FsbHkuDQo+ID4gwqANCj4gPiBWb2x1bnRlZXJzOiBSZXZpZXdz
OiBNYXJjbywgQ2FybG9zLCBTZWlsDQo+ID4gwqANCj4gPiANCj4gPiDigJTigJTigJTigJTigJTi
gJQtDQo=


From nobody Fri Jun  2 11:11:45 2017
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dmm@ietf.org
Delivered-To: dmm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E3B24126B6D; Fri,  2 Jun 2017 11:11:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-dmm-mag-multihoming@ietf.org, jouni.nospam@gmail.com, Jouni Korhonen <jouni.nospam@gmail.com>, suresh.krishnan@gmail.com, dmm-chairs@ietf.org, dmm@ietf.org
Reply-To: ietf@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <149642709788.31875.5460790199457314806.idtracker@ietfa.amsl.com>
Date: Fri, 02 Jun 2017 11:11:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/aME-Hthu4027CXi5HchRizdJ6qw>
Subject: [DMM] Last Call: <draft-ietf-dmm-mag-multihoming-03.txt> (MAG Multipath Binding Option) to Proposed Standard
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.22
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 Jun 2017 18:11:38 -0000

The IESG has received a request from the Distributed Mobility Management
WG (dmm) to consider the following document:
- 'MAG Multipath Binding Option'
  <draft-ietf-dmm-mag-multihoming-03.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-06-16. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This specification defines extensions to the Proxy Mobile IPv6
   protocol for allowing a mobile access gateway to register more than
   one proxy care-of-address with the local mobility anchor and to
   simultaneously establish multiple IP tunnels with the local mobility
   anchor.  This capability allows the mobile access gateway to utilize
   all the available access networks for routing mobile node's IP
   traffic.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dmm-mag-multihoming/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-dmm-mag-multihoming/ballot/


No IPR declarations have been submitted directly on this I-D.





From nobody Mon Jun  5 08:09:50 2017
Return-Path: <cjbc@it.uc3m.es>
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 C4F36129AFF for <dmm@ietfa.amsl.com>; Mon,  5 Jun 2017 08:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=it-uc3m-es.20150623.gappssmtp.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 8InPYArTqCYi for <dmm@ietfa.amsl.com>; Mon,  5 Jun 2017 08:09:45 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 274D9128B4E for <dmm@ietf.org>; Mon,  5 Jun 2017 08:09:45 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id n195so78416626wmg.1 for <dmm@ietf.org>; Mon, 05 Jun 2017 08:09:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=it-uc3m-es.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:reply-to:to:cc:date:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=ljN1mYeok8wB6UJeg7h4CA6/UXiOCAXXtIl1lDPV+rs=; b=eKC+P1naKqbDk82Tv6Fys77gRtxmJFsN6d/jdyZCx0ik9FXKywSuHL+i2praSbmG1l saMLGT+AE0b4uZghuHTVQWnBFNYquuDT7xp27MWm1OMyrJmkA0gwCQytnvb07vP0PZn2 zIaGTv+xyx8sUAcNPw4DOrxJBoWX9rqqYampoaf3Nv598TC994VcXr9FcUx+mf4GelLH xv79hP/ooSvbygmWYli2ayGYPqkHT021oIQTm7OB94bW6NMjW2pSrX3M4MLvULgb0F7M aYGj5dPXHnLbRmw3t5tGeegGiVnG5MvXO/Qz0wajsmEw2h1VuzbROGOKw1RvtXdqg47Y 8liA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:reply-to:to:cc:date :in-reply-to:references:organization:mime-version :content-transfer-encoding; bh=ljN1mYeok8wB6UJeg7h4CA6/UXiOCAXXtIl1lDPV+rs=; b=ODXdwAtUbpF5BhAv1ItNtFHPPxv7K354EB4Ac1kT7qIkG5bv6WOamblfof2sTL0Kc/ 5kxq5rLG6sGKQGodMxST/f768JO9BbY/RHQ8aU/vii67pvC1nEQvjDcGVNuytVFMrazj qNZM7/HsdgHimfH9DNutWy2P3jx75R1o6fH8dMhRhUV24ShXPd0hB0epEtvphWvmncaW CoVgQitbsLnWpDds0TRaB3YOjg8SpOhdkvbvIxGKj0Hc76W+1yyUyfGvjLNXrXEuTj8r GnW9QiZOfaeWQ36y55Y9i7rmeI1517IKZgltsSJQEZ11G2uliuWGxqubPjeBG4uyTl1a lGjw==
X-Gm-Message-State: AODbwcDNto/sHSqctADef1Ox2rWrIHhUzyPnum7gNkD3IAeQtBPwN7+R ABIW4wn8GZ/n1CbK
X-Received: by 10.28.133.210 with SMTP id h201mr8794242wmd.3.1496675383433; Mon, 05 Jun 2017 08:09:43 -0700 (PDT)
Received: from acorde ([2001:720:410:1010:d681:d7ff:fe28:350b]) by smtp.gmail.com with ESMTPSA id c11sm8321771wrb.58.2017.06.05.08.09.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 05 Jun 2017 08:09:42 -0700 (PDT)
Message-ID: <1496675381.8422.66.camel@it.uc3m.es>
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
Reply-To: cjbc@it.uc3m.es
To: h chan <h.anthony.chan@huawei.com>, "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, dmm <dmm@ietf.org>
Cc: Marco Liebsch <Marco.Liebsch@neclab.eu>, Dapeng Liu <maxpassion@gmail.com>,  Seil Jeon <seiljeon@gmail.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, "Byju Pularikkal (byjupg)" <byjupg@cisco.com>
Date: Mon, 05 Jun 2017 17:09:41 +0200
In-Reply-To: <6E31144C030982429702B11D6746B98C770EA3F5@DGGEMA505-MBX.china.huawei.com>
References: <D50A57EA.266603%sgundave@cisco.com> <1491464022.4390.9.camel@it.uc3m.es> <6E31144C030982429702B11D6746B98C770D4F89@DGGEMA505-MBX.china.huawei.com> <1494496831.3363.34.camel@it.uc3m.es> <6E31144C030982429702B11D6746B98C770EA3F5@DGGEMA505-MBX.china.huawei.com>
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.22.6-1 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/7xkF1wab6XakD3IbteOAnRgRc24>
Subject: Re: [DMM] Distributed Mobility Anchoring - Draft Review Request
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: Mon, 05 Jun 2017 15:09:49 -0000

Hi Anthony, all,

Again, apologies for my belated review. Please find below my comments.

- Overall, I think the draft is hard to read/follow. Part of this comes
from the fact of the extensive use of acronyms. But I think this is not
the only reason. I think it is not clear if the document is specifying
a solution or just presenting the scenarios and challenges derived from
having multiple distributed anchors.

- Related to the former comment. What is the scope of the document? If
it is about defining solutions, the document is far from achieving that
(and it is classified as informational). If the idea is to explore this
problem, then I think the scope should be clarified and I'd suggest to
narrow it down (currently the document addresses too many things and
make it hard to follow).

- Why is the document referring to network slices? I see that awkward.
The definition of slice is not yet very clear and in any case, is there
anything in the document that is slice-specific? Unless it is the case,
one could claim that most of the IETF protocols would apply to a
"network or a network slice", but this is not explicitly stated.

- The document make use of RFC2119 terminology, but I don't think this
is fine. The document is informational (this alone does not prevent
using RFC2119 terminology, but I don't see the need). Besides, one
"SHOULD" appears in the introduction, which in general is not a
normative section of a draft.

- It would be better if the introduction does not use terms that are
introduced/enumerated in the Conventions and Terminology section.

- The text about "IP prefix/address anchoring" in Section 2 is not
really a definition.

- The text about "Location Management (LM) function" in Section 2 is
not clear.

- There is no definition/reference to the term "Mobility controller".

- What is DMM specific of the "Security Management (SM) function"? To
me, this is as in any mobility protocol, so I don't see why a document
about distributed anchorning has to define a "new" function.

- Weird writing: "The CPA may co-locate with DPA or may separate".

- Typo? "for use by AN MN". I guess it should be "for use by an MN".

- Figure 1 is not very easy to follow. I have to admit that I have been
having difficulties with this type of figure since they started to be
used.

- When discussing the scenarios with network mobility, it is mentioned
that "An IP prefix/address IPn1 anchored to the MR is assigned for use
by the MNN in the mobile network." In my opinion, the prefix is
delegated to the MR for use, but it is not anchored to the MR, as the
MR may move and the address can only be topologically valid at one
location.

- In Section 3.2.2, there are different approaches mentioned to update
forwarding tables (basically to allow a change of anchor). There have
been many discussion in the past about this, with no consensus at all
on the feasibility of using any of this slides (routing based) on
scalable scenarios (its applicability seems to be limited to very
specific scenarios). Moreover, there are important security and
scalability implications on this type of solution, so I'd not include
this in the draft. I think there is no Internet-wide scalable solution
that enables switching an anchor in the middle of a session.

- FM-state:1 introduces a lot of complexity, for a problem that it is
already quite complex. Do we need to go into this?

- FR-mr:2 reminds me a lot about Route Optimization for NEMO, which
never took off at IETF mainly because of security issues and
complexity. I think this would require quite a lot of work to be
properly done in DMM.

- The security considerations section does not really explain what are
the issues and how to solve them. It just moves all the complexity to
the so-called SM function.

- With the fair disclaimer that I might not be objective here, I think
the document misses quite a lot of existing works (even as active IETF
drafts) proposing solutions for the distribution of mobility anchors.

To sum-up, I think the draft is not yet ready for IETF LC.

Thanks,

Carlos

On Thu, 2017-06-01 at 21:26 +0000, h chan wrote:
> Carlos,
> If you had already started to review version 3, I wonder if it might
> work faster to send those comments first. 
> I think the differences between version 3 and version 5 are mostly
> not in major technical issues. 
> 
> H. Anthony Chan
> 
> -----Original Message-----
> From: Carlos Jesús Bernardos Cano [mailto:cjbc@it.uc3m.es] 
> Sent: Thursday, May 11, 2017 5:01 AM
> To: h chan; Sri Gundavelli (sgundave); dmm
> Cc: Marco Liebsch; Dapeng Liu; Seil Jeon; Suresh Krishnan; Byju
> Pularikkal (byjupg)
> Subject: Re: Distributed Mobility Anchoring - Draft Review Request
> 
> Hi Anthony,
> 
> My apologies for my delay handling this. I started to review version
> 3 a while ago and then got stuck with another task. But I'll check
> version 5 and provide my comments in the next few days.
> 
> Thanks,
> 
> Carlos
> 
> On Wed, 2017-05-10 at 22:26 +0000, h chan wrote:
> > Carlos,
> > 
> > I have already uploaded version 5. Version 4 has the corrections
> > from 
> > Dirk, and version 5 has many of the corrections from Byju and 
> > Pierrick.
> > 
> > However if you had already started writing comments on the earlier 
> > version (3 or 4), please feel free to send any partial corrections
> > and 
> > comments on the earlier version if it is more convenient to you.
> > If the comment is on a particular page in an earlier version, I
> > will 
> > figure out where it applies to the latest version.
> > 
> > H. Anthony Chan
> > 
> > -----Original Message-----
> > From: Carlos Jesús Bernardos Cano [mailto:cjbc@it.uc3m.es]
> > Sent: Thursday, April 06, 2017 2:34 AM
> > To: Sri Gundavelli (sgundave); dmm
> > Cc: Marco Liebsch; Dapeng Liu; h chan; Seil Jeon; Suresh Krishnan; 
> > Byju Pularikkal (byjupg)
> > Subject: Re: Distributed Mobility Anchoring - Draft Review Request
> > 
> > Hi Sri,
> > 
> > Sure, no prob, but I might need one additional week as next week
> > I'm 
> > off on vacation. Hope that's fine.
> > 
> > Thanks,
> > 
> > Carlos
> > 
> > On Wed, 2017-04-05 at 15:14 +0000, Sri Gundavelli (sgundave) wrote:
> > > Hi Marco, Carlos, Seil & Biju,
> > > 
> > > I believe you have all kindly agreed to review the below draft
> > > and 
> > > post your feedback to the list.  Will be great if you can do that
> > > in 
> > > the next 2 weeks (COB: 19th of April, 2017).
> > > 
> > > We want to wrap up this work soon, but want to make sure the
> > > draft 
> > > is technically correct.  Editorial issues can be fixed, but 
> > > minimally the draft should be technically correct and we want to 
> > > hear that from the group.
> > > 
> > >  https://tools.ietf.org/html/draft-ietf-dmm-distributed-mobility-
> > > an
> > > ch
> > > oring-03
> > > 
> > > Any other experts, please review and post your feedback.
> > > 
> > > Anthony – Please work with the reviewers.
> > > 
> > > 
> > > 
> > >  ——————-
> > >  
> > > 10:00       Title: Distributed Mobility Anchoring
> > >             Presenter: H Anthony Chan
> > >             Time: 10 minutes
> > >             Draft: https://tools.ietf.org/html/draft-ietf-dmm-dis
> > > tr
> > > ib
> > > uted-mobility-anchoring-03
> > >  
> > >  
> > > Anthony summarizes update.
> > > Comment from Alex about nemo missed.
> > > Different modes, move to new network and keep/give up old IP 
> > > address.
> > > Rest of work for WG to review and comment.
> > >  
> > > Sri: we need good reviews on this document. Editorial but also 
> > > technically.
> > >  
> > > Volunteers: Reviews: Marco, Carlos, Seil
> > >  
> > > 
> > > ——————-


From nobody Wed Jun  7 08:37:56 2017
Return-Path: <session-request@ietf.org>
X-Original-To: dmm@ietf.org
Delivered-To: dmm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BDDF912ECC4; Wed,  7 Jun 2017 08:37:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: suresh.krishnan@gmail.com, dmm-chairs@ietf.org, dmm@ietf.org, sgundave@cisco.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.53.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149684987468.2667.134591540383352794.idtracker@ietfa.amsl.com>
Date: Wed, 07 Jun 2017 08:37:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/rTGPsVlrsYxVyxjE0pBW6njCMgU>
Subject: [DMM] dmm - New Meeting Session Request for IETF 99
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.22
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 Jun 2017 15:37:55 -0000

A new meeting session request has just been submitted by Sri Gundavelli, a Chair of the dmm working group.


---------------------------------------------------------
Working Group Name: Distributed Mobility Management
Area Name: Internet Area
Session Requester: Sri Gundavelli

Number of Sessions: 1
Length of Session(s):  2.5 Hours
Number of Attendees: 40
Conflicts to Avoid: 





People who must be present:
  Sri Gundavelli
  Suresh Krishnan
  Dapeng Liu

Resources Requested:

Special Requests:
  
---------------------------------------------------------


From nobody Wed Jun  7 08:39:48 2017
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 B0EF612ECC6 for <dmm@ietfa.amsl.com>; Wed,  7 Jun 2017 08:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 swtW0LTaN88b for <dmm@ietfa.amsl.com>; Wed,  7 Jun 2017 08:39:44 -0700 (PDT)
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 BA1F312ECC4 for <dmm@ietf.org>; Wed,  7 Jun 2017 08:39:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8460; q=dns/txt; s=iport; t=1496849982; x=1498059582; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=bd5qG74NopGpwtuo1oGutDc6lVabalgnpUIWk0J11o0=; b=kocNysBe+hSVhZvnwNYqbb3PWlmAAPp1kMr3ZP853zx2zGsnl5JrwEIY m8OhCToGDjHt5kuLhmrCLLdSOhq5Hc/82dEl78EzKjm4EbSCsceBOFG7k VGvww5CiAO3EUI6wEv1dpuIitOr9Xzs+aKe/5IcFuIjxOl+YBb9T2XZQL Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CYAADMHThZ/5ldJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1higQ0HjgSRaJYAghAshXQCAgKCdD8YAQIBAQEBAQEBayiFGAE?= =?us-ascii?q?BAQECAWsaBAIBBgIRBAEBAScHMhQJCAIEExuKCAgQkGGgBot/AQEBAQEBAQMBA?= =?us-ascii?q?QEBAQEBARsFhFCCEYFgghSBDIElgyEkhXMFnjkChySMEoIGhT6DboZOcIgfi1c?= =?us-ascii?q?BHziBCnQVHCqHBwF2hxOBMoENAQEB?=
X-IronPort-AV: E=Sophos;i="5.39,311,1493683200"; d="scan'208";a="435254533"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Jun 2017 15:39:41 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v57Fdf4t030678 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dmm@ietf.org>; Wed, 7 Jun 2017 15:39:41 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 7 Jun 2017 10:39:40 -0500
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.1210.000; Wed, 7 Jun 2017 10:39:40 -0500
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: dmm <dmm@ietf.org>
Thread-Topic: Distributed Mobility Anchoring - Draft Review Request
Thread-Index: AQHS36RHFnblL79w5kWiq7CZN8kxFA==
Date: Wed, 7 Jun 2017 15:39:40 +0000
Message-ID: <D55D5947.27D841%sgundave@cisco.com>
References: <D50A57EA.266603%sgundave@cisco.com> <1491464022.4390.9.camel@it.uc3m.es> <6E31144C030982429702B11D6746B98C770D4F89@DGGEMA505-MBX.china.huawei.com> <1494496831.3363.34.camel@it.uc3m.es> <6E31144C030982429702B11D6746B98C770EA3F5@DGGEMA505-MBX.china.huawei.com> <1496675381.8422.66.camel@it.uc3m.es>
In-Reply-To: <1496675381.8422.66.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.1.161129
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.188.53]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <E8EC86F9C059DA41BE57B5B1314493BB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/QgSe5wb5NLSlmHs_8i9dy-jxh5o>
Subject: Re: [DMM] Distributed Mobility Anchoring - Draft Review Request
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 Jun 2017 15:39:46 -0000

Hi Carlos,

Thanks for the detailed review. This is very good.

Anthony/Authors: Please address these comments/concerns. This is coming
from a domain expert and we should make sure we resolve all the identified
issues.


Regards
Sri


On 6/5/17, 8:09 AM, "Carlos Jes=FAs Bernardos Cano" <cjbc@it.uc3m.es> wrote=
:

>Hi Anthony, all,
>
>Again, apologies for my belated review. Please find below my comments.
>
>- Overall, I think the draft is hard to read/follow. Part of this comes
>from the fact of the extensive use of acronyms. But I think this is not
>the only reason. I think it is not clear if the document is specifying
>a solution or just presenting the scenarios and challenges derived from
>having multiple distributed anchors.
>
>- Related to the former comment. What is the scope of the document? If
>it is about defining solutions, the document is far from achieving that
>(and it is classified as informational). If the idea is to explore this
>problem, then I think the scope should be clarified and I'd suggest to
>narrow it down (currently the document addresses too many things and
>make it hard to follow).
>
>- Why is the document referring to network slices? I see that awkward.
>The definition of slice is not yet very clear and in any case, is there
>anything in the document that is slice-specific? Unless it is the case,
>one could claim that most of the IETF protocols would apply to a
>"network or a network slice", but this is not explicitly stated.
>
>- The document make use of RFC2119 terminology, but I don't think this
>is fine. The document is informational (this alone does not prevent
>using RFC2119 terminology, but I don't see the need). Besides, one
>"SHOULD" appears in the introduction, which in general is not a
>normative section of a draft.
>
>- It would be better if the introduction does not use terms that are
>introduced/enumerated in the Conventions and Terminology section.
>
>- The text about "IP prefix/address anchoring" in Section 2 is not
>really a definition.
>
>- The text about "Location Management (LM) function" in Section 2 is
>not clear.
>
>- There is no definition/reference to the term "Mobility controller".
>
>- What is DMM specific of the "Security Management (SM) function"? To
>me, this is as in any mobility protocol, so I don't see why a document
>about distributed anchorning has to define a "new" function.
>
>- Weird writing: "The CPA may co-locate with DPA or may separate".
>
>- Typo? "for use by AN MN". I guess it should be "for use by an MN".
>
>- Figure 1 is not very easy to follow. I have to admit that I have been
>having difficulties with this type of figure since they started to be
>used.
>
>- When discussing the scenarios with network mobility, it is mentioned
>that "An IP prefix/address IPn1 anchored to the MR is assigned for use
>by the MNN in the mobile network." In my opinion, the prefix is
>delegated to the MR for use, but it is not anchored to the MR, as the
>MR may move and the address can only be topologically valid at one
>location.
>
>- In Section 3.2.2, there are different approaches mentioned to update
>forwarding tables (basically to allow a change of anchor). There have
>been many discussion in the past about this, with no consensus at all
>on the feasibility of using any of this slides (routing based) on
>scalable scenarios (its applicability seems to be limited to very
>specific scenarios). Moreover, there are important security and
>scalability implications on this type of solution, so I'd not include
>this in the draft. I think there is no Internet-wide scalable solution
>that enables switching an anchor in the middle of a session.
>
>- FM-state:1 introduces a lot of complexity, for a problem that it is
>already quite complex. Do we need to go into this?
>
>- FR-mr:2 reminds me a lot about Route Optimization for NEMO, which
>never took off at IETF mainly because of security issues and
>complexity. I think this would require quite a lot of work to be
>properly done in DMM.
>
>- The security considerations section does not really explain what are
>the issues and how to solve them. It just moves all the complexity to
>the so-called SM function.
>
>- With the fair disclaimer that I might not be objective here, I think
>the document misses quite a lot of existing works (even as active IETF
>drafts) proposing solutions for the distribution of mobility anchors.
>
>To sum-up, I think the draft is not yet ready for IETF LC.
>
>Thanks,
>
>Carlos
>
>On Thu, 2017-06-01 at 21:26 +0000, h chan wrote:
>> Carlos,
>> If you had already started to review version 3, I wonder if it might
>> work faster to send those comments first.
>> I think the differences between version 3 and version 5 are mostly
>> not in major technical issues.
>>=20
>> H. Anthony Chan
>>=20
>> -----Original Message-----
>> From: Carlos Jes=FAs Bernardos Cano [mailto:cjbc@it.uc3m.es]
>> Sent: Thursday, May 11, 2017 5:01 AM
>> To: h chan; Sri Gundavelli (sgundave); dmm
>> Cc: Marco Liebsch; Dapeng Liu; Seil Jeon; Suresh Krishnan; Byju
>> Pularikkal (byjupg)
>> Subject: Re: Distributed Mobility Anchoring - Draft Review Request
>>=20
>> Hi Anthony,
>>=20
>> My apologies for my delay handling this. I started to review version
>> 3 a while ago and then got stuck with another task. But I'll check
>> version 5 and provide my comments in the next few days.
>>=20
>> Thanks,
>>=20
>> Carlos
>>=20
>> On Wed, 2017-05-10 at 22:26 +0000, h chan wrote:
>> > Carlos,
>> >=20
>> > I have already uploaded version 5. Version 4 has the corrections
>> > from=20
>> > Dirk, and version 5 has many of the corrections from Byju and
>> > Pierrick.
>> >=20
>> > However if you had already started writing comments on the earlier
>> > version (3 or 4), please feel free to send any partial corrections
>> > and=20
>> > comments on the earlier version if it is more convenient to you.
>> > If the comment is on a particular page in an earlier version, I
>> > will=20
>> > figure out where it applies to the latest version.
>> >=20
>> > H. Anthony Chan
>> >=20
>> > -----Original Message-----
>> > From: Carlos Jes=FAs Bernardos Cano [mailto:cjbc@it.uc3m.es]
>> > Sent: Thursday, April 06, 2017 2:34 AM
>> > To: Sri Gundavelli (sgundave); dmm
>> > Cc: Marco Liebsch; Dapeng Liu; h chan; Seil Jeon; Suresh Krishnan;
>> > Byju Pularikkal (byjupg)
>> > Subject: Re: Distributed Mobility Anchoring - Draft Review Request
>> >=20
>> > Hi Sri,
>> >=20
>> > Sure, no prob, but I might need one additional week as next week
>> > I'm=20
>> > off on vacation. Hope that's fine.
>> >=20
>> > Thanks,
>> >=20
>> > Carlos
>> >=20
>> > On Wed, 2017-04-05 at 15:14 +0000, Sri Gundavelli (sgundave) wrote:
>> > > Hi Marco, Carlos, Seil & Biju,
>> > >=20
>> > > I believe you have all kindly agreed to review the below draft
>> > > and=20
>> > > post your feedback to the list.  Will be great if you can do that
>> > > in=20
>> > > the next 2 weeks (COB: 19th of April, 2017).
>> > >=20
>> > > We want to wrap up this work soon, but want to make sure the
>> > > draft=20
>> > > is technically correct.  Editorial issues can be fixed, but
>> > > minimally the draft should be technically correct and we want to
>> > > hear that from the group.
>> > >=20
>> > >  https://tools.ietf.org/html/draft-ietf-dmm-distributed-mobility-
>> > > an
>> > > ch
>> > > oring-03
>> > >=20
>> > > Any other experts, please review and post your feedback.
>> > >=20
>> > > Anthony =AD Please work with the reviewers.
>> > >=20
>> > >=20
>> > >=20
>> > >  =8B=8B=8B=8B=8B=8B-
>> > > =20
>> > > 10:00       Title: Distributed Mobility Anchoring
>> > >             Presenter: H Anthony Chan
>> > >             Time: 10 minutes
>> > >             Draft: https://tools.ietf.org/html/draft-ietf-dmm-dis
>> > > tr
>> > > ib
>> > > uted-mobility-anchoring-03
>> > > =20
>> > > =20
>> > > Anthony summarizes update.
>> > > Comment from Alex about nemo missed.
>> > > Different modes, move to new network and keep/give up old IP
>> > > address.
>> > > Rest of work for WG to review and comment.
>> > > =20
>> > > Sri: we need good reviews on this document. Editorial but also
>> > > technically.
>> > > =20
>> > > Volunteers: Reviews: Marco, Carlos, Seil
>> > > =20
>> > >=20
>> > > =8B=8B=8B=8B=8B=8B-


From nobody Wed Jun  7 09:49:23 2017
Return-Path: <h.anthony.chan@huawei.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 7FAD312948F for <dmm@ietfa.amsl.com>; Wed,  7 Jun 2017 09:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 LOe2NqzXV1II for <dmm@ietfa.amsl.com>; Wed,  7 Jun 2017 09:49:18 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1618C12947A for <dmm@ietf.org>; Wed,  7 Jun 2017 09:49:17 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DOP83006; Wed, 07 Jun 2017 16:49:14 +0000 (GMT)
Received: from DGGEMA406-HUB.china.huawei.com (10.3.20.47) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 7 Jun 2017 17:49:12 +0100
Received: from DGGEMA505-MBX.china.huawei.com ([169.254.1.179]) by DGGEMA406-HUB.china.huawei.com ([10.3.20.47]) with mapi id 14.03.0301.000; Thu, 8 Jun 2017 00:49:07 +0800
From: h chan <h.anthony.chan@huawei.com>
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, dmm <dmm@ietf.org>
Thread-Topic: Distributed Mobility Anchoring - Draft Review Request
Thread-Index: AQHSrh9WAf4H7G3dsUy5jyuSwK7YYqG3beAAgDbe6nCAAEu0gIAiRJFAgAVcGYCAAy0KAIAAmQgg
Date: Wed, 7 Jun 2017 16:49:07 +0000
Message-ID: <6E31144C030982429702B11D6746B98C770EA926@DGGEMA505-MBX.china.huawei.com>
References: <D50A57EA.266603%sgundave@cisco.com> <1491464022.4390.9.camel@it.uc3m.es> <6E31144C030982429702B11D6746B98C770D4F89@DGGEMA505-MBX.china.huawei.com> <1494496831.3363.34.camel@it.uc3m.es> <6E31144C030982429702B11D6746B98C770EA3F5@DGGEMA505-MBX.china.huawei.com> <1496675381.8422.66.camel@it.uc3m.es> <D55D5947.27D841%sgundave@cisco.com>
In-Reply-To: <D55D5947.27D841%sgundave@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.156.81]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.59382E8C.0070, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.1.179, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 0dfaa45876e0b7783a453e9d05202cbe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/8kNgC_03HQHwjb323gDO3slzXwE>
Subject: Re: [DMM] Distributed Mobility Anchoring - Draft Review Request
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 Jun 2017 16:49:21 -0000

Yes, we are working on these issues.

H. Anthony Chan

-----Original Message-----
From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Sri Gundavelli (sgunda=
ve)
Sent: Wednesday, June 07, 2017 10:40 AM
To: dmm
Subject: Re: [DMM] Distributed Mobility Anchoring - Draft Review Request

Hi Carlos,

Thanks for the detailed review. This is very good.

Anthony/Authors: Please address these comments/concerns. This is coming fro=
m a domain expert and we should make sure we resolve all the identified iss=
ues.


Regards
Sri


On 6/5/17, 8:09 AM, "Carlos Jes=FAs Bernardos Cano" <cjbc@it.uc3m.es> wrote=
:

>Hi Anthony, all,
>
>Again, apologies for my belated review. Please find below my comments.
>
>- Overall, I think the draft is hard to read/follow. Part of this comes=20
>from the fact of the extensive use of acronyms. But I think this is not=20
>the only reason. I think it is not clear if the document is specifying=20
>a solution or just presenting the scenarios and challenges derived from=20
>having multiple distributed anchors.
>
>- Related to the former comment. What is the scope of the document? If=20
>it is about defining solutions, the document is far from achieving that=20
>(and it is classified as informational). If the idea is to explore this=20
>problem, then I think the scope should be clarified and I'd suggest to=20
>narrow it down (currently the document addresses too many things and=20
>make it hard to follow).
>
>- Why is the document referring to network slices? I see that awkward.
>The definition of slice is not yet very clear and in any case, is there=20
>anything in the document that is slice-specific? Unless it is the case,=20
>one could claim that most of the IETF protocols would apply to a=20
>"network or a network slice", but this is not explicitly stated.
>
>- The document make use of RFC2119 terminology, but I don't think this=20
>is fine. The document is informational (this alone does not prevent=20
>using RFC2119 terminology, but I don't see the need). Besides, one=20
>"SHOULD" appears in the introduction, which in general is not a=20
>normative section of a draft.
>
>- It would be better if the introduction does not use terms that are=20
>introduced/enumerated in the Conventions and Terminology section.
>
>- The text about "IP prefix/address anchoring" in Section 2 is not=20
>really a definition.
>
>- The text about "Location Management (LM) function" in Section 2 is=20
>not clear.
>
>- There is no definition/reference to the term "Mobility controller".
>
>- What is DMM specific of the "Security Management (SM) function"? To=20
>me, this is as in any mobility protocol, so I don't see why a document=20
>about distributed anchorning has to define a "new" function.
>
>- Weird writing: "The CPA may co-locate with DPA or may separate".
>
>- Typo? "for use by AN MN". I guess it should be "for use by an MN".
>
>- Figure 1 is not very easy to follow. I have to admit that I have been=20
>having difficulties with this type of figure since they started to be=20
>used.
>
>- When discussing the scenarios with network mobility, it is mentioned=20
>that "An IP prefix/address IPn1 anchored to the MR is assigned for use=20
>by the MNN in the mobile network." In my opinion, the prefix is=20
>delegated to the MR for use, but it is not anchored to the MR, as the=20
>MR may move and the address can only be topologically valid at one=20
>location.
>
>- In Section 3.2.2, there are different approaches mentioned to update=20
>forwarding tables (basically to allow a change of anchor). There have=20
>been many discussion in the past about this, with no consensus at all=20
>on the feasibility of using any of this slides (routing based) on=20
>scalable scenarios (its applicability seems to be limited to very=20
>specific scenarios). Moreover, there are important security and=20
>scalability implications on this type of solution, so I'd not include=20
>this in the draft. I think there is no Internet-wide scalable solution=20
>that enables switching an anchor in the middle of a session.
>
>- FM-state:1 introduces a lot of complexity, for a problem that it is=20
>already quite complex. Do we need to go into this?
>
>- FR-mr:2 reminds me a lot about Route Optimization for NEMO, which=20
>never took off at IETF mainly because of security issues and=20
>complexity. I think this would require quite a lot of work to be=20
>properly done in DMM.
>
>- The security considerations section does not really explain what are=20
>the issues and how to solve them. It just moves all the complexity to=20
>the so-called SM function.
>
>- With the fair disclaimer that I might not be objective here, I think=20
>the document misses quite a lot of existing works (even as active IETF
>drafts) proposing solutions for the distribution of mobility anchors.
>
>To sum-up, I think the draft is not yet ready for IETF LC.
>
>Thanks,
>
>Carlos
>
>On Thu, 2017-06-01 at 21:26 +0000, h chan wrote:
>> Carlos,
>> If you had already started to review version 3, I wonder if it might=20
>> work faster to send those comments first.
>> I think the differences between version 3 and version 5 are mostly=20
>> not in major technical issues.
>>=20
>> H. Anthony Chan
>>=20
>> -----Original Message-----
>> From: Carlos Jes=FAs Bernardos Cano [mailto:cjbc@it.uc3m.es]
>> Sent: Thursday, May 11, 2017 5:01 AM
>> To: h chan; Sri Gundavelli (sgundave); dmm
>> Cc: Marco Liebsch; Dapeng Liu; Seil Jeon; Suresh Krishnan; Byju=20
>> Pularikkal (byjupg)
>> Subject: Re: Distributed Mobility Anchoring - Draft Review Request
>>=20
>> Hi Anthony,
>>=20
>> My apologies for my delay handling this. I started to review version
>> 3 a while ago and then got stuck with another task. But I'll check=20
>> version 5 and provide my comments in the next few days.
>>=20
>> Thanks,
>>=20
>> Carlos
>>=20
>> On Wed, 2017-05-10 at 22:26 +0000, h chan wrote:
>> > Carlos,
>> >=20
>> > I have already uploaded version 5. Version 4 has the corrections=20
>> > from Dirk, and version 5 has many of the corrections from Byju and=20
>> > Pierrick.
>> >=20
>> > However if you had already started writing comments on the earlier=20
>> > version (3 or 4), please feel free to send any partial corrections=20
>> > and comments on the earlier version if it is more convenient to=20
>> > you.
>> > If the comment is on a particular page in an earlier version, I=20
>> > will figure out where it applies to the latest version.
>> >=20
>> > H. Anthony Chan
>> >=20
>> > -----Original Message-----
>> > From: Carlos Jes=FAs Bernardos Cano [mailto:cjbc@it.uc3m.es]
>> > Sent: Thursday, April 06, 2017 2:34 AM
>> > To: Sri Gundavelli (sgundave); dmm
>> > Cc: Marco Liebsch; Dapeng Liu; h chan; Seil Jeon; Suresh Krishnan;=20
>> > Byju Pularikkal (byjupg)
>> > Subject: Re: Distributed Mobility Anchoring - Draft Review Request
>> >=20
>> > Hi Sri,
>> >=20
>> > Sure, no prob, but I might need one additional week as next week=20
>> > I'm off on vacation. Hope that's fine.
>> >=20
>> > Thanks,
>> >=20
>> > Carlos
>> >=20
>> > On Wed, 2017-04-05 at 15:14 +0000, Sri Gundavelli (sgundave) wrote:
>> > > Hi Marco, Carlos, Seil & Biju,
>> > >=20
>> > > I believe you have all kindly agreed to review the below draft=20
>> > > and post your feedback to the list.  Will be great if you can do=20
>> > > that in the next 2 weeks (COB: 19th of April, 2017).
>> > >=20
>> > > We want to wrap up this work soon, but want to make sure the=20
>> > > draft is technically correct.  Editorial issues can be fixed, but=20
>> > > minimally the draft should be technically correct and we want to=20
>> > > hear that from the group.
>> > >=20
>> > >  https://tools.ietf.org/html/draft-ietf-dmm-distributed-mobility-
>> > > an
>> > > ch
>> > > oring-03
>> > >=20
>> > > Any other experts, please review and post your feedback.
>> > >=20
>> > > Anthony =AD Please work with the reviewers.
>> > >=20
>> > >=20
>> > >=20
>> > >  <<<<<<-
>> > > =20
>> > > 10:00       Title: Distributed Mobility Anchoring
>> > >             Presenter: H Anthony Chan
>> > >             Time: 10 minutes
>> > >             Draft: https://tools.ietf.org/html/draft-ietf-dmm-dis
>> > > tr
>> > > ib
>> > > uted-mobility-anchoring-03
>> > > =20
>> > > =20
>> > > Anthony summarizes update.
>> > > Comment from Alex about nemo missed.
>> > > Different modes, move to new network and keep/give up old IP=20
>> > > address.
>> > > Rest of work for WG to review and comment.
>> > > =20
>> > > Sri: we need good reviews on this document. Editorial but also=20
>> > > technically.
>> > > =20
>> > > Volunteers: Reviews: Marco, Carlos, Seil
>> > > =20
>> > >=20
>> > > <<<<<<-

_______________________________________________
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm


From nobody Wed Jun 14 12:26:22 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: dmm@ietf.org
Delivered-To: dmm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2660312943D; Wed, 14 Jun 2017 12:26:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Cc: ietf@ietf.org, dmm@ietf.org, draft-ietf-dmm-mag-multihoming.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.54.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149746836602.14035.16572809666065484300@ietfa.amsl.com>
Date: Wed, 14 Jun 2017 12:26:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/4S_roTlwyTbh0QDLolTzg8kJJS8>
Subject: [DMM] Genart last call review of draft-ietf-dmm-mag-multihoming-03
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.22
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, 14 Jun 2017 19:26:06 -0000

Reviewer: Robert Sparks
Review result: Not Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-dmm-mag-multihoming-03
Reviewer: Robert Sparks
Review Date: 2017-06-14
IETF LC End Date: 2017-06-16
IESG Telechat date: Not scheduled for a telechat

Summary: Not Ready

This document has several issues that need to be addressed before publication
as a proposed standard.

1) The document defines some wire syntax, but does not define (or refine) the
protocol for using these bits of wire syntax. For instance, the document does
not discuss if/when the MAG Identifier Option is necessary. It does not
discuss when the new error code it defines should be sent, nor what a recipient
should do if it receives that error code (I would have expected discussion
similar to some of the paragraphs in sections 5.4.1.2 and 6.9.1.2 of RFC5213).

2) There are sentence fragments that indicate information was lost at some
point in editing. 

    - "In the continuation of c, a Proxy" : what should have been where the 'c'
      is?

    - "or at When operating" : This looks a clause (and the end of a sentence)
      was lost after 'or at'. 'When operating' is clearly starting a new
      sentence.


Nits: 

* How are Preference Settings either a goal or a benefit? It seems out of 
  place in the list.
  
* at "leverage on latest" do you mean "leverage the latest"?
  
* at "allowing to make appropriate traffic steering decision", _what_ are you
  allowing to make a decision (who is the actor)?
  
* 'For example, the operator may have policy which binds traffic for 
   Application "X" needs to interface with Label "Y".' does not make sense. 
   Is the word "needs" extraneous?
  
* The last sentence in the definition of the Binding-Identifier appears to be
  describing the Interface Label.
  
* Something is missing at "and either based on" in the security considerations
  section.
  
* Consider using RFC8174 instead of RFC2119



From nobody Fri Jun 23 17:13:41 2017
Return-Path: <agenda@ietf.org>
X-Original-To: dmm@ietf.org
Delivered-To: dmm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4148A12EB32; Fri, 23 Jun 2017 17:07:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <dmm-chairs@ietf.org>, <sgundave@cisco.com>
Cc: suresh.krishnan@gmail.com, dmm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149826283126.7840.10419644639960050498.idtracker@ietfa.amsl.com>
Date: Fri, 23 Jun 2017 17:07:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/1lTK5XjNn-s03zdsng6kUhGaY3o>
Subject: [DMM] dmm - Requested session has been scheduled for IETF 99
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 24 Jun 2017 00:07:11 -0000

Dear Sri Gundavelli,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 

dmm Session 1 (2:30:00)
    Wednesday, Morning Session I 0930-1200
    Room Name: Berlin/Brussels size: 100
    ---------------------------------------------
    


Request Information:


---------------------------------------------------------
Working Group Name: Distributed Mobility Management
Area Name: Internet Area
Session Requester: Sri Gundavelli

Number of Sessions: 1
Length of Session(s):  2.5 Hours
Number of Attendees: 40
Conflicts to Avoid: 





People who must be present:
  Sri Gundavelli
  Suresh Krishnan
  Dapeng Liu

Resources Requested:

Special Requests:
  
---------------------------------------------------------


From nobody Sun Jun 25 05:18:08 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dmm@ietf.org
Delivered-To: dmm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 106911200ED; Sun, 25 Jun 2017 05:18:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dmm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149839308701.3137.13762142195405956278@ietfa.amsl.com>
Date: Sun, 25 Jun 2017 05:18:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/rPGzfLhJs7s_47JQZPwUsdKdxH4>
Subject: [DMM] I-D Action: draft-ietf-dmm-ondemand-mobility-11.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 25 Jun 2017 12:18:07 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Mobility Management of the IETF.

        Title           : On Demand Mobility Management
        Authors         : Alper Yegin
                          Danny Moses
                          Kisuk Kweon
                          Jinsung Lee
                          Jungshin Park
                          Seil Jeon
	Filename        : draft-ietf-dmm-ondemand-mobility-11.txt
	Pages           : 15
	Date            : 2017-06-25

Abstract:
   Applications differ with respect to whether they need IP session
   continuity and/or IP address reachability.  The network providing the
   same type of service to any mobile host and any application running
   on the host yields inefficiencies.  This document describes a
   solution for taking the application needs into account by selectively
   providing IP session continuity and IP address reachability on a per-
   socket basis.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-ondemand-mobility/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dmm-ondemand-mobility-11
https://datatracker.ietf.org/doc/html/draft-ietf-dmm-ondemand-mobility-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-ondemand-mobility-11


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/


From nobody Mon Jun 26 22:54:05 2017
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 702B312EB69 for <dmm@ietfa.amsl.com>; Mon, 26 Jun 2017 22:54:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 bZSUIHC604PA for <dmm@ietfa.amsl.com>; Mon, 26 Jun 2017 22:54:02 -0700 (PDT)
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 CE9DB124BFA for <dmm@ietf.org>; Mon, 26 Jun 2017 22:54:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4159; q=dns/txt; s=iport; t=1498542842; x=1499752442; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Ylf3ys6rutG7yTrInL3FJUEKfeXvrQyPQMdFBA3SrDg=; b=G27VJ0OEcZNPN/h7ewk4QGoM7O7eI2O81N53hByzXHMzkqFCT/yIptUo +v4DkqVg4VfZ8kwfsaYPgXL/I9v91nbLG0Mz9aCfrrOMSaiVXp1JvRwda 0yUSTcDCDKwk3z+cMgMCS5x3uOIYH7vK3i6k9vUML8kxGI0CkbDeVDIvc I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AuAQA68lFZ/4kNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgm9pgW8HjX6iM4UrghGGJAKCbj8YAQIBAQEBAQEBayiFGQZ5EAIBCAQ?= =?us-ascii?q?7BzIUEQIEDgWJTGSyD4tcAQEBAQEBAQECAQEBAQEBAQEBAQEdgyeDTIUFil4Fi?= =?us-ascii?q?VSGcYZch04Ck2iCCoVJikGVIwEfOIEKdBUfhz12iA+BDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.39,399,1493683200";  d="scan'208,217";a="446300366"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 27 Jun 2017 05:54:00 +0000
Received: from XCH-RCD-010.cisco.com (xch-rcd-010.cisco.com [173.37.102.20]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v5R5s09a013922 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 27 Jun 2017 05:54:00 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 27 Jun 2017 00:54:00 -0500
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.1210.000; Tue, 27 Jun 2017 00:53:59 -0500
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: dmm <dmm@ietf.org>
Thread-Topic: DMM IETF 98 meeting
Thread-Index: AQHS7wnFckB06tExWkOIWWdz94Y4Hw==
Date: Tue, 27 Jun 2017 05:53:59 +0000
Message-ID: <D5773EBE.27FF9E%sgundave@cisco.com>
References: <CAKcc6AeTqRenJke5UAAZYzSRTPaix4Bj+3p++jcjbjXzok3yKQ@mail.gmail.com> <D4C9C826.259E46%sgundave@cisco.com>
In-Reply-To: <D4C9C826.259E46%sgundave@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.188.59]
Content-Type: multipart/alternative; boundary="_000_D5773EBE27FF9Esgundaveciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/PBTooO47XiKzcSdxB-M0SW_b8h4>
Subject: Re: [DMM] DMM IETF 98 meeting
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: Tue, 27 Jun 2017 05:54:04 -0000

--_000_D5773EBE27FF9Esgundaveciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks:

We have scheduled the DMM working group meeting at IETF 99, to be held in P=
rague, Czech Republic.

We will be meeting on Wed, July 19th at 9.30AM.

If you like to make any presentations,  please send your requests to Dapeng=
 or myself, by 7th of July with the following details.


Title:
Description:
Time:
Presenters:
Draft Reference (If exists):



Regards
Sri



On 6/23/17, 5:07 PM, ""IETF Secretariat"" <agenda@ietf.org<mailto:agenda@ie=
tf.org>> wrote:

Dear Sri Gundavelli,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request.

dmm Session 1 (2:30:00)
    Wednesday, Morning Session I 0930-1200
    Room Name: Berlin/Brussels size: 100
    ---------------------------------------------



--_000_D5773EBE27FF9Esgundaveciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <6862D246F14FAD42BE70B26E78A90236@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Folks:</div>
<div><br>
</div>
<div>We have scheduled the DMM working group meeting at IETF 99, to be held=
 in Prague, Czech Republic. &nbsp;</div>
<div><br>
</div>
<div>We will be meeting on Wed, July 19th at 9.30AM.&nbsp;</div>
<div><br>
</div>
<div>If you like to make any presentations, &nbsp;please send your requests=
 to Dapeng or myself, by 7th of July with the following details.</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif;">
<div><br>
</div>
<div>Title:</div>
<div>Description:</div>
<div>Time:&nbsp;</div>
<div>Presenters:</div>
<div>Draft Reference (If exists):</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Regards</div>
<div>Sri</div>
</div>
</span>
<div><br>
</div>
<div><br>
</div>
<div>
<div><br>
</div>
<div>On 6/23/17, 5:07 PM, &quot;&quot;IETF Secretariat&quot;&quot; &lt;<a h=
ref=3D"mailto:agenda@ietf.org">agenda@ietf.org</a>&gt; wrote:</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"border-left-=
color: rgb(181, 196, 223); border-left-width: 5px; border-left-style: solid=
; padding: 0px 0px 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">Dear Sri =
Gundavelli,</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">The sessi=
on(s) that you have requested have been scheduled.</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">Below is =
the scheduled session information followed by</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">the origi=
nal request.&nbsp;</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">dmm Sessi=
on 1 (2:30:00)</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp;&nbsp;&nbsp;Wednesday, Morning Session I 0930-1200</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp;&nbsp;&nbsp;Room Name: Berlin/Brussels size: 100</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp;&nbsp;&nbsp;---------------------------------------------</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp;&nbsp;&nbsp;</div>
<div><br>
</div>
</blockquote>
</div>
</body>
</html>

--_000_D5773EBE27FF9Esgundaveciscocom_--


From nobody Thu Jun 29 07:54:16 2017
Return-Path: <pierrick.seite@orange.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 4BA4A131459; Thu, 29 Jun 2017 07:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.399
X-Spam-Level: 
X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 WlkrollBfksC; Thu, 29 Jun 2017 07:54:00 -0700 (PDT)
Received: from relais-inet.orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B779129AB8; Thu, 29 Jun 2017 07:54:00 -0700 (PDT)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id E21B116048B; Thu, 29 Jun 2017 16:53:58 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.59]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id BEA226006C; Thu, 29 Jun 2017 16:53:58 +0200 (CEST)
Received: from OPEXCLILM22.corporate.adroot.infra.ftgroup ([fe80::8c90:f4e9:be28:2a1]) by OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c%19]) with mapi id 14.03.0352.000; Thu, 29 Jun 2017 16:53:58 +0200
From: <pierrick.seite@orange.com>
To: Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>, "draft-ietf-dmm-mag-multihoming.all@ietf.org" <draft-ietf-dmm-mag-multihoming.all@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-dmm-mag-multihoming-03
Thread-Index: AQHS5UQUB4/g2YtYp0GhFtYMb97BHKI8AQUw
Date: Thu, 29 Jun 2017 14:53:57 +0000
Message-ID: <9066_1498748038_59551486_9066_325_1_81C77F07008CA24F9783A98CFD706F713AA75926@OPEXCLILM22.corporate.adroot.infra.ftgroup>
References: <149746836602.14035.16572809666065484300@ietfa.amsl.com>
In-Reply-To: <149746836602.14035.16572809666065484300@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/gw9ZS_Wg0dweWQlYP5iiBB9FRW8>
Subject: Re: [DMM] Genart last call review of draft-ietf-dmm-mag-multihoming-03
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: Thu, 29 Jun 2017 14:54:03 -0000

SGVsbG8sDQoNClRoYW5rcyBmb3IgdGhlIHJldmlldzsgcGxlYXNlIGZpbmQgYmVsb3cgY2xhcmlm
aWNhdGlvbnMgYW5kIGFuc3dlcnMuIFdlIHdpbGwgdXBkYXRlIHRoZSBkb2N1bWVudCBhY2NvcmRp
bmdseS4NCg0KUmVnYXJkcywNCg0KPiAtLS0tLU1lc3NhZ2UgZCdvcmlnaW5lLS0tLS0NCj4gRGUg
OiBSb2JlcnQgU3BhcmtzIFttYWlsdG86cmpzcGFya3NAbm9zdHJ1bS5jb21dDQo+IEVudm95w6kg
OiBtZXJjcmVkaSAxNCBqdWluIDIwMTcgMjE6MjYNCj4gw4AgOiBnZW4tYXJ0QGlldGYub3JnDQo+
IENjIDogaWV0ZkBpZXRmLm9yZzsgZG1tQGlldGYub3JnOyBkcmFmdC1pZXRmLWRtbS1tYWctbXVs
dGlob21pbmcuYWxsQGlldGYub3JnDQo+IE9iamV0IDogR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcg
b2YgZHJhZnQtaWV0Zi1kbW0tbWFnLW11bHRpaG9taW5nLTAzDQo+DQo+IFJldmlld2VyOiBSb2Jl
cnQgU3BhcmtzDQo+IFJldmlldyByZXN1bHQ6IE5vdCBSZWFkeQ0KPg0KPiBJIGFtIHRoZSBhc3Np
Z25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhIFJl
dmlldyBUZWFtDQo+IChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBw
cm9jZXNzZWQgYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGDQo+IENoYWlyLiAgUGxlYXNlIHRyZWF0
IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLg0K
Pg0KPiBGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQo+DQo+IDxo
dHRwczovL3RyYWMuaWV0Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KPg0KPiBEb2N1
bWVudDogZHJhZnQtaWV0Zi1kbW0tbWFnLW11bHRpaG9taW5nLTAzDQo+IFJldmlld2VyOiBSb2Jl
cnQgU3BhcmtzDQo+IFJldmlldyBEYXRlOiAyMDE3LTA2LTE0DQo+IElFVEYgTEMgRW5kIERhdGU6
IDIwMTctMDYtMTYNCj4gSUVTRyBUZWxlY2hhdCBkYXRlOiBOb3Qgc2NoZWR1bGVkIGZvciBhIHRl
bGVjaGF0DQo+DQo+IFN1bW1hcnk6IE5vdCBSZWFkeQ0KPg0KPiBUaGlzIGRvY3VtZW50IGhhcyBz
ZXZlcmFsIGlzc3VlcyB0aGF0IG5lZWQgdG8gYmUgYWRkcmVzc2VkIGJlZm9yZSBwdWJsaWNhdGlv
biBhcw0KPiBhIHByb3Bvc2VkIHN0YW5kYXJkLg0KPg0KPiAxKSBUaGUgZG9jdW1lbnQgZGVmaW5l
cyBzb21lIHdpcmUgc3ludGF4LCBidXQgZG9lcyBub3QgZGVmaW5lIChvciByZWZpbmUpIHRoZQ0K
PiBwcm90b2NvbCBmb3IgdXNpbmcgdGhlc2UgYml0cyBvZiB3aXJlIHN5bnRheC4gRm9yIGluc3Rh
bmNlLCB0aGUgZG9jdW1lbnQgZG9lcyBub3QNCj4gZGlzY3VzcyBpZi93aGVuIHRoZSBNQUcgSWRl
bnRpZmllciBPcHRpb24gaXMgbmVjZXNzYXJ5LiBJdCBkb2VzIG5vdCBkaXNjdXNzIHdoZW4NCj4g
dGhlIG5ldyBlcnJvciBjb2RlIGl0IGRlZmluZXMgc2hvdWxkIGJlIHNlbnQsIG5vciB3aGF0IGEg
cmVjaXBpZW50IHNob3VsZCBkbyBpZiBpdA0KPiByZWNlaXZlcyB0aGF0IGVycm9yIGNvZGUgKEkg
d291bGQgaGF2ZSBleHBlY3RlZCBkaXNjdXNzaW9uIHNpbWlsYXIgdG8gc29tZSBvZiB0aGUNCj4g
cGFyYWdyYXBocyBpbiBzZWN0aW9ucyA1LjQuMS4yIGFuZCA2LjkuMS4yIG9mIFJGQzUyMTMpLg0K
Pg0KDQo+IEZvciBpbnN0YW5jZSwgdGhlIGRvY3VtZW50IGRvZXMgbm90IGRpc2N1c3MgaWYvd2hl
biB0aGUgTUFHIElkZW50aWZpZXIgT3B0aW9uIGlzIG5lY2Vzc2FyeS4NCg0KVGhlIGZvbGxvd2lu
ZyB0ZXh0IGNvdmVycyB0aGF0IGFzcGVjdDoNCg0KIlRoZSBNQUcgTXVsdGlwYXRoLUJpbmRpbmcg
b3B0aW9uIGlzIGEgbmV3IG1vYmlsaXR5IGhlYWRlciBvcHRpb24NCmRlZmluZWQgZm9yIHVzZSB3
aXRoIFByb3h5IEJpbmRpbmcgVXBkYXRlIGFuZCBQcm94eSBCaW5kaW5nDQpBY2tub3dsZWRnZW1l
bnQgbWVzc2FnZXMgZXhjaGFuZ2VkIGJldHdlZW4gdGhlIGxvY2FsIG1vYmlsaXR5IGFuY2hvcg0K
YW5kIHRoZSBtb2JpbGUgYWNjZXNzIGdhdGV3YXkuDQoNClRoaXMgbW9iaWxpdHkgaGVhZGVyIG9w
dGlvbiBpcyB1c2VkIGZvciByZXF1ZXN0aW5nIG11bHRpcGF0aCBzdXBwb3J0Lg0KSXQgaW5kaWNh
dGVzIHRoYXQgdGhlIG1vYmlsZSBhY2Nlc3MgZ2F0ZXdheSBpcyByZXF1ZXN0aW5nIHRoZSBsb2Nh
bA0KbW9iaWxpdHkgYW5jaG9yIHRvIHJlZ2lzdGVyIHRoZSBjdXJyZW50IGNhcmUtb2YgYWRkcmVz
cyBhc3NvY2lhdGVkDQp3aXRoIHRoZSByZXF1ZXN0IGFzIG9uZSBvZiB0aGUgbWFueSBjYXJlLWFk
ZHJlc3NlcyB0aHJvdWdoIHdoaWNoIHRoZQ0KbW9iaWxlIGFjY2VzcyBnYXRld2F5IGNhbiBiZSBy
ZWFjaGVkLiAgSXQgaXMgYWxzbyBmb3IgY2FycnlpbmcgdGhlDQppbmZvcm1hdGlvbiByZWxhdGVk
IHRvIHRoZSBhY2Nlc3MgbmV0d29yayBhc3NvY2lhdGVkIHdpdGggdGhlIGNhcmUtb2YNClRoZSBN
QUcgTXVsdGlwYXRoLUJpbmRpbmcgb3B0aW9uIGhhcyBhbiBhbGlnbm1lbnQgcmVxdWlyZW1lbnQg
b2YNCiA4bisyLiAgSXRzIGZvcm1hdCBpcyBhcyBzaG93biBpbiBGaWd1cmUgMzrigJ0NCg0KPiAg
SXQgZG9lcyBub3QgZGlzY3VzcyB3aGVuIHRoZSBuZXcgZXJyb3IgY29kZSBpdCBkZWZpbmVzIHNo
b3VsZCBiZSBzZW50LCBub3Igd2hhdCBhIHJlY2lwaWVudCBzaG91bGQgZG8gaWYgaXQgcmVjZWl2
ZXMgdGhhdCBlcnJvciBjb2RlIChJIHdvdWxkIGhhdmUgZXhwZWN0ZWQgZGlzY3Vzc2lvbiBzaW1p
bGFyIHRvIHNvbWUgb2YgdGhlIHBhcmFncmFwaHMgaW4gc2VjdGlvbnMgNS40LjEuMiBhbmQgNi45
LjEuMiBvZiBSRkM1MjEzKS4NCg0KUmVhc29ucyBmb3IgdGhlIExNQSB0byBzZW5kIGVycm9yIGNv
ZGUgYXJlIGFzIGZvbGxvd3MNCg0KLSBUaGUgTE1BIGRvZXMgbm90IHN1cHBvcnQgbXVsdGlwbGUg
Y2FyZS1vZi1hZGRyZXNzIHJlZ2lzdHJhdGlvbg0KLSBhIGJpbmRpbmcgZW50cnkgd2l0aCB0aGUg
cmVxdWVzdGVkIENhcmUtb2YtYWRkcmVzcyBhbHJlYWR5IGV4aXN0DQoNCldlIHdpbGwgY2xhcmlm
eSB0aGlzIHBvaW50IGFuZCBleHBlY3RpbmcgTUFHIGJlaGF2aW9yIGFzIHdlbGwuDQoNCg0KDQo+
IDIpIFRoZXJlIGFyZSBzZW50ZW5jZSBmcmFnbWVudHMgdGhhdCBpbmRpY2F0ZSBpbmZvcm1hdGlv
biB3YXMgbG9zdCBhdCBzb21lIHBvaW50IGluDQo+IGVkaXRpbmcuDQo+DQo+ICAgICAtICJJbiB0
aGUgY29udGludWF0aW9uIG9mIGMsIGEgUHJveHkiIDogd2hhdCBzaG91bGQgaGF2ZSBiZWVuIHdo
ZXJlIHRoZSAnYycNCj4gICAgICAgaXM/DQo+DQo+ICAgICAtICJvciBhdCBXaGVuIG9wZXJhdGlu
ZyIgOiBUaGlzIGxvb2tzIGEgY2xhdXNlIChhbmQgdGhlIGVuZCBvZiBhIHNlbnRlbmNlKQ0KPiAg
ICAgICB3YXMgbG9zdCBhZnRlciAnb3IgYXQnLiAnV2hlbiBvcGVyYXRpbmcnIGlzIGNsZWFybHkg
c3RhcnRpbmcgYSBuZXcNCj4gICAgICAgc2VudGVuY2UuDQo+DQo+DQoNCkZyb20gdmVyc2lvbjE6
DQoNCiAgIEluIHRoZSBjb250aW51YXRpb24gb2YgW1JGQzQ5MDhdLCBhIFByb3h5IE1vYmlsZSBJ
UHY2IFtSRkM1MjEzXSBiYXNlZCBtdWx0aSBob21lZCBhY2hpdGVjdHVyZSBjb3VsZCBiZSBkZWZp
bmVkLg0KDQoNCldlIGNhbiBkZWxldGUgdGhpcyBzZW50ZW5jZSBhcyB0aGUgbmV4dCBzZW50ZW5j
ZSBjb3ZlcnMgdGhpcyBwb2ludC4NCg0KPiBOaXRzOg0KPg0KPiAqIEhvdyBhcmUgUHJlZmVyZW5j
ZSBTZXR0aW5ncyBlaXRoZXIgYSBnb2FsIG9yIGEgYmVuZWZpdD8gSXQgc2VlbXMgb3V0IG9mDQo+
ICAgcGxhY2UgaW4gdGhlIGxpc3QuDQo+DQoNCk9uZSBtYXkgcHJlZmVyIG9uZSBhY2Nlc3MgbmV0
d29yayBvdmVyIG90aGVyLiBFeGFtcGxlOiBVc2UgV2ktRmkgd2hlbiBpdHMgYXZhaWxhYmxlIGFu
ZCBkbyBub3QgdXNlIExURS4gT25lIGNhbiBleHRlbmQgdGhpcyBmdXJ0aGVyIGFuZCBwcm92aWRl
IHByZWZlcmVuY2Ugc2V0dGluZ3MgdGhhdCBhbGxvdyBWb2ljZSB0cmFmZmljIHRvIGdvIG9ubHkg
b3ZlciBMVEUuDQoNCj4gKiBhdCAibGV2ZXJhZ2Ugb24gbGF0ZXN0IiBkbyB5b3UgbWVhbiAibGV2
ZXJhZ2UgdGhlIGxhdGVzdCI/DQo+DQoNCk9MRDoNClRoZSBtb3RpdmF0aW9uIHRvIHVwZGF0ZSBb
UkZDNDkwOF0gIHdpdGggcHJveHkgTW9iaWxlIElQdjYgaXMgdG8gbGV2ZXJhZ2Ugb24gbGF0ZXN0
IG1vYmlsaXR5IHdvcmtpbmcgZ3JvdXAgYWNoaWV2ZW1lbnRzLCBuYW1lbHk6DQoNCk5FVzoNClRo
ZSBtb3RpdmF0aW9uIGZvciB0aGlzIHdvcmsgaXMgdG8gZXh0ZW5kIFByb3h5IE1vYmlsZSBJUHY2
IHByb3RvY29sIHdpdGggbXVsdGlob21pbmcgZXh0ZW5zaW9ucyBbUkZDNDkwOF0gYW5kIHJlYWxp
emUgdGhlIGZvbGxvd2luZyBjYXBhYmlsaXRpZXM6DQoNCg0KPiAqIGF0ICJhbGxvd2luZyB0byBt
YWtlIGFwcHJvcHJpYXRlIHRyYWZmaWMgc3RlZXJpbmcgZGVjaXNpb24iLCBfd2hhdF8gYXJlIHlv
dQ0KPiAgIGFsbG93aW5nIHRvIG1ha2UgYSBkZWNpc2lvbiAod2hvIGlzIHRoZSBhY3Rvcik/DQo+
DQo+ICogJ0ZvciBleGFtcGxlLCB0aGUgb3BlcmF0b3IgbWF5IGhhdmUgcG9saWN5IHdoaWNoIGJp
bmRzIHRyYWZmaWMgZm9yDQo+ICAgIEFwcGxpY2F0aW9uICJYIiBuZWVkcyB0byBpbnRlcmZhY2Ug
d2l0aCBMYWJlbCAiWSIuJyBkb2VzIG5vdCBtYWtlIHNlbnNlLg0KPiAgICBJcyB0aGUgd29yZCAi
bmVlZHMiIGV4dHJhbmVvdXM/DQo+DQo+ICogVGhlIGxhc3Qgc2VudGVuY2UgaW4gdGhlIGRlZmlu
aXRpb24gb2YgdGhlIEJpbmRpbmctSWRlbnRpZmllciBhcHBlYXJzIHRvIGJlDQo+ICAgZGVzY3Jp
YmluZyB0aGUgSW50ZXJmYWNlIExhYmVsLg0KPg0KDQpJbnRlcmZhY2UgbGFiZWwgaXMgYSBkZXNj
cmlwdGl2ZSBzdHJpbmcuIEJpbmRpbmcgaWRlbnRpZmllciBpcyBhbiBpZGVudGlmaWVyIGZvciB0
aGUgYmluZGluZy4gRWFjaCBCaW5kaW5nICBpcyB0aWVkIHRvIGFuIGludGVyZmFjZSBvbiB0aGUg
TUFHLg0KDQogICAgICBUaGlzIDgtYml0IGZpZWxkIGlzIHVzZWQgZm9yIGNhcnJ5aW5nIHRoZSBi
aW5kaW5nIGlkZW50aWZpZXIuICBJdA0KICAgICAgdW5pcXVlbHkgaWRlbnRpZmllcyBhIHNwZWNp
ZmljIGJpbmRpbmcgb2YgdGhlIG1vYmlsZSBub2RlLCB0bw0KICAgICAgd2hpY2ggdGhpcyByZXF1
ZXN0IGNhbiBiZSBhc3NvY2lhdGVkLiAgRWFjaCBiaW5kaW5nIGlkZW50aWZpZXIgaXMNCiAgICAg
IHJlcHJlc2VudGVkIGFzIGFuIHVuc2lnbmVkIGludGVnZXIuICBUaGUgcGVybWl0dGVkIHZhbHVl
cyBhcmUgMQ0KICAgICAgdGhyb3VnaCAyNTQuICBUaGUgQklEIHZhbHVlIG9mIDAgYW5kIDI1NSBh
cmUgcmVzZXJ2ZWQuICBUaGUgbW9iaWxlDQogICAgICBhY2Nlc3MgZ2F0ZXdheSBhc3NpZ25zIGEg
dW5pcXVlIHZhbHVlIGZvciBlYWNoIG9mIGl0cyBpbnRlcmZhY2VzDQogICAgICBhbmQgaW5jbHVk
ZXMgdGhlbSBpbiB0aGUgbWVzc2FnZS4NCg0KPiAqIFNvbWV0aGluZyBpcyBtaXNzaW5nIGF0ICJh
bmQgZWl0aGVyIGJhc2VkIG9uIiBpbiB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMNCj4gICBz
ZWN0aW9uLg0KPg0KT0xEOg0KICAgVGhpcyBlc3NlbnRpYWxseSBhbGxvd3MgdGhlIG1vYmlsZSBu
b2RlJ3MgSVAgdHJhZmZpYyB0byBiZQ0KICAgcm91dGVkIHRocm91Z2ggYW55IG9mIHRoZSB0dW5u
ZWwgcGF0aHMgYW5kIGVpdGhlciBiYXNlZCBvbiBhIHN0YXRpYw0KICAgb3IgYSBkeW5hbWljYWxs
eSBuZWdvdGlhdGVkIGZsb3cgcG9saWN5Lg0KDQpORVc6DQoNCiAgIFRoaXMgZXNzZW50aWFsbHkg
YWxsb3dzIHRoZSBtb2JpbGUgbm9kZSdzIElQIHRyYWZmaWMgdG8gYmUNCiAgIHJvdXRlZCB0aHJv
dWdoIGFueSBvZiB0aGUgdHVubmVsIHBhdGhzLCBiYXNlZCBvbiBhIHN0YXRpYw0KICAgb3IgYSBk
eW5hbWljYWxseSBuZWdvdGlhdGVkIGZsb3cgcG9saWN5Lg0KDQo+ICogQ29uc2lkZXIgdXNpbmcg
UkZDODE3NCBpbnN0ZWFkIG9mIFJGQzIxMTkNCj4NCg0KT0sNCg0KCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KCkNlIG1lc3Nh
Z2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQgY29udGVuaXIgZGVzIGluZm9ybWF0aW9u
cyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5lIGRvaXZlbnQgZG9uYwpwYXMg
ZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGllcyBzYW5zIGF1dG9yaXNhdGlvbi4gU2kg
dm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJyZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxl
cgphIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBqb2lu
dGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBldGFudCBzdXNjZXB0aWJsZXMgZCdhbHRl
cmF0aW9uLApPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNwb25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdl
IGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZpZS4gTWVyY2kuCgpUaGlzIG1lc3NhZ2Ug
YW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgb3IgcHJpdmlsZWdl
ZCBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0ZWQgYnkgbGF3Owp0aGV5IHNob3VsZCBu
b3QgYmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVkIHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4K
SWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0
aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMuCkFz
IGVtYWlscyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlzIG5vdCBsaWFibGUgZm9yIG1lc3NhZ2Vz
IHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2VkIG9yIGZhbHNpZmllZC4KVGhhbmsgeW91
LgoK


From nobody Fri Jun 30 09:42:11 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dmm@ietf.org
Delivered-To: dmm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 72397126C25; Fri, 30 Jun 2017 09:42:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dmm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149884092943.4666.7020214744393949027@ietfa.amsl.com>
Date: Fri, 30 Jun 2017 09:42:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/tPiMb1MBLmo4o0wpIFYWjBgPFCw>
Subject: [DMM] I-D Action: draft-ietf-dmm-mag-multihoming-04.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.22
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, 30 Jun 2017 16:42:09 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Mobility Management of the IETF.

        Title           : MAG Multipath Binding Option
        Authors         : Pierrick Seite
                          Alper Yegin
                          Sri Gundavelli
	Filename        : draft-ietf-dmm-mag-multihoming-04.txt
	Pages           : 14
	Date            : 2017-06-30

Abstract:
   This specification defines extensions to the Proxy Mobile IPv6
   protocol for allowing a mobile access gateway to register more than
   one proxy care-of-address with the local mobility anchor and to
   simultaneously establish multiple IP tunnels with the local mobility
   anchor.  This capability allows the mobile access gateway to utilize
   all the available access networks for routing mobile node's IP
   traffic.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-mag-multihoming/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dmm-mag-multihoming-04
https://datatracker.ietf.org/doc/html/draft-ietf-dmm-mag-multihoming-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-mag-multihoming-04


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/

