
From nobody Mon Oct  2 22:52:45 2017
Return-Path: <tomonori.takeda@ntt.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E78CD13306F; Mon,  2 Oct 2017 22:52:43 -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, RCVD_IN_DNSWL_LOW=-0.7, 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 XfNd_dHwfjGY; Mon,  2 Oct 2017 22:52:40 -0700 (PDT)
Received: from mgw030.noc.ntt.com (mgw030.noc.ntt.com [210.160.55.3]) by ietfa.amsl.com (Postfix) with ESMTP id DDB76124207; Mon,  2 Oct 2017 22:52:39 -0700 (PDT)
Received: from c0043i0.coe.ntt.com (c0043i0.nc.agilit-hosting.com [10.18.161.12]) by mgw030.noc.ntt.com (NTT Com MailSV) with ESMTP id D44301C583E0; Tue,  3 Oct 2017 14:52:38 +0900 (JST)
Received: from C0035I0.coe.ntt.com (10.18.160.39) by c0043i0.coe.ntt.com (10.18.161.12) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 3 Oct 2017 14:52:38 +0900
Received: from C0561I0.coe.ntt.com ([169.254.1.200]) by C0035I0.coe.ntt.com ([10.18.160.39]) with mapi id 14.03.0361.001; Tue, 3 Oct 2017 14:52:38 +0900
From: Tomonori Takeda <tomonori.takeda@ntt.com>
To: "'TARAPORE, PERCY S'" <pt5947@att.com>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>
CC: "'rtg-dir@ietf.org'" <rtg-dir@ietf.org>, "'draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org'" <draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org>, "'mboned@ietf.org'" <mboned@ietf.org>
Thread-Topic: RtgDir review: draft-ietf-mboned-interdomain-peering-bcp-10.txt
Thread-Index: AdMbtumwnLtrsTGiQsK3S0y1oO1rugdbLPywALoEVuA=
Date: Tue, 3 Oct 2017 05:52:37 +0000
Message-ID: <EB0F2EAC05E9C64D80571F2042700A2A868D24D4@C0561I0.coe.ntt.com>
References: <EB0F2EAC05E9C64D80571F2042700A2A8684496C@C0561I0.coe.ntt.com> <ACC789373DA69C4285B9678D0CEBF86F13036DB1@MISOUT7MSGUSRDG.ITServices.sbc.com>
In-Reply-To: <ACC789373DA69C4285B9678D0CEBF86F13036DB1@MISOUT7MSGUSRDG.ITServices.sbc.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ccmail-original-to: pt5947@att.com, rtg-ads@ietf.org
x-ccmail-original-cc: rtg-dir@ietf.org, draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org, mboned@ietf.org
x-originating-ip: [10.25.140.153]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/FTtkL5YyVH45Unks7Llxsl-ReWc>
Subject: Re: [MBONED] RtgDir review: draft-ietf-mboned-interdomain-peering-bcp-10.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Oct 2017 05:52:44 -0000

SGkgUGVyY3ksDQoNClRoYW5rcyBmb3IgY2F0Y2hpbmcgdGhlc2UuIExvb2tzIGdvb2QgdG8gbWUu
DQoNClRvbW9ub3JpDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBUQVJBUE9S
RSwgUEVSQ1kgUyBbbWFpbHRvOnB0NTk0N0BhdHQuY29tXSANClNlbnQ6IEZyaWRheSwgU2VwdGVt
YmVyIDI5LCAyMDE3IDEwOjEzIFBNDQpUbzogVG9tb25vcmkgVGFrZWRh77yI5q2m55Sw55+l5YW4
77yJOyBydGctYWRzQGlldGYub3JnDQpDYzogJ3J0Zy1kaXJAaWV0Zi5vcmcnOyAnZHJhZnQtaWV0
Zi1tYm9uZWQtaW50ZXJkb21haW4tcGVlcmluZy1iY3AuYWxsQGlldGYub3JnJzsgJ21ib25lZEBp
ZXRmLm9yZycNClN1YmplY3Q6IFJFOiBSdGdEaXIgcmV2aWV3OiBkcmFmdC1pZXRmLW1ib25lZC1p
bnRlcmRvbWFpbi1wZWVyaW5nLWJjcC0xMC50eHQNCg0KSGkgVG9tb25vcmksDQoNClRoYW5rIHlv
dSBmb3IgeW91ciBjYXJlZnVsIHJlYWQgYW5kIGRldGFpbGVkIGNvbW1lbnRzIG9uIG91ciBCQ1Au
IFdlIGhhdmUgYWRkcmVzc2VkIHlvdXIgY29tbWVudHMgd2l0aCBuZXcgZXhwbGFuYXRvcnkgdGV4
dCBhbmQgYXBwcm9wcmlhdGUgY29ycmVjdGlvbnMuIFBsZWFzZSBzZWUgaW5saW5lIGJlbG93IGZv
ciBzcGVjaWZpY3MuIFRoZSBuZXcgdmVyc2lvbiByZWZsZWN0cyB0aGVzZSBjaGFuZ2VzIGFuZCBo
YXMgYmVlbiB1cGxvYWRlZC4NCg0KVGhhbmtzIGFnYWluLA0KDQpCZXN0IHdpc2hlcywNCg0KUGVy
Y3kNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFRvbW9ub3JpIFRha2VkYSBb
bWFpbHRvOnRvbW9ub3JpLnRha2VkYUBudHQuY29tXSANClNlbnQ6IFdlZG5lc2RheSwgQXVndXN0
IDIzLCAyMDE3IDEyOjUzIEFNDQpUbzogcnRnLWFkc0BpZXRmLm9yZw0KQ2M6ICdydGctZGlyQGll
dGYub3JnJyA8cnRnLWRpckBpZXRmLm9yZz47ICdkcmFmdC1pZXRmLW1ib25lZC1pbnRlcmRvbWFp
bi1wZWVyaW5nLWJjcC5hbGxAaWV0Zi5vcmcnIDxkcmFmdC1pZXRmLW1ib25lZC1pbnRlcmRvbWFp
bi1wZWVyaW5nLWJjcC5hbGxAaWV0Zi5vcmc+OyAnbWJvbmVkQGlldGYub3JnJyA8bWJvbmVkQGll
dGYub3JnPg0KU3ViamVjdDogUnRnRGlyIHJldmlldzogZHJhZnQtaWV0Zi1tYm9uZWQtaW50ZXJk
b21haW4tcGVlcmluZy1iY3AtMTAudHh0DQoNCkhlbGxvLCANCg0KDQoNCkkgaGF2ZSBiZWVuIHNl
bGVjdGVkIGFzIHRoZSBSb3V0aW5nIERpcmVjdG9yYXRlIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0
LiBUaGUgUm91dGluZyBEaXJlY3RvcmF0ZSBzZWVrcyB0byByZXZpZXcgYWxsIHJvdXRpbmcgb3Ig
cm91dGluZy1yZWxhdGVkIGRyYWZ0cyBhcyB0aGV5IHBhc3MgdGhyb3VnaCBJRVRGIGxhc3QgY2Fs
bCBhbmQgSUVTRyByZXZpZXcsIGFuZCBzb21ldGltZXMgb24gc3BlY2lhbCByZXF1ZXN0LiBUaGUg
cHVycG9zZSBvZiB0aGUgcmV2aWV3IGlzIHRvIHByb3ZpZGUgYXNzaXN0YW5jZSB0byB0aGUgUm91
dGluZyBBRHMuIEZvciBtb3JlIGluZm9ybWF0aW9uIGFib3V0IHRoZSBSb3V0aW5nIERpcmVjdG9y
YXRlLCBwbGVhc2Ugc2VlIOKAi2h0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91
cmw/dT1odHRwLTNBX190cmFjLnRvb2xzLmlldGYub3JnX2FyZWFfcnRnX3RyYWNfd2lraV9SdGdE
aXImZD1Ed0lHYVEmYz1MRllaLW85X0hVTWVNVFNRaWN2aklnJnI9NFo5eDFaQVJlWnBfbUphaEk2
aDliUSZtPUt3UDFoZ3h0R1JJT0YwX1FFRk40LXdoY0lPUUN5eWFjTy1MazVGNjhxUG8mcz04S19j
dFpaWTlBZ2d0eDFUdHpvZlpjRHotYnkwMnBMSmdQdUdkV2JXVGdNJmU9ICANCg0KDQoNCkFsdGhv
dWdoIHRoZXNlIGNvbW1lbnRzIGFyZSBwcmltYXJpbHkgZm9yIHRoZSB1c2Ugb2YgdGhlIFJvdXRp
bmcgQURzLCBpdCB3b3VsZCBiZSBoZWxwZnVsIGlmIHlvdSBjb3VsZCBjb25zaWRlciB0aGVtIGFs
b25nIHdpdGggYW55IG90aGVyIElFVEYgTGFzdCBDYWxsIGNvbW1lbnRzIHRoYXQgeW91IHJlY2Vp
dmUsIGFuZCBzdHJpdmUgdG8gcmVzb2x2ZSB0aGVtIHRocm91Z2ggZGlzY3Vzc2lvbiBvciBieSB1
cGRhdGluZyB0aGUgZHJhZnQuIA0KDQoNCg0KIERvY3VtZW50OiBkcmFmdC1pZXRmLW1ib25lZC1p
bnRlcmRvbWFpbi1wZWVyaW5nLWJjcC0xMC50eHQNCg0KIFJldmlld2VyOiBUb21vbm9yaSBUYWtl
ZGENCg0KIFJldmlldyBEYXRlOiBBdWcuIDIzcmQsIDIwMTcNCg0KIElFVEYgTEMgRW5kIERhdGU6
IEF1Zy4gMjNyZCwgMjAxNyANCg0KIEludGVuZGVkIFN0YXR1czogQkNQDQoNCg0KDQpTdW1tYXJ5
Og0KDQpUaGlzIGRvY3VtZW50IGlzIGJhc2ljYWxseSByZWFkeSBmb3IgcHVibGljYXRpb24sIGJ1
dCBoYXMgbml0cyB0aGF0IHNob3VsZCBiZSBjb25zaWRlcmVkIHByaW9yIHRvIHB1YmxpY2F0aW9u
Lg0KDQoNCg0KQ29tbWVudHM6DQoNClRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGRlcGxveW1lbnQg
c2NlbmFyaW9zIG9mIG11bHRpY2FzdCAoc3BlY2lmaWNhbGx5IFNTTSkgYWNyb3NzIGludGVyLWRv
bWFpbiBwZWVyaW5nIHBvaW50cy4gQWxzbywgdGhpcyBkb2N1bWVudCBkZXNjcmliZXMgc3VwcG9y
dGluZyBmdW5jdGlvbmFsaXRpZXMgZm9yIHRob3NlIGRlcGxveW1lbnQgc2NlbmFyaW9zLg0KDQpJ
IHRoaW5rIHRoZSBkb2N1bWVudCBpcyB3ZWxsLW9yZ2FuaXplZCBhbmQgZWFzeSB0byByZWFkLCBi
dXQgdGhlcmUgYXJlIGEgZmV3IHBvaW50cyB0byBiZSBjbGFyaWZpZWQuDQoNCg0KDQpNYWpvciBJ
c3N1ZXM6DQoNCk5vbmUNCg0KDQoNCk1pbm9yIElzc3VlczoNCg0KMSkgSSB0aGluayBpdCBpcyBi
ZXR0ZXIgdG8gZGVzY3JpYmUgYXNzdW1lZCBidXNpbmVzcyByZWxhdGlvbnNoaXAgYmV0d2VlbiBB
RC0xIGFuZCBBRC0yLCBwZXJoYXBzIGluIFNlY3Rpb24gMi4NCg0KQWNjb3JkaW5nIHRvIGRlc2Ny
aXB0aW9ucyBpbiBTZWN0aW9uIDQsIGl0IHNlZW1zIHRoYXQgQUQtMSBoYXMgdGhlIHVsdGltYXRl
IHJlc3BvbnNpYmlsaXR5IHRvIGRlbGl2ZXIgbXVsdGljYXN0IHRyYWZmaWMgdG8gRVUuDQoNCihG
b3IgZXhhbXBsZSwgaXQgc2F5cyAiQUQtMiBwcm92aWRlcyByZWxldmFudCBwZXJmb3JtYW5jZSBp
bmZvcm1hdGlvbiB0byBBRC0xOyB0aGlzIGVuYWJsZXMgQUQtMSB0byBjcmVhdGUgYW4gZW5kLXRv
LWVuZCBwZXJmb3JtYW5jZSB2aWV3IG9uIGJlaGFsZiBvZiB0aGUgbXVsdGljYXN0IGFwcGxpY2F0
aW9uIHNvdXJjZS4iKQ0KDQoNCg0KSSB0aGluayBhbm90aGVyIHBvc3NpYmxlIG1vZGVsIGlzIHRo
YXQgQUQtMSBpcyBwcm92aWRpbmcgYSB3aG9sZXNhbGUgc2VydmljZSB0byBBRC0yLCB3aGVyZSBB
RC0xJ3MgcmVzcG9uc2liaWxpdHkgaXMgdG8gZGVsaXZlcnkgZGF0YSB1cCB0byBBRC0yLCBhbmQg
QUQtMiBoYXMgdGhlIHVsdGltYXRlIHJlc3BvbnNpYmlsaXR5IHRvIGRlbGl2ZXJ5IGRhdGEgdG8g
RVVzIGFmdGVyd2FyZHMuDQoNCihOb3RlIHRoYXQgSSBhbSBub3Qgc2F5aW5nIHRoaXMgbW9kZWwg
c2hvdWxkIGJlIGluY2x1ZGVkIGluIHRoZSBkb2N1bWVudC4pDQoNCg0KDQpTbyBJIHRoaW5rIGl0
IGlzIGJlbmVmaWNpYWwgdG8gZGVzY3JpYmUgYXNzdW1lZCBidXNpbmVzcyByZWxhdGlvbnNoaXAg
YmV0d2VlbiBBRC0xIGFuZCBBRC0yIGluIHRoaXMgZG9jdW1lbnQuDQoNClBTVDogUGFyYWdyYXBo
IGFkZGVkIGluIFNlY3Rpb24gMiBib3R0b20gb2YgcGFnZSA1IHN0YXRpbmcgdGhhdCBBRC0xIGhh
cyBwcmltZSByZXNwb25zaWJpbGl0eS4NCg0KMikgSW4gU2VjdGlvbnMgMy4xIGFuZCAzLjIsIGl0
IHNheXM6DQoNCg0KDQogICAgICAibyBGZXdlciBkZXZpY2VzIGluIHRoZSBwYXRoIHRyYXZlcnNl
ZCBieSB0aGUgbXVsdGljYXN0IHN0cmVhbSB3aGVuDQoNCiAgICAgICAgIGNvbXBhcmVkIHRvIHVu
aWNhc3QgdHJhbnNtaXNzaW9ucy4iDQoNCg0KDQpJIGRvbid0IHVuZGVyc3RhbmQgdGhpcyBwb2lu
dC4NCg0KUFNUOiBCb3RoIHNlbnRlbmNlcyBoYXZlIGJlZW4gY2hhbmdlZCB0byBpbmRpY2F0ZSBj
b21wYXJpc29uIHdpdGggYW4gQU1UIGVuYWJsZWQgcGVlcmluZyBwb2ludC4NCg0KMykgSW4gU2Vj
dGlvbiAzLjIsIGl0IHNheXM6DQoNCg0KDQogICAgICAibyBBYmlsaXR5IHRvIHN1cHBvcnQgb25s
eSBwYXJ0aWFsIElQIG11bHRpY2FzdCBkZXBsb3ltZW50cyBpbiBBRC0NCg0KICAgICAgICAgMSBh
bmQvb3IgQUQtMi4iDQoNCg0KDQpJIGRvbid0IHVuZGVyc3RhbmQgdGhpcyBwb2ludC4gRm9yIGV4
YW1wbGUsIGFyZSB5b3UgYXNzdW1pbmcgdGhhdCBHUkUgaXMgdGVybWluYXRlZCBub3Qgb24gQVMg
Ym9yZGVyIHJvdXRlcnM/DQoNClBTVDogQ2xhcmlmeWluZyBzZW50ZW5jZSBhZGRlZCBpbiB0aGlz
IGJ1bGxldA0KDQpOaXRzOg0KDQoxKSBJIHRoaW5rIHNvbWUgb2YgdGhlIHJlZmVyZW5jZXMgbWF5
IG5vdCBiZSBhcHByb3ByaWF0ZS4gDQoNCi0gSW4gU2VjdGlvbiAxLCAiUElNLVNNIFtSRkM0NjA5
XSIgc2hvdWxkIGJlICJQSU0tU00gW1JGQzc3NjFdIj8NCg0KLSBJbiBTZWN0aW9uIDQuMSwgIk1C
R1AgW1JGQzQyNzFdIiBzaG91bGQgYmUgIk1CR1AgW1JGQzQ3NjBdIj8NCg0KUFNUOiBSZWZlcmVu
Y2VzIGNoYW5nZWQgYXMgcG9pbnRlZCBvdXQNCg0KMikgSW4gU2VjdGlvbiAxLCBpdCBzYXlzOg0K
DQoNCg0KICAgIlRodXMsIHRoZSBwcmltYXJ5IHB1cnBvc2Ugb2YgdGhpcyBkb2N1bWVudCBpcyB0
byBkZXNjcmliZSBhIHNjZW5hcmlvDQoNCiAgICB3aGVyZSB0d28gQUQncyBpbnRlcmNvbm5lY3Qg
dmlhIGEgZGlyZWN0IGNvbm5lY3Rpb24gdG8gZWFjaCBvdGhlci4iDQoNCg0KDQpJIHRoaW5rICJh
IGRpcmVjdGlvbiBjb25uZWN0aW9uIiBpcyBhIGJpdCB1bmNsZWFyLiBJbiBkZXBsb3ltZW50IHNj
ZW5hcmlvcywgeW91IGFyZSBtZW50aW9uaW5nIHRoYXQgdGhlIHBlZXJpbmcgcG9pbnQgaXMgbXVs
dGljYXN0IGVuYWJsZWQgb3Igbm90Lg0KDQpEb2VzIGl0IG1lYW4gdGhhdCB0aGUgcGVlcmluZyBw
b2ludCBtYXkgYmUgYSByb3V0ZWQgbmV0d29yaz8gSXQgd291bGQgYmUgZ29vZCB0byBjbGFyaWZ5
IHRoaXMuDQoNClBTVDogU2VudGVuY2UgY2hhbmdlZCB0byBzdGF0ZSB0aGF0IHRoZSAyIEFEJ3Mg
aW50ZXJjb25uZWN0IHZpYSBhIHBlZXJpbmcgcG9pbnQuDQoNCjMpIEluIFNlY3Rpb24gMy4yLCBp
cyBzYXlzOg0KDQoNCg0KICAgIlNlY3Rpb24gNC4zIHByb3ZpZGVzIGFuIG92ZXJ2aWV3IG9mIG9u
ZSBtZXRob2QgdGhhdA0KDQogICAgZmluZHMgdGhlIG9wdGltYWwgUmVsYXktR2F0ZXdheSBjb21i
aW5hdGlvbiB2aWEgdGhlIHVzZSBvZiBhbg0KDQogICAgQW55Y2FzdCBJUCBhZGRyZXNzIGZvciBB
TVQgUmVsYXlzLiINCg0KDQoNCkkgdGhpbmsgU2VjdGlvbiA0LjMgc2hvdWxkIGJlIFNlY3Rpb24g
NC4yPw0KDQpQU1Q6IFNlY3Rpb24gbnVtYmVyIGNvcnJlY3RlZC4NCg0KDQoNClRoYW5rcywNCg0K
VG9tb25vcmkgVGFrZWRhDQoNCg0KDQoNCg0K


From nobody Wed Oct  4 11:16:41 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B535E1326FE; Wed,  4 Oct 2017 11:16:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: <gen-art@ietf.org>
Cc: mboned@ietf.org, draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150714098566.24207.8484475992270538142@ietfa.amsl.com>
Date: Wed, 04 Oct 2017 11:16:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/fC83U2Rz1ch_EzutvnrFSOL5AoE>
Subject: [MBONED] Genart telechat review of draft-ietf-mboned-interdomain-peering-bcp-11
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Oct 2017 18:16:26 -0000

Reviewer: Christer Holmberg
Review result: 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 wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

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

Document: draft-ietf-mboned-interdomain-peering-bcp-11
Reviewer: Christer Holmberg
Review Date: 2017-10-04
IETF LC End Date: 2017-08-23
IESG Telechat date: 2017-10-12

Summary: My comments on the previous version of the document have been
addressed, and the document is now ready for publication.

Major issues: N/A

Minor issues: N/A

Nits/editorial comments: N/A



From nobody Sat Oct  7 06:26:08 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BCD4134913; Sat,  7 Oct 2017 06:26:06 -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: mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150738276639.11104.8228424675657368125@ietfa.amsl.com>
Date: Sat, 07 Oct 2017 06:26:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/Lz9LFhU2WVZSEAwNOck2unQiz6E>
Subject: [MBONED] I-D Action: draft-ietf-mboned-mtrace-v2-19.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Oct 2017 13:26:06 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the MBONE Deployment WG of the IETF.

        Title           : Mtrace Version 2: Traceroute Facility for IP Multicast
        Authors         : Hitoshi Asaeda
                          Kerry Meyer
                          WeeSan Lee
	Filename        : draft-ietf-mboned-mtrace-v2-19.txt
	Pages           : 36
	Date            : 2017-10-07

Abstract:
   This document describes the IP multicast traceroute facility, named
   Mtrace version 2 (Mtrace2).  Unlike unicast traceroute, Mtrace2
   requires special implementations on the part of routers.  This
   specification describes the required functionality in multicast
   routers, as well as how an Mtrace2 client invokes a query and
   receives a reply.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-mtrace-v2/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mboned-mtrace-v2-19
https://datatracker.ietf.org/doc/html/draft-ietf-mboned-mtrace-v2-19

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-mtrace-v2-19


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 Oct  9 06:00:49 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B66313243A; Mon,  9 Oct 2017 06:00:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150755404728.18412.14285421235071964427.idtracker@ietfa.amsl.com>
Date: Mon, 09 Oct 2017 06:00:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/Aj_rlc545u9lbh-0y9qodFfXlQk>
Subject: [MBONED] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-mboned-interdomain-peering-bcp-11=3A_=28with_COMMENT=29?=
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Oct 2017 13:00:47 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-mboned-interdomain-peering-bcp-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Minor questions/comments:

1) Section 3.4 also says:
"Highly efficient use of bandwidth in AD-1."
But aren't packets eventually duplicated in this case in AD-1? I guess it's
more efficient than replicating them at the network border but might be still
less efficient than native multicast in the whole network, no?

2) section 4.3.3 says:
"The two AD's may supply additional security logs..."
This seems to be a general action not specific to multicast or the scenarios
described in this doc.

3) I don't think the conclusion section (8) is helpful or needed. If you want
to keep it at all, this text could be moved into the introduction.



From nobody Tue Oct 10 08:29:54 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EA542135146; Tue, 10 Oct 2017 08:27:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150764927891.13436.4480686201231484122.idtracker@ietfa.amsl.com>
Date: Tue, 10 Oct 2017 08:27:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/-7a3f-CHcyk40S7XyY4OcUZkXRQ>
Subject: [MBONED] Alissa Cooper's Discuss on draft-ietf-mboned-interdomain-peering-bcp-11: (with DISCUSS and COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Oct 2017 15:29:39 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-mboned-interdomain-peering-bcp-11: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Section 4.3.3 recommends that ADs generate and exchange extensive logging
information, but the document says nothing about securing these logs or
limiting the exchange of private or confidential information between the peers.
This seems like it needs to be addressed in the BCP.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

(1) Why does this document contain the copyright disclaimer for pre-RFC5378
work?

(2) Section 4.4 says:

"In the event of performance degradation (SLA violation), AD-1
        may have to compensate the multicast application source per SLA
        agreement. As appropriate, AD-1 may seek compensation from AD-2
        if the cause of the degradation is in AD-2's network."

and

"Faults in service could lead to SLA violation for which the
        multicast application source provider may have to be
        compensated by AD-1. Subsequently, AD-1 may have to be
        compensated by AD-2 based on the contract."

These bullets seem out of scope for this BCP. I would recommend deleting them.

(3) Section 6 says:

"DRM and Application Accounting, Authorization and Authentication
   should be the responsibility of the multicast application source
   provider and/or AD-1. AD-1 needs to work out the appropriate
   agreements with the source provider.

   Network has no DRM responsibilities, but might have authentication
   and authorization obligations. These though are consistent with
   normal operations of a CDN to insure end user reliability, security
   and network security."

I find these two paragraphs somewhat contradictory and vague. The first
paragraph makes it sound like DRM could be the responsibility of AD-1. The
second paragraph makes it sound like AD-1 (assuming it counts as "network")
would never be responsible for DRM. Then later on the text says:

"Authentication and authorization of EU to receive multicast content
   is done at the application layer between the client application and
   the source. This may involve some kind of token authentication and
   is done at the application layer independently of the two AD's."

Is this differentiating authentication and authorization of the application
source from that of the end user? It's not clear. I would suggest revising this
whole section to be clear about which security functions are the responsibility
of which parties.



From nobody Tue Oct 10 12:48:59 2017
Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A2BB21286C7; Tue, 10 Oct 2017 12:48:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150766493762.13535.9148103792161037817.idtracker@ietfa.amsl.com>
Date: Tue, 10 Oct 2017 12:48:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/qOEShvCmodd0n0eVAcKpR0vltpg>
Subject: [MBONED] Kathleen Moriarty's Discuss on draft-ietf-mboned-interdomain-peering-bcp-11: (with DISCUSS and COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Oct 2017 19:48:57 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-mboned-interdomain-peering-bcp-11: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thanks for your work on this draft.  I'd like to see some text clarifications
on security recommendations that should not be difficult to resolve.

Section 4.4 - the exchange of supporting information could be sensitive, are
there security requirements on the exchange?  I don’t see them in this section.

Section 6 - For the following text, it would be helpful to see some
recommendations:
   “DRM and Application Accounting, Authorization and Authentication
   should be the responsibility of the multicast application source
   provider and/or AD-1. AD-1 needs to work out the appropriate
   agreements with the source provider.”


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I agree with and support Alissa's Discuss and comments.  Since she already
holds a discuss on this point, here are my comments: Section 4.3.3 clearly
refers to different types of logs, some have well known methods of delivery
(syslog) and authentication, but setting a minimum requirement for secure
exchange including encryption and authentication should be included in this
section. The protocols and options may vary between the log types.



From nobody Tue Oct 10 14:30:56 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A06A1321A2; Tue, 10 Oct 2017 14:30:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150767104932.13511.18068380159385743071.idtracker@ietfa.amsl.com>
Date: Tue, 10 Oct 2017 14:30:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/8axAUiNQMpfFGTJaZoB000eVJQA>
Subject: [MBONED] Spencer Dawkins' No Objection on draft-ietf-mboned-interdomain-peering-bcp-11: (with COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Oct 2017 21:30:49 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-mboned-interdomain-peering-bcp-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for doing this work.

I have comments, but they're all editorial.

In this text,

     o AD-1 and AD-2 are assumed to adopt compatible protocols. The
         use of different protocols is beyond the scope of this
         document.

"compatible protocols" isn't helpful without some context. Is this talking
about "compatible multicast protocols", or complete protocol stacks from IP on
up, or something else?

I'm also noticing that the terms "should" and "recommended" appear a few times
in this document. This is a BCP and doesn't reference BCP 14, which is all
fine, but the wording is likely to lead readers in one direction. I wonder if
it's helpful to say these things differently, so that (for instance)

         Hence, in the case of inter-domain peering, it is
         recommended to use only SSM protocols; the setup of inter-
         domain peering for ASM (Any-Source Multicast) is not in scope
         for this document.

might become

         Hence, this document assumes that in the case of inter-domain
         peering, only SSM protocols are used; the setup of inter-
         domain peering for ASM (Any-Source Multicast) is not in scope
         for this document.

Nit: "out of cope"

This text,

        packet streams will be part of a suitable
        multicast transport protocol.

didn't parse for me - was it saying

       packet streams will be carried by a suitable
       multicast transport protocol.

or something else?

In this text,

  Note that domain 2 may be an independent network domain (e.g., Tier
   1 network operator domain). Alternately, domain 2 could also be an
   Enterprise network domain operated by a single customer. The peering
   point architecture and requirements may have some unique aspects
   associated with the Enterprise case.

  The Use Cases describing various architectural configurations for
   the multicast distribution along with associated requirements is
   described in section 3. Unique aspects related to the Enterprise
   network possibility will be described in this section. Section 4
   contains a comprehensive list of pertinent information that needs to
   be exchanged between the two domains in order to support functions
   to enable the application transport.

it wasn't easy for me to tie "some unique aspects" in the first paragraph to
"will be described in this section" in the second - if the last sentence in the
first paragraph was moved to be the second paragraph, so the text was

  Note that domain 2 may be an independent network domain (e.g., Tier
   1 network operator domain). Alternately, domain 2 could also be an
   Enterprise network domain operated by a single customer.

  The Use Cases describing various architectural configurations for
   the multicast distribution along with associated requirements is
   described in section 3. The peering
   point architecture and requirements may have some unique aspects
   associated with the Enterprise case. These unique aspects will be
   described in this section. Section 4
   contains a comprehensive list of pertinent information that needs to
   be exchanged between the two domains in order to support functions
   to enable the application transport.

that would have been easier for me to follow. It's also worth mentioning that
I'm guessing that "section 3" is "this section" in that text, and I'm pretty
sure "this section" isn't "section 2", which is actually where the sentence
appears, but it might be easier for the reader to say "will also be described
in section 3".

The first sentence in

     e. The interconnection of AD-1 and AD-2 should, at a minimum,
        follow guidelines for traffic filtering between autonomous
        systems [BCP38]. Filtering guidelines specific to the multicast
        control-plane and data-plane are described in section 6.

just seems odd ("this BCP says you should do that BCP"). ISTM that if there are
multicast-specific reasons to do BCP38 in addition to the usual reasons, that
would be a fine thing to say here, of course.

If your audience doesn't already know

     o The GRE tunnel is often left pinned up.

(and if they don't, thank you for telling them), you might want to add a few
words explaining why that's a disadvantage.

In this text,

  The advantage for such a chained set of AMT tunnels is that the
   total number of unicast streams across AD-2 is significantly
   reduced, thus freeing up bandwidth. Additionally, there will be a
   single unicast stream across the peering point instead of possibly,
   an unacceptably large number of such streams per Use Case 3.4.
   However, this implies that several AMT tunnels will need to be
   dynamically configured by the various AMT Gateways based solely on
   the (S,G) information received from the application client at the EU
   device. A suitable mechanism for such dynamic configurations is
   therefore critical.

is there a good reference for "suitable mechanism(s)"?



From nobody Tue Oct 10 22:09:40 2017
Return-Path: <ben@nostrum.com>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8419B1201F8; Tue, 10 Oct 2017 22:09:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ben Campbell <ben@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150769857849.24691.13403211846518625609.idtracker@ietfa.amsl.com>
Date: Tue, 10 Oct 2017 22:09:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/DluOrfl6I3LqWoCDGGpr612BUWo>
Subject: [MBONED] Ben Campbell's Discuss on draft-ietf-mboned-interdomain-peering-bcp-11: (with DISCUSS and COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Oct 2017 05:09:38 -0000

Ben Campbell has entered the following ballot position for
draft-ietf-mboned-interdomain-peering-bcp-11: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

(This is related to Alissa's DISCUSS about logging of privacy-sensitive data.
But since it's a little different, I'm entering my own DISCUSS.)

 In section 4.4 (operations) the bullet on problem notification states that AD2
 will inform AD1 of, among other things, the locations of users. Is that
 intended to be geolocation, or network location? If the former, that's
 extremely sensitive information, and needs privacy guidelines.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Substantive Comments:

- I support Alissa's and Kathleen's DISCUSS positions.

- There seem to be quite a few implied assumptions about business models. I
will call out some specifically, but I'm sure I didn't catch them all. These
assumptions should either be removed or made explicit.

- The lists of guidelines seem to mix guidelines with observations of fact.
This makes it difficult to tell which parts are "best practices" (that is,
recommendations) vs which parts simply state fact.

-2: Is the assumption that the source is a service provider and the consumer is
an end-user relevant? This seems to perpetuate the (often false) assumption
that end users only consume content, but never produce it. It would be better
to state this in the form of whatever assumptions are implied by the idea of
SPs and EUs.  For example, do you assume there is a one to many relationship
between SPs and EUs?

-3.2: Why does this section not rate a figure? I think it would be helpful to
show the GRE tunnel as distinct from the native multicast.

-3.5, paragraph after Figure 4: The large number of tunnels implies some
assumptions about the cardinality between SPs and EUs that should be stated
explicitly. (It would help to show this in the figures.)

- 4.3.2: The idea that that AD1 has a need to identify users in AD2 seems to be
based on some implied business model assumptions. Please state those
explicitly. (Or if I missed where they are stated, please point out the text.)

-4.3.3: This states that logging is necessary for delivery. Why is that? Again,
this seems to make some implicit business model assumptions. This section also
needs explicit privacy considerations.

-4.4: The choice of monitoring, etc, seems to be up to the network operators to
decide. Why does this document need to "expect" that? It might be helpful to
describe how monitoring specific information could be useful (perhaps for
troubleshooting), but the document does not go into that. The statements about
compensation should be out of scope for an IETF document.

-5: Can you define, or reference a definition for, "Looking-Glass style".

-6: Please include a discussion of threat models. When might one choose to
encrypt or not encrypt? What risks exist if you don't encrypt?

-- : "DRM and Application Accounting, Authorization and Authentication should
be the responsibility of the multicast application source" Why? This seems to
imply some business model assumptions.

Editorial Comments:

- General: I find the heavy use of nested bullet lists hard to read. Much of
the information in the lists would be better suited to paragraph form,
especially when list entries span several sentences.  Likewise, the
inconsistent use of full sentences vs fragments makes it hard to read. (Maybe
this is just me)

-2: Please explain (s,g) before using, or even better spell it out. You do, in
fact, explain it in 4.2.3, but it's used quite a bit before you get to there.

-3.2, third bullet: "Ability to support only partial IP multicast
deployments..." Does this mean "only able to support partial..." or "able to
support partial..."?

- 3.3, figure:
The figures that involve tunnels would be easier to understand if you visually
distinguished tunnels from non-tunneled links.

- 3.3, e: "AMT tunnels will then configure dynamically"
s/configure/"be configured"

-3.4, d: " It is recommended that proper procedures are implemented such
     that the AMT Gateway at the End User device is able to find the
     correct AMT Relay..."
Is that a recommendation or a requirement necessary to work at all? (Same
construction appears in at least 3.5).

-4.1: Please expand SLA on first use.

-4.2.3: AMT Gateway: "The Gateway will reside on an End-Point - this
        may be a Personal Computer (PC) or a Set Top Box (STB)."
Is that meant to be exhaustive? Surely there are endpoints that do not resemble
PCs or STBs.

-4.2.3, example procedures for gateway selection:
The heavy use of passive voice in this section obscures the actors. (This is
true to some degree throughout the document, but it seems more confusing here.)

-4.3.2, 2nd bullet: Please don't use "/" as shorthand for conjunctions. 
(Pattern repeats throughout the rest of the draft.)

-4.3.3, first paragraph: The first sentence is hard to parse.

-6: Please expand DRM and CDN on first mention.



From nobody Wed Oct 11 19:13:55 2017
Return-Path: <adam@nostrum.com>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FA70133083; Wed, 11 Oct 2017 19:13:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Adam Roach <adam@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150777442861.16836.8073838629509620225.idtracker@ietfa.amsl.com>
Date: Wed, 11 Oct 2017 19:13:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/r3gHeNC469B2wHECWXvES79U8Vc>
Subject: [MBONED] Adam Roach's No Objection on draft-ietf-mboned-interdomain-peering-bcp-11: (with COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Oct 2017 02:13:49 -0000

Adam Roach has entered the following ballot position for
draft-ietf-mboned-interdomain-peering-bcp-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I support Alissa's and Kathleen's DISCUSSes; and (as a separate concern), I
support Ben's DISCUSS.

Most of the comments I noted in my review of this document have been made by
other reviewers, and I will not reiterate most of them. I would, however, like
to draw particular attention to Ben's comments regarding charging, billing, and
settlement -- I believe these issues should either be fleshed out in
significantly more detail, or removed (with a simple statement in the
introduction that such issues are generally out of scope for the entire
document).

___

Section 4.2.3 contains the following text:

    (Note
     that in IPv6 there is a specific Anycast format and Anycast is
     inherent in IPv6 routing, whereas in IPv4 Anycast is handled via
     provisioning in the network. Details are out of scope for this
     document.)

It would be helpful to the reader if the "out of scope" statement were
accompanied by a pointer to BCP 126/RFC 4786.

___

Section 5 contains the following text:

   It is expected that multicast diagnostics will be collected
   according to currently established practices [MDH-04].

I believe this statement makes [MDH-04] normative, as it is required to
understand its contents to implement the recommendations in this BCP.



From nobody Wed Oct 11 23:35:28 2017
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BAB31320B5; Wed, 11 Oct 2017 23:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.5
X-Spam-Level: 
X-Spam-Status: No, score=0.5 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 xJ2Ezwva0owX; Wed, 11 Oct 2017 23:35:18 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [IPv6:2001:200:0:8803::53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E808126CB6; Wed, 11 Oct 2017 23:35:17 -0700 (PDT)
Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 5C7E527850A; Thu, 12 Oct 2017 15:35:15 +0900 (JST)
Received: by mail-wm0-f48.google.com with SMTP id k4so10265739wmc.1; Wed, 11 Oct 2017 23:35:15 -0700 (PDT)
X-Gm-Message-State: AMCzsaXP8AZJMJdxSgDvxRld9WXpz0DqaT0ThyDe2DI4/s4CcdKmgg1h p75oHILajCWrBO45QB49PWi4AJZ/lgoLqoNSTg8=
X-Google-Smtp-Source: AOwi7QAw99y3D2vT1/TruOOlCQKQOcE1ORY+5NoxASCwaMDcCl/BdLlr/pyP79frm4Rdjhb+RxfND2AmcKd7TL4mld8=
X-Received: by 10.223.152.86 with SMTP id v80mr963155wrb.268.1507790113341; Wed, 11 Oct 2017 23:35:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.171.232 with HTTP; Wed, 11 Oct 2017 23:35:12 -0700 (PDT)
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Wed, 11 Oct 2017 23:35:12 -0700
X-Gmail-Original-Message-ID: <CAO249yeo-E2WQtBT7_DUF-B3ju26ypphO1NHDsb4LrYimZZ6Eg@mail.gmail.com>
Message-ID: <CAO249yeo-E2WQtBT7_DUF-B3ju26ypphO1NHDsb4LrYimZZ6Eg@mail.gmail.com>
To: tsv-art@ietf.org
Cc: mboned@ietf.org, draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org,  ietf@ietf.org
Content-Type: multipart/alternative; boundary="f403045f4f281a0766055b53be2e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/2v56hWeV_yU-CgORo168-urDIW4>
Subject: [MBONED] TSV-ART review of draft-ietf-mboned-interdomain-peering-bcp-11
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Oct 2017 06:35:21 -0000

--f403045f4f281a0766055b53be2e
Content-Type: text/plain; charset="UTF-8"

Document: draft-ietf-mboned-interdomain-peering-bcp-11
Reviewer: Yoshifumi Nishida

I've reviewed this document as part of TSV-ART's ongoing effort to review
key IETF documents. These comments were written primarily for the transport
area directors, but are copied to the document's authors for their
information and to allow them to address any issues raised.When done at the
time of IETF Last Call, the authors should consider this review together
with any other last-call comments they receive. Please always CC tsv-art
@ietf.org if you reply to or forward this review.

Summary: This document is almost ready for publication, but several points
need to be clarified.

1: In Section 3.1b,
    " If the peering point between AD-1 and AD-2 is a controlled

   network environment, then bandwidth can be allocated
   accordingly by the two domains to permit the transit of non-
   rate adaptive multicast traffic. If this is not the case, then
   it is recommended that the multicast traffic should support
   rate-adaption."


    I think we need to use rate-adaption approach in non-controlled network
environments.
    However, it seems to me that texts look a bit ambiguous on this point
as it just says it is recommended.
    Are there any other approach that doesn't require congestion control in
this case?

2: The configuration described in Section 3.4 doesn't look very scalable to
me as the traffic usage on I2 will be increased as the number of AMTs
increases.
    This looks a solid disadvantage of this configuration.
    Also, we don't need any guidelines on this?


3: In Section 4.1,
     "When determining the appropriate bandwidth allocation, parties should
consider use

       of a multicast protocol suitable for live video streaming that
       is consistent with Congestion Control Principles [BCP41
<https://tools.ietf.org/html/draft-ietf-mboned-interdomain-peering-bcp-11#ref-BCP41>]."


    The text looks a bit ambiguous to me. Only live video streaming
applications need to follow congestion control principle?
    "should consider use of .." sounds to me there will be some cases where
they don't need it. But, I'm wondering what would be the cases.
    Also, I believe we also need to consider the bandwidth allocation for
tunnels as well as multicast traffics, however, this is not very clear in
the texts.

Thanks,
--
Yoshi

--f403045f4f281a0766055b53be2e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style=3D"font-size:16px"><font face=3D"arial, helveti=
ca, sans-serif">Document: draft-ietf-mboned-interdomain-<wbr>peering-bcp-11=
<br></font></div><div style=3D"font-size:16px"><font face=3D"arial, helveti=
ca, sans-serif">Reviewer: Yoshifumi Nishida<br></font></div><div style=3D"f=
ont-size:16px"><font face=3D"arial, helvetica, sans-serif"><br></font></div=
><div style=3D"font-size:16px"><font face=3D"arial, helvetica, sans-serif">=
I&#39;ve reviewed this document as part of=C2=A0<span class=3D"m_-837994451=
9681842965gmail-m_-7214914472698653903gmail-il">TSV</span>-<span class=3D"m=
_-8379944519681842965gmail-m_-7214914472698653903gmail-il">ART</span>&#39;s=
 ongoing effort to review key IETF documents. These comments were written p=
rimarily for the transport area directors, but are copied to the document&#=
39;s authors for their information and to allow them to address any issues =
raised.When done at the time of IETF Last Call, the authors should consider=
 this review together with any other last-call comments they receive. Pleas=
e always CC=C2=A0<a href=3D"mailto:tsv-art@ietf.org" target=3D"_blank"><spa=
n class=3D"m_-8379944519681842965gmail-m_-7214914472698653903gmail-il">tsv<=
/span>-<span class=3D"m_-8379944519681842965gmail-m_-7214914472698653903gma=
il-il">art</span>@ietf.org</a>=C2=A0if you reply to or forward this review.=
<br></font></div><font face=3D"arial, helvetica, sans-serif" style=3D"font-=
size:16px"><br></font><div style=3D"font-size:16px"><font face=3D"arial, he=
lvetica, sans-serif">Summary:=C2=A0This document is almost ready for public=
ation, but several points need to be clarified.</font></div><div style=3D"f=
ont-size:16px"><font face=3D"arial, helvetica, sans-serif"><br></font></div=
><div style=3D"font-size:16px"><font face=3D"arial, helvetica, sans-serif">=
1: In Section 3.1b,</font></div><div><font face=3D"arial, helvetica, sans-s=
erif"><span style=3D"font-size:16px">=C2=A0 =C2=A0</span><font size=3D"1"> =
&quot;=C2=A0</font></font><span style=3D"color:rgb(0,0,0)"><font size=3D"1"=
 face=3D"arial, helvetica, sans-serif">If the peering point between AD-1 an=
d AD-2 is a controlled</font></span></div><pre class=3D"m_-8379944519681842=
965gmail-newpage" style=3D"margin-top:0px;margin-bottom:0px;color:rgb(0,0,0=
)"><font size=3D"1" face=3D"arial, helvetica, sans-serif">   network enviro=
nment, then bandwidth can be allocated
   accordingly by the two domains to permit the transit of non-
   rate adaptive multicast traffic. If this is not the case, then
   it is recommended that the multicast traffic should support
   rate-adaption.&quot;</font></pre><div style=3D"font-size:16px"><font fac=
e=3D"arial, helvetica, sans-serif">=C2=A0 =C2=A0 =C2=A0</font></div><div st=
yle=3D"font-size:16px"><font face=3D"arial, helvetica, sans-serif">=C2=A0 =
=C2=A0 I think we need to use rate-adaption approach in non-controlled netw=
ork environments.</font></div><div style=3D"font-size:16px"><font face=3D"a=
rial, helvetica, sans-serif">=C2=A0 =C2=A0 However, it seems to me that tex=
ts look a bit ambiguous on this point as it just says it is recommended.</f=
ont></div><div style=3D"font-size:16px"><font face=3D"arial, helvetica, san=
s-serif">=C2=A0 =C2=A0 Are there any other approach that doesn&#39;t requir=
e congestion control in this case?</font></div><div style=3D"font-size:16px=
"><font face=3D"arial, helvetica, sans-serif"><br></font></div><div style=
=3D"font-size:16px"><font face=3D"arial, helvetica, sans-serif">2: The conf=
iguration described in Section 3.4 doesn&#39;t look very scalable to me as =
the traffic usage on I2 will be increased as the number of AMTs increases.=
=C2=A0</font></div><div style=3D"font-size:16px"><font face=3D"arial, helve=
tica, sans-serif">=C2=A0 =C2=A0 This looks a solid disadvantage of this con=
figuration. =C2=A0</font></div><div style=3D"font-size:16px"><font face=3D"=
arial, helvetica, sans-serif">=C2=A0 =C2=A0 Also, we don&#39;t need any gui=
delines on this?</font></div><div style=3D"font-size:16px"><pre class=3D"m_=
-8379944519681842965gmail-m_-7214914472698653903gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><font f=
ace=3D"arial, helvetica, sans-serif"><br></font></pre></div><div style=3D"f=
ont-size:16px"><font face=3D"arial, helvetica, sans-serif">3: In Section 4.=
1,</font></div><div><font face=3D"arial, helvetica, sans-serif"><span style=
=3D"font-size:16px">=C2=A0 =C2=A0 </span><font size=3D"1">=C2=A0&quot;<span=
 style=3D"color:rgb(0,0,0)">When determining the</span><span style=3D"color=
:rgb(0,0,0)">=C2=A0appropriate bandwidth allocation, parties should conside=
r use</span></font></font></div><pre class=3D"m_-8379944519681842965gmail-m=
_-7214914472698653903gmail-newpage" style=3D"margin-top:0px;margin-bottom:0=
px;color:rgb(0,0,0)"><font face=3D"arial, helvetica, sans-serif"><font size=
=3D"1">       of a multicast protocol suitable for live video streaming tha=
t
       is consistent with Congestion Control Principles [<a href=3D"https:/=
/tools.ietf.org/html/draft-ietf-mboned-interdomain-peering-bcp-11#ref-BCP41=
" title=3D"&quot;Congestion Control Principles&quot;" target=3D"_blank">BCP=
41</a>].&quot;</font><span style=3D"font-size:13.3333px">
</span></font></pre><pre class=3D"m_-8379944519681842965gmail-m_-7214914472=
698653903gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-=
bottom:0px;color:rgb(0,0,0)"><font face=3D"arial, helvetica, sans-serif"><b=
r></font></pre><div><font face=3D"arial, helvetica, sans-serif">=C2=A0 =C2=
=A0 The text looks a bit ambiguous to me. Only live video streaming applica=
tions need to follow congestion control principle?</font></div><div><font f=
ace=3D"arial, helvetica, sans-serif">=C2=A0 =C2=A0 &quot;should consider us=
e of ..&quot; sounds to me there will be some cases where they don&#39;t ne=
ed it. But, I&#39;m wondering what would be the cases.</font></div><div><fo=
nt face=3D"arial, helvetica, sans-serif">=C2=A0 =C2=A0 Also, I believe we a=
lso need to consider the bandwidth allocation for tunnels as well as multic=
ast traffics, however, this is not very clear in the texts.</font></div><di=
v><span style=3D"font-family:arial,helvetica,sans-serif"><br></span></div><=
div><span style=3D"font-family:arial,helvetica,sans-serif">Thanks,</span><b=
r></div><div><font face=3D"arial, helvetica, sans-serif">--</font></div><di=
v><font face=3D"arial, helvetica, sans-serif">Yoshi</font></div></div>

--f403045f4f281a0766055b53be2e--


From nobody Thu Oct 12 06:49:40 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B25211321A4; Thu, 12 Oct 2017 06:49:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150781617870.16770.11927598062483869535.idtracker@ietfa.amsl.com>
Date: Thu, 12 Oct 2017 06:49:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/D0kIOtndtOOemtEZ-bu2CdlX3Vw>
Subject: [MBONED] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-ietf?= =?utf-8?q?-mboned-interdomain-peering-bcp-11=3A_=28with_DISCUSS_and_COMME?= =?utf-8?b?TlQp?=
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Oct 2017 13:49:38 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-mboned-interdomain-peering-bcp-11: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Sorry for this last minute discuss but I would like to emphasize the points
made in the tsv-art review on congestion/rate control (Thanks Yoshi!):

Please provide stronger guidance (MUST) on the use of rate/congestion control
in these two cases:

 In Section 3.1:
    " If the peering point between AD-1 and AD-2 is a controlled
   network environment, then bandwidth can be allocated
   accordingly by the two domains to permit the transit of non-
   rate adaptive multicast traffic. If this is not the case, then
   it is recommended that the multicast traffic should support
   rate-adaption."

In Section 4.1,
     "When determining the appropriate bandwidth allocation, parties should
     consider use
       of a multicast protocol suitable for live video streaming that
       is consistent with Congestion Control Principles [BCP41]."


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Minor questions/comments:

1) Section 3.4 also says:
"Highly efficient use of bandwidth in AD-1."
But aren't packets eventually duplicated in this case in AD-1? I guess it's
more efficient than replicating them at the network border but might be still
less efficient than native multicast in the whole network, no?

2) section 4.3.3 says:
"The two AD's may supply additional security logs..."
This seems to be a general action not specific to multicast or the scenarios
described in this doc.

3) I don't think the conclusion section (8) is helpful or needed. If you want
to keep it at all, this text could be moved into the introduction.



From nobody Sat Oct 14 21:35:14 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 00FB11270AB; Sat, 14 Oct 2017 21:35:06 -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: mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150804210595.12212.8389177143278321599@ietfa.amsl.com>
Date: Sat, 14 Oct 2017 21:35:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/_T8SQSdDrb6UXvG-WoUFPh1--dA>
Subject: [MBONED] I-D Action: draft-ietf-mboned-mtrace-v2-20.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Oct 2017 04:35:06 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the MBONE Deployment WG of the IETF.

        Title           : Mtrace Version 2: Traceroute Facility for IP Multicast
        Authors         : Hitoshi Asaeda
                          Kerry Meyer
                          WeeSan Lee
	Filename        : draft-ietf-mboned-mtrace-v2-20.txt
	Pages           : 36
	Date            : 2017-10-14

Abstract:
   This document describes the IP multicast traceroute facility, named
   Mtrace version 2 (Mtrace2).  Unlike unicast traceroute, Mtrace2
   requires special implementations on the part of routers.  This
   specification describes the required functionality in multicast
   routers, as well as how an Mtrace2 client invokes a query and
   receives a reply.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-mtrace-v2/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mboned-mtrace-v2-20
https://datatracker.ietf.org/doc/html/draft-ietf-mboned-mtrace-v2-20

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-mtrace-v2-20


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 Fri Oct 20 17:25:31 2017
Return-Path: <agenda@ietf.org>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 49D18134492; Fri, 20 Oct 2017 17:24:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <mboned-chairs@ietf.org>, <lenny@juniper.net>
Cc: mboned@ietf.org, warren@kumari.net
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150854545429.20809.9528923035910779198.idtracker@ietfa.amsl.com>
Date: Fri, 20 Oct 2017 17:24:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/3n4P6euMcSN3cKobwJKyTjluwko>
Subject: [MBONED] mboned - Requested session has been scheduled for IETF 100
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Oct 2017 00:24:14 -0000

Dear Leonard Giuliano,

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

mboned Session 1 (2:30:00)
    Tuesday, Morning Session I 0930-1200
    Room Name: VIP A size: 100
    ---------------------------------------------
    

Special Note: Joint session with PIM


Request Information:


---------------------------------------------------------
Working Group Name: MBONE Deployment
Area Name: Operations and Management Area
Session Requester: Leonard Giuliano

Number of Sessions: 1
Length of Session(s):  2.5 Hours
Number of Attendees: 50
Conflicts to Avoid: 
 First Priority: bess mmusic pim softwire bier v6ops




People who must be present:
  Joel Jaeggli
  Leonard Giuliano
  Mike McBride
  Stig Venaas
  Greg Shepherd
  Warren Kumari

Resources Requested:

Special Requests:
  Request a 2.5 hr slot for a joint WG session with PIM WG. 
---------------------------------------------------------


From nobody Thu Oct 26 23:43:43 2017
Return-Path: <lenny@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B1013F542 for <mboned@ietfa.amsl.com>; Thu, 26 Oct 2017 23:43:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
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 Uc0q0KPbyDNe for <mboned@ietfa.amsl.com>; Thu, 26 Oct 2017 23:43:29 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0124.outbound.protection.outlook.com [104.47.37.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D96E813B133 for <mboned@ietf.org>; Thu, 26 Oct 2017 23:43:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=v+loO/snsovgnQss3z9DHxA+r3ywkwGhTKKAH2N6+/E=; b=BCRE6J/nqxw7MLAYazUogZPuaOBKADYRHKqvUAepthULhiTI29NfIm7uj+uE1P/dzSkOX5hZl9ez8uC8Rcd7+uU4dF5BtksFwf8LNXvC8mLSDtGBeStoRSzxR/2ziFr9w+p/CpPxlI05bgm/8Z70Ch3+QDj0xAfy7edX0q149cc=
Received: from DM5PR05CA0020.namprd05.prod.outlook.com (10.173.226.30) by CY4PR05MB3607.namprd05.prod.outlook.com (10.171.244.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.178.3; Fri, 27 Oct 2017 06:43:27 +0000
Received: from DM3NAM05FT029.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::203) by DM5PR05CA0020.outlook.office365.com (2603:10b6:3:d4::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.197.4 via Frontend Transport; Fri, 27 Oct 2017 06:43:27 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by DM3NAM05FT029.mail.protection.outlook.com (10.152.98.140) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.20.178.5 via Frontend Transport; Fri, 27 Oct 2017 06:43:27 +0000
Received: from svl-jtac-lnx06.juniper.net (172.17.28.215) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server id 14.3.123.3; Thu, 26 Oct 2017 23:43:26 -0700
Received: by svl-jtac-lnx06.juniper.net (Postfix, from userid 1709)	id 5111D9F910; Thu, 26 Oct 2017 23:43:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by svl-jtac-lnx06.juniper.net (Postfix) with ESMTP id 4D1499F8F5	for <mboned@ietf.org>; Thu, 26 Oct 2017 23:43:26 -0700 (PDT)
Date: Thu, 26 Oct 2017 23:43:26 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
Message-ID: <alpine.DEB.2.02.1710262342140.21903@svl-jtac-lnx02.juniper.net>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format=flowed
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(376002)(346002)(39860400002)(2980300002)(189002)(199003)(23726003)(5660300001)(97736004)(50466002)(8936002)(478600001)(6916009)(50986999)(81156014)(58126008)(81166006)(76506005)(316002)(5005980100005)(16586007)(8676002)(105596002)(6266002)(106466001)(57986006)(54356999)(86362001)(305945005)(189998001)(558084003)(356003)(47776003)(83506002)(2906002)(53936002)(68736007)(7126002)(90966002)(77096006)(3240700002)(69596002)(45336002)(46386002)(2810700001)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR05MB3607; H:P-EMFE01C-SAC.jnpr.net; FPR:;  SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; DM3NAM05FT029; 1:imYCULAwCesIpwH8kBLfBrCzDIzBWyaDnaVz/Yv+MVyuYvJQFAnurMxGhnQVizoXUWmjzz0Rpo3chEdD9t0wmzR2poPuTENh9J7Bb9u8DknIpJR6n0u8hAcSQ+sYx4m3
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 54885e9d-922e-44f9-5f51-08d51d06078b
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(2017052603238); SRVR:CY4PR05MB3607; 
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3607; 3:slJzqCEUrf0BjvmL6S+vha6KKMxxQxyypmHJlw/CnSrgyclPhdiF2pY3R7B5wIBa3AQSzAQs+Rk40sQhCsHCKh8PIOlbTzaqq8EJMjUbBphYys6Irl2xQdnpqtzYk0/mqclhAv/PThtRuFsMYuVAAY9Su2xTneFKGQKPcwzzIFejCFwbzD8UZxUot1wu2b2MgxbtM3ZVWiUXcI1q88uZk4ne3Bu7/g2zvSpeWlR4AjhMf5mAFi5I6YJDI3EuKc5Appd/n9pp6J3qEBNFZIvB4amNaDIRYj5IhobAbVMN36yZRrux2A5ZFCXGpjcD+gJVBdUKsA51IdpnXLKMWLQqHc+wjfoiRE23prj/jaDe2Dw=; 25:Z1pU6zn1Fo2mzAByjzfO0brks8Azgg1l1E19YKpBOZbn/MmlFcNLdmgGqUTVEhfVO4jenhDtXUq2ekvF0sLlbiCMKJpvTOHcFGsdAA9txS2WFSUHSReR41CCfBxmqk0ryDO0LvLfW4P8RQXQ0UjY2vPs5bRbpQioULyJULz++dQYW3eLUtLV71+fPHLfR6QoFM29aIdA9b0tZldk4xJa8762vOM0PB2w6AjObnRyx7RI5rXTCrLBvBpbb1zq4AY6NUFCzln8BQY0e4PqlJRo1dMz1HCEQ8VlRjCAxk4sBxyjcqwN/iTuxT2G028AO2kgibTNc+WM9xuDW48npmZPDg==
X-MS-TrafficTypeDiagnostic: CY4PR05MB3607:
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3607; 31:8xOGqkgBrpu/EnLtn5fT2MCJ0gSAaPQubcVObNI2XjAmQFX5mb6HRZ/sCSaYPLmNIj4zpzcnHAyfcd9KN02KF4qQ9E8A3Zl6bplB3TyrQysQlq2I6C8mlSvRnxOVeiLVCnjPa/to4S0eDFRz3G0VC/w4eEuttpGo+LpJg0iYuzBRwCp4ygu9YxpwBF2pcHjvU3zuH/2spBEdLciYAAZE975GeQqdi/bSsYfrX9CS6Mw=; 20:lWaryLmtXZuaW/hoWvNq0KqAW8h7BVwDNhu+9+NcLsIbcf3T1vURTpW18KjqI99rY4KwSC0Da3lQLSdnmo7nt9VADmvZtm/zNsGOjuJUjECyw0OsLOm9gPZ/ywsqIe9FFJ5av4NtQUZTKAJj/o7vQVK/Hk0b97LUMoWgD3mwi+cmFwFLaiRZ2wKToJuv4Eyl3bsZKxjCWZwIru6bKaC+lCElVfx5SBa55OtZuFn7fov7MPgtuJLmOvHsg+d5QJoB9M2mUK+9qaJyZmLh/h0yy4HZbt31rzxDBwZkDFUJAFRqu93w+b1r9N1CUiSe397euU5x4ZmTYihEFjU+ac4sdxrhgVoK9C4sSwIDYYb7nijMuzyqmeY0VUHMCJ78ZR+rnHSYMfH1nWUAMhQ/4cHkrujQRKjhOSuPbS9OasFucnS19ntdaFKL7w4v4V0oE28ESfIc37v3Tk2ZftUIv6EdeTAdsQ0IlcwUvmQZBBkYfq6oQGITrvMOnrLMx/itTtTn
X-Exchange-Antispam-Report-Test: UriScan:;
X-Microsoft-Antispam-PRVS: <CY4PR05MB36072234EA99BFDD598A1E64A45A0@CY4PR05MB3607.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(3002001)(100000703101)(100105400095)(3231020)(10201501046)(93006095)(93001095)(6055026)(6041248)(20161123564025)(20161123560025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123558100)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY4PR05MB3607; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY4PR05MB3607; 
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3607; 4:xPQi6V2EmAg9gsbS2qcWmPSlEgfXxXzQbvnDDCdxNT9XTugR8vlwoigExB2DCh0R+6YV69ioOKuENrAvanmaaTO620hcsSo2mUOLBos2l/iECBd8eIYtHyClgERgJ5XrKpGEwrCkI0cxFWL8QFn88FLfsTyKADYjW3/OIdrEuHusBpSBMO0UftBZNE/HmGtHgMJoTCOUIFiXMQKOdNC7e5RfULJIYrP6+iBRuFRYdpet6qtTMmGXC0XfIDXEdjibV32KyQk1Xy3UB1HevbvhIg==
X-Forefront-PRVS: 0473A03F3F
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CY4PR05MB3607; 23:cHLdWfsm2PvqGxsCrMo5dA4og9jc7x3ethupi2t/i?= =?us-ascii?Q?B+u849kEsi023saA8Lh62qWo+4Xq5L4q25Dl89coVchNzhOkeOixjHY5p00K?= =?us-ascii?Q?y69WUFLL5dNByCQiKXvbMfAutmsanNhGDtYkuNh4WTt+2hbSX3tjKBTFGvEs?= =?us-ascii?Q?lJhjDxLVqwOhvET/JTB8WZHyg6ve/uugvnz8oSXwiq5k2kf1pjoRLptKxYdJ?= =?us-ascii?Q?OuzgH5GIVLYwsY+42bXXGNbuKXfHZsjA1sMwZdrJngvl6Ei6WBub8nHyBqlH?= =?us-ascii?Q?blFKs3wxTDRl3GeNyHZgGWPLlMpnT1dQrLSgHXlkF9abL2u/XlQGTJOLBf7v?= =?us-ascii?Q?v3oEs8vQz+CZjQH10B83DIG1Hh2Sncycf/IrI0kVHCif0Urn4BrwtT2esoGN?= =?us-ascii?Q?yuyljTqKs+v8YIG4xAqR+gqHHS38UHYBcBmkJ9sxDDxB7d/+ipux3L54GDwK?= =?us-ascii?Q?mKTZLeR+4YM4yaHQjMal0GXDfKkeAvBoF+4OldkLULpxNqcuSJvnOC71KZN2?= =?us-ascii?Q?tFC82caRsr87aUYl2jOe2932myYvyaSKQ92+Z0SgWDEL4lbzxwKVIJDE7S2O?= =?us-ascii?Q?6Fjsd/p20JlmR9eg/ZuXokOwTsjUNuPqEHYFB/d+JtMqU6EqUyl+tm+cWgfQ?= =?us-ascii?Q?0sW77DaULgkp6FYmuhdLhl7NJ7nmD2CYHRCUxh/Cfe7r2nNFd8VPAGurq+X0?= =?us-ascii?Q?HSkX/FH4QFyU4INB8FK2JytgmGb65APykvEsl8jFUTdiaS0ktb1xa4iBRQpa?= =?us-ascii?Q?/GCeDl/AaAVYNV/3mOSef4j/IlcQgqWFUo0EBXRbFP4/Cb/naF2EQrTMI2if?= =?us-ascii?Q?rOOZROyPBBjdUWv3hZssloUJ3dF+5u9Un0LFsgIeUxfQj6eTP/lWGwOZZbVk?= =?us-ascii?Q?sJZttzNQWxkxoJac8XlJoG4Yia92CSYrKf1w+D3d4YBgUq1dSHozXHVvGahw?= =?us-ascii?Q?RNCFT6zkA+kZOe/SP+9BpsVGNzCNO5I7j1x87pWJ4918iXROy9VQYlbot4eF?= =?us-ascii?Q?Oepm3W00+plK3DNGvVODvXb+77/ctVr5D044Adto47HfrEM5nh0M/r+3QZYH?= =?us-ascii?Q?tJPmMwEQVQ26JEwVBRNJamo2/fCIeNeiWJqW/llyVrh7z1nGpZZ6Pj5zRyuQ?= =?us-ascii?Q?OaD0gY/Wdid+rR7XyPoPPhwz9PGTafm?=
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3607; 6:8JmQTx9Dh9E1EYh+u8TZ+tis9w/bKJWFMB6MgeFyAj288pISbGFJz7t6s9n9bLg4BLmxJaYq2U/6yUmfxIctGj07AASA62gDdYhHqQxNEVw+EbOiYuJ3lZnX7//A3vZcAC3OFiqsTWAJmjXwAvMcHOMwB1LYip3EOKmCytMH0gGayfny3Fi2MfEqVfbc2ke1Xz+uQRFt0R4mtgVtwbKuN8uTGuBjFqp9dMen8vryVd8gTMS/D26F4oQUeRVDr3nKi494KV/8n8pr066A+bi5KPERrBK8SjmlvpjcnLtwDi8i7vfTFO0mJiqLGhGo7y8dsI8AnOKrtQ51gl4PW2rR9b4jkUjoqbSD67E+EsrzPIA=; 5:7pU1kNuA/LRTS0iwIeZ6WSu0zOq/nKHmFYp53VDHzxBht9G2oN/SVeVahep+kM0nSqW7BPQOV1zn2zCs+3MwqtIPcSrMTFvspBN89C/Sw7VsMU6jPlOuaEXh/OgYNDLPfFPGnE36gMyCDHF75r92ytTygVCcp7pPmBbXQyrmDz0=; 24:vDXQRghvd8C49TECtVwCgRZHianDBEyzqY9Tb3o7f+OLi7or7nkIyJM+OspirL659c/b02+9gae9HWWDUwj2WHYSQFHb2TjF/BNQQwo/TAQ=; 7:3G8TrgQr9RrREiDyN9Sb1MrVgcj25h+DDStdPU9qTJGQD4cePRL2+cL8NlU12MK5vwPQO5LXwI7eoJNbUbC1w73YUqDlOIYfqoXFhRijENw3CpB1LeQdEfuHSaByg/nH835ogIg6b7tuILwlBd4rLZVVcfNxM9dM/l8WVOy7absxbcqpl0JwvNA9hQLoA1s9tErKqMm/n+pxpwmSzH4RSQIH+sx0fQYsXlrAlVQO5Cxbb16/7KSVEd+hqtuz7srh
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Oct 2017 06:43:27.1820 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 54885e9d-922e-44f9-5f51-08d51d06078b
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR05MB3607
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/oqXJo7212p8LO67aaTjY94yFfUw>
Subject: [MBONED] call for MBONED agenda items in Singapore
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2017 06:43:33 -0000

We are currently scheduled for 9:30AM on Tues, once again meeting jointly with 
PIM WG. If you have something you'd like to present, please let the chairs know 
what the draft name is and how much time you would like.


-Lenny and Greg


From nobody Fri Oct 27 17:02:08 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 70457139078; Fri, 27 Oct 2017 17:02:06 -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: mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150914892640.2709.17686976827208377049@ietfa.amsl.com>
Date: Fri, 27 Oct 2017 17:02:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/73LHizodMqpueR1xjgV0PwCmr08>
Subject: [MBONED] I-D Action: draft-ietf-mboned-interdomain-peering-bcp-12.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 00:02:06 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the MBONE Deployment WG of the IETF.

        Title           : Use of Multicast Across Inter-Domain Peering Points
        Authors         : Percy S. Tarapore
                          Robert Sayko
                          Greg Shepherd
                          Toerless Eckert
                          Ram Krishnan
	Filename        : draft-ietf-mboned-interdomain-peering-bcp-12.txt
	Pages           : 28
	Date            : 2017-10-27

Abstract:
   This document examines the use of Source Specific Multicast (SSM)
   across inter-domain peering points for a specified set of deployment
   scenarios.  The objective is to describe the setup process for
   multicast-based delivery across administrative domains for these
   scenarios and document supporting functionality to enable this
   process.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mboned-interdomain-peering-bcp-12
https://datatracker.ietf.org/doc/html/draft-ietf-mboned-interdomain-peering-bcp-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-interdomain-peering-bcp-12


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 Fri Oct 27 17:04:05 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EB41613A296; Fri, 27 Oct 2017 17:04:03 -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: mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150914904392.2655.6617930294349291634@ietfa.amsl.com>
Date: Fri, 27 Oct 2017 17:04:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/w_fBC4pR-6nBSH9u5syu3YBEr7s>
Subject: [MBONED] I-D Action: draft-ietf-mboned-interdomain-peering-bcp-13.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 00:04:04 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the MBONE Deployment WG of the IETF.

        Title           : Use of Multicast Across Inter-Domain Peering Points
        Authors         : Percy S. Tarapore
                          Robert Sayko
                          Greg Shepherd
                          Toerless Eckert
                          Ram Krishnan
	Filename        : draft-ietf-mboned-interdomain-peering-bcp-13.txt
	Pages           : 41
	Date            : 2017-10-27

Abstract:
   This document examines the use of Source Specific Multicast (SSM)
   across inter-domain peering points for a specified set of deployment
   scenarios.  The objective is to describe the setup process for
   multicast-based delivery across administrative domains for these
   scenarios and document supporting functionality to enable this
   process.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mboned-interdomain-peering-bcp-13
https://datatracker.ietf.org/doc/html/draft-ietf-mboned-interdomain-peering-bcp-13

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-interdomain-peering-bcp-13


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 Fri Oct 27 17:05:23 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52F2C13A296; Fri, 27 Oct 2017 17:05:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.712
X-Spam-Level: 
X-Spam-Status: No, score=-2.712 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 RLcxPgiWClmx; Fri, 27 Oct 2017 17:05:13 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB44313F487; Fri, 27 Oct 2017 17:05:13 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id EBEEE58C4AE; Sat, 28 Oct 2017 02:05:07 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id D95BFB0CFDD; Sat, 28 Oct 2017 02:05:07 +0200 (CEST)
Date: Sat, 28 Oct 2017 02:05:07 +0200
From: Toerless Eckert <tte+ietf@cs.fau.de>
To: Mirja K?hlewind <ietf@kuehlewind.net>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
Message-ID: <20171028000507.GA22613@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <150755404728.18412.14285421235071964427.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/vs_S_XHkaLgJdqZnOAwS4U5kdRY>
Subject: Re: [MBONED] Mirja K?hlewind's No Objection on draft-ietf-mboned-interdomain-peering-bcp-11: (with COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 00:05:16 -0000

[The following text up to the individual reply comments is identical for 
 the replies to all ballot comments. I originally wanted to coalesce the reply to
 all positions into one email but the auto-generated header from datatracker
 makes it sound as if per-submitter replied are required. So, here we go with some
 repeated text followed by more individualized text:]

Dear Reviewer,

This is in response of your reviews of
    https://www.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-11.txt
as entered in the ballot:
    https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/ballot/

A version of this email containing replies to all IESG feedback for -11 is also in: 
    https://raw.githubusercontent.com/toerless/peering-bcp/master/11-iesg-review-reply.txt

Thank you so much for your thorough review. In response to the IESG
feedback, version -12 and -13 of the draft where posted which we hope 
will resolve the open issues.
make 2

Version -12 of the draft was just a conversion from docx generated txt to XML (previous generations
where not built from XML), this introduced formatting changes (line wraps etc.) that rfcdiff can not ignore
and that would have obfuscated actual content changes. 

Version -13 of the draft contains the text changes done in response to your
comments and discusses. The following RFC diff shows the content diffs
vs. -11 without any formatting introduced changes:

http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-12.txt&url2=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-13.txt

In summary:
   Beside the various smaller fixups from comments, the mayor rewritten/new blocks are:

   4.1.1 - bandwidth management (aka: congestion control section). 
           I didn't just want to put the magic CC sentence in but wanted to let
           readers understand what it means in the context of specifically
   6. Security considerations
      6.1.  DoS attacks (against state and bandwidth)	
      6.2.  Content security	
      6.3.  Peering encryption
      6.4.  Operational Aspects
            This is where the securing of log exchange is discussed.
   7. Privacy Considerations
      Got somewhat longer to explain because the specifics of multicast content and privacy
      are likely not that obious to non-multicast  experienced readers, and given how this
      is a BCP and i don't even think we did describe this anywhere else, it had to be
      explanatory.
   
   4.2.4.  Public Peering Routing Aspects
      text did mention non-private peerings, but i was afraid that readers would not
      understand the problematic implications, so i detailled them given how those
      peering L2 domains are still common for unicast.


Cheers
    Toerless for the Authors

=====================================================================================
Mirja Kuehlewind:


> Sorry for this last minute discuss but I would like to emphasize the points made in the tsv-art review on congestion/rate control (Thanks Yoshi!):

> Please provide stronger guidance (MUST) on the use of rate/congestion control in these two cases:
> 
>  In Section 3.1:
>     " If the peering point between AD-1 and AD-2 is a controlled
>    network environment, then bandwidth can be allocated
>    accordingly by the two domains to permit the transit of non-
>    rate adaptive multicast traffic. If this is not the case, then
>    it is recommended that the multicast traffic should support
>    rate-adaption."
> 
> In Section 4.1,
>      "When determining the appropriate bandwidth allocation, parties should consider use
>        of a multicast protocol suitable for live video streaming that
>        is consistent with Congestion Control Principles [BCP41]."

I tried to fix this text a bit more comprehensively:
- removed text from 3.1. The CC requirements apply to every subsection of 3 (3.x)
  and it duplicates partial text in 4.1, so a random mentioning in 3.1 was not
  helpfull.
- Moved CC text from 4.1 to dedicated section 4.1.1 and made it a lot more explanatory
  because in my past experience most readers do not really understand our cryptic
  rules alone ("CC principles across non-controlled network paths"). Also added
  reference to the fresh BCP145.

Please re-read new section and let me know what you think.

> Minor questions/comments:
> 
> 1) Section 3.4 also says:
> "Highly efficient use of bandwidth in AD-1."
> But aren't packets eventually duplicated in this case in AD-1? I guess it's more efficient than replicating them at the network border but might be still less efficient than native multicast in the whole network, no?

Changed to:
  <t>Efficient use of bandwidth in AD-1 (The closer AR is to uBR, the more efficient).</t>

> 2) section 4.3.3 says:
> "The two AD's may supply additional security logs..."
> This seems to be a general action not specific to multicast or the scenarios described in this doc.

Yes, i thought about this and came up with the following explanation:
   
   <t>Note that except for implied multicast specific elements,
   the options listed here are not unique or novel for IP multicast, but
   they are more important for services novel to the operators than for
   operationally well established services (such as unicast).  Therefore
   we detail them as follows:</t>

> 3) I don't think the conclusion section (8) is helpful or needed. If you want to keep it at all, this text could be moved into the introduction.

Removed - for the time being. I was told that having a wrap up in documents is
always a good way to reflect on the document, but i agree the existing text
is more distracting than helpful.


From nobody Fri Oct 27 17:06:08 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DB1213F574; Fri, 27 Oct 2017 17:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.712
X-Spam-Level: 
X-Spam-Status: No, score=-2.712 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 K5VUiYcTvCZK; Fri, 27 Oct 2017 17:06:04 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90B2D13F629; Fri, 27 Oct 2017 17:05:33 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 99DC658C4AE; Sat, 28 Oct 2017 02:05:29 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 8A227B0CFDD; Sat, 28 Oct 2017 02:05:29 +0200 (CEST)
Date: Sat, 28 Oct 2017 02:05:29 +0200
From: Toerless Eckert <tte+ietf@cs.fau.de>
To: Alissa Cooper <alissa@cooperw.in>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
Message-ID: <20171028000529.GB22613@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <150764927891.13436.4480686201231484122.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/mVc6MaXZrzN5kq6g-_mbVwH8qM8>
Subject: Re: [MBONED] Alissa Cooper's Discuss on draft-ietf-mboned-interdomain-peering-bcp-11: (with DISCUSS and COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 00:06:07 -0000

[The following text up to the individual reply comments is identical for 
 the replies to all ballot comments. I originally wanted to coalesce the reply to
 all positions into one email but the auto-generated header from datatracker
 makes it sound as if per-submitter replied are required. So, here we go with some
 repeated text followed by more individualized text:]

Dear Reviewer,

This is in response of your reviews of
    https://www.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-11.txt
as entered in the ballot:
    https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/ballot/

A version of this email containing replies to all IESG feedback for -11 is also in: 
    https://raw.githubusercontent.com/toerless/peering-bcp/master/11-iesg-review-reply.txt

Thank you so much for your thorough review. In response to the IESG
feedback, version -12 and -13 of the draft where posted which we hope 
will resolve the open issues.
make 2

Version -12 of the draft was just a conversion from docx generated txt to XML (previous generations
where not built from XML), this introduced formatting changes (line wraps etc.) that rfcdiff can not ignore
and that would have obfuscated actual content changes. 

Version -13 of the draft contains the text changes done in response to your
comments and discusses. The following RFC diff shows the content diffs
vs. -11 without any formatting introduced changes:

http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-12.txt&url2=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-13.txt

In summary:
   Beside the various smaller fixups from comments, the mayor rewritten/new blocks are:

   4.1.1 - bandwidth management (aka: congestion control section). 
           I didn't just want to put the magic CC sentence in but wanted to let
           readers understand what it means in the context of specifically
   6. Security considerations
      6.1.  DoS attacks (against state and bandwidth)	
      6.2.  Content security	
      6.3.  Peering encryption
      6.4.  Operational Aspects
            This is where the securing of log exchange is discussed.
   7. Privacy Considerations
      Got somewhat longer to explain because the specifics of multicast content and privacy
      are likely not that obious to non-multicast  experienced readers, and given how this
      is a BCP and i don't even think we did describe this anywhere else, it had to be
      explanatory.
   
   4.2.4.  Public Peering Routing Aspects
      text did mention non-private peerings, but i was afraid that readers would not
      understand the problematic implications, so i detailled them given how those
      peering L2 domains are still common for unicast.

Cheers
    Toerless for the Authors

========================================================================================
Alissa Cooper:

> Section 4.3.3 recommends that ADs generate and exchange extensive logging information, but the document says nothing about securing these logs or limiting the exchange of private or confidential information between the peers. This seems like it needs to be addressed in the BCP.

Sure. Pls. re-read the first four paragraphs of the Log Management section, i tried to make
it clearer. Also the new section on privacy.

> (1) Why does this document contain the copyright disclaimer for pre-RFC5378 work?

It has been there since -00, and i can not think of any reason why it should be there,
so i removed it.

Will also send email to working group mailing list to re-check.

> (2) Section 4.4 says:
> 
> "In the event of performance degradation (SLA violation), AD-1
>         may have to compensate the multicast application source per SLA
>         agreement. As appropriate, AD-1 may seek compensation from AD-2
>         if the cause of the degradation is in AD-2's network."
> 
> and
> 
> "Faults in service could lead to SLA violation for which the
>         multicast application source provider may have to be
>         compensated by AD-1. Subsequently, AD-1 may have to be
>         compensated by AD-2 based on the contract."
>     
> These bullets seem out of scope for this BCP. I would recommend deleting them.

Removed. 

I welcome a chat in Singapore why everybody seems to think the word "money"
must not be mentioned, not even in an operational document. 

> (3) Section 6 says:
> 
> "DRM and Application Accounting, Authorization and Authentication
>    should be the responsibility of the multicast application source
>    provider and/or AD-1. AD-1 needs to work out the appropriate
>    agreements with the source provider.
> 
>    Network has no DRM responsibilities, but might have authentication
>    and authorization obligations. These though are consistent with
>    normal operations of a CDN to insure end user reliability, security
>    and network security."
> 
> I find these two paragraphs somewhat contradictory and vague. The first paragraph makes it sound like DRM could be the responsibility of AD-1. The second paragraph makes it sound like AD-1 (assuming it counts as "network") would never be responsible for DRM. Then later on the text says:
> 
> "Authentication and authorization of EU to receive multicast content
>    is done at the application layer between the client application and
>    the source. This may involve some kind of token authentication and
>    is done at the application layer independently of the two AD's."
> 
> Is this differentiating authentication and authorization of the application source from that of the end user? It's not clear. I would suggest revising this whole section to be clear about which security functions are the responsibility of which parties.

Pls. re-read the security section, i have tried to rewrite it with
a clearer description of these aspect. As someone like me who is
deep int the subject matter it is always easy to overlook explaining
what we may think are well understood fundamentals, so please keep
complaining until its understandable!


From nobody Fri Oct 27 17:06:50 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B4C713F629; Fri, 27 Oct 2017 17:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.712
X-Spam-Level: 
X-Spam-Status: No, score=-2.712 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 rVHQjuQzwFiH; Fri, 27 Oct 2017 17:06:28 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D728C13F614; Fri, 27 Oct 2017 17:05:54 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 9333F58C4AE; Sat, 28 Oct 2017 02:05:50 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 82368B0CFDD; Sat, 28 Oct 2017 02:05:50 +0200 (CEST)
Date: Sat, 28 Oct 2017 02:05:50 +0200
From: Toerless Eckert <tte+ietf@cs.fau.de>
To: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
Message-ID: <20171028000550.GC22613@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <150766493762.13535.9148103792161037817.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/jbR-ViwYezmaTBsJkrsJPFyYQiM>
Subject: Re: [MBONED] Kathleen Moriarty's Discuss on draft-ietf-mboned-interdomain-peering-bcp-11: (with DISCUSS and COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 00:06:42 -0000

[The following text up to the individual reply comments is identical for 
 the replies to all ballot comments. I originally wanted to coalesce the reply to
 all positions into one email but the auto-generated header from datatracker
 makes it sound as if per-submitter replied are required. So, here we go with some
 repeated text followed by more individualized text:]

Dear Reviewer,

This is in response of your reviews of
    https://www.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-11.txt
as entered in the ballot:
    https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/ballot/

A version of this email containing replies to all IESG feedback for -11 is also in: 
    https://raw.githubusercontent.com/toerless/peering-bcp/master/11-iesg-review-reply.txt

Thank you so much for your thorough review. In response to the IESG
feedback, version -12 and -13 of the draft where posted which we hope 
will resolve the open issues.
make 2

Version -12 of the draft was just a conversion from docx generated txt to XML (previous generations
where not built from XML), this introduced formatting changes (line wraps etc.) that rfcdiff can not ignore
and that would have obfuscated actual content changes. 

Version -13 of the draft contains the text changes done in response to your
comments and discusses. The following RFC diff shows the content diffs
vs. -11 without any formatting introduced changes:

http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-12.txt&url2=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-13.txt

In summary:
   Beside the various smaller fixups from comments, the mayor rewritten/new blocks are:

   4.1.1 - bandwidth management (aka: congestion control section). 
           I didn't just want to put the magic CC sentence in but wanted to let
           readers understand what it means in the context of specifically
   6. Security considerations
      6.1.  DoS attacks (against state and bandwidth)	
      6.2.  Content security	
      6.3.  Peering encryption
      6.4.  Operational Aspects
            This is where the securing of log exchange is discussed.
   7. Privacy Considerations
      Got somewhat longer to explain because the specifics of multicast content and privacy
      are likely not that obious to non-multicast  experienced readers, and given how this
      is a BCP and i don't even think we did describe this anywhere else, it had to be
      explanatory.
   
   4.2.4.  Public Peering Routing Aspects
      text did mention non-private peerings, but i was afraid that readers would not
      understand the problematic implications, so i detailled them given how those
      peering L2 domains are still common for unicast.


Cheers
    Toerless for the Authors

====================================================================================
Kathleen Moriarty:
> 
> Thanks for your work on this draft.  I'd like to see some text clarifications on security recommendations that should not be difficult to resolve.
> 
> Section 4.4 - the exchange of supporting information could be sensitive, are there security requirements on the exchange?  I don’t see them in this section.

I thought about this a lot, and i hope the fixed up text in various sections is now better.

In the end i tried to focus the description on the model that makes this closest to
unicast, eg.: where the end-to-end application is in control and just gets network
transport information from the other parties involved, eg.: AD-2 -> AD-1. So all the
information collected via logs etc. to the extend that it is per-user is really only about the transport service
and not the payload. Something which in unicast the content source would already have.

The only privacy sensitive information directly related to multicast is really "who is watching
what content" and i created a privacy consideration section for that aspect, pls. review.

[ Side note:

  Personally i think there is a real bad amount of personal info collected by
  end-to-end applications, especially what i've seen in the past in content delivery for
  monetization strategies such as targeted advertisements and the like, but seemingly there is no
  place in the IETF where this is discussed (would have to be somehwere in ART).
  IETF only seems to obsess about protecting the sensitive information against third parties
  which is good but totally not sufficient.

  I did add the last paragraph in the privacy section to hint at this and that
  multicast could help to solve this, but alas i fear that there is no interest
  in the paycheck generating part of the IETF community to explore those options
  because that invasion on privacy is at the core of the business model of most application
  service providers.  *sigh*
  ]

> Section 6 - For the following text, it would be helpful to see some recommendations:
>    “DRM and Application Accounting, Authorization and Authentication
>    should be the responsibility of the multicast application source
>    provider and/or AD-1. AD-1 needs to work out the appropriate
>    agreements with the source provider.”
> 
> I agree with and support Alissa's Discuss and comments.  Since she already holds a discuss on this point, here are my comments:
> Section 4.3.3 clearly refers to different types of logs, some have well known methods of delivery (syslog) and authentication, but setting a minimum requirement for secure exchange including encryption and authentication should be included in this section. The protocols and options may vary between the log types.

Right.

Alas, I am not aware of any established security standards to protect equivalent operational data
exchanged for unicast between SPs. I fear i would not like the answers if i asked what
is actually done. That makes it somewhat hard to be very specific. besides, with the
advent of SDN and the slow sunset of lots of insecure NNI protocols (IPfix anybody),
the option are endless.

I've tried to describe what i hope are sufficient recommendations into te first
paragraphs of section 7.4, "operational aspects" of security considerations. Please check it out.


From nobody Fri Oct 27 17:07:51 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7672B13F61A; Fri, 27 Oct 2017 17:07:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.712
X-Spam-Level: 
X-Spam-Status: No, score=-2.712 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 xiWdkUVPqf3i; Fri, 27 Oct 2017 17:07:46 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5C4113F62C; Fri, 27 Oct 2017 17:06:28 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 83BFF58C4C3; Sat, 28 Oct 2017 02:06:24 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 6A3CEB0CFDD; Sat, 28 Oct 2017 02:06:24 +0200 (CEST)
Date: Sat, 28 Oct 2017 02:06:24 +0200
From: Toerless Eckert <tte+ietf@cs.fau.de>
To: Ben Campbell <ben@nostrum.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
Message-ID: <20171028000624.GE22613@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <150769857849.24691.13403211846518625609.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/I-bTjTIyaZI91B3wChDZZftbtrU>
Subject: Re: [MBONED] Ben Campbell's Discuss on draft-ietf-mboned-interdomain-peering-bcp-11: (with DISCUSS and COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 00:07:49 -0000

[The following text up to the individual reply comments is identical for 
 the replies to all ballot comments. I originally wanted to coalesce the reply to
 all positions into one email but the auto-generated header from datatracker
 makes it sound as if per-submitter replied are required. So, here we go with some
 repeated text followed by more individualized text:]

Dear Reviewer,

This is in response of your reviews of
    https://www.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-11.txt
as entered in the ballot:
    https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/ballot/

A version of this email containing replies to all IESG feedback for -11 is also in: 
    https://raw.githubusercontent.com/toerless/peering-bcp/master/11-iesg-review-reply.txt

Thank you so much for your thorough review. In response to the IESG
feedback, version -12 and -13 of the draft where posted which we hope 
will resolve the open issues.
make 2

Version -12 of the draft was just a conversion from docx generated txt to XML (previous generations
where not built from XML), this introduced formatting changes (line wraps etc.) that rfcdiff can not ignore
and that would have obfuscated actual content changes. 

Version -13 of the draft contains the text changes done in response to your
comments and discusses. The following RFC diff shows the content diffs
vs. -11 without any formatting introduced changes:

http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-12.txt&url2=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-13.txt

In summary:
   Beside the various smaller fixups from comments, the mayor rewritten/new blocks are:

   4.1.1 - bandwidth management (aka: congestion control section). 
           I didn't just want to put the magic CC sentence in but wanted to let
           readers understand what it means in the context of specifically
   6. Security considerations
      6.1.  DoS attacks (against state and bandwidth)	
      6.2.  Content security	
      6.3.  Peering encryption
      6.4.  Operational Aspects
            This is where the securing of log exchange is discussed.
   7. Privacy Considerations
      Got somewhat longer to explain because the specifics of multicast content and privacy
      are likely not that obious to non-multicast  experienced readers, and given how this
      is a BCP and i don't even think we did describe this anywhere else, it had to be
      explanatory.
   
   4.2.4.  Public Peering Routing Aspects
      text did mention non-private peerings, but i was afraid that readers would not
      understand the problematic implications, so i detailled them given how those
      peering L2 domains are still common for unicast.


Cheers
    Toerless for the Authors

==========================================================================================
Ben Campbell:

Thanks a lot for the thorough review!

> (This is related to Alissa's DISCUSS about logging of privacy-sensitive data. But since it's a little different, I'm entering my own DISCUSS.)
> 
>  In section 4.4 (operations) the bullet on problem notification states that AD2 will inform AD1 of, among other things, the locations of users. Is that intended to be geolocation, or network location? If the former, that's extremely sensitive information, and needs privacy guidelines.

Modified to say "Network location" (of affected EUs).

> Substantive Comments:
> 
> - I support Alissa's and Kathleen's DISCUSS positions.

Yes, see feedback to their positions.

> 
> - There seem to be quite a few implied assumptions about business models. I will call out some specifically, but I'm sure I didn't catch them all. These assumptions should either be removed or made explicit.

I did not find other assumptions beyond the ones you list below. Pls let us know explicitly what others you think exist.

> - The lists of guidelines seem to mix guidelines with observations of fact. This makes it difficult to tell which parts are "best practices" (that is, recommendations) vs which parts simply state fact.
> 
> -2: Is the assumption that the source is a service provider and the consumer is an end-user relevant? This seems to perpetuate the (often false) assumption that end users only consume content, but never produce it. It would be better to state this in the form of whatever assumptions are implied by the idea of SPs and EUs.  For example, do you assume there is a one to many relationship between SPs and EUs?

Pls. check the revised first bullet (and sub-bullet) points of the introduction. It now says that there is one AD-1 but one or more AD-2. It also limits scope to EU just receiving content, but not sourcing it. It gives a suggestion how to let end-users source content but declares the detail out of scope.

To answer your points beyond what i changed in the text:

Yes, the assumption that this is a complete end-to-end story from someone (AD-1) taking responsibility  for sourcing the content to many end-users consuming the service is relevant because it allows us to constrain the scope/size of this document. If you think we should also have text for any of the current "out of scope" areas, i would be a lot happier if we could do this in BCPbis.

> -3.2: Why does this section not rate a figure? I think it would be helpful to show the GRE tunnel as distinct from the native multicast.

Done. Please check picture and modified text referring to it.

> -3.5, paragraph after Figure 4: The large number of tunnels implies some assumptions about the cardinality between SPs and EUs that should be stated explicitly. (It would help to show this in the figures.)

Done. Put into picture: N# EU/G -> N x AMT Tunnel.

Also updated both AMT pictures to show the fact that the AMT nodes are not necessarily the same as the physcial exchange point nodes.

> - 4.3.2: The idea that that AD1 has a need to identify users in AD2 seems to be based on some implied business model assumptions. Please state those explicitly. (Or if I missed where they are stated, please point out the text.)

Not really..  I added to 4.3.2:

    <t>The reason to specifically mention the need for AD-1 to initiate
    interactions with AD-2 (and use some account for that), as opposed
    to the opposite direction is based on the recommended workflow
    initiated by customers (see <xref target="section-4.4"/>): Customer
    contacts content source (part of AD-1), when AD sees the need to propagate 
    the issue, it will interact with AD-2.</t>

I am somewhat hesitating to bring long & gory explanations why we choose
this approach, because there are so many different reasons one could cite
and it cold become quite long:

-> Its the logical workflow with unicast content service.
-> Its the workflow also in CDN, even specifically in CDNI
-> Its logical that you start diagnostics from the application side
   and only once you figure out that the issue is NOT application, but
   network, you go down to network diagnostic. And you can start that
   usually only from the application sender side.
-> You want to make operations for all the AD-2 lightweight. The idea is NOT
   for all AD-2 to become broadcasters with a virtual headend. Instead
   they just need to be involved in the transport layer and beyond that
   only into the pieces they want to.

Let me know if you feel strongly that this reasoning needs to be written down.

> -4.3.3: This states that logging is necessary for delivery. Why is that? Again, this seems to make some implicit business model assumptions. This section also needs explicit privacy considerations.

I have rewritten the beginning of 4.3.3 into 4 paragraphs to hopefully make this clearer.

- I have also added a whole privacy consideration section (8.) that discusses
  privacy hopefully exhaustively enough.

Please re-check.

> -4.4: The choice of monitoring, etc, seems to be up to the network operators to decide. Why does this document need to "expect" that? It might be helpful to describe how monitoring specific information could be useful (perhaps for troubleshooting), but the document does not go into that. 

I have changed the first two paragraphs to hopefully set the context better:

    <t> Successful delivery of applications via multicast between pairs of
       interconnecting AD's can be improved through the ability to
       exchange appropriate logs for various workflows - troubleshooting,
       accounting/billing, traffic/content optimization, market research
       and so on. Except when the log includes information about the
       IP multicast behavior in AD-2, this is not specific to IP multicast
       solutions but equally desirable in Unicast-content delivery collaboration
       collaboration across AD-1/AD-2 (e.g.: for CDN services).</t>
    
    <t> The following type of logs are well understood examples known to help support operations
       in AD-1 when provided by AD-2. This could be done as part of AD-1/AD-2 contracts:</t>

Let us know please if you insist on examples. detailing operational workflows
can add quite a bit of text to the document.
 
> The statements about compensation should be out of scope for an IETF document.

Done. See my comment to the same point raised by Alissa if you like.

> -5: Can you define, or reference a definition for, "Looking-Glass style".

Ok, that paragraph didn't quite make sense to me either. I think my
co-authors where thinking about one specific implementation option, but
it really does not matter how its done. I for once did this in the past
just via radius controlled limited authentication profiles for TACACS accounts
into routers... yada yada -> removed looking-glass style mentioning, but
refined text to hightlt mtrace/traceroute more and discuss alternative
of providing this diag via EU.

> -6: Please include a discussion of threat models. When might one choose to encrypt or not encrypt? What risks exist if you don't encrypt?

Please re-read the security section. I did do a mayor overhaul to
hopefully better identify the security issues different from unicast
and to describe the attack vectors. Both for the encryption at the
peering point and other points.

> -- : "DRM and Application Accounting, Authorization and Authentication should be the responsibility of the multicast application source"
> Why? This seems to imply some business model assumptions.

No. It is only implication of the fact that this
document only considers network layer peering, but end-to-end
transport/app layer (to make it as close as possible to existing
unicast models where the same is done). See rewritten text of security section, should
make it much clearer now, i hope.
> 
> Editorial Comments:
> 
> - General: I find the heavy use of nested bullet lists hard to read. Much of the information in the lists would be better suited to paragraph form, especially when list entries span several sentences.  Likewise, the inconsistent use of full sentences vs fragments makes it hard to read. (Maybe this is just me)

I XML'ified the document which removed a lot of surpls indentation,
but introduced more vertial white space hopefully this helps. Looks nicer to me now ;-))

In or defense, the WG did ask for structured bullet
listed format of the document to create more consistency and easier
vetting of individual statements made. 

I hope you can live through this because i am fearful of
doing more verbal changes (mayority of readers/commenters didn't complain about formatting).

> -2: Please explain (s,g) before using, or even better spell it out. You do, in fact, explain it in 4.2.3, but it's used quite a bit before you get to there.

That is about the most fundamental IP multicast term and is typically
used intentionally as a first line of defense against reader not
familiar enoigh with IP multicast to understand the text. 

But since you asked so nicely, the first instance now reads:

(S,G)s (multicast traffic flows, 
        see <xref target="section-4.2.1"/> if you are unfamiliar with IP multicast).

> -3.2, third bullet: "Ability to support only partial IP multicast deployments..."
> Does this mean "only able to support partial..." or "able to support partial..."?

   <t>Ability to support partial and/or incremental IP multicast deployments in AD-
    1 and/or AD-2: Only the path(s) between AS/BR (AD-1) and BR/EU (AD-2) need to  
    be multicast enabled. The uBRs (and paths between BR and uBR) may not support IP multicast 
    or enabling it could be seen as operationally risky on that important nodes whereas dedicated
    BR nodes for IP multicast are more acceptable. BR can be located such that 
    only parts of the domain may need to support native IP multicast (e.g.: only the
    core in AD-1 but not access).</t>

> - 3.3, figure:
> The figures that involve tunnels would be easier to understand if you visually distinguished tunnels from non-tunneled links.

Done.

> - 3.3, e: "AMT tunnels will then configure dynamically"
> s/configure/"be configured"

Ack.

> -3.4, d: " It is recommended that proper procedures are implemented such
>      that the AMT Gateway at the End User device is able to find the
>      correct AMT Relay..."
> Is that a recommendation or a requirement necessary to work at all? (Same construction appears in at least 3.5).

*sigh*. No, it's necessary, and we haven't really worked out all the good mechanisms to simpify this.

Check fixed text, explains it now better.

> -4.1: Please expand SLA on first use.

Ack

> -4.2.3: AMT Gateway: "The Gateway will reside on an End-Point - this
>         may be a Personal Computer (PC) or a Set Top Box (STB)."
> Is that meant to be exhaustive? Surely there are endpoints that do not resemble PCs or STBs.

Fixed to:

<t hangText="AMT Gateway (GW):"> The Gateway will reside on an End-Point - this
        could be any type of IP host such as a Personal Computer (PC), mobile phone, 
        Set Top Box (STB) or refrigerator. 

> -4.2.3, example procedures for gateway selection:
> The heavy use of passive voice in this section obscures the actors. (This is true to some degree throughout the document, but it seems more confusing here.)

Ok. We couldn't find a co-author willing to do a fundamental overhaul
of the text to better "activate"? the draft. Not being a native english
speaker myself, i always welcome help to improve on my english, but
i would prefer very explicit suggestions/proposed text, otherwise i may
just be replacing one bad english sentence with another one.

> -4.3.2, 2nd bullet: Please don't use "/" as shorthand for conjunctions.  (Pattern repeats throughout the rest of the draft.)

Ok, went through the whole document and tried to come up with creative alternatives to "/".

> -4.3.3, first paragraph: The first sentence is hard to parse.

Check rewritten paragraph, pls.

> -6: Please expand DRM and CDN on first mention.

Done.


From nobody Fri Oct 27 17:08:40 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C828413F45A; Fri, 27 Oct 2017 17:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.712
X-Spam-Level: 
X-Spam-Status: No, score=-2.712 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 J47TR4e6GT24; Fri, 27 Oct 2017 17:08:37 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 650F413F65C; Fri, 27 Oct 2017 17:06:51 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 792EA58C4C5; Sat, 28 Oct 2017 02:06:47 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 66A96B0CFDD; Sat, 28 Oct 2017 02:06:47 +0200 (CEST)
Date: Sat, 28 Oct 2017 02:06:47 +0200
From: Toerless Eckert <tte+ietf@cs.fau.de>
To: Adam Roach <adam@nostrum.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
Message-ID: <20171028000647.GF22613@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <150777442861.16836.8073838629509620225.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/juAUxvUvMMgkRyVKQCiggTx9xAw>
Subject: Re: [MBONED] Adam Roach's No Objection on draft-ietf-mboned-interdomain-peering-bcp-11: (with COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 00:08:40 -0000

[The following text up to the individual reply comments is identical for 
 the replies to all ballot comments. I originally wanted to coalesce the reply to
 all positions into one email but the auto-generated header from datatracker
 makes it sound as if per-submitter replied are required. So, here we go with some
 repeated text followed by more individualized text:]

Dear Reviewer,

This is in response of your reviews of
    https://www.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-11.txt
as entered in the ballot:
    https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/ballot/

A version of this email containing replies to all IESG feedback for -11 is also in: 
    https://raw.githubusercontent.com/toerless/peering-bcp/master/11-iesg-review-reply.txt

Thank you so much for your thorough review. In response to the IESG
feedback, version -12 and -13 of the draft where posted which we hope 
will resolve the open issues.
make 2

Version -12 of the draft was just a conversion from docx generated txt to XML (previous generations
where not built from XML), this introduced formatting changes (line wraps etc.) that rfcdiff can not ignore
and that would have obfuscated actual content changes. 

Version -13 of the draft contains the text changes done in response to your
comments and discusses. The following RFC diff shows the content diffs
vs. -11 without any formatting introduced changes:

http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-12.txt&url2=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-13.txt

In summary:
   Beside the various smaller fixups from comments, the mayor rewritten/new blocks are:

   4.1.1 - bandwidth management (aka: congestion control section). 
           I didn't just want to put the magic CC sentence in but wanted to let
           readers understand what it means in the context of specifically
   6. Security considerations
      6.1.  DoS attacks (against state and bandwidth)	
      6.2.  Content security	
      6.3.  Peering encryption
      6.4.  Operational Aspects
            This is where the securing of log exchange is discussed.
   7. Privacy Considerations
      Got somewhat longer to explain because the specifics of multicast content and privacy
      are likely not that obious to non-multicast  experienced readers, and given how this
      is a BCP and i don't even think we did describe this anywhere else, it had to be
      explanatory.
   
   4.2.4.  Public Peering Routing Aspects
      text did mention non-private peerings, but i was afraid that readers would not
      understand the problematic implications, so i detailled them given how those
      peering L2 domains are still common for unicast.

Cheers
    Toerless for the Authors

=====================================================================================
Adam Roach:

> I support Alissa's and Kathleen's DISCUSSes; and (as a separate concern), I support Ben's DISCUSS.
> 
> Most of the comments I noted in my review of this document have been made by other reviewers, and I will not reiterate most of them. I would, however, like to draw particular attention to Ben's comments regarding charging, billing, and settlement -- I believe these issues should either be fleshed out in significantly more detail, or removed (with a simple statement in the introduction that such issues are generally out of scope for the entire document).
> 

Those sentences where removed due to comments by other reviewers.

Your is is actually better guidance than the simple "should be out of scope" i saw
in other reviewers comments: i like the: not enough actionable information to pass bar for BCP.

We did have i think 10 years ago an attempt to standardize
multicast billing/accounting information exchange between SPs, alas those drafts never finished
because they where somewhat ill-build (on the wrong protocols). I think thats
why we as authors wanted to remind the community, but a reminder alone is not
sufficient for a BCP.

> Section 4.2.3 contains the following text:
> 
>     (Note
>      that in IPv6 there is a specific Anycast format and Anycast is
>      inherent in IPv6 routing, whereas in IPv4 Anycast is handled via
>      provisioning in the network. Details are out of scope for this
>      document.)
> 
> It would be helpful to the reader if the "out of scope" statement were accompanied by a pointer to BCP 126/RFC 4786.

Thanks. Added.

> Section 5 contains the following text:
> 
>    It is expected that multicast diagnostics will be collected
>    according to currently established practices [MDH-04].
> 
> I believe this statement makes [MDH-04] normative, as it is required to understand its contents to implement the recommendations in this BCP.

Interesting. This is my first BCP co-authoring, so its not clear to me
how references have to inherit state based on the way they are referred to in
a BCP (as opposed to being use in conjunction with a MUST/SHOULD in a standards
track RFC where i do understand this). Any pointer ?

I don't think that Dave Thaler is interested to make MDH finally an RFC after 17 years
of hiatus, although now that he's not IAB maybe he has more time ;-) And the
draft would definitely deserve it.

In any case, MDH-04 is informative reference and i weakened the sentence
referring to it to avoid IETF process mess followup:

<t>It is recommended that multicast diagnostics will be performed
   leveraging established operational practices such as documented in <xref target="MDH-04"/>. </t>


From nobody Fri Oct 27 17:09:36 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B205713F651; Fri, 27 Oct 2017 17:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.712
X-Spam-Level: 
X-Spam-Status: No, score=-2.712 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 Pmj-Ls_RAYEt; Fri, 27 Oct 2017 17:09:23 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F63F13F666; Fri, 27 Oct 2017 17:07:16 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 3C5D558C4C5; Sat, 28 Oct 2017 02:07:12 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 2DCE7B0CFDD; Sat, 28 Oct 2017 02:07:12 +0200 (CEST)
Date: Sat, 28 Oct 2017 02:07:12 +0200
From: Toerless Eckert <tte+ietf@cs.fau.de>
To: ekr@rtfm.com
Cc: The IESG <iesg@ietf.org>, draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
Message-ID: <20171028000712.GG22613@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/NcFUc6EZ1Bau1xJ2vXNDMlv2NlU>
Subject: Re: [MBONED] Eric Rescorla comments on draft-ietf-mboned-interdomain-peering-bcp-11
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 00:09:27 -0000

[Did not find any original email from eric reflecting his ballot comments,
 this one email does not have right reply header, sorry.]

[The following text up to the individual reply comments is identical for 
 the replies to all ballot comments. I originally wanted to coalesce the reply to
 all positions into one email but the auto-generated header from datatracker
 makes it sound as if per-submitter replied are required. So, here we go with some
 repeated text followed by more individualized text:]

Dear Reviewer,

This is in response of your reviews of
    https://www.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-11.txt
as entered in the ballot:
    https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/ballot/

A version of this email containing replies to all IESG feedback for -11 is also in: 
    https://raw.githubusercontent.com/toerless/peering-bcp/master/11-iesg-review-reply.txt

Thank you so much for your thorough review. In response to the IESG
feedback, version -12 and -13 of the draft where posted which we hope 
will resolve the open issues.
make 2

Version -12 of the draft was just a conversion from docx generated txt to XML (previous generations
where not built from XML), this introduced formatting changes (line wraps etc.) that rfcdiff can not ignore
and that would have obfuscated actual content changes. 

Version -13 of the draft contains the text changes done in response to your
comments and discusses. The following RFC diff shows the content diffs
vs. -11 without any formatting introduced changes:

   http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://raw.githubusercontent.com/toerless/peering-bcp/master/draft-ietf-mboned-interdomain-peering-bcp-12.txt&url2=https://raw.githubusercontent.com/toerless/peering-bcp/master/draft-ietf-mboned-interdomain-peering-bcp-13.txt

In summary:
   Beside the various smaller fixups from comments, the mayor rewritten/new blocks are:

   4.1.1 - bandwidth management (aka: congestion control section). 
           I didn't just want to put the magic CC sentence in but wanted to let
           readers understand what it means in the context of specifically
   6. Security considerations
      6.1.  DoS attacks (against state and bandwidth)	
      6.2.  Content security	
      6.3.  Peering encryption
      6.4.  Operational Aspects
            This is where the securing of log exchange is discussed.
   7. Privacy Considerations
      Got somewhat longer to explain because the specifics of multicast content and privacy
      are likely not that obious to non-multicast  experienced readers, and given how this
      is a BCP and i don't even think we did describe this anywhere else, it had to be
      explanatory.
   
   4.2.4.  Public Peering Routing Aspects
      text did mention non-private peerings, but i was afraid that readers would not
      understand the problematic implications, so i detailled them given how those
      peering L2 domains are still common for unicast.

Cheers
    Toerless for the Authors

=====================================================================================
Eric Rescorla:

> I support Kathleen's and Alissa's discusses
> 
> I'm concerned about whether the practices described adequately capture the notion of user consent to receive the data. Specifically, we're talking about sending large streams of data to people. Do the protocols in question adequately ensure that the addresses in question wish to receive the data. Specifically, the issue I am concerned with is whether I can cause you to get a large video stream. I'm filing this as a Comment rather than a Discuss because it doesn't seem like an issue for this BCP but rather for the protocols it documents.

In SSM multicast, a receiver will not receive any unwanted traffic
from any source, but only traffic from those sources that it wants to receive
traffic from. Receiver issues a so-called (S,G) membership indicating it wants
from source S the traffic for group G (think of G as the equivalent of a TCP port).

Of course, all the goodness of SSM multicast is easily invalidated by the
application on the receiver device. You know, browsers that start receiving
streaming videos into some windows on the bottom of your desktop you've long
 forgotten because some content owner tries to pushes more Ads to you...

(sorry, couldn't resist ;-)

> Please define S,G at first use.

  <t>A service provider controls one or more application sources in
        AD-1 which will send multicast IP packets for one or more
        (S,G)s (multicast traffic flows,
        see <xref target="section-4.2.1"/> if you are unfamiliar with IP multicast).


From nobody Fri Oct 27 17:12:35 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3D5313AB2F; Fri, 27 Oct 2017 17:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.712
X-Spam-Level: 
X-Spam-Status: No, score=-2.712 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 glnO-Z-ITjlH; Fri, 27 Oct 2017 17:12:26 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 795651389E6; Fri, 27 Oct 2017 17:12:26 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 8CE3158C4AE; Sat, 28 Oct 2017 02:06:08 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 7C4BFB0CFDD; Sat, 28 Oct 2017 02:06:08 +0200 (CEST)
Date: Sat, 28 Oct 2017 02:06:08 +0200
From: Toerless Eckert <tte+ietf@cs.fau.de>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
Message-ID: <20171028000608.GD22613@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <150767104932.13511.18068380159385743071.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/vqlr1ydiXNUPctanhq2lMHLsvrM>
Subject: Re: [MBONED] Spencer Dawkins' No Objection on draft-ietf-mboned-interdomain-peering-bcp-11: (with COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 00:12:29 -0000

[The following text up to the individual reply comments is identical for 
 the replies to all ballot comments. I originally wanted to coalesce the reply to
 all positions into one email but the auto-generated header from datatracker
 makes it sound as if per-submitter replied are required. So, here we go with some
 repeated text followed by more individualized text:]

Dear Reviewer,

This is in response of your reviews of
    https://www.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-11.txt
as entered in the ballot:
    https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/ballot/

A version of this email containing replies to all IESG feedback for -11 is also in: 
    https://raw.githubusercontent.com/toerless/peering-bcp/master/11-iesg-review-reply.txt

Thank you so much for your thorough review. In response to the IESG
feedback, version -12 and -13 of the draft where posted which we hope 
will resolve the open issues.
make 2

Version -12 of the draft was just a conversion from docx generated txt to XML (previous generations
where not built from XML), this introduced formatting changes (line wraps etc.) that rfcdiff can not ignore
and that would have obfuscated actual content changes. 

Version -13 of the draft contains the text changes done in response to your
comments and discusses. The following RFC diff shows the content diffs
vs. -11 without any formatting introduced changes:

http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-12.txt&url2=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-13.txt

In summary:
   Beside the various smaller fixups from comments, the mayor rewritten/new blocks are:

   4.1.1 - bandwidth management (aka: congestion control section). 
           I didn't just want to put the magic CC sentence in but wanted to let
           readers understand what it means in the context of specifically
   6. Security considerations
      6.1.  DoS attacks (against state and bandwidth)	
      6.2.  Content security	
      6.3.  Peering encryption
      6.4.  Operational Aspects
            This is where the securing of log exchange is discussed.
   7. Privacy Considerations
      Got somewhat longer to explain because the specifics of multicast content and privacy
      are likely not that obious to non-multicast  experienced readers, and given how this
      is a BCP and i don't even think we did describe this anywhere else, it had to be
      explanatory.
   
   4.2.4.  Public Peering Routing Aspects
      text did mention non-private peerings, but i was afraid that readers would not
      understand the problematic implications, so i detailled them given how those
      peering L2 domains are still common for unicast.

Cheers
    Toerless for the Authors

====================================================================================
Spencer Dawkins

> Thanks for doing this work.
> 
> I have comments, but they're all editorial.
> 
> In this text,
> 
>      o AD-1 and AD-2 are assumed to adopt compatible protocols. The
>          use of different protocols is beyond the scope of this
>          document.
> 
> "compatible protocols" isn't helpful without some context. Is this talking about "compatible multicast protocols", or complete protocol stacks from IP on up, or something else?

Changed to:

        <t>The rest of the document assumes that PIM-SSM and BGP are used across
         the peering point plus AMT and/or GRE according to scenario. The use
         of other protocols is beyond the scope of this document.</t>
> 
> I'm also noticing that the terms "should" and "recommended" appear a few times in this document. This is a BCP and doesn't reference BCP 14, which is all fine, but the wording is likely to lead readers in one direction. I wonder if it's helpful to say these things differently, so that (for instance)
> 
>          Hence, in the case of inter-domain peering, it is
>          recommended to use only SSM protocols; the setup of inter-
>          domain peering for ASM (Any-Source Multicast) is not in scope
>          for this document.
> 
> might become
> 
>          Hence, this document assumes that in the case of inter-domain 
>          peering, only SSM protocols are used; the setup of inter-
>          domain peering for ASM (Any-Source Multicast) is not in scope
>          for this document.
> 
> Nit: "out of cope"

Fixed this type, but will definitely do another spell checker after getting
approval to go through IESG, so lets not worry too much about typos.

Lower cased all MUST/SHOULD/MAY (where only few).

I think the use of the word "recommend" is in general ok. In the case
above, this was immediately preceeding the now fixed text where
i am using "assume". So i hope this solves the point you raised. 

> This text,
> 
>         packet streams will be part of a suitable
>         multicast transport protocol.
> 
> didn't parse for me - was it saying
> 
>        packet streams will be carried by a suitable
>        multicast transport protocol.

Yes, Fixed.

> In this text,
> 
>   Note that domain 2 may be an independent network domain (e.g., Tier
>    1 network operator domain). Alternately, domain 2 could also be an
>    Enterprise network domain operated by a single customer. The peering
>    point architecture and requirements may have some unique aspects
>    associated with the Enterprise case.
> 
>   The Use Cases describing various architectural configurations for
>    the multicast distribution along with associated requirements is
>    described in section 3. Unique aspects related to the Enterprise
>    network possibility will be described in this section. Section 4
>    contains a comprehensive list of pertinent information that needs to
>    be exchanged between the two domains in order to support functions
>    to enable the application transport.
> 
> it wasn't easy for me to tie "some unique aspects" in the first paragraph to "will be described in this section" in the second - if the last sentence in the first paragraph was moved to be the second paragraph, so the text was 
> 
>   Note that domain 2 may be an independent network domain (e.g., Tier
>    1 network operator domain). Alternately, domain 2 could also be an
>    Enterprise network domain operated by a single customer. 
> 
>   The Use Cases describing various architectural configurations for
>    the multicast distribution along with associated requirements is
>    described in section 3. The peering
>    point architecture and requirements may have some unique aspects
>    associated with the Enterprise case. These unique aspects will be
>    described in this section. Section 4
>    contains a comprehensive list of pertinent information that needs to
>    be exchanged between the two domains in order to support functions
>    to enable the application transport.
> 
> that would have been easier for me to follow. It's also worth mentioning that I'm guessing that "section 3" is "this section" in that text, and I'm pretty sure "this section" isn't "section 2", which is actually where the sentence appears, but it might be easier for the reader to say "will also be described in section 3".

Muchas Gracias, change applied as suggested.

Hey, how can i get more ADs that give me suggested solutions instead of raising just problems for me to solve ? 
(kidding, all input welcome)

> 
>      e. The interconnection of AD-1 and AD-2 should, at a minimum,
>         follow guidelines for traffic filtering between autonomous
>         systems [BCP38]. Filtering guidelines specific to the multicast
>         control-plane and data-plane are described in section 6.
> 
> just seems odd ("this BCP says you should do that BCP"). ISTM that if there are multicast-specific reasons to do BCP38 in addition to the usual reasons, that would be a fine thing to say here, of course.

I removed that paragraph because this applies to all scenarios anyhow,
and because BCP38 is really only a necessary ad-on consideration for
unicast. Instead section 7.1 second paragraph now explains how RPF
forwarding is part of PIM-SM/SSM and therefore provides equivalent
protection to BCP38.

> If your audience doesn't already know 
> 
>      o The GRE tunnel is often left pinned up.
> 
> (and if they don't, thank you for telling them), you might want to add a few words explaining why that's a disadvantage.

;-) I actually didn't write that point and i do not agree that it is
much of a problem in the deployment scenario, but it was a consensus
between authors to have it. IMHO the likelyhood that in this setup the
GRE tunnel is at times not used at all is fairly low. You wouldn't bother
about setting up this tunnel in the first place if it wasn't expected
to be used regularily. And its not per-user, so little state wasted even
if it is unused.

> In this text,
> 
>   The advantage for such a chained set of AMT tunnels is that the
>    total number of unicast streams across AD-2 is significantly
>    reduced, thus freeing up bandwidth. Additionally, there will be a
>    single unicast stream across the peering point instead of possibly,
>    an unacceptably large number of such streams per Use Case 3.4.
>    However, this implies that several AMT tunnels will need to be
>    dynamically configured by the various AMT Gateways based solely on
>    the (S,G) information received from the application client at the EU
>    device. A suitable mechanism for such dynamic configurations is
>    therefore critical.
> 
> is there a good reference for "suitable mechanism(s)"?

No, not really. We discussed DNS but didn't make progress with that
draft yet. I think that short term deployments can quickly solve
those problems with simple SDN style automation though and then
standardize.


From nobody Fri Oct 27 17:12:50 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C51013A296 for <mboned@ietfa.amsl.com>; Fri, 27 Oct 2017 17:12:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3] 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 FhTT5jHTEW5R for <mboned@ietfa.amsl.com>; Fri, 27 Oct 2017 17:12:29 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E839913F45A for <mboned@ietf.org>; Fri, 27 Oct 2017 17:12:28 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 6EC5658C4C5 for <mboned@ietf.org>; Sat, 28 Oct 2017 02:12:25 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 3FB3EB0CFE5; Sat, 28 Oct 2017 02:12:25 +0200 (CEST)
Date: Sat, 28 Oct 2017 02:12:25 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: mboned@ietf.org
Message-ID: <20171028001225.GH22613@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/lFGQf5zRAgTCAgQylgCAIDN1LGE>
Subject: [MBONED] : pre-RFC5378 work ? draft-ietf-mboned-interdomain-peering-bcp
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 00:12:30 -0000

Alissa noted that subject draft had this quirky so-called pre-RFC5378 header:

> This document may contain material from IETF Documents or IETF
> Contributions published or made publicly available before November
> 10, 2008.  The person(s) controlling the copyright in some of this
> material may not have granted the IETF Trust the right to allow
> modifications of such material outside the IETF Standards Process.
> Without obtaining an adequate license from the person(s) controlling
> the copyright in such materials, this document may not be modified
> outside the IETF Standards Process, and derivative works of it may
> not be created outside the IETF Standards Process, except to format
> it for publication as an RFC or to translate it into languages other
> than English.

I tried to educate myself where when and how it might make sense specifically
on this draft but came up empty. So i removed it for just posted -13 but promised
to as the WG (this mail).

Anybody have any insight why this could have been in the draft since -00 except
for "bad template" ?

Anybody have a real example where in IP multicast drafts it was ever used
for a necessary reason ?

Curious minds..

Cheers
    Toerless


From nobody Fri Oct 27 17:14:09 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0E8113F487 for <mboned@ietfa.amsl.com>; Fri, 27 Oct 2017 17:14:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 9KTh-uSWQeDM for <mboned@ietfa.amsl.com>; Fri, 27 Oct 2017 17:14:05 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 595F313AB2F for <mboned@ietf.org>; Fri, 27 Oct 2017 17:13:49 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 878A358C4AE; Sat, 28 Oct 2017 02:13:45 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 78FEDB0CFE5; Sat, 28 Oct 2017 02:13:45 +0200 (CEST)
Date: Sat, 28 Oct 2017 02:13:45 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Leonard Giuliano <lenny@juniper.net>
Cc: MBONED WG <mboned@ietf.org>
Message-ID: <20171028001345.GI22613@faui40p.informatik.uni-erlangen.de>
References: <alpine.DEB.2.02.1710262342140.21903@svl-jtac-lnx02.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1710262342140.21903@svl-jtac-lnx02.juniper.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/ZLt8Gtw4eWY1WNqUUnDTz1BFtKs>
Subject: Re: [MBONED] call for MBONED agenda items in Singapore
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 00:14:07 -0000

Sure, count me in for a slot on the peering bcp update. Seems our
east coast co-authors didn't really want to take the 24 hour flight (wonder why..;-),
so it's on me.

Cheers
    Toerless

On Thu, Oct 26, 2017 at 11:43:26PM -0700, Leonard Giuliano wrote:
> 
> We are currently scheduled for 9:30AM on Tues, once again meeting
> jointly with PIM WG. If you have something you'd like to present,
> please let the chairs know what the draft name is and how much time
> you would like.
> 
> 
> -Lenny and Greg
> 
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


From nobody Fri Oct 27 18:06:24 2017
Return-Path: <william.atwood@concordia.ca>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7355F139435 for <mboned@ietfa.amsl.com>; Fri, 27 Oct 2017 18:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.534
X-Spam-Level: 
X-Spam-Status: No, score=-3.534 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, 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 51n8LoyTG0aE for <mboned@ietfa.amsl.com>; Fri, 27 Oct 2017 18:06:20 -0700 (PDT)
Received: from oldperseverance.encs.concordia.ca (oldperseverance.encs.concordia.ca [132.205.96.92]) by ietfa.amsl.com (Postfix) with ESMTP id 4568213F48E for <mboned@ietf.org>; Fri, 27 Oct 2017 18:06:18 -0700 (PDT)
Received: from [IPv6:::1] (bill@poise.encs.concordia.ca [132.205.2.209]) by oldperseverance.encs.concordia.ca (envelope-from william.atwood@concordia.ca) (8.13.7/8.13.7) with ESMTP id v9S16GVo028973 for <mboned@ietf.org>; Fri, 27 Oct 2017 21:06:17 -0400
To: mboned@ietf.org
References: <20171028001225.GH22613@faui40p.informatik.uni-erlangen.de>
From: William Atwood <william.atwood@concordia.ca>
Organization: Concordia University, Montreal
Message-ID: <74e69e9f-1393-71e9-23b4-def1bd5287a6@concordia.ca>
Date: Fri, 27 Oct 2017 21:06:19 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <20171028001225.GH22613@faui40p.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Scanned-By: MIMEDefang 2.58 on oldperseverance.encs.concordia.ca at 2017-10-27 21:06:17 EDT
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/trWzuYdXrAmvHFs3BT3rznAa0v0>
Subject: Re: [MBONED] : pre-RFC5378 work ? draft-ietf-mboned-interdomain-peering-bcp
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 01:06:22 -0000

Given that the draft was created using a .docx template, I suspect that
"ancient template" is the correct root cause.

  Bill


On 27/10/2017 8:12 PM, Toerless Eckert wrote:
> Alissa noted that subject draft had this quirky so-called pre-RFC5378 header:
>
>> This document may contain material from IETF Documents or IETF
>> Contributions published or made publicly available before November
>> 10, 2008.  The person(s) controlling the copyright in some of this
>> material may not have granted the IETF Trust the right to allow
>> modifications of such material outside the IETF Standards Process.
>> Without obtaining an adequate license from the person(s) controlling
>> the copyright in such materials, this document may not be modified
>> outside the IETF Standards Process, and derivative works of it may
>> not be created outside the IETF Standards Process, except to format
>> it for publication as an RFC or to translate it into languages other
>> than English.
> I tried to educate myself where when and how it might make sense specifically
> on this draft but came up empty. So i removed it for just posted -13 but promised
> to as the WG (this mail).
>
> Anybody have any insight why this could have been in the draft since -00 except
> for "bad template" ?
>
> Anybody have a real example where in IP multicast drafts it was ever used
> for a necessary reason ?
>
> Curious minds..
>
> Cheers
>     Toerless
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

-- 

Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
Department of Computer Science
   and Software Engineering
Concordia University EV 3.185     email:william.atwood@concordia.ca
1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
Montreal, Quebec Canada H3G 1M8


From nobody Fri Oct 27 21:09:10 2017
Return-Path: <adam@nostrum.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD9CB13F662; Fri, 27 Oct 2017 21:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, 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 MwM9V63u1HOg; Fri, 27 Oct 2017 21:09:02 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 5F5BC13F659; Fri, 27 Oct 2017 21:09:02 -0700 (PDT)
Received: from Orochi.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v9S48rcg012593 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 27 Oct 2017 23:08:54 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Orochi.local
To: Toerless Eckert <tte+ietf@cs.fau.de>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
References: <20171028000647.GF22613@faui40p.informatik.uni-erlangen.de>
From: Adam Roach <adam@nostrum.com>
Message-ID: <7f4a0d98-5821-3c41-4268-b7a8990545fc@nostrum.com>
Date: Fri, 27 Oct 2017 23:08:48 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <20171028000647.GF22613@faui40p.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/ChL4OJ3oyGWFZnSYaYMtadpHEm0>
Subject: Re: [MBONED] Adam Roach's No Objection on draft-ietf-mboned-interdomain-peering-bcp-11: (with COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 04:09:04 -0000

On 10/27/17 19:06, Toerless Eckert wrote:
> Interesting. This is my first BCP co-authoring, so its not clear to me
> how references have to inherit state based on the way they are referred to in
> a BCP (as opposed to being use in conjunction with a MUST/SHOULD in a standards
> track RFC where i do understand this). Any pointer ?


The general IESG guidance on normative references is here:

https://www.ietf.org/iesg/statement/normative-informative.html

Relevant to the original text, the following excerpts apply: "Normative 
references specify documents that must be read to understand or 
implement the technology in the new RFC, or whose technology must be 
present for the technology in the new RFC to work" and "Even references 
that are relevant only for optional features must be classified as 
normative if they meet the above conditions for normative references."

Your proposed shift to make [MDH-04] an example rather than an 
expectation makes it clear that it is only informative. Thanks.

/a


From nobody Sun Oct 29 20:51:18 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACDC713F56E; Sun, 29 Oct 2017 20:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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=gmail.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 4HRnLW_gbRHs; Sun, 29 Oct 2017 20:50:57 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (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 3EE9313FA63; Sun, 29 Oct 2017 20:50:57 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id k3so10382133ywk.8; Sun, 29 Oct 2017 20:50:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9pkxU1JwYScJ1aa74G/KbKLDHewhRCde6KxVQR5M3oM=; b=cUwvc2nwBhT+QbVBjJItC4zsEcudH3FGikFJl3ZKAdq/yY6Rw/LG5YvPgD3S9JrLOX P9koXYbAknRCXixZqRuhYd3L+Hy/CMzuXR/JnWCD5/dVIJR8Ivqnh1uqxNifM/lBuVVD EadKxpDFXfmkgJd1uVqIBxtxSkcxHqZ9WUD3c6Vx21ycmDS9sbs4NU+HjBuNd+Dee9RY /bl01Y9qk1JhQM8AaM7RzSSMJYbE/VnIwQP27xB7DQQGmi+rl78VCJJ+5K1xgMcqkywf RY2sYlCgluKKKtj61a96Off4uKdS8D74UuDy5OEm1p60vtluHgf4RWZtprFn2VgbQZXN 6L+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=9pkxU1JwYScJ1aa74G/KbKLDHewhRCde6KxVQR5M3oM=; b=f4iicdLoBwHQePzjToT7JNyNnsx8OrNdtXsKSZtMeAfkJb7uS4+PnoZLXs2qBssyWa j8aIzcG6jMtWbIKlrfWulYe35f58U9bkURzVTuGQow+RvrHf4yHPCJZHccaqWIjMZnuR ilvbqXQ3Je34uPoopG9ltrc9duolJaBatBQrreun/CCWJe7KJBav9TdK0G7+IcpulL8Q cWev21cBzmOu7aos/eDPaHZDpvjHeeNjSKZONyFoDsctw5Gi0EtO5EK1QyWQRSWpIYF0 TGyrPyvQiaHNHZSkuR1gRspYKtg7ZOQqG8oFlPxGfpANiCKTOqZH2b+EuQlqECyMMqw5 YHLA==
X-Gm-Message-State: AMCzsaUWqGWrXMbOZfmeMHUpRSzEG1bxj6GYZP8AbhvN3eHliHFXgagA qQ65L0v595KNW/e8Rhjj0D2GicdvuwxnL0R4tWA=
X-Google-Smtp-Source: ABhQp+R3ZqseEeYbOWq2rg3OAN6UnErKyXeU2dnDUEDMlaB7llkNMVudr0tktmVpmBvEjYd3gpURKeV75V5oBzg3/C8=
X-Received: by 10.37.41.4 with SMTP id p4mr1866846ybp.354.1509335456121; Sun, 29 Oct 2017 20:50:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.162.204 with HTTP; Sun, 29 Oct 2017 20:50:55 -0700 (PDT)
In-Reply-To: <20171028000608.GD22613@faui40p.informatik.uni-erlangen.de>
References: <150767104932.13511.18068380159385743071.idtracker@ietfa.amsl.com> <20171028000608.GD22613@faui40p.informatik.uni-erlangen.de>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 29 Oct 2017 22:50:55 -0500
Message-ID: <CAKKJt-e-Snqc1Rtkz0Rpj+nRNdt4zpzu5K9i+VEOtjmhjrv+bQ@mail.gmail.com>
To: Toerless Eckert <tte+ietf@cs.fau.de>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mboned-interdomain-peering-bcp@ietf.org,  mboned-chairs@ietf.org, Tim Chown <tim.chown@jisc.ac.uk>, mboned@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c14dafeb588dc055cbb8b0f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/gKS3UP3c2AjnLYXkeDrs8PquP8s>
Subject: Re: [MBONED] Spencer Dawkins' No Objection on draft-ietf-mboned-interdomain-peering-bcp-11: (with COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 03:51:12 -0000

--94eb2c14dafeb588dc055cbb8b0f
Content-Type: text/plain; charset="UTF-8"

Hi, Toerless,

Tl;dr - thanks for working through my comments. I'm good.

Spencer

On Fri, Oct 27, 2017 at 7:06 PM, Toerless Eckert <tte+ietf@cs.fau.de> wrote:

> [The following text up to the individual reply comments is identical for
>  the replies to all ballot comments. I originally wanted to coalesce the
> reply to
>  all positions into one email but the auto-generated header from
> datatracker
>  makes it sound as if per-submitter replied are required. So, here we go
> with some
>  repeated text followed by more individualized text:]
>
> Dear Reviewer,
>
> This is in response of your reviews of
>     https://www.ietf.org/id/draft-ietf-mboned-interdomain-
> peering-bcp-11.txt
> as entered in the ballot:
>     https://datatracker.ietf.org/doc/draft-ietf-mboned-
> interdomain-peering-bcp/ballot/
>
> A version of this email containing replies to all IESG feedback for -11 is
> also in:
>     https://raw.githubusercontent.com/toerless/peering-bcp/
> master/11-iesg-review-reply.txt
>
> Thank you so much for your thorough review. In response to the IESG
> feedback, version -12 and -13 of the draft where posted which we hope
> will resolve the open issues.
> make 2
>
> Version -12 of the draft was just a conversion from docx generated txt to
> XML (previous generations
> where not built from XML), this introduced formatting changes (line wraps
> etc.) that rfcdiff can not ignore
> and that would have obfuscated actual content changes.
>
> Version -13 of the draft contains the text changes done in response to your
> comments and discusses. The following RFC diff shows the content diffs
> vs. -11 without any formatting introduced changes:
>
> http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=
> https://tools.ietf.org/id/draft-ietf-mboned-interdomain-
> peering-bcp-12.txt&url2=https://tools.ietf.org/id/draft-
> ietf-mboned-interdomain-peering-bcp-13.txt
>
> In summary:
>    Beside the various smaller fixups from comments, the mayor
> rewritten/new blocks are:
>
>    4.1.1 - bandwidth management (aka: congestion control section).
>            I didn't just want to put the magic CC sentence in but wanted
> to let
>            readers understand what it means in the context of specifically
>    6. Security considerations
>       6.1.  DoS attacks (against state and bandwidth)
>       6.2.  Content security
>       6.3.  Peering encryption
>       6.4.  Operational Aspects
>             This is where the securing of log exchange is discussed.
>    7. Privacy Considerations
>       Got somewhat longer to explain because the specifics of multicast
> content and privacy
>       are likely not that obious to non-multicast  experienced readers,
> and given how this
>       is a BCP and i don't even think we did describe this anywhere else,
> it had to be
>       explanatory.
>
>    4.2.4.  Public Peering Routing Aspects
>       text did mention non-private peerings, but i was afraid that readers
> would not
>       understand the problematic implications, so i detailled them given
> how those
>       peering L2 domains are still common for unicast.
>
> Cheers
>     Toerless for the Authors
>
> ============================================================
> ========================
> Spencer Dawkins
>
> > Thanks for doing this work.
> >
> > I have comments, but they're all editorial.
> >
> > In this text,
> >
> >      o AD-1 and AD-2 are assumed to adopt compatible protocols. The
> >          use of different protocols is beyond the scope of this
> >          document.
> >
> > "compatible protocols" isn't helpful without some context. Is this
> talking about "compatible multicast protocols", or complete protocol stacks
> from IP on up, or something else?
>
> Changed to:
>
>         <t>The rest of the document assumes that PIM-SSM and BGP are used
> across
>          the peering point plus AMT and/or GRE according to scenario. The
> use
>          of other protocols is beyond the scope of this document.</t>
> >
> > I'm also noticing that the terms "should" and "recommended" appear a few
> times in this document. This is a BCP and doesn't reference BCP 14, which
> is all fine, but the wording is likely to lead readers in one direction. I
> wonder if it's helpful to say these things differently, so that (for
> instance)
> >
> >          Hence, in the case of inter-domain peering, it is
> >          recommended to use only SSM protocols; the setup of inter-
> >          domain peering for ASM (Any-Source Multicast) is not in scope
> >          for this document.
> >
> > might become
> >
> >          Hence, this document assumes that in the case of inter-domain
> >          peering, only SSM protocols are used; the setup of inter-
> >          domain peering for ASM (Any-Source Multicast) is not in scope
> >          for this document.
> >
> > Nit: "out of cope"
>
> Fixed this type, but will definitely do another spell checker after getting
> approval to go through IESG, so lets not worry too much about typos.
>
> Lower cased all MUST/SHOULD/MAY (where only few).
>
> I think the use of the word "recommend" is in general ok. In the case
> above, this was immediately preceeding the now fixed text where
> i am using "assume". So i hope this solves the point you raised.
>
> > This text,
> >
> >         packet streams will be part of a suitable
> >         multicast transport protocol.
> >
> > didn't parse for me - was it saying
> >
> >        packet streams will be carried by a suitable
> >        multicast transport protocol.
>
> Yes, Fixed.
>
> > In this text,
> >
> >   Note that domain 2 may be an independent network domain (e.g., Tier
> >    1 network operator domain). Alternately, domain 2 could also be an
> >    Enterprise network domain operated by a single customer. The peering
> >    point architecture and requirements may have some unique aspects
> >    associated with the Enterprise case.
> >
> >   The Use Cases describing various architectural configurations for
> >    the multicast distribution along with associated requirements is
> >    described in section 3. Unique aspects related to the Enterprise
> >    network possibility will be described in this section. Section 4
> >    contains a comprehensive list of pertinent information that needs to
> >    be exchanged between the two domains in order to support functions
> >    to enable the application transport.
> >
> > it wasn't easy for me to tie "some unique aspects" in the first
> paragraph to "will be described in this section" in the second - if the
> last sentence in the first paragraph was moved to be the second paragraph,
> so the text was
> >
> >   Note that domain 2 may be an independent network domain (e.g., Tier
> >    1 network operator domain). Alternately, domain 2 could also be an
> >    Enterprise network domain operated by a single customer.
> >
> >   The Use Cases describing various architectural configurations for
> >    the multicast distribution along with associated requirements is
> >    described in section 3. The peering
> >    point architecture and requirements may have some unique aspects
> >    associated with the Enterprise case. These unique aspects will be
> >    described in this section. Section 4
> >    contains a comprehensive list of pertinent information that needs to
> >    be exchanged between the two domains in order to support functions
> >    to enable the application transport.
> >
> > that would have been easier for me to follow. It's also worth mentioning
> that I'm guessing that "section 3" is "this section" in that text, and I'm
> pretty sure "this section" isn't "section 2", which is actually where the
> sentence appears, but it might be easier for the reader to say "will also
> be described in section 3".
>
> Muchas Gracias, change applied as suggested.
>
> Hey, how can i get more ADs that give me suggested solutions instead of
> raising just problems for me to solve ?
> (kidding, all input welcome)
>
> >
> >      e. The interconnection of AD-1 and AD-2 should, at a minimum,
> >         follow guidelines for traffic filtering between autonomous
> >         systems [BCP38]. Filtering guidelines specific to the multicast
> >         control-plane and data-plane are described in section 6.
> >
> > just seems odd ("this BCP says you should do that BCP"). ISTM that if
> there are multicast-specific reasons to do BCP38 in addition to the usual
> reasons, that would be a fine thing to say here, of course.
>
> I removed that paragraph because this applies to all scenarios anyhow,
> and because BCP38 is really only a necessary ad-on consideration for
> unicast. Instead section 7.1 second paragraph now explains how RPF
> forwarding is part of PIM-SM/SSM and therefore provides equivalent
> protection to BCP38.
>
> > If your audience doesn't already know
> >
> >      o The GRE tunnel is often left pinned up.
> >
> > (and if they don't, thank you for telling them), you might want to add a
> few words explaining why that's a disadvantage.
>
> ;-) I actually didn't write that point and i do not agree that it is
> much of a problem in the deployment scenario, but it was a consensus
> between authors to have it. IMHO the likelyhood that in this setup the
> GRE tunnel is at times not used at all is fairly low. You wouldn't bother
> about setting up this tunnel in the first place if it wasn't expected
> to be used regularily. And its not per-user, so little state wasted even
> if it is unused.
>
> > In this text,
> >
> >   The advantage for such a chained set of AMT tunnels is that the
> >    total number of unicast streams across AD-2 is significantly
> >    reduced, thus freeing up bandwidth. Additionally, there will be a
> >    single unicast stream across the peering point instead of possibly,
> >    an unacceptably large number of such streams per Use Case 3.4.
> >    However, this implies that several AMT tunnels will need to be
> >    dynamically configured by the various AMT Gateways based solely on
> >    the (S,G) information received from the application client at the EU
> >    device. A suitable mechanism for such dynamic configurations is
> >    therefore critical.
> >
> > is there a good reference for "suitable mechanism(s)"?
>
> No, not really. We discussed DNS but didn't make progress with that
> draft yet. I think that short term deployments can quickly solve
> those problems with simple SDN style automation though and then
> standardize.
>
>

--94eb2c14dafeb588dc055cbb8b0f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Toerless,<div><br></div><div>Tl;dr - thanks for workin=
g through my comments. I&#39;m good.</div><div><br></div><div>Spencer</div>=
</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Oct=
 27, 2017 at 7:06 PM, Toerless Eckert <span dir=3D"ltr">&lt;<a href=3D"mail=
to:tte+ietf@cs.fau.de" target=3D"_blank">tte+ietf@cs.fau.de</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">[The following text up to the indi=
vidual reply comments is identical for<br>
=C2=A0the replies to all ballot comments. I originally wanted to coalesce t=
he reply to<br>
=C2=A0all positions into one email but the auto-generated header from datat=
racker<br>
=C2=A0makes it sound as if per-submitter replied are required. So, here we =
go with some<br>
=C2=A0repeated text followed by more individualized text:]<br>
<br>
Dear Reviewer,<br>
<br>
This is in response of your reviews of<br>
=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/id/draft-ietf-mboned-interdom=
ain-peering-bcp-11.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ie=
tf.org/id/draft-<wbr>ietf-mboned-interdomain-<wbr>peering-bcp-11.txt</a><br=
>
as entered in the ballot:<br>
=C2=A0 =C2=A0 <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mboned=
-interdomain-peering-bcp/ballot/" rel=3D"noreferrer" target=3D"_blank">http=
s://datatracker.ietf.org/<wbr>doc/draft-ietf-mboned-<wbr>interdomain-peerin=
g-bcp/<wbr>ballot/</a><br>
<br>
A version of this email containing replies to all IESG feedback for -11 is =
also in:<br>
=C2=A0 =C2=A0 <a href=3D"https://raw.githubusercontent.com/toerless/peering=
-bcp/master/11-iesg-review-reply.txt" rel=3D"noreferrer" target=3D"_blank">=
https://raw.githubusercontent.<wbr>com/toerless/peering-bcp/<wbr>master/11-=
iesg-review-reply.<wbr>txt</a><br>
<br>
Thank you so much for your thorough review. In response to the IESG<br>
feedback, version -12 and -13 of the draft where posted which we hope<br>
will resolve the open issues.<br>
make 2<br>
<br>
Version -12 of the draft was just a conversion from docx generated txt to X=
ML (previous generations<br>
where not built from XML), this introduced formatting changes (line wraps e=
tc.) that rfcdiff can not ignore<br>
and that would have obfuscated actual content changes.<br>
<br>
Version -13 of the draft contains the text changes done in response to your=
<br>
comments and discusses. The following RFC diff shows the content diffs<br>
vs. -11 without any formatting introduced changes:<br>
<br>
<a href=3D"http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Dhttps://=
tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-12.txt&amp;url2=
=3Dhttps://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-13.t=
xt" rel=3D"noreferrer" target=3D"_blank">http://tools.ietf.org/tools/<wbr>r=
fcdiff/rfcdiff.pyht?url1=3D<wbr>https://tools.ietf.org/id/<wbr>draft-ietf-m=
boned-interdomain-<wbr>peering-bcp-12.txt&amp;url2=3Dhttps:<wbr>//tools.iet=
f.org/id/draft-<wbr>ietf-mboned-interdomain-<wbr>peering-bcp-13.txt</a><br>
<br>
In summary:<br>
=C2=A0 =C2=A0Beside the various smaller fixups from comments, the mayor rew=
ritten/new blocks are:<br>
<br>
=C2=A0 =C2=A04.1.1 - bandwidth management (aka: congestion control section)=
.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I didn&#39;t just want to put the =
magic CC sentence in but wanted to let<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0readers understand what it means i=
n the context of specifically<br>
=C2=A0 =C2=A06. Security considerations<br>
=C2=A0 =C2=A0 =C2=A0 6.1.=C2=A0 DoS attacks (against state and bandwidth)<b=
r>
=C2=A0 =C2=A0 =C2=A0 6.2.=C2=A0 Content security<br>
=C2=A0 =C2=A0 =C2=A0 6.3.=C2=A0 Peering encryption<br>
=C2=A0 =C2=A0 =C2=A0 6.4.=C2=A0 Operational Aspects<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 This is where the securing of log=
 exchange is discussed.<br>
=C2=A0 =C2=A07. Privacy Considerations<br>
=C2=A0 =C2=A0 =C2=A0 Got somewhat longer to explain because the specifics o=
f multicast content and privacy<br>
=C2=A0 =C2=A0 =C2=A0 are likely not that obious to non-multicast=C2=A0 expe=
rienced readers, and given how this<br>
=C2=A0 =C2=A0 =C2=A0 is a BCP and i don&#39;t even think we did describe th=
is anywhere else, it had to be<br>
=C2=A0 =C2=A0 =C2=A0 explanatory.<br>
<br>
=C2=A0 =C2=A04.2.4.=C2=A0 Public Peering Routing Aspects<br>
=C2=A0 =C2=A0 =C2=A0 text did mention non-private peerings, but i was afrai=
d that readers would not<br>
=C2=A0 =C2=A0 =C2=A0 understand the problematic implications, so i detaille=
d them given how those<br>
=C2=A0 =C2=A0 =C2=A0 peering L2 domains are still common for unicast.<br>
<br>
Cheers<br>
=C2=A0 =C2=A0 Toerless for the Authors<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Spencer Dawkins<br>
<span class=3D""><br>
&gt; Thanks for doing this work.<br>
&gt;<br>
&gt; I have comments, but they&#39;re all editorial.<br>
&gt;<br>
&gt; In this text,<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 o AD-1 and AD-2 are assumed to adopt compatible pr=
otocols. The<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 use of different protocols is beyond=
 the scope of this<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 document.<br>
&gt;<br>
&gt; &quot;compatible protocols&quot; isn&#39;t helpful without some contex=
t. Is this talking about &quot;compatible multicast protocols&quot;, or com=
plete protocol stacks from IP on up, or something else?<br>
<br>
</span>Changed to:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;t&gt;The rest of the document assumes that =
PIM-SSM and BGP are used across<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0the peering point plus AMT and/or GRE acc=
ording to scenario. The use<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0of other protocols is beyond the scope of=
 this document.&lt;/t&gt;<br>
<span class=3D"">&gt;<br>
&gt; I&#39;m also noticing that the terms &quot;should&quot; and &quot;reco=
mmended&quot; appear a few times in this document. This is a BCP and doesn&=
#39;t reference BCP 14, which is all fine, but the wording is likely to lea=
d readers in one direction. I wonder if it&#39;s helpful to say these thing=
s differently, so that (for instance)<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Hence, in the case of inter-domain p=
eering, it is<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 recommended to use only SSM protocol=
s; the setup of inter-<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 domain peering for ASM (Any-Source M=
ulticast) is not in scope<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 for this document.<br>
&gt;<br>
&gt; might become<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Hence, this document assumes that in=
 the case of inter-domain<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 peering, only SSM protocols are used=
; the setup of inter-<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 domain peering for ASM (Any-Source M=
ulticast) is not in scope<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 for this document.<br>
&gt;<br>
&gt; Nit: &quot;out of cope&quot;<br>
<br>
</span>Fixed this type, but will definitely do another spell checker after =
getting<br>
approval to go through IESG, so lets not worry too much about typos.<br>
<br>
Lower cased all MUST/SHOULD/MAY (where only few).<br>
<br>
I think the use of the word &quot;recommend&quot; is in general ok. In the =
case<br>
above, this was immediately preceeding the now fixed text where<br>
i am using &quot;assume&quot;. So i hope this solves the point you raised.<=
br>
<span class=3D""><br>
&gt; This text,<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0packet streams will be part of a suit=
able<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0multicast transport protocol.<br>
&gt;<br>
&gt; didn&#39;t parse for me - was it saying<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 packet streams will be carried by a suitabl=
e<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 multicast transport protocol.<br>
<br>
</span>Yes, Fixed.<br>
<div><div class=3D"h5"><br>
&gt; In this text,<br>
&gt;<br>
&gt;=C2=A0 =C2=A0Note that domain 2 may be an independent network domain (e=
.g., Tier<br>
&gt;=C2=A0 =C2=A0 1 network operator domain). Alternately, domain 2 could a=
lso be an<br>
&gt;=C2=A0 =C2=A0 Enterprise network domain operated by a single customer. =
The peering<br>
&gt;=C2=A0 =C2=A0 point architecture and requirements may have some unique =
aspects<br>
&gt;=C2=A0 =C2=A0 associated with the Enterprise case.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0The Use Cases describing various architectural configurati=
ons for<br>
&gt;=C2=A0 =C2=A0 the multicast distribution along with associated requirem=
ents is<br>
&gt;=C2=A0 =C2=A0 described in section 3. Unique aspects related to the Ent=
erprise<br>
&gt;=C2=A0 =C2=A0 network possibility will be described in this section. Se=
ction 4<br>
&gt;=C2=A0 =C2=A0 contains a comprehensive list of pertinent information th=
at needs to<br>
&gt;=C2=A0 =C2=A0 be exchanged between the two domains in order to support =
functions<br>
&gt;=C2=A0 =C2=A0 to enable the application transport.<br>
&gt;<br>
&gt; it wasn&#39;t easy for me to tie &quot;some unique aspects&quot; in th=
e first paragraph to &quot;will be described in this section&quot; in the s=
econd - if the last sentence in the first paragraph was moved to be the sec=
ond paragraph, so the text was<br>
&gt;<br>
&gt;=C2=A0 =C2=A0Note that domain 2 may be an independent network domain (e=
.g., Tier<br>
&gt;=C2=A0 =C2=A0 1 network operator domain). Alternately, domain 2 could a=
lso be an<br>
&gt;=C2=A0 =C2=A0 Enterprise network domain operated by a single customer.<=
br>
&gt;<br>
&gt;=C2=A0 =C2=A0The Use Cases describing various architectural configurati=
ons for<br>
&gt;=C2=A0 =C2=A0 the multicast distribution along with associated requirem=
ents is<br>
&gt;=C2=A0 =C2=A0 described in section 3. The peering<br>
&gt;=C2=A0 =C2=A0 point architecture and requirements may have some unique =
aspects<br>
&gt;=C2=A0 =C2=A0 associated with the Enterprise case. These unique aspects=
 will be<br>
&gt;=C2=A0 =C2=A0 described in this section. Section 4<br>
&gt;=C2=A0 =C2=A0 contains a comprehensive list of pertinent information th=
at needs to<br>
&gt;=C2=A0 =C2=A0 be exchanged between the two domains in order to support =
functions<br>
&gt;=C2=A0 =C2=A0 to enable the application transport.<br>
&gt;<br>
&gt; that would have been easier for me to follow. It&#39;s also worth ment=
ioning that I&#39;m guessing that &quot;section 3&quot; is &quot;this secti=
on&quot; in that text, and I&#39;m pretty sure &quot;this section&quot; isn=
&#39;t &quot;section 2&quot;, which is actually where the sentence appears,=
 but it might be easier for the reader to say &quot;will also be described =
in section 3&quot;.<br>
<br>
</div></div>Muchas Gracias, change applied as suggested.<br>
<br>
Hey, how can i get more ADs that give me suggested solutions instead of rai=
sing just problems for me to solve ?<br>
(kidding, all input welcome)<br>
<span class=3D""><br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 e. The interconnection of AD-1 and AD-2 should, at=
 a minimum,<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0follow guidelines for traffic filteri=
ng between autonomous<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0systems [BCP38]. Filtering guidelines=
 specific to the multicast<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0control-plane and data-plane are desc=
ribed in section 6.<br>
&gt;<br>
&gt; just seems odd (&quot;this BCP says you should do that BCP&quot;). IST=
M that if there are multicast-specific reasons to do BCP38 in addition to t=
he usual reasons, that would be a fine thing to say here, of course.<br>
<br>
</span>I removed that paragraph because this applies to all scenarios anyho=
w,<br>
and because BCP38 is really only a necessary ad-on consideration for<br>
unicast. Instead section 7.1 second paragraph now explains how RPF<br>
forwarding is part of PIM-SM/SSM and therefore provides equivalent<br>
protection to BCP38.<br>
<span class=3D""><br>
&gt; If your audience doesn&#39;t already know<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 o The GRE tunnel is often left pinned up.<br>
&gt;<br>
&gt; (and if they don&#39;t, thank you for telling them), you might want to=
 add a few words explaining why that&#39;s a disadvantage.<br>
<br>
</span>;-) I actually didn&#39;t write that point and i do not agree that i=
t is<br>
much of a problem in the deployment scenario, but it was a consensus<br>
between authors to have it. IMHO the likelyhood that in this setup the<br>
GRE tunnel is at times not used at all is fairly low. You wouldn&#39;t both=
er<br>
about setting up this tunnel in the first place if it wasn&#39;t expected<b=
r>
to be used regularily. And its not per-user, so little state wasted even<br=
>
if it is unused.<br>
<span class=3D""><br>
&gt; In this text,<br>
&gt;<br>
&gt;=C2=A0 =C2=A0The advantage for such a chained set of AMT tunnels is tha=
t the<br>
&gt;=C2=A0 =C2=A0 total number of unicast streams across AD-2 is significan=
tly<br>
&gt;=C2=A0 =C2=A0 reduced, thus freeing up bandwidth. Additionally, there w=
ill be a<br>
&gt;=C2=A0 =C2=A0 single unicast stream across the peering point instead of=
 possibly,<br>
&gt;=C2=A0 =C2=A0 an unacceptably large number of such streams per Use Case=
 3.4.<br>
&gt;=C2=A0 =C2=A0 However, this implies that several AMT tunnels will need =
to be<br>
&gt;=C2=A0 =C2=A0 dynamically configured by the various AMT Gateways based =
solely on<br>
&gt;=C2=A0 =C2=A0 the (S,G) information received from the application clien=
t at the EU<br>
&gt;=C2=A0 =C2=A0 device. A suitable mechanism for such dynamic configurati=
ons is<br>
&gt;=C2=A0 =C2=A0 therefore critical.<br>
&gt;<br>
&gt; is there a good reference for &quot;suitable mechanism(s)&quot;?<br>
<br>
</span>No, not really. We discussed DNS but didn&#39;t make progress with t=
hat<br>
draft yet. I think that short term deployments can quickly solve<br>
those problems with simple SDN style automation though and then<br>
standardize.<br>
<br>
</blockquote></div><br></div>

--94eb2c14dafeb588dc055cbb8b0f--


From nobody Mon Oct 30 04:59:55 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6D2E13A214 for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 04:59:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 hNqcYBgknn7m for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 04:59:46 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78FA313F5F4 for <mboned@ietf.org>; Mon, 30 Oct 2017 04:59:45 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=uGCy68SpL0So/p7JSuWRkATRk48qazUFFuinwG/hGTwGnEQEgZk8uVC4tZShOGIPcZQqpIVeiLN0ikOxA2V2skPKl+WiP/NDxd7yqNV40GFn71DOMbHY3TM+udhjsR/OxeTUOvcSyd7IfQ96/OEeKtqpQVvUDQxIJWb9OvMbtCo=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 19528 invoked from network); 30 Oct 2017 12:59:43 +0100
Received: from pd9e11fb3.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (217.225.31.179) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 30 Oct 2017 12:59:43 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <20171028000507.GA22613@faui40p.informatik.uni-erlangen.de>
Date: Mon, 30 Oct 2017 12:59:42 +0100
Cc: tim.chown@jisc.ac.uk, mboned-chairs@ietf.org, draft-ietf-mboned-interdomain-peering-bcp@ietf.org, The IESG <iesg@ietf.org>, mboned@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7148970-2AB8-4B29-BF65-C67C58770B4E@kuehlewind.net>
References: <20171028000507.GA22613@faui40p.informatik.uni-erlangen.de>
To: Toerless Eckert <tte+ietf@cs.fau.de>
X-Mailer: Apple Mail (2.3273)
X-PPP-Message-ID: <20171030115943.19519.2507@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/UL6aBhLKgp6GVCbr-qVsEUBxSSc>
Subject: Re: [MBONED] Mirja K?hlewind's No Objection on draft-ietf-mboned-interdomain-peering-bcp-11: (with COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 11:59:53 -0000

Hi Toerless,

thanks for addressing my discuss in such detail. The new text is great. =
Maybe one little change:

OLD:
   Like IP unicast traffic, IP multicast traffic carried across non-
   controlled networks must comply to Congestion Control Principles...
NOW
   Like IP unicast traffic, IP multicast traffic carried across non-
   controlled networks MUST comply to Congestion Control Principles=E2=80=A6=


Also I would still like to see that the respective text in section 3.1 =
is slightly rephrased to match this:

OLD:
      b. If the peering point between AD-1 and AD-2 is a controlled
        network environment, then bandwidth can be allocated
        accordingly by the two domains to permit the transit of non-
        rate adaptive multicast traffic. If this is not the case, then
        it is recommended that the multicast traffic should support
        rate-adaption.
Proposed NEW:
      b. If the peering point between AD-1 and AD-2 is a controlled
        network environment, then bandwidth can be allocated
        accordingly by the two domains to permit the transit of non-
        rate adaptive multicast traffic. If this is not the case, then
        the multicast traffic MUST also support rate-adaption.

Thanks!
Mirja



> Am 28.10.2017 um 02:05 schrieb Toerless Eckert <tte+ietf@cs.fau.de>:
>=20
> [The following text up to the individual reply comments is identical =
for=20
> the replies to all ballot comments. I originally wanted to coalesce =
the reply to
> all positions into one email but the auto-generated header from =
datatracker
> makes it sound as if per-submitter replied are required. So, here we =
go with some
> repeated text followed by more individualized text:]
>=20
> Dear Reviewer,
>=20
> This is in response of your reviews of
>    =
https://www.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-11.txt
> as entered in the ballot:
>    =
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp=
/ballot/
>=20
> A version of this email containing replies to all IESG feedback for =
-11 is also in:=20
>    =
https://raw.githubusercontent.com/toerless/peering-bcp/master/11-iesg-revi=
ew-reply.txt
>=20
> Thank you so much for your thorough review. In response to the IESG
> feedback, version -12 and -13 of the draft where posted which we hope=20=

> will resolve the open issues.
> make 2
>=20
> Version -12 of the draft was just a conversion from docx generated txt =
to XML (previous generations
> where not built from XML), this introduced formatting changes (line =
wraps etc.) that rfcdiff can not ignore
> and that would have obfuscated actual content changes.=20
>=20
> Version -13 of the draft contains the text changes done in response to =
your
> comments and discusses. The following RFC diff shows the content diffs
> vs. -11 without any formatting introduced changes:
>=20
> =
http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Dhttps://tools.ietf=
.org/id/draft-ietf-mboned-interdomain-peering-bcp-12.txt&url2=3Dhttps://to=
ols.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-13.txt
>=20
> In summary:
>   Beside the various smaller fixups from comments, the mayor =
rewritten/new blocks are:
>=20
>   4.1.1 - bandwidth management (aka: congestion control section).=20
>           I didn't just want to put the magic CC sentence in but =
wanted to let
>           readers understand what it means in the context of =
specifically
>   6. Security considerations
>      6.1.  DoS attacks (against state and bandwidth)=09
>      6.2.  Content security=09
>      6.3.  Peering encryption
>      6.4.  Operational Aspects
>            This is where the securing of log exchange is discussed.
>   7. Privacy Considerations
>      Got somewhat longer to explain because the specifics of multicast =
content and privacy
>      are likely not that obious to non-multicast  experienced readers, =
and given how this
>      is a BCP and i don't even think we did describe this anywhere =
else, it had to be
>      explanatory.
>=20
>   4.2.4.  Public Peering Routing Aspects
>      text did mention non-private peerings, but i was afraid that =
readers would not
>      understand the problematic implications, so i detailled them =
given how those
>      peering L2 domains are still common for unicast.
>=20
>=20
> Cheers
>    Toerless for the Authors
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Mirja Kuehlewind:
>=20
>=20
>> Sorry for this last minute discuss but I would like to emphasize the =
points made in the tsv-art review on congestion/rate control (Thanks =
Yoshi!):
>=20
>> Please provide stronger guidance (MUST) on the use of rate/congestion =
control in these two cases:
>>=20
>> In Section 3.1:
>>    " If the peering point between AD-1 and AD-2 is a controlled
>>   network environment, then bandwidth can be allocated
>>   accordingly by the two domains to permit the transit of non-
>>   rate adaptive multicast traffic. If this is not the case, then
>>   it is recommended that the multicast traffic should support
>>   rate-adaption."
>>=20
>> In Section 4.1,
>>     "When determining the appropriate bandwidth allocation, parties =
should consider use
>>       of a multicast protocol suitable for live video streaming that
>>       is consistent with Congestion Control Principles [BCP41]."
>=20
> I tried to fix this text a bit more comprehensively:
> - removed text from 3.1. The CC requirements apply to every subsection =
of 3 (3.x)
>  and it duplicates partial text in 4.1, so a random mentioning in 3.1 =
was not
>  helpfull.
> - Moved CC text from 4.1 to dedicated section 4.1.1 and made it a lot =
more explanatory
>  because in my past experience most readers do not really understand =
our cryptic
>  rules alone ("CC principles across non-controlled network paths"). =
Also added
>  reference to the fresh BCP145.
>=20
> Please re-read new section and let me know what you think.
>=20
>> Minor questions/comments:
>>=20
>> 1) Section 3.4 also says:
>> "Highly efficient use of bandwidth in AD-1."
>> But aren't packets eventually duplicated in this case in AD-1? I =
guess it's more efficient than replicating them at the network border =
but might be still less efficient than native multicast in the whole =
network, no?
>=20
> Changed to:
>  <t>Efficient use of bandwidth in AD-1 (The closer AR is to uBR, the =
more efficient).</t>
>=20
>> 2) section 4.3.3 says:
>> "The two AD's may supply additional security logs..."
>> This seems to be a general action not specific to multicast or the =
scenarios described in this doc.
>=20
> Yes, i thought about this and came up with the following explanation:
>=20
>   <t>Note that except for implied multicast specific elements,
>   the options listed here are not unique or novel for IP multicast, =
but
>   they are more important for services novel to the operators than for
>   operationally well established services (such as unicast).  =
Therefore
>   we detail them as follows:</t>
>=20
>> 3) I don't think the conclusion section (8) is helpful or needed. If =
you want to keep it at all, this text could be moved into the =
introduction.
>=20
> Removed - for the time being. I was told that having a wrap up in =
documents is
> always a good way to reflect on the document, but i agree the existing =
text
> is more distracting than helpful.
>=20


From nobody Mon Oct 30 08:49:52 2017
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A09813FACC for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 08:49:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.319
X-Spam-Level: 
X-Spam-Status: No, score=-4.319 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_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 uW_AS9njkGXJ for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 08:49:34 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0868E1FF5C2 for <mboned@ietf.org>; Mon, 30 Oct 2017 08:41:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1509378066; h=from:subject:date:message-id:to:mime-version:content-type:references; bh=NSRM3onyROYUyWXRmfC3lSdL7xtJ54mkEPxAOPEGVLg=; b=HZGhn4rxXfoHdlFSNWc8yM7dTaEXVKFfRGfOoRxU9S9qy9s6thKJ0uuoC9HtEjw6WywN0X85gMDtJy0tgjcqKDXzTUIDwtGS3z14AGUkm4cmqdCekr+PDL89Ibj26xoawpEU6DwI2t423b2b28y1lKFvR7SoqVkYhclJVHaLlno=
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-ve1eur03lp0152.outbound.protection.outlook.com [213.199.154.152]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-19-RS5gjJ7BOWKP1bxSg5MY5g-1; Mon, 30 Oct 2017 15:41:03 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1138.eurprd07.prod.outlook.com (10.163.188.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.197.4; Mon, 30 Oct 2017 15:41:02 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::f008:dc81:4b84:fd23]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::f008:dc81:4b84:fd23%14]) with mapi id 15.20.0197.011; Mon, 30 Oct 2017 15:41:02 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: MBONED WG <mboned@ietf.org>
Thread-Topic: I-D Action: draft-acg-mboned-multicast-models-01.txt
Thread-Index: AQHTUZV9/QgbIpsce0iIeL/mr9sr1Q==
Date: Mon, 30 Oct 2017 15:41:02 +0000
Message-ID: <C9C19E9D-233F-4A04-839D-31C7C99D07EF@jisc.ac.uk>
References: <150937769158.7819.7097546262622576058@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3273)
x-originating-ip: [2001:a88:d510:1101:718e:a4e1:1d41:6dad]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1138; 20:+zGpw2sdsyqDJMhTEb/8MRqTgmuxBr3qVWp85soljyP8opxJPE24i/XqdXRUBGOTylkot/UrOB6krVfuYDPDmTp8f0jmIUKdk899b1wZ4m8LY3cpks0JQzgZHA6TREpiDLR54DmoW7BYQl46spCeAqmhs7qQ4WV1tOldnyHZkg8=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 2e174fc1-ac4d-4dfa-8d54-08d51faca03b
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(2017052603238); SRVR:AM3PR07MB1138; 
x-ms-traffictypediagnostic: AM3PR07MB1138:
x-exchange-antispam-report-test: UriScan:(120809045254105)(100405760836317);
x-microsoft-antispam-prvs: <AM3PR07MB1138680531F821E0C859D2BFD6590@AM3PR07MB1138.eurprd07.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(3231020)(93006095)(93001095)(3002001)(10201501046)(6041248)(20161123562025)(20161123555025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123564025)(20161123558100)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM3PR07MB1138; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM3PR07MB1138; 
x-forefront-prvs: 0476D4AB88
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(377424004)(189002)(199003)(68736007)(7736002)(6916009)(83716003)(86362001)(81166006)(36756003)(5660300001)(81156014)(50986999)(76176999)(50226002)(8936002)(101416001)(8676002)(106356001)(3280700002)(2900100001)(33656002)(6506006)(105586002)(3660700001)(189998001)(42882006)(229853002)(6436002)(74482002)(5250100002)(6486002)(82746002)(2906002)(316002)(230783001)(786003)(72206003)(478600001)(966005)(4001150100001)(97736004)(25786009)(102836003)(6116002)(57306001)(6512007)(54896002)(6306002)(236005)(14454004)(2473003)(53936002)(99286003)(606006)(24704002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1138; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: 2e174fc1-ac4d-4dfa-8d54-08d51faca03b
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2017 15:41:02.4948 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1138
X-MC-Unique: RS5gjJ7BOWKP1bxSg5MY5g-1
Content-Type: multipart/alternative; boundary="_000_C9C19E9D233F4A04839D31C7C99D07EFjiscacuk_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/Z9hiwbjmwvbm8DOleZk-sVjajQk>
Subject: [MBONED] Fwd: I-D Action: draft-acg-mboned-multicast-models-01.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 15:49:40 -0000

--_000_C9C19E9D233F4A04839D31C7C99D07EFjiscacuk_
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

Hi,

This update to the draft has been updated to recommend the deprecation of A=
SM for inter domain multicast, and to strongly recommend that SSM be prefer=
red for all multicast scenarios.  Apologies for the delay in posting.

I believe the text catches the general consensus of the discussion at the l=
ast IETF meeting, and on the list, before that discussion slipped into a bu=
siness model discussion.

The text on multicast service models has been shortened a little, and a new=
 section added on ASM deprecation.  The text is just a starting point based=
 on what I think the WG has said, but of course comments and suggestions fo=
r changes etc ar very welcome.  Hopefully it will provide a focus for some =
discussion in Singapore.

I can probably push out another -02 update if comments are received by arou=
nd 11pm UTC.

Tim

Begin forwarded message:

From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
Subject: I-D Action: draft-acg-mboned-multicast-models-01.txt
Date: 30 October 2017 at 15:34:51 GMT
To: <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
Reply-To: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.


       Title           : Deprecating ASM for Interdomain Multicast
       Authors         : Mikael Abrahamsson
                         Tim Chown
                         Lenny Giuliano
Filename        : draft-acg-mboned-multicast-models-01.txt
Pages           : 15
Date            : 2017-10-30

Abstract:
  This document provides a high-level overview of more commonly used
  multicast service models, principally the Any-Source Multicast (ASM)
  and Source-Specific Multicast (SSM) models, and discusses the
  applicability of the models to certain scenarios.  As a result, this
  document recommends that ASM is not used for interdomain scenarios,
  and the use of SSM is strongly recommended for all multicast
  scenarios.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-acg-mboned-multicast-models/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-acg-mboned-multicast-models-01
https://datatracker.ietf.org/doc/html/draft-acg-mboned-multicast-models-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-acg-mboned-multicast-models-01


Please note that it may take a couple of minutes from the time of submissio=
n
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/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


--_000_C9C19E9D233F4A04839D31C7C99D07EFjiscacuk_
Content-Type: text/html; charset=WINDOWS-1252
Content-ID: <81FAECD00E74A249925B766F027380F9@eurprd07.prod.outlook.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;" class=3D"">
Hi,
<div class=3D""><br class=3D"">
</div>
<div class=3D"">This update to the draft has been updated to recommend the =
deprecation of ASM for inter domain multicast, and to strongly recommend th=
at SSM be preferred for all multicast scenarios. &nbsp;Apologies for the de=
lay in posting.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I believe the text catches the general consensus of the dis=
cussion at the last IETF meeting, and on the list, before that discussion s=
lipped into a business model discussion.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">The text on multicast service models has been shortened a l=
ittle, and a new section added on ASM deprecation. &nbsp;The text is just a=
 starting point based on what I think the WG has said, but of course commen=
ts and suggestions for changes etc ar very
 welcome. &nbsp;Hopefully it will provide a focus for some discussion in Si=
ngapore.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I can probably push out another -02 update if comments are =
received by around 11pm UTC.</div>
<div class=3D""><br class=3D"">
<div class=3D"">
<div class=3D"">Tim&nbsp;</div>
</div>
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><a href=3D"mailto:internet-drafts@ietf.=
org" class=3D"">internet-drafts@ietf.org</a><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><b class=3D"">I-D Action: draft-acg-mbo=
ned-multicast-models-01.txt</b><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">30 October 2017 at 15:34:51 GMT<br clas=
s=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">&lt;<a href=3D"mailto:i-d-announce@ietf=
.org" class=3D"">i-d-announce@ietf.org</a>&gt;<br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Reply-To:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><a href=3D"mailto:internet-drafts@ietf.=
org" class=3D"">internet-drafts@ietf.org</a><br class=3D"">
</span></div>
<br class=3D"">
<div class=3D"">
<div class=3D""><br class=3D"">
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br class=3D"">
<br class=3D"">
<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Deprecating ASM for Interdomain Multicas=
t<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Authors &nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;: Mikael Abrahamsson<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Tim Chown<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Lenny Giuliano<br class=3D"">
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Filename &n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-acg-mboned-multicast-models=
-01.txt<br class=3D"">
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Pages &nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 15<br class=3D"">
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Date &nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2017-10-30<br=
 class=3D"">
<br class=3D"">
Abstract:<br class=3D"">
&nbsp;&nbsp;This document provides a high-level overview of more commonly u=
sed<br class=3D"">
&nbsp;&nbsp;multicast service models, principally the Any-Source Multicast =
(ASM)<br class=3D"">
&nbsp;&nbsp;and Source-Specific Multicast (SSM) models, and discusses the<b=
r class=3D"">
&nbsp;&nbsp;applicability of the models to certain scenarios. &nbsp;As a re=
sult, this<br class=3D"">
&nbsp;&nbsp;document recommends that ASM is not used for interdomain scenar=
ios,<br class=3D"">
&nbsp;&nbsp;and the use of SSM is strongly recommended for all multicast<br=
 class=3D"">
&nbsp;&nbsp;scenarios.<br class=3D"">
<br class=3D"">
<br class=3D"">
The IETF datatracker status page for this draft is:<br class=3D"">
<a href=3D"https://datatracker.ietf.org/doc/draft-acg-mboned-multicast-mode=
ls/" class=3D"">https://datatracker.ietf.org/doc/draft-acg-mboned-multicast=
-models/</a><br class=3D"">
<br class=3D"">
There are also htmlized versions available at:<br class=3D"">
https://tools.ietf.org/html/draft-acg-mboned-multicast-models-01<br class=
=3D"">
https://datatracker.ietf.org/doc/html/draft-acg-mboned-multicast-models-01<=
br class=3D"">
<br class=3D"">
A diff from the previous version is available at:<br class=3D"">
https://www.ietf.org/rfcdiff?url2=3Ddraft-acg-mboned-multicast-models-01<br=
 class=3D"">
<br class=3D"">
<br class=3D"">
Please note that it may take a couple of minutes from the time of submissio=
n<br class=3D"">
until the htmlized version and diff are available at tools.ietf.org.<br cla=
ss=3D"">
<br class=3D"">
Internet-Drafts are also available by anonymous FTP at:<br class=3D"">
ftp://ftp.ietf.org/internet-drafts/<br class=3D"">
<br class=3D"">
_______________________________________________<br class=3D"">
I-D-Announce mailing list<br class=3D"">
I-D-Announce@ietf.org<br class=3D"">
https://www.ietf.org/mailman/listinfo/i-d-announce<br class=3D"">
Internet-Draft directories: http://www.ietf.org/shadow.html<br class=3D"">
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt<br class=3D"">
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</body>
</html>

--_000_C9C19E9D233F4A04839D31C7C99D07EFjiscacuk_--


From nobody Mon Oct 30 10:15:03 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE08613FAA4; Mon, 30 Oct 2017 10:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 q-1tGuo-KOks; Mon, 30 Oct 2017 10:14:58 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5847613FA9D; Mon, 30 Oct 2017 10:14:58 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 2A31558C4E8; Mon, 30 Oct 2017 18:14:54 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 14EEAB0D024; Mon, 30 Oct 2017 18:14:53 +0100 (CET)
Date: Mon, 30 Oct 2017 18:14:53 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Cc: Toerless Eckert <tte+ietf@cs.fau.de>, tim.chown@jisc.ac.uk, mboned-chairs@ietf.org, draft-ietf-mboned-interdomain-peering-bcp@ietf.org, The IESG <iesg@ietf.org>, mboned@ietf.org
Message-ID: <20171030171453.GA28098@faui40p.informatik.uni-erlangen.de>
References: <20171028000507.GA22613@faui40p.informatik.uni-erlangen.de> <F7148970-2AB8-4B29-BF65-C67C58770B4E@kuehlewind.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F7148970-2AB8-4B29-BF65-C67C58770B4E@kuehlewind.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/zz2j0gdDxq8wAkytV7Ul8r0EIk8>
Subject: Re: [MBONED] Mirja K?hlewind's No Objection on draft-ietf-mboned-interdomain-peering-bcp-11: (with COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 17:15:01 -0000

Thanks, Mirja

Definitely "must" in second point, sorry.

Wrt.: MUST My issue is that this BCP was not written with
RFC2119 capitalization in mind and not vetted for it. If i change
must=>MUST in just two places (and introduce reference to RFC2119,
it looks out of place for the rest of the document, but doing capitalization
throughout the document, would require a lot more work and repeated review i fear.

Would it be possible to avoid 2119 language by adding behind both
places references that mandate this ("this is not the law, but look up the law" )?

Eg:
  Like IP unicast traffic, IP multicast traffic carried across non-
  controlled networks must comply to Congestion Control Principles
  (the normative place mandating this compliance is RFCxxxx, section y.z).

If you think this would work and had some xxxx,y,z for me, that would be great.

Otherwise i will do the MUST and RFC2119 header and pray to the IAB and
IESG that this will not raise a lot of followup capitalization requests.

Cheers
    Toerless

On Mon, Oct 30, 2017 at 12:59:42PM +0100, Mirja Kuehlewind (IETF) wrote:
> Hi Toerless,
> 
> thanks for addressing my discuss in such detail. The new text is great. Maybe one little change:
> 
> OLD:
>    Like IP unicast traffic, IP multicast traffic carried across non-
>    controlled networks must comply to Congestion Control Principles...
> NOW
>    Like IP unicast traffic, IP multicast traffic carried across non-
>    controlled networks MUST comply to Congestion Control Principles???
> 
> Also I would still like to see that the respective text in section 3.1 is slightly rephrased to match this:
> 
> OLD:
>       b. If the peering point between AD-1 and AD-2 is a controlled
>         network environment, then bandwidth can be allocated
>         accordingly by the two domains to permit the transit of non-
>         rate adaptive multicast traffic. If this is not the case, then
>         it is recommended that the multicast traffic should support
>         rate-adaption.
> Proposed NEW:
>       b. If the peering point between AD-1 and AD-2 is a controlled
>         network environment, then bandwidth can be allocated
>         accordingly by the two domains to permit the transit of non-
>         rate adaptive multicast traffic. If this is not the case, then
>         the multicast traffic MUST also support rate-adaption.
> 
> Thanks!
> Mirja
> 
> 
> 
> > Am 28.10.2017 um 02:05 schrieb Toerless Eckert <tte+ietf@cs.fau.de>:
> > 
> > [The following text up to the individual reply comments is identical for 
> > the replies to all ballot comments. I originally wanted to coalesce the reply to
> > all positions into one email but the auto-generated header from datatracker
> > makes it sound as if per-submitter replied are required. So, here we go with some
> > repeated text followed by more individualized text:]
> > 
> > Dear Reviewer,
> > 
> > This is in response of your reviews of
> >    https://www.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-11.txt
> > as entered in the ballot:
> >    https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/ballot/
> > 
> > A version of this email containing replies to all IESG feedback for -11 is also in: 
> >    https://raw.githubusercontent.com/toerless/peering-bcp/master/11-iesg-review-reply.txt
> > 
> > Thank you so much for your thorough review. In response to the IESG
> > feedback, version -12 and -13 of the draft where posted which we hope 
> > will resolve the open issues.
> > make 2
> > 
> > Version -12 of the draft was just a conversion from docx generated txt to XML (previous generations
> > where not built from XML), this introduced formatting changes (line wraps etc.) that rfcdiff can not ignore
> > and that would have obfuscated actual content changes. 
> > 
> > Version -13 of the draft contains the text changes done in response to your
> > comments and discusses. The following RFC diff shows the content diffs
> > vs. -11 without any formatting introduced changes:
> > 
> > http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-12.txt&url2=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-13.txt
> > 
> > In summary:
> >   Beside the various smaller fixups from comments, the mayor rewritten/new blocks are:
> > 
> >   4.1.1 - bandwidth management (aka: congestion control section). 
> >           I didn't just want to put the magic CC sentence in but wanted to let
> >           readers understand what it means in the context of specifically
> >   6. Security considerations
> >      6.1.  DoS attacks (against state and bandwidth)	
> >      6.2.  Content security	
> >      6.3.  Peering encryption
> >      6.4.  Operational Aspects
> >            This is where the securing of log exchange is discussed.
> >   7. Privacy Considerations
> >      Got somewhat longer to explain because the specifics of multicast content and privacy
> >      are likely not that obious to non-multicast  experienced readers, and given how this
> >      is a BCP and i don't even think we did describe this anywhere else, it had to be
> >      explanatory.
> > 
> >   4.2.4.  Public Peering Routing Aspects
> >      text did mention non-private peerings, but i was afraid that readers would not
> >      understand the problematic implications, so i detailled them given how those
> >      peering L2 domains are still common for unicast.
> > 
> > 
> > Cheers
> >    Toerless for the Authors
> > 
> > =====================================================================================
> > Mirja Kuehlewind:
> > 
> > 
> >> Sorry for this last minute discuss but I would like to emphasize the points made in the tsv-art review on congestion/rate control (Thanks Yoshi!):
> > 
> >> Please provide stronger guidance (MUST) on the use of rate/congestion control in these two cases:
> >> 
> >> In Section 3.1:
> >>    " If the peering point between AD-1 and AD-2 is a controlled
> >>   network environment, then bandwidth can be allocated
> >>   accordingly by the two domains to permit the transit of non-
> >>   rate adaptive multicast traffic. If this is not the case, then
> >>   it is recommended that the multicast traffic should support
> >>   rate-adaption."
> >> 
> >> In Section 4.1,
> >>     "When determining the appropriate bandwidth allocation, parties should consider use
> >>       of a multicast protocol suitable for live video streaming that
> >>       is consistent with Congestion Control Principles [BCP41]."
> > 
> > I tried to fix this text a bit more comprehensively:
> > - removed text from 3.1. The CC requirements apply to every subsection of 3 (3.x)
> >  and it duplicates partial text in 4.1, so a random mentioning in 3.1 was not
> >  helpfull.
> > - Moved CC text from 4.1 to dedicated section 4.1.1 and made it a lot more explanatory
> >  because in my past experience most readers do not really understand our cryptic
> >  rules alone ("CC principles across non-controlled network paths"). Also added
> >  reference to the fresh BCP145.
> > 
> > Please re-read new section and let me know what you think.
> > 
> >> Minor questions/comments:
> >> 
> >> 1) Section 3.4 also says:
> >> "Highly efficient use of bandwidth in AD-1."
> >> But aren't packets eventually duplicated in this case in AD-1? I guess it's more efficient than replicating them at the network border but might be still less efficient than native multicast in the whole network, no?
> > 
> > Changed to:
> >  <t>Efficient use of bandwidth in AD-1 (The closer AR is to uBR, the more efficient).</t>
> > 
> >> 2) section 4.3.3 says:
> >> "The two AD's may supply additional security logs..."
> >> This seems to be a general action not specific to multicast or the scenarios described in this doc.
> > 
> > Yes, i thought about this and came up with the following explanation:
> > 
> >   <t>Note that except for implied multicast specific elements,
> >   the options listed here are not unique or novel for IP multicast, but
> >   they are more important for services novel to the operators than for
> >   operationally well established services (such as unicast).  Therefore
> >   we detail them as follows:</t>
> > 
> >> 3) I don't think the conclusion section (8) is helpful or needed. If you want to keep it at all, this text could be moved into the introduction.
> > 
> > Removed - for the time being. I was told that having a wrap up in documents is
> > always a good way to reflect on the document, but i agree the existing text
> > is more distracting than helpful.
> > 

-- 
---
tte@cs.fau.de


From nobody Mon Oct 30 12:49:26 2017
Return-Path: <dwcarder@es.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 467CB13FAFF for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 12:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.799
X-Spam-Level: 
X-Spam-Status: No, score=-3.799 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_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=es.net
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 DOlFkoT6CrBa for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 12:49:19 -0700 (PDT)
Received: from fe3.lbl.gov (fe3.lbl.gov [128.3.41.68]) by ietfa.amsl.com (Postfix) with ESMTP id 8FC6513FAEA for <mboned@ietf.org>; Mon, 30 Oct 2017 12:49:04 -0700 (PDT)
X-Ironport-SBRS: 2.7
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2FMAAARgfdZf8XfVdFbDgsBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBARQBAQEBAQEBAQEBAQcBAQEBAYJmgTKBFY4bdJAalkKCEQoYDYR?= =?us-ascii?q?HTwKEXz8YAQEBAQEBAQEBAQECEAEBCQsLCCYxgjgkAQ1GLAEBAQEBAQEBASMBA?= =?us-ascii?q?QEBAQEjAj4sAQEBAQIBAQE4BgEBLAsBBAsLEQMBAgoeBw8FEw0BBQELCQ4TCYo?= =?us-ascii?q?SCAEEC5wRQIshgxKDCAEBBYd1AQEBAQEBAQEBAQEBAQEBAQEBGAgJAQiDHIE2U?= =?us-ascii?q?YZmgyIchReCMpJyjxYCh2SNCYIiXoUig06HSoxdAnKIEgIEAgQFAgYUJIEVH4I?= =?us-ascii?q?hgQUKHyqCZAmCRA8cgShdWQGNIAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.44,320,1505804400"; d="scan'208";a="94691336"
Received: from mail-io0-f197.google.com ([209.85.223.197]) by fe3.lbl.gov with ESMTP; 30 Oct 2017 12:49:02 -0700
Received: by mail-io0-f197.google.com with SMTP id i38so37006383iod.10 for <mboned@ietf.org>; Mon, 30 Oct 2017 12:49:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=es.net; s=esnet-google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=67rg+G/5C3ZUaSRmG9Ezbp1sfT/hTHaGzxg8oxcYOBc=; b=fIGgwp9fqXQKM6hP4fF2q5uyuSrZf4QnOa/kPdcaFYYA6oRnjP8+KYHJtZwUG0sxYV jts9OAVLvRWCP3TYGdKIU9pHMekuvovmcx3em+XpbUMbvoDPD1f3w9Ms8ctc/e5e1B0L AeMOQbUzJpX8MWIVzoE4IsuyRI6eqed/lRnaa+sYPweHv6GDxjkPT/sP9xGVXUKbfEFb IVGvH+hKW4Fys0ci4dp6ukIGTHG1GEGcL6RQsM6mnUrkST7/ni0XZLYOqArVVSN7i5O7 9tvx4gjG7SFvQyWu55/iicfYrCOhgK0a0SOPRyVnL5mI+y3yWkx3/9q4JxeslLI4TwGx UKhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=67rg+G/5C3ZUaSRmG9Ezbp1sfT/hTHaGzxg8oxcYOBc=; b=oOkHBlDw1KoK4OQ8Y3g/C3AVOKdagq0bNyplBATgr1ZVKoeb5uKJdbUXHxAgD67RxQ EGoBkXZTH2Cf5dNIBFWdMoiB9BHHkiM6fek3vn0QvQ64rAAc8TY9AQm1Lu+4gJ35+gbj 7/0tVXYHXmiyBO+cr6NiKNycwhkZnMQfCfBFlozrGh391VGfyxphDC44lBhmFuRaaSpI JSbaNlqfvEPrfApufxRJyk908qgQ5L0F2POXQpAu/PcKpPhGiGLnT2W6fR67X6U5Hibg sk989h/CCt5uZDRBxjP4t4itKUDNQCxZ9hc0fh1Upy2GzlnEdHVjckwnM76qS/Ofbq8a u6Ig==
X-Gm-Message-State: AMCzsaVEXH9ZfjuQ6t5yy4NvEOQtACi0x1BH7T7Sgw7TLOfHPyB/coDr BZzSWlDxKjmNvJlm+3+thAdPVjvarAyMMWemw+PWONYVcEhqimqctzVLcMJ9VHIMHRpRnJXrSce CEkRmHEyk
X-Received: by 10.107.172.199 with SMTP id v190mr12290319ioe.132.1509392942527;  Mon, 30 Oct 2017 12:49:02 -0700 (PDT)
X-Google-Smtp-Source: ABhQp+StIEjEhOl9sjJiCr/aBcBxR3EZpvxp9tvVIecZJIOnjddPIMQMg7ibITLlQ6LfbpgSH9WmrA==
X-Received: by 10.107.172.199 with SMTP id v190mr12290289ioe.132.1509392942091;  Mon, 30 Oct 2017 12:49:02 -0700 (PDT)
Received: from localhost (2600-6c44-5f7f-e601-190a-f5c2-d7f8-cf0c.dhcp6.chtrptr.net. [2600:6c44:5f7f:e601:190a:f5c2:d7f8:cf0c]) by smtp.gmail.com with ESMTPSA id l206sm2227578ita.29.2017.10.30.12.49.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Oct 2017 12:49:01 -0700 (PDT)
Date: Mon, 30 Oct 2017 14:49:00 -0500
From: "Dale W. Carder" <dwcarder@es.net>
To: Tim Chown <Tim.Chown@jisc.ac.uk>
Cc: MBONED WG <mboned@ietf.org>
Message-ID: <20171030194900.GB12994@cs-it-6805697.local>
References: <150937769158.7819.7097546262622576058@ietfa.amsl.com> <C9C19E9D-233F-4A04-839D-31C7C99D07EF@jisc.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C9C19E9D-233F-4A04-839D-31C7C99D07EF@jisc.ac.uk>
User-Agent: Mutt/1.8.2 (2017-04-18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/bz0s-1DTJSPnl9slYbWX5-D2Vdc>
Subject: Re: [MBONED] Fwd: I-D Action: draft-acg-mboned-multicast-models-01.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 19:49:21 -0000

Hi Tim,

Thus spake Tim Chown (Tim.Chown@jisc.ac.uk) on Mon, Oct 30, 2017 at 03:41:02PM +0000:
> 
> The text on multicast service models has been shortened a little, and a new section added on ASM deprecation.  The text is just a starting point based on what I think the WG has said, but of course comments and suggestions for changes etc ar very welcome.  Hopefully it will provide a focus for some discussion in Singapore.

In section 3.1, there's a reference to RFC5771, but either there or in
section 7.5, it may be worth quoting part of section 9 of RFC5771 
particularly:
  "Domains with a 32-bit ASN MAY apply for space in AD-HOC Block III, 
  or consider using IPv6 multicast addresses."

My understanding is that 32-bit ASNs are increasingly common if not the
default now, so I would think that is additional motivation towards 
using SSM (if not IPv6 SSM).

Dale


> Begin forwarded message:
> 
> From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
> Subject: I-D Action: draft-acg-mboned-multicast-models-01.txt
> Date: 30 October 2017 at 15:34:51 GMT
> To: <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
> Reply-To: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>        Title           : Deprecating ASM for Interdomain Multicast
>        Authors         : Mikael Abrahamsson
>                          Tim Chown
>                          Lenny Giuliano
> Filename        : draft-acg-mboned-multicast-models-01.txt
> Pages           : 15
> Date            : 2017-10-30
> 
> Abstract:
>   This document provides a high-level overview of more commonly used
>   multicast service models, principally the Any-Source Multicast (ASM)
>   and Source-Specific Multicast (SSM) models, and discusses the
>   applicability of the models to certain scenarios.  As a result, this
>   document recommends that ASM is not used for interdomain scenarios,
>   and the use of SSM is strongly recommended for all multicast
>   scenarios.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-acg-mboned-multicast-models/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-acg-mboned-multicast-models-01
> https://datatracker.ietf.org/doc/html/draft-acg-mboned-multicast-models-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-acg-mboned-multicast-models-01
> 
> 
> 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/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 

> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


From nobody Mon Oct 30 14:23:27 2017
Return-Path: <warren@kumari.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5038B13FB9E for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 14:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.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 PdJx7VA8xxtv for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 14:23:23 -0700 (PDT)
Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::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 7AF5413FBB7 for <mboned@ietf.org>; Mon, 30 Oct 2017 14:23:19 -0700 (PDT)
Received: by mail-wr0-x232.google.com with SMTP id y9so14027580wrb.2 for <mboned@ietf.org>; Mon, 30 Oct 2017 14:23:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=neBSV/9KT1VNDHowBxLmQlB0i30La7GFC5aBTVNa98c=; b=d8eE/ngyvkO2Iq6SWuQdndpBioi/fD69HMpMLDOueC5npaPwYgXUAh/o0j+5aNOu7J Di/V7cAWQlLYRGHtSmQI2ggiEoSUxJiJUaxVH4T/5Ov2nBYvh/K38mEw3IQNEZWyP6/n hBmSyc/H1XeQwlDZOnds8mjqpVOyFwza3ZPUjafJI/l20lXK60HbfkfNocNFtzl0VSgu y4b5wCwBZDCSplR+/WXuK3FCa1u6Ep6tNb/rne0KvSIteaSzpTO+oT2QHE2Ic0D4thza zm7EUr5ZgwU5bKibReJ+j2fhSEGJJfFktAyVgH0vjD+52OA0CQMUR5D87mAnNoprbg8M G2aA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=neBSV/9KT1VNDHowBxLmQlB0i30La7GFC5aBTVNa98c=; b=WojNY1LjgtRG4WPc25J/uedWNpebgHh8GBCtmLHdkoFH4dpip9on7YQRJpdqM2olzo fAbbpXuuhNPa9b7uPpT0gsvn4MB7C2+vsJQeHwcqvLbijANtCfb3WedA83P26ll0QOzv FNp2M6lygAmsIYWFoxtkIMUi+zd3WMcRqnwSfukRKndw3LOTYefii17ZWfrSOUE5E1/3 mGaucxy6ixDSKp3cdOz87M6YQr9pY0ryY003yT6a/GHe6ZYxpY1/ayXKBOHPF/mHrNQU FKmGVY0RvRvrlFd9TiRQAct7ronvUHebOkQg/h22c9Okf8PeLHuznGC+xNWpXtzSVf6N CUOg==
X-Gm-Message-State: AMCzsaWBROXOY1x0/njCTxxMe6HAbtuq1xFB0fx1ilVC7u0ys55Fm3p6 jRj1vmnF3WhLen0ho51aZL+CcUTKyVG+kVHLafdLMw==
X-Google-Smtp-Source: ABhQp+TAnyniaXW3++6ebpgx7SQbnhnnKn7z7INQR6GlANJbj7PtWPZoMob0lL3vvMrp1oIC/bXYysVvK4A3V+GeuQs=
X-Received: by 10.223.151.198 with SMTP id t6mr9214477wrb.2.1509398597740; Mon, 30 Oct 2017 14:23:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.187.12 with HTTP; Mon, 30 Oct 2017 14:22:36 -0700 (PDT)
From: Warren Kumari <warren@kumari.net>
Date: Mon, 30 Oct 2017 17:22:36 -0400
Message-ID: <CAHw9_iLt3XMdgEw6ZoMviG+zAEPLDH6jxJojvS_f+GP8GYODmQ@mail.gmail.com>
To: draft-ietf-mboned-mtrace-v2@ietf.org, mboned-chairs@ietf.org,  mboned@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/Z8mXOsJVjMGfzagZVswBnmS2vn4>
Subject: [MBONED] AD review of draft-ietf-mboned-mtrace-v2
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 21:23:25 -0000

Hello,

Firstly, I'd like to apologize for how long it took me to review this
- I came down with a bad case of pneumonia, and was broken for a
while...


Thank you for your work on this document, it's a well written and easy
to understand
draft.  I do have a few comments that I=E2=80=99d like addressed before I
start IETF LC =E2=80=94 addressing these now will avoid issues later in the
process.


Section 1.  Introduction
   Given a multicast distribution tree, tracing from a multicast source
   to a receiver is difficult, since we do not know which branch of the
[O] know which branch
[P] know on which branch
[R] readability/grammar
   multicast tree the receiver lies.

When not receiving an Mtrace2 Reply message due to
   network congestion, a broken router (see Section 5.6), or a non-
   responding router (see Section 5.7), the Mtrace2 client may resend
   another Mtrace2 Query with a lower hop count (see Section 3.2.1), and
   repeat the process until it receives an Mtrace2 Reply message.  The
   details are Mtrace2 client specific, and it is outside the scope of

[O] specific, and it is outside
[P] specific and outside
[R] readability; otherwise we would need to say =E2=80=9Cthey,=E2=80=9D and=
 not =E2=80=9Cit,=E2=80=9D
because we are referencing =E2=80=9Cdetails=E2=80=9D (plural). That seems a=
wkward.
   this document.

   Note that when a router's control plane and forwarding plane are out
   of sync, the Mtrace2 Requests might be forwarded based on the control
   states instead.  In which case, the traced path might not represent

[O] In which case,
[P] In this case,
[R] grammar
   the real path the data packets would follow.

Section 3.2.3.  Mtrace2 Reply
...
  The Reply message would then
   be unicasted to the Mtrace2 client specified in the Mtrace2 Client
   Address field.
   There are a number of cases an intermediate router might return a

[O]  cases an intermediate router might return
[P] cases in which an intermediate router might return
[R] I think this is what was meant.

Section 3.2.6.  Mtrace2 Augmented Response Block
...
      When the NO_SPACE error occurs on a router, the router should send
      the original Mtrace2 Request received from the downstream router
      as a Reply back to the Mtrace2 client, and continue with a new

[O] client, and
[P] client and
[R] grammar
      Mtrace2 Request.

Section 4.3.3.  Appending Standard Response Block
   ...
   The router then turns the Request
   into a Reply, and sends the Reply as described in Section 4.4.
[O] Reply, and
[P] Reply and
[R] grammar

5.8.3.  No Upstream Router
   A trace can not continue if the last Upstream Router in the trace is
[O] can not
[P] cannot
[R] grammar =E2=80=94 unless you that optionally, it can elect not to conti=
nue=E2=80=A6 :-P
   set to 0.

5.9.  Continuing after an Error
  ...
   However, if all paths but one flow back towards the non-
   responding router, it is possible to be sure that this is the correct
[O] it is possible to be sure
[R] I don=E2=80=99t know what this means - perhaps "this" ?
   path.


7.3.  Packet Loss
  ...
   Since the packet counts may be
   changing as the Mtrace2 Request is propagating, there may be small
   errors (off by 1 or 2 or more) in these statistics.  However, these

[O] (off by 1 or 2 or more)
[R] limit the =E2=80=9Cor more=E2=80=9D; otherwise, what=E2=80=99s the poin=
t of saying this at
all? Perhaps "on the order of 1 or 2"?
---
Again, apolgies for the delay,
W
--=20
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Mon Oct 30 14:51:09 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F8F013FC0D for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 14:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 hIZMZiititVu for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 14:51:05 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6E2113FBF5 for <mboned@ietf.org>; Mon, 30 Oct 2017 14:51:04 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=AmKacdajSkwwGoPyhGgzLdGAINSzB4h4B+YiBuVA7Lh1eUqAYs/mqeiHuIdG8tGy316xb2QMa8yV2ZbPAqy4lJtbNOmp3KrJ8GpGCLrqMTyajsHzmM/WX16/Qjw7qLKNxEv9vFhwspHNp3W8MPCJ/JYNOd/y1aTf+D1LXC9kb5c=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 23866 invoked from network); 30 Oct 2017 22:51:03 +0100
Received: from pd9e11fb3.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (217.225.31.179) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 30 Oct 2017 22:51:02 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <20171030171453.GA28098@faui40p.informatik.uni-erlangen.de>
Date: Mon, 30 Oct 2017 22:51:01 +0100
Cc: draft-ietf-mboned-interdomain-peering-bcp@ietf.org, tim.chown@jisc.ac.uk,  The IESG <iesg@ietf.org>, mboned@ietf.org, Toerless Eckert <tte+ietf@cs.fau.de>, mboned-chairs@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA86A6FD-CD81-4248-8D65-2B60A28AABB0@kuehlewind.net>
References: <20171028000507.GA22613@faui40p.informatik.uni-erlangen.de> <F7148970-2AB8-4B29-BF65-C67C58770B4E@kuehlewind.net> <20171030171453.GA28098@faui40p.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3273)
X-PPP-Message-ID: <20171030215103.23856.40309@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/PEFSRMoujyW5lX0LL-5_l2jCjOw>
Subject: Re: [MBONED] Mirja K?hlewind's No Objection on draft-ietf-mboned-interdomain-peering-bcp-11: (with COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 21:51:07 -0000

Hi Toerless,

I didn=E2=80=99t realize that there is no normative language in the =
draft. In this case lower case must is fine. I guess you can point to =
rfc8085, however, there is also no MUST, just more guidance.=20

Mirja


> Am 30.10.2017 um 18:14 schrieb Toerless Eckert <tte@cs.fau.de>:
>=20
> Thanks, Mirja
>=20
> Definitely "must" in second point, sorry.
>=20
> Wrt.: MUST My issue is that this BCP was not written with
> RFC2119 capitalization in mind and not vetted for it. If i change
> must=3D>MUST in just two places (and introduce reference to RFC2119,
> it looks out of place for the rest of the document, but doing =
capitalization
> throughout the document, would require a lot more work and repeated =
review i fear.
>=20
> Would it be possible to avoid 2119 language by adding behind both
> places references that mandate this ("this is not the law, but look up =
the law" )?
>=20
> Eg:
>  Like IP unicast traffic, IP multicast traffic carried across non-
>  controlled networks must comply to Congestion Control Principles
>  (the normative place mandating this compliance is RFCxxxx, section =
y.z).
>=20
> If you think this would work and had some xxxx,y,z for me, that would =
be great.
>=20
> Otherwise i will do the MUST and RFC2119 header and pray to the IAB =
and
> IESG that this will not raise a lot of followup capitalization =
requests.
>=20
> Cheers
>    Toerless
>=20
> On Mon, Oct 30, 2017 at 12:59:42PM +0100, Mirja Kuehlewind (IETF) =
wrote:
>> Hi Toerless,
>>=20
>> thanks for addressing my discuss in such detail. The new text is =
great. Maybe one little change:
>>=20
>> OLD:
>>   Like IP unicast traffic, IP multicast traffic carried across non-
>>   controlled networks must comply to Congestion Control Principles...
>> NOW
>>   Like IP unicast traffic, IP multicast traffic carried across non-
>>   controlled networks MUST comply to Congestion Control Principles???
>>=20
>> Also I would still like to see that the respective text in section =
3.1 is slightly rephrased to match this:
>>=20
>> OLD:
>>      b. If the peering point between AD-1 and AD-2 is a controlled
>>        network environment, then bandwidth can be allocated
>>        accordingly by the two domains to permit the transit of non-
>>        rate adaptive multicast traffic. If this is not the case, then
>>        it is recommended that the multicast traffic should support
>>        rate-adaption.
>> Proposed NEW:
>>      b. If the peering point between AD-1 and AD-2 is a controlled
>>        network environment, then bandwidth can be allocated
>>        accordingly by the two domains to permit the transit of non-
>>        rate adaptive multicast traffic. If this is not the case, then
>>        the multicast traffic MUST also support rate-adaption.
>>=20
>> Thanks!
>> Mirja
>>=20
>>=20
>>=20
>>> Am 28.10.2017 um 02:05 schrieb Toerless Eckert <tte+ietf@cs.fau.de>:
>>>=20
>>> [The following text up to the individual reply comments is identical =
for=20
>>> the replies to all ballot comments. I originally wanted to coalesce =
the reply to
>>> all positions into one email but the auto-generated header from =
datatracker
>>> makes it sound as if per-submitter replied are required. So, here we =
go with some
>>> repeated text followed by more individualized text:]
>>>=20
>>> Dear Reviewer,
>>>=20
>>> This is in response of your reviews of
>>>   =
https://www.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-11.txt
>>> as entered in the ballot:
>>>   =
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp=
/ballot/
>>>=20
>>> A version of this email containing replies to all IESG feedback for =
-11 is also in:=20
>>>   =
https://raw.githubusercontent.com/toerless/peering-bcp/master/11-iesg-revi=
ew-reply.txt
>>>=20
>>> Thank you so much for your thorough review. In response to the IESG
>>> feedback, version -12 and -13 of the draft where posted which we =
hope=20
>>> will resolve the open issues.
>>> make 2
>>>=20
>>> Version -12 of the draft was just a conversion from docx generated =
txt to XML (previous generations
>>> where not built from XML), this introduced formatting changes (line =
wraps etc.) that rfcdiff can not ignore
>>> and that would have obfuscated actual content changes.=20
>>>=20
>>> Version -13 of the draft contains the text changes done in response =
to your
>>> comments and discusses. The following RFC diff shows the content =
diffs
>>> vs. -11 without any formatting introduced changes:
>>>=20
>>> =
http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Dhttps://tools.ietf=
.org/id/draft-ietf-mboned-interdomain-peering-bcp-12.txt&url2=3Dhttps://to=
ols.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-13.txt
>>>=20
>>> In summary:
>>>  Beside the various smaller fixups from comments, the mayor =
rewritten/new blocks are:
>>>=20
>>>  4.1.1 - bandwidth management (aka: congestion control section).=20
>>>          I didn't just want to put the magic CC sentence in but =
wanted to let
>>>          readers understand what it means in the context of =
specifically
>>>  6. Security considerations
>>>     6.1.  DoS attacks (against state and bandwidth)=09
>>>     6.2.  Content security=09
>>>     6.3.  Peering encryption
>>>     6.4.  Operational Aspects
>>>           This is where the securing of log exchange is discussed.
>>>  7. Privacy Considerations
>>>     Got somewhat longer to explain because the specifics of =
multicast content and privacy
>>>     are likely not that obious to non-multicast  experienced =
readers, and given how this
>>>     is a BCP and i don't even think we did describe this anywhere =
else, it had to be
>>>     explanatory.
>>>=20
>>>  4.2.4.  Public Peering Routing Aspects
>>>     text did mention non-private peerings, but i was afraid that =
readers would not
>>>     understand the problematic implications, so i detailled them =
given how those
>>>     peering L2 domains are still common for unicast.
>>>=20
>>>=20
>>> Cheers
>>>   Toerless for the Authors
>>>=20
>>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> Mirja Kuehlewind:
>>>=20
>>>=20
>>>> Sorry for this last minute discuss but I would like to emphasize =
the points made in the tsv-art review on congestion/rate control (Thanks =
Yoshi!):
>>>=20
>>>> Please provide stronger guidance (MUST) on the use of =
rate/congestion control in these two cases:
>>>>=20
>>>> In Section 3.1:
>>>>   " If the peering point between AD-1 and AD-2 is a controlled
>>>>  network environment, then bandwidth can be allocated
>>>>  accordingly by the two domains to permit the transit of non-
>>>>  rate adaptive multicast traffic. If this is not the case, then
>>>>  it is recommended that the multicast traffic should support
>>>>  rate-adaption."
>>>>=20
>>>> In Section 4.1,
>>>>    "When determining the appropriate bandwidth allocation, parties =
should consider use
>>>>      of a multicast protocol suitable for live video streaming that
>>>>      is consistent with Congestion Control Principles [BCP41]."
>>>=20
>>> I tried to fix this text a bit more comprehensively:
>>> - removed text from 3.1. The CC requirements apply to every =
subsection of 3 (3.x)
>>> and it duplicates partial text in 4.1, so a random mentioning in 3.1 =
was not
>>> helpfull.
>>> - Moved CC text from 4.1 to dedicated section 4.1.1 and made it a =
lot more explanatory
>>> because in my past experience most readers do not really understand =
our cryptic
>>> rules alone ("CC principles across non-controlled network paths"). =
Also added
>>> reference to the fresh BCP145.
>>>=20
>>> Please re-read new section and let me know what you think.
>>>=20
>>>> Minor questions/comments:
>>>>=20
>>>> 1) Section 3.4 also says:
>>>> "Highly efficient use of bandwidth in AD-1."
>>>> But aren't packets eventually duplicated in this case in AD-1? I =
guess it's more efficient than replicating them at the network border =
but might be still less efficient than native multicast in the whole =
network, no?
>>>=20
>>> Changed to:
>>> <t>Efficient use of bandwidth in AD-1 (The closer AR is to uBR, the =
more efficient).</t>
>>>=20
>>>> 2) section 4.3.3 says:
>>>> "The two AD's may supply additional security logs..."
>>>> This seems to be a general action not specific to multicast or the =
scenarios described in this doc.
>>>=20
>>> Yes, i thought about this and came up with the following =
explanation:
>>>=20
>>>  <t>Note that except for implied multicast specific elements,
>>>  the options listed here are not unique or novel for IP multicast, =
but
>>>  they are more important for services novel to the operators than =
for
>>>  operationally well established services (such as unicast).  =
Therefore
>>>  we detail them as follows:</t>
>>>=20
>>>> 3) I don't think the conclusion section (8) is helpful or needed. =
If you want to keep it at all, this text could be moved into the =
introduction.
>>>=20
>>> Removed - for the time being. I was told that having a wrap up in =
documents is
>>> always a good way to reflect on the document, but i agree the =
existing text
>>> is more distracting than helpful.
>>>=20
>=20
> --=20
> ---
> tte@cs.fau.de
>=20


From nobody Mon Oct 30 16:06:24 2017
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2F0BC6FE for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 16:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level: 
X-Spam-Status: No, score=-4.32 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_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 sgdY4zatQqNT for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 16:06:18 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [207.82.80.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A6751DF8AB for <mboned@ietf.org>; Mon, 30 Oct 2017 16:05:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1509404757; h=from:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=NMRKMkbPJMG1LfDV5iuUlHq4+l4yl9kUqDNabyNeNBM=; b=SiBw3zP4eaXQF3p+v44JHSaeCRyrR3nOMbplPqhjlfimMkMlxQF1RtxiI0nTGnp55TEfU+SSeEfsrT+VHqzr23fz0VD2EwemhvqB2zzTllhWMi4MiCP0juermRksOwmHWWLkxtSf2jjkTRvUcX1se4IiHxeYuTtfJtp6jJ3rlJw=
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01lp0240.outbound.protection.outlook.com [213.199.154.240]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-68-bjRGT-C1OW2N1r7H8z2tuA-1; Mon, 30 Oct 2017 23:05:52 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1138.eurprd07.prod.outlook.com (10.163.188.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.197.4; Mon, 30 Oct 2017 23:05:50 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::f008:dc81:4b84:fd23]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::f008:dc81:4b84:fd23%14]) with mapi id 15.20.0197.011; Mon, 30 Oct 2017 23:05:50 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: "Dale W. Carder" <dwcarder@es.net>
CC: MBONED WG <mboned@ietf.org>
Thread-Topic: [MBONED] I-D Action: draft-acg-mboned-multicast-models-01.txt
Thread-Index: AQHTUdOgMWpuVI+iV0ORjO7HyT8WyQ==
Date: Mon, 30 Oct 2017 23:05:49 +0000
Message-ID: <0BC8FB29-99D2-4B00-AA2D-FA321F57E2FE@jisc.ac.uk>
References: <150937769158.7819.7097546262622576058@ietfa.amsl.com> <C9C19E9D-233F-4A04-839D-31C7C99D07EF@jisc.ac.uk> <20171030194900.GB12994@cs-it-6805697.local>
In-Reply-To: <20171030194900.GB12994@cs-it-6805697.local>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3273)
x-originating-ip: [2001:a88:d510:1101:718e:a4e1:1d41:6dad]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1138; 20:ouie/tUL4Y2GhHV0sLNvzf0Sx1P9cuyMhqta72eM6eYiJrT8P0k89oLDPh7N8TRb3S2v+OajXfvzNg97X/IhaZE2nm9Lit80xizu/oxyFlRCCCLz/eyCDSXuMJnCH8KzgV0//gHtbRrFsurjPB/FiBk65cSOEQR4tZ8sF2f9um8=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 6cd4f3d2-7a42-4538-2706-08d51feac335
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(2017052603238); SRVR:AM3PR07MB1138; 
x-ms-traffictypediagnostic: AM3PR07MB1138:
x-exchange-antispam-report-test: UriScan:(274715658323672)(120809045254105);
x-microsoft-antispam-prvs: <AM3PR07MB1138665DD933CC8D9B0C5B96D6590@AM3PR07MB1138.eurprd07.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(3231020)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(3002001)(6041248)(20161123560025)(20161123558100)(20161123564025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123555025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM3PR07MB1138; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM3PR07MB1138; 
x-forefront-prvs: 0476D4AB88
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(376002)(346002)(377424004)(189002)(199003)(24454002)(68736007)(6916009)(305945005)(83716003)(86362001)(81166006)(76176999)(101416001)(5660300001)(81156014)(50986999)(50226002)(8936002)(2950100002)(8676002)(36756003)(3280700002)(2900100001)(33656002)(106356001)(5250100002)(7736002)(105586002)(3660700001)(6506006)(42882006)(229853002)(74482002)(189998001)(82746002)(6486002)(6436002)(2906002)(316002)(786003)(230783001)(966005)(478600001)(6246003)(4001150100001)(97736004)(25786009)(102836003)(57306001)(6116002)(72206003)(6512007)(14454004)(6306002)(53546010)(4326008)(99286003)(53936002)(24704002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1138; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <ACAD7F94ED755B4C9F28648BD7F8BAC4@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: 6cd4f3d2-7a42-4538-2706-08d51feac335
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2017 23:05:49.9860 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1138
X-MC-Unique: bjRGT-C1OW2N1r7H8z2tuA-1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/cHQcYkaReztDyWsSHUSwzAFFfPA>
Subject: Re: [MBONED] I-D Action: draft-acg-mboned-multicast-models-01.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 23:06:22 -0000

SGkgRGFsZSwNCg0KPiBPbiAzMCBPY3QgMjAxNywgYXQgMTk6NDksIERhbGUgVy4gQ2FyZGVyIDxk
d2NhcmRlckBlcy5uZXQ+IHdyb3RlOg0KPiANCj4gSGkgVGltLA0KPiANCj4gVGh1cyBzcGFrZSBU
aW0gQ2hvd24gKFRpbS5DaG93bkBqaXNjLmFjLnVrKSBvbiBNb24sIE9jdCAzMCwgMjAxNyBhdCAw
Mzo0MTowMlBNICswMDAwOg0KPj4gDQo+PiBUaGUgdGV4dCBvbiBtdWx0aWNhc3Qgc2VydmljZSBt
b2RlbHMgaGFzIGJlZW4gc2hvcnRlbmVkIGEgbGl0dGxlLCBhbmQgYSBuZXcgc2VjdGlvbiBhZGRl
ZCBvbiBBU00gZGVwcmVjYXRpb24uICBUaGUgdGV4dCBpcyBqdXN0IGEgc3RhcnRpbmcgcG9pbnQg
YmFzZWQgb24gd2hhdCBJIHRoaW5rIHRoZSBXRyBoYXMgc2FpZCwgYnV0IG9mIGNvdXJzZSBjb21t
ZW50cyBhbmQgc3VnZ2VzdGlvbnMgZm9yIGNoYW5nZXMgZXRjIGFyIHZlcnkgd2VsY29tZS4gIEhv
cGVmdWxseSBpdCB3aWxsIHByb3ZpZGUgYSBmb2N1cyBmb3Igc29tZSBkaXNjdXNzaW9uIGluIFNp
bmdhcG9yZS4NCj4gDQo+IEluIHNlY3Rpb24gMy4xLCB0aGVyZSdzIGEgcmVmZXJlbmNlIHRvIFJG
QzU3NzEsIGJ1dCBlaXRoZXIgdGhlcmUgb3IgaW4NCj4gc2VjdGlvbiA3LjUsIGl0IG1heSBiZSB3
b3J0aCBxdW90aW5nIHBhcnQgb2Ygc2VjdGlvbiA5IG9mIFJGQzU3NzEgDQo+IHBhcnRpY3VsYXJs
eToNCj4gICJEb21haW5zIHdpdGggYSAzMi1iaXQgQVNOIE1BWSBhcHBseSBmb3Igc3BhY2UgaW4g
QUQtSE9DIEJsb2NrIElJSSwgDQo+ICBvciBjb25zaWRlciB1c2luZyBJUHY2IG11bHRpY2FzdCBh
ZGRyZXNzZXMu4oCdDQoNCknigJlsbCBhZGQgdGhhdCwgdGhhbmtzLg0KDQo+IE15IHVuZGVyc3Rh
bmRpbmcgaXMgdGhhdCAzMi1iaXQgQVNOcyBhcmUgaW5jcmVhc2luZ2x5IGNvbW1vbiBpZiBub3Qg
dGhlDQo+IGRlZmF1bHQgbm93LCBzbyBJIHdvdWxkIHRoaW5rIHRoYXQgaXMgYWRkaXRpb25hbCBt
b3RpdmF0aW9uIHRvd2FyZHMgDQo+IHVzaW5nIFNTTSAoaWYgbm90IElQdjYgU1NNKS4NCg0KSW50
ZXJlc3RpbmcgcG9pbnQsIHdvdWxkIGJlIGludGVyZXN0aW5nIHRvIGRpZyBvdXQgc29tZSBudW1i
ZXJzIGZvciBhIGZ1dHVyZSB1cGRhdGUuDQoNClRpbQ0KDQo+IA0KPiBEYWxlDQo+IA0KPiANCj4+
IEJlZ2luIGZvcndhcmRlZCBtZXNzYWdlOg0KPj4gDQo+PiBGcm9tOiBpbnRlcm5ldC1kcmFmdHNA
aWV0Zi5vcmc8bWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZz4NCj4+IFN1YmplY3Q6IEkt
RCBBY3Rpb246IGRyYWZ0LWFjZy1tYm9uZWQtbXVsdGljYXN0LW1vZGVscy0wMS50eHQNCj4+IERh
dGU6IDMwIE9jdG9iZXIgMjAxNyBhdCAxNTozNDo1MSBHTVQNCj4+IFRvOiA8aS1kLWFubm91bmNl
QGlldGYub3JnPG1haWx0bzppLWQtYW5ub3VuY2VAaWV0Zi5vcmc+Pg0KPj4gUmVwbHktVG86IGlu
dGVybmV0LWRyYWZ0c0BpZXRmLm9yZzxtYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnPg0K
Pj4gDQo+PiANCj4+IEEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBv
bi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmllcy4NCj4+IA0KPj4gDQo+PiAgICAgICBU
aXRsZSAgICAgICAgICAgOiBEZXByZWNhdGluZyBBU00gZm9yIEludGVyZG9tYWluIE11bHRpY2Fz
dA0KPj4gICAgICAgQXV0aG9ycyAgICAgICAgIDogTWlrYWVsIEFicmFoYW1zc29uDQo+PiAgICAg
ICAgICAgICAgICAgICAgICAgICBUaW0gQ2hvd24NCj4+ICAgICAgICAgICAgICAgICAgICAgICAg
IExlbm55IEdpdWxpYW5vDQo+PiBGaWxlbmFtZSAgICAgICAgOiBkcmFmdC1hY2ctbWJvbmVkLW11
bHRpY2FzdC1tb2RlbHMtMDEudHh0DQo+PiBQYWdlcyAgICAgICAgICAgOiAxNQ0KPj4gRGF0ZSAg
ICAgICAgICAgIDogMjAxNy0xMC0zMA0KPj4gDQo+PiBBYnN0cmFjdDoNCj4+ICBUaGlzIGRvY3Vt
ZW50IHByb3ZpZGVzIGEgaGlnaC1sZXZlbCBvdmVydmlldyBvZiBtb3JlIGNvbW1vbmx5IHVzZWQN
Cj4+ICBtdWx0aWNhc3Qgc2VydmljZSBtb2RlbHMsIHByaW5jaXBhbGx5IHRoZSBBbnktU291cmNl
IE11bHRpY2FzdCAoQVNNKQ0KPj4gIGFuZCBTb3VyY2UtU3BlY2lmaWMgTXVsdGljYXN0IChTU00p
IG1vZGVscywgYW5kIGRpc2N1c3NlcyB0aGUNCj4+ICBhcHBsaWNhYmlsaXR5IG9mIHRoZSBtb2Rl
bHMgdG8gY2VydGFpbiBzY2VuYXJpb3MuICBBcyBhIHJlc3VsdCwgdGhpcw0KPj4gIGRvY3VtZW50
IHJlY29tbWVuZHMgdGhhdCBBU00gaXMgbm90IHVzZWQgZm9yIGludGVyZG9tYWluIHNjZW5hcmlv
cywNCj4+ICBhbmQgdGhlIHVzZSBvZiBTU00gaXMgc3Ryb25nbHkgcmVjb21tZW5kZWQgZm9yIGFs
bCBtdWx0aWNhc3QNCj4+ICBzY2VuYXJpb3MuDQo+PiANCj4+IA0KPj4gVGhlIElFVEYgZGF0YXRy
YWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRoaXMgZHJhZnQgaXM6DQo+PiBodHRwczovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RvYy9kcmFmdC1hY2ctbWJvbmVkLW11bHRpY2FzdC1tb2RlbHMvDQo+PiAN
Cj4+IFRoZXJlIGFyZSBhbHNvIGh0bWxpemVkIHZlcnNpb25zIGF2YWlsYWJsZSBhdDoNCj4+IGh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1hY2ctbWJvbmVkLW11bHRpY2FzdC1tb2Rl
bHMtMDENCj4+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2h0bWwvZHJhZnQtYWNn
LW1ib25lZC1tdWx0aWNhc3QtbW9kZWxzLTAxDQo+PiANCj4+IEEgZGlmZiBmcm9tIHRoZSBwcmV2
aW91cyB2ZXJzaW9uIGlzIGF2YWlsYWJsZSBhdDoNCj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL3Jm
Y2RpZmY/dXJsMj1kcmFmdC1hY2ctbWJvbmVkLW11bHRpY2FzdC1tb2RlbHMtMDENCj4+IA0KPj4g
DQo+PiBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJv
bSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQo+PiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBh
bmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KPj4gDQo+PiBJbnRlcm5l
dC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQo+PiBmdHA6
Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPj4gDQo+PiBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gSS1ELUFubm91bmNlIG1haWxpbmcg
bGlzdA0KPj4gSS1ELUFubm91bmNlQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2ktZC1hbm5vdW5jZQ0KPj4gSW50ZXJuZXQtRHJhZnQgZGlyZWN0b3Jp
ZXM6IGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwNCj4+IG9yIGZ0cDovL2Z0cC5pZXRm
Lm9yZy9pZXRmLzFzaGFkb3ctc2l0ZXMudHh0DQo+PiANCj4gDQo+PiBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gTUJPTkVEIG1haWxpbmcgbGlzdA0K
Pj4gTUJPTkVEQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL21ib25lZA0KPiANCg0K


From nobody Mon Oct 30 16:23:25 2017
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C01313F586 for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 16:23:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.319
X-Spam-Level: 
X-Spam-Status: No, score=-4.319 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_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 p7dsLjalcmAz for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 16:23:21 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE36813AF75 for <mboned@ietf.org>; Mon, 30 Oct 2017 16:23:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1509405799; h=from:subject:date:message-id:to:mime-version:content-type:references; bh=y4Jc/ofX/HDKJyDnGVbUdLHYetlZ05Qr+G20CK4aC7w=; b=NCawqFHmtEC5nNCtILHz8ZIjl2h0Con8m0s0bpfikrXOTNdmg8/DBzLrl542tFF57Af1cMx9GxLl7b6rYJTYLIcXQDyDJ6cDmQDO9I4BDjHvYvSv2TOSwaPPIeLXgCjjrdKk34rbkTNrBccde/SXeG6dN+VJ0YdofMC5JXsouxw=
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01lp0213.outbound.protection.outlook.com [213.199.154.213]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-27-ERfYTuf1Mxa2nRKSbbOwoQ-1; Mon, 30 Oct 2017 23:23:16 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.197.4; Mon, 30 Oct 2017 23:23:14 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::f008:dc81:4b84:fd23]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::f008:dc81:4b84:fd23%14]) with mapi id 15.20.0197.011; Mon, 30 Oct 2017 23:23:14 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: MBONED WG <mboned@ietf.org>
Thread-Topic: I-D Action: draft-acg-mboned-multicast-models-02.txt
Thread-Index: AQHTUdYOqU0dK+jzYE2Aawd+iPMOXw==
Date: Mon, 30 Oct 2017 23:23:14 +0000
Message-ID: <C54D2DC2-6EA7-41D2-BEC2-81A27BC202BF@jisc.ac.uk>
References: <150940561832.28310.1470763748333970243@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3273)
x-originating-ip: [2001:a88:d510:1101:718e:a4e1:1d41:6dad]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1140; 20:B4gGN8I6ukk5ss7sK6qrk+63drqLfIfAu3flIwNkc5nMze58QUnVxi19L8CET7jk+F8eU6yOcxC2Oa0Dg3yOsxqIk0t7Q+MQ7YY50Ft3T+GkXNz8+RRTIte8JezAJmAeAZsjivC29Csh7pF4sMrvpx3zl9tPk4gvReVY/ITEhYg=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 86fc9bcf-50bc-48b7-2cdf-08d51fed319a
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(2017052603199); SRVR:AM3PR07MB1140; 
x-ms-traffictypediagnostic: AM3PR07MB1140:
x-exchange-antispam-report-test: UriScan:(120809045254105);
x-microsoft-antispam-prvs: <AM3PR07MB1140F606C2A409C18E383A97D6590@AM3PR07MB1140.eurprd07.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231020)(100000703101)(100105400095)(6041248)(20161123562025)(20161123558100)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123555025)(20161123564025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM3PR07MB1140; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM3PR07MB1140; 
x-forefront-prvs: 0476D4AB88
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(199003)(189002)(377424004)(7736002)(229853002)(8936002)(6306002)(74482002)(81166006)(83716003)(54896002)(4001150100001)(6486002)(966005)(68736007)(786003)(2473003)(101416001)(236005)(6512007)(5660300001)(97736004)(99286003)(189998001)(2900100001)(230783001)(86362001)(6916009)(106356001)(105586002)(6436002)(42882006)(6506006)(50226002)(57306001)(14454004)(53936002)(36756003)(33656002)(478600001)(606006)(82746002)(72206003)(2906002)(3280700002)(3660700001)(81156014)(50986999)(76176999)(102836003)(8676002)(5250100002)(25786009)(316002)(6116002)(24704002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1140; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: 86fc9bcf-50bc-48b7-2cdf-08d51fed319a
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2017 23:23:14.2066 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1140
X-MC-Unique: ERfYTuf1Mxa2nRKSbbOwoQ-1
Content-Type: multipart/alternative; boundary="_000_C54D2DC26EA741D2BEC281A27BC202BFjiscacuk_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/paqnRYsqLeyIQGU5ygGxmBfOM_E>
Subject: [MBONED] Fwd: I-D Action: draft-acg-mboned-multicast-models-02.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 23:23:23 -0000

--_000_C54D2DC26EA741D2BEC281A27BC202BFjiscacuk_
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

Hi,

This -02 update on the earlier -01 version today includes some minor commen=
ts from two people, and some minor edits and typo corrections.

Hopefully this version can help provoke further discussion in Singapore on =
what we mean by deprecating inter domain multicast, alongside a strong reco=
mmendation to use SSM in general.

Tim

Begin forwarded message:

From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
Subject: I-D Action: draft-acg-mboned-multicast-models-02.txt
Date: 30 October 2017 at 23:20:18 GMT
To: <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
Reply-To: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.


       Title           : Deprecating ASM for Interdomain Multicast
       Authors         : Mikael Abrahamsson
                         Tim Chown
                         Lenny Giuliano
Filename        : draft-acg-mboned-multicast-models-02.txt
Pages           : 15
Date            : 2017-10-30

Abstract:
  This document provides a high-level overview of more commonly used
  multicast service models, principally the Any-Source Multicast (ASM)
  and Source-Specific Multicast (SSM) models, and discusses the
  applicability of the models to certain scenarios.  As a result, this
  document recommends that ASM is not used for interdomain scenarios,
  and the use of SSM is strongly recommended for all multicast
  scenarios.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-acg-mboned-multicast-models/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-acg-mboned-multicast-models-02
https://datatracker.ietf.org/doc/html/draft-acg-mboned-multicast-models-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-acg-mboned-multicast-models-02


Please note that it may take a couple of minutes from the time of submissio=
n
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/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


--_000_C54D2DC26EA741D2BEC281A27BC202BFjiscacuk_
Content-Type: text/html; charset=WINDOWS-1252
Content-ID: <E809B13F8C1E534588CBA631E20EA4EA@eurprd07.prod.outlook.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;" class=3D"">
Hi,
<div class=3D""><br class=3D"">
</div>
<div class=3D"">This -02 update on the earlier -01 version today includes s=
ome minor comments from two people, and some minor edits and typo correctio=
ns.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Hopefully this version can help provoke further discussion =
in Singapore on what we mean by deprecating inter domain multicast, alongsi=
de a strong recommendation to use SSM in general.</div>
<div class=3D""><br class=3D"">
<div class=3D"">
<div class=3D"">Tim&nbsp;</div>
<div class=3D""><br class=3D"">
</div>
</div>
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><a href=3D"mailto:internet-drafts@ietf.=
org" class=3D"">internet-drafts@ietf.org</a><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><b class=3D"">I-D Action: draft-acg-mbo=
ned-multicast-models-02.txt</b><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">30 October 2017 at 23:20:18 GMT<br clas=
s=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">&lt;<a href=3D"mailto:i-d-announce@ietf=
.org" class=3D"">i-d-announce@ietf.org</a>&gt;<br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Reply-To:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><a href=3D"mailto:internet-drafts@ietf.=
org" class=3D"">internet-drafts@ietf.org</a><br class=3D"">
</span></div>
<br class=3D"">
<div class=3D"">
<div class=3D""><br class=3D"">
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br class=3D"">
<br class=3D"">
<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Deprecating ASM for Interdomain Multicas=
t<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Authors &nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;: Mikael Abrahamsson<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Tim Chown<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Lenny Giuliano<br class=3D"">
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Filename &n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-acg-mboned-multicast-models=
-02.txt<br class=3D"">
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Pages &nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 15<br class=3D"">
<span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Date &nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2017-10-30<br=
 class=3D"">
<br class=3D"">
Abstract:<br class=3D"">
&nbsp;&nbsp;This document provides a high-level overview of more commonly u=
sed<br class=3D"">
&nbsp;&nbsp;multicast service models, principally the Any-Source Multicast =
(ASM)<br class=3D"">
&nbsp;&nbsp;and Source-Specific Multicast (SSM) models, and discusses the<b=
r class=3D"">
&nbsp;&nbsp;applicability of the models to certain scenarios. &nbsp;As a re=
sult, this<br class=3D"">
&nbsp;&nbsp;document recommends that ASM is not used for interdomain scenar=
ios,<br class=3D"">
&nbsp;&nbsp;and the use of SSM is strongly recommended for all multicast<br=
 class=3D"">
&nbsp;&nbsp;scenarios.<br class=3D"">
<br class=3D"">
<br class=3D"">
The IETF datatracker status page for this draft is:<br class=3D"">
<a href=3D"https://datatracker.ietf.org/doc/draft-acg-mboned-multicast-mode=
ls/" class=3D"">https://datatracker.ietf.org/doc/draft-acg-mboned-multicast=
-models/</a><br class=3D"">
<br class=3D"">
There are also htmlized versions available at:<br class=3D"">
https://tools.ietf.org/html/draft-acg-mboned-multicast-models-02<br class=
=3D"">
https://datatracker.ietf.org/doc/html/draft-acg-mboned-multicast-models-02<=
br class=3D"">
<br class=3D"">
A diff from the previous version is available at:<br class=3D"">
https://www.ietf.org/rfcdiff?url2=3Ddraft-acg-mboned-multicast-models-02<br=
 class=3D"">
<br class=3D"">
<br class=3D"">
Please note that it may take a couple of minutes from the time of submissio=
n<br class=3D"">
until the htmlized version and diff are available at tools.ietf.org.<br cla=
ss=3D"">
<br class=3D"">
Internet-Drafts are also available by anonymous FTP at:<br class=3D"">
ftp://ftp.ietf.org/internet-drafts/<br class=3D"">
<br class=3D"">
_______________________________________________<br class=3D"">
I-D-Announce mailing list<br class=3D"">
I-D-Announce@ietf.org<br class=3D"">
https://www.ietf.org/mailman/listinfo/i-d-announce<br class=3D"">
Internet-Draft directories: http://www.ietf.org/shadow.html<br class=3D"">
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt<br class=3D"">
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</body>
</html>

--_000_C54D2DC26EA741D2BEC281A27BC202BFjiscacuk_--


From nobody Mon Oct 30 16:42:17 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D00D13F623; Mon, 30 Oct 2017 16:42:11 -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: mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150940693116.28209.15702031793560851677@ietfa.amsl.com>
Date: Mon, 30 Oct 2017 16:42:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/POufoPuLWADynczNeGYIwhvgIec>
Subject: [MBONED] I-D Action: draft-ietf-mboned-interdomain-peering-bcp-14.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 23:42:11 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the MBONE Deployment WG of the IETF.

        Title           : Use of Multicast Across Inter-Domain Peering Points
        Authors         : Percy S. Tarapore
                          Robert Sayko
                          Greg Shepherd
                          Toerless Eckert
                          Ram Krishnan
	Filename        : draft-ietf-mboned-interdomain-peering-bcp-14.txt
	Pages           : 41
	Date            : 2017-10-30

Abstract:
   This document examines the use of Source Specific Multicast (SSM)
   across inter-domain peering points for a specified set of deployment
   scenarios.  The objective is to describe the setup process for
   multicast-based delivery across administrative domains for these
   scenarios and document supporting functionality to enable this
   process.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mboned-interdomain-peering-bcp-14
https://datatracker.ietf.org/doc/html/draft-ietf-mboned-interdomain-peering-bcp-14

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-interdomain-peering-bcp-14


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 Oct 30 16:48:30 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF16C184; Mon, 30 Oct 2017 16:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 hUfMHR1cR6el; Mon, 30 Oct 2017 16:48:21 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC38513F886; Mon, 30 Oct 2017 16:48:18 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 9FC4258C4EA; Tue, 31 Oct 2017 00:48:14 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 7E3F3B0D023; Tue, 31 Oct 2017 00:48:14 +0100 (CET)
Date: Tue, 31 Oct 2017 00:48:14 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Cc: draft-ietf-mboned-interdomain-peering-bcp@ietf.org, tim.chown@jisc.ac.uk, The IESG <iesg@ietf.org>, mboned@ietf.org, Toerless Eckert <tte+ietf@cs.fau.de>, mboned-chairs@ietf.org
Message-ID: <20171030234814.GA6469@faui40p.informatik.uni-erlangen.de>
References: <20171028000507.GA22613@faui40p.informatik.uni-erlangen.de> <F7148970-2AB8-4B29-BF65-C67C58770B4E@kuehlewind.net> <20171030171453.GA28098@faui40p.informatik.uni-erlangen.de> <DA86A6FD-CD81-4248-8D65-2B60A28AABB0@kuehlewind.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DA86A6FD-CD81-4248-8D65-2B60A28AABB0@kuehlewind.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/9ANr5pIFiH7IIxWEqh9ZL_CM4OE>
Subject: Re: [MBONED] Mirja K?hlewind's No Objection on draft-ietf-mboned-interdomain-peering-bcp-11: (with COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 23:48:29 -0000

Thanks!

8085 actually does have a lot of normative language, can't quite remember whether
it has the actual magic sentence (not controlled network ->MUST CC). If not, thats too bad.

At the off-chance one of the three remaining IESG members with discuss will be happy 
before the window for posting opens in Singapore, i've just pushed out -14 with the should->must
fix.

http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-13.txt&url2=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-14.txt

Cheers
    Toerless


On Mon, Oct 30, 2017 at 10:51:01PM +0100, Mirja Kuehlewind (IETF) wrote:
> Hi Toerless,
> 
> I didn???t realize that there is no normative language in the draft. In this case lower case must is fine. I guess you can point to rfc8085, however, there is also no MUST, just more guidance. 
> 
> Mirja
> 
> 
> > Am 30.10.2017 um 18:14 schrieb Toerless Eckert <tte@cs.fau.de>:
> > 
> > Thanks, Mirja
> > 
> > Definitely "must" in second point, sorry.
> > 
> > Wrt.: MUST My issue is that this BCP was not written with
> > RFC2119 capitalization in mind and not vetted for it. If i change
> > must=>MUST in just two places (and introduce reference to RFC2119,
> > it looks out of place for the rest of the document, but doing capitalization
> > throughout the document, would require a lot more work and repeated review i fear.
> > 
> > Would it be possible to avoid 2119 language by adding behind both
> > places references that mandate this ("this is not the law, but look up the law" )?
> > 
> > Eg:
> >  Like IP unicast traffic, IP multicast traffic carried across non-
> >  controlled networks must comply to Congestion Control Principles
> >  (the normative place mandating this compliance is RFCxxxx, section y.z).
> > 
> > If you think this would work and had some xxxx,y,z for me, that would be great.
> > 
> > Otherwise i will do the MUST and RFC2119 header and pray to the IAB and
> > IESG that this will not raise a lot of followup capitalization requests.
> > 
> > Cheers
> >    Toerless
> > 
> > On Mon, Oct 30, 2017 at 12:59:42PM +0100, Mirja Kuehlewind (IETF) wrote:
> >> Hi Toerless,
> >> 
> >> thanks for addressing my discuss in such detail. The new text is great. Maybe one little change:
> >> 
> >> OLD:
> >>   Like IP unicast traffic, IP multicast traffic carried across non-
> >>   controlled networks must comply to Congestion Control Principles...
> >> NOW
> >>   Like IP unicast traffic, IP multicast traffic carried across non-
> >>   controlled networks MUST comply to Congestion Control Principles???
> >> 
> >> Also I would still like to see that the respective text in section 3.1 is slightly rephrased to match this:
> >> 
> >> OLD:
> >>      b. If the peering point between AD-1 and AD-2 is a controlled
> >>        network environment, then bandwidth can be allocated
> >>        accordingly by the two domains to permit the transit of non-
> >>        rate adaptive multicast traffic. If this is not the case, then
> >>        it is recommended that the multicast traffic should support
> >>        rate-adaption.
> >> Proposed NEW:
> >>      b. If the peering point between AD-1 and AD-2 is a controlled
> >>        network environment, then bandwidth can be allocated
> >>        accordingly by the two domains to permit the transit of non-
> >>        rate adaptive multicast traffic. If this is not the case, then
> >>        the multicast traffic MUST also support rate-adaption.
> >> 
> >> Thanks!
> >> Mirja
> >> 
> >> 
> >> 
> >>> Am 28.10.2017 um 02:05 schrieb Toerless Eckert <tte+ietf@cs.fau.de>:
> >>> 
> >>> [The following text up to the individual reply comments is identical for 
> >>> the replies to all ballot comments. I originally wanted to coalesce the reply to
> >>> all positions into one email but the auto-generated header from datatracker
> >>> makes it sound as if per-submitter replied are required. So, here we go with some
> >>> repeated text followed by more individualized text:]
> >>> 
> >>> Dear Reviewer,
> >>> 
> >>> This is in response of your reviews of
> >>>   https://www.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-11.txt
> >>> as entered in the ballot:
> >>>   https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/ballot/
> >>> 
> >>> A version of this email containing replies to all IESG feedback for -11 is also in: 
> >>>   https://raw.githubusercontent.com/toerless/peering-bcp/master/11-iesg-review-reply.txt
> >>> 
> >>> Thank you so much for your thorough review. In response to the IESG
> >>> feedback, version -12 and -13 of the draft where posted which we hope 
> >>> will resolve the open issues.
> >>> make 2
> >>> 
> >>> Version -12 of the draft was just a conversion from docx generated txt to XML (previous generations
> >>> where not built from XML), this introduced formatting changes (line wraps etc.) that rfcdiff can not ignore
> >>> and that would have obfuscated actual content changes. 
> >>> 
> >>> Version -13 of the draft contains the text changes done in response to your
> >>> comments and discusses. The following RFC diff shows the content diffs
> >>> vs. -11 without any formatting introduced changes:
> >>> 
> >>> http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-12.txt&url2=https://tools.ietf.org/id/draft-ietf-mboned-interdomain-peering-bcp-13.txt
> >>> 
> >>> In summary:
> >>>  Beside the various smaller fixups from comments, the mayor rewritten/new blocks are:
> >>> 
> >>>  4.1.1 - bandwidth management (aka: congestion control section). 
> >>>          I didn't just want to put the magic CC sentence in but wanted to let
> >>>          readers understand what it means in the context of specifically
> >>>  6. Security considerations
> >>>     6.1.  DoS attacks (against state and bandwidth)	
> >>>     6.2.  Content security	
> >>>     6.3.  Peering encryption
> >>>     6.4.  Operational Aspects
> >>>           This is where the securing of log exchange is discussed.
> >>>  7. Privacy Considerations
> >>>     Got somewhat longer to explain because the specifics of multicast content and privacy
> >>>     are likely not that obious to non-multicast  experienced readers, and given how this
> >>>     is a BCP and i don't even think we did describe this anywhere else, it had to be
> >>>     explanatory.
> >>> 
> >>>  4.2.4.  Public Peering Routing Aspects
> >>>     text did mention non-private peerings, but i was afraid that readers would not
> >>>     understand the problematic implications, so i detailled them given how those
> >>>     peering L2 domains are still common for unicast.
> >>> 
> >>> 
> >>> Cheers
> >>>   Toerless for the Authors
> >>> 
> >>> =====================================================================================
> >>> Mirja Kuehlewind:
> >>> 
> >>> 
> >>>> Sorry for this last minute discuss but I would like to emphasize the points made in the tsv-art review on congestion/rate control (Thanks Yoshi!):
> >>> 
> >>>> Please provide stronger guidance (MUST) on the use of rate/congestion control in these two cases:
> >>>> 
> >>>> In Section 3.1:
> >>>>   " If the peering point between AD-1 and AD-2 is a controlled
> >>>>  network environment, then bandwidth can be allocated
> >>>>  accordingly by the two domains to permit the transit of non-
> >>>>  rate adaptive multicast traffic. If this is not the case, then
> >>>>  it is recommended that the multicast traffic should support
> >>>>  rate-adaption."
> >>>> 
> >>>> In Section 4.1,
> >>>>    "When determining the appropriate bandwidth allocation, parties should consider use
> >>>>      of a multicast protocol suitable for live video streaming that
> >>>>      is consistent with Congestion Control Principles [BCP41]."
> >>> 
> >>> I tried to fix this text a bit more comprehensively:
> >>> - removed text from 3.1. The CC requirements apply to every subsection of 3 (3.x)
> >>> and it duplicates partial text in 4.1, so a random mentioning in 3.1 was not
> >>> helpfull.
> >>> - Moved CC text from 4.1 to dedicated section 4.1.1 and made it a lot more explanatory
> >>> because in my past experience most readers do not really understand our cryptic
> >>> rules alone ("CC principles across non-controlled network paths"). Also added
> >>> reference to the fresh BCP145.
> >>> 
> >>> Please re-read new section and let me know what you think.
> >>> 
> >>>> Minor questions/comments:
> >>>> 
> >>>> 1) Section 3.4 also says:
> >>>> "Highly efficient use of bandwidth in AD-1."
> >>>> But aren't packets eventually duplicated in this case in AD-1? I guess it's more efficient than replicating them at the network border but might be still less efficient than native multicast in the whole network, no?
> >>> 
> >>> Changed to:
> >>> <t>Efficient use of bandwidth in AD-1 (The closer AR is to uBR, the more efficient).</t>
> >>> 
> >>>> 2) section 4.3.3 says:
> >>>> "The two AD's may supply additional security logs..."
> >>>> This seems to be a general action not specific to multicast or the scenarios described in this doc.
> >>> 
> >>> Yes, i thought about this and came up with the following explanation:
> >>> 
> >>>  <t>Note that except for implied multicast specific elements,
> >>>  the options listed here are not unique or novel for IP multicast, but
> >>>  they are more important for services novel to the operators than for
> >>>  operationally well established services (such as unicast).  Therefore
> >>>  we detail them as follows:</t>
> >>> 
> >>>> 3) I don't think the conclusion section (8) is helpful or needed. If you want to keep it at all, this text could be moved into the introduction.
> >>> 
> >>> Removed - for the time being. I was told that having a wrap up in documents is
> >>> always a good way to reflect on the document, but i agree the existing text
> >>> is more distracting than helpful.
> >>> 
> > 
> > -- 
> > ---
> > tte@cs.fau.de
> > 

-- 
---
tte@cs.fau.de


From nobody Mon Oct 30 17:45:34 2017
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65E0313B144 for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 17:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 WDVDC-gmxuHa for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 17:45:30 -0700 (PDT)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C86A3138DE1 for <mboned@ietf.org>; Mon, 30 Oct 2017 17:45:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v9V0jUnU018050; Mon, 30 Oct 2017 17:45:30 -0700
Received: from XCH15-06-09.nw.nos.boeing.com (xch15-06-09.nw.nos.boeing.com [137.136.239.172]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v9V0jN7A018034 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 30 Oct 2017 17:45:24 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-09.nw.nos.boeing.com (2002:8988:efac::8988:efac) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 30 Oct 2017 17:45:23 -0700
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1320.000; Mon, 30 Oct 2017 17:45:22 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Tim Chown <Tim.Chown@jisc.ac.uk>, MBONED WG <mboned@ietf.org>
Thread-Topic: I-D Action: draft-acg-mboned-multicast-models-02.txt
Thread-Index: AQHTUdYOqU0dK+jzYE2Aawd+iPMOX6L9EzeA
Date: Tue, 31 Oct 2017 00:45:22 +0000
Message-ID: <9563781e07234ac7919ecaf64b02073e@XCH15-06-11.nw.nos.boeing.com>
References: <150940561832.28310.1470763748333970243@ietfa.amsl.com> <C54D2DC2-6EA7-41D2-BEC2-81A27BC202BF@jisc.ac.uk>
In-Reply-To: <C54D2DC2-6EA7-41D2-BEC2-81A27BC202BF@jisc.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: multipart/alternative; boundary="_000_9563781e07234ac7919ecaf64b02073eXCH150611nwnosboeingcom_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/9XK7BLgLu0BU2P5X_Gj_JdN8jAs>
Subject: Re: [MBONED] I-D Action: draft-acg-mboned-multicast-models-02.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2017 00:45:33 -0000

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

While I can fully appreciate why in interdomain multicast PIM-SSM is much e=
asier to deal with that PIM-SM, and that therefore in interdomain multicast=
 it makes sense to deprecate ASM, I don't think we should go too far with t=
his. There are uses of multicast that specifically want to avoid having the=
 destinations know the source(s), which is often exactly why multicast is u=
sed!

So I do not think the IETF should strongly recommend against ASM, in genera=
l. This kind of strong recommendation gets in the hands of the "wrong peopl=
e," and then the job at hand becomes that much more difficult.

With respect to Section 7:

7.  Recommendations on ASM and SSM deployment

   This document recommends that the use of interdomain ASM is
   deprecated, i.e., only SSM is to be used for interdomain multicast.
   Further, it also strongly recommends the use of SSM for all multicast
   scenarios, be they run inter or intradomain.

I think that in practice, interdomain multicast is now being discouraged fo=
r security reasons. Conversely, ASM, within a single domain remains very us=
eful. That's why I'd be uncomfortable with a blanket condemnation of ASM.

For interdomain multicast, more manual schemes, such as proxy IGMP, can be =
used if necessary, especially when security is an issue. We want to avoid a=
ny chance of some unknown multicast entering a domain. The downside of SSM =
will depend on how multicast is used. So for example, in Section 7.3:

   However, it is strongly recommended that sites using ASM internally
   conduct an audit of the multicast applications used, and begin
   planning a migration to using SSM instead wherever possible.

No, honestly, this is none of the IETF's business? Everything depends on us=
e case. In a control system scenario, ASM may well be used specifically bec=
ause knowing the source is what one wants to avoid. A bit like using anycas=
t. Sometimes, it's one of the main reasons to use multicast. For instance, =
many hosts need the information simultaneously, and the source depends on m=
odes of operation, and is likely to change. Or, also frequently, multicast =
is used for status messages from many sources, some or all of which have re=
dundant interfaces. So having every host configured to know all the possibl=
e sources, and join all of the possible multicast groups, becomes a huge pa=
in. Hardly "simpler" than ASM.

In short, my preference would be to avoid string blanket recommendations, a=
gainst ASM, within a single domain.

Bert


From: MBONED [mailto:mboned-bounces@ietf.org] On Behalf Of Tim Chown
Sent: Monday, October 30, 2017 19:23
To: MBONED WG <mboned@ietf.org>
Subject: [MBONED] Fwd: I-D Action: draft-acg-mboned-multicast-models-02.txt

Hi,

This -02 update on the earlier -01 version today includes some minor commen=
ts from two people, and some minor edits and typo corrections.

Hopefully this version can help provoke further discussion in Singapore on =
what we mean by deprecating inter domain multicast, alongside a strong reco=
mmendation to use SSM in general.

Tim

Begin forwarded message:

From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
Subject: I-D Action: draft-acg-mboned-multicast-models-02.txt
Date: 30 October 2017 at 23:20:18 GMT
To: <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
Reply-To: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.


       Title           : Deprecating ASM for Interdomain Multicast
       Authors         : Mikael Abrahamsson
                         Tim Chown
                         Lenny Giuliano
Filename        : draft-acg-mboned-multicast-models-02.txt
Pages           : 15
Date            : 2017-10-30

Abstract:
  This document provides a high-level overview of more commonly used
  multicast service models, principally the Any-Source Multicast (ASM)
  and Source-Specific Multicast (SSM) models, and discusses the
  applicability of the models to certain scenarios.  As a result, this
  document recommends that ASM is not used for interdomain scenarios,
  and the use of SSM is strongly recommended for all multicast
  scenarios.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-acg-mboned-multicast-models/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-acg-mboned-multicast-models-02
https://datatracker.ietf.org/doc/html/draft-acg-mboned-multicast-models-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-acg-mboned-multicast-models-02


Please note that it may take a couple of minutes from the time of submissio=
n
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/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org<mailto:I-D-Announce@ietf.org>
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Times New Roman",serif;
	color:#0E25D0;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0">While=
 I can fully appreciate why in interdomain multicast PIM-SSM is much easier=
 to deal with that PIM-SM, and that therefore in interdomain multicast it m=
akes sense to deprecate ASM, I don&#8217;t
 think we should go too far with this. There are uses of multicast that spe=
cifically want to avoid having the destinations know the source(s), which i=
s often exactly why multicast is used!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0">So I =
do not think the IETF should strongly recommend against ASM, in general. Th=
is kind of strong recommendation gets in the hands of the &#8220;wrong peop=
le,&#8221; and then the job at hand becomes that
 much more difficult.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0">With =
respect to Section 7:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:11.0pt;color:#0=
E25D0"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:11.0pt;color:#0=
E25D0">7.&nbsp; Recommendations on ASM and SSM deployment<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:11.0pt;color:#0=
E25D0"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:11.0pt;color:#0=
E25D0">&nbsp;&nbsp; This document recommends that the use of interdomain AS=
M is<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:11.0pt;color:#0=
E25D0">&nbsp;&nbsp; deprecated, i.e., only SSM is to be used for interdomai=
n multicast.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:11.0pt;color:#0=
E25D0">&nbsp;&nbsp; Further, it also strongly recommends the use of SSM for=
 all multicast<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:11.0pt;color:#0=
E25D0">&nbsp;&nbsp; scenarios, be they run inter or intradomain.<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0">I thi=
nk that in practice, interdomain multicast is now being discouraged for sec=
urity reasons. Conversely, ASM, within a single domain remains very useful.=
 That&#8217;s why I&#8217;d be uncomfortable with
 a blanket condemnation of ASM.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0">For i=
nterdomain multicast, more manual schemes, such as proxy IGMP, can be used =
if necessary, especially when security is an issue. We want to avoid any ch=
ance of some unknown multicast entering
 a domain. The downside of SSM will depend on how multicast is used. So for=
 example, in Section 7.3:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:11.0pt;color:#0=
E25D0">&nbsp;&nbsp; However, it is strongly recommended that sites using AS=
M internally<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:11.0pt;color:#0=
E25D0">&nbsp;&nbsp; conduct an audit of the multicast applications used, an=
d begin<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:11.0pt;color:#0=
E25D0">&nbsp;&nbsp; planning a migration to using SSM instead wherever poss=
ible.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0">No, h=
onestly, this is none of the IETF&#8217;s business? Everything depends on u=
se case. In a control system scenario, ASM may well be used specifically be=
cause knowing the source is what one wants
 to avoid. A bit like using anycast. Sometimes, it&#8217;s one of the main =
reasons to use multicast. For instance, many hosts need the information sim=
ultaneously, and the source depends on modes of operation, and is likely to=
 change. Or, also frequently, multicast
 is used for status messages from many sources, some or all of which have r=
edundant interfaces. So having every host configured to know all the possib=
le sources, and join all of the possible multicast groups, becomes a huge p=
ain. Hardly &#8220;simpler&#8221; than ASM.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0">In sh=
ort, my preference would be to avoid string blanket recommendations, agains=
t ASM, within a single domain.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0">Bert<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> MBONED [mailto:mboned-bounces@=
ietf.org]
<b>On Behalf Of </b>Tim Chown<br>
<b>Sent:</b> Monday, October 30, 2017 19:23<br>
<b>To:</b> MBONED WG &lt;mboned@ietf.org&gt; <br>
<b>Subject:</b> [MBONED] Fwd: I-D Action: draft-acg-mboned-multicast-models=
-02.txt<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi, <o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This -02 update on the earlier -01 version today inc=
ludes some minor comments from two people, and some minor edits and typo co=
rrections.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Hopefully this version can help provoke further disc=
ussion in Singapore on what we mean by deprecating inter domain multicast, =
alongside a strong recommendation to use SSM in general.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">Tim&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">Begin forwarded message:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;Helvetica&quot;,=
sans-serif">From: </span>
</b><span style=3D"font-family:&quot;Helvetica&quot;,sans-serif"><a href=3D=
"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></span><o:p><=
/o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;Helvetica&quot;,=
sans-serif">Subject: I-D Action: draft-acg-mboned-multicast-models-02.txt</=
span></b><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;Helvetica&quot;,=
sans-serif">Date: </span>
</b><span style=3D"font-family:&quot;Helvetica&quot;,sans-serif">30 October=
 2017 at 23:20:18 GMT</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;Helvetica&quot;,=
sans-serif">To: </span>
</b><span style=3D"font-family:&quot;Helvetica&quot;,sans-serif">&lt;<a hre=
f=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a>&gt;</span><o:p=
></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;Helvetica&quot;,=
sans-serif">Reply-To:
</span></b><span style=3D"font-family:&quot;Helvetica&quot;,sans-serif"><a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></span=
><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Deprecating ASM for Interdomain Multicas=
t<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Authors &nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;: Mikael Abrahamsson<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Tim Chown<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Lenny Giuliano<br>
Filename &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-acg-mboned-multi=
cast-models-02.txt<br>
Pages &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 15<br>
Date &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 20=
17-10-30<br>
<br>
Abstract:<br>
&nbsp;&nbsp;This document provides a high-level overview of more commonly u=
sed<br>
&nbsp;&nbsp;multicast service models, principally the Any-Source Multicast =
(ASM)<br>
&nbsp;&nbsp;and Source-Specific Multicast (SSM) models, and discusses the<b=
r>
&nbsp;&nbsp;applicability of the models to certain scenarios. &nbsp;As a re=
sult, this<br>
&nbsp;&nbsp;document recommends that ASM is not used for interdomain scenar=
ios,<br>
&nbsp;&nbsp;and the use of SSM is strongly recommended for all multicast<br=
>
&nbsp;&nbsp;scenarios.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-acg-mboned-multicast-mode=
ls/">https://datatracker.ietf.org/doc/draft-acg-mboned-multicast-models/</a=
><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-acg-mboned-multicast-models-02=
">https://tools.ietf.org/html/draft-acg-mboned-multicast-models-02</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-acg-mboned-multicast=
-models-02">https://datatracker.ietf.org/doc/html/draft-acg-mboned-multicas=
t-models-02</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-acg-mboned-multicast-m=
odels-02">https://www.ietf.org/rfcdiff?url2=3Ddraft-acg-mboned-multicast-mo=
dels-02</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at tools.ietf.org.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet=
-drafts/</a><br>
<br>
_______________________________________________<br>
I-D-Announce mailing list<br>
<a href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce">https://www.=
ietf.org/mailman/listinfo/i-d-announce</a><br>
Internet-Draft directories: <a href=3D"http://www.ietf.org/shadow.html">htt=
p://www.ietf.org/shadow.html</a><br>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org=
/ietf/1shadow-sites.txt</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_9563781e07234ac7919ecaf64b02073eXCH150611nwnosboeingcom_--


From nobody Mon Oct 30 22:04:59 2017
Return-Path: <asaeda@ieee.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46C8F13FC72 for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 22:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ieee-org.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 EXQ_CEwuq5su for <mboned@ietfa.amsl.com>; Mon, 30 Oct 2017 22:04:55 -0700 (PDT)
Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (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 A8E7013FD09 for <mboned@ietf.org>; Mon, 30 Oct 2017 22:04:55 -0700 (PDT)
Received: by mail-pf0-x244.google.com with SMTP id i5so12858892pfe.6 for <mboned@ietf.org>; Mon, 30 Oct 2017 22:04:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=e+KGaWFE5sOjIAeWIl67Wu94WsuaGhCueH1SHD4BpPQ=; b=1p582JialcAQQucsqM2JmeHUHjm8WpT21ywoyg1uVAdR01LTL2JCplMyeVQglJ5SvI 4kvJ+z9kCIESJFlerrN0Rk7PvOWCcWhaGJiVUDeZCqybChgvpO2NkMOxzWGK5bCkOnmC DgojflfoOr9tVLpqOB7mFKVo9Qm7xR8e6H9VGQ8FdkgZc6rgXE12cvb+H4OkBEzEskIN 04HbLdA5FUvs4145BhowItegNj7gliRPCZhW/7QKwYqr/N6x/y1bQE8LEKe4VTatZVo3 LtYDgx6mY+PpsQUWLfY/muuPuHMGxCfDd8M2h1z7uSrfhFXRxdSeEgWeJeBG7sQaHgmu KKcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=e+KGaWFE5sOjIAeWIl67Wu94WsuaGhCueH1SHD4BpPQ=; b=CRvRQVZde2S7O/DF/tWUfGP5HozBbJI7prplQY8uq4hW7NXqawo05t5yiTQ0MW6D/+ 2JIdrMgcuEbBvIROtebPec/8OTy+l5PfmWzyYtQGkGTEu8O1biSfmpJEkXQrm/4tRVyF wiPRpddleeOLshhoN2fvtQ2lRnPFQr2A3pMLW7WEI2timrFMJJA6YYyW1/1NqeJ9UKHq z6bV4BgAF+FEWHbENqnh1zljQAne/AArKNNlQf2FP6bfLVRD2+mC+XMa/ZDZGJH8DD5n HwR95VuzFnCadITD+FPBg+m7JQGp7ekfK9zHzXHf6M3VWnuX7wEh3f8BRzywZKmIbFij IlHw==
X-Gm-Message-State: AMCzsaVGUUGhyVICtEhbm2wri032RGZwWqKl+fBMIVfSnIKuee04jNGk YbRVXryyoNipHAjdw/yNgpeQlg==
X-Google-Smtp-Source: ABhQp+QvSGYsAs48sHbBYf+s5wzs0D5vLTIUcCd3/4COVGRLoKT1cgtdFZ/x6o6nevJ+r9q+KAjw1Q==
X-Received: by 10.101.97.130 with SMTP id c2mr770669pgv.101.1509426295040; Mon, 30 Oct 2017 22:04:55 -0700 (PDT)
Received: from ?IPv6:2001:200:e103:1000:1534:3d02:c6ca:bee0? ([2001:200:e103:1000:1534:3d02:c6ca:bee0]) by smtp.gmail.com with ESMTPSA id 2sm765234pgb.30.2017.10.30.22.04.53 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 30 Oct 2017 22:04:54 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Hitoshi Asaeda <asaeda@ieee.org>
In-Reply-To: <CAHw9_iLt3XMdgEw6ZoMviG+zAEPLDH6jxJojvS_f+GP8GYODmQ@mail.gmail.com>
Date: Tue, 31 Oct 2017 14:04:53 +0900
Cc: draft-ietf-mboned-mtrace-v2@ietf.org, mboned-chairs@ietf.org, mboned@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF4E377C-A58A-45AE-85B9-EAD29A2EAB48@ieee.org>
References: <CAHw9_iLt3XMdgEw6ZoMviG+zAEPLDH6jxJojvS_f+GP8GYODmQ@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/w_k-_vSepPBBVh90dKKubBGpE0Q>
Subject: Re: [MBONED] AD review of draft-ietf-mboned-mtrace-v2
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2017 05:04:58 -0000

Hello Warren,

Thank you very much for your review.

We will address your comments ASAP.
BTW, since this C/O date was past, we cannot submit the revised document =
now. Whenever the draft submission site is opened again, we will do it.
Can you chairs just wait for the IESG review process until the revision?

Regards,

Hitoshi


> 2017/10/31 6:22, Warren Kumari <warren@kumari.net> wrote:
>=20
> Hello,
>=20
> Firstly, I'd like to apologize for how long it took me to review this
> - I came down with a bad case of pneumonia, and was broken for a
> while...
>=20
>=20
> Thank you for your work on this document, it's a well written and easy
> to understand
> draft.  I do have a few comments that I=E2=80=99d like addressed =
before I
> start IETF LC =E2=80=94 addressing these now will avoid issues later =
in the
> process.
>=20
>=20
> Section 1.  Introduction
>   Given a multicast distribution tree, tracing from a multicast source
>   to a receiver is difficult, since we do not know which branch of the
> [O] know which branch
> [P] know on which branch
> [R] readability/grammar
>   multicast tree the receiver lies.
>=20
> When not receiving an Mtrace2 Reply message due to
>   network congestion, a broken router (see Section 5.6), or a non-
>   responding router (see Section 5.7), the Mtrace2 client may resend
>   another Mtrace2 Query with a lower hop count (see Section 3.2.1), =
and
>   repeat the process until it receives an Mtrace2 Reply message.  The
>   details are Mtrace2 client specific, and it is outside the scope of
>=20
> [O] specific, and it is outside
> [P] specific and outside
> [R] readability; otherwise we would need to say =E2=80=9Cthey,=E2=80=9D =
and not =E2=80=9Cit,=E2=80=9D
> because we are referencing =E2=80=9Cdetails=E2=80=9D (plural). That =
seems awkward.
>   this document.
>=20
>   Note that when a router's control plane and forwarding plane are out
>   of sync, the Mtrace2 Requests might be forwarded based on the =
control
>   states instead.  In which case, the traced path might not represent
>=20
> [O] In which case,
> [P] In this case,
> [R] grammar
>   the real path the data packets would follow.
>=20
> Section 3.2.3.  Mtrace2 Reply
> ...
>  The Reply message would then
>   be unicasted to the Mtrace2 client specified in the Mtrace2 Client
>   Address field.
>   There are a number of cases an intermediate router might return a
>=20
> [O]  cases an intermediate router might return
> [P] cases in which an intermediate router might return
> [R] I think this is what was meant.
>=20
> Section 3.2.6.  Mtrace2 Augmented Response Block
> ...
>      When the NO_SPACE error occurs on a router, the router should =
send
>      the original Mtrace2 Request received from the downstream router
>      as a Reply back to the Mtrace2 client, and continue with a new
>=20
> [O] client, and
> [P] client and
> [R] grammar
>      Mtrace2 Request.
>=20
> Section 4.3.3.  Appending Standard Response Block
>   ...
>   The router then turns the Request
>   into a Reply, and sends the Reply as described in Section 4.4.
> [O] Reply, and
> [P] Reply and
> [R] grammar
>=20
> 5.8.3.  No Upstream Router
>   A trace can not continue if the last Upstream Router in the trace is
> [O] can not
> [P] cannot
> [R] grammar =E2=80=94 unless you that optionally, it can elect not to =
continue=E2=80=A6 :-P
>   set to 0.
>=20
> 5.9.  Continuing after an Error
>  ...
>   However, if all paths but one flow back towards the non-
>   responding router, it is possible to be sure that this is the =
correct
> [O] it is possible to be sure
> [R] I don=E2=80=99t know what this means - perhaps "this" ?
>   path.
>=20
>=20
> 7.3.  Packet Loss
>  ...
>   Since the packet counts may be
>   changing as the Mtrace2 Request is propagating, there may be small
>   errors (off by 1 or 2 or more) in these statistics.  However, these
>=20
> [O] (off by 1 or 2 or more)
> [R] limit the =E2=80=9Cor more=E2=80=9D; otherwise, what=E2=80=99s the =
point of saying this at
> all? Perhaps "on the order of 1 or 2"?
> ---
> Again, apolgies for the delay,
> W
> --=20
> I don't think the execution is relevant when it was obviously a bad
> idea in the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair
> of pants.
>   ---maf
>=20
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


From nobody Mon Oct 30 23:36:37 2017
Return-Path: <lenny@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7406D115FA; Mon, 30 Oct 2017 23:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
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 dFjmur9uAYUe; Mon, 30 Oct 2017 23:36:33 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0130.outbound.protection.outlook.com [104.47.37.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89E6C115F9; Mon, 30 Oct 2017 23:36:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=V1ocLGWYUxYNFuSptQAmCh/73cYs8roFWfBAOsQs8uQ=; b=F4RjdVQCrN9qLZkooeeBj+dN1Oo8t/uQSAKKnjwjM+kae3JnIrZs0871hgB8gwL9eiV7oZ0hkwcbHazhNwrjKnvr2C+3Zf+iMLso+TkV4nBkEEBm1GX41fVkheEf8B5vZbEi/J9nalRHQf0bF8ZKLGNHLRTC+2lgTqHTajCKzJQ=
Received: from SN4PR0501CA0099.namprd05.prod.outlook.com (10.167.128.16) by BY2PR0501MB2071.namprd05.prod.outlook.com (10.163.197.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.197.4; Tue, 31 Oct 2017 06:36:32 +0000
Received: from CO1NAM05FT039.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::209) by SN4PR0501CA0099.outlook.office365.com (2603:10b6:803:42::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.197.4 via Frontend Transport; Tue, 31 Oct 2017 06:36:31 +0000
Authentication-Results: spf=softfail (sender IP is 66.129.239.15) smtp.mailfrom=juniper.net; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=fail action=none header.from=juniper.net;
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by CO1NAM05FT039.mail.protection.outlook.com (10.152.96.152) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.20.197.9 via Frontend Transport; Tue, 31 Oct 2017 06:36:31 +0000
Received: from svl-jtac-lnx06.juniper.net (172.17.28.215) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server id 14.3.123.3; Mon, 30 Oct 2017 23:36:31 -0700
Received: by svl-jtac-lnx06.juniper.net (Postfix, from userid 1709)	id 9AD3B9F90F; Mon, 30 Oct 2017 23:36:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by svl-jtac-lnx06.juniper.net (Postfix) with ESMTP id 9734A9F8F7; Mon, 30 Oct 2017 23:36:30 -0700 (PDT)
Date: Mon, 30 Oct 2017 23:36:30 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Hitoshi Asaeda <asaeda@ieee.org>
CC: Warren Kumari <warren@kumari.net>, <draft-ietf-mboned-mtrace-v2@ietf.org>,  <mboned@ietf.org>, <mboned-chairs@ietf.org>
In-Reply-To: <CF4E377C-A58A-45AE-85B9-EAD29A2EAB48@ieee.org>
Message-ID: <alpine.DEB.2.02.1710302333340.9511@svl-jtac-lnx02.juniper.net>
References: <CAHw9_iLt3XMdgEw6ZoMviG+zAEPLDH6jxJojvS_f+GP8GYODmQ@mail.gmail.com> <CF4E377C-A58A-45AE-85B9-EAD29A2EAB48@ieee.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8BIT
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(376002)(346002)(39860400002)(2980300002)(189002)(24454002)(45984002)(199003)(47776003)(83506002)(6916009)(2950100002)(345774005)(54906003)(46386002)(229853002)(58126008)(5660300001)(7126002)(106466001)(97736004)(23676003)(105596002)(5005980100005)(316002)(189998001)(6306002)(305945005)(4326008)(76176999)(50986999)(230783001)(2906002)(45336002)(57986006)(53936002)(575784001)(8936002)(76506005)(356003)(50466002)(86362001)(68736007)(81166006)(81156014)(966005)(77096006)(6246003)(6266002)(54356999)(90966002)(2870700001)(3240700002)(8676002)(478600001)(2810700001)(69596002)(372894003)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0501MB2071; H:P-EMFE01C-SAC.jnpr.net; FPR:; SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; CO1NAM05FT039; 1:2h8tXfrUUzFxqU691PejLtRvxHk4u2PKfU45yaKBNEy7LJCmeog1O+M5UpLM4plQ+6cuYdhs+//iRZ4zilcd7w/DY4h2Wjo6LH5WVZxpPyRqPIA0xuBYKFS24zNuijwu
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 0033a1fe-f71d-411f-6d99-08d52029b92d
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(2017052603199); SRVR:BY2PR0501MB2071; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2071; 3:ShHX5NZDu66U36aFbREX8gmn8TZCIAuNfBpYH2fdZgCCQh6xToCNOVk9n1IBaj/Te1DyGxYjS0Vs+FUiDLK2xCpCX1qjmd6mQUDX2uzlVneJXgBtThsyIJS6DgyllLornZsV6jsPB8WhswWPU38zqFrTdMr1AlXgqCztztk3l0oiir+thaePbwpINMyR69QjXImUZ0QKV+vI9wO7GSIs/qVeAp3fG9Dh2Uxb1fEvO70BgzokqLIYarxWxDi7UT3wjpaFWyYj8BOEoK5QQYBIpFO1YXuiQwLJjuqv4rofvaFQ0LtFU8jdgJd4Msg5QU9tZCd0+0ntIyCNWrX6UGkMWmYnQZpMD4bzHcFW0gZSnv0=; 25:Aor/kFuLNrRQDD2y7k+HVpfdnht/DqIzmJsBdZzxV09BmzFw/mah9/7s/RrIAh8jllPBoYsJP17dADmec5hmWJjw4vaSyOrRmjYpoUO7XTqM1LCzTClbB1jBTf4Qj40oNAHuw1wr7Zr0G0oSEJ0VHMFG41fbKgcyaXbOZF2KIhRtQ/yiYrgM1kId9djwJZs85v5wq4AIzeVWkoub7qrAq9KLILLyICrjYhO/sVpZtszemBOB4Nytjvo/Vdjq2LXKmOhKUIMuegU6FR14DcZwnSNETVB+0A63JSJrvyVmt5R8IZe/hIUrrBofavuIOy3yepSeVXVUWznBzUMVlZrnXg==
X-MS-TrafficTypeDiagnostic: BY2PR0501MB2071:
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2071; 31:xQB3TXCTpz0VI72SxobMe42SLbJFj9RiAEAfJT8uSwNcfoOy8nsHPJag0q+G+d6mVwY68Q+VIHusqJvqPWne0drCbqPuEhUfWXtNzHNEkKaxXAat8Nf+OmiGKRuGZNznFdtJzXSBHsOpoQBis3VHHakDaFwS8/j43QQmzAH1X3HoKYRbdZHnuLvNNdwe2o2EP3OLQ8Lmnb1DMeSXw/PnO5Z9PqifQFMXoPSoDqpQGmw=; 20:y2/IBQBqjCkMbUvx84LMY+dC8xeqKEXHHwxLd3GpJhrDOvo2M+jhUldLrC9RlgSmqAukhM0TYfjXdi4LR1CQ77gchvcZ8PLGSYhT6q+xoQmNLGIsr7sjsaktnqs2xa2+ZunXVijFmGlj6+M/zEyrObpYjwbMJ572cLilf+EGOnPuBKT/U1HSW1tLq4Rwl89oCc5PNcwUMMsGngiVizeXkXcRrU//ILaU3afoDtFfLtqrOsg7YAIGvcQKUSFwiOFxSN0ZO0ATOvcejf1jYgl7IYY4ECSIuKYYhvt7Cfh7l4GbHyWACul5Hq0dYQGqWGFvTZeqwBJyE5b6DCgFWvGGbzuYDH6cJFh4Ovdh57ZpFwrxV5YR2soJcin4rJEPKMXgWncYtKzjX12utWh7cr1EnvH7wreDWMcmbs/VJp/0sqf4Piz++8RrsYONcKUi/D+nYdUafNmxSH6Gf+BA93kBVzjj8uVVEjc4SRYg6TQ26/C8dJCo04OtYCeKJKlTtv3s
X-Exchange-Antispam-Report-Test: UriScan:(10436049006162);
X-Microsoft-Antispam-PRVS: <BY2PR0501MB2071A99B5A63C1A990C28989A45E0@BY2PR0501MB2071.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(3231020)(93006095)(93001095)(10201501046)(3002001)(6055026)(6041248)(20161123558100)(20161123564025)(20161123560025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BY2PR0501MB2071; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BY2PR0501MB2071; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2071; 4:JZJWXGqpJwu8DzWeBESbvs4Ml09kY4hy78C3B/0qYp94t/OdwREzwocWbBzBaK8vvk6xk/vwXl6TDyaeJb4g66FXR7TJNASnpVmkb/5vkczcnOiZfNs+N1ID/woM/uXKEdY9pitBI5oS0LgSfzJAempxJuubzEhS/xF2JS6h5hCDjURZVxxnzGPQ1qg4OJQ4SI7v7zzUZxvnVz2upiojorgdBhs/61KM9Yn8bO4JMNzFA98N5DhdFmhuV3cltHbFMCPwBvu8FL+RV2ubcW/BG3mtx6UMkqDmopOX+R4CBfzzW/+PoqbaKlZ2Prdo4Xs1
X-Forefront-PRVS: 04772EA191
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCWTJQUjA1MDFNQjIwNzE7MjM6elhQbmVJVUk4elBpWkZTZTA1ZGUzc1RG?= =?utf-8?B?NHFzc2w5eVVoUEFCVHFmaWJreDdoeFc2NG9EQlpPdzhhM0ZaUm1kaUk3Z3hi?= =?utf-8?B?UnpZQ1MvVElZL0VBY0ltNTVQTllyclVDNVhGdWJGTyswdnNOTGR5czlhZUtN?= =?utf-8?B?clB4dmZBZXMvc2JpUnhvMFc1OUJpWTlxLzdCb1lJd0Jvc3NNVGVqRVg1TlY4?= =?utf-8?B?VjIyb0dEdnRaUHFUWVE2d1k1UnNEU0ZvT2U0aU1DZDViOGZZY1JMYkxwajVT?= =?utf-8?B?bnJlaHlQYWJVbHM1bDNZbUkwZDhpd1dWRFZGZ3lVaDg4dHplTEZYYk1NekMy?= =?utf-8?B?Wk8zSDExU3pKSUhSZm9ldnpHa3Y3dzhnRmtVYVNjdVUzTklqR1BBYmxRZ3JR?= =?utf-8?B?YXRWVHp2T1dYbGI5Qm5jWWY4UTFQcFdpRWNJK0lnbStRRjRGbkVnODQvV3BK?= =?utf-8?B?UzZtdWVnVmlFSno1R3lzRGJUaXpnT0g1cC9BeEQ0R0VxbjZqdmpPTjErZjF5?= =?utf-8?B?d3pJWFlGYmhDY0pJc1FMR0VSbHhxOTFRZDJOd0NIZDZaV1Q2V2dFQjFQZzJ1?= =?utf-8?B?TkZ3eVJVeDJIY3Era0RReFUrOCtKUUVIVWtLajZrVHJma2tuWGdiMnpoYlc3?= =?utf-8?B?VlZqY2tYVXFPWGFnTEUvV0duRnZScWswbEsrd1RKbW9lMDQyOURYdXR2Tk9h?= =?utf-8?B?SVF2a2lSUjI0cUVNcGhPQXJSeDhYaFBENXUzVWRUYkowS29PbFRraWhac2oz?= =?utf-8?B?RmNXOUVFSm44RnNPdTJ6NHVwZ3ZWeEl3SmtpOEIxckRQMmVMNDc5NE9HcDI3?= =?utf-8?B?RWM2TisreFg4enFmT1V3WGZKTEFsc3duY0RFbVlsZ2lJOUk3NVh1ZmN5QWFU?= =?utf-8?B?em9ESktIY1N0NVVUa0s2K1pyQ3FwblRpY05xK0dqWVZwNlZSOFZLMlh1ZkpX?= =?utf-8?B?bzVPbmN0bGZPZU9lTCtsSlpEdmVyNHYzbmpBM3JMWU8yTGVob1ZlS0h4TE84?= =?utf-8?B?WmdETVZ6N3d6U3ZDbUJrK1pRdGNmMGNGNWpTSFFxS0x3WDRvOUE4aFNRVE5a?= =?utf-8?B?OG5CRC9PTjJ2cnpMRksvQTRTT2JPRng5OGdZbWNPS3V1WWoyYkdobDBnbnRy?= =?utf-8?B?VVNYSXczdmwxMkxSaHhmOEJER21JR1ltNTgzd3lGMTI2VHNVUVBHNmVQcGV2?= =?utf-8?B?czJEcG5rTnJadGRqKzRPbS9CdHBlMEk2UFFSdEM0UDR0eS9WWFErZVVOYnh1?= =?utf-8?B?SUhsci94SDQwZEx4WDErRVlQckVZc21adGRYV3Z0RzJ1RDkwWnZnZ0k5cDRa?= =?utf-8?B?N29FZ0kwa2d3bHkxWEJVdXVtS1ZZbXpyRWJHeWFkVEhuR3JuY2szeGN6R0pr?= =?utf-8?B?NGFPVHNzM3lTMjQ1b2t1dHdjTGVvMGZ1V2RXNFJ4M3A5K2lCMk1OeUdNMEFB?= =?utf-8?B?VG1QWGZ3eC9xOXVsODAvM3lTelNXbE9aMGRjNTVlRmNnckNiYnJqaHNDYkdH?= =?utf-8?B?LzE0TWdHYXMzTTRsQ08xSnF1bktVNVVWRFJpRnNYbkl1NjFaSnRYamxWalhi?= =?utf-8?B?Mm5JNXZ0NmtaNkE3RXlpL2hFbU5TUFA3TWd2UFZxZGtNRVNxK29YTTJnOGRY?= =?utf-8?B?ZlhYdXRZd1hLNlYzVXZaRWZQb1FNeTNaaXdsYWhwd0lFeEtTSHc5Z1NOcGl4?= =?utf-8?B?MTlMd2sraHNIajRzeU56R0VEUHgyekYvNFBIdkdJRVY5cXhadnpSbFgxRkE0?= =?utf-8?B?S3ppNGtHMjYwVlJ3bVJFM3NWODVmbStrVzI2YXZTVXNQSXlDei9UZ0FaRExu?= =?utf-8?B?RDRnSUlEM0tDNnMvSlJJeVNMQ3VOWi9qTCtpOTJrb3hRSEU0M3RkRjNRM3NC?= =?utf-8?B?U2dXRjA3QUhDSGNNKzRWdi8vSFNIQ1FZemdTcDQ2cHZOeVpOeDVJOXF1YkNq?= =?utf-8?B?UjZNTDBRQ3gwQnc9PQ==?=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2071; 6:guITXWHbvQZLS8slh9qOeZwoyLxn6kPoZxDkvyYb3C7AWBfiKgf9ACjlKEcXCSkd5jUUciaNmYHtSCmB6kh1Tbw0Cr0xQpvdYlX4xCG0g4w0kYApiye/w5AKcRzaKX8/0iaS9iW2K5eN8H1W8dXVbqC03wLYtlHQeTeAGThc2hTYdQdrcsN8re7tufuvgKqbgJSYYIF59PqW7DIS0OoE2xY5282XhhbpyDKMDALM8fJYrAGolwb7xclWZGq2N6twtwH7X8MhTm63Bw7BPR5cqqRXwymqeNUzl5Q/Qr4GpGkRiT7B1gmHaP2Q9Cocl23aiXCUGO8kaXUb4zv0w5JfVGgnbk/gXIWVYIcW/2YA+yA=; 5:F7BKJz+iGxmli0m7xJKJdPtUA4WgQmgMOTJGxtKmxLw/Nq6imFAUAC+QiUvbTI5cUpAPTXsRA+eZwSz7LaVz046p306ogJ4RvpMPTca6hGpbDSvblyae/4h0FI1n2pbGzrEgXJlZsxmboQaXbdqTnIhY8VvXbKRsZLMuqlk8NJY=; 24:tDIhX8oy1oel+5fYsXviX9jEFEZJ/saMja+CQPwyaOIoe6eiJ6JlYtqhaATLNGo4bxU72xmYca+YqC5vX8kA9aXXt54FhUQf6stYDKZPWgU=; 7:JI6SlVf6c623ZelMA3NbeMzj1Y6nvEvUoi6HVbIJzUl/rFq2VzzIxeY43QTjJ4g3jTsIDHCNlzbsjUeX8Qch0tN7XPn1uh2VmVAF8RsfG3bpM3NwGkgtyIAYkZSa69Q53tPDccMpQOPtS1k5/NKkF86C9FB4jdVXMggGJObJJklSR0+HL5RkrgZQ1pp8Oq0ERd+6QL4/hjHPySfB7zdfj9r5McIMbuQRpRQI+OYxC1vcMEmE5Wrpklp7L3EpCYN8
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 31 Oct 2017 06:36:31.2178 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 0033a1fe-f71d-411f-6d99-08d52029b92d
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0501MB2071
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/zM5sbr_l-C2D92P4QQODM0Busag>
Subject: Re: [MBONED] AD review of draft-ietf-mboned-mtrace-v2
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2017 06:36:36 -0000

Hitoshi- Warren will be taking the draft to IETF LC, and as he mentions, 
it's best to address these items now to avoid issues later in the process.

I think it's OK to wait until the cutoff is over to resubmit.


Lenny Giuliano
Juniper Networks
Herndon, VA
703-786-3398

On Tue, 31 Oct 2017, Hitoshi Asaeda wrote:

| Hello Warren,
| 
| Thank you very much for your review.
| 
| We will address your comments ASAP.
| BTW, since this C/O date was past, we cannot submit the revised document now. Whenever the draft submission site is opened again, we will do it.
| Can you chairs just wait for the IESG review process until the revision?
| 
| Regards,
| 
| Hitoshi
| 
| 
| > 2017/10/31 6:22, Warren Kumari <warren@kumari.net> wrote:
| > 
| > Hello,
| > 
| > Firstly, I'd like to apologize for how long it took me to review this
| > - I came down with a bad case of pneumonia, and was broken for a
| > while...
| > 
| > 
| > Thank you for your work on this document, it's a well written and easy
| > to understand
| > draft.  I do have a few comments that I’d like addressed before I
| > start IETF LC — addressing these now will avoid issues later in the
| > process.
| > 
| > 
| > Section 1.  Introduction
| >   Given a multicast distribution tree, tracing from a multicast source
| >   to a receiver is difficult, since we do not know which branch of the
| > [O] know which branch
| > [P] know on which branch
| > [R] readability/grammar
| >   multicast tree the receiver lies.
| > 
| > When not receiving an Mtrace2 Reply message due to
| >   network congestion, a broken router (see Section 5.6), or a non-
| >   responding router (see Section 5.7), the Mtrace2 client may resend
| >   another Mtrace2 Query with a lower hop count (see Section 3.2.1), and
| >   repeat the process until it receives an Mtrace2 Reply message.  The
| >   details are Mtrace2 client specific, and it is outside the scope of
| > 
| > [O] specific, and it is outside
| > [P] specific and outside
| > [R] readability; otherwise we would need to say “they,” and not “it,”
| > because we are referencing “details” (plural). That seems awkward.
| >   this document.
| > 
| >   Note that when a router's control plane and forwarding plane are out
| >   of sync, the Mtrace2 Requests might be forwarded based on the control
| >   states instead.  In which case, the traced path might not represent
| > 
| > [O] In which case,
| > [P] In this case,
| > [R] grammar
| >   the real path the data packets would follow.
| > 
| > Section 3.2.3.  Mtrace2 Reply
| > ...
| >  The Reply message would then
| >   be unicasted to the Mtrace2 client specified in the Mtrace2 Client
| >   Address field.
| >   There are a number of cases an intermediate router might return a
| > 
| > [O]  cases an intermediate router might return
| > [P] cases in which an intermediate router might return
| > [R] I think this is what was meant.
| > 
| > Section 3.2.6.  Mtrace2 Augmented Response Block
| > ...
| >      When the NO_SPACE error occurs on a router, the router should send
| >      the original Mtrace2 Request received from the downstream router
| >      as a Reply back to the Mtrace2 client, and continue with a new
| > 
| > [O] client, and
| > [P] client and
| > [R] grammar
| >      Mtrace2 Request.
| > 
| > Section 4.3.3.  Appending Standard Response Block
| >   ...
| >   The router then turns the Request
| >   into a Reply, and sends the Reply as described in Section 4.4.
| > [O] Reply, and
| > [P] Reply and
| > [R] grammar
| > 
| > 5.8.3.  No Upstream Router
| >   A trace can not continue if the last Upstream Router in the trace is
| > [O] can not
| > [P] cannot
| > [R] grammar — unless you that optionally, it can elect not to continue… :-P
| >   set to 0.
| > 
| > 5.9.  Continuing after an Error
| >  ...
| >   However, if all paths but one flow back towards the non-
| >   responding router, it is possible to be sure that this is the correct
| > [O] it is possible to be sure
| > [R] I don’t know what this means - perhaps "this" ?
| >   path.
| > 
| > 
| > 7.3.  Packet Loss
| >  ...
| >   Since the packet counts may be
| >   changing as the Mtrace2 Request is propagating, there may be small
| >   errors (off by 1 or 2 or more) in these statistics.  However, these
| > 
| > [O] (off by 1 or 2 or more)
| > [R] limit the “or more”; otherwise, what’s the point of saying this at
| > all? Perhaps "on the order of 1 or 2"?
| > ---
| > Again, apolgies for the delay,
| > W
| > -- 
| > I don't think the execution is relevant when it was obviously a bad
| > idea in the first place.
| > This is like putting rabid weasels in your pants, and later expressing
| > regret at having chosen those particular rabid weasels and that pair
| > of pants.
| >   ---maf
| > 
| > _______________________________________________
| > MBONED mailing list
| > MBONED@ietf.org
| > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_mboned&d=DwIGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=iw2TU3OZ0CDpCbqeV23zdah2FoG9Do-zEmGgWTaavDg&m=3edLGzdsQxcFpVJH9_zNcVA5vyzKmcwscKD72Nw3laY&s=i5OB_xGccMzEPkQ6JqRclxJpQiUKQKYB14TvVuDwsxA&e=
| 
| _______________________________________________
| MBONED mailing list
| MBONED@ietf.org
| https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_mboned&d=DwIGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=iw2TU3OZ0CDpCbqeV23zdah2FoG9Do-zEmGgWTaavDg&m=3edLGzdsQxcFpVJH9_zNcVA5vyzKmcwscKD72Nw3laY&s=i5OB_xGccMzEPkQ6JqRclxJpQiUKQKYB14TvVuDwsxA&e=
| 


From nobody Tue Oct 31 01:34:31 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CCC4F13F6B9; Tue, 31 Oct 2017 01:34:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, tim.chown@jisc.ac.uk, mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150943886479.28384.8698296324769434500.idtracker@ietfa.amsl.com>
Date: Tue, 31 Oct 2017 01:34:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/IyJkEBy4uKd9tfxAP8DoFwvy6dg>
Subject: [MBONED] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-mboned-interdomain-peering-bcp-14=3A_=28with_COMMENT=29?=
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2017 08:34:25 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-mboned-interdomain-peering-bcp-14: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for addressing my discuss and providing a detailed section on congestion
control. And thanks Yoshi for the TSV-ART review again!

-----------------------------
Old questions/comments:

1) Section 3.4 also says:
"Highly efficient use of bandwidth in AD-1."
But aren't packets eventually duplicated in this case in AD-1? I guess it's
more efficient than replicating them at the network border but might be still
less efficient than native multicast in the whole network, no?

2) section 4.3.3 says:
"The two AD's may supply additional security logs..."
This seems to be a general action not specific to multicast or the scenarios
described in this doc.

3) I don't think the conclusion section (8) is helpful or needed. If you want
to keep it at all, this text could be moved into the introduction.



From nobody Tue Oct 31 10:25:04 2017
Return-Path: <warren@kumari.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3001E139095 for <mboned@ietfa.amsl.com>; Tue, 31 Oct 2017 10:25:03 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.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 KpCE1k-fNf57 for <mboned@ietfa.amsl.com>; Tue, 31 Oct 2017 10:25:00 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 4BB7A13F9F2 for <mboned@ietf.org>; Tue, 31 Oct 2017 10:25:00 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id y80so335381wmd.0 for <mboned@ietf.org>; Tue, 31 Oct 2017 10:25:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=mERz6LUvDoTC39sRrhvVEDfTK7Xw6sYkW69xBJan6CE=; b=BzPpGqjyw5qSyr47rA9dCxfRw23qywzAnDjaD2eq3jNakSRc20Wvg++OPCIe0eRK+5 SSQGmGOq9tCL2UrRqkK0LnOPRNVCg2sjjjSC5Ooua+pypgstC2gw0OXOjOOKFfPfnZSY kBSE06pkPef/xVjPK1jhjhtxW5whRwa5d4GnmlmxYLiUhTWu/qAeb834Qiyj8dua0ldt B2mqQ04DzgJL0AdshzwAfGYSII49FWYJZZ/5YEKrgxpK7fnI1O6ko+RVDWf/aZ1pq7o/ 2BzZg3qBwRUt74I6FHTbzsql7ZLQgAzLZk5ap4BBJUIYIIRQWW7U5pVzJAs6/isC3D5r VqRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=mERz6LUvDoTC39sRrhvVEDfTK7Xw6sYkW69xBJan6CE=; b=kgoOR6OXVkBTeCjH1aaS6EPOJ/6ZWuP2hyGr7+Thjghhvdn9KIjM6bcDeEtFA4EzQ+ 2gDDTu8nCq5YEUcK2mlnOMZimyT/psnLlCB5EakAr70OV/AcN2PsSDejOmyIVxAQqlBv JULKBoSzjsE6WrWLn/sGNspQjjOkEhms8chahmau0V1BjY8zaVTiucBfA587ljN4qQjZ v5lY5xvdMh5Zjc98Mxc7JqSAp6Zcku7ckcv+5rdAQmuDJ6+0MqmjO11efvIrB9snHMTK KMf6fs1wmdb7DceT3O3D3uHDZmrypo0oZqfVhSFa7JTec/VXeRLHwj9JLhoNBYve/eK8 TY7A==
X-Gm-Message-State: AMCzsaUarCHDw23Br+gfaq6IDd2VvQbhwzkICi9bgxXA/kpJDb5OH9wJ chUL9GqFGhUqgQricyt8pfBWl83YZ+FYazSnYYROUw==
X-Google-Smtp-Source: ABhQp+TUUZESDQaqWZWFgMuZtEHw7R4aYjlI8GzDlA+MgCEWg3tj9XbpbKgMW63EjhQ9vsc8Yw3jD7dd29lW9+zx2aE=
X-Received: by 10.28.26.138 with SMTP id a132mr2590456wma.124.1509470698523; Tue, 31 Oct 2017 10:24:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.187.12 with HTTP; Tue, 31 Oct 2017 10:24:17 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.02.1710302333340.9511@svl-jtac-lnx02.juniper.net>
References: <CAHw9_iLt3XMdgEw6ZoMviG+zAEPLDH6jxJojvS_f+GP8GYODmQ@mail.gmail.com> <CF4E377C-A58A-45AE-85B9-EAD29A2EAB48@ieee.org> <alpine.DEB.2.02.1710302333340.9511@svl-jtac-lnx02.juniper.net>
From: Warren Kumari <warren@kumari.net>
Date: Tue, 31 Oct 2017 13:24:17 -0400
Message-ID: <CAHw9_iKFqz87Hd=8XPjtgcMcwax6Scba50aoSh=Z69tsd2dD8w@mail.gmail.com>
To: Leonard Giuliano <lenny@juniper.net>
Cc: Hitoshi Asaeda <asaeda@ieee.org>, draft-ietf-mboned-mtrace-v2@ietf.org, mboned@ietf.org, mboned-chairs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/5cSaMrE0X1kM_7t90Kpv1uP6lPE>
Subject: Re: [MBONED] AD review of draft-ietf-mboned-mtrace-v2
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2017 17:25:03 -0000

On Tue, Oct 31, 2017 at 2:36 AM, Leonard Giuliano <lenny@juniper.net> wrote=
:
>
> Hitoshi- Warren will be taking the draft to IETF LC, and as he mentions,
> it's best to address these items now to avoid issues later in the process=
.
>
> I think it's OK to wait until the cutoff is over to resubmit.

Yup -- otherwise, because this is my fault (and the changes are all
editorial) I'll approve submission if you want to submit before the
cuffoff opens again.
If so, please make sure to let me know.


W

>
>
> Lenny Giuliano
> Juniper Networks
> Herndon, VA
> 703-786-3398
>
> On Tue, 31 Oct 2017, Hitoshi Asaeda wrote:
>
> | Hello Warren,
> |
> | Thank you very much for your review.
> |
> | We will address your comments ASAP.
> | BTW, since this C/O date was past, we cannot submit the revised documen=
t now. Whenever the draft submission site is opened again, we will do it.
> | Can you chairs just wait for the IESG review process until the revision=
?
> |
> | Regards,
> |
> | Hitoshi
> |
> |
> | > 2017/10/31 6:22, Warren Kumari <warren@kumari.net> wrote:
> | >
> | > Hello,
> | >
> | > Firstly, I'd like to apologize for how long it took me to review this
> | > - I came down with a bad case of pneumonia, and was broken for a
> | > while...
> | >
> | >
> | > Thank you for your work on this document, it's a well written and eas=
y
> | > to understand
> | > draft.  I do have a few comments that I=E2=80=99d like addressed befo=
re I
> | > start IETF LC =E2=80=94 addressing these now will avoid issues later =
in the
> | > process.
> | >
> | >
> | > Section 1.  Introduction
> | >   Given a multicast distribution tree, tracing from a multicast sourc=
e
> | >   to a receiver is difficult, since we do not know which branch of th=
e
> | > [O] know which branch
> | > [P] know on which branch
> | > [R] readability/grammar
> | >   multicast tree the receiver lies.
> | >
> | > When not receiving an Mtrace2 Reply message due to
> | >   network congestion, a broken router (see Section 5.6), or a non-
> | >   responding router (see Section 5.7), the Mtrace2 client may resend
> | >   another Mtrace2 Query with a lower hop count (see Section 3.2.1), a=
nd
> | >   repeat the process until it receives an Mtrace2 Reply message.  The
> | >   details are Mtrace2 client specific, and it is outside the scope of
> | >
> | > [O] specific, and it is outside
> | > [P] specific and outside
> | > [R] readability; otherwise we would need to say =E2=80=9Cthey,=E2=80=
=9D and not =E2=80=9Cit,=E2=80=9D
> | > because we are referencing =E2=80=9Cdetails=E2=80=9D (plural). That s=
eems awkward.
> | >   this document.
> | >
> | >   Note that when a router's control plane and forwarding plane are ou=
t
> | >   of sync, the Mtrace2 Requests might be forwarded based on the contr=
ol
> | >   states instead.  In which case, the traced path might not represent
> | >
> | > [O] In which case,
> | > [P] In this case,
> | > [R] grammar
> | >   the real path the data packets would follow.
> | >
> | > Section 3.2.3.  Mtrace2 Reply
> | > ...
> | >  The Reply message would then
> | >   be unicasted to the Mtrace2 client specified in the Mtrace2 Client
> | >   Address field.
> | >   There are a number of cases an intermediate router might return a
> | >
> | > [O]  cases an intermediate router might return
> | > [P] cases in which an intermediate router might return
> | > [R] I think this is what was meant.
> | >
> | > Section 3.2.6.  Mtrace2 Augmented Response Block
> | > ...
> | >      When the NO_SPACE error occurs on a router, the router should se=
nd
> | >      the original Mtrace2 Request received from the downstream router
> | >      as a Reply back to the Mtrace2 client, and continue with a new
> | >
> | > [O] client, and
> | > [P] client and
> | > [R] grammar
> | >      Mtrace2 Request.
> | >
> | > Section 4.3.3.  Appending Standard Response Block
> | >   ...
> | >   The router then turns the Request
> | >   into a Reply, and sends the Reply as described in Section 4.4.
> | > [O] Reply, and
> | > [P] Reply and
> | > [R] grammar
> | >
> | > 5.8.3.  No Upstream Router
> | >   A trace can not continue if the last Upstream Router in the trace i=
s
> | > [O] can not
> | > [P] cannot
> | > [R] grammar =E2=80=94 unless you that optionally, it can elect not to=
 continue=E2=80=A6 :-P
> | >   set to 0.
> | >
> | > 5.9.  Continuing after an Error
> | >  ...
> | >   However, if all paths but one flow back towards the non-
> | >   responding router, it is possible to be sure that this is the corre=
ct
> | > [O] it is possible to be sure
> | > [R] I don=E2=80=99t know what this means - perhaps "this" ?
> | >   path.
> | >
> | >
> | > 7.3.  Packet Loss
> | >  ...
> | >   Since the packet counts may be
> | >   changing as the Mtrace2 Request is propagating, there may be small
> | >   errors (off by 1 or 2 or more) in these statistics.  However, these
> | >
> | > [O] (off by 1 or 2 or more)
> | > [R] limit the =E2=80=9Cor more=E2=80=9D; otherwise, what=E2=80=99s th=
e point of saying this at
> | > all? Perhaps "on the order of 1 or 2"?
> | > ---
> | > Again, apolgies for the delay,
> | > W
> | > --
> | > I don't think the execution is relevant when it was obviously a bad
> | > idea in the first place.
> | > This is like putting rabid weasels in your pants, and later expressin=
g
> | > regret at having chosen those particular rabid weasels and that pair
> | > of pants.
> | >   ---maf
> | >
> | > _______________________________________________
> | > MBONED mailing list
> | > MBONED@ietf.org
> | > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_m=
ailman_listinfo_mboned&d=3DDwIGaQ&c=3DHAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTX=
cWzoCI&r=3Diw2TU3OZ0CDpCbqeV23zdah2FoG9Do-zEmGgWTaavDg&m=3D3edLGzdsQxcFpVJH=
9_zNcVA5vyzKmcwscKD72Nw3laY&s=3Di5OB_xGccMzEPkQ6JqRclxJpQiUKQKYB14TvVuDwsxA=
&e=3D
> |
> | _______________________________________________
> | MBONED mailing list
> | MBONED@ietf.org
> | https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mai=
lman_listinfo_mboned&d=3DDwIGaQ&c=3DHAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcW=
zoCI&r=3Diw2TU3OZ0CDpCbqeV23zdah2FoG9Do-zEmGgWTaavDg&m=3D3edLGzdsQxcFpVJH9_=
zNcVA5vyzKmcwscKD72Nw3laY&s=3Di5OB_xGccMzEPkQ6JqRclxJpQiUKQKYB14TvVuDwsxA&e=
=3D
> |



--=20
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf

