
From nobody Mon Jan  3 05:28:28 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7B213A073E; Mon,  3 Jan 2022 05:28:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 YDzrL44lM2-U; Mon,  3 Jan 2022 05:28:08 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (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 5081D3A06E7; Mon,  3 Jan 2022 05:28:05 -0800 (PST)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar25.francetelecom.fr (ESMTP service) with ESMTPS id 4JSGlR2glyz8tsD;  Mon,  3 Jan 2022 14:28:03 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1641216483; bh=dUWDrfWcv0Jzzo7si7pyTx9bG6l2gYQyy1T2VKSRhXQ=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=O2hOmJjKC1bN+irasuvl8SyDaWk3xSjlrMZtoNCWv45kqCov8WYFBMD7h0WVlXS1Z B8fGxFilSGy9yIWgB7SxPXhDvHxm2h//7IKkeOVbDuJMOQAz8Pr/elyL0+mce+kdgR NbvTuOaQhQTGOLibZkVNVVxUV0oZpsudpie8pYesIwOysIpDvyXGYaC7Uf1WySm/Ff ECMxulI6um7JxHOYQxT2pi3p70j3/0Y28bpnSZv+/3KkYWiBY9Z2/roH6FEgF54M7b 6ftEYbt0Hc7/62xbEzP/KPu+Ia+EyLeA0c6ovjf/hBNKcjlbsTU7zvhLdPsyCUWW3l FW9jl+t5PolNw==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar01.francetelecom.fr (ESMTP service) with ESMTPS id 4JSGlR1Ss8zBrLp;  Mon,  3 Jan 2022 14:28:03 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Joel Jaeggli <joelja@bogus.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-multihoming.all@ietf.org" <draft-ietf-dots-multihoming.all@ietf.org>
Thread-Topic: Opsdir early review of draft-ietf-dots-multihoming-09
Thread-Index: AQHX+DpRFRDhDHZ8g0S+QXKBtDvnNKxRUW1g
Content-Class: 
Date: Mon, 3 Jan 2022 13:28:02 +0000
Message-ID: <11252_1641216483_61D2F9E3_11252_455_1_787AE7BB302AE849A7480A190F8B93303546C068@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164029073540.5038.12545190735213564633@ietfa.amsl.com>
In-Reply-To: <164029073540.5038.12545190735213564633@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-03T13:23:04Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=9e1de163-9e64-4a85-bab0-1e1f1f5ba3fc; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/ULma3Y2zq64HFzzZPaLGbfXNcOU>
Subject: Re: [Dots] Opsdir early review of draft-ietf-dots-multihoming-09
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jan 2022 13:28:14 -0000

SGkgSm9lbCwgDQoNClRoYW5rIHlvdSBmb3IgdGhlIHJldmlldy4gDQoNClBsZWFzZSBzZWUgaW5s
aW5lLiANCg0KQ2hlZXJzLA0KTWVkDQoNCj4gLS0tLS1NZXNzYWdlIGQnb3JpZ2luZS0tLS0tDQo+
IERlwqA6IEpvZWwgSmFlZ2dsaSB2aWEgRGF0YXRyYWNrZXIgPG5vcmVwbHlAaWV0Zi5vcmc+DQo+
IEVudm95w6nCoDogamV1ZGkgMjMgZMOpY2VtYnJlIDIwMjEgMjE6MTkNCj4gw4DCoDogb3BzLWRp
ckBpZXRmLm9yZw0KPiBDY8KgOiBkb3RzQGlldGYub3JnOyBkcmFmdC1pZXRmLWRvdHMtbXVsdGlo
b21pbmcuYWxsQGlldGYub3JnDQo+IE9iamV0wqA6IE9wc2RpciBlYXJseSByZXZpZXcgb2YgZHJh
ZnQtaWV0Zi1kb3RzLW11bHRpaG9taW5nLTA5DQo+IA0KPiBSZXZpZXdlcjogSm9lbCBKYWVnZ2xp
DQo+IFJldmlldyByZXN1bHQ6IEhhcyBOaXRzDQo+IA0KPiBJIGhhdmUgcmV2aWV3ZWQgZHJhZnQt
aWV0Zi1kb3RzLW11bHRpaG9taW5nLTA5IGZvciBvbiBiZWhhbGYgb2YgdGhlDQo+IG9wZXJhdGlv
bnMgYW5kIGFuZCBtYW5hZ2VtZW50IGFyZWEgZGlyZWN0b3JhdGUuIFdoaWxlIEkgdGhpbmsgdGhp
cw0KPiBkb2N1bWVudCBpcyBsYXJnZWx5IGNvbXBsZXRlLCBJIGhhdmUgYSBjb3VwbGUgb2YgcXVl
c3Rpb25zIGFiIG91dCB0aGUgd2F5cw0KPiBpbiB3aGljaCBpcyBwcm9wb3NlcyB0byBpbXBsbWVu
dCB0aGUgdmFyaW91cyBjYXNlcyB3aGljaCBtYXkgb3IgbWF5IG5vdA0KPiBhZGQgY2xhcml0eSB0
byB0aGUgZG9jdW1lbnQuDQo+IA0KPiBJdCB3b3VsZCBzZWVtIHRoYXQgdGhlIGNoaWVmIGRpZmZl
cmVuY2UgYmV0d2VlbiB0aGUgcmVzaWRlbnRpYWwgQ1BFIGNhc2UNCj4gYW5kIHRoZSBlbnRlcnBy
aXNlIGNhc2Ugd291bGQgc2VlbSB0byBiZSB0aGUgaW50ZXJjZXNzaW9uIG9mIEJHUCwgIFdobw0K
PiBtYW5hZ2VzIHRoZSBDUEUgZnJvbSB0aGUgdmFudGFnZSBwb2ludCBvZiBjb25maWd1cmF0aW9u
LA0KDQpbTWVkXSBBcyBpbmRpY2F0ZWQgaW4gdGhlIGludHJvZHVjdGlvbiBvZiBTZWN0aW9uIDQs
IHRoZSBtYWluIGRpZmZlcmVuY2UgYmV0d2VlbiB0aGUgdHdvIGlzIHRoYXQgcHJvdmlkZXIgaW5k
ZXBlbmRlbnQgYWRkcmVzc2luZyBpcyBvbmx5IHVzZWQgZm9yIGVudGVycHJpc2VzLCBub3QgcmVz
aWRlbnRpYWwgQ1BFcy4gT3RoZXIgYXNwZWN0cyBzdWNoIGFzIENFLVBFIHJvdXRpbmcsIG1hbmFn
ZW1lbnQgY29udHJvbCwgZXRjLiBhcmUgbm90IHNwZWNpZmljLiBUaGVyZSBhcmUgb2YgY291cnNl
IHNvbWUgZGlmZmVyZW5jZXMgaW4gdGhlIHRlY2huaWNhbCByZWFsaXphdGlvbiBzdWNoIGFzIGFj
dGl2YXRpbmcgYSBkeW5hbWljIHJvdXRpbmcgcHJvdG9jb2wgaW4gdGhlIENFLVBFIGxpbmsgdnMu
IHN0YXRpYyByb3V0aW5nIGJ1dCB3ZSBkb24ndCB0aGluayB0aGF0J3MgaW1wb3J0YW50IHdoZW4g
aXQgY29tZXMgdG8gc2lnbmFsaW5nIGF0dGFja3MuIA0KDQo+IA0KPiBJbiBwcmFjdGljZSBJIGRv
bid0IHNlZSBhIG1lYW5pbmdmdWwgZGlmZmVyZW5jZSBiZXR3ZWVuIGEgc2luZ2xlIENQRSBhbmQN
Cj4gbXVsdGlwbGUgQ1BFcyBpbiB0aGUgZW50ZXJwcmlzZSBjYXNlICg1LjIvNS4zKQ0KDQpbTWVk
XSBUaGVyZSBhcmUgc2ltaWxhcml0aWVzIGJ1dCB0aGVyZSBhcmUgYWxzbyBpbXBsaWNhdGlvbnMs
IGUuZy4sIHdoZW4gaXQgY29tZXMgdG8gZGVwbG95aW5nIGdhdGV3YXlzIGluIGVhY2ggb2YgdGhl
c2UgQ1BFcyBvciB3aGVuIGVhY2ggb2YgdGhlc2UgQ1BFcyBpcyBtYW5pcHVsYXRpbmcgYSBkZWRp
Y2F0ZWQgcHJlZml4LCBldGMuIA0KDQosIHNvdXJjZSBhZGRyZXNzIHNlbGVjdGlvbg0KPiBpcyBh
IGNvb3JkaW5hdGlvbiBwcm9ibGVtIGluIGVpdGhlciBjYXNlPw0KDQpbTWVkXSBUaGlzIG9uZSBp
cyBhcHBsaWNhYmxlIHRvIGJvdGgsIGhvd2V2ZXIgdGhlIG11bHRpLUNQRSBoYXMgYWxzbyB0byBk
ZWFsIHdpdGggdGhlIHNlbGVjdGlvbiBvZiB0aGUgYXBwcm9wcmlhdGUgZXhpdCAoQ1BFKS4gVGhp
cyBpcyBjYWxsZWQgb3V0IGluOiANCg0KICAgVGhlIGRlcGxveW1lbnRzIGRlcGljdGVkIGluIEZp
Z3VyZXMgNyBhbmQgOCBhbHNvIGFwcGx5IHRvIHRoZQ0KICAgc2NlbmFyaW8gZGVzY3JpYmVkIGlu
IFNlY3Rpb24gNC4zLiAgT25lIHNwZWNpZmljIHByb2JsZW0gZm9yIHRoaXMNCiAgIHNjZW5hcmlv
IGlzIHRvIHNlbGVjdCB0aGUgYXBwcm9wcmlhdGUgZXhpdCByb3V0ZXIgd2hlbiBjb250YWN0aW5n
IGENCiAgIGdpdmVuIERPVFMgc2VydmVyLg0KIA0KDQogYnV0IGluIGZhY3QgdGhhdCdzIG1vc3Rs
eSBhDQo+IGNvb3JkaW5hdGlvbiBwcm9ibGVtLiAgc2VsZWN0aW5nIHRoZSBwYXRoIHRvIHRoZSBk
b3RzIHNlcnZlcihzKSBjYW4gYmUNCj4gYWNoaWV2ZWQgdmlhIHJvdXRlIHNlbGVjdGlvbiBpZiBu
byBtZWNoYW5pc20gZm9yIHNpZ25hbGluZyByb3V0ZXMgYmV0d2Vlbg0KPiBDUEVzIHRoYXQgc2Vl
bXMgbGlrZSBhIHNlcmlvdXMgbGltaXRhdGlvbi4NCj4gDQo+IEluIGEgbXVsdGlob21pbmcgc2Nl
bmFyaW8gaW52b2x2aW5nIGEgcHJvdmlkZXIgYXNzaWduZWQgcHJlZml4IHRoZSBwcmVmaXgNCj4g
bWF5IHdlbGwgYmUgYm90aCBkZWFnZ3JhdGVkIGZvciBhIGxhcmdlIHByb3ZpZGVyIGFzc2lnbm1l
bnQgYW5kIGFkdmVydGlzZWQNCj4gdG8gYm90aCBwcm92aWRlcnMgKGUuZy4gSSBoYXZlIGFuIG9m
ZmljZSB3aGljaCByZWNlaXZlcyBhIC8yNCBhc3NpZ25tZW50DQo+IGZyb20gbHVtZW4gYW5kIGFs
c28gYWR2ZXJ0aXNlcyB0aGF0IHNlbGYgc2FtZSBwcmVmaXggdG8gemF5byksIGluIHRoaXMNCj4g
Y2FzZSB0aGUgcHJlZml4IG11c3QgYmUgYWR2ZXJ0aXNlZCBkZS1hZ2dyZWdhdGVkIHRvIGJvdGgg
cHJvdmlkZXJzLg0KPiBlbnRlcnByaXNlIHBhIGFzc2lnbm1lbnRzIG9mIHRoaXMgZm9ybSBhcmUg
bmVjZXNzYXJpbHkgZXF1aXZhbGVudCB0byBwaQ0KPiBwcmVmaXhlcyBmcm9tIGEgdXNhZ2Ugc3Rh
bmRwb2ludC4gd2hpY2ggaXAgaXMgdXNlZCBmb3IgZG90cyBzaWduYWxpbmcgaW4NCj4gY2FzZXMg
bGlrZSB0aGlzIGlzIG5lY2Vzc2FyaWx5IGEgcHJvYmxlbSBvZiBjb29yZGluYXRpb24gd2hldGhl
ciBpdCBiZSB0aGUNCj4gY3BlL3JvdXRlciBwZWVyIGludGVyZmFjZSwgcm91dGVyIGxvb3BiYWNr
LCBvciBzb21lIG90aGVyIHNvdXJjZSBpcA0KPiBlbmNsb3NlZCB3aXRoaW4gdGhlIGFzc2lnbmVk
IHByZWZpeCAob3IgaW5kZWVkIHNvbWUgb3RoZXIgcHJlZml4KS4NCj4gDQo+ID4gV2hlbiBQSSBh
ZGRyZXNzZXMvcHJlZml4ZXMgYXJlIHVzZWQsIERPVFMgY2xpZW50cyBNVVNUIGNvbnRhY3QgYWxs
IHRoZQ0KPiA+IERPVFMNCj4gZ2F0ZXdheXMgdG8gc2VuZCBhIERPVFMgbWVzc2FnZS4NCj4gDQo+
IFdoZW4gZW5nYWdlZCBpbiBET1MgcmVsYXRlZCBzaWduYWxpbmcgbm90IGFsbCBkb3MgYXR0YWNr
cyBhcmUgaW4gZmFjdA0KPiBkaXN0cmlidXRlZCwgd2hlbiBhdHRhY2sgdHJhZmZpYyBpcyB1bnNw
b2ZmZWQgYXMgaXQgaXMgaW4gbW9zdCB1cHBlciBsYXllcg0KPiB0YXJnZXRpbmcgYXR0YWNrcyBp
dCBtdXN0IG5lY2Vzc2FyaWx5IGZvbGxvdyBhIGNvbnNpc3RlbnQgcGF0aCBwZXINCj4gYXR0YWNr
ZXIsIG1vcmVvdmVyLCB5b3VyIHRlbGVtZXRyeSBtYXkgd2VsbCB0ZWxsIHlvdSB3aGljaCBpbmdy
ZXNzDQo+IGludGVyZmFjZSBhbmQgdGhlcmVmb3JlIHByb3ZpZGVyIG5lZWRzIHRvIHJlY2VpdmUg
d2hpY2ggc2lnbmFsaW5nIHNlbmRpbmcNCj4gdGhlbSB0byB1bi1pbXBhY3RlZCBwcm92aWRlcnMg
dW5uZWNlc3NhcnkgYW5kIG1heSByZXN1bHQgaW4gdW5pbnRlbnRpb25hbA0KPiBpbmZvcm1hdGlv
biBsZWFrYWdlLg0KDQpbTWVkXSBUaGUgY2xpZW50cyBkbyBub3Qga25vdyB0aGUgZ2F0ZXdheShz
KSBmcm9tIHdoaWNoIHRoZSBhdHRhY2sgdHJhZmZpYyBpcyByZWNlaXZlZC4gVGhpcyBpcyB3aHkg
dGhleSBoYXZlIHRvIHNvbGljaXQgYWxsIHRoZSBnYXRld2F5cy4gDQoNCj4gDQo+ID4gICBUaGUg
dXNlIG9mIGFueWNhc3QgYWRkcmVzc2VzIGlzIE5PVCBSRUNPTU1FTkRFRCB0byByZWFjaCBET1RT
DQo+IGdhdGV3YXlzLg0KPiANCj4gcHJvdmlkZXIgc3BlY2lmaWMgYW55Y2FzdHMgZG8gbm90IGlu
IHByaW5jaXBsZSBzZWVtIHdvcnNlIHRoZW4gIHByb3ZpZGVyDQoNCltNZWRdIEl0IGlzIGluIHRo
aXMgY2FzZSBhcyBpdCBwcmV2ZW50cyBjb250YWN0aW5nIGFsbCBnYXRld2F5cyB3aGlsZSB1bmlj
YXN0IGFsbG93cyBmb3IgaXQuIFRoaXMgaXMgY292ZXJlZCBieSB0aGlzIHRleHQ6DQoNCiAgIE5v
dGUgdGhhdCBhbnljYXN0IGFkZHJlc3Nlcw0KICAgY2Fubm90IGJlIHVzZWQgdG8gZXN0YWJsaXNo
IERPVFMgc2Vzc2lvbnMgYmV0d2VlbiBET1RTIGNsaWVudHMgYW5kDQogICBET1RTIGdhdGV3YXlz
IGJlY2F1c2Ugb25seSBvbmUgRE9UUyBnYXRld2F5IHdpbGwgcmVjZWl2ZSB0aGUNCiAgIG1pdGln
YXRpb24gcmVxdWVzdC4NCg0KUGxlYXNlIG5vdGUgdGhhdCBhbGwgdGhlc2UgZ2F0ZXdheXMgYXJl
IHBhcnQgb2YgdGhlIHNhbWUgbmV0d29yay4gDQoNCj4gc3BlY2lmaWMgdW5pY2FzdHMsIHRoZXkg
YWxsb3cgYSBwcm92aWRlciByZWR1Y2UgdGhlIGFtbW91bnQgb2YNCj4gY29vcmRpbmF0aW9uIHJl
cXVpcmVkIHdpdGhpbiB0aGVpciBvd24gaW5mcmFzdHJ1Y3R1cmUuDQoNCltNZWRdIEFncmVlLiBB
ZGRlZCBhIHBvaW50ZXIgdG8gU2VjdGlvbiAzLjIuNCBvZiBSRkM4ODExIGZvciB0aGlzIHBhcnQu
DQoNCiBhc3NpZ25pbmcgYSB3ZWxsDQo+IGtub3cgYW55Y2FzdCBmb3IgdGhpcyBwdXJwb3NlIGFt
b25nIGFsbCBwcm92aWRlcnMgb24gdGhlIG90aGVyIGhhbmQgc291bmRzDQo+IGxpa2UgYSB0ZXJy
aWJsZSBpZGVhLCBmb3IgdGhlIHJlYXNvbnMgdGhhdCB3ZWxsIGtub3duLWFueWNhc3RzIGFyZQ0K
PiBnZW5lcmFsbHkgYmFkLg0KPiANCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCgpDZSBtZXNzYWdlIGV0IHNlcyBwaWVjZXMg
am9pbnRlcyBwZXV2ZW50IGNvbnRlbmlyIGRlcyBpbmZvcm1hdGlvbnMgY29uZmlkZW50aWVsbGVz
IG91IHByaXZpbGVnaWVlcyBldCBuZSBkb2l2ZW50IGRvbmMKcGFzIGV0cmUgZGlmZnVzZXMsIGV4
cGxvaXRlcyBvdSBjb3BpZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMgYXZleiByZWN1IGNl
IG1lc3NhZ2UgcGFyIGVycmV1ciwgdmV1aWxsZXogbGUgc2lnbmFsZXIKYSBsJ2V4cGVkaXRldXIg
ZXQgbGUgZGV0cnVpcmUgYWluc2kgcXVlIGxlcyBwaWVjZXMgam9pbnRlcy4gTGVzIG1lc3NhZ2Vz
IGVsZWN0cm9uaXF1ZXMgZXRhbnQgc3VzY2VwdGlibGVzIGQnYWx0ZXJhdGlvbiwKT3JhbmdlIGRl
Y2xpbmUgdG91dGUgcmVzcG9uc2FiaWxpdGUgc2kgY2UgbWVzc2FnZSBhIGV0ZSBhbHRlcmUsIGRl
Zm9ybWUgb3UgZmFsc2lmaWUuIE1lcmNpLgoKVGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVu
dHMgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIG9yIHByaXZpbGVnZWQgaW5mb3JtYXRpb24gdGhh
dCBtYXkgYmUgcHJvdGVjdGVkIGJ5IGxhdzsKdGhleSBzaG91bGQgbm90IGJlIGRpc3RyaWJ1dGVk
LCB1c2VkIG9yIGNvcGllZCB3aXRob3V0IGF1dGhvcmlzYXRpb24uCklmIHlvdSBoYXZlIHJlY2Vp
dmVkIHRoaXMgZW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBhbmQgZGVs
ZXRlIHRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzLgpBcyBlbWFpbHMgbWF5IGJlIGFs
dGVyZWQsIE9yYW5nZSBpcyBub3QgbGlhYmxlIGZvciBtZXNzYWdlcyB0aGF0IGhhdmUgYmVlbiBt
b2RpZmllZCwgY2hhbmdlZCBvciBmYWxzaWZpZWQuClRoYW5rIHlvdS4KCg==


From nobody Mon Jan  3 06:23:05 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D07183A08B5; Mon,  3 Jan 2022 06:23:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 hMnF_LrUD4eo; Mon,  3 Jan 2022 06:23:00 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (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 F0B823A08B4; Mon,  3 Jan 2022 06:22:59 -0800 (PST)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar24.francetelecom.fr (ESMTP service) with ESMTPS id 4JSHyn6f4Dz5wTf;  Mon,  3 Jan 2022 15:22:57 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1641219777; bh=igBlxUg5BNQ5+dABhYCH6zXosRWzKUWZ7qpE4JzkXeM=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=iYKyk8T5fih6rrR3Zj2odAdbkxF2H82p6DwCiIbLKfL0QvH6dWmtkX1BY4uZa8guB /qkO7tgnehCDxmIklvfn3T7nEAvz8L+t9xLz6cmpk/iTSzhzY+mKoOnoAbEKpFP5++ W/UX7RzbUcsKAjCrR3DgsttMTJUqreVujyQo8WXX6ns2rhrzaxiaptgp9M309I8N9h qr6Y1TQzamO+eaLTGeXYnMmGn742GauT8sAIl/R2pqx/GSIRjHlzVR3C+88+l0YYf/ Tky27vVS8ZrhhfdI98JRbNvd6B7Ysz8f7IF7jG7G/1Cn/7IH/JbQW35wwkXPs/D25A SuBp9eBke1qKg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar02.francetelecom.fr (ESMTP service) with ESMTPS id 4JSHyn5dYdzCqlx;  Mon,  3 Jan 2022 15:22:57 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Benjamin Kaduk <kaduk@mit.edu>
CC: "draft-ietf-dots-telemetry.all@ietf.org" <draft-ietf-dots-telemetry.all@ietf.org>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] AD review of draft-ietf-dots-telemetry-16 (Sections 8-10)
Thread-Index: AQHX+5QrBz9AjLCdwEyYBaXM/oU/6axRWhyQ
Content-Class: 
Date: Mon, 3 Jan 2022 14:22:57 +0000
Message-ID: <21727_1641219777_61D306C1_21727_204_1_787AE7BB302AE849A7480A190F8B93303546C0CC@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <12675_1637836624_619F6750_12675_177_6_787AE7BB302AE849A7480A190F8B933035458E4B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <20211228023916.GR11486@mit.edu>
In-Reply-To: <20211228023916.GR11486@mit.edu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-03T13:59:40Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=57fcc848-6497-4ed1-a47d-4cb8e1595764; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/O__2LTwGs6_SQDDS-G38HWGObG8>
Subject: Re: [Dots] AD review of draft-ietf-dots-telemetry-16 (Sections 8-10)
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jan 2022 14:23:04 -0000

Hi Ben,

Please see inline for this specific comment. Thank you.

Cheers,
Med

> -----Message d'origine-----
> De=A0: Dots <dots-bounces@ietf.org> De la part de Benjamin Kaduk
> Envoy=E9=A0: mardi 28 d=E9cembre 2021 03:39
> =C0=A0: BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
> Cc=A0: draft-ietf-dots-telemetry.all@ietf.org; dots@ietf.org
> Objet=A0: Re: [Dots] AD review of draft-ietf-dots-telemetry-16 (Sections =
8-
> 10)
>=20
> Hi Med,
>=20
...
> >
> > >
> > > Also (editorial), I think we should be more clear about when we
> > > switch from describing RFC 9132 behavior to to describing the new
> > > functionality provided by this document.
> > >
> > >    Figure 46 shows an example of an asynchronous notification of
> attack
> > >    mitigation status from the DOTS server.  This notification
> > > signals
> > >
> > > Is the "new stuff" in Figure 46 just the subtree under
> > > :(server-to-client- only)?
>=20
> Oops, I think I meant the tree diagram prior to figure 46, which does not
> seem to have a dedicated label

[Med] Aah, I see. Added a label for it. It is now Figure 46. This tree is a=
bout what the server can send in an update. Except the nodes under "server-=
to-client-only", a server can send in an update the same telemetry nodes as=
 the client can do in an efficacy update (figure 44).

We don't omit the common nodes as this is about distinct operations.=20

 (or "anchor" attribute in the XML).  I can
> see how that made the question confusion; sorry about that.
>=20
> > [Med] What is new is what is indicated right after the text you quoted:
> >
> > " This notification signals
> >    both the mid-percentile value of processed attack traffic and the
> >    peak count of unique sources involved in the attack. "
> >
> >
> > this can be identified in the figure by looking at items that are
> prefixes with "ietf-dots-telemetry:".
> >
> >
> >  The 'total-attack-traffic' leaf seems to be the same content as in
> > > Figure 45, and maybe could be omitted?
> >
> > [Med] Please note this is not for the same mid. Putting that aside, the
> one in Figure 45 is what is seen by the client, while figure 46 as about
> the server's view. Changed the total attack traffic value to avoid
> inducing readers to assume a correlation between the two.
>=20
> (So this comment was attempting to compare two tree diagrams, which
> obviously did not come across properly to you.)  Note that I must have
> meant the other tree diagram in figure 44, not the example message in
> figure 45.

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Mon Jan  3 06:47:03 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 177003A092F; Mon,  3 Jan 2022 06:47:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 Rqa1vGRPUK8u; Mon,  3 Jan 2022 06:46:57 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (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 91E703A0948; Mon,  3 Jan 2022 06:46:57 -0800 (PST)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar20.francetelecom.fr (ESMTP service) with ESMTPS id 4JSJVP5tJyz8ty1;  Mon,  3 Jan 2022 15:46:53 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1641221213; bh=Hwp13aipco8he2V2ZYwI2vOxw/A+/s4eYfVqV2ERsjE=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=KsMgv81mnxtcy9zRPm63wFUwpmo75VGFENNPKqbPl0bXy+0gMzNE+PzjZ9wzqRH+d qJuPe5XG3TeOQiArzYW8Dh9PzeSARsga4AeGpM0WcDOeY2p/njd75IvhDw2dS76l42 fdsaLXL6ujlTVhO8k5cRMHwwiwCDKByqj5vuDyY3LklSMXWYbRixMb77fNgjNkL3Cf BRts2ZIzLyf9MBH4TQkab8B4rbMyWKCyZ3QKkXMFoMeuH7k5f1OiVgXt1imXQ0HAos 1begayStkIq0zgABzmQREedt6/sH4kfNzG8UCQUBAxoikHv+QaGPzsJKD6/e2J3V2T /2U6mvKbONBnQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar03.francetelecom.fr (ESMTP service) with ESMTPS id 4JSJVP4x7HzCql2;  Mon,  3 Jan 2022 15:46:53 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Benjamin Kaduk <kaduk@mit.edu>
CC: "draft-ietf-dots-telemetry.all@ietf.org" <draft-ietf-dots-telemetry.all@ietf.org>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] AD review of draft-ietf-dots-telemetry-16 (Sections 7.1.5 - 7.3)
Thread-Index: AQHX+5cy4DNiYjiaOEWU9VBGQvZeo6xRZBIg
Content-Class: 
Date: Mon, 3 Jan 2022 14:46:52 +0000
Message-ID: <24809_1641221213_61D30C5D_24809_49_1_787AE7BB302AE849A7480A190F8B93303546C10C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <8173_1637848085_619F9415_8173_37_1_787AE7BB302AE849A7480A190F8B933035458F83@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <20211228030106.GS11486@mit.edu>
In-Reply-To: <20211228030106.GS11486@mit.edu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-03T14:26:58Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=5d059e05-9797-4924-b6a2-155b9d4c1438; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/YxksUk8vKqBL7G7918rcAwwOPpk>
Subject: Re: [Dots] AD review of draft-ietf-dots-telemetry-16 (Sections 7.1.5 - 7.3)
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jan 2022 14:47:02 -0000

Re-,

Please see two comments inline.

Cheers,
Med

> -----Message d'origine-----
> De=A0: Benjamin Kaduk <kaduk@mit.edu>
> Envoy=E9=A0: mardi 28 d=E9cembre 2021 04:01
> =C0=A0: BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
> Cc=A0: draft-ietf-dots-telemetry.all@ietf.org; dots@ietf.org
> Objet=A0: Re: [Dots] AD review of draft-ietf-dots-telemetry-16 (Sections
> 7.1.5 - 7.3)
>=20
> Hi Med,
>=20
> Also inline
>=20
> On Thu, Nov 25, 2021 at 01:48:04PM +0000, mohamed.boucadair@orange.com
> wrote:
> > Re-,
> >
> > You can track the changes at: https://tinyurl.com/dots-telemetry-latest.
> >
> > Please see inline for more context for Sections 7.1.5 to 7.3.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De=A0: Dots <dots-bounces@ietf.org> De la part de Benjamin Kaduk
> > > Envoy=E9=A0: mercredi 24 novembre 2021 23:42 =C0=A0:
> > > draft-ietf-dots-telemetry.all@ietf.org
> > > Cc=A0: dots@ietf.org
> > > Objet=A0: [Dots] AD review of draft-ietf-dots-telemetry-16
> > >
> > > Hi all,
> > >
> > ...
> > >
> > > Section 7.1.5
> > >
> > >    vendor-id:  Vendor ID is a security vendor's Enterprise Number as
> > >       registered with IANA [Enterprise-Numbers].  It is a four-byte
> > >       integer value.
> > >
> > >    attack-id:  Unique identifier assigned for the attack.
> > >
> > > If the vendor-id is being used as a scoping value to let each vendor
> > > assign attack-id values, then we should say so here, the first place
> > > we really handle this part of the YANG tree.  Even if not, we should
> > > probably say more about why we care what the vendor-id is, and we
> > > should also say who assigns the attack-id.  (Maybe it's scoped to
> > > the DOTS server; I don't know yet at this point in the document!)
> >
> > [Med] The is assigned by the vendor. We don't have globally unique
> attack-ids and we don't ambition to have such a registry.
> >
> > We have the following in the YANG module "Unique identifier assigned by
> the vendor for the attack".
> >
> > Updated the text to align.
> >
> > >
> > > Furthermore, the module structure where attack-id and vendor-id are
> > > always required, but there is going to need to be the ability to
> > > assign a new attack description at runtime, seems to force us to
> > > conflate externally/statically assigned attack-ids and dynamically
> > > assigned ones in the same number space.  Should we give any guidance
> > > to vendors about how to allocate IDs in a way that will not produce
> > > collisions between predistributed/fixed attack IDs and new ones
> > > created at runtime?  Or is the thought that there will be no dynamic
> > > attack-ids since that just corresponds to the attack-description
> > > string and a generic description can be used if there is not a better
> one available?
> >
> > [Med] We really don't want to interfere with how these ids are assigned
> by vendors. For new attacks, and because the client may not have the
> mapping we do allow for the following:
> >
> >    When conveying attack details in DOTS telemetry messages (Sections
> >    7.2, 7.3, and 8), DOTS agents MUST NOT include the 'attack-
> >    description' attribute unless the corresponding attack mapping
> >    details were not previously shared with the peer DOTS agent.
>=20
> This is good, but it's of the form "only include the string version if you
> can't use a preestablished mapping"; I don't remember any guidance about
> not providing an integer attack-id in this case.

[Med] attack-id must always be provided, otherwise the message won't be val=
id. The value that will be included in the attack-id is a value that will b=
e assigned by a vendor for a new attack.=20

  In particular, since
> 'attack-id' is a list key, it seems to be a mandatory YANG element,
> implying that there needs to be *some* value to put in there even for a
> new attack.
>=20
> > >
> > > Regardless, I think we should have more verbiage as to what the
> > > scope of the attack-id is -- what information is it supposed to
> > > indicate or replace?
> > >
> > >    start-time:  The time the attack started.  The attack's start time
> is
> > >       expressed in seconds relative to 1970-01-01T00:00Z in UTC time
> > >
> > > (nit) "in UTC time" and "Z" seem redundant (which does not
> > > necessarily imply that we should only use one of them...).
> >
> > [Med] We preferred to echo 3.4.2 of RFC8949 cited right after
> >
> > >
> > >       (Section 3.4.2 of [RFC8949]).  The CBOR encoding is modified so
> > >       that the leading tag 1 (epoch-based date/time) MUST be omitted.
> > >
> > > (nit) Maybe we should move the CBOR section reference to after we
> > > start talking about CBOR encoding.  (And we should do the same for
> > > 'end-time', if we do anything.)
> >
> > [Med] The section where we discuss CBOR encoding is 4.5. I prefer to
> keep this mention here. Thanks.
> >
> > >
> > >    top-talker:  A list of top talkers among attack sources.  The top
> > >       talkers are represented using the 'source-prefix'.
> > >
> > > Is there a good reference or short description for the notion of
> > > top- talkers?  I know it's a well-established term of art in many
> > > different circles, but it's hard to be fully confident that all
> > > readers will be familiar with it.
> >
> > [Med] What about:
> >
> >       A list of attack sources that are involved in an attack
> >       and which are generating an important part of the attack traffic.
>=20
> I'll take it; thanks.
>=20
> > >
> > > Also, should we say anything about how the number of talkers to
> > > include is determined?  (I assume it is best left to the discretion
> > > of the sender, but we probably want to set a clear expectation that
> > > the list is not all talkers or a complete list in any other way.)
> >
> > [Med] We don't include any hint as this is deployment-specific.
> >
> > >
> > >       'spoofed-status' indicates whether a top talker is a spoofed IP
> > >       address (e.g., reflection attacks) or not.
> > >
> > > Is this something that can be unambiguously determined by all
> > > parties that might be producing this telemetry data, or should we
> > > use a tri-statae (for
> > > "unknown") rather than a boolean to represent it?
> >
> > [Med] The unknown status is handled by not including the leaf. Update
> the text to indicate so.
>=20
> Ah, that makes sense.
>=20
> > >
> > >    In order to optimize the size of telemetry data conveyed over the
> > >    DOTS signal channel, DOTS agents MAY use the DOTS data channel
> > >    [RFC8783] to exchange vendor specific attack mapping details (that
> > >    is, {vendor identifier, attack identifier} =3D=3D> attack descript=
ion).
> > >    As such, DOTS agents do not have to convey systematically an attack
> > >    description in their telemetry messages over the DOTS signal
> channel.
> > >
> > > It's a little surprising to me that this is only a MAY.  Does it
> > > make sense as a SHOULD (expected to usually happen, but leaving open
> > > the flexibility when an observed attack does not match a previously
> > > characterized attack description)?
> >
> > [Med] We went for "MAY" because this is an optimization for a an
> optional feature.
> >
> > >
> > > Also, when reading this I assumed that the "attack description"
> > > being mapped to could include things like the target port/protocol,
> > > whether it was spoofed, etc.
> >
> > [Med] Some of the details you cited can be discovered during an attack.
> >
> >   But reading on to the ietf-dots-mapping module, it
> > > seems that this is intended to just be the single "attack-description"
> > > string.
> >
> > [Med] This is the portion that consumes most packet size and is thus
> problematic.
> >
> >   If so, we might give some more indications of that, e.g., by
> > > spelling it that way and having some prose about it being a
> > > "string", or similar.
> >
> > [Med] OK.
> >
> > >
> > > Also^2, from here to the end of the section might benefit from being
> > > split off into a dedicated subsection on using the data channel to
> > > pre-populate vendor and attack description information
> >
> > [Med] Makes sense.
> >
> > >
> > >    tables are at different revisions.  The DOTS client SHOULD transmit
> > >    telemetry information using the vendor mapping(s) that it provided
> to
> > >    the DOTS server and the DOTS server SHOULD use the vendor
> mappings(s)
> > >    provided to the DOTS client when transmitting telemetry data to
> peer
> > >    DOTS agent.
> > >
> > > Having read a bit further on, I'm not actually sure where in the
> > > protocol the client has provided vendor mappings to the server, and
> > > the server provided vendor mappings to the client.  It *might* be
> > > the GET and POST from/to dots-data/ietf-dots-mapping:vendor-mapping,
> > > but we don't really give a clear indication of that.  I think we
> > > should try to be more precise about what we mean by "provided".
> >
> > [Med] added: (e.g., using a POST as depicted in Figure 34)
> >
> > > (editorial) would this then be "SHOULD use any vendor mapping(s)"
> > > (s/the/any/)?
> >
> > [Med] Yeah.
> >
> > >
> > >      augment /data-channel:dots-data/data-channel:capabilities:
> > >        +--ro vendor-mapping-enabled?   boolean {dots-telemetry}?
> > >
> > > None of the other capabilities in this tree (as specified by RFC
> > > 8783) include a name suffix like "-enabled".  Should this just be
> > > "vendor- mapping"?
> >
> > [Med] We could, but we went for -enabled to ease referencing this data
> node in the text. See for example:
> >
> >    attack mapping details is supported by the server (i.e., check the
> >    value of 'vendor-mapping-enabled').
> >
> > Otherwise, we would need to provide the full hierarchy because we do
> > have "vendor-mapping" in
> >
> >      augment /data-channel:dots-data:
> >        +--ro vendor-mapping {dots-telemetry}?
>=20
> Okay.  We can see if anyone complains later on.
>=20
> > >
> > >            "vendor-id": 1234,
> > >            "vendor-name": "mitigator-s",
> > >            "last-updated": "1576856561",
> > >            "attack-mapping": []
> > >
> > > [this last updated is from December 2019; we could probably pick
> > > something more current if we wanted, but it doesn't really matter.]
> >
> > [Med] OK
> >
> > >
> > >    The DOTS client reiterates the above procedure regularly (e.g.,
> once
> > >    a week) to update the DOTS server's vendor attack mapping details.
> > >
> > > Do the udpates have to preserve any existing assignments?
> >
> > [Med] No. The client can even determine that a given vendor is not used
> anymore.
>=20
> I was trying to ask if the server has to preserve its existing assignments
> when the client asks for the current mapping.  In some sense it's just a
> "quality of implementation" matter for the server, but on the other hand
> if it's allowed to change, we may have to give clients a warning to
> prepare for that.
>=20

[Med] A server may install a new mapping table (a new vendor, for example).=
 This is why the client is asked to send regularly GETs to the server to de=
tect changes.=20


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Mon Jan  3 08:22:31 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D9A93A08CE for <dots@ietfa.amsl.com>; Mon,  3 Jan 2022 08:22:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 2-H3bfQWZ72o for <dots@ietfa.amsl.com>; Mon,  3 Jan 2022 08:22:22 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (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 C0B4F3A0867 for <dots@ietf.org>; Mon,  3 Jan 2022 08:22:16 -0800 (PST)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar22.francetelecom.fr (ESMTP service) with ESMTPS id 4JSLcQ6tj5z30V5;  Mon,  3 Jan 2022 17:22:14 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1641226935; bh=Kmew+cElFqUu2YOGDQfKkfStKJzvUd42an93HJO6S04=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=spkUx+veccNwqJAtN8TmXwnKMM8uDIvF+ppzdCW8sMEVNEUfuY/zbpjFgAFaociUb Btg8JPgzOCOBXo41xWRKVQfO3a4Of0SBn7h6oK2EWr3X7v0lOYDDM4xAPG0zWPdS4u FxNHybW//65JNh/c+9shrbKs2H1C+CsfZDNI1fSKGEpG5uKlzdueKgOXWreONZSe3a iaQpGOD+cxKC5kqK7dc2gFt9OqMOjPoN1QbBvwy4J3q9I76THbaOxVwrBR4VIYXzAJ 6RkQ3cQbPfxUHlJ+9ADANXV4m+vQUMWqrqPLkVqam9A/NVoOdUz3DWYZbCV6+N4IDm dZYijh58E8KGA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar01.francetelecom.fr (ESMTP service) with ESMTPS id 4JSLcQ5qGKzBrMN;  Mon,  3 Jan 2022 17:22:14 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Benjamin Kaduk <kaduk@mit.edu>
CC: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] AD review of draft-ietf-dots-telemetry-16
Thread-Index: AQHX/AFSOpcExwK+N0ifnw7xhdZO3axRbYJw
Content-Class: 
Date: Mon, 3 Jan 2022 16:22:13 +0000
Message-ID: <7036_1641226934_61D322B6_7036_251_12_787AE7BB302AE849A7480A190F8B93303546C1F3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <20211124224140.GH93060@kduck.mit.edu> <CAFpG3gfBSarzE7aPm6JM0h1LJHt=DwfKXnaRUGosU6_=VY150A@mail.gmail.com> <20211228154033.GU11486@mit.edu>
In-Reply-To: <20211228154033.GU11486@mit.edu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-03T16:18:33Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=6e038553-35a3-4636-bb5f-75e6009cf7a6; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/5xbY_jhdbJkCbKHSIgu-Vj9uW-4>
Subject: Re: [Dots] AD review of draft-ietf-dots-telemetry-16
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jan 2022 16:22:30 -0000

Re-,

Please find below some follow-up replies.

Cheers,
Med

> -----Message d'origine-----
> De=A0: Dots <dots-bounces@ietf.org> De la part de Benjamin Kaduk
> Envoy=E9=A0: mardi 28 d=E9cembre 2021 16:41
> =C0=A0: tirumal reddy <kondtir@gmail.com>
> Cc=A0: draft-ietf-dots-telemetry.all@ietf.org; dots@ietf.org
> Objet=A0: Re: [Dots] AD review of draft-ietf-dots-telemetry-16
>=20
> Hi Tiru,
>=20
> Thanks for these (and thanks Med as well for the additional follow-up; I
> don't think I have any replies to that part).
> A few comments inline...
>=20
...
> > >
> > > It looks like we have to use backslash continuation markers for
> several of
> > > the CoAP request target resources in the examples; do we want to
> reference
> > > RFC 8792 folding and use its specific note text about line wrapping?
> > >
> > > There are a few places where we say something like "the DOTS client
> MUST
> > > auto-scale so that the appropriate unit is used".  (1) We don't
> > > specifically
> > > say what the goal of this automatic behavior is (I guess, use the
> "largest
> > > unit" that gives a value greater than one?), and (2) it seems that we
> are
> > > in
> > > part relying on this behavior to ensure that the client only specifies
> one
> > > measure in a given unit class.  That is, I didn't see anything else
> that
> > > would prevent a client from sending (say) both Mbps and Gbps values,
> that
> > > could of course be in conflict with each other -- if there's a
> potential
> > > for
> > > conflict we'd need to say how to resolve the conflict.
> > >
> > > Relatedly, there seems to *also* be potential for conflict in that we
> allow
> > > both bit/second and Byte/second as unit-classes.  What is to happen if
> I
> > > say
> > > that something is both 2 bit/second and 2 Byte/second?
>=20
> Med's follow-up implies that we are to just treat that as "invalid
> parameters".  I'd prefer to be more explicit about that, e.g., with a
> statement like "at most one of the bit/second and Byte/second unit-class
> entries can be present; if such conflicting values are received the
> combination is treated as specifying an illegal parameter and rejected
> with
> 4.00 (Bad Request)".

[Med] Added this NEW text:=20

"Supplying both bits per second and bytes per second unit-classes is allowe=
d for a given telemetry data. However, receipt of conflicting values is tre=
ated as invalid parameters and rejected with 4.00 (Bad Request)."

>=20
> > > We have a lot of examples that use the same 'cuid' of
> > > dz6pHjaADkaFTbjr0JGBpw, which is fine and representative of normal
> > > operation.  Do we want to curate the 'tsid' and 'tmid' values used by
> that
> > > client?  I see some reuse, which I think is not prohibited (at least
> for
> > > 'tsid'), but may merit checking, and the values are not monotonically
> > > increasing throughout the course of the document, which may or may not
> be
> > > desirable.
>=20
> Did you have any thoughts on this part?

[Med] The reuse of some ids is normal as this is done to retrieve or to del=
ete an entry. Made some changes to monotonically increase ids (https://tiny=
url.com/dots-telemetry-latest).=20=20

...
> > >
> > > Section 6
> > >
> > >    Telemetry setup configuration is bound to a DOTS client domain.
> DOTS
> > >    servers MUST NOT expect DOTS clients to send regular requests to
> > >    refresh the telemetry setup configuration.  Any available telemetry
> > >    setup configuration has a validity timeout of the DOTS association
> > >    with a DOTS client domain.  [...]
> > >
> > > The term "DOTS association" does not seem to have been used previously
> > > (in RFC 9132 we discuss the "DOTS session" heavily, though).  Also, I
>=20
> Are we planning to keep the "DOTS association" phrasing?

[Med] Changed to: "Any available telemetry setup configuration is valid til=
l the DOTS server ceases to service a DOTS client domain."

>=20
> > > don't remember any previous requirement to keep state on the server
> for
> > > the duration of anything scoped to the entire client *domain*, just
> > > individual DOTS sessions.  We do mention detecting
> conflicts/overlapping
> > > requests within the scope of a client domain, in RFC 9132, but as far
> as
> > > I can tell that only holds when all the DOTS sessions involved in the
> > > conflict are still active.
> > >
> > > Perhaps related, this discussion (at least so far) is not clear to me
> > > about what level of coordination/consistency is expected between
> clients
> > > in the same domain.  I believe that stock DOTS works fine with no such
> > > coordination amongst clients within a domain, so if we are introducing
> such
> > > a requirement we should say prominently that it's a change.
> > >
> >
> > Yes, telemetry configuration is not specific to the client. For example,
> > the pipe capacity is specific to the site.
>=20
> So what happens if there are two clients in a site and they are reporting
> different values for pipe-capacity?

[Med] This is covered in this part:

   A DOTS server may detect conflicts between requests conveying pipe
   and baseline information received from DOTS clients of the same DOTS
   client domain. 'conflict-information' is used to report the conflict
   to the DOTS client following similar conflict handling discussed in
   Section 4.4.1 of [RFC9132].

>=20
> I think I'm just generally unsure what the expected division of work is
> between multiple clients in a domain, so my questions involve a lot of
> speculating and I don't have a good suggestion for changes to the text
> yet.
>=20
> >
> > >
> > > Section 6.1.1
> > >
> > >    Upon receipt of such request, and assuming no error is encountered
> by
> > >    processing the request, the DOTS server replies with a 2.05
> (Content)
> > >    response that conveys the current and telemetry parameters
> acceptable
> > >    by the DOTS server.  [...]
> > >
> >
> > NEW:
> >
> > Upon receipt of such request, and assuming no error is encountered by
> >
> > processing the request, the DOTS server replies with a 2.05 (Content)
> >
> > response that conveys the telemetry parameters acceptable by the DOTS
> > server
> >
> > and the current baseline information maintained by the DOTS server.
> >
> >
> > >
> > > (editorial) Something seems off, here (around "current and telemetry
> > > parameters acceptable").  Is it returning current configuration,
> acceptable
> > > parameter values, or some combination thereof?
> > >
> > >           |  |     +-- query-type*            query-type
> > >
> > > Since this is a leaf-list of supported query types, should the list
> name
> > > include the word "supported" or similar?
> > >
> > > Section 6.1.2
> > >
> > >    The PUT request with a higher numeric 'tsid' value overrides the
> DOTS
> > >    telemetry configuration data installed by a PUT request with a
> lower
> > >    numeric 'tsid' value.  To avoid maintaining a long list of 'tsid'
> > >    requests for requests carrying telemetry configuration data from a
> > >    DOTS client, the lower numeric 'tsid' MUST be automatically deleted
> > >    and no longer be available at the DOTS server.
> > >
> > > The way this is phrased with "the lower" and "higher" (vs "highest")
> > > assumes
> > > or implies that there is only one "lower" 'tsid' value, perhaps
> leaving
> > > some
> > > ambiguity if there is actually more than one.  We might make a
> statement
> > > about how there is only at most one active 'tsid' per 'cuid'+'cdid' at
> a
> > > time other than during a config change (if that's the intent), or
> > > alternatively to qualify that the requirement to remove is only
> incurred in
> > > the event of a conflict (as is done for other types of config, later).
> > >
> >
> > We can have multiple tsids for the same client for pipe/baseline
> > information. This is why we have:
> >
>=20
> Ok.  Should we say something like "when telemetry configuration data is
> received that has overlapping scope with existing telemetry configuration,
> the PUT request with higher numeric 'tsid' value [...]"?
>=20

[Med] Actually, there is only one tsid in the context of 6.1.2. I don't thi=
nk a change is needed to the OLD text. Of course, multiple tsids are allowe=
d for pipe/baseline but that is covered in 6.2.1/6.3.1.

Thank you.=20

> The rest of this looks good; thanks again for all the updates.
>=20
> -Ben

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Mon Jan  3 08:42:37 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59BCF3A0812 for <dots@ietfa.amsl.com>; Mon,  3 Jan 2022 08:42:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 USPLsotRW_H6 for <dots@ietfa.amsl.com>; Mon,  3 Jan 2022 08:42:30 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.36]) (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 965823A080E for <dots@ietf.org>; Mon,  3 Jan 2022 08:42:30 -0800 (PST)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr25.francetelecom.fr (ESMTP service) with ESMTPS id 4JSM3m5pblzCrnp;  Mon,  3 Jan 2022 17:42:28 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1641228148; bh=qBvquYQJmhUWIX5nZ4mkRGt7AIU982qCIHuvgHF1SgA=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=fKw2l8ULZuSH98VBsXJ2MBdQ48PB6wOHLZheBW884do6Lwfchbb9rrOSKKAfUMvv3 lIiDjysBOjU/RxP63FfYbSHkVwk2fr8bctrH7FVaPNP+RmJdDErVo8PsUmELNMfref VT/YGm9ZXk9uj3Tw5TLTtSzZgXoKtkyVjw0fXpxJbKBGy/ZPlj8LTr6t08KwHnc9Gj 1IL715Y9p2Dhi66JTUSeY40bu8enFqhPueF3BspSXgYYlbQevRCRJuD3qYI+ijCTgC HcMQofVut9Vg33gSeFR8wIpxF7Nm9wyOjet66hvaitLXA6FM1yVa9XfesG91338C7a nSYEi9yECVPeQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr05.francetelecom.fr (ESMTP service) with ESMTPS id 4JSM3m4PVjzyhX; Mon,  3 Jan 2022 17:42:28 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Benjamin Kaduk <kaduk@mit.edu>
CC: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] I-D Action: draft-ietf-dots-telemetry-18.txt
Thread-Index: AQHX/ALp1EX80f/8KkG6r6xHtj4DE6xRhO/w
Content-Class: 
Date: Mon, 3 Jan 2022 16:42:27 +0000
Message-ID: <9216_1641228148_61D32774_9216_234_7_787AE7BB302AE849A7480A190F8B93303546C22B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <163939252488.21261.15352577366570117756@ietfa.amsl.com> <23629_1639392661_61B72595_23629_108_1_787AE7BB302AE849A7480A190F8B9330354635AD@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <20211228155203.GV11486@mit.edu>
In-Reply-To: <20211228155203.GV11486@mit.edu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-03T16:41:46Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=1b0687fc-6185-495b-b8a6-cd260362f8bb; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/M56ccLfq8i4uCQF08THOrFjxpHg>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-telemetry-18.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jan 2022 16:42:35 -0000

Re-,

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De=A0: Dots <dots-bounces@ietf.org> De la part de Benjamin Kaduk
> Envoy=E9=A0: mardi 28 d=E9cembre 2021 16:52
> =C0=A0: BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
> Cc=A0: dots@ietf.org
> Objet=A0: Re: [Dots] I-D Action: draft-ietf-dots-telemetry-18.txt
>=20
> On Mon, Dec 13, 2021 at 10:51:00AM +0000, mohamed.boucadair@orange.com
> wrote:
> > Hi Ben, all,
> >
> > This version integrates the AD review.
> >
> > Please let us know if there are issues we didn't address. Thank you.
>=20
> Thanks, and sorry for not tending to my email more quickly.
>=20
> You probably already saw the handful of replies I sent to the email thread
> (and https://github.com/boucadair/draft-dots-telemetry/pull/10).
>=20
> I do not think I saw a reply to this remark on Section 8.1:
>=20
> =3D=3D=3D
>    In order to signal telemetry data in a mitigation efficacy update, it
>    is RECOMMENDED that the DOTS client has already established a DOTS
>    telemetry setup session with the server in 'idle' time.
>=20

[Med] This recommendation is to make sure that the server understands the t=
elemetry attributes before using them. Otherwise, there is a risk that a me=
ssage with the telemetry attributes will be rejected by a legacy server.=20

> If I understand correctly, it seems that at least part of the need for
> having a preestablished telemetry session is that the mitigation efficacy
> update is identified only by the 'mid', and so we cannot specify a 'tmid'
> as part of such an efficacy update.  Thus, in order for the server to
> associate the telemetry data in the efficacy update with an ongoing
> telemetry status session, the 'tsid' must be associated with the 'mid'
> that is the subject of the efficacy update.
> If that is correct, then I think we should have some text here about how
> the efficacy update does not/cannot include the 'tmid', and so is
> associated with the 'mid' of the update.
> =3D=3D=3D
>=20
> Of the things in the email chain, I am most interested in getting clarity
> around:
>=20
> - what to put in the "attack-id" field when we are sending an
>   "attack-description" string for a not-previously-characterized attack
> (or
>   make that field not mandatory at the YANG level).

[Med] The attack-id is assigned by vendors. This applies for both shared an=
d new attacks.=20

>=20
> - when a server updates its published attack mappings, if there's a
>   requirement/expectation that already assigned attack-id values retain
> the
>   same meaning.

[Med] This was clarified in another message.

>=20
> Thanks again,
>=20
> Ben
>=20
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Mon Jan  3 10:07:09 2022
Return-Path: <joelja@bogus.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 753063A0654; Mon,  3 Jan 2022 10:07:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, SPF_NONE=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 ICEUYi23hMjV; Mon,  3 Jan 2022 10:07:02 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 C5F1A3A0653; Mon,  3 Jan 2022 10:07:02 -0800 (PST)
Received: from [IPV6:2601:1c0:cb00:5dd1:dcc2:d39e:3984:12b3] ([IPv6:2601:1c0:cb00:5dd1:dcc2:d39e:3984:12b3]) (authenticated bits=0) by nagasaki.bogus.com (8.16.1/8.16.1) with ESMTPSA id 203I6xa3025921; Mon, 3 Jan 2022 18:07:00 GMT (envelope-from joelja@bogus.com)
Message-ID: <07d1a5b0-0ccd-a871-4a94-b7bfef520894@bogus.com>
Date: Mon, 3 Jan 2022 10:06:52 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
To: mohamed.boucadair@orange.com, "ops-dir@ietf.org" <ops-dir@ietf.org>
Cc: "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-multihoming.all@ietf.org" <draft-ietf-dots-multihoming.all@ietf.org>
References: <164029073540.5038.12545190735213564633@ietfa.amsl.com> <11252_1641216483_61D2F9E3_11252_455_1_787AE7BB302AE849A7480A190F8B93303546C068@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <11252_1641216483_61D2F9E3_11252_455_1_787AE7BB302AE849A7480A190F8B93303546C068@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/tIV_LVZJS75g7xDV_2jw-LDyFwE>
Subject: Re: [Dots] Opsdir early review of draft-ietf-dots-multihoming-09
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jan 2022 18:07:08 -0000

On 1/3/22 05:28, mohamed.boucadair@orange.com wrote:
> Hi Joel,
>
> Thank you for the review.
>
> Please see inline.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : Joel Jaeggli via Datatracker <noreply@ietf.org>
>> Envoyé : jeudi 23 décembre 2021 21:19
>> À : ops-dir@ietf.org
>> Cc : dots@ietf.org; draft-ietf-dots-multihoming.all@ietf.org
>> Objet : Opsdir early review of draft-ietf-dots-multihoming-09
>>
>> Reviewer: Joel Jaeggli
>> Review result: Has Nits
>>
>> I have reviewed draft-ietf-dots-multihoming-09 for on behalf of the
>> operations and and management area directorate. While I think this
>> document is largely complete, I have a couple of questions ab out the ways
>> in which is proposes to implment the various cases which may or may not
>> add clarity to the document.
>>
>> It would seem that the chief difference between the residential CPE case
>> and the enterprise case would seem to be the intercession of BGP,  Who
>> manages the CPE from the vantage point of configuration,
> [Med] As indicated in the introduction of Section 4, the main difference between the two is that provider independent addressing is only used for enterprises, not residential CPEs. Other aspects such as CE-PE routing, management control, etc. are not specific. There are of course some differences in the technical realization such as activating a dynamic routing protocol in the CE-PE link vs. static routing but we don't think that's important when it comes to signaling attacks.
>
>> In practice I don't see a meaningful difference between a single CPE and
>> multiple CPEs in the enterprise case (5.2/5.3)
> [Med] There are similarities but there are also implications, e.g., when it comes to deploying gateways in each of these CPEs or when each of these CPEs is manipulating a dedicated prefix, etc.
>
> , source address selection
>> is a coordination problem in either case?
> [Med] This one is applicable to both, however the multi-CPE has also to deal with the selection of the appropriate exit (CPE). This is called out in:
>
>     The deployments depicted in Figures 7 and 8 also apply to the
>     scenario described in Section 4.3.  One specific problem for this
>     scenario is to select the appropriate exit router when contacting a
>     given DOTS server.
>   
>
>   but in fact that's mostly a
>> coordination problem.  selecting the path to the dots server(s) can be
>> achieved via route selection if no mechanism for signaling routes between
>> CPEs that seems like a serious limitation.
>>
>> In a multihoming scenario involving a provider assigned prefix the prefix
>> may well be both deaggrated for a large provider assignment and advertised
>> to both providers (e.g. I have an office which receives a /24 assignment
>> from lumen and also advertises that self same prefix to zayo), in this
>> case the prefix must be advertised de-aggregated to both providers.
>> enterprise pa assignments of this form are necessarily equivalent to pi
>> prefixes from a usage standpoint. which ip is used for dots signaling in
>> cases like this is necessarily a problem of coordination whether it be the
>> cpe/router peer interface, router loopback, or some other source ip
>> enclosed within the assigned prefix (or indeed some other prefix).
>>
>>> When PI addresses/prefixes are used, DOTS clients MUST contact all the
>>> DOTS
>> gateways to send a DOTS message.
>>
>> When engaged in DOS related signaling not all dos attacks are in fact
>> distributed, when attack traffic is unspoffed as it is in most upper layer
>> targeting attacks it must necessarily follow a consistent path per
>> attacker, moreover, your telemetry may well tell you which ingress
>> interface and therefore provider needs to receive which signaling sending
>> them to un-impacted providers unnecessary and may result in unintentional
>> information leakage.
> [Med] The clients do not know the gateway(s) from which the attack traffic is received. This is why they have to solicit all the gateways.
I find that dubious if you're receiving packet related telemetery in 
order to identify ddos in the first place finding where it ingressed 
your network is fairly critical (we do this with IPFIX, have been doing 
it for more than a decade) source based rtbh/bgp flow spec 
implementation which is the precursor to this work more or less assume 
you can identify the provider to signal. Assuming that you cannot, the 
question of information leakage persists, and should be noted, as you 
are signaling to a provider that  may or may not be a conduit of the 
attack that you are being attacked, and likewise may unintentionally 
make the attack more effective by applying ip based mitigitations to 
paths over which legitimate rather than attack traffic is traversing.
>>>    The use of anycast addresses is NOT RECOMMENDED to reach DOTS
>> gateways.
>>
>> provider specific anycasts do not in principle seem worse then  provider
> [Med] It is in this case as it prevents contacting all gateways while unicast allows for it. This is covered by this text:
>
>     Note that anycast addresses
>     cannot be used to establish DOTS sessions between DOTS clients and
>     DOTS gateways because only one DOTS gateway will receive the
>     mitigation request.
>
> Please note that all these gateways are part of the same network.
in practice you probably don't need signal all of them, potentially in a 
large provider there are hundreds, if you have one or few ingress points 
from a provider to your network you don't need to signals many upsteam 
dots servers in order for the provider to install a mitigiation, one is 
sufficient.
>
>> specific unicasts, they allow a provider reduce the ammount of
>> coordination required within their own infrastructure.
> [Med] Agree. Added a pointer to Section 3.2.4 of RFC8811 for this part.
>
>   assigning a well
>> know anycast for this purpose among all providers on the other hand sounds
>> like a terrible idea, for the reasons that well known-anycasts are
>> generally bad.
>>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>


From nobody Tue Jan  4 00:38:39 2022
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C3FA03A1949; Tue,  4 Jan 2022 00:38:32 -0800 (PST)
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: dots@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.41.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dots@ietf.org
Message-ID: <164128551273.11649.12733481825423212960@ietfa.amsl.com>
Date: Tue, 04 Jan 2022 00:38:32 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/9P0ZF8zJa8EVVjwib46DH13Ec38>
Subject: [Dots] I-D Action: draft-ietf-dots-multihoming-10.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2022 08:38:33 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the DDoS Open Threat Signaling WG of the IETF.

        Title           : Multi-homing Deployment Considerations for Distributed-Denial-of-Service Open Threat Signaling (DOTS)
        Authors         : Mohamed Boucadair
                          Tirumaleswar Reddy
                          Wei Pan
	Filename        : draft-ietf-dots-multihoming-10.txt
	Pages           : 16
	Date            : 2022-01-04

Abstract:
   This document discusses multi-homing considerations for Distributed-
   Denial-of-Service Open Threat Signaling (DOTS).  The goal is to
   provide some guidance for DOTS clients and client-domain DOTS
   gateways when multihomed.


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

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dots-multihoming-10

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


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts



From nobody Tue Jan  4 00:40:30 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FE263A0C0B; Tue,  4 Jan 2022 00:40:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 xkJ_aY-TkhV6; Tue,  4 Jan 2022 00:40:24 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (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 144153A0C0D; Tue,  4 Jan 2022 00:40:24 -0800 (PST)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr21.francetelecom.fr (ESMTP service) with ESMTPS id 4JSmJz2C4xz5wNP;  Tue,  4 Jan 2022 09:40:19 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1641285619; bh=pWxb8pggQTFk/0xrm69egzNqdUB9l1IEgzKMu7Y4HF4=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=gy80nClsY3hyFwKABnB4JwqchTS1XiAifylGcvr2QAhzWJo3Ww48gbL9AdeUFhcah OTMSUqKjUH5pZ7oJKc9DFXB9Pf1+TexRUYFBTDiOmiH6Xuri3MW7FvWsDeQlTleUuZ hPJsVhR+hvpO9fHuhPpCv+28CugMEKmA6A6ur/Y20CsqpyPGCn6eh9TWn7MtLerWoD QPI8mD7NrkZjgbN2ls3NT9oqLL4P/KL4H4QRMrgHjgJ1aNCoXFLi63laUWeCtvHoeA qI+7nyvReFaIszBfmJN0glSnP3M0uVW2F4zosSW0SG8kUISYAq6JpOzxO7obrwLtjT T1nG3zcZ5Myag==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr02.francetelecom.fr (ESMTP service) with ESMTPS id 4JSmJz11NSz8sYK;  Tue,  4 Jan 2022 09:40:19 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Joel Jaeggli <joelja@bogus.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-multihoming.all@ietf.org" <draft-ietf-dots-multihoming.all@ietf.org>
Thread-Topic: Opsdir early review of draft-ietf-dots-multihoming-09
Thread-Index: AQHYAMy3idAzk0fRxUytuhdval+6baxSe53w
Content-Class: 
Date: Tue, 4 Jan 2022 08:40:18 +0000
Message-ID: <16812_1641285619_61D407F3_16812_49_1_787AE7BB302AE849A7480A190F8B93303546C6AD@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164029073540.5038.12545190735213564633@ietfa.amsl.com> <11252_1641216483_61D2F9E3_11252_455_1_787AE7BB302AE849A7480A190F8B93303546C068@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <07d1a5b0-0ccd-a871-4a94-b7bfef520894@bogus.com>
In-Reply-To: <07d1a5b0-0ccd-a871-4a94-b7bfef520894@bogus.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-04T07:42:34Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=54fcef5d-690f-405e-a0c3-bcbfef88bbc7; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/rmc6u_x8Nbo_0gjB6p9aJceK8gQ>
Subject: Re: [Dots] Opsdir early review of draft-ietf-dots-multihoming-09
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2022 08:40:29 -0000

SGkgSm9lbCwNCg0KVGhhbmsgeW91IGZvciB0aGUgZm9sbG93LXVwLiBNdWNoIGFwcHJlY2lhdGVk
LiANCg0KTWFkZSBzb21lIGNoYW5nZXMgdG8gYWRkcmVzcyB5b3VyIGNvbW1lbnRzLiBUaGUgY2hh
bmdlcyBjYW4gYmUgdHJhY2tlZCBhdDogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwy
PWRyYWZ0LWlldGYtZG90cy1tdWx0aWhvbWluZy0xMC4NCg0KUGxlYXNlIHNlZSBpbmxpbmUgZm9y
IG1vcmUgY29udGV4dC4gDQoNCkNoZWVycywNCk1lZA0KDQo+IC0tLS0tTWVzc2FnZSBkJ29yaWdp
bmUtLS0tLQ0KPiBEZcKgOiBKb2VsIEphZWdnbGkgPGpvZWxqYUBib2d1cy5jb20+DQo+IEVudm95
w6nCoDogbHVuZGkgMyBqYW52aWVyIDIwMjIgMTk6MDcNCj4gw4DCoDogQk9VQ0FEQUlSIE1vaGFt
ZWQgSU5OT1YvTkVUIDxtb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tPjsgb3BzLQ0KPiBkaXJA
aWV0Zi5vcmcNCj4gQ2PCoDogZG90c0BpZXRmLm9yZzsgZHJhZnQtaWV0Zi1kb3RzLW11bHRpaG9t
aW5nLmFsbEBpZXRmLm9yZw0KPiBPYmpldMKgOiBSZTogT3BzZGlyIGVhcmx5IHJldmlldyBvZiBk
cmFmdC1pZXRmLWRvdHMtbXVsdGlob21pbmctMDkNCj4gDQo+IA0KWy4uLl0NCj4gPj4NCj4gPj4+
IFdoZW4gUEkgYWRkcmVzc2VzL3ByZWZpeGVzIGFyZSB1c2VkLCBET1RTIGNsaWVudHMgTVVTVCBj
b250YWN0IGFsbA0KPiA+Pj4gdGhlIERPVFMNCj4gPj4gZ2F0ZXdheXMgdG8gc2VuZCBhIERPVFMg
bWVzc2FnZS4NCj4gPj4NCj4gPj4gV2hlbiBlbmdhZ2VkIGluIERPUyByZWxhdGVkIHNpZ25hbGlu
ZyBub3QgYWxsIGRvcyBhdHRhY2tzIGFyZSBpbiBmYWN0DQo+ID4+IGRpc3RyaWJ1dGVkLCB3aGVu
IGF0dGFjayB0cmFmZmljIGlzIHVuc3BvZmZlZCBhcyBpdCBpcyBpbiBtb3N0IHVwcGVyDQo+ID4+
IGxheWVyIHRhcmdldGluZyBhdHRhY2tzIGl0IG11c3QgbmVjZXNzYXJpbHkgZm9sbG93IGEgY29u
c2lzdGVudCBwYXRoDQo+ID4+IHBlciBhdHRhY2tlciwgbW9yZW92ZXIsIHlvdXIgdGVsZW1ldHJ5
IG1heSB3ZWxsIHRlbGwgeW91IHdoaWNoDQo+ID4+IGluZ3Jlc3MgaW50ZXJmYWNlIGFuZCB0aGVy
ZWZvcmUgcHJvdmlkZXIgbmVlZHMgdG8gcmVjZWl2ZSB3aGljaA0KPiA+PiBzaWduYWxpbmcgc2Vu
ZGluZyB0aGVtIHRvIHVuLWltcGFjdGVkIHByb3ZpZGVycyB1bm5lY2Vzc2FyeSBhbmQgbWF5DQo+
ID4+IHJlc3VsdCBpbiB1bmludGVudGlvbmFsIGluZm9ybWF0aW9uIGxlYWthZ2UuDQo+ID4gW01l
ZF0gVGhlIGNsaWVudHMgZG8gbm90IGtub3cgdGhlIGdhdGV3YXkocykgZnJvbSB3aGljaCB0aGUg
YXR0YWNrDQo+IHRyYWZmaWMgaXMgcmVjZWl2ZWQuIFRoaXMgaXMgd2h5IHRoZXkgaGF2ZSB0byBz
b2xpY2l0IGFsbCB0aGUgZ2F0ZXdheXMuDQo+IEkgZmluZCB0aGF0IGR1YmlvdXMgaWYgeW91J3Jl
IHJlY2VpdmluZyBwYWNrZXQgcmVsYXRlZCB0ZWxlbWV0ZXJ5IGluIG9yZGVyDQo+IHRvIGlkZW50
aWZ5IGRkb3MgaW4gdGhlIGZpcnN0IHBsYWNlIGZpbmRpbmcgd2hlcmUgaXQgaW5ncmVzc2VkIHlv
dXINCj4gbmV0d29yayBpcyBmYWlybHkgY3JpdGljYWwgKHdlIGRvIHRoaXMgd2l0aCBJUEZJWCwg
aGF2ZSBiZWVuIGRvaW5nIGl0IGZvcg0KPiBtb3JlIHRoYW4gYSBkZWNhZGUpIHNvdXJjZSBiYXNl
ZCBydGJoL2JncCBmbG93IHNwZWMgaW1wbGVtZW50YXRpb24gd2hpY2gNCj4gaXMgdGhlIHByZWN1
cnNvciB0byB0aGlzIHdvcmsgbW9yZSBvciBsZXNzIGFzc3VtZSB5b3UgY2FuIGlkZW50aWZ5IHRo
ZQ0KPiBwcm92aWRlciB0byBzaWduYWwuDQoNCltNZWRdIFllcyBidXQgbm90IGFsbCBjbGllbnQg
ZG9tYWlucyBoYXZlIHRoZXNlIGNhcGFiaWxpdGllcy4gVGhlIERPVFMgY2xpZW50IGNhbiBiZSBl
bWJlZGRlZCBpbiBhIHJvdXRlciwgYSBob3N0LCBldGMuIA0KDQogQXNzdW1pbmcgdGhhdCB5b3Ug
Y2Fubm90LCB0aGUgcXVlc3Rpb24gb2YgaW5mb3JtYXRpb24NCj4gbGVha2FnZSBwZXJzaXN0cw0K
DQpbTWVkXSBUaGUgbGVha2FnZSBkb2VzIG5vdCBoYXBwZW4gd2hlbiBhbiBpbnRlcm5hbCBjbGll
bnQgc2lnbmFscyBhbiBhdHRhY2sgdG8gYW4gaW50ZXJuYWwgZ2F0ZXdheSAod2hpY2ggdGhlIHRl
eHQgeW91IHF1b3RlZCBpcyBhYm91dCkuIFVwZGF0ZWQgdGhlIGRyYWZ0IHRvIG1ha2UgaXQgY2xl
YXIgdGhlIGdhdGV3YXlzIGFyZSAiY2xpZW50LWRvbWFpbiBET1RTIGdhdGV3YXlzIi4gDQoNClRo
ZSBsZWFrYWdlIGNvbmNlcm4gaXMgbW9yZSBiZXR3ZWVuIHRoZSBnYXRld2F5IGFuZCBhbiBleHRl
cm5hbCBzZXJ2ZXIuIEkgdGhpbmsgdGhpcyBpc3N1ZSBpcyBjb3ZlcmVkIGJ5IHRoaXMgdGV4dDoN
Cg0KICAgRE9UUyBjbGllbnRzIHNob3VsZCBjb250cm9sIHRoZSBpbmZvcm1hdGlvbiB0aGF0IHRo
ZXkgc2hhcmUgd2l0aCBwZWVyDQogICBET1RTIHNlcnZlcnMuICBJbiBwYXJ0aWN1bGFyLCBpZiBh
IERPVFMgY2xpZW50IG1haW50YWlucyBET1RTDQogICBhc3NvY2lhdGlvbnMgd2l0aCBzcGVjaWZp
YyBET1RTIHNlcnZlcnMgcGVyIGludGVyY29ubmVjdGlvbiBsaW5rLCB0aGUNCiAgIERPVFMgY2xp
ZW50IFNIT1VMRCBOT1QgbGVhayBpbmZvcm1hdGlvbiBzcGVjaWZpYyB0byBhIGdpdmVuIGxpbmsg
dG8NCiAgIERPVFMgc2VydmVycyBvbiBkaWZmZXJlbnQgaW50ZXJjb25uZWN0aW9uIGxpbmtzIHRo
YXQgYXJlIG5vdA0KICAgYXV0aG9yaXplZCB0byBtaXRpZ2F0ZSBhdHRhY2tzIGZvciB0aGF0IGdp
dmVuIGxpbmsuICBXaGV0aGVyIHRoaXMNCiAgIGNvbnN0cmFpbnQgaXMgcmVsYXhlZCBpcyBkZXBs
b3ltZW50LXNwZWNpZmljIGFuZCBtdXN0IGJlIHN1YmplY3QgdG8NCiAgIGV4cGxpY2l0IGNvbnNl
bnQgZnJvbSB0aGUgRE9UUyBjbGllbnQgZG9tYWluIGFkbWluaXN0cmF0b3IuICBIb3cgdG8NCiAg
IHNlZWsgZm9yIHN1Y2ggY29uc2VudCBpcyBpbXBsZW1lbnRhdGlvbi0gYW5kIGRlcGxveW1lbnQt
c3BlY2lmaWMuDQoNClRoaXMgdGV4dCBhcHBsaWVzIHRvIHRoZSAiY2xpZW50IiBzaWRlIG9mIGEg
ZG90cyBnYXRld2F5LiBBcyBhIHJlbWluZGVyLCBSRkM4NjEyIHNheXMgdGhlIGZvbGxvd2luZzoN
Cg0KICAgRE9UUyBnYXRld2F5OiAgQSBET1RTLWF3YXJlIHNvZnR3YXJlIG1vZHVsZSByZXN1bHRp
bmcgZnJvbSB0aGUNCiAgICAgIGxvZ2ljYWwgY29uY2F0ZW5hdGlvbiBvZiB0aGUgZnVuY3Rpb25h
bGl0eSBvZiBhIERPVFMgc2VydmVyIGFuZCBhDQogICAgICBET1RTIGNsaWVudCBpbnRvIGEgc2lu
Z2xlIERPVFMgYWdlbnQuICBUaGlzIGZ1bmN0aW9uYWxpdHkgaXMNCiAgICAgIGFuYWxvZ291cyB0
byBhIFNlc3Npb24gSW5pdGlhdGlvbiBQcm90b2NvbCAoU0lQKSBbUkZDMzI2MV0gQmFjay0NCiAg
ICAgIHRvLUJhY2sgVXNlciBBZ2VudCAoQjJCVUEpIFtSRkM3MDkyXS4gIEEgRE9UUyBnYXRld2F5
IGhhcyBhDQogICAgICBjbGllbnQtZmFjaW5nIHNpZGUsIHdoaWNoIGJlaGF2ZXMgYXMgYSBET1RT
IHNlcnZlciBmb3IgZG93bnN0cmVhbQ0KICAgICAgY2xpZW50cywgYW5kIGEgc2VydmVyLWZhY2lu
ZyBzaWRlLCB3aGljaCBwZXJmb3JtcyB0aGUgcm9sZSBvZiBhDQogICAgICBET1RTIGNsaWVudCBm
b3IgdXBzdHJlYW0gRE9UUyBzZXJ2ZXJzLiAgQ2xpZW50LWRvbWFpbiBET1RTDQogICAgICBnYXRl
d2F5cyBhcmUgRE9UUyBnYXRld2F5cyB0aGF0IGFyZSBpbiB0aGUgRE9UUyBjbGllbnQncyBkb21h
aW4sDQogICAgICB3aGlsZSBzZXJ2ZXItZG9tYWluIERPVFMgZ2F0ZXdheXMgZGVub3RlIERPVFMg
Z2F0ZXdheXMgdGhhdCBhcmUgaW4NCiAgICAgIHRoZSBET1RTIHNlcnZlcidzIGRvbWFpbi4gIEEg
RE9UUyBnYXRld2F5IG1heSB0ZXJtaW5hdGUgbXVsdGlwbGUNCiAgICAgIGRpc2NyZXRlIERPVFMg
Y2xpZW50IGNvbm5lY3Rpb25zIGFuZCBtYXkgYWdncmVnYXRlIHRoZXNlIGludG8gb25lDQogICAg
ICBvciBtb3JlIGNvbm5lY3Rpb25zLiAgRE9UUyBnYXRld2F5cyBhcmUgZGVzY3JpYmVkIGZ1cnRo
ZXIgaW4NCiAgICAgIFtET1RTLUFSQ0hdLg0KDQoNCiwgYW5kIHNob3VsZCBiZSBub3RlZCwgYXMg
eW91IGFyZSBzaWduYWxpbmcgdG8gYSBwcm92aWRlcg0KPiB0aGF0wqAgbWF5IG9yIG1heSBub3Qg
YmUgYSBjb25kdWl0IG9mIHRoZSBhdHRhY2sgdGhhdCB5b3UgYXJlIGJlaW5nDQo+IGF0dGFja2Vk
LCBhbmQgbGlrZXdpc2UgbWF5IHVuaW50ZW50aW9uYWxseSBtYWtlIHRoZSBhdHRhY2sgbW9yZSBl
ZmZlY3RpdmUNCj4gYnkgYXBwbHlpbmcgaXAgYmFzZWQgbWl0aWdpdGF0aW9ucyB0byBwYXRocyBv
dmVyIHdoaWNoIGxlZ2l0aW1hdGUgcmF0aGVyDQo+IHRoYW4gYXR0YWNrIHRyYWZmaWMgaXMgdHJh
dmVyc2luZy4NCg0KW01lZF0gTWFkZSB0aGlzIGNoYW5nZSBzbyB0aGF0IHByb3BhZ2F0aW5nIHRo
ZSBzaWduYWwgaXMgcG9saWN5LWJhc2VkOiAgIA0KDQpPTEQ6IA0KICAgRE9UUyBnYXRld2F5cyB3
aWxsIHRoZW4NCiAgIHJlbGF5IHRoZSByZXF1ZXN0IHRvIHRoZSBET1RTIHNlcnZlcnMuDQoNCk5F
VzoNCiAgIERPVFMgZ2F0ZXdheXMgd2lsbCB0aGVuDQogICByZWxheSB0aGUgcmVxdWVzdCB0byB0
aGUgRE9UUyBzZXJ2ZXJzIGFzIGEgZnVuY3Rpb24gb2YgbG9jYWwgcG9saWN5Lg0KDQo+ID4+PiAg
ICBUaGUgdXNlIG9mIGFueWNhc3QgYWRkcmVzc2VzIGlzIE5PVCBSRUNPTU1FTkRFRCB0byByZWFj
aCBET1RTDQo+ID4+IGdhdGV3YXlzLg0KPiA+Pg0KPiA+PiBwcm92aWRlciBzcGVjaWZpYyBhbnlj
YXN0cyBkbyBub3QgaW4gcHJpbmNpcGxlIHNlZW0gd29yc2UgdGhlbg0KPiA+PiBwcm92aWRlcg0K
PiA+IFtNZWRdIEl0IGlzIGluIHRoaXMgY2FzZSBhcyBpdCBwcmV2ZW50cyBjb250YWN0aW5nIGFs
bCBnYXRld2F5cyB3aGlsZQ0KPiB1bmljYXN0IGFsbG93cyBmb3IgaXQuIFRoaXMgaXMgY292ZXJl
ZCBieSB0aGlzIHRleHQ6DQo+ID4NCj4gPiAgICAgTm90ZSB0aGF0IGFueWNhc3QgYWRkcmVzc2Vz
DQo+ID4gICAgIGNhbm5vdCBiZSB1c2VkIHRvIGVzdGFibGlzaCBET1RTIHNlc3Npb25zIGJldHdl
ZW4gRE9UUyBjbGllbnRzIGFuZA0KPiA+ICAgICBET1RTIGdhdGV3YXlzIGJlY2F1c2Ugb25seSBv
bmUgRE9UUyBnYXRld2F5IHdpbGwgcmVjZWl2ZSB0aGUNCj4gPiAgICAgbWl0aWdhdGlvbiByZXF1
ZXN0Lg0KPiA+DQo+ID4gUGxlYXNlIG5vdGUgdGhhdCBhbGwgdGhlc2UgZ2F0ZXdheXMgYXJlIHBh
cnQgb2YgdGhlIHNhbWUgbmV0d29yay4NCj4gaW4gcHJhY3RpY2UgeW91IHByb2JhYmx5IGRvbid0
IG5lZWQgc2lnbmFsIGFsbCBvZiB0aGVtLCBwb3RlbnRpYWxseSBpbiBhDQo+IGxhcmdlIHByb3Zp
ZGVyIHRoZXJlIGFyZSBodW5kcmVkcywgaWYgeW91IGhhdmUgb25lIG9yIGZldyBpbmdyZXNzIHBv
aW50cw0KPiBmcm9tIGEgcHJvdmlkZXIgdG8geW91ciBuZXR3b3JrIHlvdSBkb24ndCBuZWVkIHRv
IHNpZ25hbHMgbWFueSB1cHN0ZWFtDQo+IGRvdHMgc2VydmVycyBpbiBvcmRlciBmb3IgdGhlIHBy
b3ZpZGVyIHRvIGluc3RhbGwgYSBtaXRpZ2lhdGlvbiwgb25lIGlzDQo+IHN1ZmZpY2llbnQuDQoN
CltNZWRdIEkgYWdyZWUgYnV0IHRoZSBjYXNlIHdlIGFyZSBkZXNjcmliaW5nIGhlcmUgYXNzdW1l
cyB0aGF0IGVhY2ggZ2F0ZXdheSBpcyBpbnRlcmZhY2VkIHdpdGggYSBkaXN0aW5jdCBwcm92aXNp
b25pbmcgZG9tYWluLiBGb3IgdGhpcyBjYXNlLCBjb250YWN0aW5nIG9ubHkgb25lIHNlcnZlciB3
b27igJl0IGJlIHN1ZmZpY2llbnQgaWYgdGhlIGF0dGFjayB0cmFmZmljIGlzIHJlY2VpdmVkIHZp
YSBhbGwgbGlua3MuICANCg0KPiA+DQo+ID4+IHNwZWNpZmljIHVuaWNhc3RzLCB0aGV5IGFsbG93
IGEgcHJvdmlkZXIgcmVkdWNlIHRoZSBhbW1vdW50IG9mDQo+ID4+IGNvb3JkaW5hdGlvbiByZXF1
aXJlZCB3aXRoaW4gdGhlaXIgb3duIGluZnJhc3RydWN0dXJlLg0KPiA+IFtNZWRdIEFncmVlLiBB
ZGRlZCBhIHBvaW50ZXIgdG8gU2VjdGlvbiAzLjIuNCBvZiBSRkM4ODExIGZvciB0aGlzIHBhcnQu
DQo+ID4NCj4gPiAgIGFzc2lnbmluZyBhIHdlbGwNCj4gPj4ga25vdyBhbnljYXN0IGZvciB0aGlz
IHB1cnBvc2UgYW1vbmcgYWxsIHByb3ZpZGVycyBvbiB0aGUgb3RoZXIgaGFuZA0KPiA+PiBzb3Vu
ZHMgbGlrZSBhIHRlcnJpYmxlIGlkZWEsIGZvciB0aGUgcmVhc29ucyB0aGF0IHdlbGwga25vd24t
YW55Y2FzdHMNCj4gPj4gYXJlIGdlbmVyYWxseSBiYWQuDQo+ID4+DQo+ID4gDQoKX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwoK
Q2UgbWVzc2FnZSBldCBzZXMgcGllY2VzIGpvaW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMgaW5m
b3JtYXRpb25zIGNvbmZpZGVudGllbGxlcyBvdSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBk
b25jCnBhcyBldHJlIGRpZmZ1c2VzLCBleHBsb2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0
aW9uLiBTaSB2b3VzIGF2ZXogcmVjdSBjZSBtZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6IGxl
IHNpZ25hbGVyCmEgbCdleHBlZGl0ZXVyIGV0IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGll
Y2VzIGpvaW50ZXMuIExlcyBtZXNzYWdlcyBlbGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxl
cyBkJ2FsdGVyYXRpb24sCk9yYW5nZSBkZWNsaW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNl
IG1lc3NhZ2UgYSBldGUgYWx0ZXJlLCBkZWZvcm1lIG91IGZhbHNpZmllLiBNZXJjaS4KClRoaXMg
bWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciBw
cml2aWxlZ2VkIGluZm9ybWF0aW9uIHRoYXQgbWF5IGJlIHByb3RlY3RlZCBieSBsYXc7CnRoZXkg
c2hvdWxkIG5vdCBiZSBkaXN0cmlidXRlZCwgdXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jp
c2F0aW9uLgpJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ug
bm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2ht
ZW50cy4KQXMgZW1haWxzIG1heSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3Ig
bWVzc2FnZXMgdGhhdCBoYXZlIGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLgpU
aGFuayB5b3UuCgo=


From nobody Tue Jan  4 02:20:33 2022
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BEE93A1A68; Tue,  4 Jan 2022 02:20:31 -0800 (PST)
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: dots@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.41.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dots@ietf.org
Message-ID: <164129163114.16875.18140424627149627746@ietfa.amsl.com>
Date: Tue, 04 Jan 2022 02:20:31 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/X16p-oWRAJuWK-jzQ6xn4eh6hSU>
Subject: [Dots] I-D Action: draft-ietf-dots-telemetry-19.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2022 10:20:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the DDoS Open Threat Signaling WG of the IETF.

        Title           : Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
        Authors         : Mohamed Boucadair
                          Tirumaleswar Reddy
                          Ehud Doron
                          Meiling Chen
                          Jon Shallow
	Filename        : draft-ietf-dots-telemetry-19.txt
	Pages           : 116
	Date            : 2022-01-04

Abstract:
   This document aims to enrich the DOTS signal channel protocol with
   various telemetry attributes, allowing for optimal Distributed
   Denial-of-Service (DDoS) attack mitigation.  It specifies the normal
   traffic baseline and attack traffic telemetry attributes a DOTS
   client can convey to its DOTS server in the mitigation request, the
   mitigation status telemetry attributes a DOTS server can communicate
   to a DOTS client, and the mitigation efficacy telemetry attributes a
   DOTS client can communicate to a DOTS server.  The telemetry
   attributes can assist the mitigator to choose the DDoS mitigation
   techniques and perform optimal DDoS attack mitigation.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dots-telemetry-19

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


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts



From nobody Tue Jan  4 02:23:24 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BDAC3A1A6A for <dots@ietfa.amsl.com>; Tue,  4 Jan 2022 02:23:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 SzsAa0HnTfNL for <dots@ietfa.amsl.com>; Tue,  4 Jan 2022 02:23:17 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (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 9F6673A1A69 for <dots@ietf.org>; Tue,  4 Jan 2022 02:23:17 -0800 (PST)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar26.francetelecom.fr (ESMTP service) with ESMTPS id 4JSpbl689BzFqTt;  Tue,  4 Jan 2022 11:23:15 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1641291795; bh=Z4r/0bx2HC/A47iXC7hXFY+Pq1afTsA6WnyOehJLT/8=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=ur+5nqkyFT6oXGBbCIelD3urWCA5WehyCilnyqbp0Gu7Dpei4KwKtUDnSOkGIC7OT jberlw408vimJDsUVlG1xKU7hDk1vrZbAZsTTGA98jRy1HvbZ0wa0+0+5pSWJHFP1h mtmydru2oOcoCRqXZ1S2nIpHMEPo9SfYlT7YCM3DQnOoXv82bWZwUnKoYg1kdbgnaN s7iwFEWzVZPATP8esQYeEQ6eVb0tQ0TnN0e6aB14GnJLoqHlnk9ghvkEdUICorHV26 OTc4gQLkOuwMb8NX0E0ozKSFrVEwBaXlRs7FrhkAee0HAEC9ePy8p+WQ9JoGzczevD bt5rvocLrM3Pg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar00.francetelecom.fr (ESMTP service) with ESMTPS id 4JSpbl5KVHzCqkW;  Tue,  4 Jan 2022 11:23:15 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Benjamin Kaduk <kaduk@mit.edu>
CC: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] I-D Action: draft-ietf-dots-telemetry-18.txt
Thread-Index: AQHX/ALp1EX80f/8KkG6r6xHtj4DE6xRhO/wgAEsrnA=
Content-Class: 
Date: Tue, 4 Jan 2022 10:23:14 +0000
Message-ID: <28056_1641291795_61D42013_28056_132_1_787AE7BB302AE849A7480A190F8B93303546C7E3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <163939252488.21261.15352577366570117756@ietfa.amsl.com> <23629_1639392661_61B72595_23629_108_1_787AE7BB302AE849A7480A190F8B9330354635AD@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <20211228155203.GV11486@mit.edu> <9216_1641228148_61D32774_9216_234_7_787AE7BB302AE849A7480A190F8B93303546C22B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <9216_1641228148_61D32774_9216_234_7_787AE7BB302AE849A7480A190F8B93303546C22B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-04T10:21:33Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=cb8c197a-399a-4f38-b81e-014e7e9ce853; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/muF56fsac3W9d7XFfRDODgIof-0>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-telemetry-18.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2022 10:23:22 -0000

Hi Ben,

An updated version that I hope addresses your pending comments is online:

URL:            https://www.ietf.org/archive/id/draft-ietf-dots-telemetry-1=
9.txt=20
Status:         https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/=
=20
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-dots-telem=
etry=20
Diff:           https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dots-telemet=
ry-19

Thank you.

Cheers,
Med

> -----Message d'origine-----
> De=A0: Dots <dots-bounces@ietf.org> De la part de
> mohamed.boucadair@orange.com
> Envoy=E9=A0: lundi 3 janvier 2022 17:42
> =C0=A0: Benjamin Kaduk <kaduk@mit.edu>
> Cc=A0: dots@ietf.org
> Objet=A0: Re: [Dots] I-D Action: draft-ietf-dots-telemetry-18.txt
>=20
> Re-,
>=20
> Please see inline.
>=20
> Cheers,
> Med
>=20
> > -----Message d'origine-----
> > De=A0: Dots <dots-bounces@ietf.org> De la part de Benjamin Kaduk Envoy=
=E9
> > : mardi 28 d=E9cembre 2021 16:52 =C0=A0: BOUCADAIR Mohamed INNOV/NET
> > <mohamed.boucadair@orange.com> Cc=A0: dots@ietf.org Objet=A0: Re: [Dots]
> > I-D Action: draft-ietf-dots-telemetry-18.txt
> >
> > On Mon, Dec 13, 2021 at 10:51:00AM +0000, mohamed.boucadair@orange.com
> > wrote:
> > > Hi Ben, all,
> > >
> > > This version integrates the AD review.
> > >
> > > Please let us know if there are issues we didn't address. Thank you.
> >
> > Thanks, and sorry for not tending to my email more quickly.
> >
> > You probably already saw the handful of replies I sent to the email
> > thread (and https://github.com/boucadair/draft-dots-telemetry/pull/10).
> >
> > I do not think I saw a reply to this remark on Section 8.1:
> >
> > =3D=3D=3D
> >    In order to signal telemetry data in a mitigation efficacy update, it
> >    is RECOMMENDED that the DOTS client has already established a DOTS
> >    telemetry setup session with the server in 'idle' time.
> >
>=20
> [Med] This recommendation is to make sure that the server understands the
> telemetry attributes before using them. Otherwise, there is a risk that a
> message with the telemetry attributes will be rejected by a legacy server.
>=20
> > If I understand correctly, it seems that at least part of the need for
> > having a preestablished telemetry session is that the mitigation
> > efficacy update is identified only by the 'mid', and so we cannot
> specify a 'tmid'
> > as part of such an efficacy update.  Thus, in order for the server to
> > associate the telemetry data in the efficacy update with an ongoing
> > telemetry status session, the 'tsid' must be associated with the 'mid'
> > that is the subject of the efficacy update.
> > If that is correct, then I think we should have some text here about
> > how the efficacy update does not/cannot include the 'tmid', and so is
> > associated with the 'mid' of the update.
> > =3D=3D=3D
> >
> > Of the things in the email chain, I am most interested in getting
> > clarity
> > around:
> >
> > - what to put in the "attack-id" field when we are sending an
> >   "attack-description" string for a not-previously-characterized
> > attack (or
> >   make that field not mandatory at the YANG level).
>=20
> [Med] The attack-id is assigned by vendors. This applies for both shared
> and new attacks.
>=20
> >
> > - when a server updates its published attack mappings, if there's a
> >   requirement/expectation that already assigned attack-id values
> > retain the
> >   same meaning.
>=20
> [Med] This was clarified in another message.
>=20
> >
> > Thanks again,
> >
> > Ben
> >
> > _______________________________________________
> > Dots mailing list
> > Dots@ietf.org
> > https://www.ietf.org/mailman/listinfo/dots
>=20
> __________________________________________________________________________
> _______________________________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses,
> exploites ou copies sans autorisation. Si vous avez recu ce message par
> erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les
> pieces jointes. Les messages electroniques etant susceptibles
> d'alteration, Orange decline toute responsabilite si ce message a ete
> altere, deforme ou falsifie. Merci.
>=20
> This message and its attachments may contain confidential or privileged
> information that may be protected by law; they should not be distributed,
> used or copied without authorisation.
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
>=20
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Wed Jan  5 02:14:09 2022
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AFA13A0163; Wed,  5 Jan 2022 02:14:07 -0800 (PST)
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: dots@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.41.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dots@ietf.org
Message-ID: <164137764747.8868.9592514632814928071@ietfa.amsl.com>
Date: Wed, 05 Jan 2022 02:14:07 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/8-dpH0FSCeQckPRGnYvNwElNFr4>
Subject: [Dots] I-D Action: draft-ietf-dots-robust-blocks-01.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2022 10:14:08 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the DDoS Open Threat Signaling WG of the IETF.

        Title           : Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission
        Authors         : Mohamed Boucadair
                          Jon Shallow
	Filename        : draft-ietf-dots-robust-blocks-01.txt
	Pages           : 21
	Date            : 2022-01-05

Abstract:
   This document specifies new DOTS signal channel configuration
   parameters that are negotiated between DOTS peers to enable the use
   of Q-Block1 and Q-Block2 CoAP Options.  These options enable robust
   and faster transmission rates for large amounts of data with less
   packet interchanges as well as supporting faster recovery should any
   of the blocks get lost in transmission.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dots-robust-blocks/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dots-robust-blocks-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-robust-blocks-01


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts



From nobody Wed Jan  5 02:21:33 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30C173A0489; Wed,  5 Jan 2022 02:21:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 x57jPuJe4SLO; Wed,  5 Jan 2022 02:21:26 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.36]) (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 63FB33A0483; Wed,  5 Jan 2022 02:21:26 -0800 (PST)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr25.francetelecom.fr (ESMTP service) with ESMTPS id 4JTQW83rsNzCrKD;  Wed,  5 Jan 2022 11:21:24 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1641378084; bh=1cN4KAPIaElIpFumANPZDzKjLtcFKH+Cy5fkyG0Zg2A=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=YK1QoJ1F5xnloDg5/2nl6iEX1e0g+Cv4hZ5l4JnxG0Noo6yVOOplSDTGKVP0oJGNH 5eookZUiEIC1nm2gVfB/JmdM75XsxREDLHNaxZ/VIDfIiEBSrsM5atiGmnyAJt2eS8 R7l7y5/HN+ErfGlfxLACjfQ1wVQN8LWtco3Qztm+7J4DeFsjCtv+DCEXONpZJErALb 25ZK6UxuWnI16Da9aY/hZEImpq3yFl/nZayA1tGkK21EhkVtnOYFqWPFHl270See5L 9CHxmTS6TTB+mc0Zu19tDKn5XuBz1TnvOtLu89TdigGN3FCWhLp84f+9B13JLZfBj0 SNHvf+1G+T1TA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr00.francetelecom.fr (ESMTP service) with ESMTPS id 4JTQW830yHzDq7d;  Wed,  5 Jan 2022 11:21:24 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: "dots@ietf.org" <dots@ietf.org>, "dots-chairs@ietf.org" <dots-chairs@ietf.org>
Thread-Topic: [Dots] I-D Action: draft-ietf-dots-robust-blocks-01.txt
Thread-Index: AQHYAhz/Up8eiovovECoi7CQB7hKYqxUNhAA
Content-Class: 
Date: Wed, 5 Jan 2022 10:21:23 +0000
Message-ID: <11126_1641378084_61D57124_11126_289_1_787AE7BB302AE849A7480A190F8B93303546D15D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164137764747.8868.9592514632814928071@ietfa.amsl.com>
In-Reply-To: <164137764747.8868.9592514632814928071@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-05T10:15:32Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=0ed1d913-948a-43b7-875d-a07cd767ccc9; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/d5_nHF668xZ4YLKvy9B6KNFnAQE>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-robust-blocks-01.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2022 10:21:31 -0000

Hi all,

We updated the draft with the following changes:=20
* Add non-receive-timeout to the parameters that can be configured.=20
* Add a reminder that the attributes are mapped to CBOR when signaled in a =
DOTS message
* Add new text to indicate the behavior to follow to make use of the new at=
tributes
* Add reference statements to the YANG module
* Rearrange the text for better readability
* Updated the requested IANA range to comply with Section 3.1 of RFC9132
* Fix nits

We believe this version is ready for the WGLC.=20

Cheers,
Jon & Med

> -----Message d'origine-----
> De=A0: Dots <dots-bounces@ietf.org> De la part de internet-drafts@ietf.org
> Envoy=E9=A0: mercredi 5 janvier 2022 11:14
> =C0=A0: i-d-announce@ietf.org
> Cc=A0: dots@ietf.org
> Objet=A0: [Dots] I-D Action: draft-ietf-dots-robust-blocks-01.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the DDoS Open Threat Signaling WG of the
> IETF.
>=20
>         Title           : Distributed Denial-of-Service Open Threat
> Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block
> Transmission
>         Authors         : Mohamed Boucadair
>                           Jon Shallow
> 	Filename        : draft-ietf-dots-robust-blocks-01.txt
> 	Pages           : 21
> 	Date            : 2022-01-05
>=20
> Abstract:
>    This document specifies new DOTS signal channel configuration
>    parameters that are negotiated between DOTS peers to enable the use
>    of Q-Block1 and Q-Block2 CoAP Options.  These options enable robust
>    and faster transmission rates for large amounts of data with less
>    packet interchanges as well as supporting faster recovery should any
>    of the blocks get lost in transmission.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dots-robust-blocks/
>=20
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-robust-blocks-01
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dots-robust-blocks-01
>=20
>=20
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-
> drafts
>=20
>=20
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Wed Jan  5 17:49:30 2022
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CDE63A1367; Wed,  5 Jan 2022 17:49:28 -0800 (PST)
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: dots@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.41.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dots@ietf.org
Message-ID: <164143376852.21052.12782320185142562934@ietfa.amsl.com>
Date: Wed, 05 Jan 2022 17:49:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/yoacHqF3qKJ0yA_ZqfmqXrrUO3I>
Subject: [Dots] I-D Action: draft-ietf-dots-telemetry-use-cases-04.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2022 01:49:29 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the DDoS Open Threat Signaling WG of the IETF.

        Title           : Use Cases for DDoS Open Threat Signaling (DOTS) Telemetry
        Authors         : Yuhei Hayashi
                          Meiling Chen
                          Li Su
	Filename        : draft-ietf-dots-telemetry-use-cases-04.txt
	Pages           : 25
	Date            : 2022-01-05

Abstract:
   Denial-of-service Open Threat Signaling (DOTS) Telemetry enriches the
   base DOTS protocols to assist the mitigator in using efficient DDoS-
   attack-mitigation techniques in a network.  This document presents
   sample use cases for DOTS Telemetry: what components are deployed in
   the network, how they cooperate, and what information is exchanged to
   effectively use these techniques.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry-use-cases/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dots-telemetry-use-cases-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-telemetry-use-cases-04


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts



From nobody Fri Jan  7 14:41:14 2022
Return-Path: <kaduk@mit.edu>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27DD63A0CEB for <dots@ietfa.amsl.com>; Fri,  7 Jan 2022 14:41:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.496
X-Spam-Level: 
X-Spam-Status: No, score=-1.496 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 QohE0z1dSLmm for <dots@ietfa.amsl.com>; Fri,  7 Jan 2022 14:41:07 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 AC9D33A0CEA for <dots@ietf.org>; Fri,  7 Jan 2022 14:41:07 -0800 (PST)
Received: from mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 207Meve9006881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 7 Jan 2022 17:41:03 -0500
Date: Fri, 7 Jan 2022 14:40:57 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: mohamed.boucadair@orange.com
Cc: "dots@ietf.org" <dots@ietf.org>
Message-ID: <20220107224057.GR11486@mit.edu>
References: <163939252488.21261.15352577366570117756@ietfa.amsl.com> <23629_1639392661_61B72595_23629_108_1_787AE7BB302AE849A7480A190F8B9330354635AD@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <20211228155203.GV11486@mit.edu> <9216_1641228148_61D32774_9216_234_7_787AE7BB302AE849A7480A190F8B93303546C22B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <28056_1641291795_61D42013_28056_132_1_787AE7BB302AE849A7480A190F8B93303546C7E3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <28056_1641291795_61D42013_28056_132_1_787AE7BB302AE849A7480A190F8B93303546C7E3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/zvpV85Xv3ZVT6kxeMnOjeuVsjcU>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-telemetry-18.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2022 22:41:12 -0000

On Tue, Jan 04, 2022 at 10:23:14AM +0000, mohamed.boucadair@orange.com wrote:
> Hi Ben,
> 
> An updated version that I hope addresses your pending comments is online:
> 
> URL:            https://www.ietf.org/archive/id/draft-ietf-dots-telemetry-19.txt 
> Status:         https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/ 
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-dots-telemetry 
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-telemetry-19

Thanks, Med.

I think I figured out what was bothering me about 'attack-id', and your
latest messages helped me realize why it is not an issue; thanks for your
patience and multiple explanations.  In short, I was worried that at
runtime a DOTS server would see a "new attack" and try to generate a wholly
new description for it, which would require a new attack-id as well.  But
it's far more likely that the server is going to have a fixed set of
attacks it knows about, and just pick the entry from that set that most
closely matches the observed attack, even if the match is not very good
(i.e., a generic "other attack" case).  The new description would come from
the vendor after review and action by humans looking over the data, and
would not be synthesized at runtime by an automated procedure in the
server, so it really is the case that all attack-ids are assigned
(centrally) by the vendor.

I will go ahead and request the IETF Last Call.

-Ben

P.S. There is one nit in the new 'attack-id' description -- it should be
"independent of whether", not "independently whether".


From nobody Sun Jan  9 22:36:43 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 564DA3A0654 for <dots@ietfa.amsl.com>; Sun,  9 Jan 2022 22:36:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 uHp-b1LJmUbr for <dots@ietfa.amsl.com>; Sun,  9 Jan 2022 22:36:37 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (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 9E4D03A0653 for <dots@ietf.org>; Sun,  9 Jan 2022 22:36:37 -0800 (PST)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr26.francetelecom.fr (ESMTP service) with ESMTPS id 4JXPHR5KSKzyjT; Mon, 10 Jan 2022 07:36:35 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1641796595; bh=Hbbu6tW0c1eVLsg+3ZGvhG4JBX87+zx6YwkglR2M+xY=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=ntY7/VYJOFUk6hI3IwwUlLIyYg00TqYMwJDvg2OB4DlTAMS2y+H8TPJ0Fj2lBlYH0 izObwVlkdiLkC2AZvfXgBdeytVcHfIqUuwsDmGTxFdjsxVTQg2u9aOMjui2PBfv41E TbCGDPKRsi3RsKyVuxARCm+dEfE5ZyIfNhsAAdZleQ3eQKVwbxpo9t1VHRJ6TV8k0H rswHperB3XKeYI78txAFAPYovQQ1vjdAlZcs1tZL/MSgM8wPvw3AsVc2QbuooKyqYV wlq36Gk7p76W6DoPMOtbRfFtJD4itc7vQEMXWafJZ9SXjdKHE+I50AJXSaaUUkfC6N dsa+/Z/Helikw==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr06.francetelecom.fr (ESMTP service) with ESMTPS id 4JXPHR4Wb9zDq7L;  Mon, 10 Jan 2022 07:36:35 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Benjamin Kaduk <kaduk@mit.edu>
CC: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] I-D Action: draft-ietf-dots-telemetry-18.txt
Thread-Index: AQHYBBeraCGwcIzHt0WWez55+Gy4zaxb0AFw
Content-Class: 
Date: Mon, 10 Jan 2022 06:36:34 +0000
Message-ID: <16472_1641796595_61DBD3F3_16472_269_1_787AE7BB302AE849A7480A190F8B9330354702D9@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <163939252488.21261.15352577366570117756@ietfa.amsl.com> <23629_1639392661_61B72595_23629_108_1_787AE7BB302AE849A7480A190F8B9330354635AD@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <20211228155203.GV11486@mit.edu> <9216_1641228148_61D32774_9216_234_7_787AE7BB302AE849A7480A190F8B93303546C22B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <28056_1641291795_61D42013_28056_132_1_787AE7BB302AE849A7480A190F8B93303546C7E3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <20220107224057.GR11486@mit.edu>
In-Reply-To: <20220107224057.GR11486@mit.edu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-10T06:34:28Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=809bbd36-266e-4f08-bb7f-4d5b37d40d0e; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/_v4WeXjAMuUZ4IC7U0cLmWAhQwQ>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-telemetry-18.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2022 06:36:43 -0000

Hi Ben,=20

Thanks.=20=20

Fixed the nit (and some few others) in the editor's copy: https://tinyurl.c=
om/dots-telemetry-latest).=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: Benjamin Kaduk <kaduk@mit.edu>
> Envoy=E9=A0: vendredi 7 janvier 2022 23:41
> =C0=A0: BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
> Cc=A0: dots@ietf.org
> Objet=A0: Re: [Dots] I-D Action: draft-ietf-dots-telemetry-18.txt
>=20
> On Tue, Jan 04, 2022 at 10:23:14AM +0000, mohamed.boucadair@orange.com
> wrote:
> > Hi Ben,
> >
> > An updated version that I hope addresses your pending comments is
> online:
> >
> > URL:            https://www.ietf.org/archive/id/draft-ietf-dots-
> telemetry-19.txt
> > Status:         https://datatracker.ietf.org/doc/draft-ietf-dots-
> telemetry/
> > Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-dots-
> telemetry
> > Diff:           https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dots-
> telemetry-19
>=20
> Thanks, Med.
>=20
> I think I figured out what was bothering me about 'attack-id', and your
> latest messages helped me realize why it is not an issue; thanks for your
> patience and multiple explanations.  In short, I was worried that at
> runtime a DOTS server would see a "new attack" and try to generate a
> wholly new description for it, which would require a new attack-id as
> well.  But it's far more likely that the server is going to have a fixed
> set of attacks it knows about, and just pick the entry from that set that
> most closely matches the observed attack, even if the match is not very
> good (i.e., a generic "other attack" case).  The new description would
> come from the vendor after review and action by humans looking over the
> data, and would not be synthesized at runtime by an automated procedure in
> the server, so it really is the case that all attack-ids are assigned
> (centrally) by the vendor.
>=20
> I will go ahead and request the IETF Last Call.
>=20
> -Ben
>=20
> P.S. There is one nit in the new 'attack-id' description -- it should be
> "independent of whether", not "independently whether".

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Mon Jan 10 06:32:23 2022
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BF4133A117F; Mon, 10 Jan 2022 06:32:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.42.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: dots-chairs@ietf.org, dots@ietf.org, draft-ietf-dots-telemetry@ietf.org, kaduk@mit.edu, valery@smyslov.net
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <164182513674.28016.284174261896096787@ietfa.amsl.com>
Date: Mon, 10 Jan 2022 06:32:16 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/Equz2Xtez_0CGup5VApzwhtzzK0>
Subject: [Dots] Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2022 14:32:17 -0000

The IESG has received a request from the DDoS Open Threat Signaling WG (dots)
to consider the following document: - 'Distributed Denial-of-Service Open
Threat Signaling (DOTS) Telemetry'
  <draft-ietf-dots-telemetry-19.txt> as Proposed Standard

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

Abstract


   This document aims to enrich the DOTS signal channel protocol with
   various telemetry attributes, allowing for optimal Distributed
   Denial-of-Service (DDoS) attack mitigation.  It specifies the normal
   traffic baseline and attack traffic telemetry attributes a DOTS
   client can convey to its DOTS server in the mitigation request, the
   mitigation status telemetry attributes a DOTS server can communicate
   to a DOTS client, and the mitigation efficacy telemetry attributes a
   DOTS client can communicate to a DOTS server.  The telemetry
   attributes can assist the mitigator to choose the DDoS mitigation
   techniques and perform optimal DDoS attack mitigation.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/



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






From nobody Fri Jan 14 04:32:43 2022
Return-Path: <daedulus@btconnect.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34E5E3A2365; Fri, 14 Jan 2022 04:32:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.615
X-Spam-Level: 
X-Spam-Status: No, score=-2.615 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, 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=btconnect.onmicrosoft.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 FGljM7IBK_Bp; Fri, 14 Jan 2022 04:32:32 -0800 (PST)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40106.outbound.protection.outlook.com [40.107.4.106]) (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 607433A2366; Fri, 14 Jan 2022 04:32:30 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Tt0SR1c/GUXEAcGgxBLc6essuL1IQlS/BgxQYo71+WS+LXn9ADgW8HXngnVxg8soKygIQiZhpLK+ZWhmjaOtpp1rBpS/nCyaVj3eerAtTfjw/iG29SSGNP/VfoYH2AudXQTEsGviHolKtj0RKEC5YMeMcFBxUtlxOXnbzUZlXhT53mYS5liVY6JKsUaOKRPWf7ocsJILrqqtlL/AenxDebb7OJ1FX3TygYxOEC5A6evMS7B19IIS04WMqAt7pIRlwrYMPqE2eNMAvKmxV/17VlJWD60WOOOJbolTQV0Loee+TFmwY6MHFtQWCAPrF8Y5HiAAWLsVUQvzb7DYpt+Vrg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=jQ8nnNnLrkB6UGmEySLvCe7s3kSlrhcg6erdV9qtVXM=; b=i9oyHY7CGR4biz6XIv5FLAX0VxXoYK6yicftYidgm8bxVXh+jJ4ODt2ksinV6a0KCg1iUh3GlphhPuAU/v/FDGXnFMmJhaus6Kf3IiZ67VrmCqfXKoZec1L9bPDVO/U7tha/DgnLbYgWZFdKBCRyKqeb6BVnwLArrJVof/Q1y1fCcJofhHwJksFgR0mvnB45CjvEGpDpRpGMta0P4Dcqd10IuvPP1QquUZwlS9RWFFFz5fbEQAh49ZOf3slHxvkx18seSXAx61swgVdrJb5ZYg/OiIi7CGDfK9aYQCcKW24vULFneIner1PiJH8N/+LXgqAyKKvwQBmKR1BI40sLBQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jQ8nnNnLrkB6UGmEySLvCe7s3kSlrhcg6erdV9qtVXM=; b=vwXOperMwkgT+HCeuz5rA4PUDzLFIOEzh1Lwdqw95U6Fjpu/x/yP1xkBVZ7XiLHcCbyAP/tTuQR5L9zQHbEerNk37Ba8Hom7tHHFfP5y6H3QoppNRQIvzL2vSqLGXca5cov+1HdtM28dArHchTzGnjYDl+/qdzmx27oor7TECzA=
Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR0701MB2638.eurprd07.prod.outlook.com (2603:10a6:801:4::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4909.3; Fri, 14 Jan 2022 12:32:28 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::60fd:157e:c5e3:1a18]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::60fd:157e:c5e3:1a18%7]) with mapi id 15.20.4909.003; Fri, 14 Jan 2022 12:32:27 +0000
To: last-call@ietf.org
References: <164182513674.28016.284174261896096787@ietfa.amsl.com>
Cc: dots-chairs@ietf.org, valery@smyslov.net, dots@ietf.org, draft-ietf-dots-telemetry@ietf.org
From: tom petch <daedulus@btconnect.com>
Message-ID: <61E16D53.7050003@btconnect.com>
Date: Fri, 14 Jan 2022 12:32:19 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <164182513674.28016.284174261896096787@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: LO2P265CA0240.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:b::36) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: b2a1e533-f459-463c-7aa5-08d9d759ecac
X-MS-TrafficTypeDiagnostic: VI1PR0701MB2638:EE_
X-Microsoft-Antispam-PRVS: <VI1PR0701MB2638AF09E202261DFD8F95FFC6549@VI1PR0701MB2638.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: vLJApsH4zZmIxMjFm9yJE15TPgTw2qAELx7NdZkxC+z2s0ahvverTv3c69CxfRw0M+x07zBN18+2c/wZOG34tcx6V3Xj+Rgx+1fzYZ823oi9NgfM8Ws+BdINzAB0utj6AxwkfFi33AsQtDRIbUxqaxgcUJLuKFfYRdtFHCW9u6iplDyjSwwmcuI5p2W4O6yjqPwbHGGQozPdtLfIkJ19sAyBOuOP2gNlb7XNpVHr1QIwhb6XdNJmeoh07EHeacDbJ11NQ52CaT6IKtjEewhAeTdURONOcdGMMVIaL5s2u62emqBpHP9htdj1MprZTwBgrP4TZ+vzaOtulai95GTyF+sDF79KfyNiNpogR/MhLkJl3wz+wex3wqmBUDEBxjT2zWEvT7CH82qOgW3IcBiBIZDszcqkYz4xhLOzlETmHbzxb2nlukGOT6CoBYFNHqm2qcJ7eyzD12pvb/AJyJ//EYGzfV3laWfWpKgk9GKS57IJprPsSDN/TL4n4HzOiwmLlLQVKJDuMSmqy36AJ5djGgxZqQ8GcC5YWEA/iOOCDmu4qFhyk5PKQs8zEGhfw4MtOYCjlg47Q2+xMUzYA2ElB+LhwARNBAQKCgsBP5dl5o4N3BITvkwIlw4ixaVpZsb3HAETw/ebS/SJ6wntH+pqan96LahKL74CyGyOlqTKKfiMNevB7EuynNRwWddP6mthG5WUVRAof96pGSmjRrglclAdMcpffukE8jMCdZF30pVykV0CbBwe3as0O2fcnaE/TTSwmk3BlDHC3FeSqAoCnLKpuYp9y7anIUzyBTzNU9LE3V+1nSaiqAE3mtet18Rb
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(13230001)(4636009)(366004)(38350700002)(82960400001)(4326008)(38100700002)(66476007)(52116002)(6512007)(6916009)(8676002)(8936002)(66946007)(86362001)(316002)(5660300002)(66556008)(83380400001)(2616005)(36756003)(87266011)(186003)(53546011)(6506007)(6666004)(6486002)(26005)(966005)(2906002)(33656002)(508600001)(20210929001); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?Windows-1252?Q?K82/eIkmdmkFrc8Dac8gDiXhdrKUPPUM1Gq/zj08TJbmipp4p5/hsgmd?= =?Windows-1252?Q?rppfR6Do6TtWbFHt+eoTAlUqvvxrRgpksqabd5ifeG5eua58tN5T40zG?= =?Windows-1252?Q?ZbtlrbP5NqTDydowSPHdIVSog7jTLkI1zU4fZzWT9JmA02oDibtHq3G4?= =?Windows-1252?Q?+DsfZDTFlCW0Nm/fUhfnH9NBgh95uKt6v1j6OAyGzYdknQuIh2Kxa2eB?= =?Windows-1252?Q?mXjg9/ICH+5VjFK2WL82+MikRLNKL5kY/EdZmvunlpWme17HtVU3H8pq?= =?Windows-1252?Q?eyTSHpeTthB4m8HwqD/i/C5aUSs4O7icnPe7axZJbYRFrbRBOitrclb/?= =?Windows-1252?Q?OHqeruy9UsVMtUh5nHr+a1AZKhOPU/7u/sLti/zrY79eIl8Zw7nclIVy?= =?Windows-1252?Q?usnietd7Gu2AkQhZkYqPjuy+eEoNbSU9/W9uSRCbvKU7R2vM1ov7F9j1?= =?Windows-1252?Q?ytvDX7QogVka5HTCw6NOQvYVynZ88CkpI+8REcdcz3Slx69VcA9pprZl?= =?Windows-1252?Q?++rQ+hLus0ZbSIkCN34bG3FEHdhHmKhjOa6RKJ9sS7drehOyrWmURNOz?= =?Windows-1252?Q?BRP4NgtZG+xfCvBVlnyHXZMqilKhBPR1rpV387G2Tb+w5CyvvGg6N3h1?= =?Windows-1252?Q?peooPu6w5P9ExrLbFKy01e/JuzqtKRjzRkYyou58qMFxbcGJok77r1Rc?= =?Windows-1252?Q?307Eq5nzEbJAwpoBS7T6Kbu6gS9vHd+BlikvG4l9QHpLfrXuejb4kRLL?= =?Windows-1252?Q?691p8sVXYT3kfMitRZpSSvpYCoPw8ByW7sdWghBhpLuY5J3fWBqnaGAc?= =?Windows-1252?Q?CeLFessF7I7WtU3v1P3gt3AgbxPmQIKkhaDHyANQQSLKonMmCnhFgwJS?= =?Windows-1252?Q?jUj7Z++8Mw+G8hrINQ8J0xS0INzPHNDrBUQNeHXCEE0OZhEVLXHfRslv?= =?Windows-1252?Q?NBV8fg6neIU4JAcE8YNgCNs930DNWC0AKvqfwj7EmudZur35BiQGe4RN?= =?Windows-1252?Q?V/pt5TjjhAWaOgltIoG7jSEy2+EXq4xR+prBbUGiy+MVy6jb/QKy0Hot?= =?Windows-1252?Q?0mb19xFh/nEhRn3GsOiEsfHLWLstYMllOd3Sum4vqjfBRzrT3UMHvWe3?= =?Windows-1252?Q?4ts20rKCaf7sxz56XfCQQXOJo9F1vrA9sEPH3BsNpCCiGZCFEec9sUnQ?= =?Windows-1252?Q?3gtbkqcmN6FjSmMPEFkQwpr+FFbwyEZOdYtWDH5340ZSaA1pxsBGGNz2?= =?Windows-1252?Q?cp2X1GAO/YdfSr5uZPqIgQr2CYtGIR1CePW3UCi//ZKV1tExRrO5iKf2?= =?Windows-1252?Q?8Eoh1OlOj/iZ/lZvc3MFqJxgtw/2Iu44Upr0Ffm6Fikulj7Cc3DcRmDr?= =?Windows-1252?Q?Z4oE4etQaike94Md20tQPEqLGJZYOxah3ILB3YXGtnC5/eAW5kS0rZ/R?= =?Windows-1252?Q?CqEGfGnOKmx3pCsXswoju/ACqJQBFISQ4OWK2WhKx59gMHZSZZtFiv30?= =?Windows-1252?Q?GtC9NWJe0R8xZNc5stdo8GlOD4PuHR8NmzPD4eds1c5d3ypktfUEvv3e?= =?Windows-1252?Q?DTBN8WFt4aT31NCLPuDU5cqR6cDHKworkho9L8P8w3TfwePNOtuuyjtk?= =?Windows-1252?Q?zgUYDlHEvEU/RRSPtNnhh0Wx04EV1a4l0WoqOxIEddOYJRpS1XK0vesf?= =?Windows-1252?Q?56vmZuKT6jXa2BrHk0qeSUP5DQCtWzOVztzozLiIDBETG6NRAuXOAj5y?= =?Windows-1252?Q?mQgjYCBHp6bqQytJ9yk=3D?=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b2a1e533-f459-463c-7aa5-08d9d759ecac
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Jan 2022 12:32:27.6632 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 1Ns8SvTNWB5EvUXAU26xXbVVhLIxrRpqADcvlsJkw0oFl7jC1bfxFzU6gy361bVyIewUyauixwT8W8EzTJ5JEg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB2638
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/uvJnPvyhGdzq6W1zdHD3MVWMRgs>
Subject: Re: [Dots] Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2022 12:32:38 -0000

Some stray thoughts

I wonder if there is a recognised terminology for attacks, threats and 
such-like.  I have been looking at I2NSF I-D recently and they are, 
well, different.  I note too that secdir reviews thereof queried some of 
the I2NSF terminology but what is right and what is wrong?.  I am 
reminded of the efforts to produce a second version of the Security 
Glossary some time ago.

I find the use of -g and -ps alien.  I worked out what they mean but 
cannot help feeling that there is a clearer way to express this, such as 
pps, bps, Bps (YANG does not like capitalisation but does allow it where 
it is widely recognised, which, for me, Bps is).

URI for IANA are inconsistent, http: and https: - since IANA allows 
http: (hurrah) I am easy with either but do like consistency

"The DOTS telemetry module (Section 10.1) uses "enumerations" rather
    than "identities" to define units, samples, and intervals because
    otherwise the namespace identifier "ietf-dots-telemetry" must be
    included when a telemetry attribute is included "
Well yes but that is saying the ietf-dots-telemetry is a bad choice of 
prefix - the 'ietf' is redundant and the 'telemetry' is prolix

       TBA: Overlapping pipe scope (see Section 12).
could do with an explanatory note, perhaps one for the RFC Editor


    vendor-id:  Vendor ID is a security vendor's Enterprise Number as
       registered with IANA [Enterprise-Numbers].  It is a four-byte
       integer value.
No, it is an integer which in this model is uint32 which can be 
represented in a number of ways

The user has to understand that [Enterprise-Numbers] is the same as 
Private Enterprise Numbers", which may not be apparent; consistent 
terminology is good.

YANG TLD is out of date and URI lacks https:

Authors vary between the frontispiece, the YANG modules and Authors' 
Addresses

Two references in the YANG modules I do not see in the I-D References
       <https://www.iana.org/assignments/protocol-numbers/>.
       "Section 4.4.2 of RFC UUUU.";
The latter is not an RFC I am familiar with (but then that is true of 
most RFC:-(

     reference
       "IANA: Private Enterprise Numbers";
would be clearer with a URI, whereever it occurs which is in more than 
one place

Security COnsiderations uses part of the YANG Guidelines template but 
not all; TLS is notable for its absence.

Tom Petch





On 10/01/2022 14:32, The IESG wrote:
>
> The IESG has received a request from the DDoS Open Threat Signaling WG (dots)
> to consider the following document: - 'Distributed Denial-of-Service Open
> Threat Signaling (DOTS) Telemetry'
>    <draft-ietf-dots-telemetry-19.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call@ietf.org mailing lists by 2022-01-24. Exceptionally, comments may
> be sent to iesg@ietf.org instead. In either case, please retain the beginning
> of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document aims to enrich the DOTS signal channel protocol with
>     various telemetry attributes, allowing for optimal Distributed
>     Denial-of-Service (DDoS) attack mitigation.  It specifies the normal
>     traffic baseline and attack traffic telemetry attributes a DOTS
>     client can convey to its DOTS server in the mitigation request, the
>     mitigation status telemetry attributes a DOTS server can communicate
>     to a DOTS client, and the mitigation efficacy telemetry attributes a
>     DOTS client can communicate to a DOTS server.  The telemetry
>     attributes can assist the mitigator to choose the DDoS mitigation
>     techniques and perform optimal DDoS attack mitigation.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/
>
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> .
>


From nobody Sat Jan 15 10:49:38 2022
Return-Path: <noreply@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C66F63A0EDC; Sat, 15 Jan 2022 10:49:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: James Gruessing via Datatracker <noreply@ietf.org>
To: <art@ietf.org>
Cc: dots@ietf.org, draft-ietf-dots-telemetry.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164227257574.1686.16790605376691634274@ietfa.amsl.com>
Reply-To: James Gruessing <james.ietf@gmail.com>
Date: Sat, 15 Jan 2022 10:49:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/v8YVqlJWfyhHHBEDwTPs8vXRkxQ>
Subject: [Dots] Artart last call review of draft-ietf-dots-telemetry-19
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jan 2022 18:49:36 -0000

Reviewer: James Gruessing
Review result: Ready with Nits

This is my review of draft-ietf-dots-telemetry-19 as requested by ARTART chairs.

Overall this is a well written document that explains its purpose, rationale,
and technical details for someone like myself with no previous knowledge of DOTS
or its underlying dependent protocols. As such my focus in this review has been
looking at the readability of the document through the eyes of a future implementer.

Comments:

3.2 - At a few points in this section, the concept of "measurements should be
taken when traffic is 'normal'" is repeated a few times and done in a way not as
clear as it could be. The authors should consider editing this section to be
more concise and avoid repetition.

3.3 - Perhaps a clear definition for the word "pipe" belongs in the terminology
section? Although it may appear obvious as to what it means, it is jargon that
is not used in RFC 9132 nor 9133. Consider that a client split with multiple
interfaces/networks/DOTS domains etc may affect interpretation of the word, and
thus the potential value it should calculate and send.

4.2 - This section could be expanded to cover quite a few duplicate pieces of
normative language listed throughout later sections - for example there are many
references to 'cuid' being mandatory and should not be present in PUT/DELETE
request bodies. Putting common details in this section, and exceptions
throughout should make interpretation by implementers easier particularly for
the structure of Uri-Path values.

9 - It may be beneficial to implementers if this section provides guidance on
the use of plain text diagnostic payloads for the additional error cases this
document defines.

Nit:

8.2 - Figure 48 shows the target of "https1" not "http1", the text above
refers to the latter.



From nobody Mon Jan 17 01:35:40 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A27093A14FA; Mon, 17 Jan 2022 01:35:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 07jD42faucV5; Mon, 17 Jan 2022 01:35:23 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (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 932083A14F9; Mon, 17 Jan 2022 01:35:22 -0800 (PST)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr24.francetelecom.fr (ESMTP service) with ESMTPS id 4JcmwS5cJ4z1xxq;  Mon, 17 Jan 2022 10:35:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1642412120; bh=J8imZs5+aKZTTL9MqGFUJJs+3rldGVgV9NT3Ll7gle0=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=qvMbGMCB0DdT8JN0omO937oXnCylZXL6veHbRslQAVYzEYbsRAN3NOcuZs029iv8d MakzqzEngAG4ZcreJT/V/gHrIMXfkbPIqGczJFKGbh7DtT6PBSOlD1vzbmUHM793Np qjJciAOVfbFZ7oiudGwVGpIP4cHOo061j+tDpPJI2cmAyPuydJBRk5K+Yb6vSxPwoE oeTsTjU2bAqanPgkOrQFtay4u9PdrEHYolN0CraYDyjn5zrPU007wl2V0koFiGf0w7 KgeiTAwcguMF26qHX3lZwgaJ5Cl9Tvfd8TJ8hT7qMJc/gCFlDGMsIoAfHTHfeVdaID pL22cAWmhG2SA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr05.francetelecom.fr (ESMTP service) with ESMTPS id 4JcmwS45D2zyQS; Mon, 17 Jan 2022 10:35:20 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: tom petch <daedulus@btconnect.com>, "last-call@ietf.org" <last-call@ietf.org>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "valery@smyslov.net" <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry@ietf.org" <draft-ietf-dots-telemetry@ietf.org>
Thread-Topic: Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
Thread-Index: AQHYCULSD7/Svs/tXk+Y7jeLTmHZCKxm6W8w
Content-Class: 
Date: Mon, 17 Jan 2022 09:35:20 +0000
Message-ID: <29779_1642412120_61E53858_29779_198_1_787AE7BB302AE849A7480A190F8B933035473D6C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164182513674.28016.284174261896096787@ietfa.amsl.com> <61E16D53.7050003@btconnect.com>
In-Reply-To: <61E16D53.7050003@btconnect.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-17T09:32:33Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=7bba7e4d-2732-448e-a61a-65581ca2c161; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/WquqK2qJwot3P4bPR0B38-FBhE4>
Subject: Re: [Dots] Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2022 09:35:28 -0000

Hi Tom,=20

Thank you for the review. Much appreciated.=20

Please see inline.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: tom petch <daedulus@btconnect.com>
> Envoy=E9=A0: vendredi 14 janvier 2022 13:32
> =C0=A0: last-call@ietf.org
> Cc=A0: dots-chairs@ietf.org; valery@smyslov.net; dots@ietf.org; draft-
> ietf-dots-telemetry@ietf.org
> Objet=A0: Re: Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed
> Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed
> Standard
>=20
> Some stray thoughts
>=20
> I wonder if there is a recognised terminology for attacks, threats and
> such-like.  I have been looking at I2NSF I-D recently and they are,
> well, different.  I note too that secdir reviews thereof queried some of
> the I2NSF terminology but what is right and what is wrong?.  I am
> reminded of the efforts to produce a second version of the Security
> Glossary some time ago.

[Med] You may look at RFC4949, but that document requires a refresh. For th=
e particular DoS case, RFC4732 is still a good reading reference.=20

>=20
> I find the use of -g and -ps alien.  I worked out what they mean but
> cannot help feeling that there is a clearer way to express this, such as
> pps, bps, Bps (YANG does not like capitalisation but does allow it where
> it is widely recognised, which, for me, Bps is).

[Med] *-g is used to identify nodes of gauge type while *-ps identifies nod=
es that are expressed as a value "per second". We don't include the reasoni=
ng of the naming convention as what matters is the description of the attri=
butes, not their names. We can add a note if you think this is helpful.=20

>=20
> URI for IANA are inconsistent, http: and https: - since IANA allows
> http: (hurrah) I am easy with either but do like consistency

[Med] Fixed this one https://www.iana.org/assignments/enterprise-numbers.ht=
ml. Thanks.=20

>=20
> "The DOTS telemetry module (Section 10.1) uses "enumerations" rather
>     than "identities" to define units, samples, and intervals because
>     otherwise the namespace identifier "ietf-dots-telemetry" must be
>     included when a telemetry attribute is included "
> Well yes but that is saying the ietf-dots-telemetry is a bad choice of
> prefix - the 'ietf' is redundant and the 'telemetry' is prolix

[Med] We could shorten the prefix but the issue is still there:  have to in=
clude a prefix.=20=20

>=20
>        TBA: Overlapping pipe scope (see Section 12).
> could do with an explanatory note, perhaps one for the RFC Editor
>=20

[Med] Sure. Added a note to Section 12.2.=20

>=20
>     vendor-id:  Vendor ID is a security vendor's Enterprise Number as
>        registered with IANA [Enterprise-Numbers].  It is a four-byte
>        integer value.
> No, it is an integer which in this model is uint32 which can be
> represented in a number of ways

[Med] Fixed.=20

>=20
> The user has to understand that [Enterprise-Numbers] is the same as
> Private Enterprise Numbers", which may not be apparent; consistent
> terminology is good.

[Med] Not sure a (which) change is needed. The current text says:=20=20

   vendor-id:  Vendor ID is a security vendor's Enterprise Number as
      registered with IANA [Enterprise-Numbers].

with:

   [Enterprise-Numbers]
              "Private Enterprise Numbers", 4 May 2020,
              <http://www.iana.org/assignments/enterprise-numbers.html>.

>=20
> YANG TLD is out of date and URI lacks https:

[Med] OK

>=20
> Authors vary between the frontispiece,

[Med] That is not an issue.=20

 the YANG modules and Authors'
> Addresses

[Med] Fixed Tiru's address. Thanks.=20

>=20
> Two references in the YANG modules I do not see in the I-D References
>        <https://www.iana.org/assignments/protocol-numbers/>.
>        "Section 4.4.2 of RFC UUUU.";
> The latter is not an RFC I am familiar with (but then that is true of
> most RFC:-(
>=20

[Med] :-) Changed to "RFC 9132". Thanks.=20

>      reference
>        "IANA: Private Enterprise Numbers"; would be clearer with a URI,
> whereever it occurs which is in more than one place
>=20

[Med] Will leave this one for the RFC editor.=20

> Security COnsiderations uses part of the YANG Guidelines template but
> not all

[Med] That is on purpose:
* we don't use it in 13.1 because this YANG module is not used for manageme=
nt purposes:

   The DOTS telemetry module (Section 10.1) is not intended to be used
   via NETCONF/RESTCONF for DOTS server management purposes.  It serves
   only to provide a data model and encoding following [RFC8791].

* as we are pointing to rfc8783#section-10, only new considerations are inc=
luded here.=20

; TLS is notable for its absence.
>=20

[Med] That's covered in the 9132 and 8738. We don't repeat these aspects he=
re.=20

> Tom Petch
>=20
>=20
>=20
>=20
>=20
> On 10/01/2022 14:32, The IESG wrote:
> >
> > The IESG has received a request from the DDoS Open Threat Signaling WG
> > (dots) to consider the following document: - 'Distributed
> > Denial-of-Service Open Threat Signaling (DOTS) Telemetry'
> >    <draft-ietf-dots-telemetry-19.txt> as Proposed Standard
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > last-call@ietf.org mailing lists by 2022-01-24. Exceptionally,
> > comments may be sent to iesg@ietf.org instead. In either case, please
> > retain the beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >     This document aims to enrich the DOTS signal channel protocol with
> >     various telemetry attributes, allowing for optimal Distributed
> >     Denial-of-Service (DDoS) attack mitigation.  It specifies the
> normal
> >     traffic baseline and attack traffic telemetry attributes a DOTS
> >     client can convey to its DOTS server in the mitigation request,
> the
> >     mitigation status telemetry attributes a DOTS server can
> communicate
> >     to a DOTS client, and the mitigation efficacy telemetry attributes
> a
> >     DOTS client can communicate to a DOTS server.  The telemetry
> >     attributes can assist the mitigator to choose the DDoS mitigation
> >     techniques and perform optimal DDoS attack mitigation.
> >
> >
> >
> >
> > The file can be obtained via
> > https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/
> >
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> >
> >
> >
> > _______________________________________________
> > IETF-Announce mailing list
> > IETF-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf-announce
> > .
> >

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Mon Jan 17 02:06:16 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 511673A167B; Mon, 17 Jan 2022 02:06:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 sy6pyxU_v_In; Mon, 17 Jan 2022 02:06:05 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (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 98B973A167A; Mon, 17 Jan 2022 02:06:04 -0800 (PST)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr24.francetelecom.fr (ESMTP service) with ESMTPS id 4Jcnbt1gCRz1y7d;  Mon, 17 Jan 2022 11:06:02 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1642413962; bh=PQJKtV7ZwtsnuEv4Vi1B7i7Iop3+2Tlj0MC5Q5F9yA8=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=JRDt3NNRbxVRF0Jk4u8FZHmT9avs34GwJLIqsADCNI2t3sR8FN23i2zeg4XIi1f9r GVgmAMAWolswoDdNeQ/l4MkI5nyhbqouHEQxyBqsk/nwZVwTn7eNW8AWBc3Nb41d9E NPtDZ6JvdRjnyFG/6oQ3NjEeCfbTpp1GD6Rxf/M8nPms1EmJfpNk9PkGtzoShVVSA1 nNrfL7/npZ7UYjnlwO4XWmdvriNK1uwWLZ8XZ+sQ03WD6uYAZ9eRsZbLsy0kCB8aeS uLT61RIwdyPXapaTdiZ9t8poOjyd7EdLhDfo6e91dpnyCXhVjdPtMLoosZAphd2qkp 73aTOI4i3idEg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr02.francetelecom.fr (ESMTP service) with ESMTPS id 4Jcnbt087wz8sYV;  Mon, 17 Jan 2022 11:06:02 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: James Gruessing <james.ietf@gmail.com>, "art@ietf.org" <art@ietf.org>
CC: "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry.all@ietf.org" <draft-ietf-dots-telemetry.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: Artart last call review of draft-ietf-dots-telemetry-19
Thread-Index: AQHYCkCnhVuAaerS3EaYcLe0OGgWpKxmyX8A
Content-Class: 
Date: Mon, 17 Jan 2022 10:06:01 +0000
Message-ID: <21593_1642413962_61E53F8A_21593_138_1_787AE7BB302AE849A7480A190F8B933035473DAB@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164227257574.1686.16790605376691634274@ietfa.amsl.com>
In-Reply-To: <164227257574.1686.16790605376691634274@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-17T07:45:44Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=e0c3b663-f553-4047-a492-f65863073e6b; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/LR6wlSHymcTyjlCwNSFbvaxbDZY>
Subject: Re: [Dots] Artart last call review of draft-ietf-dots-telemetry-19
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2022 10:06:10 -0000

SGkgSmFtZXMsIA0KDQpUaGFuayB5b3UgZm9yIHRoZSByZXZpZXcuIA0KDQpQbGVhc2Ugc2VlIGlu
bGluZS4NCg0KQ2hlZXJzLA0KTWVkDQoNCj4gLS0tLS1NZXNzYWdlIGQnb3JpZ2luZS0tLS0tDQo+
IERlwqA6IEphbWVzIEdydWVzc2luZyB2aWEgRGF0YXRyYWNrZXIgPG5vcmVwbHlAaWV0Zi5vcmc+
DQo+IEVudm95w6nCoDogc2FtZWRpIDE1IGphbnZpZXIgMjAyMiAxOTo1MA0KPiDDgMKgOiBhcnRA
aWV0Zi5vcmcNCj4gQ2PCoDogZG90c0BpZXRmLm9yZzsgZHJhZnQtaWV0Zi1kb3RzLXRlbGVtZXRy
eS5hbGxAaWV0Zi5vcmc7IGxhc3QtDQo+IGNhbGxAaWV0Zi5vcmcNCj4gT2JqZXTCoDogQXJ0YXJ0
IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1kb3RzLXRlbGVtZXRyeS0xOQ0KPiANCj4g
UmV2aWV3ZXI6IEphbWVzIEdydWVzc2luZw0KPiBSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIE5p
dHMNCj4gDQo+IFRoaXMgaXMgbXkgcmV2aWV3IG9mIGRyYWZ0LWlldGYtZG90cy10ZWxlbWV0cnkt
MTkgYXMgcmVxdWVzdGVkIGJ5IEFSVEFSVA0KPiBjaGFpcnMuDQo+IA0KPiBPdmVyYWxsIHRoaXMg
aXMgYSB3ZWxsIHdyaXR0ZW4gZG9jdW1lbnQgdGhhdCBleHBsYWlucyBpdHMgcHVycG9zZSwNCj4g
cmF0aW9uYWxlLCBhbmQgdGVjaG5pY2FsIGRldGFpbHMgZm9yIHNvbWVvbmUgbGlrZSBteXNlbGYg
d2l0aCBubw0KPiBwcmV2aW91cyBrbm93bGVkZ2Ugb2YgRE9UUyBvciBpdHMgdW5kZXJseWluZyBk
ZXBlbmRlbnQgcHJvdG9jb2xzLiBBcw0KPiBzdWNoIG15IGZvY3VzIGluIHRoaXMgcmV2aWV3IGhh
cyBiZWVuIGxvb2tpbmcgYXQgdGhlIHJlYWRhYmlsaXR5IG9mIHRoZQ0KPiBkb2N1bWVudCB0aHJv
dWdoIHRoZSBleWVzIG9mIGEgZnV0dXJlIGltcGxlbWVudGVyLg0KDQpbTWVkXSBUaGFua3MuIA0K
DQo+IA0KPiBDb21tZW50czoNCj4gDQo+IDMuMiAtIEF0IGEgZmV3IHBvaW50cyBpbiB0aGlzIHNl
Y3Rpb24sIHRoZSBjb25jZXB0IG9mICJtZWFzdXJlbWVudHMNCj4gc2hvdWxkIGJlIHRha2VuIHdo
ZW4gdHJhZmZpYyBpcyAnbm9ybWFsJyIgaXMgcmVwZWF0ZWQgYSBmZXcgdGltZXMgYW5kDQo+IGRv
bmUgaW4gYSB3YXkgbm90IGFzIGNsZWFyIGFzIGl0IGNvdWxkIGJlLiBUaGUgYXV0aG9ycyBzaG91
bGQgY29uc2lkZXINCj4gZWRpdGluZyB0aGlzIHNlY3Rpb24gdG8gYmUgbW9yZSBjb25jaXNlIGFu
ZCBhdm9pZCByZXBldGl0aW9uLg0KDQpbTWVkXSBGb3VuZCBhbmQgZml4ZWQgb25lIHNlbnRlbmNl
IHRoYXQgSSB0aGluayBpcyByZWR1bmRhbnQuIE5vdCBzdXJlIGlmIHlvdSBoYXZlIGlkZW50aWZp
ZWQgb3RoZXJzLiANCg0KPiANCj4gMy4zIC0gUGVyaGFwcyBhIGNsZWFyIGRlZmluaXRpb24gZm9y
IHRoZSB3b3JkICJwaXBlIiBiZWxvbmdzIGluIHRoZQ0KPiB0ZXJtaW5vbG9neSBzZWN0aW9uPyBB
bHRob3VnaCBpdCBtYXkgYXBwZWFyIG9idmlvdXMgYXMgdG8gd2hhdCBpdCBtZWFucywNCj4gaXQg
aXMgamFyZ29uIHRoYXQgaXMgbm90IHVzZWQgaW4gUkZDIDkxMzIgbm9yIDkxMzMuIENvbnNpZGVy
IHRoYXQgYQ0KPiBjbGllbnQgc3BsaXQgd2l0aCBtdWx0aXBsZSBpbnRlcmZhY2VzL25ldHdvcmtz
L0RPVFMgZG9tYWlucyBldGMgbWF5DQo+IGFmZmVjdCBpbnRlcnByZXRhdGlvbiBvZiB0aGUgd29y
ZCwgYW5kIHRodXMgdGhlIHBvdGVudGlhbCB2YWx1ZSBpdA0KPiBzaG91bGQgY2FsY3VsYXRlIGFu
ZCBzZW5kLg0KDQpbTWVkXSBTdXJlLiBBZGRlZCBhIG5ldyBlbnRyeSB0byBTZWN0aW9uIDIuIA0K
DQo+IA0KPiA0LjIgLSBUaGlzIHNlY3Rpb24gY291bGQgYmUgZXhwYW5kZWQgdG8gY292ZXIgcXVp
dGUgYSBmZXcgZHVwbGljYXRlDQo+IHBpZWNlcyBvZiBub3JtYXRpdmUgbGFuZ3VhZ2UgbGlzdGVk
IHRocm91Z2hvdXQgbGF0ZXIgc2VjdGlvbnMgLSBmb3INCj4gZXhhbXBsZSB0aGVyZSBhcmUgbWFu
eSByZWZlcmVuY2VzIHRvICdjdWlkJyBiZWluZyBtYW5kYXRvcnkgYW5kIHNob3VsZA0KPiBub3Qg
YmUgcHJlc2VudCBpbiBQVVQvREVMRVRFIHJlcXVlc3QgYm9kaWVzLiBQdXR0aW5nIGNvbW1vbiBk
ZXRhaWxzIGluDQo+IHRoaXMgc2VjdGlvbiwgYW5kIGV4Y2VwdGlvbnMgdGhyb3VnaG91dCBzaG91
bGQgbWFrZSBpbnRlcnByZXRhdGlvbiBieQ0KPiBpbXBsZW1lbnRlcnMgZWFzaWVyIHBhcnRpY3Vs
YXJseSBmb3IgdGhlIHN0cnVjdHVyZSBvZiBVcmktUGF0aCB2YWx1ZXMuDQoNCltNZWRdIFRoYW5r
IHlvdSBmb3IgdGhlIHByb3Bvc2FsLCBidXQgd2UgcHJlZmVyIHRoZSBjdXJyZW50IHZlcnNpb24g
YXMgd2UgaGF2ZSBrZXkgaW5mb3JtYXRpb24gaW4gb25lIHNpbmdsZSBwbGFjZS4NCg0KPiANCj4g
OSAtIEl0IG1heSBiZSBiZW5lZmljaWFsIHRvIGltcGxlbWVudGVycyBpZiB0aGlzIHNlY3Rpb24g
cHJvdmlkZXMNCj4gZ3VpZGFuY2Ugb24gdGhlIHVzZSBvZiBwbGFpbiB0ZXh0IGRpYWdub3N0aWMg
cGF5bG9hZHMgZm9yIHRoZSBhZGRpdGlvbmFsDQo+IGVycm9yIGNhc2VzIHRoaXMgZG9jdW1lbnQg
ZGVmaW5lcy4NCj4gDQoNCltNZWRdIE9LLiBBZGRlZCBhIG5ldyB0ZXh0IHRvIGNvdmVyIHRoaXMu
ICANCg0KPiBOaXQ6DQo+IA0KPiA4LjIgLSBGaWd1cmUgNDggc2hvd3MgdGhlIHRhcmdldCBvZiAi
aHR0cHMxIiBub3QgImh0dHAxIiwgdGhlIHRleHQgYWJvdmUNCj4gcmVmZXJzIHRvIHRoZSBsYXR0
ZXIuDQo+IA0KDQpbTWVkXSBUaGFuayB5b3UgZm9yIGNhdGNoaW5nIHRoaXMuIEZpeGVkLiANCg0K
RldJVywgd2Ugd2lsbCBBQ0sgeW91ciByZXZpZXcgaW4gdGhlIG5leHQgaXRlcmF0aW9uLiBBIGRp
ZmYgdG8gdHJhY2sgdGhlIGNoYW5nZXMgdG8gYWRkcmVzcyB5b3VyIHJldmlldyBjYW4gYmUgc2Vl
biBhdDogaHR0cHM6Ly90aW55dXJsLmNvbS9kb3RzLXRlbGVtZXRyeS1sYXRlc3QuDQoKX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
XwoKQ2UgbWVzc2FnZSBldCBzZXMgcGllY2VzIGpvaW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMg
aW5mb3JtYXRpb25zIGNvbmZpZGVudGllbGxlcyBvdSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVu
dCBkb25jCnBhcyBldHJlIGRpZmZ1c2VzLCBleHBsb2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jp
c2F0aW9uLiBTaSB2b3VzIGF2ZXogcmVjdSBjZSBtZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6
IGxlIHNpZ25hbGVyCmEgbCdleHBlZGl0ZXVyIGV0IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMg
cGllY2VzIGpvaW50ZXMuIExlcyBtZXNzYWdlcyBlbGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRp
YmxlcyBkJ2FsdGVyYXRpb24sCk9yYW5nZSBkZWNsaW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNp
IGNlIG1lc3NhZ2UgYSBldGUgYWx0ZXJlLCBkZWZvcm1lIG91IGZhbHNpZmllLiBNZXJjaS4KClRo
aXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBv
ciBwcml2aWxlZ2VkIGluZm9ybWF0aW9uIHRoYXQgbWF5IGJlIHByb3RlY3RlZCBieSBsYXc7CnRo
ZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRlZCwgdXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRo
b3Jpc2F0aW9uLgpJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVh
c2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRh
Y2htZW50cy4KQXMgZW1haWxzIG1heSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBm
b3IgbWVzc2FnZXMgdGhhdCBoYXZlIGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVk
LgpUaGFuayB5b3UuCgo=


From nobody Mon Jan 17 04:51:15 2022
Return-Path: <valery@smyslov.net>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EE2E3A115D; Mon, 17 Jan 2022 04:51:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, 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=smyslov.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 oUrT_1ge2Uru; Mon, 17 Jan 2022 04:51:08 -0800 (PST)
Received: from direct.host-care.com (direct.host-care.com [198.136.54.115]) (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 B66173A115B; Mon, 17 Jan 2022 04:51:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smyslov.net ; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :Date:Subject:In-Reply-To:References:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=u47V25S31IgoRf6RJGKrOelAbgPh0oqv6L1TXgyvNFA=; b=bw/or8b+1Y035YVXDyMIDK3bnB oQ9H7JabhRu3ovfy5zuiCRdfm4dE2b8pwsYSefcpQDxIQH4x9pu0gGb+bvmPo3C/FtBA17NZIQGUG P+bB6IeNF38t5EUjpJl+FBqgo/S470A43gIEfaS+vExsCF/0JpKEzinj4hcwPHjZwT0VPhZNhS2OF H2irRt0z+mWy/xWl6uV08oW3mjHaUd+dLr957Y/N8iyZrDaseDYSO5nI2puOxQeWdZNHcNCybo6Jx RTEow4RPRm2zeImub9psVMIYym0vMhudFkTd06HB5WBCZrbs3Ya2XvadQaP4WY+1bPsF4QSjM+hyc xQ2JgOYw==;
Received: from [93.188.44.204] (port=56735 helo=buildpc) by direct.host-care.com with esmtpsa (TLS1.2) tls TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <valery@smyslov.net>) id 1n9RTS-0002jJ-4D; Mon, 17 Jan 2022 07:51:02 -0500
From: "Valery Smyslov" <valery@smyslov.net>
To: <mohamed.boucadair@orange.com>, <dots@ietf.org>
Cc: <dots-chairs@ietf.org>
References: <164137764747.8868.9592514632814928071@ietfa.amsl.com> <11126_1641378084_61D57124_11126_289_1_787AE7BB302AE849A7480A190F8B93303546D15D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <11126_1641378084_61D57124_11126_289_1_787AE7BB302AE849A7480A190F8B93303546D15D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Date: Mon, 17 Jan 2022 15:50:59 +0300
Message-ID: <06dc01d80ba0$e27f3510$a77d9f30$@smyslov.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIwQF2+vHgC3U85zaccyBApjEMQfQGmP73Pq6mOKSA=
Content-Language: ru
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - direct.host-care.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - smyslov.net
X-Get-Message-Sender-Via: direct.host-care.com: authenticated_id: valery@smyslov.net
X-Authenticated-Sender: direct.host-care.com: valery@smyslov.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/ROSocp2ZEDzupaGnpXAHkQndAz8>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-robust-blocks-01.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2022 12:51:14 -0000

Hi Med, Jon,

before issuing WGLC I'd like to request an early YANG Doctors review.

I'll do it shortly.

Regards,
Valery.

> Hi all,
>=20
> We updated the draft with the following changes:
> * Add non-receive-timeout to the parameters that can be configured.
> * Add a reminder that the attributes are mapped to CBOR when signaled =
in a DOTS message
> * Add new text to indicate the behavior to follow to make use of the =
new attributes
> * Add reference statements to the YANG module
> * Rearrange the text for better readability
> * Updated the requested IANA range to comply with Section 3.1 of =
RFC9132
> * Fix nits
>=20
> We believe this version is ready for the WGLC.
>=20
> Cheers,
> Jon & Med
>=20
> > -----Message d'origine-----
> > De=A0: Dots <dots-bounces@ietf.org> De la part de =
internet-drafts@ietf.org
> > Envoy=E9=A0: mercredi 5 janvier 2022 11:14
> > =C0=A0: i-d-announce@ietf.org
> > Cc=A0: dots@ietf.org
> > Objet=A0: [Dots] I-D Action: draft-ietf-dots-robust-blocks-01.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > This draft is a work item of the DDoS Open Threat Signaling WG of =
the
> > IETF.
> >
> >         Title           : Distributed Denial-of-Service Open Threat
> > Signaling (DOTS) Signal Channel Configuration Attributes for Robust =
Block
> > Transmission
> >         Authors         : Mohamed Boucadair
> >                           Jon Shallow
> > 	Filename        : draft-ietf-dots-robust-blocks-01.txt
> > 	Pages           : 21
> > 	Date            : 2022-01-05
> >
> > Abstract:
> >    This document specifies new DOTS signal channel configuration
> >    parameters that are negotiated between DOTS peers to enable the =
use
> >    of Q-Block1 and Q-Block2 CoAP Options.  These options enable =
robust
> >    and faster transmission rates for large amounts of data with less
> >    packet interchanges as well as supporting faster recovery should =
any
> >    of the blocks get lost in transmission.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-dots-robust-blocks/
> >
> > There is also an htmlized version available at:
> > =
https://datatracker.ietf.org/doc/html/draft-ietf-dots-robust-blocks-01
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dots-robust-blocks-01
> >
> >
> > Internet-Drafts are also available by rsync at =
rsync.ietf.org::internet-
> > drafts
> >
> >
> > _______________________________________________
> > Dots mailing list
> > Dots@ietf.org
> > https://www.ietf.org/mailman/listinfo/dots
>=20
> =
_________________________________________________________________________=
___________________
> _____________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations =
confidentielles ou privilegiees et ne
> doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez =
recu ce message par erreur, veuillez le
> signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les =
messages electroniques etant susceptibles
> d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, =
deforme ou falsifie. Merci.
>=20
> This message and its attachments may contain confidential or =
privileged information that may be protected
> by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and =
delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.
> Thank you.



From nobody Mon Jan 17 06:39:22 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C74873A090D; Mon, 17 Jan 2022 06:39:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 mV0wHho6LoAW; Mon, 17 Jan 2022 06:39:16 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (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 4D0F83A0907; Mon, 17 Jan 2022 06:39:16 -0800 (PST)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr26.francetelecom.fr (ESMTP service) with ESMTPS id 4Jcvg51VSfzyjJ; Mon, 17 Jan 2022 15:39:13 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1642430353; bh=/2DFlOVoYNXBsIzbN/oZjLssrSKew1T1fK8HQVeeXpc=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=b00k1PQmeHsM9arE+EHbR9Aa5mb1IO0gn0RVGkE9+V5yqRZkwXM24B+FHxwCn1Oaj JYchYVhLYiPg8SWUafzDaddri3fg/LacraEVAsNm4ysaoDQ6k2sYQwxY/t+RbPWaJN CokcY3PwZ0Qe/l/n6+gMzdNhrkNuExYIgUYMnQSc9LTlyc8hHUXGJFlqQr37SYC7uh dm55vberPCZugB4QUHxKhYQmHw1kncvriRB/wC7o3PtSdTfZ878HwQfrOThBML1gk8 FkMrIu8cLVC1c0LKYogqRMGoBMpne75cd8XPSIeAuQSZffv26sJ9zo2SPqUHraHFzF v2HjofzUc6yww==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr04.francetelecom.fr (ESMTP service) with ESMTPS id 4Jcvg506kQz1xpM;  Mon, 17 Jan 2022 15:39:13 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: James <james.ietf@gmail.com>
CC: "art@ietf.org" <art@ietf.org>, "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry.all@ietf.org" <draft-ietf-dots-telemetry.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: Artart last call review of draft-ietf-dots-telemetry-19
Thread-Index: AQHYC61IXjKgyXERdEa0IslcLBIfZKxnRPgg
Content-Class: 
Date: Mon, 17 Jan 2022 14:39:11 +0000
Message-ID: <21278_1642430353_61E57F91_21278_116_1_787AE7BB302AE849A7480A190F8B933035473FC7@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164227257574.1686.16790605376691634274@ietfa.amsl.com> <21593_1642413962_61E53F8A_21593_138_1_787AE7BB302AE849A7480A190F8B933035473DAB@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <6783496E-F5B5-4D2F-96B2-744D52CC56EF@gmail.com>
In-Reply-To: <6783496E-F5B5-4D2F-96B2-744D52CC56EF@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-17T14:26:55Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=53284a87-4c32-4d14-812a-5d84aca170b0; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/pPklXIPXIJr69SY4phTDc2aK4WQ>
Subject: Re: [Dots] Artart last call review of draft-ietf-dots-telemetry-19
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2022 14:39:21 -0000

UmUtLA0KDQpUaGFuayB5b3UgZm9yIHRoZSBmb2xsb3ctdXAuDQoNClBsZWFzZSBzZWUgYmVsb3cg
Zm9yIHRoZSBjb21tZW50IGFib3V0IHBpcGVzLiANCg0KQ2hlZXJzLA0KTWVkDQoNCj4gLS0tLS1N
ZXNzYWdlIGQnb3JpZ2luZS0tLS0tDQo+IERlwqA6IEphbWVzIDxqYW1lcy5pZXRmQGdtYWlsLmNv
bT4NCj4gRW52b3nDqcKgOiBsdW5kaSAxNyBqYW52aWVyIDIwMjIgMTU6MTkNCj4gw4DCoDogQk9V
Q0FEQUlSIE1vaGFtZWQgSU5OT1YvTkVUIDxtb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tPg0K
PiBDY8KgOiBhcnRAaWV0Zi5vcmc7IGRvdHNAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtZG90cy0NCj4g
dGVsZW1ldHJ5LmFsbEBpZXRmLm9yZzsgbGFzdC1jYWxsQGlldGYub3JnDQo+IE9iamV0wqA6IFJl
OiBBcnRhcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWRvdHMtdGVsZW1ldHJ5LTE5
DQo+IA0KPiBUaGFua3MgZm9yIHRoZSBjaGFuZ2VzLiBBIGZldyBjb21tZW50cyBhbHNvIGlubGlu
ZS4NCj4gDQo+IC0gSg0KPiANCj4gPiBPbiAxNyBKYW4gMjAyMiwgYXQgMTE6MDYsIDxtb2hhbWVk
LmJvdWNhZGFpckBvcmFuZ2UuY29tPg0KPiA8bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbT4g
d3JvdGU6DQo+ID4NCj4gPiBIaSBKYW1lcywNCj4gPg0KPiA+IFRoYW5rIHlvdSBmb3IgdGhlIHJl
dmlldy4NCj4gPg0KPiA+IFBsZWFzZSBzZWUgaW5saW5lLg0KPiA+DQo+ID4gQ2hlZXJzLA0KPiA+
IE1lZA0KPiA+DQo+ID4+IC0tLS0tTWVzc2FnZSBkJ29yaWdpbmUtLS0tLQ0KPiA+PiBEZSA6IEph
bWVzIEdydWVzc2luZyB2aWEgRGF0YXRyYWNrZXIgPG5vcmVwbHlAaWV0Zi5vcmc+IEVudm95w6kg
Og0KPiA+PiBzYW1lZGkgMTUgamFudmllciAyMDIyIDE5OjUwIMOAIDogYXJ0QGlldGYub3JnIENj
IDogZG90c0BpZXRmLm9yZzsNCj4gPj4gZHJhZnQtaWV0Zi1kb3RzLXRlbGVtZXRyeS5hbGxAaWV0
Zi5vcmc7IGxhc3QtIGNhbGxAaWV0Zi5vcmcgT2JqZXQgOg0KPiA+PiBBcnRhcnQgbGFzdCBjYWxs
IHJldmlldyBvZiBkcmFmdC1pZXRmLWRvdHMtdGVsZW1ldHJ5LTE5DQo+ID4+DQo+ID4+IFJldmll
d2VyOiBKYW1lcyBHcnVlc3NpbmcNCj4gPj4gUmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBOaXRz
DQo+ID4+DQo+ID4+IFRoaXMgaXMgbXkgcmV2aWV3IG9mIGRyYWZ0LWlldGYtZG90cy10ZWxlbWV0
cnktMTkgYXMgcmVxdWVzdGVkIGJ5DQo+ID4+IEFSVEFSVCBjaGFpcnMuDQo+ID4+DQo+ID4+IE92
ZXJhbGwgdGhpcyBpcyBhIHdlbGwgd3JpdHRlbiBkb2N1bWVudCB0aGF0IGV4cGxhaW5zIGl0cyBw
dXJwb3NlLA0KPiA+PiByYXRpb25hbGUsIGFuZCB0ZWNobmljYWwgZGV0YWlscyBmb3Igc29tZW9u
ZSBsaWtlIG15c2VsZiB3aXRoIG5vDQo+ID4+IHByZXZpb3VzIGtub3dsZWRnZSBvZiBET1RTIG9y
IGl0cyB1bmRlcmx5aW5nIGRlcGVuZGVudCBwcm90b2NvbHMuIEFzDQo+ID4+IHN1Y2ggbXkgZm9j
dXMgaW4gdGhpcyByZXZpZXcgaGFzIGJlZW4gbG9va2luZyBhdCB0aGUgcmVhZGFiaWxpdHkgb2YN
Cj4gPj4gdGhlIGRvY3VtZW50IHRocm91Z2ggdGhlIGV5ZXMgb2YgYSBmdXR1cmUgaW1wbGVtZW50
ZXIuDQo+ID4NCj4gPiBbTWVkXSBUaGFua3MuDQo+ID4NCj4gPj4NCj4gPj4gQ29tbWVudHM6DQo+
ID4+DQo+ID4+IDMuMiAtIEF0IGEgZmV3IHBvaW50cyBpbiB0aGlzIHNlY3Rpb24sIHRoZSBjb25j
ZXB0IG9mICJtZWFzdXJlbWVudHMNCj4gPj4gc2hvdWxkIGJlIHRha2VuIHdoZW4gdHJhZmZpYyBp
cyAnbm9ybWFsJyIgaXMgcmVwZWF0ZWQgYSBmZXcgdGltZXMgYW5kDQo+ID4+IGRvbmUgaW4gYSB3
YXkgbm90IGFzIGNsZWFyIGFzIGl0IGNvdWxkIGJlLiBUaGUgYXV0aG9ycyBzaG91bGQNCj4gPj4g
Y29uc2lkZXIgZWRpdGluZyB0aGlzIHNlY3Rpb24gdG8gYmUgbW9yZSBjb25jaXNlIGFuZCBhdm9p
ZA0KPiByZXBldGl0aW9uLg0KPiA+DQo+ID4gW01lZF0gRm91bmQgYW5kIGZpeGVkIG9uZSBzZW50
ZW5jZSB0aGF0IEkgdGhpbmsgaXMgcmVkdW5kYW50LiBOb3Qgc3VyZQ0KPiBpZiB5b3UgaGF2ZSBp
ZGVudGlmaWVkIG90aGVycy4NCj4gDQo+IFtKYW1lc10gSSBoYXZlbid0IGlkZW50aWZpZWQgYW55
dGhpbmcgZWxzZSBzcGVjaWZpYywgaG93ZXZlciB5b3VyIGNoYW5nZQ0KPiBpcyBhIGdvb2QgaW1w
cm92ZW1lbnQuDQo+IA0KPiA+DQo+ID4+DQo+ID4+IDMuMyAtIFBlcmhhcHMgYSBjbGVhciBkZWZp
bml0aW9uIGZvciB0aGUgd29yZCAicGlwZSIgYmVsb25ncyBpbiB0aGUNCj4gPj4gdGVybWlub2xv
Z3kgc2VjdGlvbj8gQWx0aG91Z2ggaXQgbWF5IGFwcGVhciBvYnZpb3VzIGFzIHRvIHdoYXQgaXQN
Cj4gPj4gbWVhbnMsIGl0IGlzIGphcmdvbiB0aGF0IGlzIG5vdCB1c2VkIGluIFJGQyA5MTMyIG5v
ciA5MTMzLiBDb25zaWRlcg0KPiA+PiB0aGF0IGEgY2xpZW50IHNwbGl0IHdpdGggbXVsdGlwbGUg
aW50ZXJmYWNlcy9uZXR3b3Jrcy9ET1RTIGRvbWFpbnMNCj4gPj4gZXRjIG1heSBhZmZlY3QgaW50
ZXJwcmV0YXRpb24gb2YgdGhlIHdvcmQsIGFuZCB0aHVzIHRoZSBwb3RlbnRpYWwNCj4gPj4gdmFs
dWUgaXQgc2hvdWxkIGNhbGN1bGF0ZSBhbmQgc2VuZC4NCj4gPg0KPiA+IFtNZWRdIFN1cmUuIEFk
ZGVkIGEgbmV3IGVudHJ5IHRvIFNlY3Rpb24gMi4NCj4gDQo+IFtKYW1lc10gVGhhbmsgeW91LCB0
aGF0J3MgY2xlYXJlci4gQXMgYW4gYXNpZGUgdG8gdGhpcyBkZWZpbml0aW9uLA0KPiBhcm91bmQg
Ni4yIGFuZCBsYXRlciBJIGNhbm5vdCBmaW5kIGFueSB0ZXh0IHRoYXQgY292ZXJzIGNsaWVudHMg
bm90DQo+IHNlbmRpbmcgYSBwaXBlIGNhcGFjaXR5IGZpZ3VyZSBncmVhdGVyIHRoYW4gYWN0dWFs
KiBhdmFpbGFibGUgY2FwYWNpdHkgLQ0KPiBpbiBhIHNpbXBsZSBleGFtcGxlLCBhIGNsaWVudCB3
aXRoIDFHYml0IHByb2JhYmx5IHNob3VsZG4ndCBhbm5vdW5jZQ0KPiAxMEdiaXQuIERpZCBJIG1p
c3MgaXQsIG9yIGlzIHRoYXQgc29tZXRoaW5nIHRvIGNvbnNpZGVyPw0KPiANCg0KW01lZF0gV2hh
dCBpcyBhZHZlcnRpc2VkIGlzIG5vdCBuZWNlc3NhcmlseSBhIGxvY2FsIGludGVyZmFjZSBvZiB0
aGUgY2xpZW50LCBidXQgdGhlICJwaXBlIiBvZiB0aGUgY2xpZW50ICoqZG9tYWluKiouIFRoaW5r
IGFib3V0IGNhc2VzIHdoZXJlIHRoZSBET1RTIGNsaWVudCBpcyBub3QgZW1iZWRkZWQgaW4gYSBy
b3V0ZXIuIFdlIGRvbid0IGluY2x1ZGUgY2hlY2tzIGFnYWluc3Qgc2lnbmFsZWQgcGlwZSBpbmZv
cm1hdGlvbiBiZWNhdXNlIGhvdyBhIGNsaWVudCByZXRyaWV2ZXMgKCBvciBpcyBwcm92aWRlZCB3
aXRoKSB0aGUgaW5mb3JtYXRpb24gdG8gc2lnbmFsIGlzIGRlcGxveW1lbnQtc3BlY2lmaWMuICAg
DQoNCg0KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18KCkNlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQg
Y29udGVuaXIgZGVzIGluZm9ybWF0aW9ucyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVz
IGV0IG5lIGRvaXZlbnQgZG9uYwpwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGll
cyBzYW5zIGF1dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJy
ZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxlcgphIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBh
aW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBl
dGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLApPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNw
b25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZp
ZS4gTWVyY2kuCgpUaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBj
b25maWRlbnRpYWwgb3IgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0
ZWQgYnkgbGF3Owp0aGV5IHNob3VsZCBub3QgYmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVk
IHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4KSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBp
biBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdl
IGFuZCBpdHMgYXR0YWNobWVudHMuCkFzIGVtYWlscyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlz
IG5vdCBsaWFibGUgZm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2Vk
IG9yIGZhbHNpZmllZC4KVGhhbmsgeW91LgoK


From nobody Mon Jan 17 06:42:08 2022
Return-Path: <noreply@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 65A533A0923; Mon, 17 Jan 2022 06:42:07 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Michal_Va=C5=A1ko_via_Datatracker?= <noreply@ietf.org>
To: <yang-doctors@ietf.org>
Cc: dots@ietf.org, draft-ietf-dots-robust-blocks.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164243052732.6946.2539903030545924979@ietfa.amsl.com>
Reply-To: =?utf-8?q?Michal_Va=C5=A1ko?= <mvasko@cesnet.cz>
Date: Mon, 17 Jan 2022 06:42:07 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/WWTrWjRfVcitRJAAdhlj_hElNU0>
Subject: [Dots] Yangdoctors early review of draft-ietf-dots-robust-blocks-01
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2022 14:42:07 -0000

Reviewer: Michal Vaško
Review result: Ready

The YANG module is fairly short and straightforward in its content but there is
a YANG structure-augment extension used with single-case choice that is ready
for further augments. Because of that I am quite confident in saying that the
authors are proficient in YANG and I could not find any issues in the module,
anyway.



From nobody Mon Jan 17 07:05:40 2022
Return-Path: <valery@smyslov.net>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B87B3A0B2A; Mon, 17 Jan 2022 07:05:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level: 
X-Spam-Status: No, score=-7.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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=smyslov.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 sOA7q1j0ekWK; Mon, 17 Jan 2022 07:05:33 -0800 (PST)
Received: from direct.host-care.com (direct.host-care.com [198.136.54.115]) (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 D92E13A0B20; Mon, 17 Jan 2022 07:05:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smyslov.net ; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :Date:Subject:Cc:To:From:Sender:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=HMfz4/ChSy+YajFaLjCCLKQThfqwY253evDW9cMKRGo=; b=D6nq4qW200MD/VHJXXV3UERpRh eJjzhDtrzeu8sl1EpuKZYe/uERlhwgrm+I54bDbMgGa9N55iRFsDinD9/nW8o04AXyY693YHCHYvG iYA1IkbB5oNyUjNmUY0iCp8SJ24chH60kAgHRjghiZKWXzNgXzWPgitJXHqoLSElebrb6COVTefK/ gpFPC/lScQeaujgBPTd9XrkT7QgvNtYH0QyrfPvGVSjOvUmMaAsZzCQFpSGZdIgLgd4Rnn/VdGyT4 3wbvs2mK3FqUIyNVuCCmcW0q+i6mY2beprsguOgeUlTzO0MdAkm9EQjUyKkDfncgkcRPkRJUNc07f 3TPiw+AQ==;
Received: from 78-107-207-25.broadband.corbina.ru ([78.107.207.25]:51094 helo=chichi) by direct.host-care.com with esmtpsa (TLS1.2) tls TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <valery@smyslov.net>) id 1n9TZW-0003PF-Rj; Mon, 17 Jan 2022 10:05:27 -0500
From: "Valery Smyslov" <valery@smyslov.net>
To: <dots@ietf.org>
Cc: <draft-ietf-dots-robust-blocks@ietf.org>, <dots-chairs@ietf.org>
Date: Mon, 17 Jan 2022 18:05:23 +0300
Message-ID: <001301d80bb3$a8afba90$fa0f2fb0$@smyslov.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdgLs2reOBhOQVf/TFefiVWHV3zYzQ==
Content-Language: ru
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - direct.host-care.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - smyslov.net
X-Get-Message-Sender-Via: direct.host-care.com: authenticated_id: valery@smyslov.net
X-Authenticated-Sender: direct.host-care.com: valery@smyslov.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/ZQ468xYgPQf8yDRWA9VXxZXHjc0>
Subject: [Dots] WGLC for draft-ietf-dots-robust-blocks-01
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2022 15:05:39 -0000

Hi,

this message starts a two-week working group last call for
draft-ietf-dots-robust-blocks-01.
The WGLC will end on Monday, January 31. Please, review the draft and send
your comments to the mailing list.

Regards,
Frank & Valery.


From nobody Mon Jan 17 22:25:41 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57AA63A1563; Mon, 17 Jan 2022 22:25:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 sOx9x_5QNYsk; Mon, 17 Jan 2022 22:25:09 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (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 3F5F23A154E; Mon, 17 Jan 2022 22:25:06 -0800 (PST)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar24.francetelecom.fr (ESMTP service) with ESMTPS id 4JdJfS2f85z5wMY;  Tue, 18 Jan 2022 07:25:04 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1642487104; bh=RENs3Uj9d4/r7inTuUAZHcfQqKUWIk9r606he4vCQ74=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=Oqy+vFlkbUz6P5GRkMRodMw/WRFA/B32euvSZm3DdsMs4a5YPdY24R8YnSYUYOgly pqBAEEkQj6B2raV7Ml6gR+nr/5UkQhNEAd4iYH/aaR67MICX/H+mhH1vnFP46znsIU o9S4/XuMYSRXUhbty03Ohnem6Ho4Gwq6WvrUagB8vJgtBxO0n6ZqKWCH4lKSeG2j9A zzN46l7fL06qQ029PygJjecf2dO7u/K3QNEmVddU9fP+vy0tOGHHHH4tpVWsMaDFXd xsD5alkAFTote39/So3CcRd7ArArYHdZDaH7K1ICEKk6d6UlYsJXDKhkaAiy2F4Sf0 qCl/3/wTa6VwQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar06.francetelecom.fr (ESMTP service) with ESMTPS id 4JdJfS1WZnz3wbJ;  Tue, 18 Jan 2022 07:25:04 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: =?utf-8?B?TWljaGFsIFZhxaFrbw==?= <mvasko@cesnet.cz>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-robust-blocks.all@ietf.org" <draft-ietf-dots-robust-blocks.all@ietf.org>
Thread-Topic: Yangdoctors early review of draft-ietf-dots-robust-blocks-01
Thread-Index: AQHYC7BoMXuIA4urDkSjTLPUsUvTVaxoTobA
Content-Class: 
Date: Tue, 18 Jan 2022 06:25:03 +0000
Message-ID: <5527_1642487104_61E65D40_5527_38_1_787AE7BB302AE849A7480A190F8B93303547C7ED@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164243052732.6946.2539903030545924979@ietfa.amsl.com>
In-Reply-To: <164243052732.6946.2539903030545924979@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-18T06:16:55Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=b14ec402-dc2c-4720-98bf-7fda5fc1dd71; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/kSJxEnuRvSVT3DnbnQnt1wGRsmI>
Subject: Re: [Dots] Yangdoctors early review of draft-ietf-dots-robust-blocks-01
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2022 06:25:17 -0000

SGkgTWljaGFsLCANCg0KTWFueSB0aGFua3MgZm9yIHRoZSByZXZpZXcuIA0KDQpXaWxsIEFDSyBp
dCBpbiB0aGUgbmV4dCB2ZXJzaW9uIG9mIHRoZSBkcmFmdC4NCg0KQ2hlZXJzLA0KTWVkDQoNCj4g
LS0tLS1NZXNzYWdlIGQnb3JpZ2luZS0tLS0tDQo+IERlwqA6IE1pY2hhbCBWYcWha28gdmlhIERh
dGF0cmFja2VyIDxub3JlcGx5QGlldGYub3JnPg0KPiBFbnZvecOpwqA6IGx1bmRpIDE3IGphbnZp
ZXIgMjAyMiAxNTo0Mg0KPiDDgMKgOiB5YW5nLWRvY3RvcnNAaWV0Zi5vcmcNCj4gQ2PCoDogZG90
c0BpZXRmLm9yZzsgZHJhZnQtaWV0Zi1kb3RzLXJvYnVzdC1ibG9ja3MuYWxsQGlldGYub3JnDQo+
IE9iamV0wqA6IFlhbmdkb2N0b3JzIGVhcmx5IHJldmlldyBvZiBkcmFmdC1pZXRmLWRvdHMtcm9i
dXN0LWJsb2Nrcy0wMQ0KPiANCj4gUmV2aWV3ZXI6IE1pY2hhbCBWYcWha28NCj4gUmV2aWV3IHJl
c3VsdDogUmVhZHkNCj4gDQo+IFRoZSBZQU5HIG1vZHVsZSBpcyBmYWlybHkgc2hvcnQgYW5kIHN0
cmFpZ2h0Zm9yd2FyZCBpbiBpdHMgY29udGVudCBidXQNCj4gdGhlcmUgaXMgYSBZQU5HIHN0cnVj
dHVyZS1hdWdtZW50IGV4dGVuc2lvbiB1c2VkIHdpdGggc2luZ2xlLWNhc2UgY2hvaWNlDQo+IHRo
YXQgaXMgcmVhZHkgZm9yIGZ1cnRoZXIgYXVnbWVudHMuIEJlY2F1c2Ugb2YgdGhhdCBJIGFtIHF1
aXRlIGNvbmZpZGVudA0KPiBpbiBzYXlpbmcgdGhhdCB0aGUgYXV0aG9ycyBhcmUgcHJvZmljaWVu
dCBpbiBZQU5HIGFuZCBJIGNvdWxkIG5vdCBmaW5kDQo+IGFueSBpc3N1ZXMgaW4gdGhlIG1vZHVs
ZSwgYW55d2F5Lg0KPiANCg0KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KCkNlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2lu
dGVzIHBldXZlbnQgY29udGVuaXIgZGVzIGluZm9ybWF0aW9ucyBjb25maWRlbnRpZWxsZXMgb3Ug
cHJpdmlsZWdpZWVzIGV0IG5lIGRvaXZlbnQgZG9uYwpwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9p
dGVzIG91IGNvcGllcyBzYW5zIGF1dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVz
c2FnZSBwYXIgZXJyZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxlcgphIGwnZXhwZWRpdGV1ciBldCBs
ZSBkZXRydWlyZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxl
Y3Ryb25pcXVlcyBldGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLApPcmFuZ2UgZGVjbGlu
ZSB0b3V0ZSByZXNwb25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3Jt
ZSBvdSBmYWxzaWZpZS4gTWVyY2kuCgpUaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBt
YXkgY29udGFpbiBjb25maWRlbnRpYWwgb3IgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiB0aGF0IG1h
eSBiZSBwcm90ZWN0ZWQgYnkgbGF3Owp0aGV5IHNob3VsZCBub3QgYmUgZGlzdHJpYnV0ZWQsIHVz
ZWQgb3IgY29waWVkIHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4KSWYgeW91IGhhdmUgcmVjZWl2ZWQg
dGhpcyBlbWFpbCBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUg
dGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMuCkFzIGVtYWlscyBtYXkgYmUgYWx0ZXJl
ZCwgT3JhbmdlIGlzIG5vdCBsaWFibGUgZm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1vZGlm
aWVkLCBjaGFuZ2VkIG9yIGZhbHNpZmllZC4KVGhhbmsgeW91LgoK


From nobody Tue Jan 18 02:06:19 2022
Return-Path: <daedulus@btconnect.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 840A63A15A3; Tue, 18 Jan 2022 02:06:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.415
X-Spam-Level: 
X-Spam-Status: No, score=-2.415 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.714, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=btconnect.onmicrosoft.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 WvObjbL5oKu1; Tue, 18 Jan 2022 02:06:12 -0800 (PST)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20105.outbound.protection.outlook.com [40.107.2.105]) (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 B78853A15A0; Tue, 18 Jan 2022 02:06:11 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KqojzPgLwfBg/Mx+mQ7xNvZYX5PrcPBd0lOR+Ln/OxMN/BSvKI79BUtP7F4GuWbRQxNuExqvtV2EpLBkBrHhh4D2LVQGddv2QELOSkKAmFv+oELKQPx5UrJPrxxIa7OMrjssU39Au+5I4cUZA5lz0YSugrgluoCP9frKV6PNGXxs3Vvm0dArDezKosx0LBAAiCfnq9L4RULFDLhUq3Q2TL1emVDpTrErUHGpqxboNaGxVfj4GkWlvQ+rSKeO0na2uBiv/CZkKsdfotM2/D1mOO9sVWNybbuT/H/Eo/8KaRX1H25B/pL3XySJglsNmUlVKs0VQDoqw/HWwl06Sxsnbg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=D50xwKXdDz2+AaDwb3cjB1oFWcbT1sAZr/bZX3ddYGo=; b=ITeb6dGJjyaVFb5XLITkXr+ASqqyYH8W9+vuIazQ/Gpdo2m+AURVshbrzDXI9MIN5EiUk6lFE5g20rSGOb+gSTB9irszVdJy1yjQ7DaeNOIcgAUs9Egx9nbfi08cVRCTm/3jvW2EzB+s0lGyW6RVwGW6t5FvIZBmXcxYvC9yWk/jKVoIhHVZ5UkJpKEl4iaWF0P6GX1WJ8XOtJ1/kJoq22qRv5PSFNB1/NOOXYynWcQ5zSDkdrx1AF1hX4lyYb1fd3l31pnpqIYz+7jSOL8T5FkUFGaMr1K09fA3ecCBgJbKWfxw0vHpI4gZN+1GOLgRjKpjaLXyckKWN7pb26YIaA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=D50xwKXdDz2+AaDwb3cjB1oFWcbT1sAZr/bZX3ddYGo=; b=tkTTeikdXQRxSPUqKqPiHh3r98MA78yLvwZKKJvSruoO/oR11qQvuG9xGSfbwda1QAMdSXAMAgJDOTrkSuAYl7mVz70VKmdXQmEvb4d5+TY8rA8xpqs+vfMddahnATj1qxojO6yh0u9xdnVoRm1y7S82kzOyVcWU3CuzM0GpTGw=
Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by AM0PR0702MB3777.eurprd07.prod.outlook.com (2603:10a6:208:1e::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4909.3; Tue, 18 Jan 2022 10:06:07 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::60fd:157e:c5e3:1a18]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::60fd:157e:c5e3:1a18%7]) with mapi id 15.20.4909.007; Tue, 18 Jan 2022 10:06:07 +0000
To: mohamed.boucadair@orange.com, "last-call@ietf.org" <last-call@ietf.org>
References: <164182513674.28016.284174261896096787@ietfa.amsl.com> <61E16D53.7050003@btconnect.com> <29779_1642412120_61E53858_29779_198_1_787AE7BB302AE849A7480A190F8B933035473D6C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Cc: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "valery@smyslov.net" <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry@ietf.org" <draft-ietf-dots-telemetry@ietf.org>
From: tom petch <daedulus@btconnect.com>
Message-ID: <61E69102.2090001@btconnect.com>
Date: Tue, 18 Jan 2022 10:05:54 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <29779_1642412120_61E53858_29779_198_1_787AE7BB302AE849A7480A190F8B933035473D6C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: LO2P265CA0355.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:d::31) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: d2f20a70-65b0-4ee3-50ab-08d9da6a24ca
X-MS-TrafficTypeDiagnostic: AM0PR0702MB3777:EE_
X-Microsoft-Antispam-PRVS: <AM0PR0702MB3777592E70749A9B4E6FB319C6589@AM0PR0702MB3777.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: UghlFRRSpx2sm1UzZHrEdUejM1Qp0edTCAGQ1uRiiaJSmCp5t9U6maDZ3cBVx7pB9oMGZEruP/YaHDzxrmJKtBZVh4xkhYL/n2d86IF7TWFn0nll/kK1DvW6bYENc96zClJHRz10R1bh0t4pOzG75e6qNRQtSXRDu3kr+i1FTeguzJL6qCnYFLirTYt5ueIe3dB8lzUnwNeTYl8F3vJ7tr/zKlEThILgWjHXt5PVxC+i1ZCYstwdIA7lJIrY4vvQ3LahzdNmWwufTwkO8/tJKVZ2cpD9lZaqzRfeTVgpiXWoQ9pch6dbwsnAlBAYAOr1k4untzGU3HPgsPlKBchgoId5nQVBGwvx/Qe5XEckfb2HjCBOfT9WRT9rgCaNMn/B0n9FPYEU5h+JIic8rXR1zZ3ZBMPhBdFtRs3dg73QlUcooJTLzr2b2oPZCciYXk1qr8PC2cYPzqhzkbiyKkeX3Hn4JpF7eet+2du1+BAhG70fdyBdagr0DFQRVau8ARk1u1R3reRcqelYLJHjR8JU0aRkATHwkpSSl3AaPE3Idzqt4hL/qU/gZtyu0gPwMML5QqSsErDu+7mwsgxS/fyLfChIuSMJLzT4NxnzJbSZm1KgQmDafQIt4KtUWq/Qa4qT07wYRBGmu7YmrKbmByActHHLxG/ctnHb8BUAwQMaSGoyB+GiCVYvs204E0M+I70dZWf1BbbXzM0VDNAs5Aj/sxeoANfXbbaYi42Rio9xb0kpUvTufxWuG5IHo6NlxGQ670BBKBcVvbsfueB1WXPKXA==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(13230001)(4636009)(366004)(186003)(5660300002)(2616005)(82960400001)(87266011)(26005)(508600001)(6486002)(33656002)(53546011)(86362001)(6666004)(6512007)(6506007)(2906002)(52116002)(38100700002)(38350700002)(4326008)(8676002)(316002)(66476007)(66556008)(66946007)(83380400001)(54906003)(6916009)(8936002)(36756003)(20210929001); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?Windows-1252?Q?XdQZZYYW2jv2KRGQJOLfJdYFD4CVtODaxY6HkRVgIIY0IdDRSzTHkSqu?= =?Windows-1252?Q?kOL8mPZ6QYoZbQ6lf2UTKGJma6j1CEJ8rxHNqZIHIhlHySBCqxIjzXFy?= =?Windows-1252?Q?fKXBOWUl3yI1fRSQ+hChtQY0Kwtvg/UR4VSPBIDc12d1k+hyC97S3YYf?= =?Windows-1252?Q?G6voauaj57Gz0weIogMPM7JuKMlXvWL0rwPVT/A020xNJL/fWpZAlzlQ?= =?Windows-1252?Q?HL5DaZ0VB4iwYvYduSZnYkk2PuzPhsKb5XSbVB31bsgE3aFEE64gtVtU?= =?Windows-1252?Q?HpTkWoxtbrW98PGBZAvTTVlvXeaxlncYieJ4byK3v6632moSlwLnRY4d?= =?Windows-1252?Q?dr82hDze3kC7nSIw7rrOkgLqu2JzETmrA7qHV1tHbVUjKe0FB9+LTUd1?= =?Windows-1252?Q?cFUkH6GrwX41+N4djz6wCnSbMp7i8hMrj7tP58O+mMcThviW5xrEtT/k?= =?Windows-1252?Q?7sun1F2l4b64N5A0d14mQU3eO8C1RyMne9KU1Lja7ueT9IL6vbIPzry7?= =?Windows-1252?Q?XYQkCDI5bUKnVRBW3c/rcznTCvZ7JwTMAfJCSbyiJC+CKskIoLrbQKHA?= =?Windows-1252?Q?ZBWaX5o+mbxUs9d3csv/GltWvf293EYUX+eemaee6RIE4zxfzv8bPn5c?= =?Windows-1252?Q?35E/rnacxoK4+6yy+XPfB6MIqMNJuIxV+xN9LTnyla1c1eYhxSayiLHk?= =?Windows-1252?Q?unl/9j7/1v9eTnEo4erWzt18ZcdR6zrO5DqBnzVZcm6IYleeIGLsHhRq?= =?Windows-1252?Q?DPhXO9MKIpnRiInghhL8fWzm+n6fNSVw5CGjEsZi1H6fKxmETWSkAsWJ?= =?Windows-1252?Q?iKMQ+fm84iiSt1zn0MYYmJu1f0GHv+/VioWnAjAhTCbJU5L+g+MJQIgo?= =?Windows-1252?Q?yFbcoZJmQURMHBh6PS66EEgtG2MRfGtuDgu73E5iU8joAER9fUSQI92k?= =?Windows-1252?Q?bTOGt1hZc8UyafFZsaqJEgR3twfoN5jKIzTy7gC0xHKxYYm5KhLBnH0r?= =?Windows-1252?Q?VoFmvB7/Medf8nmI/Y7zCzkm4HPxien5gHG9gPNGQl80WMdP7J8CQu0B?= =?Windows-1252?Q?HE8YEYKiM0PyKmt/mrUph0ODsuF95RzqazCevVEO9xXSSfSveGSh+58X?= =?Windows-1252?Q?oZbPAdHF1truDe9Ueib/6/9xwk706efXe0qcr/9+c3ZbSa8njLd8P7mQ?= =?Windows-1252?Q?2nqKF0ShCwy98ObYXD6cy14IHVbI2+8Ey7Q9MyDlhA3efq8R+aVf91kA?= =?Windows-1252?Q?8ow5Lr9TneXiwIXmWXUTHYu0vgw1w7NYVPh2A4S+JFOHgAuTGBK0rTN3?= =?Windows-1252?Q?zY88G9Npn+Kp4TJGfZwToViZ871fsXr20hprqNbVq4zdYPl2h49wXMj8?= =?Windows-1252?Q?uMNyZ0cYBqLW89ylSbcABu7PVdIZFgaxo9otCaHtQUrD9yVRPWgzhHrw?= =?Windows-1252?Q?z5CPEE6dJKp5gLHPd1d2O8aVVKf3FFE+LoHnUARwMpYJ2SSaCCRtmoFv?= =?Windows-1252?Q?SQ5ShnLfCz5RuX8LKax2tyNC0z4WTuoywnJiMU9/3FCTA5lEFwTfcTOp?= =?Windows-1252?Q?wLFvoY1cMQS1ZuBGsC+ykNp4FA+5DLHW6JQjx5HbLOWJWiTo4w0OBlrJ?= =?Windows-1252?Q?UB+/SVILp0Y7wQFCPK55X1PAeVoLz+AatMnqZARyiHRmyaGr3Pj9WM7l?= =?Windows-1252?Q?LznvGos1HbiHPp1H03P5lIP5HmpM+0GldMEgwHODIZBIqVuzYL25DjJA?= =?Windows-1252?Q?A0RFcZ592U0N2/ZTQXI=3D?=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d2f20a70-65b0-4ee3-50ab-08d9da6a24ca
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 Jan 2022 10:06:07.4668 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 1mj9JKqWmOIRR2GRrdsJ1DAkwInmCGH1ZO4tUKqb8iNSERaBDSiZEOLFynSD6cpoSQRE2zXuqw8YiJzPOjG+cw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR0702MB3777
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/NR4XYGHxuo9t4GCh8WpZfFh5OuM>
Subject: Re: [Dots] Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2022 10:06:18 -0000

<inline excising the agreed ones>

On 17/01/2022 09:35, mohamed.boucadair@orange.com wrote:
> Hi Tom,
>
> Thank you for the review. Much appreciated.
>
> Please see inline.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : tom petch <daedulus@btconnect.com>
>> Envoyé : vendredi 14 janvier 2022 13:32
>>
>> Some stray thoughts
>>
>> I wonder if there is a recognised terminology for attacks, threats and
>> such-like.  I have been looking at I2NSF I-D recently and they are,
>> well, different.  I note too that secdir reviews thereof queried some of
>> the I2NSF terminology but what is right and what is wrong?.  I am
>> reminded of the efforts to produce a second version of the Security
>> Glossary some time ago.
>
> [Med] You may look at RFC4949, but that document requires a refresh. For the particular DoS case, RFC4732 is still a good reading reference.


Yes. When RFC4949 was an I-D I quoted from it and got an off-list 
comment from an AD that that I-D was controversial and at least some AD 
thought it should not be published.  RFC2828 is fine, if dated, RFC4949 
not, so I do not refer to it.

>>
>> I find the use of -g and -ps alien.  I worked out what they mean but
>> cannot help feeling that there is a clearer way to express this, such as
>> pps, bps, Bps (YANG does not like capitalisation but does allow it where
>> it is widely recognised, which, for me, Bps is).
>
> [Med] *-g is used to identify nodes of gauge type while *-ps identifies nodes that are expressed as a value "per second". We don't include the reasoning of the naming convention as what matters is the description of the attributes, not their names. We can add a note if you think this is helpful.


Well yes, I worked that out but I still find those suffix jarring. I 
think that the concept of gauge is not well known so the -g will not be 
obvious and ps is much used for 'post scriptum'!

>> "The DOTS telemetry module (Section 10.1) uses "enumerations" rather
>>      than "identities" to define units, samples, and intervals because
>>      otherwise the namespace identifier "ietf-dots-telemetry" must be
>>      included when a telemetry attribute is included "
>> Well yes but that is saying the ietf-dots-telemetry is a bad choice of
>> prefix - the 'ietf' is redundant and the 'telemetry' is prolix
>
> [Med] We could shorten the prefix but the issue is still there:  have to include a prefix.

Depends what the default is, at least with XML.  This came up recently 
with I2NSF where I sought and got clarification on the NETMOD list that 
most of the prefix in the examples were not needed.  I don't know how 
well this fits with CoAP.

>> The user has to understand that [Enterprise-Numbers] is the same as
>> Private Enterprise Numbers", which may not be apparent; consistent
>> terminology is good.
>
> [Med] Not sure a (which) change is needed. The current text says:

In most walks of life, if you have a registry and a private registry, 
then users will assume that the registry is public and the private 
registry is private and that there are two separate registries.  Here 
there is just the one and the correct name is 'Private Enterprise 
Number' sometimes abbreviated to PEN.  Experts will know that there is 
no Public Enterprise Number, others will not so I think we should use 
Private Enterprise Number in all cases and not just Enterprise Number.

>     vendor-id:  Vendor ID is a security vendor's Enterprise Number as
>        registered with IANA [Enterprise-Numbers].
>
> with:
>
>     [Enterprise-Numbers]
>                "Private Enterprise Numbers", 4 May 2020,
>                <http://www.iana.org/assignments/enterprise-numbers.html>.
>
>>
>> Authors vary between the frontispiece,
>
> [Med] That is not an issue.
>
>   the YANG modules and Authors'
>> Addresses
>
> [Med] Fixed Tiru's address. Thanks.

Well the YANG has 'Author: Konda ...' and it is not immediately obvious 
whioh that is.  I like consistency  although I recognise that I18N can 
make that awkward.


>>       reference
>>         "IANA: Private Enterprise Numbers"; would be clearer with a URI,
>> whereever it occurs which is in more than one place
>>
>
> [Med] Will leave this one for the RFC editor.

Tom Petch

>> Tom Petch
>>
>>
>>
>>
>>
>> On 10/01/2022 14:32, The IESG wrote:
>>>
>>> The IESG has received a request from the DDoS Open Threat Signaling WG
>>> (dots) to consider the following document: - 'Distributed
>>> Denial-of-Service Open Threat Signaling (DOTS) Telemetry'
>>>     <draft-ietf-dots-telemetry-19.txt> as Proposed Standard
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> last-call@ietf.org mailing lists by 2022-01-24. Exceptionally,
>>> comments may be sent to iesg@ietf.org instead. In either case, please
>>> retain the beginning of the Subject line to allow automated sorting.
>>>


From nobody Tue Jan 18 05:05:26 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E16B3A10A9; Tue, 18 Jan 2022 05:05:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 xT54jfCArMtd; Tue, 18 Jan 2022 05:05:14 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (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 956A03A10AC; Tue, 18 Jan 2022 05:05:14 -0800 (PST)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar26.francetelecom.fr (ESMTP service) with ESMTPS id 4JdTX84cXszFqLq;  Tue, 18 Jan 2022 14:05:12 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1642511112; bh=RJQkvYebmi6hZz0YsXpDYlBWp6EaqoLB/XkshoiYtuo=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=xn3pYYtPUbsVIjD3XNyzZiH2MoNxV0tOJ6s47Ets/RCcQ3/Ywrdtxm2qX4hO2YfHV /pFME1wfO/ULV2xH1EKmvlnNi+N1UMaOZVrz4l7L8fHt6ABB+oqt+jt6KXhnoSyCzz shKPdT8hrsNRQcG/y5mJWRGnp4t8Xn+JZK5kpzhaRUE/se+tP1ihqfSA2Plw79+IuO XE2+ThJmGrL8y/DEMKL8KUlOVmZdkDPyYdeRVxYS7LBbRhfIQIUia9lK3Z3ytNYH8G Ws8TGx+i+zKtctTpx76AWJgwGcT7ZsrP+juMC7AT+vqYV0+Y6AgqZxPHx9BYV5UwR5 5Fui2o35RJZew==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar02.francetelecom.fr (ESMTP service) with ESMTPS id 4JdTX82PpCzCqlT;  Tue, 18 Jan 2022 14:05:12 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: tom petch <daedulus@btconnect.com>, "last-call@ietf.org" <last-call@ietf.org>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "valery@smyslov.net" <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry@ietf.org" <draft-ietf-dots-telemetry@ietf.org>
Thread-Topic: Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
Thread-Index: AQHYDFMLXrYMRGp9wEy3KmCDNRZeb6xovA6Q
Content-Class: 
Date: Tue, 18 Jan 2022 13:05:11 +0000
Message-ID: <20948_1642511112_61E6BB08_20948_182_3_787AE7BB302AE849A7480A190F8B93303547FCE0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164182513674.28016.284174261896096787@ietfa.amsl.com> <61E16D53.7050003@btconnect.com> <29779_1642412120_61E53858_29779_198_1_787AE7BB302AE849A7480A190F8B933035473D6C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <61E69102.2090001@btconnect.com>
In-Reply-To: <61E69102.2090001@btconnect.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-18T13:01:33Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=333549b6-2212-40f0-b912-39dc249febd5; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/t2r5QPMDZRorCwWLEdGZGvoF_KU>
Subject: Re: [Dots] Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2022 13:05:20 -0000

Hi Tom,=20

Thank you for the follow-up.=20

Please see inline for two proposed changes.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: tom petch <daedulus@btconnect.com>
> Envoy=E9=A0: mardi 18 janvier 2022 11:06
> =C0=A0: BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>; last-
> call@ietf.org
> Cc=A0: dots-chairs@ietf.org; valery@smyslov.net; dots@ietf.org; draft-
> ietf-dots-telemetry@ietf.org
> Objet=A0: Re: Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed
> Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed
> Standard
>=20
> <inline excising the agreed ones>
>=20
> On 17/01/2022 09:35, mohamed.boucadair@orange.com wrote:
> > Hi Tom,
> >
> > Thank you for the review. Much appreciated.
> >
> > Please see inline.
> >
> > Cheers,
> > Med
> >
> >> -----Message d'origine-----
> >> De : tom petch <daedulus@btconnect.com> Envoy=E9 : vendredi 14 janvier
> >> 2022 13:32
> >>
> >> Some stray thoughts
> >>
...
>=20
> >>
> >> I find the use of -g and -ps alien.  I worked out what they mean but
> >> cannot help feeling that there is a clearer way to express this, such
> as
> >> pps, bps, Bps (YANG does not like capitalisation but does allow it
> where
> >> it is widely recognised, which, for me, Bps is).
> >
> > [Med] *-g is used to identify nodes of gauge type while *-ps
> identifies nodes that are expressed as a value "per second". We don't
> include the reasoning of the naming convention as what matters is the
> description of the attributes, not their names. We can add a note if you
> think this is helpful.
>=20
>=20
> Well yes, I worked that out but I still find those suffix jarring. I
> think that the concept of gauge is not well known so the -g will not be
> obvious and ps is much used for 'post scriptum'!
>=20

[Med] OK. Added this NEW text:=20

   Some parameters (e.g., low percentile values) may be associated with
   different YANG types (e.g., decimal64 and yang:gauge64).  To easily
   distinguish the types of these parameters while using meaningful
   names, the following suffixes are used:

               +--------+--------------+------------------+
               | Suffix | YANG Type    | Example          |
               +--------+--------------+------------------+
               | -g     | yang:gauge64 | low-percentile-g |
               | -c     | container    | connection-c     |
               | -ps    | per second   | connection-ps    |
               +--------+--------------+------------------+


...
>=20
> >> The user has to understand that [Enterprise-Numbers] is the same as
> >> Private Enterprise Numbers", which may not be apparent; consistent
> >> terminology is good.
> >
> > [Med] Not sure a (which) change is needed. The current text says:
>=20
> In most walks of life, if you have a registry and a private registry,
> then users will assume that the registry is public and the private
> registry is private and that there are two separate registries.  Here
> there is just the one and the correct name is 'Private Enterprise
> Number' sometimes abbreviated to PEN.  Experts will know that there is
> no Public Enterprise Number, others will not so I think we should use
> Private Enterprise Number in all cases and not just Enterprise Number.
>=20

[Med] Went with the following change:

OLD:

> >     vendor-id:  Vendor ID is a security vendor's Enterprise Number as
> >        registered with IANA [Enterprise-Numbers].
> >

NEW:
   vendor-id:  Vendor ID is a security vendor's enterprise number as
      registered in the IANA's "Private Enterprise Numbers" registry
      [Enterprise-Numbers].

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Wed Jan 19 04:35:07 2022
Return-Path: <daedulus@btconnect.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE65C3A1BAF; Wed, 19 Jan 2022 04:35:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.415
X-Spam-Level: 
X-Spam-Status: No, score=-2.415 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.714, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=btconnect.onmicrosoft.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 DA_kjo2TFeCv; Wed, 19 Jan 2022 04:35:01 -0800 (PST)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60121.outbound.protection.outlook.com [40.107.6.121]) (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 9192B3A1BB0; Wed, 19 Jan 2022 04:34:59 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jXkeXR2uHtGoBZxPn34DqK8XV/WI1yaI4jZ2zQ8GV+718+a/jNaEZd4VzzG30ZEwCo6ZJZQmgg/Yfzf68UhbjVbbuKvxP/o0AkOwJU/Rh2npQRr2KjZuNghy+gihsJcrnb7r+yFy1qgbVy3tnVr7ac/6w9qCf6jt1WBtFvnZzsyaV52ZUH2TVWJZnMo7FLOy8P5W2bi0W9LlXFria/z8V978pwMz2lvdUMXALBkJpKD1u2un8QM3HJKHVCUVyYB2yeFrTr4kDpu10NHZbubBavEzNh/GSMFk622DC2wZDcQjld2e5tk0m0fT0gcxLKdvSMVPQ+j0+RqEM28HB328fw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=055fuPqzFQov7YmAN3AHKSnBWFcJ438iNgFurCW48Go=; b=SZL8SBsZn0f7e0EZ2ypVdyzXVa/jMkqyuqKzwzQK9fyGSoDcnM6XVHmVqvMXt9KtZKsttx/0orCM5VWgFGPeC1Ar7kKcvNLxRyxFez9HYyvY6LnI2SjtqlyQ8PATu1F1k27jnRrOR9qf8VzmcjDoWGb68lEIiQdVwGty3rhCsi0CLWKhNgKyeW4eOsoMffUcRjEdciXFsGgUVEFMiC1FZOEUUXNnsnile+KZEVhOojTdub1A53IUCvZoGbPD9a5lJWTWpHEgcxIhBmsNK3/l/pyhfK6YmGfjxCYY58DlMvfVrw4Pzbpq+nVe7CMES5/DIxWfk+z4slC7LaRzK3XD9g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=055fuPqzFQov7YmAN3AHKSnBWFcJ438iNgFurCW48Go=; b=Eb/hUWCWiwTP04r8TbqIZ4Pl0auNVRA25DgU040Tp0Zb6FJNi4v0dLi0961Rm2pFExYjx2RsnxjgQZaetPNoA6a/QX8iLDUkGJOzShecl5uZwALy0GD9K325t6Q29QWxiUWwKJlSGTAnMyfZEjATxoeZE1siwfyBxF4wyPmA+RE=
Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by AM6PR07MB4117.eurprd07.prod.outlook.com (2603:10a6:209:34::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4930.4; Wed, 19 Jan 2022 12:34:54 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::60fd:157e:c5e3:1a18]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::60fd:157e:c5e3:1a18%7]) with mapi id 15.20.4909.008; Wed, 19 Jan 2022 12:34:54 +0000
To: mohamed.boucadair@orange.com, "last-call@ietf.org" <last-call@ietf.org>
References: <164182513674.28016.284174261896096787@ietfa.amsl.com> <61E16D53.7050003@btconnect.com> <29779_1642412120_61E53858_29779_198_1_787AE7BB302AE849A7480A190F8B933035473D6C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <61E69102.2090001@btconnect.com> <20948_1642511112_61E6BB08_20948_182_3_787AE7BB302AE849A7480A190F8B93303547FCE0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Cc: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "valery@smyslov.net" <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry@ietf.org" <draft-ietf-dots-telemetry@ietf.org>
From: tom petch <daedulus@btconnect.com>
Message-ID: <61E80563.5090304@btconnect.com>
Date: Wed, 19 Jan 2022 12:34:43 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <20948_1642511112_61E6BB08_20948_182_3_787AE7BB302AE849A7480A190F8B93303547FCE0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: LO4P123CA0316.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:197::15) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: d2dcff66-e911-45f1-6d9a-08d9db481887
X-MS-TrafficTypeDiagnostic: AM6PR07MB4117:EE_
X-Microsoft-Antispam-PRVS: <AM6PR07MB4117567263D418DA8BF87E36C6599@AM6PR07MB4117.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: cnhD5WbMourUr+X9v6X4hX3SznqJlAAvUVdF8LZ1F1pKe3J6AFJW3xMliy4ol6QWd1if9Fyd2gwKhcfBlwPie9tFko6lcpTsV7LwK1nEIKPxiVPj0FeTi2x1YQB/TJR2ss5qIgbldsI59nNO2Loc3DboOM8ciOz3xc07aIvj8c7Kf3fLZJn4tr/e/H+OnwTxtpPrGfIz9UZc5/2yVYuM781LZ55b7oiWIt0ypLidsm8Yrfmro6NUcLfiJpfwUJrz80OO4Cn2Qys89vHLePSusL+0OOatt99WLQydWYpfVar2mbeFI64ipmKu9rvS4ql1OzZWVI/8kcWGZ3HcN1z+HD6UWpBwD+wjQ8+cHpUQewncpLZdD83HeUbRUUbLDDP7dEvJK24V+nJ4M5W8rqVQUd6xS5LHNp4mPDilR1IipsRaWXN+5pL2BHnS/9cyvA4pXcv+REyBb3pXGJ+rSF4c4lYamncTMBg5YdXzmFHXw8yC/7zo7dPpPD8ZfJTiCfciZCuzx7+mLCwtFXylZdueu0QFh4d9tNn0q64o11/iOR0CYhS9lOuRcjrT7Wx/hoNqoEzyWsB9af23R8GUhHamD1DBjN5Yp7dFxDhOHHWk1+TjGlMs4D0LRvop6H8FU5gZTEVdeKRYF+8fQgfh3UD70gd7MGHqQ/YhjEQiJISD9H32egdy2WXBV6Mp5QjtXThmC/kzhzuLtHsw+QCocit42A==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(13230001)(4636009)(366004)(86362001)(2906002)(38350700002)(38100700002)(36756003)(82960400001)(5660300002)(6512007)(6506007)(53546011)(52116002)(8676002)(83380400001)(66946007)(8936002)(33656002)(87266011)(66556008)(508600001)(6486002)(66476007)(4326008)(2616005)(54906003)(6666004)(6916009)(316002)(26005)(186003)(20210929001); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?Windows-1252?Q?MKySqvtDCEm8sPsqFdWwMnvz0Od12Z/yVvz8unD3oQe/iVn2JAXvcktS?= =?Windows-1252?Q?jwJlPx9BukFfvEc2619+zuliHIcoI+7Zxa0MiyhnYutxaNmxuW/RBRoL?= =?Windows-1252?Q?LORJeFaAjnBlBdPtbBHQ8l0LWLvssZ2qZezp0D+ZZDW9S55fCGf+kFAf?= =?Windows-1252?Q?Ege5B9muo5XC0x1mwtjO35jsl2345+JaVK7iEz+DGvlDqnb8o5NdIbUc?= =?Windows-1252?Q?Fb6adQrFv3CzwTd1IGqhKxat5clwyN6chu4/8lkzqMQ/oxtE8ns6ygPu?= =?Windows-1252?Q?Y3R+tdglTEz1eoUOMAUzpfVEqNDo3wREwJCLiFesap2kQH5jypQK7ztw?= =?Windows-1252?Q?5oLtbJG13n9yI0mCituuKsSJ31jlq3a0rXl5ndpf9kmIJGjvME9ivPUo?= =?Windows-1252?Q?eDlyRAir8ZL7QZ31Go9rWilNMQf/SfjzasnCw1A9X5r8ejO8SRWgXF7q?= =?Windows-1252?Q?3ESg8ztYJbzPQx1Fq9jRrXwXHv8FsJoDRBY5V9dRV1JPHbJRaGMlfXuP?= =?Windows-1252?Q?eRQu7Aq/vGux3eHvK6fD0nsCJ2tsi4sugVT8sFQHPQ55Tiw3axP7GR/n?= =?Windows-1252?Q?761aoqtcaszw8+2bBcNd7VANbsHYhbcZppLFYLYlUwuQ7qqN06Pu85aA?= =?Windows-1252?Q?aj8FZbUL/VjUGkQPne1SxdVyQqtPAglAPsIikwPLk++yKJtTNzTei/gQ?= =?Windows-1252?Q?r9I9Q7CVohrHw03Z2PkYngz4b8ggLBdKrZwCqD6xRbXADgoE2SaDQ3zV?= =?Windows-1252?Q?pIU9F6ZeGYJ/r5yNt4P9FWHtF0PDj+VvKD06+K7LDF5rHPvESPSc6D6+?= =?Windows-1252?Q?R0jT7fMxBgrma1Sp3oOvVkb/R3DX25T69HKjB9GcsNRsKeHqATxSNCw5?= =?Windows-1252?Q?UGxy2T1vzoEiAPxKmdDNKPFeFCfdTX/CDquHK8EKUvFz6eHNjt4fT+ii?= =?Windows-1252?Q?0jEjOKe3W9po0m3jLo755Onc63z9J/KiE9jWIWZY9eK3eypBR8j7dxZO?= =?Windows-1252?Q?PBH86jLijzKfpLPY+G0qV7JzJTw4No8K1x1jHpByzgjBdAwvujfkTCIg?= =?Windows-1252?Q?vHZA/dDatKGv6PTXUUhE8u+7DFn4tUgooUoVk+YuZRpfcchJf+k8ZFrk?= =?Windows-1252?Q?aApfo3o3GtNUgtDAq0j/IwthcJICC6IUWC2x0rXw1sKA4JjFAlfZfvRo?= =?Windows-1252?Q?VK8KhxsCGs/NAXDmIrayniPupZdnWzkKrmlG8UymWQ6kjhZVywuKW6sL?= =?Windows-1252?Q?TbiTOxdh/dxCwiRliv7KcLB2e141AjRGFjJbbQ4DAb2NMGFdlxoStGSb?= =?Windows-1252?Q?NtgiwYXnxNDKNemMAvZm4Qc97q0uuzPGRuO54Q8I9/rrmq8P3Fmd2++r?= =?Windows-1252?Q?Yf7b4rDt8XQAR/Qu7HvMpaYkhswiXao0FWk0lpz1HdRCrYwWcyKcTYIv?= =?Windows-1252?Q?DFzQB+MtuBnDidCLFabeqMfoWLVUDboLI3RleCQKvzmhQs/R0G3HguzP?= =?Windows-1252?Q?7QK2/RjTcQcEIzkmpmFdSfh+SQmnBQFUBh5dBdw4x7AMmb0dOkFRZhUU?= =?Windows-1252?Q?CJ6sb4dEA0OeltOU8/HCujPadbPgJG8SLZPYepIlf74f7v18P5oCqXi9?= =?Windows-1252?Q?gXNwExBmhoCwJhaeEODef79iO6n9S3m2mzyi6CE7OEnk8cmX4Jb9dbTz?= =?Windows-1252?Q?epoEgXqivncFJfY+VxyG2Rwt3GZPk77/2SpMRXz1ugM3sqi+Wa73k/Cs?= =?Windows-1252?Q?yBD7tljMytWqRhE+9H8=3D?=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d2dcff66-e911-45f1-6d9a-08d9db481887
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 Jan 2022 12:34:54.8260 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: ukFFu+OHIy7yaO7aUTuS0ISNFYYV8wfCgHn6aOSAp4CoqizW7o2O9VLvhEpp/Oqse2ZggucPcXpRuhmIBFxvtQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR07MB4117
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/KNny0urTmAYquYKQLP1XkzI7VOo>
Subject: Re: [Dots] Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jan 2022 12:35:06 -0000

On 18/01/2022 13:05, mohamed.boucadair@orange.com wrote:
> Hi Tom,
>
> Thank you for the follow-up.
>
> Please see inline for two proposed changes.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : tom petch <daedulus@btconnect.com>
>> Envoyé : mardi 18 janvier 2022 11:06
>>
>> <inline excising the agreed ones>
>>
>> On 17/01/2022 09:35, mohamed.boucadair@orange.com wrote:
>>> Hi Tom,
>>>
>>> Thank you for the review. Much appreciated.
>>>
>>> Please see inline.
>>>
>>> Cheers,
>>> Med
>>>
>>>> -----Message d'origine-----
>>>> De : tom petch <daedulus@btconnect.com> Envoyé : vendredi 14 janvier
>>>> 2022 13:32
>>>>
>>>> Some stray thoughts
>>>>
> ...
>>
>>>>
>>>> I find the use of -g and -ps alien.  I worked out what they mean but
>>>> cannot help feeling that there is a clearer way to express this, such
>> as
>>>> pps, bps, Bps (YANG does not like capitalisation but does allow it
>> where
>>>> it is widely recognised, which, for me, Bps is).
>>>
>>> [Med] *-g is used to identify nodes of gauge type while *-ps
>> identifies nodes that are expressed as a value "per second". We don't
>> include the reasoning of the naming convention as what matters is the
>> description of the attributes, not their names. We can add a note if you
>> think this is helpful.
>>
>>
>> Well yes, I worked that out but I still find those suffix jarring. I
>> think that the concept of gauge is not well known so the -g will not be
>> obvious and ps is much used for 'post scriptum'!
>>
>
> [Med] OK. Added this NEW text:
>
>     Some parameters (e.g., low percentile values) may be associated with
>     different YANG types (e.g., decimal64 and yang:gauge64).  To easily
>     distinguish the types of these parameters while using meaningful
>     names, the following suffixes are used:
>
>                 +--------+--------------+------------------+
>                 | Suffix | YANG Type    | Example          |
>                 +--------+--------------+------------------+
>                 | -g     | yang:gauge64 | low-percentile-g |
>                 | -c     | container    | connection-c     |
>                 | -ps    | per second   | connection-ps    |
>                 +--------+--------------+------------------+
>
  ok, reluctantly

>
> ...
>>
>>>> The user has to understand that [Enterprise-Numbers] is the same as
>>>> Private Enterprise Numbers", which may not be apparent; consistent
>>>> terminology is good.
>>>
>>> [Med] Not sure a (which) change is needed. The current text says:
>>
>> In most walks of life, if you have a registry and a private registry,
>> then users will assume that the registry is public and the private
>> registry is private and that there are two separate registries.  Here
>> there is just the one and the correct name is 'Private Enterprise
>> Number' sometimes abbreviated to PEN.  Experts will know that there is
>> no Public Enterprise Number, others will not so I think we should use
>> Private Enterprise Number in all cases and not just Enterprise Number.
>>
>
> [Med] Went with the following change:
>
> OLD:
>
>>>      vendor-id:  Vendor ID is a security vendor's Enterprise Number as
>>>         registered with IANA [Enterprise-Numbers].
>>>
>
> NEW:
>     vendor-id:  Vendor ID is a security vendor's enterprise number as
>        registered in the IANA's "Private Enterprise Numbers" registry
>        [Enterprise-Numbers].


You have still got half a dozen or so uses of 'Enterprise Number' in the 
I-D and my preference would be to change them all to 'Private Enterprise 
Number'!  As I said before, an expert knows that there is no Public 
Enterprise Number, others do not.

Tom Petch

>
> _____________________________________


From nobody Wed Jan 19 04:56:59 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 883733A1C6D; Wed, 19 Jan 2022 04:56:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 vrQg6B1BlT3u; Wed, 19 Jan 2022 04:56:47 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (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 7D13C3A1C6B; Wed, 19 Jan 2022 04:56:47 -0800 (PST)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr23.francetelecom.fr (ESMTP service) with ESMTPS id 4Jf5Hx0FYZz5vyX;  Wed, 19 Jan 2022 13:56:45 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1642597005; bh=LsLIFBRQC/v8kVNvpemzDTe2ZSfXacjpNGwg7QJuX40=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=A56FnB0yOB3qqYUYAlqAaHHd1SNxqzkYWiqFkHIzJNX82jwp0UR6sJNyQsLqpBTXh EGQPby+7zP9r/VTkYhXYDTYG0SFr4KolZQMbEixFJit011xYHUg9SBJ0n2RkcNlNlf Gr2WuVyeGhg7Z+8GDxOu9UHZ/IubL3CL16bOJfCV3Iu4NNALSqkf3dG5Pr5hiGIECS zpulEDgQEYK69o6Yo5mpass3kdtj/GFFUj+HPSAY+zK50R6mtP2PTuo9Ab4NFzAKfN JNe/Ss4hWjKFBY5Ioi2OggXREnm0V3ty0zaR6IC8A7ffoDXKQqYt48RkUDfciaX+mp Y1BsiZP+2JAjw==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr02.francetelecom.fr (ESMTP service) with ESMTPS id 4Jf5Hw6Sffz8sYL;  Wed, 19 Jan 2022 13:56:44 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: tom petch <daedulus@btconnect.com>, "last-call@ietf.org" <last-call@ietf.org>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "valery@smyslov.net" <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry@ietf.org" <draft-ietf-dots-telemetry@ietf.org>
Thread-Topic: Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
Thread-Index: AQHYDTD3OGHGRra4k0i4XNwKO9WkvqxqSIOA
Content-Class: 
Date: Wed, 19 Jan 2022 12:56:43 +0000
Message-ID: <16719_1642597004_61E80A8C_16719_95_2_787AE7BB302AE849A7480A190F8B9330354837BA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164182513674.28016.284174261896096787@ietfa.amsl.com> <61E16D53.7050003@btconnect.com> <29779_1642412120_61E53858_29779_198_1_787AE7BB302AE849A7480A190F8B933035473D6C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <61E69102.2090001@btconnect.com> <20948_1642511112_61E6BB08_20948_182_3_787AE7BB302AE849A7480A190F8B93303547FCE0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <61E80563.5090304@btconnect.com>
In-Reply-To: <61E80563.5090304@btconnect.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-19T12:55:27Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=df13f9e1-cd75-4850-b807-4f29afad7ecd; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/ADGVnZbtJcdgl0JxkfmC9OeoTTM>
Subject: Re: [Dots] Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jan 2022 12:56:53 -0000

Hi Tom,=20

Thank you for checking the changes and sharing your feedback.=20

Please see inline.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: tom petch <daedulus@btconnect.com>
> Envoy=E9=A0: mercredi 19 janvier 2022 13:35
> =C0=A0: BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>; last-
> call@ietf.org
> Cc=A0: dots-chairs@ietf.org; valery@smyslov.net; dots@ietf.org; draft-
> ietf-dots-telemetry@ietf.org
> Objet=A0: Re: Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed
> Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed
> Standard
>=20
...
> > ...
> >>
> >>>> The user has to understand that [Enterprise-Numbers] is the same as
> >>>> Private Enterprise Numbers", which may not be apparent; consistent
> >>>> terminology is good.
> >>>
> >>> [Med] Not sure a (which) change is needed. The current text says:
> >>
> >> In most walks of life, if you have a registry and a private registry,
> >> then users will assume that the registry is public and the private
> >> registry is private and that there are two separate registries.  Here
> >> there is just the one and the correct name is 'Private Enterprise
> >> Number' sometimes abbreviated to PEN.  Experts will know that there
> >> is no Public Enterprise Number, others will not so I think we should
> >> use Private Enterprise Number in all cases and not just Enterprise
> Number.
> >>
> >
> > [Med] Went with the following change:
> >
> > OLD:
> >
> >>>      vendor-id:  Vendor ID is a security vendor's Enterprise Number
> as
> >>>         registered with IANA [Enterprise-Numbers].
> >>>
> >
> > NEW:
> >     vendor-id:  Vendor ID is a security vendor's enterprise number as
> >        registered in the IANA's "Private Enterprise Numbers" registry
> >        [Enterprise-Numbers].
>=20
>=20
> You have still got half a dozen or so uses of 'Enterprise Number' in the
> I-D and my preference would be to change them all to 'Private Enterprise
> Number'!

[Med] No change is made for the other occurrences on purpose. For example,=
=20=20

   The examples use the Enterprise Number 32473 defined for
   documentation use [RFC5612].

no change is made to that text because we want to be consistent with existi=
ng RFC5612 which says the following:=20=20

   IANA has updated the registration for Enterprise Number 32473 to
   point to this RFC.

  As I said before, an expert knows that there is no Public
> Enterprise Number, others do not.
>=20

[Med] Added this new entry to the terminology section:

NEW:
   The document uses IANA-assigned Enterprise Numbers.  These numbers
   are also known as "Private Enterprise Numbers" and "SMI (Structure of
   Management Information) Network Management Private Enterprise Codes"
   [Enterprise-Numbers].

Better?

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Wed Jan 19 14:40:09 2022
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CFA13A1FB9; Wed, 19 Jan 2022 14:39:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80A-QYyaRW58; Wed, 19 Jan 2022 14:39:52 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74D0A3A1FB5; Wed, 19 Jan 2022 14:39:52 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 471F8EB6BE; Wed, 19 Jan 2022 14:39:52 -0800 (PST)
To: mohamed.boucadair@orange.com, mohamed.boucadair@orange.com, kondtir@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rdd@cert.org, iesg@ietf.org, dots@ietf.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20220119223952.471F8EB6BE@rfc-editor.org>
Date: Wed, 19 Jan 2022 14:39:52 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/gO1nRRkfNz3B92mQUVMKn9E09aI>
Subject: [Dots] [Errata Verified] RFC8783 (6496)
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jan 2022 22:39:57 -0000

The following errata report has been verified for RFC8783,
"Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6496

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Mohamed Boucadair <mohamed.boucadair@orange.com>
Date Reported: 2021-03-26
Verified by: Roman Danyliw (IESG)

Section: 7.3

Original Text
-------------
   A DOTS client can also issue a GET request with a "content" query
   parameter set to 'non-config' to exclusively retrieve non-
   configuration data bound to a given ACL as shown in Figure 30.  A
   response to this GET request is shown in Figure 31.

     GET /restconf/data/ietf-dots-data-channel:dots-data\
         /dots-client=paL8p4Zqo4SLv64TLPXrxA/acls\
         /acl=test-acl-ipv6-udp?content=non-config HTTP/1.1
     Host: example.com
     Accept: application/yang-data+json

Corrected Text
--------------
   A DOTS client can also issue a GET request with a "content" query
   parameter set to 'nonconfig' to exclusively retrieve non-
   configuration data bound to a given ACL as shown in Figure 30.  A
   response to this GET request is shown in Figure 31.

     GET /restconf/data/ietf-dots-data-channel:dots-data\
         /dots-client=paL8p4Zqo4SLv64TLPXrxA/acls\
         /acl=test-acl-ipv6-udp?content=nonconfig HTTP/1.1
     Host: example.com
     Accept: application/yang-data+json

Notes
-----
RFC8040 defines this value for the "content" Query Parameter (RFC 4.8.1):

    | nonconfig | Return only non-configuration descendant data nodes |

--------------------------------------
RFC8783 (draft-ietf-dots-data-channel-31)
--------------------------------------
Title               : Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification
Publication Date    : May 2020
Author(s)           : M. Boucadair, Ed., T. Reddy.K, Ed.
Category            : PROPOSED STANDARD
Source              : DDoS Open Threat Signaling
Area                : Security
Stream              : IETF
Verifying Party     : IESG


From nobody Thu Jan 20 00:53:10 2022
Return-Path: <chenmeiling@chinamobile.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13BE33A127B; Thu, 20 Jan 2022 00:53:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=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 FM7UKCC0Emo5; Thu, 20 Jan 2022 00:53:04 -0800 (PST)
Received: from cmccmta2.chinamobile.com (cmccmta2.chinamobile.com [221.176.66.80]) by ietfa.amsl.com (Postfix) with ESMTP id 871333A1296; Thu, 20 Jan 2022 00:53:01 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.19]) by rmmx-syy-dmz-app05-12005 (RichMail) with SMTP id 2ee561e922ec220-1ebfa; Thu, 20 Jan 2022 16:53:00 +0800 (CST)
X-RM-TRANSID: 2ee561e922ec220-1ebfa
X-RM-TagInfo: emlType=0                                       
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[10.2.51.26]) by rmsmtp-syy-appsvr10-12010 (RichMail) with SMTP id 2eea61e922ebde6-e707b; Thu, 20 Jan 2022 16:53:00 +0800 (CST)
X-RM-TRANSID: 2eea61e922ebde6-e707b
Date: Thu, 20 Jan 2022 16:53:04 +0800
From: "Meiling Chen" <chenmeiling@chinamobile.com>
To: "Valery Smyslov" <valery@smyslov.net>,  dots <dots@ietf.org>
Cc: dots-chairs <dots-chairs@ietf.org>,  draft-ietf-dots-robust-blocks <draft-ietf-dots-robust-blocks@ietf.org>
References: <001301d80bb3$a8afba90$fa0f2fb0$@smyslov.net>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.9.115[cn]
Mime-Version: 1.0
Message-ID: <202201201653040024972@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart337448641223_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/RSPGA-SCU2EAdWliVm3I57l1TSo>
Subject: Re: [Dots] WGLC for draft-ietf-dots-robust-blocks-01
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jan 2022 08:53:08 -0000

This is a multi-part message in MIME format.

------=_001_NextPart337448641223_=----
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQpJIGhhdmUgcmV2aWV3ZWQgdGhlIGRyYWZ0LCBJIHRoaW5rIGl0IGlzIHJlYWR5IGZvciBw
dWJsaWNhdGlvbi4NCg0KQmVzdCwNCk1laWxpbmcgDQpGcm9tOiBWYWxlcnkgU215c2xvdg0KRGF0
ZTogMjAyMi0wMS0xNyAyMzowNQ0KVG86IGRvdHNAaWV0Zi5vcmcNCkNDOiBkb3RzLWNoYWlyczsg
ZHJhZnQtaWV0Zi1kb3RzLXJvYnVzdC1ibG9ja3MNClN1YmplY3Q6IFtEb3RzXSBXR0xDIGZvciBk
cmFmdC1pZXRmLWRvdHMtcm9idXN0LWJsb2Nrcy0wMQ0KSGksDQogDQp0aGlzIG1lc3NhZ2Ugc3Rh
cnRzIGEgdHdvLXdlZWsgd29ya2luZyBncm91cCBsYXN0IGNhbGwgZm9yDQpkcmFmdC1pZXRmLWRv
dHMtcm9idXN0LWJsb2Nrcy0wMS4NClRoZSBXR0xDIHdpbGwgZW5kIG9uIE1vbmRheSwgSmFudWFy
eSAzMS4gUGxlYXNlLCByZXZpZXcgdGhlIGRyYWZ0IGFuZCBzZW5kDQp5b3VyIGNvbW1lbnRzIHRv
IHRoZSBtYWlsaW5nIGxpc3QuDQogDQpSZWdhcmRzLA0KRnJhbmsgJiBWYWxlcnkuDQogDQpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRG90cyBtYWlsaW5n
IGxpc3QNCkRvdHNAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vZG90cw0KIA0K

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

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3Dutf-8"><style>body { line-height: 1.5; }blockquote { margin-top: 0px; =
margin-bottom: 0px; margin-left: 0.5em; }body { font-size: 10.5pt; font-fa=
mily: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91; color: rgb(0, 0, 0); line-heig=
ht: 1.5; }</style></head><body>=0A<div><span></span>Hi,</div><div>I have r=
eviewed the draft, I think it is<span style=3D"font-family: =E5=BE=AE=E8=
=BD=AF=E9=9B=85=E9=BB=91, Tahoma; line-height: normal; font-size: 10.5pt; =
background-color: transparent;">&nbsp;ready for publication.</span></div>=
=0A<div><br></div><div>Best,</div><div>Meiling<span style=3D"font-size: 10=
.5pt; line-height: 1.5; background-color: transparent;">&nbsp;</span></div=
><blockquote style=3D"margin-Top: 0px; margin-Bottom: 0px; margin-Left: 0.=
5em"><div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0p=
t 0cm 0cm 0cm"><div style=3D"PADDING-RIGHT: 8px; PADDING-LEFT: 8px; FONT-S=
IZE: 12px;FONT-FAMILY:tahoma;COLOR:#000000; BACKGROUND: #efefef; PADDING-B=
OTTOM: 8px; PADDING-TOP: 8px"><div><b>From:</b>&nbsp;<a href=3D"mailto:val=
ery@smyslov.net">Valery Smyslov</a></div><div><b>Date:</b>&nbsp;2022-01-17=
&nbsp;23:05</div><div><b>To:</b>&nbsp;<a href=3D"mailto:dots@ietf.org">dot=
s@ietf.org</a></div><div><b>CC:</b>&nbsp;<a href=3D"mailto:dots-chairs@iet=
f.org">dots-chairs</a>; <a href=3D"mailto:draft-ietf-dots-robust-blocks@ie=
tf.org">draft-ietf-dots-robust-blocks</a></div><div><b>Subject:</b>&nbsp;[=
Dots] WGLC for draft-ietf-dots-robust-blocks-01</div></div></div><div><div=
>Hi,</div>=0A<div>&nbsp;</div>=0A<div>this message starts a two-week worki=
ng group last call for</div>=0A<div>draft-ietf-dots-robust-blocks-01.</div=
>=0A<div>The WGLC will end on Monday, January 31. Please, review the draft=
 and send</div>=0A<div>your comments to the mailing list.</div>=0A<div>&nb=
sp;</div>=0A<div>Regards,</div>=0A<div>Frank &amp; Valery.</div>=0A<div>&n=
bsp;</div>=0A<div>_______________________________________________</div>=0A=
<div>Dots mailing list</div>=0A<div>Dots@ietf.org</div>=0A<div>https://www=
.ietf.org/mailman/listinfo/dots</div>=0A<div>&nbsp;</div>=0A</div></blockq=
uote></body></html>
------=_001_NextPart337448641223_=------




From nobody Fri Jan 21 03:31:54 2022
Return-Path: <daedulus@btconnect.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 806403A1C79; Fri, 21 Jan 2022 03:31:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=btconnect.onmicrosoft.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 zdkXDIgKnLjm; Fri, 21 Jan 2022 03:31:47 -0800 (PST)
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05on20714.outbound.protection.outlook.com [IPv6:2a01:111:f400:7d00::714]) (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 4AD7F3A1C77; Fri, 21 Jan 2022 03:31:46 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EHdVBJj/Z22e0gcAtOmeMPySuTFHILzSIHo+HZK0Weo/XcbOnT53oLAHV/5XySy/zFAVPxwAXgtMCN4fmZOJB6aS72l/h5UIvZ4iwIwDY4amFcXAOIAO4CwS4+9u+Fb9afEUbzQPcuMTh4tn7RceTtCm0mU6yiXPXkeD3BH9JD8eeeY4LENxQw6ckTdc/6X8RctMPjno8ZIDHT3HyVzHoftaNBtnvnqGbaXVPiG0+V9HN5e52J/TAzYLdFLgLtYg8GVo8VLQFVmpVzLomKBnvtgW2aZuFbqftnmV9l36AkSlKA0oaPRJ5C7ntFFw6MkIlg1yJaPBTyo6BNOPPNZ8lw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=X1hpQySUEmCw48JAf0iVCtOTrFjAh8DE569AhqLmWWI=; b=dvcmQqXTEDjLILaaXebGgbZTCTw2Xj31hg+wcBP5xnEcyJ1Y7WcEjUZBdJ7PDFww9EnbP1CV7beZ1xgBpSfDRVvr2LjZTAaoCpve2oS8W54js2DkG+Wvw41rVjNuzx1LOXQqotyGX7yG82lGxCgIxqaIeep5h1FubjfVWdXx95ICx6wqN6q9Pw/gQs96OENkomoUE5wHcsMU7AmdaQNQrnwKusg00m/fD8TlqWSBXYUsVPaeoo10eXBxf2Epzjx7tvDTp2RdhiKSMtlw6i1hAExax8Y4kFSWIeN8fZDBDA4QkFadyCKYnLatsuJPrRMWCb8CtlJqTfFYkZDgVZlsew==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=X1hpQySUEmCw48JAf0iVCtOTrFjAh8DE569AhqLmWWI=; b=qP/z6OLmF8g8nkapIguMO6nkIXpovEt9ahRy78Yl0D9mbsGUvkLKSgelO26a6pw6bQbkcUuNPKCFjoej9T/tF1ccuAioBB/3dMPQj8RWguWrLauDj9X9WEV4M8vpB4LuZA8Xegae49fcvkI3lXr+zRZv9kjiqMNM5O8SQoL0zYM=
Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR07MB5069.eurprd07.prod.outlook.com (2603:10a6:803:9d::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4909.8; Fri, 21 Jan 2022 11:31:42 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::1040:a0b:e4e1:f512]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::1040:a0b:e4e1:f512%4]) with mapi id 15.20.4930.008; Fri, 21 Jan 2022 11:31:40 +0000
To: mohamed.boucadair@orange.com, "last-call@ietf.org" <last-call@ietf.org>
References: <164182513674.28016.284174261896096787@ietfa.amsl.com> <61E16D53.7050003@btconnect.com> <29779_1642412120_61E53858_29779_198_1_787AE7BB302AE849A7480A190F8B933035473D6C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <61E69102.2090001@btconnect.com> <20948_1642511112_61E6BB08_20948_182_3_787AE7BB302AE849A7480A190F8B93303547FCE0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <61E80563.5090304@btconnect.com> <16719_1642597004_61E80A8C_16719_95_2_787AE7BB302AE849A7480A190F8B9330354837BA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Cc: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "valery@smyslov.net" <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry@ietf.org" <draft-ietf-dots-telemetry@ietf.org>
From: tom petch <daedulus@btconnect.com>
Message-ID: <61EA9999.1090906@btconnect.com>
Date: Fri, 21 Jan 2022 11:31:37 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <16719_1642597004_61E80A8C_16719_95_2_787AE7BB302AE849A7480A190F8B9330354837BA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: LO2P123CA0030.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600::18) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 9b1c27f0-5030-4514-d370-08d9dcd197e6
X-MS-TrafficTypeDiagnostic: VI1PR07MB5069:EE_
X-Microsoft-Antispam-PRVS: <VI1PR07MB50698B78A54053B6D08A51BAC65B9@VI1PR07MB5069.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: NB3kbH2wHD9QTrWTy6cmrjG8wvGzmRNEV72CvErK27OoDUEQSMmpkKDDaxHolwRm6DoUH5tUZrXamouQvtgaEWhX5qETSHj3E4o76Ll1aaEgJi1IYvvIGV712Nw0Xw3QEVLvOjyKucT+XUiIIM5aCjJ+EXkbge59Tb5aAIj5sEBpNWg2cm+ssvmNzCIos7xCS2j9r6WZoy6W40Yc5aQEFCtyOE/E6ahmhW1Goab5rgxa5M1kAThTrVrvY4SPIbVZJ4SVBPKOiBCIJfwJS1m1E34xlaYZ1JV3zQpkHBeCyw53qYd3EpBwBCLfCAExnZGYFNTdyDHyNKlKJ/8i+JLoeoXz6tT257lYA28nYS3C3A52P8htYkySgSkFjiRCzCH0B9NlD7EPKTL4npJxtRKI0TPM0BfLeQoI+0C/xV15EXcwtYGzKMNhL6NDvruYwfQJN0Dd6mBykS0rDJ/IEKY3UpN7PWJ8d/MXO6AwlSOICTgxmEGq4PRY3SjBLO/Gh8sVakccmbK9A5Pd63olTUjj4YscJKsDc+34YucK+ur0KuRMTTBEOqcLQyeRZUQ3es1KLeBglYFpH2akRz6gIbJqyEc3o0J3i002EE5vN0pQSmn8ztCfmnY27MuennLQXePW05Ujyd0fjqDuVWcwZSOrw/b7XihvQiMI938ArueAHNaqwKX/bvPlOirVHsXcZ6oN5BVabu1b6XfkcDIxv65PmrNoinkgn5712QfjgAJDDUcBVRsBPyLBxAMGPkk7dChy
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(13230001)(4636009)(366004)(508600001)(38350700002)(82960400001)(38100700002)(4326008)(6916009)(6486002)(54906003)(316002)(6666004)(36756003)(8676002)(66556008)(5660300002)(186003)(26005)(8936002)(33656002)(2906002)(6512007)(2616005)(53546011)(83380400001)(87266011)(86362001)(52116002)(6506007)(66476007)(66946007)(20210929001); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?Windows-1252?Q?IH5XBChPi8ITZI/vTH1soXQMVpv1a0uXONUKyZCk0cnE2OOBgej2vv0f?= =?Windows-1252?Q?YCPJ8+lgmp8tXW4/WAQrybBlskIzLZQoo03re8vXjT47qgoEooUuSEUZ?= =?Windows-1252?Q?PElOKnEnStVaLgeXCNVgrM2uxkEY1WcBa+0jOw4wx+k1ailoFOkUJjOG?= =?Windows-1252?Q?k0wtxYuEapTqKQCialmM1Q805pupWpTdUdmrqTIN0hE8bXWVfsd5bJq3?= =?Windows-1252?Q?oUUoiTfTn7F/CShXzXh6bQQBc31B9gpKZHKpHLQiGjZKFLUDmcflAm4y?= =?Windows-1252?Q?EQ6p/2nomms+BTp7PT+GZm0D0WPrmq5gHfmFBh+S6H3iJf1UZPzZoc87?= =?Windows-1252?Q?qq2HfHMyELLa3jj1zCaYZPN9zKFJu/UzEtWmGTQIaR/3xP5Pf+mJEmDH?= =?Windows-1252?Q?t9j1+fyiZcJlcOPS3WaIucCmfHLDliIxdoswcduMt9fmCVEi7hWz1sjs?= =?Windows-1252?Q?PCXAkjAImnK/bZ9h7RGQaglq5Kqefd0Vz+eI0HEPpoEEwH1iVkF8+wc+?= =?Windows-1252?Q?9h0zDhm5pq++I6huaHjyHsSqT54xvtKladCeW4eBTf4I3xtaEv6BDXsA?= =?Windows-1252?Q?+HOANv5cSHxRF+KqpYKS7L7phbx2f3skmT4TuvoT9Kn9BMotR0CgUwQA?= =?Windows-1252?Q?qbzIcCZahMf49zwlKj89cM/VSnEGfhoxAk0DxgHY5axC5kDxxRY6l/OY?= =?Windows-1252?Q?WTwzKItoLXPuL25iVZsVth+mzu4BHcpcQE5hCqe4tFQmQbm/fmZ+wlH2?= =?Windows-1252?Q?TVzshKZWLsOlWwWs243maHdyEyUQJ3A17pL1Tu32VBiF9WE2Ar9ZwtTT?= =?Windows-1252?Q?+YYT4cpDVd5f3GQMdzdZy9wRP2zChZKVzRBAukT5xqGIvOI/U3c0Kh1D?= =?Windows-1252?Q?LlewSojYD8qGoJ/Cqh17FfKrSP91vo+JSo6IYn1hwtOQarjcBcWfyvLA?= =?Windows-1252?Q?6Gz545zv9DRIn1qY5TNedFDqF5Jr8Uk3n/a6Y4WWbB3QNhO4i4iPRYMZ?= =?Windows-1252?Q?my7vFrJJ6kEm2RkYN93D/EUE7XrSmBUMwg1mtd5PT6OqAw2+L1LoKm17?= =?Windows-1252?Q?qpmD0tMoL+SEh5kMQNo4bAPn4Q/qWLvJewNo7YqRUKHQztihOYqSHLTP?= =?Windows-1252?Q?C2ZdMuNHgE43Xl9lswDZTrP7Qgd6VsFl8K2T9C5I6TYMjyhux3CYuznd?= =?Windows-1252?Q?JuGcTUAPA4NyDScmb177Pcw/WS+VuQ8t+teLbyRRdjs+qwBWbmvirA6n?= =?Windows-1252?Q?LiA9IobKj9D6rYV7+voXjfasflHiSJte/2WyHJCizkjBMTHnSVwxuIn6?= =?Windows-1252?Q?3SvVlBwSFncP0YKxelawl1zFioP9dYZJ0KgiExasTXkUk9ui4fjQu/rQ?= =?Windows-1252?Q?18Ey4TegDYAWK1X1y04nHF2S961VaB4DlptdsMOwgrEgCsbhWj46Npa/?= =?Windows-1252?Q?kQvUS3niYByh6qoZbjKmSrAyb1URBA96SMfbjnKyVuXmfm9KwNzC3mSB?= =?Windows-1252?Q?V7vRVIbGi6+Gn98E84Gy3KBgPEIH00ZpF/dp2ZHcpLH+VsLW//DAsr+K?= =?Windows-1252?Q?YHqgYef205w6gSK60B8jyS4s2mGfQjdrnwI7VxKpGiFuY0VDUkU9WUnX?= =?Windows-1252?Q?MREbwkI9W4P6hDbWvkX8amzbCFy7rz8q89QgAPeBOPlsJWNQ5CPlPZ73?= =?Windows-1252?Q?j4392FvqWhYU6CgGt2J8Zz33RbCuwtPooT4eXCMdKf4BNcw4oqAKoJC7?= =?Windows-1252?Q?8ns6UFgKLJtZ7kNQpMM=3D?=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9b1c27f0-5030-4514-d370-08d9dcd197e6
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Jan 2022 11:31:40.7679 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: RXvh0W46ZdNwhsvubLPoRZ//XANjVzZxuGt8RpjC09Sn0jT2ivmJyVp7+wZjdi0HoWHyJqdGJ3BETyDIaCdPWg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB5069
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/ADAPijIjyZ-2vkcE-k16oIf-fx4>
Subject: Re: [Dots] Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jan 2022 11:31:53 -0000

On 19/01/2022 12:56, mohamed.boucadair@orange.com wrote:
> Hi Tom,
>
> Thank you for checking the changes and sharing your feedback.
>
> Please see inline.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : tom petch <daedulus@btconnect.com>
>> Envoyé : mercredi 19 janvier 2022 13:35
>>
> ...
>>> ...
>>>>
>>>>>> The user has to understand that [Enterprise-Numbers] is the same as
>>>>>> Private Enterprise Numbers", which may not be apparent; consistent
>>>>>> terminology is good.
>>>>>
>>>>> [Med] Not sure a (which) change is needed. The current text says:
>>>>
>>>> In most walks of life, if you have a registry and a private registry,
>>>> then users will assume that the registry is public and the private
>>>> registry is private and that there are two separate registries.  Here
>>>> there is just the one and the correct name is 'Private Enterprise
>>>> Number' sometimes abbreviated to PEN.  Experts will know that there
>>>> is no Public Enterprise Number, others will not so I think we should
>>>> use Private Enterprise Number in all cases and not just Enterprise
>> Number.
>>>>
>>>
>>> [Med] Went with the following change:
>>>
>>> OLD:
>>>
>>>>>       vendor-id:  Vendor ID is a security vendor's Enterprise Number
>> as
>>>>>          registered with IANA [Enterprise-Numbers].
>>>>>
>>>
>>> NEW:
>>>      vendor-id:  Vendor ID is a security vendor's enterprise number as
>>>         registered in the IANA's "Private Enterprise Numbers" registry
>>>         [Enterprise-Numbers].
>>
>>
>> You have still got half a dozen or so uses of 'Enterprise Number' in the
>> I-D and my preference would be to change them all to 'Private Enterprise
>> Number'!
>
> [Med] No change is made for the other occurrences on purpose. For example,
>
>     The examples use the Enterprise Number 32473 defined for
>     documentation use [RFC5612].
>
> no change is made to that text because we want to be consistent with existing RFC5612 which says the following:
>
>     IANA has updated the registration for Enterprise Number 32473 to
>     point to this RFC.
>
>    As I said before, an expert knows that there is no Public
>> Enterprise Number, others do not.
>>
>
> [Med] Added this new entry to the terminology section:
>
> NEW:
>     The document uses IANA-assigned Enterprise Numbers.  These numbers
>     are also known as "Private Enterprise Numbers" and "SMI (Structure of
>     Management Information) Network Management Private Enterprise Codes"
>     [Enterprise-Numbers].
>
> Better?


I cannot see us agreeing on this.  The fact that the terminology of 
RFC5612 is not what it might be does not, for me, sanction other such 
glitches.

Tom Petch


>
> _________________________________________________


From nobody Fri Jan 21 09:58:08 2022
Return-Path: <iana-shared@icann.org>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C77ED3A1125 for <dots@ietfa.amsl.com>; Fri, 21 Jan 2022 09:57:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.626
X-Spam-Level: 
X-Spam-Status: No, score=-0.626 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MISSING_HEADERS=1.021, RCVD_IN_MSPIKE_BL=0.001, RCVD_IN_MSPIKE_L3=0.001, SPF_HELO_NONE=0.001, 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 y6IEbLi5VT_j for <dots@ietfa.amsl.com>; Fri, 21 Jan 2022 09:57:50 -0800 (PST)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [192.0.33.81]) (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 D457E3A1120 for <dots@ietf.org>; Fri, 21 Jan 2022 09:57:50 -0800 (PST)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 80039E30EF; Fri, 21 Jan 2022 17:57:50 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id 7E5F6207C1; Fri, 21 Jan 2022 17:57:50 +0000 (UTC)
RT-Owner: sabrina.tanamal
From: "Sabrina Tanamal via RT" <drafts-expert-review-comment@iana.org>
Reply-To: drafts-expert-review-comment@iana.org
In-Reply-To: <rt-4.4.3-13834-1642787548-803.1223069-9-0@icann.org>
References: <RT-Ticket-1223069@icann.org> <rt-4.4.3-13834-1642787548-803.1223069-9-0@icann.org>
Message-ID: <rt-4.4.3-19699-1642787870-656.1223069-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1223069
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: sabrina.tanamal@icann.org
CC: mt@lowentropy.net, tbray@textuality.com, dots@ietf.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Fri, 21 Jan 2022 17:57:50 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/iWDiJoOi9fwzxSsYIGEF-BW6nu0>
Subject: [Dots] [IANA #1223069] expert review for draft-ietf-dots-telemetry-19 (xml-registry)
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jan 2022 17:57:56 -0000

Hi Martin and Tim (cc: dots WG), 

As the designated experts for the ns IETF XML registry, can you review the proposed registration in draft-ietf-dots-telemetry for us? Please see

https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/

If this is OK, when the IESG approves the document for publication, we'll make the registration at

https://www.iana.org/assignments/xml-registry

The IESG has asked us to set a two-week deadline for registration reviews. The due date for this request is 4 February 2022. 

thanks,

Sabrina Tanamal
Lead IANA Services Specialist




From nobody Fri Jan 21 10:23:41 2022
Return-Path: <tbray@textuality.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D83F3A0828 for <dots@ietfa.amsl.com>; Fri, 21 Jan 2022 10:23:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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=textuality-com.20210112.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 bZO_R35WE2iI for <dots@ietfa.amsl.com>; Fri, 21 Jan 2022 10:23:34 -0800 (PST)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 1FFC73A081F for <dots@ietf.org>; Fri, 21 Jan 2022 10:23:34 -0800 (PST)
Received: by mail-lf1-x12e.google.com with SMTP id y15so27313318lfa.9 for <dots@ietf.org>; Fri, 21 Jan 2022 10:23:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DuWxy30UsCd53DS5GN+dKsZ6Cl48FuKFOkV/Nm6yaiA=; b=vFUQ8CrhwCr34a6L+tL0RqeXMvXZ2MSLROM9IWMaDkvj4/4RImD1H8agAsr9Apybqf M6tYkrFgyo4fDYACoyrjaGL/3QG0v5i6QL0kPZJUoA1TL3RlEY6p95WKn4bqdaELbSYj /iqZPNRofvl+VzUBYtYO2gxRhOq9mcdVE0bFWQmts2GLGyHvNs8pFhYTvHRjki53G/hc 87v3RoOafpIgT3C/ho+0mY97KExsixWOeIYUZNR3OU7WFpHp2Z9UtrHBIRFjJbsvvtqc l1wtwcs4I6n6/spyfghms/A+Ymifm21KdJgkmBgxZNf+EYG8Xk/uNC8APFps3vLZhb5q zH8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DuWxy30UsCd53DS5GN+dKsZ6Cl48FuKFOkV/Nm6yaiA=; b=t3VITfBeYN6mO5y9nSlCeCHfCu94WjS0F3QD8XgSDZqpqO1sBO2IARM8qdiCoETXDR vWa+wUikgcHyMHZ3ivcl2N+j/HSqI6UdnpFsFHxM7Wgs0mxn2BqtP0L1Hq3WuW/cL3cl m4BIkB+xTgPrB0Z2VXtRwoj91wM5hQdvcY7nCypFQGcXkgxCs2ZZVVPyyAOhMV1bfSuQ mzWmdcyhPDPaRzEM4r++3N/sykzpEHLP7wJvEAf/ouSLbhPcqHifMyJNuzDi+cOPiiJl LOvSSyx02GiuS5/2mp1hJv56/aY47L5c3nGMAZ4cyxxzHctoUp4b3LYW+M0UEsdQmH/P Fi1A==
X-Gm-Message-State: AOAM532l27Zan93yzfhhNncOUx8unp4dH6QzpFXsZUoVEDzFzrzkZn+X udXL+4tgsTM+/pNa06aXBW6gcet/EnhVUdMj5ytsvUm1kmY=
X-Google-Smtp-Source: ABdhPJyDh2YDM6PfuVklINiE5AHHh/02+msCkQ3ZhYc/SIDYahdAjXDlVOMa5XIJxED4ghmUoH55+Pd0yWF0dMgfyhs=
X-Received: by 2002:a05:6512:3406:: with SMTP id i6mr4513195lfr.637.1642789411046;  Fri, 21 Jan 2022 10:23:31 -0800 (PST)
MIME-Version: 1.0
References: <RT-Ticket-1223069@icann.org> <rt-4.4.3-13834-1642787548-803.1223069-9-0@icann.org> <rt-4.4.3-19699-1642787870-656.1223069-9-0@icann.org>
In-Reply-To: <rt-4.4.3-19699-1642787870-656.1223069-9-0@icann.org>
From: Tim Bray <tbray@textuality.com>
Date: Fri, 21 Jan 2022 10:23:19 -0800
Message-ID: <CAHBU6iv-mDC7ApzB09bCET620GUQBfUiuqzvh6YPzGPv_KB1Rg@mail.gmail.com>
To: Amanda Baber via RT <drafts-expert-review-comment@iana.org>
Cc: Martin Thomson <mt@lowentropy.net>, dots@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004965a905d61bb710"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/ctFI_SFHdd_MrLmbT45BXGZHEzQ>
Subject: Re: [Dots] [IANA #1223069] expert review for draft-ietf-dots-telemetry-19 (xml-registry)
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jan 2022 18:23:39 -0000

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

Looks OK to me.

On Fri, Jan 21, 2022 at 9:57 AM Sabrina Tanamal via RT <
drafts-expert-review-comment@iana.org> wrote:

> Hi Martin and Tim (cc: dots WG),
>
> As the designated experts for the ns IETF XML registry, can you review the
> proposed registration in draft-ietf-dots-telemetry for us? Please see
>
> https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/
>
> If this is OK, when the IESG approves the document for publication, we'll
> make the registration at
>
> https://www.iana.org/assignments/xml-registry
>
> The IESG has asked us to set a two-week deadline for registration reviews.
> The due date for this request is 4 February 2022.
>
> thanks,
>
> Sabrina Tanamal
> Lead IANA Services Specialist
>
>
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">Loo=
ks OK to me.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Fri, Jan 21, 2022 at 9:57 AM Sabrina Tanamal via RT &l=
t;<a href=3D"mailto:drafts-expert-review-comment@iana.org">drafts-expert-re=
view-comment@iana.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-st=
yle:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hi Martin an=
d Tim (cc: dots WG), <br>
<br>
As the designated experts for the ns IETF XML registry, can you review the =
proposed registration in draft-ietf-dots-telemetry for us? Please see<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/" rel=
=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ie=
tf-dots-telemetry/</a><br>
<br>
If this is OK, when the IESG approves the document for publication, we&#39;=
ll make the registration at<br>
<br>
<a href=3D"https://www.iana.org/assignments/xml-registry" rel=3D"noreferrer=
" target=3D"_blank">https://www.iana.org/assignments/xml-registry</a><br>
<br>
The IESG has asked us to set a two-week deadline for registration reviews. =
The due date for this request is 4 February 2022. <br>
<br>
thanks,<br>
<br>
Sabrina Tanamal<br>
Lead IANA Services Specialist<br>
<br>
<br>
<br>
</blockquote></div>

--0000000000004965a905d61bb710--


From nobody Fri Jan 21 15:01:44 2022
Return-Path: <noreply@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DF0A63A14DF; Fri, 21 Jan 2022 15:01:27 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: dots@ietf.org, draft-ietf-dots-telemetry.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164280608786.26256.18141980913416166060@ietfa.amsl.com>
Reply-To: Robert Sparks <rjsparks@nostrum.com>
Date: Fri, 21 Jan 2022 15:01:27 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/0Pq7_Dkx1Ajl1MVgpaofGqthvl4>
Subject: [Dots] Genart last call review of draft-ietf-dots-telemetry-19
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jan 2022 23:01:28 -0000

Reviewer: Robert Sparks
Review result: Ready with Issues

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

For more information, please see the FAQ at

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

Document: draft-ietf-dots-telemetry-19
Reviewer: Robert Sparks
Review Date: 2022-01-21
IETF LC End Date: 2022-01-24
IESG Telechat date: Not scheduled for a telechat

Summary: Ready for publication as a Proposed Standard RFC, but with issues and
nits to consider before publication

Issues:
-------

This document relies heavily on the requirements in the DOTS signal and data
channel specifications (RFC9132 and RFC8783) saying authenticated encryption
MUST be used. Explicitly calling that out in this document's security section
would be worthwhile.

I am not a YANG Doctor. This document seems to make a reasonable but unusual
use of YANG. I would really like to see YANG Doctor review of -19. I wonder if
it would be possible to factor some of the more generic enums out into
something that could be reused elsewhere. Why do you stop at discouraging
rather than forbidding server deviations? The point of a specification like
this is interoperability.

I'm a little uncomfortable with the passively stated requirement to use
ietf-dots-rehoming (at "clients are assumed to follow") while that document is
an Informative reference.

In 6.1.2, I'm confused by the requirement that "'tsid' values MUST increase
monotonically when a new PUT is generated" combined with "If the dot server
finds the 'tsid' parameter value conveyed in the PUT request in its
configuration data and (it) has accepted the updated configuration parameters,
a 2.04 (Changed) MUST be returned". What am I missing that would allow a PUT
with a tsid that's already in the server's configuration data? Is there perhaps
leftover tension here from earlier designs that were changed?

At the end of 7.1, there is a MUST NOT level requirement against repeating
attack-descriptions that have been previously sent to a peer. Is it always the
case that when these descriptions are sent, the message they are contained in
is acknowledged? If not, consider adding discussion of how/whether a peer can
ask for a description when it gets an attack-id it doesn't have a description
for.

In 7.2, you require a freshly rebooted client to send a GET request to retrieve
active 'tmid' values. Why? Why not let it just send a DELETE with no 'tmid'
right away if that's what it would do after receiving the response to the GET
anyhow?

In 7.3 at "The PUT request MUST be maintained in an active state", you mean the
configuration that the PUT established must be kept. The PUT request itself has
no state beyond its response. Consider saying something like "The
pre-or-ongoing mitigation requests MUST be considered active" instead.

In the yang module, there's a reference at page 79 that points to "Section
4.4.2 of RFC UUUU." This is the only occurrence of UUUU in the document, and if
it's meant to be replaced with 'this RFC', this document has no section 4.4.2.

Nits:
---------------

Last paragraph of introduction at "Nevertheless, when..". That sentence is
particularly hard to parse, please simplify it.

Curious that you called out TCP port 80 in the discussion in 3.3. Why not 443?

At 4.1, where you say "that truly require reliable delivery", I think you mean
something more like "that are important to deliver". Nothing here is trying to
guarantee reliable delivery and the statement misleads the reader to look for
reliable delivery mechanisms.

In 4.5 at "The reason for not including these keys...". That sentence does not
parse. Please simplify.

In 4.6, the second paragraph is about validating messages, not examples. It's
not clear the paragraph is useful as a roadmap through the document. Consider
deleting it.

The outline structure of section 4 is odd. There are several Considerations
subsections including "Generic Considerations" (which is jarring), and several
subsections that are not considerations sections. Having them under a section
titled "Design Overview" doesn't help pull them together. Perhaps a mild
restructure/reorder would bring more clarity?

At 6.1, consider replacing "(with suitable default)." with ". Default values
are defined later in this section."

In 6.1 you claim clients can negotiate configuration parameters with server. I
don't find a negotiation protocol specified here. I think you mean clients can
configure parameters at a servers, and servers can configure parameters at a
client. There's not really a mechanism for a peer to say "no, I don't the
percentile config you're trying to set and I won't do that".

The introduction of "a third-party DOTS server" in the narrative after Figure
13 is surprising. For the paragraph to make sense, the messages in the
discussion before Figure 13 would also have to have gone to that third-part
DOTS server. Consider calling out that the DOTS server may not be hosted at any
of the ISPs at the beginning of 6.2.1 instead.

In 6.2.1 where you require servers to reject PUT requests with 0 capacity for
all included links, consider saying "Use DELETE instead." Maybe say _why_ you
require that PUT to be rejected.

In the sentence after Figure 19 (at least in the text version), you mean to
point to Figure 20.

At 7.1 "DOTS telemetry attributes are optionally signaled and therefore MUST
NOT be treated as mandatory fields in the DOTS signal channel protocol" is an
odd thing to call out this way. I think this was mentioned in the earlier yang
doctors review as well. Why is it here?

In 7.1.1 consider replacing "the same attributes" with simply "the attributes".

In 7.1.6, please replace "reiterates" with "repeats".

In 7.1.6, please replace the phrase "Concretely, " with "A".




From nobody Sun Jan 23 06:13:49 2022
Return-Path: <noreply@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C6C43A1B6A; Sun, 23 Jan 2022 06:13:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Michael Scharf via Datatracker <noreply@ietf.org>
To: <tsv-art@ietf.org>
Cc: dots@ietf.org, draft-ietf-dots-telemetry.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164294721399.6670.12040039401983463326@ietfa.amsl.com>
Reply-To: Michael Scharf <michael.scharf@hs-esslingen.de>
Date: Sun, 23 Jan 2022 06:13:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/OWW_J8WIoSZn4GAWJcZ-GCPGO0U>
Subject: [Dots] Tsvart last call review of draft-ietf-dots-telemetry-19
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Jan 2022 14:13:34 -0000

Reviewer: Michael Scharf
Review result: Ready

This document has been reviewed as part of the transport area review team'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 and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

I have reviewed this document as TSV-ART reviewer. All in all, it is a
well-written document, albeit with a somewhat atypical usage of YANG. 

I have only reviewed the document regarding typical TSV-ART issues.
As far as I can see, the document does not contain any major problem
related to Internet transport protocols.



From nobody Sun Jan 23 14:41:39 2022
Return-Path: <noreply@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C2003A2D6B; Sun, 23 Jan 2022 14:41:37 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ted Lemon via Datatracker <noreply@ietf.org>
To: <int-dir@ietf.org>
Cc: dots@ietf.org, draft-ietf-dots-telemetry.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164297769741.21935.5814690155836157029@ietfa.amsl.com>
Reply-To: Ted Lemon <mellon@fugue.com>
Date: Sun, 23 Jan 2022 14:41:37 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/dDpLSoIxGKk086-bJaEQEHiOk2c>
Subject: [Dots] Intdir last call review of draft-ietf-dots-telemetry-19
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Jan 2022 22:41:38 -0000

Reviewer: Ted Lemon
Review result: Ready with Nits

I am an assigned INT directorate reviewer for draft-ietf-dots-telemetry. These
comments were written primarily for the benefit of the Internet Area Directors.
Document editors and shepherd(s) should treat these comments just like they
would treat comments from any other IETF contributors and resolve them along
with any other Last Call comments that have been received. For more details on
the INT Directorate, see https://datatracker.ietf.org/group/intdir/about/
<https://datatracker.ietf.org/group/intdir/about/>.

I do not see any issues in this document that would suggest that the INT Area
directors should object to it. The document appears to be a combination of
three things: a description of the context in which what is specified would be
useful; a collection of advice about operational considerations when using what
is specified; and finally the actual specification. To the best of my ability
to evaluate it, it seems to be complete, and it should be possible to use it as
a basis for an implementation.

Although I would prefer to see this document published as three separate
documents, each addressing one of the aforementioned topics, I don't think
that's a reasonable request to make during last call. As such, I'm going to say
that the document is ready to publish as is.



From nobody Sun Jan 23 21:35:52 2022
Return-Path: <valery@smyslov.net>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35BCE3A1B2F; Sun, 23 Jan 2022 21:35:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, 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=smyslov.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 olGiYd-BkVXW; Sun, 23 Jan 2022 21:35:45 -0800 (PST)
Received: from direct.host-care.com (direct.host-care.com [198.136.54.115]) (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 2F1273A1B2E; Sun, 23 Jan 2022 21:35:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smyslov.net ; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :Date:Subject:Cc:To:From:Sender:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=gBSPLluQu6AyLETO8dQJBGZ9GKCkePQNSd0M7rJnAKY=; b=A8IhoKKciKdAY7b+7QgcKDMEsM GuDsEA5rB91h5Q6z06xXfg/DbEy6r2sF1wAG23CsgjGN23u2vgUoIqviD+CNLwZu0yRrsu1rw/6rq HatVzzD0rbmJNil8EYVULiCDynUTXsw37q3u9Vd0KzK74CXUQsJkT2Z0d7qZ3IJgIeFsH68iLE76W lEoe/ZzIh+b+jmv5kDCYTGJPMP0qOnqapSv7DmHffB0ncnvZn4vQaJnwTydAikmJLyM5lSKY/jrfq zb4dyAphC089ht325O2ioNH+CsrrOiLZf2Z4zNzDc1s6At44DjOIhyUc+VuMmRliOI6+TzTYaYITK 8T6kYldA==;
Received: from 78-107-207-25.broadband.corbina.ru ([78.107.207.25]:51294 helo=chichi) by direct.host-care.com with esmtpsa (TLS1.2) tls TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <valery@smyslov.net>) id 1nBs0z-0002xB-GY; Mon, 24 Jan 2022 00:35:41 -0500
From: "Valery Smyslov" <valery@smyslov.net>
To: <draft-ietf-dots-multihoming@ietf.org>, <dots@ietf.org>
Cc: <dots-chairs@ietf.org>
Date: Mon, 24 Jan 2022 08:35:38 +0300
Message-ID: <003c01d810e4$394e2480$abea6d80$@smyslov.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: ru
Thread-Index: AdgQ454uLlw+cuWkQqqZ6dtJPHivRg==
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - direct.host-care.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - smyslov.net
X-Get-Message-Sender-Via: direct.host-care.com: authenticated_id: valery@smyslov.net
X-Authenticated-Sender: direct.host-care.com: valery@smyslov.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/29ercCFxnlcJd6Dl2yMijDXh_lU>
Subject: [Dots] IPR confirmation for draft-ietf-dots-multihoming-10
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 05:35:50 -0000

Hi authors,

while preparing shepherd write-up for draft-ietf-dots-multihoming-10, 
in accordance with BCP78 and BCP79 I have to ask all authors and
contributors 
whether they are aware of any IPR regarding this document.
Can you please confirm that you are not aware of any IPR 
or disclose any IPR you are aware of that are concerned with this draft.

I'd also like to ask authors about implementation status of the draft.
Are there any implementations that follow recommendations from the draft 
you are aware of?

Regards,
Valery.


From nobody Mon Jan 24 00:21:45 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F88E3A2286; Mon, 24 Jan 2022 00:21:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level: 
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 XVbGliH-4v3U; Mon, 24 Jan 2022 00:21:26 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (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 AB9E73A2284; Mon, 24 Jan 2022 00:21:25 -0800 (PST)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr21.francetelecom.fr (ESMTP service) with ESMTPS id 4Jj2xv3zkwz5wLH;  Mon, 24 Jan 2022 09:21:23 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1643012483; bh=aUvfhjVk24ikh7A+uakyxunyESN8rDyPnkKYoUN4vck=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=Qjg3FW1nHjCMI0AXrm26bln+VnMH8L2J/7ounwFyisgh6Tx2ob5pxN10hbWgemfu4 V8au032TjpndvYY1PTdEAP8FHnpPJ4jqaYzhWleDjqjxKxKRIb6EBumjIP2OC0Gf9p pCF5O6rUgoJ1TlOUYkiglpid8YwQgJu7PsJg+TVnli1sIMrGOiPGetJVaxAIj5texJ gZi9xpoq1uXDAMAmQI9/NYynyedqZIM/d3UhiM605+614hxKrtPbeFsn1Mh5vkYu2f N+qNciJl+SfA1EwcXtzbua+5SSNb/9Iec3Fh1nLGAM5sKppZTUgsYjMbXrtEKe7cKa CyaX2dTs2UAqg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr05.francetelecom.fr (ESMTP service) with ESMTPS id 4Jj2xv2hSgzyQ3; Mon, 24 Jan 2022 09:21:23 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Michael Scharf <michael.scharf@hs-esslingen.de>, "tsv-art@ietf.org" <tsv-art@ietf.org>
CC: "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry.all@ietf.org" <draft-ietf-dots-telemetry.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: Tsvart last call review of draft-ietf-dots-telemetry-19
Thread-Index: AQHYEGNp4aD1mJre9U6iX4HVMU/Wtaxx1VkQ
Content-Class: 
Date: Mon, 24 Jan 2022 08:21:22 +0000
Message-ID: <10600_1643012483_61EE6183_10600_197_1_787AE7BB302AE849A7480A190F8B9330354855A6@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164294721399.6670.12040039401983463326@ietfa.amsl.com>
In-Reply-To: <164294721399.6670.12040039401983463326@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-24T08:19:16Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=9d639f5a-5f00-478d-b33c-bc0933884245; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/SxFvJm-DoUXwnzaenj_TIvrlJ18>
Subject: Re: [Dots] Tsvart last call review of draft-ietf-dots-telemetry-19
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 08:21:30 -0000

SGkgTWljaGFlbCwgDQoNClRoYW5rIHlvdSBmb3IgdGhlIHJldmlldy4gDQoNCllvdXIgcmV2aWV3
IHdpbGwgYmUgYWNrbm93bGVkZ2VkIGluIHRoZSBuZXh0IHZlcnNpb246IGh0dHBzOi8vZ2l0aHVi
LmNvbS9ib3VjYWRhaXIvZHJhZnQtZG90cy10ZWxlbWV0cnkvYmxvYi9tYXN0ZXIvZHJhZnQtaWV0
Zi1kb3RzLXRlbGVtZXRyeS50eHQgDQoNCkNoZWVycywNCk1lZA0KDQo+IC0tLS0tTWVzc2FnZSBk
J29yaWdpbmUtLS0tLQ0KPiBEZcKgOiBNaWNoYWVsIFNjaGFyZiB2aWEgRGF0YXRyYWNrZXIgPG5v
cmVwbHlAaWV0Zi5vcmc+DQo+IEVudm95w6nCoDogZGltYW5jaGUgMjMgamFudmllciAyMDIyIDE1
OjE0DQo+IMOAwqA6IHRzdi1hcnRAaWV0Zi5vcmcNCj4gQ2PCoDogZG90c0BpZXRmLm9yZzsgZHJh
ZnQtaWV0Zi1kb3RzLXRlbGVtZXRyeS5hbGxAaWV0Zi5vcmc7IGxhc3QtDQo+IGNhbGxAaWV0Zi5v
cmcNCj4gT2JqZXTCoDogVHN2YXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1kb3Rz
LXRlbGVtZXRyeS0xOQ0KPiANCj4gUmV2aWV3ZXI6IE1pY2hhZWwgU2NoYXJmDQo+IFJldmlldyBy
ZXN1bHQ6IFJlYWR5DQo+IA0KPiBUaGlzIGRvY3VtZW50IGhhcyBiZWVuIHJldmlld2VkIGFzIHBh
cnQgb2YgdGhlIHRyYW5zcG9ydCBhcmVhIHJldmlldw0KPiB0ZWFtJ3Mgb25nb2luZyBlZmZvcnQg
dG8gcmV2aWV3IGtleSBJRVRGIGRvY3VtZW50cy4gVGhlc2UgY29tbWVudHMgd2VyZQ0KPiB3cml0
dGVuIHByaW1hcmlseSBmb3IgdGhlIHRyYW5zcG9ydCBhcmVhIGRpcmVjdG9ycywgYnV0IGFyZSBj
b3BpZWQgdG8NCj4gdGhlIGRvY3VtZW50J3MgYXV0aG9ycyBhbmQgV0cgdG8gYWxsb3cgdGhlbSB0
byBhZGRyZXNzIGFueSBpc3N1ZXMgcmFpc2VkDQo+IGFuZCBhbHNvIHRvIHRoZSBJRVRGIGRpc2N1
c3Npb24gbGlzdCBmb3IgaW5mb3JtYXRpb24uDQo+IA0KPiBXaGVuIGRvbmUgYXQgdGhlIHRpbWUg
b2YgSUVURiBMYXN0IENhbGwsIHRoZSBhdXRob3JzIHNob3VsZCBjb25zaWRlcg0KPiB0aGlzIHJl
dmlldyBhcyBwYXJ0IG9mIHRoZSBsYXN0LWNhbGwgY29tbWVudHMgdGhleSByZWNlaXZlLiBQbGVh
c2UNCj4gYWx3YXlzIENDIHRzdi1hcnRAaWV0Zi5vcmcgaWYgeW91IHJlcGx5IHRvIG9yIGZvcndh
cmQgdGhpcyByZXZpZXcuDQo+IA0KPiBJIGhhdmUgcmV2aWV3ZWQgdGhpcyBkb2N1bWVudCBhcyBU
U1YtQVJUIHJldmlld2VyLiBBbGwgaW4gYWxsLCBpdCBpcyBhDQo+IHdlbGwtd3JpdHRlbiBkb2N1
bWVudCwgYWxiZWl0IHdpdGggYSBzb21ld2hhdCBhdHlwaWNhbCB1c2FnZSBvZiBZQU5HLg0KPiAN
Cj4gSSBoYXZlIG9ubHkgcmV2aWV3ZWQgdGhlIGRvY3VtZW50IHJlZ2FyZGluZyB0eXBpY2FsIFRT
Vi1BUlQgaXNzdWVzLg0KPiBBcyBmYXIgYXMgSSBjYW4gc2VlLCB0aGUgZG9jdW1lbnQgZG9lcyBu
b3QgY29udGFpbiBhbnkgbWFqb3IgcHJvYmxlbQ0KPiByZWxhdGVkIHRvIEludGVybmV0IHRyYW5z
cG9ydCBwcm90b2NvbHMuDQo+IA0KDQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwoKQ2UgbWVzc2FnZSBldCBzZXMgcGllY2Vz
IGpvaW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25zIGNvbmZpZGVudGllbGxl
cyBvdSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jCnBhcyBldHJlIGRpZmZ1c2VzLCBl
eHBsb2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3VzIGF2ZXogcmVjdSBj
ZSBtZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyCmEgbCdleHBlZGl0ZXVy
IGV0IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExlcyBtZXNzYWdl
cyBlbGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24sCk9yYW5nZSBk
ZWNsaW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBldGUgYWx0ZXJlLCBk
ZWZvcm1lIG91IGZhbHNpZmllLiBNZXJjaS4KClRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1l
bnRzIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciBwcml2aWxlZ2VkIGluZm9ybWF0aW9uIHRo
YXQgbWF5IGJlIHByb3RlY3RlZCBieSBsYXc7CnRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRl
ZCwgdXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLgpJZiB5b3UgaGF2ZSByZWNl
aXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRl
bGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4KQXMgZW1haWxzIG1heSBiZSBh
bHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZlIGJlZW4g
bW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLgpUaGFuayB5b3UuCgo=


From nobody Mon Jan 24 00:28:05 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12C653A22C8; Mon, 24 Jan 2022 00:28:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 ULANoW9L_GLI; Mon, 24 Jan 2022 00:27:59 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (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 1E26A3A22C6; Mon, 24 Jan 2022 00:27:59 -0800 (PST)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar21.francetelecom.fr (ESMTP service) with ESMTPS id 4Jj35S5rpYz7tr0;  Mon, 24 Jan 2022 09:27:56 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1643012876; bh=DTRaWge/oh2Dc4EBinPHB3schMB4zKh1DkQIAg11lQc=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=T0VZQR3Z8pW4KUUgFJwK4ReEqPnScVxsft9ut9SbYbGQYEkDNG5ccj+QxNZVsVhSL Vdo/jQSYE3TLn8/3HDpTGnOfgiJZ2F4+lhWPv35yz1gCre/r2RVpKpg7mmQST2hNT5 +QkqHBU9D2ilURvmE78pQ++vRsXDH7vCQ6cmT3j6A8igeVouupS0aMLie7gj+o7qag aN47FPUxOS0Tqenn6Els8FkdokKa+FO5B6sBLfE9Db+3Eu2WmpObQz5YEft1HvDl8M Z6zWregziVAqcVZHTe6YEd3NrQn9kWtrPoqAVRgZaL41WevPSE60qp1zT4tux/4uAD Xoh6HIyx1t0dQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar02.francetelecom.fr (ESMTP service) with ESMTPS id 4Jj35S4gHyzCqkP;  Mon, 24 Jan 2022 09:27:56 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Valery Smyslov <valery@smyslov.net>, "draft-ietf-dots-multihoming@ietf.org" <draft-ietf-dots-multihoming@ietf.org>, "dots@ietf.org" <dots@ietf.org>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>
Thread-Topic: IPR confirmation for draft-ietf-dots-multihoming-10
Thread-Index: AdgQ454uLlw+cuWkQqqZ6dtJPHivRgAGCnlA
Content-Class: 
Date: Mon, 24 Jan 2022 08:27:55 +0000
Message-ID: <25911_1643012876_61EE630C_25911_48_1_787AE7BB302AE849A7480A190F8B9330354855CB@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <003c01d810e4$394e2480$abea6d80$@smyslov.net>
In-Reply-To: <003c01d810e4$394e2480$abea6d80$@smyslov.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-24T08:24:25Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=a6aef23b-997a-4955-b7a7-cf09cd574411; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/snqL2m4aFISAk9ttDDqiGNCy2T8>
Subject: Re: [Dots] IPR confirmation for draft-ietf-dots-multihoming-10
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 08:28:04 -0000

Hi Valery, all,=20

I'm not aware of any IPR related to this draft.=20

I don't know if the recommendations are followed in the existing implementa=
tions.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: Valery Smyslov <valery@smyslov.net>
> Envoy=E9=A0: lundi 24 janvier 2022 06:36
> =C0=A0: draft-ietf-dots-multihoming@ietf.org; dots@ietf.org
> Cc=A0: dots-chairs@ietf.org
> Objet=A0: IPR confirmation for draft-ietf-dots-multihoming-10
>=20
> Hi authors,
>=20
> while preparing shepherd write-up for draft-ietf-dots-multihoming-10, in
> accordance with BCP78 and BCP79 I have to ask all authors and
> contributors whether they are aware of any IPR regarding this document.
> Can you please confirm that you are not aware of any IPR or disclose any
> IPR you are aware of that are concerned with this draft.
>=20
> I'd also like to ask authors about implementation status of the draft.
> Are there any implementations that follow recommendations from the draft
> you are aware of?
>=20
> Regards,
> Valery.


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Mon Jan 24 00:30:17 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FB2D3A22DD; Mon, 24 Jan 2022 00:30:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 ZYnIiuF2oev1; Mon, 24 Jan 2022 00:30:11 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (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 BBC533A22DC; Mon, 24 Jan 2022 00:30:10 -0800 (PST)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar20.francetelecom.fr (ESMTP service) with ESMTPS id 4Jj3805cnTz8tnq;  Mon, 24 Jan 2022 09:30:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1643013008; bh=z8MDFwLFlaNLQv11QjclepL/5uNlz0SfhfPODLhFGTY=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=AX3mhn4EnjhTsiQZFSotEf5nJbtDMKGUaLTH9gie/7ij2f99ITJFt8BZ+Np/DLeVp /qoISN4JeIZGCNdwcN9AaE78jDtlmbObdOeLYg/cj36pjGTE07r1bfrNRdCd7eI895 3nqLXNrP3HzbpOwi+Hgpt8j9ht+SZKcxwFXtuF0Ny9WK35Zc84BdunlpBE8Xxk9z0Q mvjiCxUhlTKuas4TAQGcRusM99/tDeg3/ZmmeBXl/5TfBHJ2DwQmGlMRLw7Ki8j0hj cBPp6kmRDHyxfV17gzQ8JwlXkgZMpTfw15eEHOm8ZUCT41r4y3bMCUqcpJyca4weri 1gBb5T8fgsPwA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar00.francetelecom.fr (ESMTP service) with ESMTPS id 4Jj3803tj4zCqkf;  Mon, 24 Jan 2022 09:30:08 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Ted Lemon <mellon@fugue.com>, "int-dir@ietf.org" <int-dir@ietf.org>
CC: "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry.all@ietf.org" <draft-ietf-dots-telemetry.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: Intdir last call review of draft-ietf-dots-telemetry-19
Thread-Index: AQHYEKpjLdQ0pTYV0U+C2If2SvOGE6xx1ZRw
Content-Class: 
Date: Mon, 24 Jan 2022 08:30:07 +0000
Message-ID: <12832_1643013008_61EE6390_12832_399_1_787AE7BB302AE849A7480A190F8B9330354855E2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164297769741.21935.5814690155836157029@ietfa.amsl.com>
In-Reply-To: <164297769741.21935.5814690155836157029@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-24T08:22:04Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=1ea5c61d-360f-49a0-bc3a-66db80c7e0ab; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/v-Cq3vuqEsWHEMA9AJyA_NkPfYs>
Subject: Re: [Dots] Intdir last call review of draft-ietf-dots-telemetry-19
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 08:30:16 -0000

SGkgVGVkLCANCg0KTWFueSB0aGFua3MgZm9yIHRoZSByZXZpZXcuIA0KDQpGV0lXLCB5b3VyIHJl
dmlldyB3aWxsIGJlIGFja25vd2xlZGdlZCBpbiB0aGUgbmV4dCB2ZXJzaW9uOiBodHRwczovL2dp
dGh1Yi5jb20vYm91Y2FkYWlyL2RyYWZ0LWRvdHMtdGVsZW1ldHJ5L2Jsb2IvbWFzdGVyL2RyYWZ0
LWlldGYtZG90cy10ZWxlbWV0cnkudHh0IA0KDQpDaGVlcnMsDQpNZWQNCg0KPiAtLS0tLU1lc3Nh
Z2UgZCdvcmlnaW5lLS0tLS0NCj4gRGXCoDogVGVkIExlbW9uIHZpYSBEYXRhdHJhY2tlciA8bm9y
ZXBseUBpZXRmLm9yZz4NCj4gRW52b3nDqcKgOiBkaW1hbmNoZSAyMyBqYW52aWVyIDIwMjIgMjM6
NDINCj4gw4DCoDogaW50LWRpckBpZXRmLm9yZw0KPiBDY8KgOiBkb3RzQGlldGYub3JnOyBkcmFm
dC1pZXRmLWRvdHMtdGVsZW1ldHJ5LmFsbEBpZXRmLm9yZzsgbGFzdC0NCj4gY2FsbEBpZXRmLm9y
Zw0KPiBPYmpldMKgOiBJbnRkaXIgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWRvdHMt
dGVsZW1ldHJ5LTE5DQo+IA0KPiBSZXZpZXdlcjogVGVkIExlbW9uDQo+IFJldmlldyByZXN1bHQ6
IFJlYWR5IHdpdGggTml0cw0KPiANCj4gSSBhbSBhbiBhc3NpZ25lZCBJTlQgZGlyZWN0b3JhdGUg
cmV2aWV3ZXIgZm9yIGRyYWZ0LWlldGYtZG90cy10ZWxlbWV0cnkuDQo+IFRoZXNlIGNvbW1lbnRz
IHdlcmUgd3JpdHRlbiBwcmltYXJpbHkgZm9yIHRoZSBiZW5lZml0IG9mIHRoZSBJbnRlcm5ldA0K
PiBBcmVhIERpcmVjdG9ycy4NCj4gRG9jdW1lbnQgZWRpdG9ycyBhbmQgc2hlcGhlcmQocykgc2hv
dWxkIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlrZQ0KPiB0aGV5IHdvdWxkIHRyZWF0IGNv
bW1lbnRzIGZyb20gYW55IG90aGVyIElFVEYgY29udHJpYnV0b3JzIGFuZCByZXNvbHZlDQo+IHRo
ZW0gYWxvbmcgd2l0aCBhbnkgb3RoZXIgTGFzdCBDYWxsIGNvbW1lbnRzIHRoYXQgaGF2ZSBiZWVu
IHJlY2VpdmVkLg0KPiBGb3IgbW9yZSBkZXRhaWxzIG9uIHRoZSBJTlQgRGlyZWN0b3JhdGUsIHNl
ZQ0KPiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2dyb3VwL2ludGRpci9hYm91dC8NCj4g
PGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZ3JvdXAvaW50ZGlyL2Fib3V0Lz4uDQo+IA0K
PiBJIGRvIG5vdCBzZWUgYW55IGlzc3VlcyBpbiB0aGlzIGRvY3VtZW50IHRoYXQgd291bGQgc3Vn
Z2VzdCB0aGF0IHRoZSBJTlQNCj4gQXJlYSBkaXJlY3RvcnMgc2hvdWxkIG9iamVjdCB0byBpdC4g
VGhlIGRvY3VtZW50IGFwcGVhcnMgdG8gYmUgYQ0KPiBjb21iaW5hdGlvbiBvZiB0aHJlZSB0aGlu
Z3M6IGEgZGVzY3JpcHRpb24gb2YgdGhlIGNvbnRleHQgaW4gd2hpY2ggd2hhdA0KPiBpcyBzcGVj
aWZpZWQgd291bGQgYmUgdXNlZnVsOyBhIGNvbGxlY3Rpb24gb2YgYWR2aWNlIGFib3V0IG9wZXJh
dGlvbmFsDQo+IGNvbnNpZGVyYXRpb25zIHdoZW4gdXNpbmcgd2hhdCBpcyBzcGVjaWZpZWQ7IGFu
ZCBmaW5hbGx5IHRoZSBhY3R1YWwNCj4gc3BlY2lmaWNhdGlvbi4gVG8gdGhlIGJlc3Qgb2YgbXkg
YWJpbGl0eSB0byBldmFsdWF0ZSBpdCwgaXQgc2VlbXMgdG8gYmUNCj4gY29tcGxldGUsIGFuZCBp
dCBzaG91bGQgYmUgcG9zc2libGUgdG8gdXNlIGl0IGFzIGEgYmFzaXMgZm9yIGFuDQo+IGltcGxl
bWVudGF0aW9uLg0KPiANCj4gQWx0aG91Z2ggSSB3b3VsZCBwcmVmZXIgdG8gc2VlIHRoaXMgZG9j
dW1lbnQgcHVibGlzaGVkIGFzIHRocmVlIHNlcGFyYXRlDQo+IGRvY3VtZW50cywgZWFjaCBhZGRy
ZXNzaW5nIG9uZSBvZiB0aGUgYWZvcmVtZW50aW9uZWQgdG9waWNzLCBJIGRvbid0DQo+IHRoaW5r
IHRoYXQncyBhIHJlYXNvbmFibGUgcmVxdWVzdCB0byBtYWtlIGR1cmluZyBsYXN0IGNhbGwuIEFz
IHN1Y2gsIEknbQ0KPiBnb2luZyB0byBzYXkgdGhhdCB0aGUgZG9jdW1lbnQgaXMgcmVhZHkgdG8g
cHVibGlzaCBhcyBpcy4NCj4gDQoNCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCgpDZSBtZXNzYWdlIGV0IHNlcyBwaWVjZXMg
am9pbnRlcyBwZXV2ZW50IGNvbnRlbmlyIGRlcyBpbmZvcm1hdGlvbnMgY29uZmlkZW50aWVsbGVz
IG91IHByaXZpbGVnaWVlcyBldCBuZSBkb2l2ZW50IGRvbmMKcGFzIGV0cmUgZGlmZnVzZXMsIGV4
cGxvaXRlcyBvdSBjb3BpZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMgYXZleiByZWN1IGNl
IG1lc3NhZ2UgcGFyIGVycmV1ciwgdmV1aWxsZXogbGUgc2lnbmFsZXIKYSBsJ2V4cGVkaXRldXIg
ZXQgbGUgZGV0cnVpcmUgYWluc2kgcXVlIGxlcyBwaWVjZXMgam9pbnRlcy4gTGVzIG1lc3NhZ2Vz
IGVsZWN0cm9uaXF1ZXMgZXRhbnQgc3VzY2VwdGlibGVzIGQnYWx0ZXJhdGlvbiwKT3JhbmdlIGRl
Y2xpbmUgdG91dGUgcmVzcG9uc2FiaWxpdGUgc2kgY2UgbWVzc2FnZSBhIGV0ZSBhbHRlcmUsIGRl
Zm9ybWUgb3UgZmFsc2lmaWUuIE1lcmNpLgoKVGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVu
dHMgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIG9yIHByaXZpbGVnZWQgaW5mb3JtYXRpb24gdGhh
dCBtYXkgYmUgcHJvdGVjdGVkIGJ5IGxhdzsKdGhleSBzaG91bGQgbm90IGJlIGRpc3RyaWJ1dGVk
LCB1c2VkIG9yIGNvcGllZCB3aXRob3V0IGF1dGhvcmlzYXRpb24uCklmIHlvdSBoYXZlIHJlY2Vp
dmVkIHRoaXMgZW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBhbmQgZGVs
ZXRlIHRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzLgpBcyBlbWFpbHMgbWF5IGJlIGFs
dGVyZWQsIE9yYW5nZSBpcyBub3QgbGlhYmxlIGZvciBtZXNzYWdlcyB0aGF0IGhhdmUgYmVlbiBt
b2RpZmllZCwgY2hhbmdlZCBvciBmYWxzaWZpZWQuClRoYW5rIHlvdS4KCg==


From nobody Mon Jan 24 01:12:41 2022
Return-Path: <william.panwei@huawei.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD653A2458; Mon, 24 Jan 2022 01:12:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wpsQUELCUBMq; Mon, 24 Jan 2022 01:12:37 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B16E53A0112; Mon, 24 Jan 2022 01:12:28 -0800 (PST)
Received: from fraeml739-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Jj44N2ysMz681Mw; Mon, 24 Jan 2022 17:12:04 +0800 (CST)
Received: from kwepeml500003.china.huawei.com (7.221.188.182) by fraeml739-chm.china.huawei.com (10.206.15.220) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Mon, 24 Jan 2022 10:12:24 +0100
Received: from kwepeml500004.china.huawei.com (7.221.188.141) by kwepeml500003.china.huawei.com (7.221.188.182) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Mon, 24 Jan 2022 17:12:22 +0800
Received: from kwepeml500004.china.huawei.com ([7.221.188.141]) by kwepeml500004.china.huawei.com ([7.221.188.141]) with mapi id 15.01.2308.021;  Mon, 24 Jan 2022 17:12:22 +0800
From: "Panwei (William)" <william.panwei@huawei.com>
To: Valery Smyslov <valery@smyslov.net>, "draft-ietf-dots-multihoming@ietf.org" <draft-ietf-dots-multihoming@ietf.org>, "dots@ietf.org" <dots@ietf.org>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>
Thread-Topic: IPR confirmation for draft-ietf-dots-multihoming-10
Thread-Index: AdgQ454uLlw+cuWkQqqZ6dtJPHivRgAHqm2g
Date: Mon, 24 Jan 2022 09:12:22 +0000
Message-ID: <641149946cc24b858bc1438b915e5712@huawei.com>
References: <003c01d810e4$394e2480$abea6d80$@smyslov.net>
In-Reply-To: <003c01d810e4$394e2480$abea6d80$@smyslov.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.136.99.246]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/uqndoqiklmiG_wMInsESm9H7UGc>
Subject: Re: [Dots] IPR confirmation for draft-ietf-dots-multihoming-10
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 09:12:41 -0000

SGkgVmFsZXJ5LCBhbGwsIA0KDQpJJ20gbm90IGF3YXJlIG9mIGFueSBJUFIgcmVsYXRlZCB0byB0
aGlzIGRyYWZ0Lg0KDQpJIGRvbid0IGtub3cgaWYgdGhlIHJlY29tbWVuZGF0aW9ucyBhcmUgZm9s
bG93ZWQgaW4gdGhlIGV4aXN0aW5nIGltcGxlbWVudGF0aW9ucy4gDQoNClJlZ2FyZHMgJiBUaGFu
a3MhDQpXZWkgUGFuICjFy86wKQ0KDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4g
RnJvbTogVmFsZXJ5IFNteXNsb3YgW21haWx0bzp2YWxlcnlAc215c2xvdi5uZXRdDQo+IFNlbnQ6
IE1vbmRheSwgSmFudWFyeSAyNCwgMjAyMiAxOjM2IFBNDQo+IFRvOiBkcmFmdC1pZXRmLWRvdHMt
bXVsdGlob21pbmdAaWV0Zi5vcmc7IGRvdHNAaWV0Zi5vcmcNCj4gQ2M6IGRvdHMtY2hhaXJzQGll
dGYub3JnDQo+IFN1YmplY3Q6IElQUiBjb25maXJtYXRpb24gZm9yIGRyYWZ0LWlldGYtZG90cy1t
dWx0aWhvbWluZy0xMA0KPiANCj4gSGkgYXV0aG9ycywNCj4gDQo+IHdoaWxlIHByZXBhcmluZyBz
aGVwaGVyZCB3cml0ZS11cCBmb3IgZHJhZnQtaWV0Zi1kb3RzLW11bHRpaG9taW5nLTEwLCBpbg0K
PiBhY2NvcmRhbmNlIHdpdGggQkNQNzggYW5kIEJDUDc5IEkgaGF2ZSB0byBhc2sgYWxsIGF1dGhv
cnMgYW5kIGNvbnRyaWJ1dG9ycw0KPiB3aGV0aGVyIHRoZXkgYXJlIGF3YXJlIG9mIGFueSBJUFIg
cmVnYXJkaW5nIHRoaXMgZG9jdW1lbnQuDQo+IENhbiB5b3UgcGxlYXNlIGNvbmZpcm0gdGhhdCB5
b3UgYXJlIG5vdCBhd2FyZSBvZiBhbnkgSVBSIG9yIGRpc2Nsb3NlIGFueSBJUFINCj4geW91IGFy
ZSBhd2FyZSBvZiB0aGF0IGFyZSBjb25jZXJuZWQgd2l0aCB0aGlzIGRyYWZ0Lg0KPiANCj4gSSdk
IGFsc28gbGlrZSB0byBhc2sgYXV0aG9ycyBhYm91dCBpbXBsZW1lbnRhdGlvbiBzdGF0dXMgb2Yg
dGhlIGRyYWZ0Lg0KPiBBcmUgdGhlcmUgYW55IGltcGxlbWVudGF0aW9ucyB0aGF0IGZvbGxvdyBy
ZWNvbW1lbmRhdGlvbnMgZnJvbSB0aGUNCj4gZHJhZnQgeW91IGFyZSBhd2FyZSBvZj8NCj4gDQo+
IFJlZ2FyZHMsDQo+IFZhbGVyeS4NCg0K


From nobody Mon Jan 24 01:39:40 2022
Return-Path: <jon.shallow@jpshallow.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43D1E3A011D for <dots@ietfa.amsl.com>; Mon, 24 Jan 2022 01:39:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7dvA9huX5xcd for <dots@ietfa.amsl.com>; Mon, 24 Jan 2022 01:39:35 -0800 (PST)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (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 190E23A0113 for <dots@ietf.org>; Mon, 24 Jan 2022 01:39:34 -0800 (PST)
Received: from mail2.jpshallow.com ([192.168.0.3] helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.92.3) (envelope-from <jon.shallow@jpshallow.com>) id 1nBvox-0007Wx-R3; Mon, 24 Jan 2022 09:39:31 +0000
From: <supjps-ietf@jpshallow.com>
To: "Valery Smyslov" <valery@smyslov.net>, <draft-ietf-dots-multihoming@ietf.org>, <dots@ietf.org>
Cc: <dots-chairs@ietf.org>
References: <003c01d810e4$394e2480$abea6d80$@smyslov.net>
In-Reply-To: <003c01d810e4$394e2480$abea6d80$@smyslov.net>
Date: Mon, 24 Jan 2022 09:39:32 -0000
Message-ID: <012501d81106$4a74bc70$df5e3550$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-gb
Thread-Index: AQHqRJPTWlsZx/ONiI+CdVea/RACbaxNgKbA
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/9gGWJAnSsXCRSUww0_L4K99RBdI>
Subject: Re: [Dots] IPR confirmation for draft-ietf-dots-multihoming-10
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 09:39:39 -0000

Hi all,

I'm not aware of any IPR related to this draft.

My implementation does support PA address separation (including splitting PI
address ranges into discrete ranges) to talk to different upstream DOTS
Gateways/DOTS servers, and so different aspects of the different scenarios
are covered.

Regards

Jon

> -----Original Message-----
> From: Valery Smyslov [mailto: valery@smyslov.net]
> Sent: 24 January 2022 05:36
> To: draft-ietf-dots-multihoming@ietf.org; dots@ietf.org
> Cc: dots-chairs@ietf.org
> Subject: [Dots] IPR confirmation for draft-ietf-dots-multihoming-10
> 
> Hi authors,
> 
> while preparing shepherd write-up for draft-ietf-dots-multihoming-10,
> in accordance with BCP78 and BCP79 I have to ask all authors and
> contributors
> whether they are aware of any IPR regarding this document.
> Can you please confirm that you are not aware of any IPR
> or disclose any IPR you are aware of that are concerned with this draft.
> 
> I'd also like to ask authors about implementation status of the draft.
> Are there any implementations that follow recommendations from the draft
> you are aware of?
> 
> Regards,
> Valery.
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots


From nobody Mon Jan 24 02:57:46 2022
Return-Path: <kondtir@gmail.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 312A13A0D06; Mon, 24 Jan 2022 02:57:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 qpK-4cC6RiDu; Mon, 24 Jan 2022 02:57:40 -0800 (PST)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 3CEFE3A0D03; Mon, 24 Jan 2022 02:57:40 -0800 (PST)
Received: by mail-lf1-x136.google.com with SMTP id a28so18239493lfl.7; Mon, 24 Jan 2022 02:57:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KQStoa2FNxNo/J4X7+GgxJHOpA4kkWkzU1jXuFZbfs0=; b=aKpvuCo7tYuajkmhQlMlbfJ+bHfJKUsMf3SzD/P+bt4JSibAl/0ZRCRzlBHGXIIuDM such1Zj9t+OXl6cQ6+g1fDyy7JLDfS+qRo3N/Ff6tNroAePkdgzo9+z4pzVyEfbgm+/K 3jcVEpIrq+t68SJMjFBcHa74uORcEkk6zoOiNM4gz6bJIz4yVdQREyQhK8cKnioVqDg0 0P+b3Bpae1G6s1typhcnTGU2oUMnXwPSaHzCZIrG08EI+HxX0LZ1pSvaeMQUOCswwJ52 Pmq8oUZubQAWcbcvlVl1lwTE3jVaPrww/T9/LTeezvSGOSfnfWRkiJKunHHyVgvFyNDJ POHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KQStoa2FNxNo/J4X7+GgxJHOpA4kkWkzU1jXuFZbfs0=; b=MwL98sVf9ReaxJYC+X365n5Fo8EonC5c+fucOCnaGxRGEEOBcIOXF/XjrK2A+LZQcy 4DByf+RsfLDwho40BnIPMV7lTNMzfjlUxrDkQASZAvTh3p5YuePLNzrqR0/qZ4ozETCo JGQ0FEGAn+C9JYpmce3BugAZgNFU7lzFPf7R7J3HyOcYNSeBOqPd19DRMPk4B1z1Gm47 oRxUtVvJCeOwvMLHmnV+CFKE/ZB8NaItvm+RJFRK1YnNY+X//yXnDtGIxVKZgGjhhaTK Esx5jwJuNUhEX/VIPPw4Csnwlavuu316VDfEp4rm9B2gWUo4y/CCccM3aid3GbMI2WAR wyyQ==
X-Gm-Message-State: AOAM533QX8djfxHEyl8StJr2bJ0yDC4iRFMe4NNVx7VBGuqdqiOt16TI 5YMOQ+MEA+aurMNGyGJTS0hskPUQ4+uyM0alTTVW8+JPiZk=
X-Google-Smtp-Source: ABdhPJxj+HzPPT8eUki6ndRxzxgWzByRoj1tAhEOdGk+YwpCHHaHJE/zcIB3SmgOKX+auY9Dyj1PGOR56AKQy+RgO4E=
X-Received: by 2002:a05:6512:3cb:: with SMTP id w11mr12750500lfp.621.1643021856919;  Mon, 24 Jan 2022 02:57:36 -0800 (PST)
MIME-Version: 1.0
References: <003c01d810e4$394e2480$abea6d80$@smyslov.net>
In-Reply-To: <003c01d810e4$394e2480$abea6d80$@smyslov.net>
From: tirumal reddy <kondtir@gmail.com>
Date: Mon, 24 Jan 2022 16:27:25 +0530
Message-ID: <CAFpG3gf1X_HZjBaBdVBQ2fmW6rg9zwCH7GM4o3qttgbyt=UoFw@mail.gmail.com>
To: Valery Smyslov <valery@smyslov.net>
Cc: draft-ietf-dots-multihoming@ietf.org, dots@ietf.org, dots-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000023d5f405d651d6ac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/xx9dPak-0dX9SuR1QqlPbeJlZSQ>
Subject: Re: [Dots] IPR confirmation for draft-ietf-dots-multihoming-10
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 10:57:45 -0000

--00000000000023d5f405d651d6ac
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I am not aware of any IPR related to this draft and I don=E2=80=99t know if=
 the
draft is implemented by an existing implementation.


Cheers,

-Tiru

On Mon, 24 Jan 2022 at 11:05, Valery Smyslov <valery@smyslov.net> wrote:

> Hi authors,
>
> while preparing shepherd write-up for draft-ietf-dots-multihoming-10,
> in accordance with BCP78 and BCP79 I have to ask all authors and
> contributors
> whether they are aware of any IPR regarding this document.
> Can you please confirm that you are not aware of any IPR
> or disclose any IPR you are aware of that are concerned with this draft.
>
> I'd also like to ask authors about implementation status of the draft.
> Are there any implementations that follow recommendations from the draft
> you are aware of?
>
> Regards,
> Valery.
>
>

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

<div dir=3D"ltr">





<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;">I am not aware of any IPR rela=
ted to this draft and I don=E2=80=99t know if the draft is implemented by a=
n existing implementation.</p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;;min-height:14px"><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;">Cheers,</p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:no=
rmal;font-family:&quot;Helvetica Neue&quot;">-Tiru</p></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, 24 Jan 2022 =
at 11:05, Valery Smyslov &lt;<a href=3D"mailto:valery@smyslov.net">valery@s=
myslov.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">Hi authors,<br>
<br>
while preparing shepherd write-up for draft-ietf-dots-multihoming-10, <br>
in accordance with BCP78 and BCP79 I have to ask all authors and<br>
contributors <br>
whether they are aware of any IPR regarding this document.<br>
Can you please confirm that you are not aware of any IPR <br>
or disclose any IPR you are aware of that are concerned with this draft.<br=
>
<br>
I&#39;d also like to ask authors about implementation status of the draft.<=
br>
Are there any implementations that follow recommendations from the draft <b=
r>
you are aware of?<br>
<br>
Regards,<br>
Valery.<br>
<br>
</blockquote></div>

--00000000000023d5f405d651d6ac--


From nobody Mon Jan 24 03:30:27 2022
Return-Path: <kondtir@gmail.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7F33A0EC3; Mon, 24 Jan 2022 03:30:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 PeG6kBc6dAAQ; Mon, 24 Jan 2022 03:30:20 -0800 (PST)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 892D13A0EC0; Mon, 24 Jan 2022 03:30:20 -0800 (PST)
Received: by mail-lf1-x129.google.com with SMTP id bu18so48559929lfb.5; Mon, 24 Jan 2022 03:30:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZXMnCbFA6N1Rf0wgXAaN2zykQ1Gs1Zk+GKvQWm9Bkzo=; b=ntF3wShuamKUeLWUfUKvqnXKg3qVwR1NeamIBjr9hrr3+Kogl+cUztAi75p00n4i1s an04l04kgJT1At4U9Kx88ocyGXyB8HjWHeTzbBsUD7/2YS7JSYe9EdznvsHz7Ou/+wa0 Rkk8ohzRLxhzRMNI+QIOqZ6GQCv9lWKRSyTN+QWaJE7bEppj6gySR9iuTEov/oqVUjUL FFP9x6KpUU3f0gUYwFt56R2/9UBFqoKssC4vHlwgMdNwEgq6xFSZEpwj8y4PGtQy1F+I UgQVgBJg+ciZIlpuGhT7JbhMe4VzbTT+RzlXfUovMDF4mAm+YfV4iWQJwIuwVreRybI8 zlrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZXMnCbFA6N1Rf0wgXAaN2zykQ1Gs1Zk+GKvQWm9Bkzo=; b=76IPMg4NOmyIx+51dUxXuFyv0in7AsrinADTJVfyQeN9o1CEfUXBeUOFqwoSpSJi0v RWg9gPWlAyZr3IoGriSy1u/61BEl8swMNsQaFfkJS71TjkG1Dr1eyxIaK6BjO+Engut3 kcRe+i6SBlgJK/2mLSF1dZwKAbyIRUrDmVPwTZUUcE1ENHIwvcSoK43qLCSb2FLFb+65 x67H0ztZhkbxp0pwrLKsa0WBONdam6w4p8b9rNKNenacO5gIJQk7w0uFab4GtSvBqWgw h+lCpYpU9ANiQtWROXYLodZu8y1WI4Q7XlYgtwzn803CFwdXlmzJR2MAPpxKKucWtqLw 8sGQ==
X-Gm-Message-State: AOAM531CQABse8YCSSMQFFO5AEdTS57P7RZiICIepOoBTckvKqICUx7U h/NRHNm/2xySc03cNPlledz7HKBcS5ktyASFnd4=
X-Google-Smtp-Source: ABdhPJy5lg819jaek50QmKLfMFIhNhM0ROx3yZHvr1WG9rsxX6vsk+KSMIXQQbUnIhAnOKJDA5xrSvzaQOtrWDa9VmM=
X-Received: by 2002:a05:6512:ba0:: with SMTP id b32mr3452899lfv.122.1643023817701;  Mon, 24 Jan 2022 03:30:17 -0800 (PST)
MIME-Version: 1.0
References: <001301d80bb3$a8afba90$fa0f2fb0$@smyslov.net>
In-Reply-To: <001301d80bb3$a8afba90$fa0f2fb0$@smyslov.net>
From: tirumal reddy <kondtir@gmail.com>
Date: Mon, 24 Jan 2022 17:00:06 +0530
Message-ID: <CAFpG3gfVSUoeVOiwR0njozoOJebrY25EBzY985yXj8dHbQbEZg@mail.gmail.com>
To: Valery Smyslov <valery@smyslov.net>
Cc: dots@ietf.org, dots-chairs@ietf.org,  draft-ietf-dots-robust-blocks@ietf.org
Content-Type: multipart/alternative; boundary="00000000000002fd4105d6524b9e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/IUZHtF3kHY5ozPBk4aSD6vBonY8>
Subject: Re: [Dots] WGLC for draft-ietf-dots-robust-blocks-01
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 11:30:26 -0000

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

I reviewed the draft and it looks good to me. I don't think OSCORE
discussed in the security considerations of draft-ietf-core-new-block is
relevant to this draft.

Cheers,
-Tiru

On Mon, 17 Jan 2022 at 20:35, Valery Smyslov <valery@smyslov.net> wrote:

> Hi,
>
> this message starts a two-week working group last call for
> draft-ietf-dots-robust-blocks-01.
> The WGLC will end on Monday, January 31. Please, review the draft and send
> your comments to the mailing list.
>
> Regards,
> Frank & Valery.
>
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots
>

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

<div dir=3D"ltr"><div>I reviewed the draft and it looks good to me. I don&#=
39;t think OSCORE discussed in the security considerations of draft-ietf-co=
re-new-block is relevant to this draft.=C2=A0</div><div><br></div><div>Chee=
rs,</div><div>-Tiru</div><div><br></div><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Mon, 17 Jan 2022 at 20:35, Valery Smyslov =
&lt;<a href=3D"mailto:valery@smyslov.net">valery@smyslov.net</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
this message starts a two-week working group last call for<br>
draft-ietf-dots-robust-blocks-01.<br>
The WGLC will end on Monday, January 31. Please, review the draft and send<=
br>
your comments to the mailing list.<br>
<br>
Regards,<br>
Frank &amp; Valery.<br>
<br>
_______________________________________________<br>
Dots mailing list<br>
<a href=3D"mailto:Dots@ietf.org" target=3D"_blank">Dots@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dots" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/dots</a><br>
</blockquote></div></div>

--00000000000002fd4105d6524b9e--


From nobody Mon Jan 24 03:50:51 2022
Return-Path: <jon.shallow@jpshallow.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEA753A10AB for <dots@ietfa.amsl.com>; Mon, 24 Jan 2022 03:50:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mq3fVMi8ZR8x for <dots@ietfa.amsl.com>; Mon, 24 Jan 2022 03:50:44 -0800 (PST)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (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 B374F3A10A5 for <dots@ietf.org>; Mon, 24 Jan 2022 03:50:44 -0800 (PST)
Received: from mail2.jpshallow.com ([192.168.0.3] helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.92.3) (envelope-from <jon.shallow@jpshallow.com>) id 1nBxrt-0007dM-5p; Mon, 24 Jan 2022 11:50:41 +0000
From: <supjps-ietf@jpshallow.com>
To: "Valery Smyslov" <valery@smyslov.net>, <dots@ietf.org>
Cc: <draft-ietf-dots-robust-blocks@ietf.org>, <dots-chairs@ietf.org>
References: <001301d80bb3$a8afba90$fa0f2fb0$@smyslov.net>
In-Reply-To: <001301d80bb3$a8afba90$fa0f2fb0$@smyslov.net>
Date: Mon, 24 Jan 2022 11:50:41 -0000
Message-ID: <021f01d81118$9ce6ac40$d6b404c0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-gb
Thread-Index: AQKFePpRuJZYCogUNthCWROf8cD29qsXPJXQ
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/sfcy_o1yCm5E4T-dF_7u0PApldU>
Subject: Re: [Dots] WGLC for draft-ietf-dots-robust-blocks-01
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 11:50:49 -0000

Hi all,

I have re-reviewed the draft as well as being one of the Authors and can
find no issues.

The ability to dynamically configure and negotiate values for the first 4
parameter values has been implemented.

libcoap (outstanding PR) has been updated to support the configuration (the
last 2 parameter values are auto-computed based on the other parameters) as
a part of the work for draft-ietf-core-new-block and my DOTS implement does
the negotiation and pushes the resultant configuration.

Regards

Jon 

> -----Original Message-----
> From: Valery Smyslov [mailto: valery@smyslov.net]
> Sent: 17 January 2022 15:05
> To: dots@ietf.org
> Cc: draft-ietf-dots-robust-blocks@ietf.org; dots-chairs@ietf.org
> Subject: WGLC for draft-ietf-dots-robust-blocks-01
> 
> Hi,
> 
> this message starts a two-week working group last call for
> draft-ietf-dots-robust-blocks-01.
> The WGLC will end on Monday, January 31. Please, review the draft and send
> your comments to the mailing list.
> 
> Regards,
> Frank & Valery.



From nobody Mon Jan 24 04:08:41 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D1733A11AD; Mon, 24 Jan 2022 04:08:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 eZYn7fbiNj_Z; Mon, 24 Jan 2022 04:08:35 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (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 AC3843A11AA; Mon, 24 Jan 2022 04:08:34 -0800 (PST)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr24.francetelecom.fr (ESMTP service) with ESMTPS id 4Jj8011CwVz1y9l;  Mon, 24 Jan 2022 13:08:33 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1643026113; bh=KYCKp27aL+u1eNwBPrrcJynF+WubjmPerh0lTe6F5BU=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=EW7ovYIaZExVGFro6+uVMmID5+x9ktNJbpcYv1E+4X5oVo/I4ghW8ZLr1Nbw5O8SM NCEHgIDVVRR0OOHN2OhJvfrTecvCLLEPK/Lrj9iHD+mo9c3BnOkBibqzbTjPjYU5ug xM5OhqYrfUVLi/8690ruM79ogCJjulh6Y6XWBgBgE+gbOplscY3XtCT1SZe2QlAMOW M76OhqayUYQ1u3Ywm4eXEJjlC6Tfbd0HotKAeI1AWMme3qTAc74cPCnkXo2XA8/vmI pUlgREyc69/Qo9GyrE8wcmidipm2lZg/GggxmhJxVBp9E/U4dMcwpw5ReNBNTCMs/H SxwUS0SVSZ6zQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr07.francetelecom.fr (ESMTP service) with ESMTPS id 4Jj8010LCdzFpWv;  Mon, 24 Jan 2022 13:08:33 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry.all@ietf.org" <draft-ietf-dots-telemetry.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-dots-telemetry-19
Thread-Index: AQHYDxrUPARgPt+tSUepcEEmr7uL1qxx4VpQ
Content-Class: 
Date: Mon, 24 Jan 2022 12:08:32 +0000
Message-ID: <21506_1643026113_61EE96C1_21506_165_1_787AE7BB302AE849A7480A190F8B93303548581B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164280608786.26256.18141980913416166060@ietfa.amsl.com>
In-Reply-To: <164280608786.26256.18141980913416166060@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-24T08:53:08Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=3e324281-e879-4942-9fe2-f7e1a4b93be6; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/PXJEexqyigkPJc_rRG4bjLb-W10>
Subject: Re: [Dots] Genart last call review of draft-ietf-dots-telemetry-19
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 12:08:40 -0000

SGkgUm9iZXJ0LCANCg0KTWFueSB0aGFua3MgZm9yIHRoZSBjYXJlZnVsIHJldmlldy4gDQoNClBs
ZWFzZSBzZWUgaW5saW5lLiANCg0KQ2hlZXJzLA0KTWVkDQoNCj4gLS0tLS1NZXNzYWdlIGQnb3Jp
Z2luZS0tLS0tDQo+IERlwqA6IFJvYmVydCBTcGFya3MgdmlhIERhdGF0cmFja2VyIDxub3JlcGx5
QGlldGYub3JnPg0KPiBFbnZvecOpwqA6IHNhbWVkaSAyMiBqYW52aWVyIDIwMjIgMDA6MDENCj4g
w4DCoDogZ2VuLWFydEBpZXRmLm9yZw0KPiBDY8KgOiBkb3RzQGlldGYub3JnOyBkcmFmdC1pZXRm
LWRvdHMtdGVsZW1ldHJ5LmFsbEBpZXRmLm9yZzsgbGFzdC0NCj4gY2FsbEBpZXRmLm9yZw0KPiBP
YmpldMKgOiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWRvdHMtdGVsZW1l
dHJ5LTE5DQo+IA0KPiBSZXZpZXdlcjogUm9iZXJ0IFNwYXJrcw0KPiBSZXZpZXcgcmVzdWx0OiBS
ZWFkeSB3aXRoIElzc3Vlcw0KPiANCj4gSSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdl
ciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdlbmVyYWwgQXJlYQ0KPiBSZXZpZXcgVGVhbSAoR2VuLUFS
VCkgcmV2aWV3cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkIGJ5IHRoZQ0KPiBJ
RVNHIGZvciB0aGUgSUVURiBDaGFpci4gIFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0
IGxpa2UgYW55DQo+IG90aGVyIGxhc3QgY2FsbCBjb21tZW50cy4NCj4gDQo+IEZvciBtb3JlIGlu
Zm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4gDQo+IDxodHRwczovL3RyYWMuaWV0
Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KPiANCj4gRG9jdW1lbnQ6IGRyYWZ0LWll
dGYtZG90cy10ZWxlbWV0cnktMTkNCj4gUmV2aWV3ZXI6IFJvYmVydCBTcGFya3MNCj4gUmV2aWV3
IERhdGU6IDIwMjItMDEtMjENCj4gSUVURiBMQyBFbmQgRGF0ZTogMjAyMi0wMS0yNA0KPiBJRVNH
IFRlbGVjaGF0IGRhdGU6IE5vdCBzY2hlZHVsZWQgZm9yIGEgdGVsZWNoYXQNCj4gDQo+IFN1bW1h
cnk6IFJlYWR5IGZvciBwdWJsaWNhdGlvbiBhcyBhIFByb3Bvc2VkIFN0YW5kYXJkIFJGQywgYnV0
IHdpdGgNCj4gaXNzdWVzIGFuZCBuaXRzIHRvIGNvbnNpZGVyIGJlZm9yZSBwdWJsaWNhdGlvbg0K
PiANCj4gSXNzdWVzOg0KPiAtLS0tLS0tDQo+IA0KPiBUaGlzIGRvY3VtZW50IHJlbGllcyBoZWF2
aWx5IG9uIHRoZSByZXF1aXJlbWVudHMgaW4gdGhlIERPVFMgc2lnbmFsIGFuZA0KPiBkYXRhIGNo
YW5uZWwgc3BlY2lmaWNhdGlvbnMgKFJGQzkxMzIgYW5kIFJGQzg3ODMpIHNheWluZyBhdXRoZW50
aWNhdGVkDQo+IGVuY3J5cHRpb24gTVVTVCBiZSB1c2VkLiBFeHBsaWNpdGx5IGNhbGxpbmcgdGhh
dCBvdXQgaW4gdGhpcyBkb2N1bWVudCdzDQo+IHNlY3VyaXR5IHNlY3Rpb24gd291bGQgYmUgd29y
dGh3aGlsZS4NCg0KW01lZF0gV2UgZG8gaGF2ZSBwb2ludGVycyB0byB0aGUgcmVsZXZhbnQgc2Vj
dGlvbnMgZnJvbSA5MTMyLzg3ODMgaW4gU2VjdGlvbiAxMy4gV2UgYXZvaWRlZCB0byBleHRyYWN0
IHNwZWNpZmljIHJlcXVpcmVtZW50cyB0byBhdm9pZCB0aGUgY29uZnVzaW9uIHRoYXQgd2UgYXJl
IGNyZWF0aW5nIG5ldyByZXF1aXJlbWVudHMgb3IgdG8gbWlzZ3VpZGUgcmVhZGVycyB0aGF0IG9u
bHkgdGhlICJleHRyYWN0ZWQiIHBhcnRzIGFyZSB3b3J0aCB0byBiZSBjb25zaWRlcmVkLiBUaGF0
4oCZcyBzYWlkLCBhZGRlZCB0aGlzIHNlbnRlbmNlIHRvIGRlc2lnbiBvdmVydmlldyB0byByZW1p
bmQgdGhhdCBzZWN1cmUgY29tbXVuaWNhdGlvbnMgY2hhbm5lbHMgYXJlIHJlcXVpcmVkIGZvciBE
T1RTLiANCg0KPiANCj4gSSBhbSBub3QgYSBZQU5HIERvY3Rvci4gVGhpcyBkb2N1bWVudCBzZWVt
cyB0byBtYWtlIGEgcmVhc29uYWJsZSBidXQNCj4gdW51c3VhbCB1c2Ugb2YgWUFORy4gSSB3b3Vs
ZCByZWFsbHkgbGlrZSB0byBzZWUgWUFORyBEb2N0b3IgcmV2aWV3IG9mIC0NCj4gMTkuDQoNCltN
ZWRdIFRoZSBkZXNpZ24gd2UgaGF2ZSBpbiAtMTkgd2FzIGFscmVhZHkgcmV2aWV3ZWQgYnkgeWFu
Z2RvY3RvcnMuIEZXSVcsIHRoZSBkZXNpZ24gaW4gdGhpcyBleHRlbnNpb24gZm9sbG93cyB0aGUg
b25lIGluIDkxMzIuDQoNCiBJIHdvbmRlciBpZiBpdCB3b3VsZCBiZSBwb3NzaWJsZSB0byBmYWN0
b3Igc29tZSBvZiB0aGUgbW9yZSBnZW5lcmljDQo+IGVudW1zIG91dCBpbnRvIHNvbWV0aGluZyB0
aGF0IGNvdWxkIGJlIHJldXNlZCBlbHNld2hlcmUuDQoNCltNZWRdIFdlIGRvbid0IGhhdmUgdGhh
dCBtdWNoIHR5cGVzICsgd2UgZG9uJ3Qga25vdyBpZiB0aGVzZSB3aWxsIGJlIHJldXNlZC4gRldJ
VywgcmZjODQwNyNzZWN0aW9uLTQuMTIgc2F5cyB0aGUgZm9sbG93aW5nOiANCg0KICAgSWYgYSBz
aWduaWZpY2FudCBudW1iZXIgb2YgZGVyaXZlZCB0eXBlcyBhcmUgZGVmaW5lZCwgYW5kIGl0IGlz
DQogICBhbnRpY2lwYXRlZCB0aGF0IHRoZXNlIGRhdGEgdHlwZXMgd2lsbCBiZSByZXVzZWQgYnkg
bXVsdGlwbGUgbW9kdWxlcywNCiAgIHRoZW4gdGhlc2UgZGVyaXZlZCB0eXBlcyBTSE9VTEQgYmUg
Y29udGFpbmVkIGluIGEgc2VwYXJhdGUgbW9kdWxlIG9yDQogICBzdWJtb2R1bGUsIHRvIGFsbG93
IGVhc2llciByZXVzZSB3aXRob3V0IHVubmVjZXNzYXJ5IGNvdXBsaW5nLg0KDQoNCiBXaHkgZG8g
eW91IHN0b3ANCj4gYXQgZGlzY291cmFnaW5nIHJhdGhlciB0aGFuIGZvcmJpZGRpbmcgc2VydmVy
IGRldmlhdGlvbnM/IFRoZSBwb2ludCBvZiBhDQo+IHNwZWNpZmljYXRpb24gbGlrZSB0aGlzIGlz
IGludGVyb3BlcmFiaWxpdHkuDQoNCltNZWRdIFRoaXMgaXMgYSBwb2ludCB3ZSBkaXNjdXNzZWQg
d2l0aCB0aGUgeWFuZ2RvY3RvcnMgaW4gdGhlIHBhc3QuIEhlcmUgaXMgdGhlIHJlYXNvbmluZzog
DQoNCj09PQ0KPiANCj4gIzYpIGRldmlhdGlvbnMNCj4gDQo+IERldmlhdGlvbnMgYXJlIG5ldmVy
IG1lbnRpb25lZC4gQXJlIGltcGxlbWVudG9ycyBhbGxvd2VkIHRvIGRldmlhdGUNCj4gZnJvbSB0
aGUgcHJvdG9jb2wgaW4gYW55IHdheSwgaWYgZGVjbGFyZWQgdXNpbmcgZGV2aWF0aW9uDQo+IHN0
YXRlbWVudHM/IElmIHNvLCBob3cgd291bGQgYSBjbGllbnQga25vdyBpZiBhIGRldmlhdGVkIG1v
ZGVsIGlzIGluDQo+IHVzZT8NCg0KW01lZF0gU29tZSBjb21tZW50cyBoZXJlOiANCiogQSBjbGll
bnQgaW4gZ2VuZXJhbCBkb2VzIG5vdCBrbm93IHdoYXQgbW9kZWwgaXMgdXNlZCBieSBhIHBlZXIg
YXMgd2hhdCBpdCBzZWVzIGlzIENCT1IuDQoqIEEgc2VydmVyIGNhbiB1c2UgZGlzdGluY3QgZGVm
YXVsdCB2YWx1ZXMgKGUuZy4sIHBlcmNlbnRpbGUgdmFsdWVzKSwgYnV0IHRoaXMgY2FuIGJlIHJl
dHJpZXZlZCBieSBhIGNsaWVudCBkdXJpbmcgdGhlIHRlbGVtZXRyeS1zZXR1cC4gDQoNCk90aGVy
IHRoYW4gdGhhdCwgZGV2aWF0aW9ucyBzaG91bGQgYmUgYXZvaWRlZCBhcyB0aGlzIHdpbGwgaW1w
YWN0IG1lc3NhZ2UgdmFsaWRhdGlvbi4NCj09PQ0KDQo+IA0KPiBJJ20gYSBsaXR0bGUgdW5jb21m
b3J0YWJsZSB3aXRoIHRoZSBwYXNzaXZlbHkgc3RhdGVkIHJlcXVpcmVtZW50IHRvIHVzZQ0KPiBp
ZXRmLWRvdHMtcmVob21pbmcgKGF0ICJjbGllbnRzIGFyZSBhc3N1bWVkIHRvIGZvbGxvdyIpIHdo
aWxlIHRoYXQNCj4gZG9jdW1lbnQgaXMgYW4gSW5mb3JtYXRpdmUgcmVmZXJlbmNlLg0KDQpbTWVk
XSBDaGFuZ2VkIHRoZSB3b3JkaW5nIHRvOiAiQ29uc2lkZXJhdGlvbnMgZm9yIG11bHRpLWhvbWVk
IERPVFMgY2xpZW50cyB0byBzZWxlY3Qgd2hpY2ggLi4uLmFyZSBkaXNjdXNzZWQgaW4gW2lldGYt
ZG90cy1tdWx0aWhvbWluZ10uIiANCg0KPiANCj4gSW4gNi4xLjIsIEknbSBjb25mdXNlZCBieSB0
aGUgcmVxdWlyZW1lbnQgdGhhdCAiJ3RzaWQnIHZhbHVlcyBNVVNUDQo+IGluY3JlYXNlIG1vbm90
b25pY2FsbHkgd2hlbiBhIG5ldyBQVVQgaXMgZ2VuZXJhdGVkIg0KDQpbTWVkXSBUaGUgZnVsbCBj
b250ZXh0IGlzOiANCg0KICAgICAgIiAod2hlbiBhIG5ldyBQVVQgaXMgZ2VuZXJhdGVkDQogICAg
ICAgIGJ5IGEgRE9UUyBjbGllbnQgdG8gY29udmV5IG5ldyBjb25maWd1cmF0aW9uIHBhcmFtZXRl
cnMgZm9yIHRoZQ0KICAgICAgICB0ZWxlbWV0cnkpLiAiDQoNCiBjb21iaW5lZCB3aXRoICJJZg0K
PiB0aGUgZG90IHNlcnZlciBmaW5kcyB0aGUgJ3RzaWQnIHBhcmFtZXRlciB2YWx1ZSBjb252ZXll
ZCBpbiB0aGUgUFVUDQo+IHJlcXVlc3QgaW4gaXRzIGNvbmZpZ3VyYXRpb24gZGF0YSBhbmQgKGl0
KSBoYXMgYWNjZXB0ZWQgdGhlIHVwZGF0ZWQNCj4gY29uZmlndXJhdGlvbiBwYXJhbWV0ZXJzLCBh
IDIuMDQgKENoYW5nZWQpIE1VU1QgYmUgcmV0dXJuZWQiLg0KDQpbTWVkXSB0aGlzIG9uZSBpcyB0
byBjb3ZlciB1cGRhdGluZyB0aGUgY2hhbmdlIG9mIGEgcGFyYW1ldGVyIHRoYXQgd2FzIGFscmVh
ZHkgY29uZmlndXJlZDoNCg0KICAiRE9UUyBjbGllbnRzIHVwZGF0ZSB0aGVpcg0KICAgdGVsZW1l
dHJ5IHNldHVwIGNvbmZpZ3VyYXRpb24gdXBvbiBjaGFuZ2Ugb2YgYSBwYXJhbWV0ZXIgdGhhdCBt
YXkNCiAgIGltcGFjdCBhdHRhY2sgbWl0aWdhdGlvbi4iDQoNCiBXaGF0IGFtIEkNCj4gbWlzc2lu
ZyB0aGF0IHdvdWxkIGFsbG93IGEgUFVUIHdpdGggYSB0c2lkIHRoYXQncyBhbHJlYWR5IGluIHRo
ZQ0KPiBzZXJ2ZXIncyBjb25maWd1cmF0aW9uIGRhdGE/IElzIHRoZXJlIHBlcmhhcHMgbGVmdG92
ZXIgdGVuc2lvbiBoZXJlIGZyb20NCj4gZWFybGllciBkZXNpZ25zIHRoYXQgd2VyZSBjaGFuZ2Vk
Pw0KPiANCj4gQXQgdGhlIGVuZCBvZiA3LjEsIHRoZXJlIGlzIGEgTVVTVCBOT1QgbGV2ZWwgcmVx
dWlyZW1lbnQgYWdhaW5zdA0KPiByZXBlYXRpbmcgYXR0YWNrLWRlc2NyaXB0aW9ucyB0aGF0IGhh
dmUgYmVlbiBwcmV2aW91c2x5IHNlbnQgdG8gYSBwZWVyLg0KPiBJcyBpdCBhbHdheXMgdGhlIGNh
c2UgdGhhdCB3aGVuIHRoZXNlIGRlc2NyaXB0aW9ucyBhcmUgc2VudCwgdGhlIG1lc3NhZ2UNCj4g
dGhleSBhcmUgY29udGFpbmVkIGluIGlzIGFja25vd2xlZGdlZD8NCg0KW01lZF0gVGhlIGV4Y2hh
bmdlIGhhcHBlbnMgb3ZlciBhIHJlbGlhYmxlIHRyYW5zcG9ydC4NCg0KIElmIG5vdCwgY29uc2lk
ZXIgYWRkaW5nDQo+IGRpc2N1c3Npb24gb2YgaG93L3doZXRoZXIgYSBwZWVyIGNhbiBhc2sgZm9y
IGEgZGVzY3JpcHRpb24gd2hlbiBpdCBnZXRzDQo+IGFuIGF0dGFjay1pZCBpdCBkb2Vzbid0IGhh
dmUgYSBkZXNjcmlwdGlvbiBmb3IuDQo+IA0KPiBJbiA3LjIsIHlvdSByZXF1aXJlIGEgZnJlc2hs
eSByZWJvb3RlZCBjbGllbnQgdG8gc2VuZCBhIEdFVCByZXF1ZXN0IHRvDQo+IHJldHJpZXZlIGFj
dGl2ZSAndG1pZCcgdmFsdWVzLiBXaHk/DQoNCltNZWRdIFRoaXMgYWxsb3dzIChhbW5lc2ljKSBj
bGllbnRzIHRvIHJlY292ZXIgc3RhdGUuIFdoZXRoZXIgdGhleSBtYWludGFpbiBhbGwgb3IgYSBz
dWJzZXQgb2YgcmVjb3ZlcmVkIGVudHJpZXMgaXMgdGhlbiBsb2NhbCB0byB0aGUgY2xpZW50IChw
b2xpY3ksIHNhbml0eSBjaGVja3MsIGV0Yy4pLiANCg0KIFdoeSBub3QgbGV0IGl0IGp1c3Qgc2Vu
ZCBhIERFTEVURQ0KPiB3aXRoIG5vICd0bWlkJw0KPiByaWdodCBhd2F5IGlmIHRoYXQncyB3aGF0
IGl0IHdvdWxkIGRvIGFmdGVyIHJlY2VpdmluZyB0aGUgcmVzcG9uc2UgdG8NCj4gdGhlIEdFVCBh
bnlob3c/DQo+IA0KPiBJbiA3LjMgYXQgIlRoZSBQVVQgcmVxdWVzdCBNVVNUIGJlIG1haW50YWlu
ZWQgaW4gYW4gYWN0aXZlIHN0YXRlIiwgeW91DQo+IG1lYW4gdGhlIGNvbmZpZ3VyYXRpb24gdGhh
dCB0aGUgUFVUIGVzdGFibGlzaGVkIG11c3QgYmUga2VwdC4gVGhlIFBVVA0KPiByZXF1ZXN0IGl0
c2VsZiBoYXMgbm8gc3RhdGUgYmV5b25kIGl0cyByZXNwb25zZS4gQ29uc2lkZXIgc2F5aW5nDQo+
IHNvbWV0aGluZyBsaWtlICJUaGUgcHJlLW9yLW9uZ29pbmcgbWl0aWdhdGlvbiByZXF1ZXN0cyBN
VVNUIGJlDQo+IGNvbnNpZGVyZWQgYWN0aXZlIiBpbnN0ZWFkLg0KDQpbTWVkXSBUaGlzIGlzIGJl
dHRlci4gVXBkYXRlZCB0aGUgdGV4dC4gVGhhbmsgeW91Lg0KDQo+IA0KPiBJbiB0aGUgeWFuZyBt
b2R1bGUsIHRoZXJlJ3MgYSByZWZlcmVuY2UgYXQgcGFnZSA3OSB0aGF0IHBvaW50cyB0bw0KPiAi
U2VjdGlvbg0KPiA0LjQuMiBvZiBSRkMgVVVVVS4iIFRoaXMgaXMgdGhlIG9ubHkgb2NjdXJyZW5j
ZSBvZiBVVVVVIGluIHRoZSBkb2N1bWVudCwNCj4gYW5kIGlmIGl0J3MgbWVhbnQgdG8gYmUgcmVw
bGFjZWQgd2l0aCAndGhpcyBSRkMnLCB0aGlzIGRvY3VtZW50IGhhcyBubw0KPiBzZWN0aW9uIDQu
NC4yLg0KDQpbTWVkXSBUaGlzIHJlZmVycyB0byBSRkM5MTMyLiBGaXhlZC4gVGhhbmsgeW91LiAN
Cg0KPiANCj4gTml0czoNCj4gLS0tLS0tLS0tLS0tLS0tDQo+IA0KPiBMYXN0IHBhcmFncmFwaCBv
ZiBpbnRyb2R1Y3Rpb24gYXQgIk5ldmVydGhlbGVzcywgd2hlbi4uIi4gVGhhdCBzZW50ZW5jZQ0K
PiBpcyBwYXJ0aWN1bGFybHkgaGFyZCB0byBwYXJzZSwgcGxlYXNlIHNpbXBsaWZ5IGl0Lg0KDQpb
TWVkXSBDaGFuZ2VkIHRvOiANCg0KIldoZW4gbm8gbGltaXRhdGlvbiBwb2xpY3kgaXMgcHJvdmlk
ZWQgdG8gYSBET1RTIGFnZW50LCBpdCBjYW4gc2lnbmFsIGF2YWlsYWJsZSB0ZWxlbWV0cnkgYXR0
cmlidXRlcyB0byBpdCBwZWVycyBpbiBvcmRlciB0byBvcHRpbWl6ZSB0aGUgb3ZlcmFsbCBtaXRp
Z2F0aW9uIHNlcnZpY2UgcHJvdmlzaW9uZWQgdXNpbmcgRE9UUy4gIg0KDQo+IA0KPiBDdXJpb3Vz
IHRoYXQgeW91IGNhbGxlZCBvdXQgVENQIHBvcnQgODAgaW4gdGhlIGRpc2N1c3Npb24gaW4gMy4z
LiBXaHkNCj4gbm90IDQ0Mz8NCg0KW01lZF0gVGhhdCdzIGp1c3QgYW4gZXhhbXBsZS4gV2UgY291
bGQgdXNlIDQ0MyBhcyB3ZSBkaWQgaW4gOTEzMi4gDQoNCj4gDQo+IEF0IDQuMSwgd2hlcmUgeW91
IHNheSAidGhhdCB0cnVseSByZXF1aXJlIHJlbGlhYmxlIGRlbGl2ZXJ5IiwgSSB0aGluaw0KPiB5
b3UgbWVhbiBzb21ldGhpbmcgbW9yZSBsaWtlICJ0aGF0IGFyZSBpbXBvcnRhbnQgdG8gZGVsaXZl
ciIuIE5vdGhpbmcNCj4gaGVyZSBpcyB0cnlpbmcgdG8gZ3VhcmFudGVlIHJlbGlhYmxlIGRlbGl2
ZXJ5IGFuZCB0aGUgc3RhdGVtZW50IG1pc2xlYWRzDQo+IHRoZSByZWFkZXIgdG8gbG9vayBmb3Ig
cmVsaWFibGUgZGVsaXZlcnkgbWVjaGFuaXNtcy4NCg0KW01lZF0gWWVzLCBmaXhlZC4gDQoNCj4g
DQo+IEluIDQuNSBhdCAiVGhlIHJlYXNvbiBmb3Igbm90IGluY2x1ZGluZyB0aGVzZSBrZXlzLi4u
Ii4gVGhhdCBzZW50ZW5jZQ0KPiBkb2VzIG5vdCBwYXJzZS4gUGxlYXNlIHNpbXBsaWZ5Lg0KDQpb
TWVkXSBDaGFuZ2VkIHRvOg0KDQoiVGhlIHJlYXNvbiBmb3Igbm90IGluY2x1ZGluZyB0aGVzZSBr
ZXlzIGlzIGJlY2F1c2UgdGhleSBhcmUgbm90IGluY2x1ZGVkIGluIHRoZSBtZXNzYWdlIGJvZHkg
b2YgRE9UUyByZXF1ZXN0czsgc3VjaCBrZXlzIGFyZSBpbmNsdWRlZCBhcyBtYW5kYXRvcnkgVXJp
LVBhdGhzIC4uIg0KDQo+IA0KPiBJbiA0LjYsIHRoZSBzZWNvbmQgcGFyYWdyYXBoIGlzIGFib3V0
IHZhbGlkYXRpbmcgbWVzc2FnZXMsIG5vdCBleGFtcGxlcy4NCj4gSXQncyBub3QgY2xlYXIgdGhl
IHBhcmFncmFwaCBpcyB1c2VmdWwgYXMgYSByb2FkbWFwIHRocm91Z2ggdGhlDQo+IGRvY3VtZW50
LiBDb25zaWRlciBkZWxldGluZyBpdC4NCg0KW01lZF0gQWdyZWUuIE1vdmVkIHRvIGEgbmV3IHN1
YnNlY3Rpb24gdW5kZXIgNC4yLg0KDQo+IA0KPiBUaGUgb3V0bGluZSBzdHJ1Y3R1cmUgb2Ygc2Vj
dGlvbiA0IGlzIG9kZC4gVGhlcmUgYXJlIHNldmVyYWwNCj4gQ29uc2lkZXJhdGlvbnMgc3Vic2Vj
dGlvbnMgaW5jbHVkaW5nICJHZW5lcmljIENvbnNpZGVyYXRpb25zIiAod2hpY2ggaXMNCj4gamFy
cmluZyksIGFuZCBzZXZlcmFsIHN1YnNlY3Rpb25zIHRoYXQgYXJlIG5vdCBjb25zaWRlcmF0aW9u
cyBzZWN0aW9ucy4NCj4gSGF2aW5nIHRoZW0gdW5kZXIgYSBzZWN0aW9uIHRpdGxlZCAiRGVzaWdu
IE92ZXJ2aWV3IiBkb2Vzbid0IGhlbHAgcHVsbA0KPiB0aGVtIHRvZ2V0aGVyLiBQZXJoYXBzIGEg
bWlsZCByZXN0cnVjdHVyZS9yZW9yZGVyIHdvdWxkIGJyaW5nIG1vcmUNCj4gY2xhcml0eT8NCg0K
W01lZF0gV2lsbCBzZWUgaWYgdGhlcmUgaXMgYSBiZXR0ZXIgYXBwcm9hY2ggdG8gc3RydWN0dXJl
IHRoYXQgcGFydC4gDQoNCj4gDQo+IEF0IDYuMSwgY29uc2lkZXIgcmVwbGFjaW5nICIod2l0aCBz
dWl0YWJsZSBkZWZhdWx0KS4iIHdpdGggIi4gRGVmYXVsdA0KPiB2YWx1ZXMgYXJlIGRlZmluZWQg
bGF0ZXIgaW4gdGhpcyBzZWN0aW9uLiINCg0KW01lZF0gV2VudCBmb3IgIkRlZmF1bHQgdmFsdWVz
IGFyZSBkZWZpbmVkIGluIFNlY3Rpb24gNi4xLjIuIg0KDQo+IA0KPiBJbiA2LjEgeW91IGNsYWlt
IGNsaWVudHMgY2FuIG5lZ290aWF0ZSBjb25maWd1cmF0aW9uIHBhcmFtZXRlcnMgd2l0aA0KPiBz
ZXJ2ZXIuIEkgZG9uJ3QgZmluZCBhIG5lZ290aWF0aW9uIHByb3RvY29sIHNwZWNpZmllZCBoZXJl
LiBJIHRoaW5rIHlvdQ0KPiBtZWFuIGNsaWVudHMgY2FuIGNvbmZpZ3VyZSBwYXJhbWV0ZXJzIGF0
IGEgc2VydmVycywgYW5kIHNlcnZlcnMgY2FuDQo+IGNvbmZpZ3VyZSBwYXJhbWV0ZXJzIGF0IGEg
Y2xpZW50LiBUaGVyZSdzIG5vdCByZWFsbHkgYSBtZWNoYW5pc20gZm9yIGENCj4gcGVlciB0byBz
YXkgIm5vLCBJIGRvbid0IHRoZSBwZXJjZW50aWxlIGNvbmZpZyB5b3UncmUgdHJ5aW5nIHRvIHNl
dCBhbmQNCj4gSSB3b24ndCBkbyB0aGF0Ii4NCg0KW01lZF0gVGhlcmUgaXMgdGV4dCBzdWNoIGFz
OiANCg0KDQogICAqICBJZiBhbnkgb2YgdGhlIGVuY2xvc2VkIGNvbmZpZ3VyYWJsZSBhdHRyaWJ1
dGUgdmFsdWVzIGFyZSBub3QNCiAgICAgIGFjY2VwdGFibGUgdG8gdGhlIERPVFMgc2VydmVyIChT
ZWN0aW9uIDYuMS4xKSwgNC4yMiAoVW5wcm9jZXNzYWJsZQ0KICAgICAgRW50aXR5KSBNVVNUIGJl
IHJldHVybmVkIGluIHRoZSByZXNwb25zZS4NCg0KICAgICAgVGhlIERPVFMgY2xpZW50IG1heSBy
ZXRyeSBhbmQgc2VuZCB0aGUgUFVUIHJlcXVlc3Qgd2l0aCB1cGRhdGVkDQogICAgICBhdHRyaWJ1
dGUgdmFsdWVzIGFjY2VwdGFibGUgdG8gdGhlIERPVFMgc2VydmVyLg0KDQo+IA0KPiBUaGUgaW50
cm9kdWN0aW9uIG9mICJhIHRoaXJkLXBhcnR5IERPVFMgc2VydmVyIiBpbiB0aGUgbmFycmF0aXZl
IGFmdGVyDQo+IEZpZ3VyZQ0KPiAxMyBpcyBzdXJwcmlzaW5nLiBGb3IgdGhlIHBhcmFncmFwaCB0
byBtYWtlIHNlbnNlLCB0aGUgbWVzc2FnZXMgaW4gdGhlDQo+IGRpc2N1c3Npb24gYmVmb3JlIEZp
Z3VyZSAxMyB3b3VsZCBhbHNvIGhhdmUgdG8gaGF2ZSBnb25lIHRvIHRoYXQgdGhpcmQtDQo+IHBh
cnQgRE9UUyBzZXJ2ZXIuIENvbnNpZGVyIGNhbGxpbmcgb3V0IHRoYXQgdGhlIERPVFMgc2VydmVy
IG1heSBub3QgYmUNCj4gaG9zdGVkIGF0IGFueSBvZiB0aGUgSVNQcyBhdCB0aGUgYmVnaW5uaW5n
IG9mIDYuMi4xIGluc3RlYWQuDQoNCltNZWRdIE9LLg0KDQo+IA0KPiBJbiA2LjIuMSB3aGVyZSB5
b3UgcmVxdWlyZSBzZXJ2ZXJzIHRvIHJlamVjdCBQVVQgcmVxdWVzdHMgd2l0aCAwDQo+IGNhcGFj
aXR5IGZvciBhbGwgaW5jbHVkZWQgbGlua3MsIGNvbnNpZGVyIHNheWluZyAiVXNlIERFTEVURSBp
bnN0ZWFkLiINCj4gTWF5YmUgc2F5IF93aHlfIHlvdSByZXF1aXJlIHRoYXQgUFVUIHRvIGJlIHJl
amVjdGVkLg0KDQpbTWVkXSBPSw0KDQo+IA0KPiBJbiB0aGUgc2VudGVuY2UgYWZ0ZXIgRmlndXJl
IDE5IChhdCBsZWFzdCBpbiB0aGUgdGV4dCB2ZXJzaW9uKSwgeW91IG1lYW4NCj4gdG8gcG9pbnQg
dG8gRmlndXJlIDIwLg0KDQpbTWVkXSBHb29kIGNhdGNoLiBGaXhlZC4gVGhhbmtzLiANCg0KPiAN
Cj4gQXQgNy4xICJET1RTIHRlbGVtZXRyeSBhdHRyaWJ1dGVzIGFyZSBvcHRpb25hbGx5IHNpZ25h
bGVkIGFuZCB0aGVyZWZvcmUNCj4gTVVTVCBOT1QgYmUgdHJlYXRlZCBhcyBtYW5kYXRvcnkgZmll
bGRzIGluIHRoZSBET1RTIHNpZ25hbCBjaGFubmVsDQo+IHByb3RvY29sIiBpcyBhbiBvZGQgdGhp
bmcgdG8gY2FsbCBvdXQgdGhpcyB3YXkuIEkgdGhpbmsgdGhpcyB3YXMNCj4gbWVudGlvbmVkIGlu
IHRoZSBlYXJsaWVyIHlhbmcgZG9jdG9ycyByZXZpZXcgYXMgd2VsbC4gV2h5IGlzIGl0IGhlcmU/
DQoNCltNZWRdIEZhaXIgY29tbWVudC4gVGhhdCB0ZXh0IGlzIHJlZHVuZGFudCB3aXRoIHRoaXMg
b25lICJjb21wcmVoZW5zaW9uLW9wdGlvbmFsIHBhcmFtZXRlcnMiIGluIHRoZSBJQU5BIHNlY3Rp
b24uIERlbGV0ZWQgdGhlIHNlbnRlbmNlIHlvdSBxdW90ZWQuIA0KDQo+IA0KPiBJbiA3LjEuMSBj
b25zaWRlciByZXBsYWNpbmcgInRoZSBzYW1lIGF0dHJpYnV0ZXMiIHdpdGggc2ltcGx5ICJ0aGUN
Cj4gYXR0cmlidXRlcyIuDQoNCltNZWRdIE9LDQoNCj4gDQo+IEluIDcuMS42LCBwbGVhc2UgcmVw
bGFjZSAicmVpdGVyYXRlcyIgd2l0aCAicmVwZWF0cyIuDQo+IA0KDQpbTWVkXSBBQ0suDQoNCj4g
SW4gNy4xLjYsIHBsZWFzZSByZXBsYWNlIHRoZSBwaHJhc2UgIkNvbmNyZXRlbHksICIgd2l0aCAi
QSIuDQoNCltNZWRdIEFDSy4NCg0KDQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwoKQ2UgbWVzc2FnZSBldCBzZXMgcGllY2Vz
IGpvaW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25zIGNvbmZpZGVudGllbGxl
cyBvdSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jCnBhcyBldHJlIGRpZmZ1c2VzLCBl
eHBsb2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3VzIGF2ZXogcmVjdSBj
ZSBtZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyCmEgbCdleHBlZGl0ZXVy
IGV0IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExlcyBtZXNzYWdl
cyBlbGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24sCk9yYW5nZSBk
ZWNsaW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBldGUgYWx0ZXJlLCBk
ZWZvcm1lIG91IGZhbHNpZmllLiBNZXJjaS4KClRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1l
bnRzIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciBwcml2aWxlZ2VkIGluZm9ybWF0aW9uIHRo
YXQgbWF5IGJlIHByb3RlY3RlZCBieSBsYXc7CnRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRl
ZCwgdXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLgpJZiB5b3UgaGF2ZSByZWNl
aXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRl
bGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4KQXMgZW1haWxzIG1heSBiZSBh
bHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZlIGJlZW4g
bW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLgpUaGFuayB5b3UuCgo=


From nobody Mon Jan 24 22:59:07 2022
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BA943A09A4; Mon, 24 Jan 2022 22:58:57 -0800 (PST)
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: dots@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dots@ietf.org
Message-ID: <164309393755.9767.5736764059895478370@ietfa.amsl.com>
Date: Mon, 24 Jan 2022 22:58:57 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/HikKZEXk-u2kzSA-FY6FQ6xsicA>
Subject: [Dots] I-D Action: draft-ietf-dots-telemetry-20.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jan 2022 06:58:58 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the DDoS Open Threat Signaling WG of the IETF.

        Title           : Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
        Authors         : Mohamed Boucadair
                          Tirumaleswar Reddy.K
                          Ehud Doron
                          Meiling Chen
                          Jon Shallow
	Filename        : draft-ietf-dots-telemetry-20.txt
	Pages           : 117
	Date            : 2022-01-24

Abstract:
   This document aims to enrich the DOTS signal channel protocol with
   various telemetry attributes, allowing for optimal Distributed
   Denial-of-Service (DDoS) attack mitigation.  It specifies the normal
   traffic baseline and attack traffic telemetry attributes a DOTS
   client can convey to its DOTS server in the mitigation request, the
   mitigation status telemetry attributes a DOTS server can communicate
   to a DOTS client, and the mitigation efficacy telemetry attributes a
   DOTS client can communicate to a DOTS server.  The telemetry
   attributes can assist the mitigator to choose the DDoS mitigation
   techniques and perform optimal DDoS attack mitigation.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dots-telemetry-20

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


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts



From nobody Tue Jan 25 07:58:03 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 288C23A0D36; Tue, 25 Jan 2022 07:58:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 vjvQbX2iICd4; Tue, 25 Jan 2022 07:57:56 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (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 36AAD3A0D35; Tue, 25 Jan 2022 07:57:56 -0800 (PST)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr26.francetelecom.fr (ESMTP service) with ESMTPS id 4Jjs2B3BHlzyk9; Tue, 25 Jan 2022 16:57:54 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1643126274; bh=kx20xNEovDVCjVp64dFm4cWN05GdAkPph96fvdwJM1s=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=H6hGx6EuwaH9auZIVIgtKprrj75DlaTrJ8lIAgu9Ne/i1F7/qJ6m7+mvI2eLXRNRT YHboXzG6YP+IwDBHJsc+hMl7XM3BEctLxAcYL2Fm7csm/K2gjvABQ9VBz2NMOqvvNI wbrJ4jL3eB/jOrPCMA4EJh9QmpucAlESYb8CxK3xYYhmJRMir0VkziMJ25rL9mozI8 /a8y5b1sQksJQ7CYysdbI9MlGPIVVnV+nZgxD0FSm0qjahn71RXLgqbEw+tSHlL31y oW4F0isXMkS0AaFc1wBHz2R8ezhLxykY1tTLGZkxhUhse0ZFPOT/5lT3PWtdYkLwDq Iali0j7aksf3Q==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr03.francetelecom.fr (ESMTP service) with ESMTPS id 4Jjs2B1g2bzDq89;  Tue, 25 Jan 2022 16:57:54 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: tom petch <daedulus@btconnect.com>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "valery@smyslov.net" <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry@ietf.org" <draft-ietf-dots-telemetry@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
Thread-Index: AQHYDrpzHB/4Y+Z4S7GlhDjJvUTaVKxz6dsg
Content-Class: 
Date: Tue, 25 Jan 2022 15:57:53 +0000
Message-ID: <28167_1643126274_61F01E02_28167_20_1_787AE7BB302AE849A7480A190F8B9330354869F3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164182513674.28016.284174261896096787@ietfa.amsl.com> <61E16D53.7050003@btconnect.com> <29779_1642412120_61E53858_29779_198_1_787AE7BB302AE849A7480A190F8B933035473D6C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <61E69102.2090001@btconnect.com> <20948_1642511112_61E6BB08_20948_182_3_787AE7BB302AE849A7480A190F8B93303547FCE0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <61E80563.5090304@btconnect.com> <16719_1642597004_61E80A8C_16719_95_2_787AE7BB302AE849A7480A190F8B9330354837BA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <61EA9999.1090906@btconnect.com>
In-Reply-To: <61EA9999.1090906@btconnect.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-25T15:53:18Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=dc0f1286-98c3-46f3-bab7-e533b1d41464; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/X-GReAaQYqcLMDTL7vJvjOTsqAg>
Subject: Re: [Dots] Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed Standard
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jan 2022 15:58:01 -0000

Hi Tom,=20

The changes to take into account the outcome of this thread can be seen at =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dots-telemetry-20=20

I highly appreciate your effort to review as much documents in the IETF LC.=
 Big thanks for that. Your review is ACKed in the document.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: tom petch <daedulus@btconnect.com>
> Envoy=E9=A0: vendredi 21 janvier 2022 12:32
> =C0=A0: BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>; last-
> call@ietf.org
> Cc=A0: dots-chairs@ietf.org; valery@smyslov.net; dots@ietf.org; draft-
> ietf-dots-telemetry@ietf.org
> Objet=A0: Re: Last Call: <draft-ietf-dots-telemetry-19.txt> (Distributed
> Denial-of-Service Open Threat Signaling (DOTS) Telemetry) to Proposed
> Standard
>=20
> On 19/01/2022 12:56, mohamed.boucadair@orange.com wrote:
> > Hi Tom,
> >
> > Thank you for checking the changes and sharing your feedback.
> >
> > Please see inline.
> >
> > Cheers,
> > Med
> >
> >> -----Message d'origine-----
> >> De : tom petch <daedulus@btconnect.com> Envoy=E9 : mercredi 19 janvier
> >> 2022 13:35
> >>
> > ...
> >>> ...
> >>>>
> >>>>>> The user has to understand that [Enterprise-Numbers] is the same
> >>>>>> as Private Enterprise Numbers", which may not be apparent;
> >>>>>> consistent terminology is good.
> >>>>>
> >>>>> [Med] Not sure a (which) change is needed. The current text says:
> >>>>
> >>>> In most walks of life, if you have a registry and a private
> >>>> registry, then users will assume that the registry is public and
> >>>> the private registry is private and that there are two separate
> >>>> registries.  Here there is just the one and the correct name is
> >>>> 'Private Enterprise Number' sometimes abbreviated to PEN.  Experts
> >>>> will know that there is no Public Enterprise Number, others will
> >>>> not so I think we should use Private Enterprise Number in all cases
> >>>> and not just Enterprise
> >> Number.
> >>>>
> >>>
> >>> [Med] Went with the following change:
> >>>
> >>> OLD:
> >>>
> >>>>>       vendor-id:  Vendor ID is a security vendor's Enterprise
> >>>>> Number
> >> as
> >>>>>          registered with IANA [Enterprise-Numbers].
> >>>>>
> >>>
> >>> NEW:
> >>>      vendor-id:  Vendor ID is a security vendor's enterprise number
> as
> >>>         registered in the IANA's "Private Enterprise Numbers"
> registry
> >>>         [Enterprise-Numbers].
> >>
> >>
> >> You have still got half a dozen or so uses of 'Enterprise Number' in
> >> the I-D and my preference would be to change them all to 'Private
> >> Enterprise Number'!
> >
> > [Med] No change is made for the other occurrences on purpose. For
> > example,
> >
> >     The examples use the Enterprise Number 32473 defined for
> >     documentation use [RFC5612].
> >
> > no change is made to that text because we want to be consistent with
> existing RFC5612 which says the following:
> >
> >     IANA has updated the registration for Enterprise Number 32473 to
> >     point to this RFC.
> >
> >    As I said before, an expert knows that there is no Public
> >> Enterprise Number, others do not.
> >>
> >
> > [Med] Added this new entry to the terminology section:
> >
> > NEW:
> >     The document uses IANA-assigned Enterprise Numbers.  These numbers
> >     are also known as "Private Enterprise Numbers" and "SMI (Structure
> of
> >     Management Information) Network Management Private Enterprise
> Codes"
> >     [Enterprise-Numbers].
> >
> > Better?
>=20
>=20
> I cannot see us agreeing on this.  The fact that the terminology of
> RFC5612 is not what it might be does not, for me, sanction other such
> glitches.
>=20
> Tom Petch

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Tue Jan 25 16:59:01 2022
Return-Path: <kaduk@mit.edu>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C83C3A1962; Tue, 25 Jan 2022 16:59:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level: 
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=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 Ku6KKY3rIWiR; Tue, 25 Jan 2022 16:58:55 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 595813A1964; Tue, 25 Jan 2022 16:58:55 -0800 (PST)
Received: from mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 20Q0wi6M018647 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 25 Jan 2022 19:58:50 -0500
Date: Tue, 25 Jan 2022 16:58:43 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: mohamed.boucadair@orange.com
Cc: Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-telemetry.all@ietf.org" <draft-ietf-dots-telemetry.all@ietf.org>,  "last-call@ietf.org" <last-call@ietf.org>
Message-ID: <20220126005843.GV11486@mit.edu>
References: <164280608786.26256.18141980913416166060@ietfa.amsl.com> <21506_1643026113_61EE96C1_21506_165_1_787AE7BB302AE849A7480A190F8B93303548581B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <21506_1643026113_61EE96C1_21506_165_1_787AE7BB302AE849A7480A190F8B93303548581B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/d4uIf2n0KQCkisbwtIEwh5WWS5k>
Subject: Re: [Dots] Genart last call review of draft-ietf-dots-telemetry-19
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2022 00:59:00 -0000

Hi Med, Robert,

I echo the thanks to Robert for the review.
A few notes inline (trimming as needed)...

On Mon, Jan 24, 2022 at 12:08:32PM +0000, mohamed.boucadair@orange.com wrote:
> Hi Robert, 
> 
> Many thanks for the careful review. 
> 
> Please see inline. 
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Robert Sparks via Datatracker <noreply@ietf.org>
> > Envoyé : samedi 22 janvier 2022 00:01
> > À : gen-art@ietf.org
> > Cc : dots@ietf.org; draft-ietf-dots-telemetry.all@ietf.org; last-
> > call@ietf.org
> > Objet : Genart last call review of draft-ietf-dots-telemetry-19
> > 
[...]
> > In 6.1.2, I'm confused by the requirement that "'tsid' values MUST
> > increase monotonically when a new PUT is generated"
> 
> [Med] The full context is: 
> 
>       " (when a new PUT is generated
>         by a DOTS client to convey new configuration parameters for the
>         telemetry). "

I think I see how this causes Robert to be confused.
In particular, a PUT is just a single CoAP request, but what we really mean
here is the persistent configuration object on the server that's identified
by the 'tsid'.  So, we should impose the requirement not on a "new PUT"
being generated, but rather that when we allocate a new tsid value for a
new configuration object, we must make that allocation in the monotonic
manner.

>  combined with "If
> > the dot server finds the 'tsid' parameter value conveyed in the PUT
> > request in its configuration data and (it) has accepted the updated
> > configuration parameters, a 2.04 (Changed) MUST be returned".
> 
> [Med] this one is to cover updating the change of a parameter that was already configured:
> 
>   "DOTS clients update their
>    telemetry setup configuration upon change of a parameter that may
>    impact attack mitigation."
> 
>  What am I
> > missing that would allow a PUT with a tsid that's already in the
> > server's configuration data? Is there perhaps leftover tension here from
> > earlier designs that were changed?
> > 
[...]
> > In 7.2, you require a freshly rebooted client to send a GET request to
> > retrieve active 'tmid' values. Why?
> 
> [Med] This allows (amnesic) clients to recover state. Whether they maintain all or a subset of recovered entries is then local to the client (policy, sanity checks, etc.). 

To attempt to expound on this a bit more, the state that the client would
be recovering applies (in some cases) to the entire client domain and not
just the client itself.  There is assumed to be some internal (e.g.,
monitoring or state synchronization) protocol within the domain to identify
the resources needing protection and the corresponding type of state
expected at the DOTS layer.  Deleting all state at the DOTS layer is very
unlikely to be a useful response to a client reboot.  (Which does not
definitively force a strict prohibition on going straight to DELETE without
GET, but it's why I didn't have a problem with the specified behavior.)

-Ben

>  Why not let it just send a DELETE
> > with no 'tmid'
> > right away if that's what it would do after receiving the response to
> > the GET anyhow?
> > 


From nobody Wed Jan 26 06:26:55 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 827193A11D5; Wed, 26 Jan 2022 06:26:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 3MAi_Q1hH7gC; Wed, 26 Jan 2022 06:26:50 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (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 E48443A11CC; Wed, 26 Jan 2022 06:26:49 -0800 (PST)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar23.francetelecom.fr (ESMTP service) with ESMTPS id 4JkQyc011PzBrm9;  Wed, 26 Jan 2022 15:26:48 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1643207208; bh=PTVKSLVHogo84HjISl9eoF9p4IjlsIkTEmt0DfN6MuM=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=F/dPho4Vc85A7U7COZxPUuPy4Wrq5fqp/ER8uY+9hAcv0HIGS/WOOyWeLVJB4scP0 JujkdBUyBBhXEZPsb6XXMHewvAjvjhlqgBFEHxlfHpE11Ho0oWt+AAev0y4ymAPngS nx2rHK4Hymk3r6RU+ahe4eyfVBJryz1W0WKzJx16oMehjV/LCF5lQucQgqu6KXPmJC zHUMuAuMo6B3WZT3x5yx0itPqOCNzhefRc8x4EI/Q2P5ZhQ8nXzzzmihrMvDSgmoTN lvT0/4zlLyvsiva5ACjbWC8bHyMX/8KWygB3YooIhJsLycz1PYJjbgKX6vzgjdG7kq UeM1L3CIlKLGQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar00.francetelecom.fr (ESMTP service) with ESMTPS id 4JkQyb5dyGzCqnc;  Wed, 26 Jan 2022 15:26:47 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Benjamin Kaduk <kaduk@mit.edu>
CC: "last-call@ietf.org" <last-call@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dots-telemetry.all@ietf.org" <draft-ietf-dots-telemetry.all@ietf.org>, "dots@ietf.org" <dots@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
Thread-Topic: [Dots] Genart last call review of draft-ietf-dots-telemetry-19
Thread-Index: AQHYEk/sxauU7vDzkU+2swdyv6P6Eax1Wh3Q
Content-Class: 
Date: Wed, 26 Jan 2022 14:26:46 +0000
Message-ID: <4705_1643207207_61F15A27_4705_162_1_787AE7BB302AE849A7480A190F8B9330354873A2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164280608786.26256.18141980913416166060@ietfa.amsl.com> <21506_1643026113_61EE96C1_21506_165_1_787AE7BB302AE849A7480A190F8B93303548581B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <20220126005843.GV11486@mit.edu>
In-Reply-To: <20220126005843.GV11486@mit.edu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-26T14:17:02Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=8e5a05c1-6a68-4cf9-9948-7e2991aae84a; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/mfSX0mL6tbW3qs_i2qwZEW9E0xI>
Subject: Re: [Dots] Genart last call review of draft-ietf-dots-telemetry-19
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2022 14:26:55 -0000

Hi Ben, all,=20

Thank you for zooming on these two points.=20

Please see below.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: Dots <dots-bounces@ietf.org> De la part de Benjamin Kaduk
> Envoy=E9=A0: mercredi 26 janvier 2022 01:59
> =C0=A0: BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
> Cc=A0: last-call@ietf.org; gen-art@ietf.org; draft-ietf-dots-
> telemetry.all@ietf.org; dots@ietf.org; Robert Sparks
> <rjsparks@nostrum.com>
> Objet=A0: Re: [Dots] Genart last call review of draft-ietf-dots-telemetry-
> 19
>=20
> Hi Med, Robert,
>=20
> I echo the thanks to Robert for the review.
> A few notes inline (trimming as needed)...
>=20
> On Mon, Jan 24, 2022 at 12:08:32PM +0000, mohamed.boucadair@orange.com
> wrote:
> > Hi Robert,
> >
> > Many thanks for the careful review.
> >
> > Please see inline.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De=A0: Robert Sparks via Datatracker <noreply@ietf.org> Envoy=E9=A0:
> > > samedi 22 janvier 2022 00:01 =C0=A0: gen-art@ietf.org Cc=A0:
> > > dots@ietf.org; draft-ietf-dots-telemetry.all@ietf.org; last-
> > > call@ietf.org Objet=A0: Genart last call review of
> > > draft-ietf-dots-telemetry-19
> > >
> [...]
> > > In 6.1.2, I'm confused by the requirement that "'tsid' values MUST
> > > increase monotonically when a new PUT is generated"
> >
> > [Med] The full context is:
> >
> >       " (when a new PUT is generated
> >         by a DOTS client to convey new configuration parameters for
> the
> >         telemetry). "
>=20
> I think I see how this causes Robert to be confused.
> In particular, a PUT is just a single CoAP request, but what we really
> mean here is the persistent configuration object on the server that's
> identified by the 'tsid'.  So, we should impose the requirement not on a
> "new PUT"
> being generated, but rather that when we allocate a new tsid value for a
> new configuration object, we must make that allocation in the monotonic
> manner.
>=20

[Med] We made this change:

OLD:
   tsid:  Telemetry Setup Identifier is an identifier for the DOTS
        telemetry setup configuration data represented as an integer.
        This identifier MUST be generated by DOTS clients.  'tsid'
        values MUST increase monotonically (when a new PUT is generated
        by a DOTS client to convey new configuration parameters for the
        telemetry).

NEW:
   tsid:  Telemetry Setup Identifier is an identifier for the DOTS
        telemetry setup configuration data represented as an integer.
        This identifier MUST be generated by DOTS clients.  'tsid'
        values MUST increase monotonically whenever new configuration
        parameters need to be conveyed by the DOTS client.

(also tweaked a similar text for tmid)

I hope this removes the confusion.=20


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Fri Jan 28 07:50:00 2022
Return-Path: <noreply@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9111E3A18A5; Fri, 28 Jan 2022 07:49:57 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Valery Smyslov via Datatracker <noreply@ietf.org>
To: <kaduk@mit.edu>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: dots-chairs@ietf.org, dots@ietf.org, iesg-secretary@ietf.org, valery@smyslov.net
Message-ID: <164338499757.15034.3641589751238078652@ietfa.amsl.com>
Date: Fri, 28 Jan 2022 07:49:57 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/xfvttVv5LDPi3VIB1P5hrclEdjs>
Subject: [Dots] Publication has been requested for draft-ietf-dots-multihoming-10
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jan 2022 15:49:58 -0000

Valery Smyslov has requested publication of draft-ietf-dots-multihoming-10 as Informational on behalf of the DOTS working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-dots-multihoming/



From nobody Sun Jan 30 05:27:20 2022
Return-Path: <kaname@nttv6.jp>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73ECC3A291D; Sun, 30 Jan 2022 05:27:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.814
X-Spam-Level: 
X-Spam-Status: No, score=-2.814 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.714, 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=nttv6.jp
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 yS8rBIbY5MjR; Sun, 30 Jan 2022 05:27:13 -0800 (PST)
Received: from guri.nttv6.jp (guri.nttv6.jp [IPv6:2402:c800:ff06:136::140]) by ietfa.amsl.com (Postfix) with ESMTP id DA0D13A291E; Sun, 30 Jan 2022 05:27:12 -0800 (PST)
Received: from z.nttv6.jp (z.nttv6.jp [IPv6:2402:c800:ff06:6::f]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id 7D10B25F68D; Sun, 30 Jan 2022 22:27:08 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nttv6.jp; s=20180820;  t=1643549228; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CRbfPULkJwuIzzk8fyma1Qr9Xp0wg1kj1R6JPsbc0XQ=; b=brWWWXL0oWsuNguFtZDwORyNzYZr596TF6QZddxRiYrGnxOM5Alhr6z7Vzegsg6df7FvS1 V6Zohj/lMXLKjkHitmo7uBXnrbE0e6rW65S+b50ZXxbwPhjyRWKyh3yPg8rNxWRGktyiik XKafHuYHZGYc02bwOwD09EaR6hbK6fU=
Received: from [127.0.0.1] (fujiko.nttv6.jp [IPv6:2402:c800:ff06:136::141]) by z.nttv6.jp (NTTv6MTA) with ESMTP id 503B6759007; Sun, 30 Jan 2022 22:27:08 +0900 (JST)
Message-ID: <0bf5f4a8-0c1d-025a-174b-619a786b8a72@nttv6.jp>
Date: Sun, 30 Jan 2022 22:27:08 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.1
Content-Language: en-US
To: supjps-ietf@jpshallow.com, Valery Smyslov <valery@smyslov.net>, dots@ietf.org
Cc: dots-chairs@ietf.org, draft-ietf-dots-robust-blocks@ietf.org
References: <001301d80bb3$a8afba90$fa0f2fb0$@smyslov.net> <021f01d81118$9ce6ac40$d6b404c0$@jpshallow.com>
From: kaname nishizuka <kaname@nttv6.jp>
In-Reply-To: <021f01d81118$9ce6ac40$d6b404c0$@jpshallow.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Authentication-Results: guri.nttv6.jp; spf=pass smtp.mailfrom=kaname@nttv6.jp
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/scPt2jqJ5VcjtqgperCvRgMmb7w>
Subject: Re: [Dots] WGLC for draft-ietf-dots-robust-blocks-01
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jan 2022 13:27:19 -0000

Hi,

I've reviewed the draft.
I found no issue around the specification.

The dynamic configuration and negotiation of the values are not implemented yet on my side(go-dots).
But it'll be a good candidate for the next interop with Jon.

The good news is that in our internal test, it's revealed that QBlock is more robust against certain rate of packet loss compared with normal block option. I will share the test result soon (maybe in the next IETF)

One more thing I'd like to mention is about cache behavior.
I think it can be stated what the cache key should be based on(how it is distinguished/identified).
There is no specific text on draft-ietf-core-new-block (and should not be)
If this draft can include a bit sense about DOTS specific cache strategy, it could get more friendly for implementers.
I'm not sure it's on CoAP side or DOTS side, still though.

Regards,
Kaname


On 2022/01/24 20:50, supjps-ietf@jpshallow.com wrote:
> Hi all,
>
> I have re-reviewed the draft as well as being one of the Authors and can
> find no issues.
>
> The ability to dynamically configure and negotiate values for the first 4
> parameter values has been implemented.
>
> libcoap (outstanding PR) has been updated to support the configuration (the
> last 2 parameter values are auto-computed based on the other parameters) as
> a part of the work for draft-ietf-core-new-block and my DOTS implement does
> the negotiation and pushes the resultant configuration.
>
> Regards
>
> Jon
>
>> -----Original Message-----
>> From: Valery Smyslov [mailto: valery@smyslov.net]
>> Sent: 17 January 2022 15:05
>> To: dots@ietf.org
>> Cc: draft-ietf-dots-robust-blocks@ietf.org; dots-chairs@ietf.org
>> Subject: WGLC for draft-ietf-dots-robust-blocks-01
>>
>> Hi,
>>
>> this message starts a two-week working group last call for
>> draft-ietf-dots-robust-blocks-01.
>> The WGLC will end on Monday, January 31. Please, review the draft and send
>> your comments to the mailing list.
>>
>> Regards,
>> Frank & Valery.
>
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots


From nobody Sun Jan 30 23:56:02 2022
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E01E03A2673; Sun, 30 Jan 2022 23:56:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level: 
X-Spam-Status: No, score=-7.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 qAKS3GYLarCp; Sun, 30 Jan 2022 23:55:56 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (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 0FDAD3A2674; Sun, 30 Jan 2022 23:55:56 -0800 (PST)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr21.francetelecom.fr (ESMTP service) with ESMTPS id 4JnL3G1nKTz5w0G;  Mon, 31 Jan 2022 08:55:54 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1643615754; bh=NAHQXLcSgy53hJ/6eugTHotovDcwkOOlZHqMxbnOuTo=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=lgnMQG3iKKfdL5Ncz5vDRDYsNemFa4oWrv0XqUPIpLq0OCn8ehEoJFnSu4UFARqt2 GnIKailSCjkoZgR463CcvgbebUOcFl7t5OXY20Qu7XQviWReWxMmPhGhf/DW0SBpia IZVigpm5vHXa6rYy4UUMQ+1uTlluV8H5jqvVxBbFa69YlYSGFSjDmwHXEVTT2EUOcL TuGAOcqQsNYIYGBZ7RLvT0ceArOIDTdNgAO3FruqGC7Z6Pl6NR/yNvq+/DkMU98oUs xAC8RLOBCBDLoHnlL9IeegXuCP4ek3HiqPXW3wJcLOAXtEikYqrB5FPn18s17bpEi4 /V+uJMAYiTNZA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr07.francetelecom.fr (ESMTP service) with ESMTPS id 4JnL3G0ynGzFpX2;  Mon, 31 Jan 2022 08:55:54 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: kaname nishizuka <kaname@nttv6.jp>, "dots@ietf.org" <dots@ietf.org>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "draft-ietf-dots-robust-blocks@ietf.org" <draft-ietf-dots-robust-blocks@ietf.org>
Thread-Topic: [Dots] WGLC for draft-ietf-dots-robust-blocks-01
Thread-Index: AQHYFd0g4S+StFV6akOX6tgDbo9znKx8vv2w
Content-Class: 
Date: Mon, 31 Jan 2022 07:55:53 +0000
Message-ID: <4816_1643615754_61F7960A_4816_304_1_787AE7BB302AE849A7480A190F8B9330354895C3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <001301d80bb3$a8afba90$fa0f2fb0$@smyslov.net> <021f01d81118$9ce6ac40$d6b404c0$@jpshallow.com> <0bf5f4a8-0c1d-025a-174b-619a786b8a72@nttv6.jp>
In-Reply-To: <0bf5f4a8-0c1d-025a-174b-619a786b8a72@nttv6.jp>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-31T07:37:19Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=2be932c8-9528-493d-8394-48644185ba61; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/F3bgNHiRM8rkrRJCEDxqX4npdu4>
Subject: Re: [Dots] WGLC for draft-ietf-dots-robust-blocks-01
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jan 2022 07:56:01 -0000

Hi Kaname,=20

Thank you for sharing the comments.=20

We can't specify what cache key will be used as this will depend on used op=
tions (and their types). We may consider adding an example and reason about=
 it, but still that's just an example and can't be generalized. That's why =
my current take on this is to make no change, but more opinions are welcome=
.=20=20=20=20

Looking forward to reading more about the Q-Block tests results.

Cheers,
Med

> -----Message d'origine-----
> De=A0: Dots <dots-bounces@ietf.org> De la part de kaname nishizuka
> Envoy=E9=A0: dimanche 30 janvier 2022 14:27
> =C0=A0: supjps-ietf@jpshallow.com; Valery Smyslov <valery@smyslov.net>;
> dots@ietf.org
> Cc=A0: dots-chairs@ietf.org; draft-ietf-dots-robust-blocks@ietf.org
> Objet=A0: Re: [Dots] WGLC for draft-ietf-dots-robust-blocks-01
>=20
> Hi,
>=20
> I've reviewed the draft.
> I found no issue around the specification.
>=20
> The dynamic configuration and negotiation of the values are not
> implemented yet on my side(go-dots).
> But it'll be a good candidate for the next interop with Jon.
>=20
> The good news is that in our internal test, it's revealed that QBlock is
> more robust against certain rate of packet loss compared with normal
> block option. I will share the test result soon (maybe in the next IETF)
>=20
> One more thing I'd like to mention is about cache behavior.
> I think it can be stated what the cache key should be based on(how it is
> distinguished/identified).
> There is no specific text on draft-ietf-core-new-block (and should not
> be) If this draft can include a bit sense about DOTS specific cache
> strategy, it could get more friendly for implementers.
> I'm not sure it's on CoAP side or DOTS side, still though.
>=20
> Regards,
> Kaname
>=20
>=20
> On 2022/01/24 20:50, supjps-ietf@jpshallow.com wrote:
> > Hi all,
> >
> > I have re-reviewed the draft as well as being one of the Authors and
> > can find no issues.
> >
> > The ability to dynamically configure and negotiate values for the
> > first 4 parameter values has been implemented.
> >
> > libcoap (outstanding PR) has been updated to support the configuration
> > (the last 2 parameter values are auto-computed based on the other
> > parameters) as a part of the work for draft-ietf-core-new-block and my
> > DOTS implement does the negotiation and pushes the resultant
> configuration.
> >
> > Regards
> >
> > Jon
> >
> >> -----Original Message-----
> >> From: Valery Smyslov [mailto: valery@smyslov.net]
> >> Sent: 17 January 2022 15:05
> >> To: dots@ietf.org
> >> Cc: draft-ietf-dots-robust-blocks@ietf.org; dots-chairs@ietf.org
> >> Subject: WGLC for draft-ietf-dots-robust-blocks-01
> >>
> >> Hi,
> >>
> >> this message starts a two-week working group last call for
> >> draft-ietf-dots-robust-blocks-01.
> >> The WGLC will end on Monday, January 31. Please, review the draft and
> >> send your comments to the mailing list.
> >>
> >> Regards,
> >> Frank & Valery.
> >
> > _______________________________________________
> > Dots mailing list
> > Dots@ietf.org
> > https://www.ietf.org/mailman/listinfo/dots
>=20
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Mon Jan 31 03:01:23 2022
Return-Path: <jon.shallow@jpshallow.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1037A3A2C7E for <dots@ietfa.amsl.com>; Mon, 31 Jan 2022 03:01:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g7w3DiIyN_vi for <dots@ietfa.amsl.com>; Mon, 31 Jan 2022 03:01:16 -0800 (PST)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (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 469453A2C7C for <dots@ietf.org>; Mon, 31 Jan 2022 03:01:15 -0800 (PST)
Received: from mail2.jpshallow.com ([192.168.0.3] helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.92.3) (envelope-from <jon.shallow@jpshallow.com>) id 1nEUQq-0004jt-LA; Mon, 31 Jan 2022 11:01:12 +0000
From: <supjps-ietf@jpshallow.com>
To: <mohamed.boucadair@orange.com>, "'kaname nishizuka'" <kaname@nttv6.jp>, <dots@ietf.org>
Cc: <dots-chairs@ietf.org>, <draft-ietf-dots-robust-blocks@ietf.org>
References: <001301d80bb3$a8afba90$fa0f2fb0$@smyslov.net> <021f01d81118$9ce6ac40$d6b404c0$@jpshallow.com> <0bf5f4a8-0c1d-025a-174b-619a786b8a72@nttv6.jp> <4816_1643615754_61F7960A_4816_304_1_787AE7BB302AE849A7480A190F8B9330354895C3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <4816_1643615754_61F7960A_4816_304_1_787AE7BB302AE849A7480A190F8B9330354895C3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Date: Mon, 31 Jan 2022 11:01:11 -0000
Message-ID: <105a01d81691$db5d1850$921748f0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKFePpRuJZYCogUNthCWROf8cD29gHEW+5pAiO2Cb4B8Q8zTqrzW/Vg
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/_kCa4uzdI8RGr4DmIgJasunKfvw>
Subject: Re: [Dots] WGLC for draft-ietf-dots-robust-blocks-01
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jan 2022 11:01:21 -0000

Hi Kaname,

Thanks for the feedback.

The cache-key in general is built from the presented options in the =
request.
Whether an option and its value is included in the cache-key is =
initially
determined from whether the Option is either Unsafe or (Safe-To-Forward =
and
NoCacheKey does not have all the bits set)
https://datatracker.ietf.org/doc/html/rfc7252#section-5.4.6

However, there are exceptions to this.  If you want the cache-key to be =
the
entire body spanning multiple payloads, then you would exclude BLOCK1 =
and
BLOCK2 options form the cache-key, but if you want access to specific
blocks, then you could include BLOCK1 and/or BLOCK2 as a part of the
cache-key definition.  This is hinted at in
https://datatracker.ietf.org/doc/html/rfc7959#section-2.10

Q-BLOCK1 and Q-BLOCK2 are also Critical and Unsafe as are BLOCK1 and =
BLOCK2
respectively.  For a proxy - aka DOTS gateway - for simplicity, it is
expected that the entire body is cached
https://datatracker.ietf.org/doc/html/draft-ietf-core-new-block#section-8=

(i.e. Q-BLOCK1 and Q-BLOCK2 are not a part of the cache-key).

I don=92t think anything extra needs to be added to dots-robust-blocks
regarding DOTS specific caching requirements as this draft is all about
tuning (should it be needed, but unlikely and not recommended unless you
really know what you are doing and have done lots of robustness testing) =
how
Q-Blocks work.  There was only one change to the recommended default =
CoAP
transmission parameters (MAX_RETRANSMIT changed from 4 to 3) as there =
were
timeout issues on lossy networks
https://datatracker.ietf.org/doc/html/rfc9132#section-4.5.2=20

Regards

Jon
> -----Original Message-----
> From: mohamed.boucadair@orange.com =
[mailto:mohamed.boucadair@orange.com]
> Sent: 31 January 2022 07:56
> To: kaname nishizuka; dots@ietf.org
> Cc: dots-chairs@ietf.org; draft-ietf-dots-robust-blocks@ietf.org
> Subject: Re: [Dots] WGLC for draft-ietf-dots-robust-blocks-01
>=20
> Hi Kaname,
>=20
> Thank you for sharing the comments.
>=20
> We can't specify what cache key will be used as this will depend on =
used
> options (and their types). We may consider adding an example and =
reason
> about it, but still that's just an example and can't be generalized.
That's why my
> current take on this is to make no change, but more opinions are =
welcome.
>=20
> Looking forward to reading more about the Q-Block tests results.
>=20
> Cheers,
> Med
>=20
> > -----Message d'origine-----
> > De=A0: Dots <dots-bounces@ietf.org> De la part de kaname nishizuka
> > Envoy=E9=A0: dimanche 30 janvier 2022 14:27
> > =C0=A0: supjps-ietf@jpshallow.com; Valery Smyslov =
<valery@smyslov.net>;
> > dots@ietf.org
> > Cc=A0: dots-chairs@ietf.org; draft-ietf-dots-robust-blocks@ietf.org
> > Objet=A0: Re: [Dots] WGLC for draft-ietf-dots-robust-blocks-01
> >
> > Hi,
> >
> > I've reviewed the draft.
> > I found no issue around the specification.
> >
> > The dynamic configuration and negotiation of the values are not
> > implemented yet on my side(go-dots).
> > But it'll be a good candidate for the next interop with Jon.
> >
> > The good news is that in our internal test, it's revealed that =
QBlock is
> > more robust against certain rate of packet loss compared with normal
> > block option. I will share the test result soon (maybe in the next =
IETF)
> >
> > One more thing I'd like to mention is about cache behavior.
> > I think it can be stated what the cache key should be based on(how =
it is
> > distinguished/identified).
> > There is no specific text on draft-ietf-core-new-block (and should =
not
> > be) If this draft can include a bit sense about DOTS specific cache
> > strategy, it could get more friendly for implementers.
> > I'm not sure it's on CoAP side or DOTS side, still though.
> >
> > Regards,
> > Kaname
> >
> >
> > On 2022/01/24 20:50, supjps-ietf@jpshallow.com wrote:
> > > Hi all,
> > >
> > > I have re-reviewed the draft as well as being one of the Authors =
and
> > > can find no issues.
> > >
> > > The ability to dynamically configure and negotiate values for the
> > > first 4 parameter values has been implemented.
> > >
> > > libcoap (outstanding PR) has been updated to support the =
configuration
> > > (the last 2 parameter values are auto-computed based on the other
> > > parameters) as a part of the work for draft-ietf-core-new-block =
and my
> > > DOTS implement does the negotiation and pushes the resultant
> > configuration.
> > >
> > > Regards
> > >
> > > Jon
> > >
> > >> -----Original Message-----
> > >> From: Valery Smyslov [mailto: valery@smyslov.net]
> > >> Sent: 17 January 2022 15:05
> > >> To: dots@ietf.org
> > >> Cc: draft-ietf-dots-robust-blocks@ietf.org; dots-chairs@ietf.org
> > >> Subject: WGLC for draft-ietf-dots-robust-blocks-01
> > >>
> > >> Hi,
> > >>
> > >> this message starts a two-week working group last call for
> > >> draft-ietf-dots-robust-blocks-01.
> > >> The WGLC will end on Monday, January 31. Please, review the draft =
and
> > >> send your comments to the mailing list.
> > >>
> > >> Regards,
> > >> Frank & Valery.
> > >
> > > _______________________________________________
> > > Dots mailing list
> > > Dots@ietf.org
> > > https://www.ietf.org/mailman/listinfo/dots
> >
> > _______________________________________________
> > Dots mailing list
> > Dots@ietf.org
> > https://www.ietf.org/mailman/listinfo/dots
>=20
> ___________________________________________________________________
> ______________________________________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
recu ce
> message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les =
messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, =
deforme ou
> falsifie. Merci.
>=20
> This message and its attachments may contain confidential or =
privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and
delete this
> message and its attachments.
> As emails may be altered, Orange is not liable for messages that have =
been
> modified, changed or falsified.
> Thank you.
>=20
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots


From nobody Mon Jan 31 12:38:09 2022
Return-Path: <noreply@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 200643A16EA; Mon, 31 Jan 2022 12:38:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dots-telemetry@ietf.org, dots-chairs@ietf.org, dots@ietf.org, valery@smyslov.net, valery@smyslov.net
X-Test-IDTracker: no
X-IETF-IDTracker: 7.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <164366148160.3866.16890109548673178465@ietfa.amsl.com>
Date: Mon, 31 Jan 2022 12:38:02 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/FnmR5EAJfFx96AOpgov_tV9xtEU>
Subject: [Dots] Roman Danyliw's Discuss on draft-ietf-dots-telemetry-20: (with DISCUSS and COMMENT)
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jan 2022 20:38:02 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-dots-telemetry-20: 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/blog/handling-iesg-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/



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

** Sections 8.1.5 and 9.1. These sections describe a human readable text field,
“attack-description”.  Per Section 4.2 of BCP 18, “[p]rotocols that transfer
text MUST provide for carrying information about the language of that text.”. 
Practically, can a field to list a language tag field (RFC 5646 and
https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry)
be added in all places that “attack-description” is defined or at the top level?


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

Authors: thank you for the clarifying language in Section 4.4 explaining how
the design of mapping YANG into CBOR

** Section 4.4.  Per “Server deviations are strongly discouraged …”, what kind
of “deviations” are being referenced here?  Is it the use of NETCONF/RESTCONF?

** Section 8.1.6.  An attack type appears to be characterized by a vendor-id,
vendor-name, last-updated, attack-id and attack-description.  Would an
additional field of attack-id-revision (or attack-id-version) be beneficial
too?  I’m imagining a workflow where a vendor’s definition of an attack (and
the associated detection rule/logic) changes overtime and it might be useful to
version that – akin to the snort/suricata’s “rev:” field.  A vendor could of
course assign a new attack-id but this might impact down-stream analysis.

A few editorial suggestions to consider:

** Section 1.  Editorial.  s/more complex and hard to/more complex and harder
to/

** Section 1.  Editorial
These attacks are assembled from dynamic attack vectors
   (Network/Application) and tactics.  As such, multiple attack vectors
   formed by multiple attack types and volumes are launched
   simultaneously towards a victim.

What is the difference between the first and the second sentence?

** Section 1.  Per “The conclusion derived from these real scenarios is that
modern …”, what are these “real” scenarios?

** Section 2.  Typo. s/whike/while/

** Section 2.  Typo. s/to be considered to be/considered to be/

** Section 3.1.  It seems like much of this information is a re-statement of
what was said in Section 1.  Does it need to be said twice?

** Section 3.1.  “Machine learning approaches …”, do you mean statistical and
artificial intelligence algorithms? ML is only a particular approach.

** Section 4.1.  Per “Telemetry information has aspects …”, this sentence if
very long and difficult to parse.  Could it be split up for improved
readability?

** Section 8.1.4.  typo.  s/subattributes/sub-attributes/

** Section 11.1.  Typo. s/extremly/extremely/



