
From nobody Thu Nov  1 14:13:06 2018
Return-Path: <rjsparks@nostrum.com>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 75925127B92; Thu,  1 Nov 2018 14:13:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Cc: clue@ietf.org, ietf@ietf.org, draft-ietf-clue-signaling.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154110678434.25382.16163243596596461379@ietfa.amsl.com>
Date: Thu, 01 Nov 2018 14:13:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/ZS1DizQXKyQwn4jvfj0PyhR7HQ0>
Subject: [clue] Genart telechat review of draft-ietf-clue-signaling-14
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2018 21:13:05 -0000

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

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

Document: draft-ietf-clue-signaling-14
Reviewer: Robert Sparks
Review Date: 2018-11-01
IETF LC End Date: 2018-10-17
IESG Telechat date: 2018-11-21

Summary: Ready for publication as a Proposed Standard



From nobody Fri Nov  2 05:53:03 2018
Return-Path: <roni.even@huawei.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B231B124408; Fri,  2 Nov 2018 05:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8IzEg3-oAzHz; Fri,  2 Nov 2018 05:52:54 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 68E30123FFD; Fri,  2 Nov 2018 05:52:54 -0700 (PDT)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 3D19DF813317; Fri,  2 Nov 2018 12:52:50 +0000 (GMT)
Received: from DGGEMM402-HUB.china.huawei.com (10.3.20.210) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 2 Nov 2018 12:52:51 +0000
Received: from DGGEMM526-MBX.china.huawei.com ([169.254.8.186]) by DGGEMM402-HUB.china.huawei.com ([10.3.20.210]) with mapi id 14.03.0415.000; Fri, 2 Nov 2018 20:52:46 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
CC: "clue-chairs@ietf.org" <clue-chairs@ietf.org>, "clue@ietf.org" <clue@ietf.org>, "draft-ietf-clue-protocol@ietf.org" <draft-ietf-clue-protocol@ietf.org>
Thread-Topic: =?utf-8?B?W2NsdWVdIE1pcmphIEvDvGhsZXdpbmQncyBEaXNjdXNzIG9uIGRyYWZ0LWll?= =?utf-8?Q?tf-clue-protocol-17:_(with_DISCUSS_and_COMMENT)?=
Thread-Index: AQHUcVBilQ2Ni2nLI0qDoEse3sOvUKU8cqUw
Date: Fri, 2 Nov 2018 12:52:45 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD13044718@dggemm526-mbx.china.huawei.com>
References: <154101430593.5389.2663125960619308709.idtracker@ietfa.amsl.com>
In-Reply-To: <154101430593.5389.2663125960619308709.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.126.174.212]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/btVTnWp_CmsFbdchiKjWRNxrOaE>
Subject: Re: [clue]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-ietf-?= =?utf-8?q?clue-protocol-17=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Nov 2018 12:52:57 -0000

SGkgTWlyamEsDQpUaGFua3MgZm9yIHRoZSByZXZpZXcuDQpUaGUgcHJvdG9jb2wgZG9jdW1lbnQg
ZGVzY3JpYmVzIHRoZSBjbHVlIHByb3RvY29sLiBUaGUgZXN0YWJsaXNobWVudCBvZiB0aGUgZGF0
YSBjaGFubmVsIGlzIGRpc2N1c3NlZCBpbiB0aGUgc2lnbmFsaW5nIHByb3RvY29sICBodHRwczov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1jbHVlLXNpZ25hbGluZy0xNCANCg0KVGhl
IGludHJvZHVjdGlvbiBzYXlzDQoNCkNMVUUtY2FwYWJsZSBlbmRwb2ludHMgYXJlIGNvbm5lY3Rl
ZCBieSBtZWFucyBvZiB0aGUgQ0xVRSBkYXRhDQogICBjaGFubmVsLCBhbiBTQ1RQIG92ZXIgRFRM
UyBjaGFubmVsIHdoaWNoIGlzIG9wZW5lZCBhbmQgZXN0YWJsaXNoZWQgYXMNCiAgIGRlc2NyaWJl
ZCBpbiBbSS1ELmlldGYtY2x1ZS1zaWduYWxpbmddIGFuZA0KICAgW0ktRC5pZXRmLWNsdWUtZGF0
YWNoYW5uZWxdLiAgQ0xVRSBwcm90b2NvbCBtZXNzYWdlcyBmbG93aW5nIG92ZXINCiAgIHN1Y2gg
YSBjaGFubmVsIGFyZSBkZXRhaWxlZCBpbiB0aGlzIGRvY3VtZW50LCBib3RoIHN5bnRhY3RpY2Fs
bHkgYW5kDQogICBzZW1hbnRpY2FsbHkuDQoNClJvbmkgRXZlbg0KDQotLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KRnJvbTogY2x1ZSBbbWFpbHRvOmNsdWUtYm91bmNlc0BpZXRmLm9yZ10gT24g
QmVoYWxmIE9mIE1pcmphIEvDvGhsZXdpbmQNClNlbnQ6IFRodXJzZGF5LCBOb3ZlbWJlciAwMSwg
MjAxOCAyOjMyIEFNDQpUbzogVGhlIElFU0cNCkNjOiBjbHVlLWNoYWlyc0BpZXRmLm9yZzsgY2x1
ZUBpZXRmLm9yZzsgZHJhZnQtaWV0Zi1jbHVlLXByb3RvY29sQGlldGYub3JnDQpTdWJqZWN0OiBb
Y2x1ZV0gTWlyamEgS8O8aGxld2luZCdzIERpc2N1c3Mgb24gZHJhZnQtaWV0Zi1jbHVlLXByb3Rv
Y29sLTE3OiAod2l0aCBESVNDVVNTIGFuZCBDT01NRU5UKQ0KDQpNaXJqYSBLw7xobGV3aW5kIGhh
cyBlbnRlcmVkIHRoZSBmb2xsb3dpbmcgYmFsbG90IHBvc2l0aW9uIGZvcg0KZHJhZnQtaWV0Zi1j
bHVlLXByb3RvY29sLTE3OiBEaXNjdXNzDQoNCldoZW4gcmVzcG9uZGluZywgcGxlYXNlIGtlZXAg
dGhlIHN1YmplY3QgbGluZSBpbnRhY3QgYW5kIHJlcGx5IHRvIGFsbCBlbWFpbCBhZGRyZXNzZXMg
aW5jbHVkZWQgaW4gdGhlIFRvIGFuZCBDQyBsaW5lcy4gKEZlZWwgZnJlZSB0byBjdXQgdGhpcyBp
bnRyb2R1Y3RvcnkgcGFyYWdyYXBoLCBob3dldmVyLikNCg0KDQpQbGVhc2UgcmVmZXIgdG8gaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvaWVzZy9zdGF0ZW1lbnQvZGlzY3Vzcy1jcml0ZXJpYS5odG1sDQpm
b3IgbW9yZSBpbmZvcm1hdGlvbiBhYm91dCBJRVNHIERJU0NVU1MgYW5kIENPTU1FTlQgcG9zaXRp
b25zLg0KDQoNClRoZSBkb2N1bWVudCwgYWxvbmcgd2l0aCBvdGhlciBiYWxsb3QgcG9zaXRpb25z
LCBjYW4gYmUgZm91bmQgaGVyZToNCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LWlldGYtY2x1ZS1wcm90b2NvbC8NCg0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkRJU0NVU1M6DQot
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tDQoNClRoaXMgZG9jdW1lbnQgZG9lcyBub3QgZGlzY3VzcyBhbnkgaW50ZXJh
Y3Rpb25zIHdpdGggdGhlIHRyYW5zcG9ydCBwcm90b2NvbCAoZS5nLiB3aG8gZXN0YWJsaXNoZXMg
dGhlIGNvbm5lY3Rpb24/IHdoYXQgaGFwcGVucyBpZiB0aGUgY29ubmVjdGlvbnMgYnJlYWtzOyB3
aG8gc2hvdWxkIHJlLWVzdGFibGlzaD8pLiBBbHNvLCBJIGFzc3VtZSB0aGF0IFNDVFAgaXMgdXNl
ZCAoaW5zdGVhZCBvZiBUQ1ApIGJlY2F1c2UgdGhlIGlkZWEgaXMgdG8gdXNlIGRpZmZlcmVudCBT
Q1RQIHN0cmVhbXMgZm9yIHRoZSBkaWZmZXJlbnQgZGlyZWN0aW9ucyBvZiB0aGUgY29tbXVuaWNh
dGlvbi4uLj8gSG93ZXZlciwgdGhpcyBpcyBhIGNvbXBsZXRlIGd1ZXNzLCBhcyB0aGUgZG9jdW1l
bnQgZG9lcyB1bmZvcnR1bmF0ZWx5IG5vdCBzYXkgbm90aGluZyBhYm91dCB0aGUgbWFwcGluZyBv
ZiBDTFVFIG1lc3NhZ2VzIHRvIFNDVFAgc2Vzc2lvbnMuIEluIGNhc2UgYWxsIG1lc3NhZ2UgYXJl
IGFzc3VtZWQgdG8gYmUgc2VuZCBvdmVyIHRoZSBzYW1lIHN0cmVhbSBpbnN0ZWFkLCB3aHkgaXMg
U0NUUCB1c2VkIGFuZCBub3QgVENQPyBQbGVhc2UgcHJvdmlkZSBtb3JlIGluZm9ybWF0aW9uIGFu
ZCBndWlkYW5jZSBvbiB0aGUgdXNlIG9mIFNDVFAhDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KQ09NTUVO
VDoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCg0KVHdvIG1pbm9yIGVkaXRvcmlhbCBjb21tZXRzOg0KDQoxKSBJ
biB0aGUgdGVybWlub2xvZ3kgc2VjdGlvbjogV2hhdCBkb2VzIE1DVSBhY3R1YWxseSBzdGFuZCBm
b3I/DQoNCjIpIHNlYyA0Og0KIkNMVUUgcHJvdG9jb2wgdmVyc2lvbiBudW1iZXJzIGFyZQ0KICAg
Y2hhcmFjdGVyaXplZCBieSBhIG1ham9yIHZlcnNpb24gbnVtYmVyIChzaW5nbGUgZGlnaXQpIGFu
ZCBhIG1pbm9yDQogICB2ZXJzaW9uIG51bWJlciAoc2luZ2xlIGRpZ2l0KS4uLiINCkhvd2V2ZXIs
IGxhdGVyIG9uIHRoZSB0ZXh0IHNheXMgdGhhdCB0aGUgbnVtYmVycyBjYW4gYWxzbyBjb25zaXN0
IG9mIG11bHRpcGxlIGRpZ2l0cy4uLg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQpjbHVlIG1haWxpbmcgbGlzdA0KY2x1ZUBpZXRmLm9yZw0KaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9jbHVlDQo=


From nobody Sun Nov  4 01:11:39 2018
Return-Path: <ietf@kuehlewind.net>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3170F130DCF; Sun,  4 Nov 2018 01:11:31 -0700 (PDT)
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, 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 1TwTj6u6OC3a; Sun,  4 Nov 2018 01:11:28 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 96649127133; Sun,  4 Nov 2018 01:11:25 -0700 (PDT)
Received: from static-146-88-49-66.violin.co.th ([146.88.49.66] helo=[172.27.14.52]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1gJDVA-0004K9-7Q; Sun, 04 Nov 2018 09:11:20 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD13044718@dggemm526-mbx.china.huawei.com>
Date: Sun, 4 Nov 2018 15:11:12 +0700
Cc: The IESG <iesg@ietf.org>, "clue-chairs@ietf.org" <clue-chairs@ietf.org>, "clue@ietf.org" <clue@ietf.org>, "draft-ietf-clue-protocol@ietf.org" <draft-ietf-clue-protocol@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <11FAC9A1-1007-44BC-920F-BB033B60EA88@kuehlewind.net>
References: <154101430593.5389.2663125960619308709.idtracker@ietfa.amsl.com> <6E58094ECC8D8344914996DAD28F1CCD13044718@dggemm526-mbx.china.huawei.com>
To: "Roni Even (A)" <roni.even@huawei.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1541319088;2ab7c0f5;
X-HE-SMSGID: 1gJDVA-0004K9-7Q
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/AvxQXH0zW0_ms7nJh8lioyGoQ-I>
Subject: Re: [clue]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-ietf-?= =?utf-8?q?clue-protocol-17=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2018 08:11:31 -0000

Yes, I saw this right after I pushed the send button and already revised =
my position. Thanks for the pointer and sorry for the noise.


> Am 02.11.2018 um 19:52 schrieb Roni Even (A) <roni.even@huawei.com>:
>=20
> Hi Mirja,
> Thanks for the review.
> The protocol document describes the clue protocol. The establishment =
of the data channel is discussed in the signaling protocol  =
https://tools.ietf.org/html/draft-ietf-clue-signaling-14=20
>=20
> The introduction says
>=20
> CLUE-capable endpoints are connected by means of the CLUE data
>   channel, an SCTP over DTLS channel which is opened and established =
as
>   described in [I-D.ietf-clue-signaling] and
>   [I-D.ietf-clue-datachannel].  CLUE protocol messages flowing over
>   such a channel are detailed in this document, both syntactically and
>   semantically.
>=20
> Roni Even
>=20
> -----Original Message-----
> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Mirja =
K=C3=BChlewind
> Sent: Thursday, November 01, 2018 2:32 AM
> To: The IESG
> Cc: clue-chairs@ietf.org; clue@ietf.org; =
draft-ietf-clue-protocol@ietf.org
> Subject: [clue] Mirja K=C3=BChlewind's Discuss on =
draft-ietf-clue-protocol-17: (with DISCUSS and COMMENT)
>=20
> Mirja K=C3=BChlewind has entered the following ballot position for
> draft-ietf-clue-protocol-17: Discuss
>=20
> 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.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-clue-protocol/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>=20
> This document does not discuss any interactions with the transport =
protocol (e.g. who establishes the connection? what happens if the =
connections breaks; who should re-establish?). Also, I assume that SCTP =
is used (instead of TCP) because the idea is to use different SCTP =
streams for the different directions of the communication...? However, =
this is a complete guess, as the document does unfortunately not say =
nothing about the mapping of CLUE messages to SCTP sessions. In case all =
message are assumed to be send over the same stream instead, why is SCTP =
used and not TCP? Please provide more information and guidance on the =
use of SCTP!
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> Two minor editorial commets:
>=20
> 1) In the terminology section: What does MCU actually stand for?
>=20
> 2) sec 4:
> "CLUE protocol version numbers are
>   characterized by a major version number (single digit) and a minor
>   version number (single digit)..."
> However, later on the text says that the numbers can also consist of =
multiple digits...
>=20
>=20
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue


From nobody Sun Nov 18 20:11:06 2018
Return-Path: <wangzitao@huawei.com>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C7E812D4EE; Sun, 18 Nov 2018 20:11:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Zitao Wang <wangzitao@huawei.com>
To: <ops-dir@ietf.org>
Cc: clue@ietf.org, ietf@ietf.org, draft-ietf-clue-protocol.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.88.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154260066457.2434.9338339513625969422@ietfa.amsl.com>
Date: Sun, 18 Nov 2018 20:11:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/MYs2Pl1aEr3xsJloWYr8CT3vOXo>
Subject: [clue] Opsdir last call review of draft-ietf-clue-protocol-17
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 04:11:04 -0000

Reviewer: Zitao Wang
Review result: Ready

I have reviewed this document as part of the Operational directorate’s ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments. Document reviewed:
 draft-ietf-clue-protocol-17 Summary: The CLUE protocol is an application
protocol conceived for the description and negotiation of a telepresence
session.  The design of the CLUE protocol takes into account the requirements
and the framework defined within the IETF CLUE working group.  A companion
document delves into CLUE signaling details, as well as on the SIP/SDP session
establishment phase.  CLUE messages flow over the CLUE data channel, based on
reliable and ordered SCTP over DTLS transport. Message details, together with
the behavior of CLUE Participants acting as Media Providers and/or Media
Consumers, are herein discussed.

I think the document make sense and is written very clear, except some small
nits: # The XML examples seem not compatible with XML format, especially, the
folding lines. For example:
        <xs:element name="supportedVersions" type="versionsListType"
                minOccurs="0"/>
        <xs:element name="supportedExtensions"  type="extensionsListType"
                minOccurs="0"/>
        <xs:any namespace="##other" processContents="lax"
                minOccurs="0"/>
Suggest to following the artwork folding rules
[draft-ietf-netmod-artwork-folding-00].

# A run of idnits revealed there were 0 error, 4 warning and 2 comments:

  Miscellaneous warnings:
  ----------------------------------------------------------------------------

  -- The document date (September 21, 2018) is 58 days in the past.  Is this
     intentional?

  Checking references for intended status: Proposed Standard
  ----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative references
     to lower-maturity documents in RFCs)

  == Missing Reference: '1-9' is mentioned on line 1357, but not defined

  == Missing Reference: '0-9' is mentioned on line 1363, but not defined

  == Unused Reference: 'RFC7667' is defined on line 2987, but no explicit
     reference was found in the text

  == Outdated reference: A later version (-14) exists of
     draft-ietf-clue-signaling-13

  -- Obsolete informational reference (is this intentional?): RFC 5117
     (Obsoleted by RFC 7667)

     Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--).

-----------------------------------------------------------------------



From nobody Mon Nov 19 10:26:03 2018
Return-Path: <kaduk@mit.edu>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5046F130DE2; Mon, 19 Nov 2018 10:25:53 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk <kaduk@mit.edu>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-clue-protocol@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, clue-chairs@ietf.org, pkyzivat@alum.mit.edu, clue@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.88.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154265195328.5264.10510811874699482118.idtracker@ietfa.amsl.com>
Date: Mon, 19 Nov 2018 10:25:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/knYP4WavreAH9mCn4-C34SmhIT8>
Subject: [clue] Benjamin Kaduk's Discuss on draft-ietf-clue-protocol-17: (with DISCUSS and COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 18:25:53 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-clue-protocol-17: Discuss

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


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


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



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

Thanks for the generally clear and well-written document!
I would like to discuss whether there needs to be more prominent coverage
of timers/timeouts, especially as relating to the state machines.  (I'd be happy
to learn that this is well-covered elsewhere in the document set; I just haven't
run into it yet.)

In a similar vein, do we want to have any treatment of avoiding infinite loops
(e.g., when a 'configure' or 'advertisement' is rejected in expectation of modification
but the sending implementation continues to generate an identical message)?

It is not clear to me that any change to the document text is needed in either case,
but I don't know to what extent the topics have already been discussed.


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

I also have some substantial comments that do not rise to Discuss-level.

How do I know which endpoint is the channel initiator and which is the
channel receiver?
draft-ietf-clue-signaling suggests that the DTLS client is the channel
initiator, but even that is not explicit about it -- the protocol could be
considered under-specified if there is insufficient clarity.

Section 2

The MCU definition doesn't actually expand the acronym, which seems a
little reader-unfriendly.

Section 5.1

There are perhaps more XML extension points in here than is reasonable for
some of these elements (e.g., <versionsListType>).

Section 5.2

                           If the responseCode is between 200 and 299
   inclusive, the response MUST also include <mediaProvider>,
   <mediaConsumer>, <version> and <commonExtensions> elements;

Maybe re-mention that MP and MC are booleans here.

   Finally, the commonly supported extensions are copied in the
   <commonExtensions> field.

Does this need to say that only extensions that are applicable to the
negotiated protocol version are included?  (Also, how does one handle an
extension that exists for multiple major versions -- are there two
<extension> elments for it in the <options> message?)

   Upon reception of the 'optionsResponse' the version to be used is the
   one provided in the <version> tag of the message.  The following CLUE
   messages MUST use such a version number in the "v" attribute.  The
   allowed extensions in the CLUE dialogue are those indicated in the
   <commonExtensions> of the 'optionsResponse' message.

Couldn't this restriction on the "v" value apply even to the
'optionsResponse' message?

Section 5.3

   The 'advertisement' message is used by the MP to advertise the
   available media captures and related information to the MC.  [...]

I'd consider avoiding the definite article "the" to refer to MP/MC roles,
since in many caess there will be 2+ of each, and we don't want to confuse
the reader into thinking that there is an MP/CR equivalence or something
like that.  So, perhaps "each MP" and "the corresponding MC".

Section 5.4

                             As it can be seen from the message schema
   provided in the following excerpt (Figure 6), the 'ack' contains a
   response code and a reason string for describing the processing
   result of the 'advertisement'.  [...]

[the reason string is part of the base clueResponseType]
The text quoted here could be read as implying that the reason string is
required in the 'ack' message, a stronger requirement than of the base
clueResponseType where it has minOccurs=0.  Some greater clarity in the
text here is probably called for, especially since when the 'ack' is
piggybacked on a 'configure' message, there is no provision for a reason
string at all.

Section 5.5

                             The <ack> element MUST NOT be present if an
   'ack' message has been already sent back to the MP.

I think you need to clarify that this is scoped to the current
advSequenceNr.

Section 5.6

                                             It contains (Figure 8) a
   response code with a reason string indicating either the success or
   the failure (along with failure details) of a 'configure' request
   processing.  [...]

[Same comment about reason string as for 'ack']

Section 5.7

   Such new response codes MUST NOT overwrite the ones here defined and
   they MUST respect the semantics of the first code digit.

nit: is this "overwrite" or "override"?

   This document does not define response codes starting with "1", and
   such response codes are not allowed to appear in major version 1 of
   the CLUE protocol.  The range from 100 to 199 inclusive is reserved
   for future major versions of the protocol to define response codes
   for delayed or incomplete operations if necessary.  Response codes
   starting with "5" through "9" are reserved for future major versions
   of the protocol to define new classes of response, and are not
   allowed in major version 1 of the CLUE protocol.  Response codes
   starting with "0" are not allowed.

This text seems to also preclude extensions to major version '1' from
defining 1xx or [5-9]xx reason codes; is that the intent?

Section 6

   When the CLUE data channel set up starts ("start channel"), the CP
   moves from the IDLE state to the CHANNEL SETUP state.

nit: only one of "sets up" and "starts" is needed.

   When in the ACTIVE state, the CP starts the envisioned sub-state
   machines (i.e., the MP state machine and the MC state machine)
   according to the roles it plays in the telepresence sessions.  Such
   roles have been previously declared in the 'options' and
   'optionsResponse' messages involved in the initiation phase (see
   OPTIONS sections Section 5.1 and Section 5.2 for the details).  [...]

My reading of the initiation phase is that each CP sends only a boolean
indication of whether it supports the MP/MC roles, and so each party has to
determine on its own whether it will act as a MP and/or MC; is that
correct?  If so, do we need to say anything about how the boolean matrix
translates to activating the respective sub-state machines?

Section 6.1

                         'configure+ack' messages referring to out-of-
   date (i.e., having a sequence number equal to or less than the
   highest seen so far) advertisements MUST be ignored, i.e., they do
   not trigger any state transition.  [...]

Is this really less than or equal or just less than?  Also, is "seen" the
right verb, since IIUC these are sequence numbers that the MP has
*generated* in its advertisements?

Section 7

                                                          In other
   words, in this example, the MP MUST use version 1.4 and downgrade to
   the lower version.  [...]

nit: does the phrase "and downgrade to the lower version" add any value
here?  The word "downgrade" can have negative connotations in some other
contexts, so if it's not adding value I'd suggest avoiding it.

Section 8

   As reported in Figure 13, the values of the fields of the <extension>
   element (either new information or new messages) take the following
   values:
[...]
   o  the major standard version of the protocol that the extension
      refers to.

The XSL includes a full version (including minor), even though the
semantics basically only use the major version.  That said, why is the
'version' element minOccurs="0" -- what are the semantics when it is
absent?

Section 8.1

   The CLUE data model document ([I-D.ietf-clue-data-model-schema])
   envisions the possibility of adding this kind of "extra" information
   in the description of a video capture by keeping the compatibility
   with the CLUE data model schema.  [...]

nit: I don't think this is grammatical; maybe just "keeping compatibility".

Section 10

This claims to be a "call flow" example, but the described flows only
contain a single unidirectional media flow, which is not really consistent
with the normal usage of the word "call".  Buried in the body text there is
a disclaimer:
   [...]                      For the sake of simplicity, the following
   call flow focuses only on the dialogue between MP CP1 and MC CP2.
I would suggest making the presence of this simplification much clearer
from the start, perhaps "CLUE protocol messages exchanged in the following
call flow are detailed; only one direction of media is shown for
simplicity, as the other direction is precisely symmetric".

   CP2 acknowledges the second 'advertisement' message with an 'ack'
   message (Section 10.7).

   In a second moment, CP2 changes the requested media streams from CP1
   by sending to CP1 a 'configure' message replacing the previously
   selected video streams with the new composed media streams advertised
   by CP1 (Section 10.8).

This might be an appropriate place to indicate that media from the previous
configuration continue to flow during the reconfiguration process.

It might also be worth noting again somewhere in here (or a subsection)
that there are three (well, two, since we only show one direction of media)
distinct sequence number spaces per sender, and that the discontinuity
between Section 10.2 and 10.3's numbers is correct.

Section 11

Thanks for the well-thought-through security considerations; in combination
with the linked documents (particularly the framework), they cover all the
considerations (especially privacy considerations) that I had in mind.

Section 14.2

We appear to be citing both 5117 and 7667, whereas the latter obsoletes the
former.



From nobody Mon Nov 19 10:55:28 2018
Return-Path: <adam@nostrum.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26CE4130E8D for <clue@ietfa.amsl.com>; Mon, 19 Nov 2018 10:55:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 gC8t8Hk0xj8D for <clue@ietfa.amsl.com>; Mon, 19 Nov 2018 10:55:17 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3CB0130E43 for <clue@ietf.org>; Mon, 19 Nov 2018 10:55:11 -0800 (PST)
Received: from Svantevit.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id wAJIt9FE000711 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 19 Nov 2018 12:55:10 -0600 (CST) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.roach.at
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
Cc: clue-chairs@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, clue@ietf.org, pkyzivat@alum.mit.edu, draft-ietf-clue-protocol@ietf.org
References: <154265195328.5264.10510811874699482118.idtracker@ietfa.amsl.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <fb638fef-452a-4958-31a7-aa403b570ed8@nostrum.com>
Date: Mon, 19 Nov 2018 12:55:04 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.3.0
MIME-Version: 1.0
In-Reply-To: <154265195328.5264.10510811874699482118.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/uO5gx_qf_jpXaRoy04fMD44fF0Y>
Subject: Re: [clue] Benjamin Kaduk's Discuss on draft-ietf-clue-protocol-17: (with DISCUSS and COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 18:55:26 -0000

Trying to help out a bit on one of the discuss points...

On 11/19/18 12:25 PM, Benjamin Kaduk wrote:
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Thanks for the generally clear and well-written document!
> I would like to discuss whether there needs to be more prominent coverage
> of timers/timeouts, especially as relating to the state machines.  (I'd be happy
> to learn that this is well-covered elsewhere in the document set; I just haven't
> run into it yet.)


The initial document included several timers that triggered 
retransmissions of messages -- but since the CLUE protocol uses TCP as a 
substrate, these kind of application-level retransmissions can cause a 
spike of traffic when the networks starts getting congested, which is 
the opposite of what we want to happen. So they were removed, and the 
protocol now relies exclusively on the reliability mechanisms provided 
by TCP both for retransmission and for detection of connection failures.

In terms of supervising the overall lifetime of the state machines, it's 
important to keep in mind that these operations always take place within 
the context of a larger session (e.g., a SIP session), which naturally 
limits how long the state machines can live: at the end of the 
corresponding session, all CLUE state goes away.

/a


From nobody Mon Nov 19 11:02:09 2018
Return-Path: <kaduk@mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE54C130DED; Mon, 19 Nov 2018 11:01:59 -0800 (PST)
X-Quarantine-ID: <5DVNigcQCfqM>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char 9C hex): Received: ...s kaduk@ATHENA.MIT.EDU)\n\t\234by outgoing.mit[...]
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 5DVNigcQCfqM; Mon, 19 Nov 2018 11:01:57 -0800 (PST)
Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) (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 C6781130DE3; Mon, 19 Nov 2018 11:01:56 -0800 (PST)
X-AuditID: 12074422-bb9ff70000005074-ad-5bf308a083dc
Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 22.BA.20596.1A803FB5; Mon, 19 Nov 2018 14:01:54 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.14.7/8.9.2) with ESMTP id wAJJ1khI009966; Mon, 19 Nov 2018 14:01:47 -0500
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) œby outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id wAJJ1en0004503 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 19 Nov 2018 14:01:43 -0500
Date: Mon, 19 Nov 2018 13:01:40 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: Adam Roach <adam@nostrum.com>
Cc: The IESG <iesg@ietf.org>, clue-chairs@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, clue@ietf.org, pkyzivat@alum.mit.edu, draft-ietf-clue-protocol@ietf.org
Message-ID: <20181119190139.GU11132@kduck.kaduk.org>
References: <154265195328.5264.10510811874699482118.idtracker@ietfa.amsl.com> <fb638fef-452a-4958-31a7-aa403b570ed8@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <fb638fef-452a-4958-31a7-aa403b570ed8@nostrum.com>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA01SbUhTURju7M7tbOzW8ap40iy8Wj+MmYbBfpT5o8ykwAoMG5RXd3XDfci9 U5wUiFToXJKDQieV2LQQCVb4MZgsVxkNjUKKFkqERumfaVKSH6N7HX78e97zfPEeXkhQrTFJ 0GC2spyZMdIypZSS56aru+GSNmtlNVXjW++Wa/443TKNPzhJaDzew5rIfA+haV9rI/JkBV7X tLzA7f4nKXB5Z6VFxBXlcR1rNNSy3JHcUqU+sOAgqn/tqWvqXwYN4LvKDhQQoxzcMeYHdqCE FOqX4G5nMxEdPAD7V4Ky6DAtwQv2p3LRIkUHsaclJBOxDKXjhpZJQsTxKBXffhXacBNoBOAf A4NCLoRxqAz7JjJEDSnU3Xw4sZFDoUaAw6vF0fdY/K5jVipiAmXgL5E5iWglUDJ+EoEiVKCT eM59QlQkoDQ80hqQ3wXItcPs2mF2bZu7ANEHUnSmerWJMRh5tlzNlzNmM8upj2WaDNZMVlfz HGx89Sl6GLRFCgMAQUCryJevF7VUDFPL20wBsBdK6ARy/NtvLbW7zKKz6Rlef42rMbJ8AGBI 0PFkUa/AkTrGVs9ylk0qGUrpRHItfkZLoUrGylaxbDXLbbL7IKQxeVa+pKViObaSraswGK3b tAQqxHCVEO4QNSRfzZh4Q2WUDwI1HBxvbicoqdliZpMSyQuiCIkifY15K0c8I1zlvz4PEoW1 4shZUaUSjmwraV4okQglPz+FxRIrs00lNYADtZZBzWlnICX/TqfP6Vt//0ipdqifOYbO952h bnzd7/GNLfe+OFqYMprdE2m6hN7OlFwcyVc4exendtmL7x2ayh1IA3NXZxrDqqLLZaVZIGd0 OIiKP98PTYb+vnk81CnVj6ZW5IAH58JV3pLgh48tJJlVol2wTd9a78jTddFSXs9kZxAcz/wH QoiwFSEDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/RFi-10MoYjrruZzqMQWha4Rfm-E>
Subject: Re: [clue] Benjamin Kaduk's Discuss on draft-ietf-clue-protocol-17: (with DISCUSS and COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 19:02:00 -0000

On Mon, Nov 19, 2018 at 12:55:04PM -0600, Adam Roach wrote:
> Trying to help out a bit on one of the discuss points...
> 
> On 11/19/18 12:25 PM, Benjamin Kaduk wrote:
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> >
> > Thanks for the generally clear and well-written document!
> > I would like to discuss whether there needs to be more prominent coverage
> > of timers/timeouts, especially as relating to the state machines.  (I'd be happy
> > to learn that this is well-covered elsewhere in the document set; I just haven't
> > run into it yet.)
> 
> 
> The initial document included several timers that triggered 
> retransmissions of messages -- but since the CLUE protocol uses TCP as a 
> substrate, these kind of application-level retransmissions can cause a 
> spike of traffic when the networks starts getting congested, which is 
> the opposite of what we want to happen. So they were removed, and the 
> protocol now relies exclusively on the reliability mechanisms provided 
> by TCP both for retransmission and for detection of connection failures.

(SCTP now, but sure.)

> In terms of supervising the overall lifetime of the state machines, it's 
> important to keep in mind that these operations always take place within 
> the context of a larger session (e.g., a SIP session), which naturally 
> limits how long the state machines can live: at the end of the 
> corresponding session, all CLUE state goes away.

So it seems the question is scoped to what to do with a peer that is
behaving properly with the SIP session and claims to negotiate CLUE at the
SIP layer, but then fails to actually send one of the required CLUE
messages.  Section 6 of this document only mentions "a timeout error is
raised" twice, in some informal discussion of why the initiation phase
might fail, which is part of what got me thinking about the question.

-Benjamin


From nobody Mon Nov 19 11:07:26 2018
Return-Path: <adam@nostrum.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC22130DF3 for <clue@ietfa.amsl.com>; Mon, 19 Nov 2018 11:07:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 UERFtK8UfkRY for <clue@ietfa.amsl.com>; Mon, 19 Nov 2018 11:07:23 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EBF0130DE2 for <clue@ietf.org>; Mon, 19 Nov 2018 11:07:23 -0800 (PST)
Received: from Svantevit.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id wAJJ7LWv002763 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 19 Nov 2018 13:07:22 -0600 (CST) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.roach.at
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, clue-chairs@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, clue@ietf.org, pkyzivat@alum.mit.edu, draft-ietf-clue-protocol@ietf.org
References: <154265195328.5264.10510811874699482118.idtracker@ietfa.amsl.com> <fb638fef-452a-4958-31a7-aa403b570ed8@nostrum.com> <20181119190139.GU11132@kduck.kaduk.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <975b22f1-ddd2-b267-51ce-e5629fd50d04@nostrum.com>
Date: Mon, 19 Nov 2018 13:07:16 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.3.0
MIME-Version: 1.0
In-Reply-To: <20181119190139.GU11132@kduck.kaduk.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/SA7LfzcmfhPr1rgkERzrudbz-6s>
Subject: Re: [clue] Benjamin Kaduk's Discuss on draft-ietf-clue-protocol-17: (with DISCUSS and COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 19:07:24 -0000

On 11/19/18 1:01 PM, Benjamin Kaduk wrote:
> So it seems the question is scoped to what to do with a peer that is
> behaving properly with the SIP session and claims to negotiate CLUE at the
> SIP layer, but then fails to actually send one of the required CLUE
> messages.


Sure. This isn't much different than an implementation that advertises a 
video stream, causing you to allocate resources for a corresponding 
codec, and then never sends any associated packets. The net effect is 
that you have wasted resources, potentially for the entire duration of 
the session; but, since they go away when the session terminates, there 
is little to no harm inflicted on the system.


>    Section 6 of this document only mentions "a timeout error is
> raised" twice, in some informal discussion of why the initiation phase
> might fail, which is part of what got me thinking about the question.


I suspect that's left-over language from back when we had explicit 
retransmission timers in the document. It might bear removing (or, at 
least, clarification that it's talking about SCTP timeouts).

/a


From nobody Mon Nov 19 13:09:32 2018
Return-Path: <warren@kumari.net>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B3FA130DE5; Mon, 19 Nov 2018 13:09:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Warren Kumari <warren@kumari.net>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-clue-protocol@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, clue-chairs@ietf.org, pkyzivat@alum.mit.edu, clue@ietf.org, wangzitao@huawei.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.88.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154266177029.16507.4739255211393565991.idtracker@ietfa.amsl.com>
Date: Mon, 19 Nov 2018 13:09:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/RsH6WRYpoIR6egYptzBWlxqyE_8>
Subject: [clue] Warren Kumari's No Objection on draft-ietf-clue-protocol-17: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 21:09:30 -0000

Warren Kumari has entered the following ballot position for
draft-ietf-clue-protocol-17: No Objection

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


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


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



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

I'd like to thank Benjamin for his detailed review! Also, Zitao Wang for the
OpsDir review - it contains some useful nits, and I'd encourage the authors to
address them.



From nobody Mon Nov 19 14:52:01 2018
Return-Path: <ben@nostrum.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3CBA129BBF; Mon, 19 Nov 2018 14:51:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 DQ_Jb-BYlDWq; Mon, 19 Nov 2018 14:51:56 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C38311252B7; Mon, 19 Nov 2018 14:51:56 -0800 (PST)
Received: from [10.0.1.24] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id wAJMpjus039182 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 19 Nov 2018 16:51:46 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.24]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <4A25F2E2-675B-4F26-BF08-DA20581DB798@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_7AAD9084-EF8C-46DA-BDB4-4EB8806B0268"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
Date: Mon, 19 Nov 2018 16:51:45 -0600
In-Reply-To: <fb638fef-452a-4958-31a7-aa403b570ed8@nostrum.com>
Cc: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>, clue-chairs@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, clue@ietf.org, draft-ietf-clue-protocol@ietf.org, pkyzivat@alum.mit.edu
To: Adam Roach <adam@nostrum.com>
References: <154265195328.5264.10510811874699482118.idtracker@ietfa.amsl.com> <fb638fef-452a-4958-31a7-aa403b570ed8@nostrum.com>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/C8tqCbJ_ijHbqZpEEdD-KW7BZkg>
Subject: Re: [clue] Benjamin Kaduk's Discuss on draft-ietf-clue-protocol-17: (with DISCUSS and COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 22:51:59 -0000

--Apple-Mail=_7AAD9084-EF8C-46DA-BDB4-4EB8806B0268
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I haven=E2=80=99t finished writing up my notes yet, but I have some =
similar concerns. Comments below:



> On Nov 19, 2018, at 12:55 PM, Adam Roach <adam@nostrum.com> wrote:
>=20
> Trying to help out a bit on one of the discuss points...
>=20
> On 11/19/18 12:25 PM, Benjamin Kaduk wrote:
>> =
----------------------------------------------------------------------
>> DISCUSS:
>> =
----------------------------------------------------------------------
>>=20
>> Thanks for the generally clear and well-written document!
>> I would like to discuss whether there needs to be more prominent =
coverage
>> of timers/timeouts, especially as relating to the state machines.  =
(I'd be happy
>> to learn that this is well-covered elsewhere in the document set; I =
just haven't
>> run into it yet.)
>=20
>=20
> The initial document included several timers that triggered =
retransmissions of messages -- but since the CLUE protocol uses TCP as a =
substrate, these kind of application-level retransmissions can cause a =
spike of traffic when the networks starts getting congested, which is =
the opposite of what we want to happen. So they were removed, and the =
protocol now relies exclusively on the reliability mechanisms provided =
by TCP both for retransmission and for detection of connection failures.

IIRC, there are some situations where an endpoint sits in a state and =
waits for a message from the other side. Even with SCTP, there=E2=80=99s =
the possibility the other side doesn=E2=80=99t send that message.  I =
realize that might be an implementation error, but does that mean the =
endpoint just waits until the session ends? If that=E2=80=99s the case, =
why are timeouts even mentioned?

>=20
> In terms of supervising the overall lifetime of the state machines, =
it's important to keep in mind that these operations always take place =
within the context of a larger session (e.g., a SIP session), which =
naturally limits how long the state machines can live: at the end of the =
corresponding session, all CLUE state goes away.
>=20

I=E2=80=99m not sure it=E2=80=99s reasonable for the protocol to depend =
on SIP eventually closing it down, as the SIP session could be =
arbitrarily long lived. =E2=80=9CWormwhole=E2=80=9D conferences that are =
nailed up for days, months, or even years are not all that uncommon =
these days. Are those sorts of things in scope?


--Apple-Mail=_7AAD9084-EF8C-46DA-BDB4-4EB8806B0268
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlvzPoEACgkQgFZKbJXz
1A1qnhAAxP/R8Hw0Yy+b8rY2JXrgp9z+Jugpnc9fCLyXdJ7/b+DUZt8Ml/VlMSRm
CknWs3FjqJNHr2SiH5lZxO28UDiILmMx8Hu4I5fuj5e2XioISvta2rHe2k9BBqDb
NEi+TlOm61n99dSqBl0cv7hgbQY11OaSC7j+NGvHb9SfkxISfUhinYUaMUSnlhnT
7gUkc7dl+DESl4dzgMgarnExFYushvLYwHCVI8sEq1InqYV2bywiMg6ijyNFhWaq
IgalK0COCm1ioQh075JdJrgWItoRTs6dvA2+7Axifs2qzR7f3+qoSmU/ElY/ABbA
aDxpI21Nq/Wk3K226oZ+mCEo/OA6CGp8QpBMsTwmylScd6X2C+XJzKRiDpsSmgUT
W9/1BB+azxZ4Zr0LBM8U8WLno3IGFSNj1J8aBBP5Fq6XpwT2AWPefG6cI6bbxXMD
5H//yRSggy9dX/cTltSxNlUczBR+WSvWH5/a6beUz4QCXtd9VX8fZGIpwT2IAPhp
fwTJkcep8YGIShbAKYUOOsgJsX6LVxdeO5wfEk00K/syjz1SV/ea7gGVyUMqjXKQ
nFhhJarrTZ+aRtH2uM04sCN9cnIhfIWNMY9Elw0ftJxgUXtMYVEDWXU1KKl1QjRF
Mre7UzwKVdAv6jCeNdbn1FTNS+f8oyF/Lt5pgBeM/mZOhEwmTNs=
=JZRd
-----END PGP SIGNATURE-----

--Apple-Mail=_7AAD9084-EF8C-46DA-BDB4-4EB8806B0268--


From nobody Mon Nov 19 15:28:26 2018
Return-Path: <suresh@kaloom.com>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DE0DA127598; Mon, 19 Nov 2018 15:28:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Suresh Krishnan <suresh@kaloom.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-clue-protocol@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, clue-chairs@ietf.org, pkyzivat@alum.mit.edu, clue@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.88.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154267010483.26695.8084095442219691276.idtracker@ietfa.amsl.com>
Date: Mon, 19 Nov 2018 15:28:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/baXYkIAv07Y7rMoVC_ENh__29Ps>
Subject: [clue] Suresh Krishnan's No Objection on draft-ietf-clue-protocol-17: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 23:28:25 -0000

Suresh Krishnan has entered the following ballot position for
draft-ietf-clue-protocol-17: No Objection

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


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


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



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

I found the document to be well written and easy to read. I just had a concern
about the response codes. I did not find text either in this on in
draft-ietf-clue-signaling that describes the behavior that results in a
specific response code. e.g. 402 and 404 seem to have some overlap but there is
no text for when a 404 will be sent to disambiguate it from 402. Likewise for
the other response codes. I did not find any prescriptive behavior that results
in these codes.



From nobody Mon Nov 19 15:56:24 2018
Return-Path: <kaduk@mit.edu>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 16C12124C04; Mon, 19 Nov 2018 15:56:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk <kaduk@mit.edu>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-clue-signaling@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Roni Even <roni.even@mail01.huawei.com>, clue-chairs@ietf.org, roni.even@mail01.huawei.com, clue@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.88.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154267178201.26570.2400616201103578148.idtracker@ietfa.amsl.com>
Date: Mon, 19 Nov 2018 15:56:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/e1zW7FBQntsBBmjdw7I2vtke9TQ>
Subject: [clue] Benjamin Kaduk's Discuss on draft-ietf-clue-signaling-14: (with DISCUSS and COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 23:56:22 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-clue-signaling-14: Discuss

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


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


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



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

Section 11.2 of the IANA considerations lists an actual OID value to use
for the "sip.clue" media feature tag, but the IANA last call review
indicates that the decimal value for sip.clue will be assigned at
registration, so it is incorrect to claim that it will be 1.3.6.1.8.4.29.
Squatting on the next available codepoint like this is quite risky and I
really want to discourage this practice.  We had a lot of trouble in TLS
recently with *three* different extensions attempting to use the same
codepoint, which was not fun to resolve.


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

Please consider using the RFC 8174 version of the BCP 14 boilerplate.

Section 3

   The "sip.clue" media feature tag SIP [RFC3840] indicates support for
   CLUE in SIP [RFC3261] calls.

nit: I think there's a missing word or three here; maybe "for SIP"?

Section 4.3

   The restrictions on CLUE-controlled media always apply to "m=" lines
   in an SDP offer or answer, even if negotiation of the data channel in
   [...]

I'm not entirely sure I understand what "the restrictions" are, here.
Unless this is supposed to just be the general requirements for how they
are (not) sent?

Section 4.4.1.1

   Each <encID> (in encodingIDList) in a CLUE ADVERTISEMENT message
   SHOULD represent an Encoding defined in SDP; the specific Encoding
   referenced is a CLUE-controlled "m=" line in the most recent SDP sent
                                                    ^^^^^^^^^^^^^^^
   by the sender of the ADVERTISEMENT message with a label value
   corresponding to the text content of the <encID>.

Is this "most recent SDP Offer/Answer"?
(Similarly in the following paragraph.)
I'm also not sure why these are SHOULD- instead of MUST-level requirements,
modulo the non-atomicity mentioned in the final paragraph of the section.

Section 4.5.1

[I will leave it to Adam to check that the "initial offer" terminology is
being used in the consensus manner, since I haven't been tracking what
manner that is.]

Section 4.5.2.2

(Also in 4.4.1.1) Am I reading this correctly that with the initial offer,
we are talking about negotiating media lines with labels that correspond to
CLUE Encoding names that have not yet been present in any CLUE messages
(that is, we're doing it "blind")?

Section 4.5.4.2

   group then the call is now CLUE-enabled; negotiation of the data
   channel and subsequently the CLUE protocol begin.

nit: begins

Section 4.5.4.4

   o  The CLUE protocol enters an unrecoverable error state as defined
      in Section 6. of [I-D.ietf-clue-protocol], either the 'MP-
      TERMINATED' state for the Media Provider or 'MC-TERMINATED' for
      the Media Consumer.

The MP-TERMINATED and MC-TERMINATED states do not seem to exist in the -17
of the protocol document.  (I'm assuming this is essentially editorial
in nature and doesn't need to be part of the DISCUSS section.)

Section 5.1

   The primary implication of this is that a device may receive an SDP
   with a CLUE Encoding for which it does not yet have Capture [...]

presumably this is "SDP Offer/Answer" as well?

   A device with the CLUE Participant state machine in the ACTIVE state
   MAY choose not to move from ESTABLISHED to ADV (Media Provider state
   machine) or from ESTABLISHED to WAIT FOR CONF RESPONSE (Media
   Consumer state machine) based on the SDP state.  [...]

Is this "choose not to move", "choose to not move", or "chose whether or
not to move"?

Section 5.2

                    : an implementation MUST NOT send a specific CLUE
   Capture Encoding unless its most recent SDP exchange contains an
   active media channel for that Encoding AND the far end has sent a
   CLUE CONFIGURE message specifying a valid Capture for that Encoding.

nit: "far end" is perhaps a bit informal; "peer" or "MC" might be
alternatives.
I guess technically this also doesn't require that he CONFIGURE parsed
correctly and was accepted, which is arguably a bug.

Section 8

   With the successful initial SDP Offer/Answer exchange complete Alice
   and Bob are also free to negotiate the CLUE data channel.  This is
   illustrated as CLUE DATA CHANNEL ESTABLISHED.

   Once the data channel is established CLUE protocol negotiation
   begins.  In this case Bob chose to be the DTLS client (sending
   a=active in his SDP answer) and hence is the CLUE Channel Initiator
   and sends a CLUE OPTIONS message describing his version support.  On
   receiving that message Alice sends her corresponding CLUE OPTIONS
   RESPONSE.

My understanding was that the DTLS connection was a prerequisite for
setting up the CLUE data channel (so I would have been less confused if the
note about DTLS client was in the first paragraph).

There are some instances of "CLUE channel" in this section that might be
better as "CLUE data channel".

Is it normal for the mid of the CLUE data channel to be changing around in
the various SDP snippets shown in these examples?

Section 12

   This attack can be prevented by ensuring that the media recipient
   intends to receive the media packets.  As such all CLUE-capable
   devices MUST support key negotiation and receiver intent assurance
   via DTLS-SRTP [RFC5763] on CLUE-controlled RTP "m=" lines.  All CLUE-
   controlled RTP "m" lines must be secured and implemented using
   mechanisms such as SRTP [RFC3711].  CLUE implementations MAY choose
   not to require the use of SRTP to secure legacy (non-CLUE-controlled)
   media for backwards compatibility with older SIP clients that are
   incapable of supporting it.

Should these normative requirements be placed somewhere in the main body of
this (or some other) document in addition to their necessity being
described in the security considerations here?

Section 14.2

Should-ietf-rtcweb-data-channel be a normative reference?  (It seems like
it should be so at least in draft-ietf-clue-datachannel, which is not on
this week's telechat.)  I think that RFC 3840 should be normative here,
though, since you have to use it to enable CLUE.  There's probably others,
though I'd be inclined to consider at least the core SIP and SDP specs as
"basic specifications" (per
https://www.ietf.org/blog/iesg-statement-normative-and-informative-references/)
that do not need to be normative.



From nobody Mon Nov 19 19:39:19 2018
Return-Path: <ben@nostrum.com>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BDD30127333; Mon, 19 Nov 2018 19:39:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Ben Campbell <ben@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-clue-protocol@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, clue-chairs@ietf.org, pkyzivat@alum.mit.edu, clue@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.88.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154268515769.26665.4530527657139603206.idtracker@ietfa.amsl.com>
Date: Mon, 19 Nov 2018 19:39:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/eKWuFPFAyoyetrKchVHq0WOdtH0>
Subject: [clue] Ben Campbell's Discuss on draft-ietf-clue-protocol-17: (with DISCUSS and COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 03:39:18 -0000

Ben Campbell has entered the following ballot position for
draft-ietf-clue-protocol-17: Discuss

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


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


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



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

Thanks for all the work on this over the years. I have a few concerns that I
think require discussion prior to publication:

§5.7: Is the "description" field expected to be human readable? If so, are
there internationalization issues to consider?

§6.2, 5th paragraph: This says that if you get an error back for a configure
message, you send a new configure message. This seems likely to cause an
infinite loop unless some guidance is given about escaping the loop when the
endpoints cannot agree on a configuration.

§7:  I’m confused by the versioning mechanisms. This section requires an
endpoint to ignore unknown elements, but it also requires the peer to downgrade
to the highest shared version. These requirements seem to be at cross purposes.
If the peer downgrades, one should only see unknown elements in the case of
implementation errors. The requirement to ignore unknown elements does not come
for free; nor does the requirement to downgrade.

§5.1 and §8: The use of the options message to negotiate extensions seems
underspecified. How does an endpoint compare extensionType elements?  Is a spec
required or expected? Is the extension spec expected to register the URI for
schemaRef somewhere? Does this need to be in IANA?


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

I've got a number of additional comments that do not seem to rise to the level
of a DISCUSS:

*** Substantive Comments ***

I support Benjamin Kaduk's DISCUSS.

Additionally, I think there's some missing sub-transaction states, at least in
the state machine in Figure 10. When an endpoint sends a message and is waiting
for a response, shouldn't there be a separate waiting state (for example, when
waiting for optionsResponse)? The MP and MC state machines include this sort of
thing but the initial state machine does not. Also, I wonder if there are some
unhandled cases where a configure and advertise message cross on the wire.

- §1 ( also §2, definition of "endpoint"):
I'd like to see a few more words about the relationship between this, the
framework draft, the datachannel draft, and SIP.  Am I correct to understand
that is the only environment the protocol is ever expected to operate in? That
is, is there room for different signaling protocols, different transports, etc?
This also impacts the security considerations. For example if this depends on
the security properties of datachannels (over SCTP and DTLS), then it's worth
some language to the effect that it MUST not be used on other transports, or
that if it is used on other transports they must have similar security
properties.

§2, definition of endpoint: Please cite RFC3261 for SIP. (I have mixed feelings
whether this needs to be normative or informational.)

§4:
- "a lack of interoperability between the
protocol implementations. In order to correctly establish a CLUE
dialogue, the involved CPs MUST have in common a major version number"

That seems like a statement of fact. I suggest reserving the normative keywords
for the actual procedures that require this.

§5:
- ClueID: Is this truly optional in the sence of never required under any
circumstances? - sequenceNr: Is the language about incrementing intended to use
normative keywords? (e.g MUST)? Why do implementations need to send errors for
unexpected sequence numbers when using a reliable protocol? That would only
happen in the case of implementation errors, right? Why is it optional to start
with a random sequence number? Is there a concern about fingerprinting if
people choose otherwise? (I guess as the security considerations mention,
there's a lot of other things to fingerprint.)

- Protocol field: Do you envision non-CLUE messages will ever occur on the same
SCTP association? if not, then why require this? If so, then what should an
endpoint do if it gets a message with something other than "clue" here?

§5.1: "since minor versions are
defined to be both backwards and forwards compatible,"
Please see related DISCUSS comment.

§5.7:

- What is the reason for defining meaning the "100" response code range if no
codes in that range are defined? Why is this different from the 500-900 ranges
that are merely reserved for future use? (I gather there was an intent to be
consistent with SIP error codes, but why not leave that to the first spec that
defines a 1XX code, assuming that ever happens?

- "message. Implementations can (and are encouraged to)
include more specific descriptions of the error condition, if
possible."

Am I correct to assume that implementations should not expect any particular
description text for a given error code? (That used to be a common interop
problem for SIP.)

§6:
- "When the CLUE data channel set up starts ("start channel"), the CP
moves from the IDLE state to the CHANNEL SETUP state."

What does "set up starts" mean? Is this trigged by SDP signaling? SCTP
connection? Is it different for the SCTP client and server? (I suspect the
data-channel draft answers this, but it should at least be cited here.)

§6.1:
- "Finally, if there are changes
in the MP’s telepresence settings ("changed telepresence settings"),
the MP switches to the ADV state."
If I understand correctly, the MC can send new configure messages at any time.
What happens if one arrives in the ADV state but before sending the advertise?

6.2, 2nd paragraph:
-  Is the MC forbidden from sending a configure without the ack field set prior
to sending an ack? - Is the response code limited to 200, are or other 2XX
codes allowed if defined?

§12.3: The mime type isn’t mentioned anywhere else in the doc? Why is it
registered here? What is it used for?

§12.4.1: Why is it necessary to both register these directly in IANA and define
them in a (presumably registered) schema? Am I correct to assume new message
types must also be defined in a schema?

*** Editorial Comments ***

- General:
-- Please proofread for "which" vs "that" usage.
-- Please proofread for null words, especially "obviously" and similar terms,
which some readers might read as condescending.

- Abstract: Is CLUE an acronym? If so, what is its expansion? (If the title is
the expansion, it's very obscure.). If not, why all-caps?

§2: Please expand MCU on first mention.

§4:
- "The subset of the extensions
that are allowed within the CLUE session is also determined in the initiation
phase, such subset being the one including only the extensions that are
supported by both parties" Convoluted sentence, can it be simplified?

- "Hence in a call between two
CPs, A and B, there would be two separate dialogs, as follows:"
Please define the meaning of "dialog" as used in this document. In particular,
that it is not related to SIP's usage of the term.

§5:
"While the ’options’ and ’optionsResponse’ messages are exchanged in
the initiation phase between the CPs, the other messages are involved
in MP-MC dialogues."
This also needs a definition of "dialog" for the meaning to be clear.

§5.5:

- "The MC can send a
’configure’ after the reception of an ’advertisement’ or each time it
wants to request other captures that have been previously advertised
by the MP."
The use of "can" makes this seem optional. I gather from the state machine this
is not the case.

- "It indicates that the ’configure’
message also acknowledges with success the referred advertisement
(’configure’ + ’ack’ message), by applying in that way a piggybacking
mechanism for simultaneously acknowledging and replying to the
’advertisement’ message."
Convoluted sentence.

5.7:
- "200, 300 and 400 codes are considered catch-alls."
Please elaborate on what "catch-all" means in context.

- "Further response codes can be either defined
in future versions of the protocol (by adding them to the related
IANA registry)..."
The parenthetical phrase is redundant to the next sentence.

§6:

- First Paragraph: The first and last sentences are redundant with earlier text
in the draft. Should "MC process" and "MP process" be "MC role" and "MP role"?

§6.1, 3rd paragrap: The first sentence seems out of place, given that much of
the previous paragraph was about what happens in the WAIT FOR CONF state.

- 5th paragraph: "If there are
changes in the MP’s telepresence settings ("changed telepresence
settings"), the MP moves back to the ADV state."
Redundant to previous paragraph.

§8.1, 2nd paragraph: The second sentence is redundant to similar text in §8.



From nobody Mon Nov 19 20:11:43 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF540124BAA; Mon, 19 Nov 2018 20:11:40 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Eric Rescorla <ekr@rtfm.com>
To: "The IESG" <iesg@ietf.org>
Cc: "Daniel C. Burnett" <danielcburnett@gmail.com>, clue@ietf.org, pkyzivat@alum.mit.edu, clue-chairs@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-ietf-clue-protocol@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.88.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154268710090.26610.16964659587054726281.idtracker@ietfa.amsl.com>
Date: Mon, 19 Nov 2018 20:11:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/FXonqMtuoQCiujjIIdIN14EGP1A>
Subject: [clue] Eric Rescorla's No Objection on draft-ietf-clue-protocol-17: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 04:11:41 -0000

Eric Rescorla has entered the following ballot position for
draft-ietf-clue-protocol-17: No Objection

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


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


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



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

Rich version of this review at:
https://mozphab-ietf.devsvcdev.mozaws.net/D3717


I have noted a number of points where I think this is not fully
specified. I am not marking this DISCUSS because I believe they are
easy to fix and assume the AD will take care of them.


IMPORTANT
S 5.1.
>      detailed in Section 5.7
>   
>   5.1.  options
>   
>      The 'options' message is sent by the CLUE Participant which is the
>      Channel Initiator to the CLUE Participant which is the Channel

How do I know who is the CI and CR


S 6.
>      moves from the IDLE state to the CHANNEL SETUP state.
>   
>      If the CLUE data channel is successfully set up ("channel
>      established"), the CP moves from the CHANNEL SETUP state to the
>      OPTIONS state.  Otherwise if "channel error", it moves back to the
>      IDLE state.  The same transition happens if the CLUE-enabled

Is it possible to re-start the setup phase? If not, perhaps you want
an ERROR state. If so, maybe describe how


S 6.1.
>      MP moves to the WAIT FOR CONF state.  If a NACK arrives (i.e., an
>      'ack' message with an error response code), the MP moves back to the
>      ADV state for preparing a new 'advertisement'.  When in the WAIT FOR
>      ACK state, if a 'configure' message with the <ack> element set to
>      TRUE arrives ("configure+ack received"), the MP goes directly to the
>      CONF RESPONSE state.  'configure+ack' messages referring to out-of-

What about a configure without an ACK?


S 6.1.
>      date (i.e., having a sequence number equal to or less than the
>      highest seen so far) advertisements MUST be ignored, i.e., they do
>      not trigger any state transition.  If the telepresence settings of
>      the MP change while in the WAIT FOR ACK state ("changed telepresence
>      settings"), the MP switches from the WAIT FOR ACK state to the ADV
>      state to create a new 'advertisement'.

What happens if I receive configure while in ADV?


S 7.
>      the lower version.  This said, and coherently with the general IETF
>      "protocol robustness principle" stating that "an implementation must
>      be conservative in its sending behavior, and liberal in its receiving
>      behavior" [RFC1122], CLUE Participants MUST ignore unknown elements
>      or attributes that are not envisioned in the negotiated protocol
>      version and related extensions.

This seems to mean that if you speak X.Y, then you need to minimally
have a map of all features in [0..Y-1]. Is that correct?

COMMENTS
S 5.1.
>     <xs:anyAttribute namespace="##other" processContents="lax"/>
>   </xs:complexType>
>                  Figure 3: Structure of CLUE 'options' message
>   
>      <supportedVersions> contains the list of the versions that are
>      supported by the CI, each one represented in a child <version>

Are these ordered?


S 5.1.
>      misinterpreting the contents of messages.  The minor version is
>      obviously less useful in this context, since minor versions are
>      defined to be both backwards and forwards compatible, but it is more
>      useful to know the highest minor version supported than some random
>      minor version, as it indicates the full feature set that is
>      supported.  The reason why it is less useful is that the value can in

I'm not quite following the juxtaposition of "full feature set" and
"backwards and forwards compatible". Can you spell out the guarantees
more precisely


S 5.2.
>      inclusive, the response MUST also include <mediaProvider>,
>      <mediaConsumer>, <version> and <commonExtensions> elements; it MAY
>      include them for any other response code.  <mediaProvider> and
>      <mediaConsumer> elements are associated with the supported roles (in
>      terms of, respectively MP and MC), similarly to what the CI does in
>      the 'options' message.  The <version> field indicates the highest

What does it mean to provide these for other codes?


S 5.2.
>   
>              Figure 4: Structure of CLUE 'optionsResponse' message
>   
>      Upon reception of the 'optionsResponse' the version to be used is the
>      one provided in the <version> tag of the message.  The following CLUE
>      messages MUST use such a version number in the "v" attribute.  The

What goes in the "v" attribute for this message?


S 5.5.
>      </xs:complexType>
>   
>                 Figure 7: Structure of CLUE 'configure' message
>   
>      The <advSequenceNr> element contains the sequence number of the
>      'advertisement' message the 'configure' refers to.

It would be useful to mention here how out of date configures are
handled.


S 6.
>      herein discuss the state machines associated, respectively, with the
>      CLUE Participant (Figure 10), with the MC process (Figure 11) and
>      with the MP process (Figure 12).  Endpoints often wish to both send
>      and receive media, i.e., act as both MP and MC.  As such there will
>      often be two sets of messages flowing in opposite directions; the
>      state machines of these two flows do not interact with each other.

This point would have been useful to make earlier.


S 6.2.
>      successfully agreed on the media streams to be shared.  Then, the MC
>      can move to the ESTABLISHED state.  On the other hand, if an error
>      response is received ("error configureResponse received"), the MC
>      moves back to the CONF state to prepare a new 'configure' request.
>      If a new 'advertisement' is received in the WAIT FOR CONF RESPONSE
>      state, the MC switches to the ADV PROCESSING state.

I agree with what others have said here. It seems like only certain
errors merit this.


S 10.
>   </xs:schema>
>   
>                    Figure 16: Schema defining CLUE messages
>   
>   10.  Call flow example
>   

This would be vastly more useful earlier.



From nobody Mon Nov 19 20:42:06 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 899B2130E0E; Mon, 19 Nov 2018 20:42:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Eric Rescorla <ekr@rtfm.com>
To: "The IESG" <iesg@ietf.org>
Cc: "Daniel C. Burnett" <danielcburnett@gmail.com>, clue@ietf.org, roni.even@mail01.huawei.com, Roni Even <roni.even@mail01.huawei.com>, clue-chairs@ietf.org, draft-ietf-clue-signaling@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.88.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154268892146.26648.17870778354406192041.idtracker@ietfa.amsl.com>
Date: Mon, 19 Nov 2018 20:42:01 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/P76SHlUPQ-Sgmnv-41Q5aXwsqpw>
Subject: [clue] Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 04:42:06 -0000

Eric Rescorla has entered the following ballot position for
draft-ietf-clue-signaling-14: No Objection

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


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


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



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

Rich version of this review at:
https://mozphab-ietf.devsvcdev.mozaws.net/D4099



COMMENTS
S 12.
>      via DTLS-SRTP [RFC5763] on CLUE-controlled RTP "m=" lines.  All CLUE-
>      controlled RTP "m" lines must be secured and implemented using
>      mechanisms such as SRTP [RFC3711].  CLUE implementations MAY choose
>      not to require the use of SRTP to secure legacy (non-CLUE-controlled)
>      media for backwards compatibility with older SIP clients that are
>      incapable of supporting it.

It seems like you need more than support, you also need to require the
use of DTLS-SRTP, no?



From nobody Mon Nov 19 21:32:44 2018
Return-Path: <ben@nostrum.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B04681293FB; Mon, 19 Nov 2018 21:32:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level: 
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-4KoScIQdkz; Mon, 19 Nov 2018 21:32:42 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18AC4127332; Mon, 19 Nov 2018 21:32:42 -0800 (PST)
Received: from [10.0.1.24] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id wAK5WbFj003398 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 19 Nov 2018 23:32:37 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.24]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <B30E6067-2E81-4F43-BF8B-6BD26F6F6BCF@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_3FDEA8E0-F443-40D4-BF1B-408C3F055127"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
Date: Mon, 19 Nov 2018 23:32:36 -0600
In-Reply-To: <154268515769.26665.4530527657139603206.idtracker@ietfa.amsl.com>
Cc: clue-chairs@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, clue@ietf.org, pkyzivat@alum.mit.edu, draft-ietf-clue-protocol@ietf.org
To: The IESG <iesg@ietf.org>
References: <154268515769.26665.4530527657139603206.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/tlozvDpVvT_R84VU8as5G4EYfeg>
Subject: Re: [clue] Ben Campbell's Discuss on draft-ietf-clue-protocol-17: (with DISCUSS and COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 05:32:44 -0000

--Apple-Mail=_3FDEA8E0-F443-40D4-BF1B-408C3F055127
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_6B3FD601-30AC-40F3-8700-670A60FAA01D"


--Apple-Mail=_6B3FD601-30AC-40F3-8700-670A60FAA01D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


Responding to my own comments:

> On Nov 19, 2018, at 9:39 PM, Ben Campbell <ben@nostrum.com> wrote:
>=20
> - Abstract: Is CLUE an acronym? If so, what is its expansion? (If the =
title is
> the expansion, it's very obscure.). If not, why all-caps?

I remembered the acronym expansion after submitting this. It was =
especially creative in its obscurity; Only the first word got an =
initial, and the word =E2=80=9Cstream=E2=80=9D didn't even get a letter.

 I don=E2=80=99t expect any action on this point, but I also expect we =
will live to regret that expansion :-)

Thanks!

Ben.


--Apple-Mail=_6B3FD601-30AC-40F3-8700-670A60FAA01D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div>Responding to my own comments:</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Nov =
19, 2018, at 9:39 PM, Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com" =
class=3D"">ben@nostrum.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">- Abstract: Is CLUE an acronym? =
If so, what is its expansion? (If the title is</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">the expansion, it's very =
obscure.). If not, why all-caps?</span><br style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""></div></blockquote><br =
class=3D""></div><div>I remembered the acronym expansion after =
submitting this. It was especially creative in its obscurity; Only the =
first word got an initial, and the word =E2=80=9Cstream=E2=80=9D didn't =
even get a letter.</div><div><br class=3D""></div><div>&nbsp;I don=E2=80=99=
t expect any action on this point, but I also expect we will live to =
regret that expansion :-)</div><div><br =
class=3D""></div><div>Thanks!</div><div><br =
class=3D""></div><div>Ben.</div><br class=3D""></body></html>=

--Apple-Mail=_6B3FD601-30AC-40F3-8700-670A60FAA01D--

--Apple-Mail=_3FDEA8E0-F443-40D4-BF1B-408C3F055127
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlvznHQACgkQgFZKbJXz
1A1D2Q//XFl1r0IxhtLMRaRBfq7Ri+phFqVSRrYRMf9nCgJlET8ClnpAu21tF/Os
opSvon1ODChjIh4uUu1NANZeSPu0mmoecWzOoZuUc+G+gEFQvrtwJqrhFlJKvcsz
zqtWTt5i0jFGdPSAVcJ5fS9rEazEKbDZ9w/udoG8HG5gtZ6ukQ7L04ViZ374TSiR
wfE5rSqZBCZ9W5sNWP57V9tFvxSfpAT3oXkYKtMx/EqBFoQQUnHM5iRb/jUWoVH9
sT1MKyM07yV/T9V7CZopk+Xw/8hzpmp+p0h/jzvn1Xmm7w1Y2aC7FYJe0tQrYArp
67/XZerFswRdzOwlCw4WRApqId3TnmKwpg3hBHhV9zX/F8oUYXXSSvFu/32RuQCZ
4bKm5buGX/uDQdgZ3Da8cRvKKGI2q4Z6j+X2TmyyuT0oKG3RfodilDvxCTClCp8F
tMnzgiaXYfg9JT1pJB3HjYMoVRwVsjQPAD6DW9CV6Qh54qgSAJlpdsUZ9PDX7+oA
ROG7wzdwqyAtNJZQZF4ZXoplUXr19CTe5edHWmiSZUZCzlK+PgNBaEDNeRuIa1a2
3qrSI2RUWbe8hXe4MBg1td7VcBqyXBcY3s4L9oT6cjFK8ADQyzYS/ztijmgC8LKv
SA7RbTdLuioXEI3ONHVnpvsSEJZklKFGn7CQ/vvrpq+GPtFnRk4=
=YF/i
-----END PGP SIGNATURE-----

--Apple-Mail=_3FDEA8E0-F443-40D4-BF1B-408C3F055127--


From nobody Tue Nov 20 08:49:49 2018
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 592C0130DD6; Tue, 20 Nov 2018 08:49:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-clue-protocol@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, clue-chairs@ietf.org, pkyzivat@alum.mit.edu, clue@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.88.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154273258728.18467.13818258072714840442.idtracker@ietfa.amsl.com>
Date: Tue, 20 Nov 2018 08:49:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/UUuUhggRTs8pSpGYaY8c9HFCStM>
Subject: [clue] Alexey Melnikov's No Objection on draft-ietf-clue-protocol-17: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 16:49:48 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-clue-protocol-17: No Objection

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


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


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



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

I support Ben's DISCUSS.

A couple of extra nits, which I think need addressing:

XML and XML Schema need to be a Normative References.

12.4.1.  CLUE Message Types

   +-------------------+-----------------------------------+-----------+
   | Message           | Description                       | Reference |
   +-------------------+-----------------------------------+-----------+
   | options           | Sent by the CI to the CR  in the  | RFCXXXX   |
   |                   | initiation phase to specify the   |           |
   |                   | roles played by the CI, the       |           |
   |                   | supported versions and the        |           |
   |                   | supported extensions.             |           |
   | optionsResponse   | Sent by the CI to the CR in reply | RFCXXXX   |

Should the above be: "Sent by the CR to the CI ..."

   |                   | to an 'options' message to        |           |
   |                   | finally estabilsh the version and |           |

Typo: establish

   |                   | the extensions to be used in the  |           |
   |                   | following CLUE messages exchange. |           |

Examples in Section 10 contain URI
"http://wpage.unina.it/spromano/clue-protocol-17-schema-file.xsd". Maybe they
shouldn't.



From nobody Tue Nov 20 09:41:18 2018
Return-Path: <alissa@cooperw.in>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F67212008A; Tue, 20 Nov 2018 09:41:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-clue-protocol@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, clue-chairs@ietf.org, pkyzivat@alum.mit.edu, clue@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154273567651.29950.1856997742921373295.idtracker@ietfa.amsl.com>
Date: Tue, 20 Nov 2018 09:41:16 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/v0wAQgGlc__hS_em0JcJy1Y_E9s>
Subject: [clue] Alissa Cooper's No Objection on draft-ietf-clue-protocol-17: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 17:41:17 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-clue-protocol-17: No Objection

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


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


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



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

Section 5.7: I don't understand why the 100-199 range is reserved for a
specific purpose for a future major version rather than having codes in that
range defined now. That is, if it is discovered that delay or incompleteness is
useful to signal, why would establishing support for that necessarily require
some other backwards-incompatible change to the protocol?

Section 8: In addition to Benjamin's question about the version I don't
understand how the schemaRef having minOccurs=0 makes sense. Doesn't it need to
be included?



From nobody Tue Nov 20 09:42:06 2018
Return-Path: <alissa@cooperw.in>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4EC12008A; Tue, 20 Nov 2018 09:42:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-clue-protocol@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, clue-chairs@ietf.org, pkyzivat@alum.mit.edu, clue@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154273572464.29810.8913835992627968908.idtracker@ietfa.amsl.com>
Date: Tue, 20 Nov 2018 09:42:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/dT1uKugcSZnyBkeWmTGjw7KVUzc>
Subject: [clue] Alissa Cooper's No Objection on draft-ietf-clue-protocol-17: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 17:42:05 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-clue-protocol-17: No Objection

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


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


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



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

Please address the Gen-ART review comments.

Section 5.7: I don't understand why the 100-199 range is reserved for a
specific purpose for a future major version rather than having codes in that
range defined now. That is, if it is discovered that delay or incompleteness is
useful to signal, why would establishing support for that necessarily require
some other backwards-incompatible change to the protocol?

Section 8: In addition to Benjamin's question about the version I don't
understand how the schemaRef having minOccurs=0 makes sense. Doesn't it need to
be included?



From nobody Tue Nov 20 09:43:04 2018
Return-Path: <alissa@cooperw.in>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF905130DC8; Tue, 20 Nov 2018 09:42:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=Y0tezTbD; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Q6g+uG1r
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 Rb7fO3LZ0LU9; Tue, 20 Nov 2018 09:42:53 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55F1F130DCD; Tue, 20 Nov 2018 09:42:50 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 3FDA724202; Tue, 20 Nov 2018 12:42:47 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Tue, 20 Nov 2018 12:42:47 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=f eaFKzyF1MpaPvm7yEHV9V5vg+B6/ZQpJS4jxXNl+6I=; b=Y0tezTbDhX0ln9WUu Q0+ZWOdqhDID/6nRCPLecmcFwW7GNrwNMuz02FMDK+d9/wTmp15pnNlJ6Cb7PYu0 OTepGjDDdW/AosObpMEXeyXHWj0uYdKj73t7YZyZs+JZhIMh+i8UnP9lUTxbI0uW yubMmiMAIceTe7y6mHwUkrjsT80WA2raLZVcq8D+ri81t8sZmK0nioftODT4BWoX ekVW1TzxVa0w0xCZJzfBjXT4rWacqv7NjJZu7UEhj9SNNM/F8IoSNmVIoZNRazhC B2O9IZKVoWSQHXvPzM1rOjH3ryCCBplveZP/HUHPMa/heDe+ixnbDbEngkyQzhdP BeNog==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=feaFKzyF1MpaPvm7yEHV9V5vg+B6/ZQpJS4jxXNl+ 6I=; b=Q6g+uG1rvVKYbECZwTBDdxTEyWc18Tsc8oucVXQbBxE3vhkkgchGH15NG BqQ73FhMcdB8M6Z2vDhsjK/b21MdjxbmunFgE0+iZRblujq+m4+G2ES4V1BN+XrH YX/58X5miSz1coajilVGWyqvQel+i8u+VKwimPW+9JvwwldSHCaHSOEBIobX3zQA GpIfN6Jk/NsC78uSPs9BXuc89bwtWS237tNMDSPEsmadi5AWHKqlz/Y/zai7tmbh BGxuJKTlbkNQ4yRlV8+AMZStMifrtZZzAjaH8/8076PDSYOUhh5Idq7zUCF759es TuGt7+4oQvAeQ7dgByc8JWsuOLayg==
X-ME-Sender: <xms:lkf0WzCzy8N5mAg0mhosF6zmVkvzjJSj7Lvx1_NS1ay1liIxaIlS5g>
X-ME-Proxy: <xmx:lkf0W8FrG5MHo0igBQu_8saYT9uFOse838YLNXhdYZaknAr_HjvrwA> <xmx:lkf0W1fI-QPgZQNgSR4om1o4537yiZXH3cgMUvsQdLTPu3sp7NU7ow> <xmx:lkf0W-GAX6u-RWro7ZFPghwIPi3W_NhLHVsldSc_XxFn5IYhwkbveA> <xmx:lkf0W2XGDhaHT9fXvJ9ccMhgj7hlrQDHSSQAMi5MQH9NVdWuwT5MWQ> <xmx:lkf0W9JEj5NGk2xNFdZiIF59ezDriOEkcetEejTVB3x5MUoFptJFkQ> <xmx:l0f0W4VCOmcHDck2knudHmzrg4cuPDs0LTWauliiwl04pM8jk77sMQ>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.92]) by mail.messagingengine.com (Postfix) with ESMTPA id 38F57102DE; Tue, 20 Nov 2018 12:42:46 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <201810180859.w9I8xRaU022814@givry.fdupont.fr>
Date: Tue, 20 Nov 2018 12:42:45 -0500
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-clue-protocol.all@ietf.org, clue@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <73144965-FC20-453E-9206-6BB1B167053B@cooperw.in>
References: <201810180859.w9I8xRaU022814@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/Q-seAJY66ERU5fJF0VgsNJE5XFE>
Subject: Re: [clue] [Gen-art] review of draft-ietf-clue-protocol-17.txt
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 17:42:56 -0000

Francis, thanks for your review. I have not seen a response yet so =
I=E2=80=99ve flagged your review in my No Objection ballot.

Alissa

> On Oct 18, 2018, at 4:59 AM, Francis Dupont =
<Francis.Dupont@fdupont.fr> wrote:
>=20
> 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.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-clue-protocol-17.txt
> Reviewer: Francis Dupont
> Review Date: 20181017
> IETF LC End Date: 20181017
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:=20
> I have a problem with the CLUE abbrev itself (which BTW is not in the
> RFC Editor abbrev list
> https://www.rfc-editor.org/materials/abbrev.expansion.txt):
> in theory the abbrev should be introduced at its first use in the =
Abstract
> and in the body (so 1 introduction) but this seems to be overkilling
> and not really solving the issue so I have a better proposal: ask
> the RFC Editor if it is not possible to add the CLUE abbrev in the
> list as a well known one.
>=20
> - Abstract page 1: you use SCTP over DTLS so a transport over another
> transport. At the first view it looks strange but in fact it should be
> the simplest solution to add security to SCTP so I have no concern =
about
> this.
>=20
> - 4 page 5 twice: version numbers are qualified as "single digit" =
which
> does not match the syntax 5 figure 1 page 8 nor examples: please =
remove
> these.
>=20
> - 5 page 8: the version number syntax. BTW it allows a minor version
> to begin by a 0 followed by other digits which perhaps is not what
> you want.
>=20
> - 5 page 8: same comment about examples: a priori 1.01 is legal and
>  it is not clear if it is the same than 1.1 ?
>=20
> - 5 page 8 (before the previous one): procotol -> protocol
>=20
> - 5.1 page 11: IMHO in "<supportedVersion> is provided ..."
>  it shoild be <supportedVersions>.
>=20
> - 5.4 page 13: I noted you use the UK spelling for the type name
> (Acknowledgement vs. Acknowledgment).
>=20
> - 5.7 page 17 figure 9 and 12.4.2 page 65:
> Please remove the final dot in " Low-level request error."
>=20
> - 11 page 60: defence -> defense (UK vs US English)
>=20
> - 12.4.1 page 64: estabilsh -> establish
>=20
> - 12.4.2 page 65: Conficting -> Conflicting
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Nov 20 10:26:59 2018
Return-Path: <ben@nostrum.com>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B71031277BB; Tue, 20 Nov 2018 10:26:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Ben Campbell <ben@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-clue-signaling@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Roni Even <roni.even@mail01.huawei.com>, clue-chairs@ietf.org, roni.even@mail01.huawei.com, clue@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154273841271.29820.17924219884246634745.idtracker@ietfa.amsl.com>
Date: Tue, 20 Nov 2018 10:26:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/eEgqtMp6hvAcrx3EEqsIa_3lI7s>
Subject: [clue] Ben Campbell's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 18:26:53 -0000

Ben Campbell has entered the following ballot position for
draft-ietf-clue-signaling-14: No Objection

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


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


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



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

Thanks for the work on this. I have some substantive and editorial comments:

*** Substantive Comments ***

§2: Is there a reason not to use the new (preferred) boilerplate from RFC 8174?
There are a lot of lower case instances of "must" and "should". These are
ambiguous under the old boilerplate.

§4.4.1.1: "Each <encID> (in encodingIDList) in a CLUE ADVERTISEMENT message
SHOULD represent an Encoding defined in SDP..."

I started out asking why this was not a MUST. But after reading the discussion
in §5.1 and elsewhere, I think the issue is too nuanced to be conveyed by a
single normative keyword. Perhaps this should say something to the effect of
"SHOULD converge to representing...". Or even "will eventually represent...but
may not match for short time after encoding changes..."  (The same applies to
the SHOULD in the following paragraph.)

§4.5.1:

- What sort of user experience is expected when a CLUE device talks to a
non-CLUE device? Is this a realistic use case? (I'm not saying it's not; I'm
just asking.)

- "If the device has evidence that the receiver is also CLUE-capable,
for instance due to receiving an initial INVITE with no SDP but
including a "sip.clue" media feature tag,"

 Is it reasonable to remember CLUE support from previous sessions? I suspect
 the answer is  "no", due to SIP forking issues, but I think it's worth
 guidance one way or the other.)

§5.1: "A device with the CLUE Participant state machine in the ACTIVE state
MAY choose not to move from ESTABLISHED to ADV (Media Provider state
machine) or from ESTABLISHED to WAIT FOR CONF RESPONSE (Media
Consumer state machine) based on the SDP state."

 I'm not sure what that means. Is the specific SDP state a reason for skipping
 the state transition specified in due-protocol? or is it saying that an
 endpoint can choose not to let SDP state trigger a CLUE state change when it
 normally would?

*** Editorial Comments ***

- General: This document does not follow the protocol draft's convention for
naming message types. For example, this draft refers to ADVERTISEMENT while the
protocol draft says  'advertisement'  (in single quotes). I don't have strong
feelings which to use, but the two should be consistent.

§5: Is "CLUE channel" the same as the datachannel that carries the CLUE
protocol?

§5.1: "Because of the constraints of SDP offer/answer and because new SDP
negotiations are generally more ’costly’ than sending a new CLUE
message..."
Why the 'scare quotes' around "costly"?



From nobody Tue Nov 20 10:54:22 2018
Return-Path: <alissa@cooperw.in>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F23112D4E9; Tue, 20 Nov 2018 10:54:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=H0mcaE3C; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=fi4EYuTf
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 POYh-MminQm4; Tue, 20 Nov 2018 10:54:18 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 487131277BB; Tue, 20 Nov 2018 10:54:15 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 52CB124644; Tue, 20 Nov 2018 13:54:14 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Tue, 20 Nov 2018 13:54:14 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=4 HsCPBIdKB/v0JEWRd4K4yQpGdoYqKuoXBj1EUYY7a0=; b=H0mcaE3C7pnSmYJQe NB0UrYxTsYrSZHnG3r0/yKWljRJvjaSAUDRe7vrBwJ1vRoS7pEjnGSpNnQ/CeA10 GwrIm8dcR7Kb98uJKtYK5NXiMkvi4dNRMvTI3IBrYpp1Ix2ciAjKQ8H0eECzIVgp Ou/kHeoc71zxEK9sgTGz631ZBCfEuph3FflU2s85vrOhFpiVj3KPqlJj1tuxwJey 2EIQaVuNWmhH7DV6cJeDI5O3Zrf/37FWA2nZP1GtqU1RzNGwfOfW+6a5uDfOpq4x gDS7HT0JNxFvL/L1mcsfHgngZsPS207s0hIthsxDX9atQH6j7FwAm6zu/gv8QZHy hmqEQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=4HsCPBIdKB/v0JEWRd4K4yQpGdoYqKuoXBj1EUYY7 a0=; b=fi4EYuTfRv4h0aI8tDCj0GG10fpJZ5UZWmHviGc8vm0rylG57So8MmG9s hO16BNYLfr+cloxYufyByvO8Rn8NHN5HLJw6c6z9mWE3DEKy6bdEWVF/kj4sPIDm X8JukeunBoeTCm57p/Q4IW053ZxPgP3hN3ivkviFR+zraqkbT7MRjhQ6XLH4n7/A iM34+zscPvXDHrCxGiLmonk+cDOi85QWu5D3qsNF3W7tXexxmeGe/IX9c/9Wg0bQ gRPXIUpDgn82dqJVPnNZgHqSalnzl/0l/wsjuCHT6sInD53iLkRSLrtX9C0BznMq BWrvkVIDlDolQP+EW3+ujochDGhOw==
X-ME-Sender: <xms:VVj0W0wo0RChhvKZA12KX_HFz5p4BR9-eW8X1FBGNyV8cE14cRrmkQ>
X-ME-Proxy: <xmx:VVj0Wy9nrYVvkdQePAMjmT0ma4TLvZXGMCdgkxm8O0w3AIn0Z7sf4A> <xmx:VVj0W6WhlI62z32NKwMF5ouxMaXqKHZg1FSu5USMmxjjfFv6bzjEEw> <xmx:Vlj0W4MYaG4GFeMODdVI8e0rXIRDtXtfB0zWZuGzCcCN2V6tpcdm7A> <xmx:Vlj0WycH3iF80gX2WeUgagMrZzyuCGui_RDHsBlfJovz5fa1aQpKpg> <xmx:Vlj0W3y8-xW5Lr2aqn6-BAN0k5KeVMl-yVNJklV2Cs8nPs5scOzxFA> <xmx:Vlj0W5sc-cZpiwwM2tJiANbOljwtecdioilS3FJmTQ_ph5HjNvJ8pQ>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.92]) by mail.messagingengine.com (Postfix) with ESMTPA id 968CFE491E; Tue, 20 Nov 2018 13:54:13 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <154110678434.25382.16163243596596461379@ietfa.amsl.com>
Date: Tue, 20 Nov 2018 13:54:12 -0500
Cc: gen-art@ietf.org, clue@ietf.org, ietf@ietf.org, draft-ietf-clue-signaling.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB226C47-B64A-4EF4-8FEB-69F5C3503BD5@cooperw.in>
References: <154110678434.25382.16163243596596461379@ietfa.amsl.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/645-nIrHGGKMLk_Xq_WudKlFZkA>
Subject: Re: [clue] [Gen-art] Genart telechat review of draft-ietf-clue-signaling-14
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 18:54:21 -0000

Robert, thank you for your reviews of this document. I have entered a No =
Objection ballot.

Alissa

> On Nov 1, 2018, at 5:13 PM, Robert Sparks <rjsparks@nostrum.com> =
wrote:
>=20
> Reviewer: Robert Sparks
> Review result: Ready
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-clue-signaling-14
> Reviewer: Robert Sparks
> Review Date: 2018-11-01
> IETF LC End Date: 2018-10-17
> IESG Telechat date: 2018-11-21
>=20
> Summary: Ready for publication as a Proposed Standard
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Nov 20 11:34:26 2018
Return-Path: <paul.kyzivat@comcast.net>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B7D6130DD2 for <clue@ietfa.amsl.com>; Tue, 20 Nov 2018 11:34:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.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 B9oTAWgnpDXl for <clue@ietfa.amsl.com>; Tue, 20 Nov 2018 11:34:23 -0800 (PST)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (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 CB927130DC6 for <clue@ietf.org>; Tue, 20 Nov 2018 11:34:23 -0800 (PST)
Received: from resomta-ch2-08v.sys.comcast.net ([69.252.207.104]) by resqmta-ch2-01v.sys.comcast.net with ESMTP id PA7VgZT9PPqi4PBmwgmDMZ; Tue, 20 Nov 2018 19:34:22 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1542742462; bh=A+NZtPLBOsnoMNnZMaWcjPJ2eTgKhJtDFGehoL1AwPg=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=Wth05TE79f/5oT80t/TXwjj9s3Zdzk4Wx9ANe46z5WyXFSXqEvcksEmHf8eZPG+HG qjQ/rZZGE1XzgLnghu0BzJo82kI8EBNbq+RvrE3PC1fsOrxGReh3w79BE50vxEPtB+ qYMwjDK4MTJvrORzKgvmxzROcDRWzxxwi56vXfA6xe3apJWzhXQYWzWm9NOnqPk5ti wH0G+e/TcjZLHS5jMi0sF6YBY63JD+CG6cCIxeQTqQWYA11oG7lzBe6v8sjVqA1wkX pLlRLAARtmlECcsJqTjxNMS75HWk7jsYJSq8GhAnPjMJ/c+N6mKdq0jmyXlC2wwjVu 4JCVD2oBAW3DQ==
Received: from PaulKyzivatsMBP.localdomain ([24.62.227.142]) by resomta-ch2-08v.sys.comcast.net with ESMTPA id PBmvgy5hrWw14PBmwgzlYz; Tue, 20 Nov 2018 19:34:22 +0000
To: Ben Campbell <ben@nostrum.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-clue-signaling@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Roni Even <roni.even@mail01.huawei.com>, clue-chairs@ietf.org, clue@ietf.org
References: <154273841271.29820.17924219884246634745.idtracker@ietfa.amsl.com>
From: Paul Kyzivat <paul.kyzivat@comcast.net>
Message-ID: <977036c6-db84-cb8e-c317-46d008e9a81b@comcast.net>
Date: Tue, 20 Nov 2018 14:34:21 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <154273841271.29820.17924219884246634745.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfDQPkW2HqJ9voWH7G2HxeriXvqU5TbTFfE3dsHLqMXa17srLVlROrRlx6rSoOMiQYrrkEiOPJuUQk/gbGQkN/id15YpdNdVIfHLKH9aGboQHSN17ZWod fawEQxv/pzy4wPxET3gANjMEaSStypQeN84VJchb5umPWiEFpr8y0WA/v5Y6RWH9Gkw073HjfjIsoEs8kkUQZNbLxVeRLADrvU+caCndBgLBenND6LehQJaZ n5W38GU3p3pLVBvYAwbzSB3Ea276pCkV59PYdjwIR00S0T+CMfLAyb7why7ZbfHShROg0s8vIPCWjDUsP+kutHTIBAZDY7ZrFflbRvQ/YmmKJNcYn9wzgwuU j0PznSwspN8LdyRH39cGnf8z7ItA/v1Dk5dDPFsj6fUdMvZy4+o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/FTPW-IX-WGXLv0FJ0YbVSwgZYds>
Subject: Re: [clue] Ben Campbell's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 19:34:25 -0000

On 11/20/18 1:26 PM, Ben Campbell wrote:

> §4.5.1:
> 
> - What sort of user experience is expected when a CLUE device talks to a
> non-CLUE device? Is this a realistic use case? (I'm not saying it's not; I'm
> just asking.)

If the non-clue device is audio-only then you will get an audio call. If 
it is an audio/video device then you will get a basic audio/video call.

This can be entirely reasonable. For instance, if you have a 
clue-capable device on your desktop, you can use it for all of your 
calls. If the call is being originated from a clue-based conference 
room, inviting multiple clients, somebody in their car can be included 
in the call.

> - "If the device has evidence that the receiver is also CLUE-capable,
> for instance due to receiving an initial INVITE with no SDP but
> including a "sip.clue" media feature tag,"
> 
>   Is it reasonable to remember CLUE support from previous sessions? I suspect
>   the answer is  "no", due to SIP forking issues, but I think it's worth
>   guidance one way or the other.)

This doesn't have to be from a prior session. The initial call may be an 
offerless invite (e.g., from a 3pcc controller). If the caller indicates 
support for clue then the callee can respond with an offer of a clue 
session.

	Thanks,
	Paul


From nobody Tue Nov 20 11:40:04 2018
Return-Path: <ben@nostrum.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71741130DD0; Tue, 20 Nov 2018 11:40:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=unavailable 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 kwMIGzuIhv42; Tue, 20 Nov 2018 11:39:53 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id A82B3130DCF; Tue, 20 Nov 2018 11:39:51 -0800 (PST)
Received: from [10.0.1.24] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id wAKJdRkn042709 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 20 Nov 2018 13:39:28 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.24]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <065E26A1-EDB6-4487-804F-882DF4F7101A@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_00BE8791-82BF-4A2D-9127-F8B6DFB53D86"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
Date: Tue, 20 Nov 2018 13:39:27 -0600
In-Reply-To: <977036c6-db84-cb8e-c317-46d008e9a81b@comcast.net>
Cc: The IESG <iesg@ietf.org>, draft-ietf-clue-signaling@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Roni Even <roni.even@mail01.huawei.com>, clue-chairs@ietf.org, clue@ietf.org
To: Paul Kyzivat <paul.kyzivat@comcast.net>
References: <154273841271.29820.17924219884246634745.idtracker@ietfa.amsl.com> <977036c6-db84-cb8e-c317-46d008e9a81b@comcast.net>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/emTWl_BMTIbixMXQRQ_NNzEHrvo>
Subject: Re: [clue] Ben Campbell's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 19:40:04 -0000

--Apple-Mail=_00BE8791-82BF-4A2D-9127-F8B6DFB53D86
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Nov 20, 2018, at 1:34 PM, Paul Kyzivat <paul.kyzivat@comcast.net> =
wrote:
>=20
> On 11/20/18 1:26 PM, Ben Campbell wrote:
>=20
>> =C2=A74.5.1:
>> - What sort of user experience is expected when a CLUE device talks =
to a
>> non-CLUE device? Is this a realistic use case? (I'm not saying it's =
not; I'm
>> just asking.)
>=20
> If the non-clue device is audio-only then you will get an audio call. =
If it is an audio/video device then you will get a basic audio/video =
call.
>=20
> This can be entirely reasonable. For instance, if you have a =
clue-capable device on your desktop, you can use it for all of your =
calls. If the call is being originated from a clue-based conference =
room, inviting multiple clients, somebody in their car can be included =
in the call.

Okay, that makes sense. I wasn=E2=80=99t thinking about =E2=80=9Cdesktop=E2=
=80=9D CLUE devices, I guess.

>=20
>> - "If the device has evidence that the receiver is also CLUE-capable,
>> for instance due to receiving an initial INVITE with no SDP but
>> including a "sip.clue" media feature tag,"
>>  Is it reasonable to remember CLUE support from previous sessions? I =
suspect
>>  the answer is  "no", due to SIP forking issues, but I think it's =
worth
>>  guidance one way or the other.)
>=20
> This doesn't have to be from a prior session. The initial call may be =
an offerless invite (e.g., from a 3pcc controller). If the caller =
indicates support for clue then the callee can respond with an offer of =
a clue session.
>=20

To be clear, I was wondering if remembering past sessions was an =
_additional_ way to =E2=80=9Cknow=E2=80=9D a peer is clue capable. In =
particular, if it=E2=80=99s not a good idea it would be worth mentioning =
that, because I suspect implementors might get creative in that =
particular direction.

Thanks!

Ben.


--Apple-Mail=_00BE8791-82BF-4A2D-9127-F8B6DFB53D86
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlv0Yu8ACgkQgFZKbJXz
1A3wKxAAo0olLPa3yvRsixrqWC25IOzzM5HkUtGJiEtpqz9AVX1phKUPiWK1/0Xi
FCUrZod5o5p2uk60lL19xd9YAVlnzRyqa5qtu96tUVn0cjLD22laYBrvXUTjcske
ACJXOmNaFnnG8WZVR53oip9oTLpEmGBbuT5ec0o95AU7gv8y4HePoFVWvMze37Rc
QDps9yT0nLKniHmQNDoMtpwJ5Su0pMXsqb2UzIGOUIQ4WG+Num1PsLeKqijrszHp
zeSOH9XiglznxAcWIalKqP2R1Vsk0P8v5QSAwLNgopOundCroqfrQpZueQAKxiCC
pWICXP3F4WxXoxlSGN85JZ5xTHBhfmjC+bl7BMtgfMYGuEsk8MlYqw0tQebYeOYo
h59+3WLbCXVj1/CllGM7ALRHS+u7JOL77x6vyU3Rwun+ljcIxZ2mGoisUKE8+KyP
2xAhX/A+eKUb+JweZsaVOgwNz5GTl4/xcAP1ZnxJ2z0V9Uslladnej18s0IwXo9t
fV0AD71ayNrFLunyAyGevng2B7Mci0vPz/H5ajOVubRpZ8Ff1Js1hRWAHAQSPc4j
FWu75LPspQYGFm6MyM3eXKvap0d4ZblxFt6pPi2D8Opts/xcEpmcDXN5dlvwdw9+
ULpNguxeiyFVHhLEB3iRYWE1yCclRDOkoi8LwMdqP+6sFyti2oA=
=opWT
-----END PGP SIGNATURE-----

--Apple-Mail=_00BE8791-82BF-4A2D-9127-F8B6DFB53D86--


From nobody Tue Nov 20 12:15:29 2018
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2601B130E2A; Tue, 20 Nov 2018 12:15:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tHbKZE1paVTL; Tue, 20 Nov 2018 12:15:21 -0800 (PST)
Received: from alum-mailsec-scanner-5.mit.edu (alum-mailsec-scanner-5.mit.edu [18.7.68.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9479B130E70;  Tue, 20 Nov 2018 12:15:18 -0800 (PST)
X-AuditID: 12074411-57bff70000007049-1d-5bf46b552dc0
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id A4.77.28745.55B64FB5; Tue, 20 Nov 2018 15:15:17 -0500 (EST)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id wAKKFFqE024673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 20 Nov 2018 15:15:16 -0500
To: Ben Campbell <ben@nostrum.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-clue-signaling@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Roni Even <roni.even@mail01.huawei.com>, clue-chairs@ietf.org, clue@ietf.org
References: <154273841271.29820.17924219884246634745.idtracker@ietfa.amsl.com> <977036c6-db84-cb8e-c317-46d008e9a81b@comcast.net> <065E26A1-EDB6-4487-804F-882DF4F7101A@nostrum.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <e1321782-7904-c904-93cc-5036880ef195@alum.mit.edu>
Date: Tue, 20 Nov 2018 15:15:15 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <065E26A1-EDB6-4487-804F-882DF4F7101A@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sb0gTcRzG+d2d2zl2cp7KflnOHPRmNrVSGWnlC6FBfzClXswwT3duw+1m d5tor0SFVKLMKOaUDFKh6RsVw5FiLiZpIZhIf6BSGolCxKYjrWndudS9e+D5PM/Dj98XR6mB mGTczNoZjqUtKokMo6SFaZqr1RulWUuNR7U9rW+k2lBHr0Q7ObuAaoc86dqf74YRrTN8H9X6 mzfRAqnO4/os1fX2biG6sZGlGJ3L48eKML0s38BYzLUMl3m2XGZq+OWX1jjJuq/BMGgAQXkb wHFIZsOHXn0biMUpcgqBQz5TRC8jsCVQJOoEUg9Xx1elok4kVXClaRQTNUp+BDAQPNMGZAI/ BuDc6gAQDQmpht3ev7sQQZ6DjZODElFj5DEYbn+/yySRVXC7tRdEmHg40+nf5WMFfu7HChoZ yIWPR5b/awX85O9BIjoVNo12oe2AdEXFXVERV1TEFRV5AjA3UNIWh1Vjpc0WnqnU8JU0yzKc JifDarZnMAbHMIj8QPwYcM4ovYDEgUpOlCdslFIxdC1fb/WCQziiSiIK+tdLqbgKm6HeRPOm G5zDwvBeAHFUlUjMqQWcMND1txjOtmcdxjGVgkCzJ/QUaaTtTDXD1DDcnnsEx1WQWL4kBOM5 xsjUVZkt9gMbwWPFcrlQ7hMZgq+hrbzZGPFnwSl8PNToRHG3s8WJUhhrY5lkBZEkoqSImhzs ftveja0BhfC4BCLlskDJhQvc71sTphBhKuXtujhlpw+s5AZw8rSP6kr13NseU1+bd8fkFlqf 9zU/Nd+ZyTQOdiBU907mVr5k6mbw0eYIQnwJcp0t4fmAr2x69OXEYmHW99fedD2tTJWFTPLF Z/3D35T0Dnu8ONYie5WTJ9u8GHchwNptodt5D6Z/X6fdxQsv7vaVfaiY0v1BPSVXSvLSzqsw 3kSfUKMcT/8D4vjujD4DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/OzoFhp4Frx00HKHRTFudw5neEDo>
Subject: Re: [clue] Ben Campbell's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 20:15:28 -0000

On 11/20/18 2:39 PM, Ben Campbell wrote:
> 
> 
>> On Nov 20, 2018, at 1:34 PM, Paul Kyzivat <paul.kyzivat@comcast.net> wrote:
>>
>> On 11/20/18 1:26 PM, Ben Campbell wrote:
>>
>>> §4.5.1:
>>> - What sort of user experience is expected when a CLUE device talks to a
>>> non-CLUE device? Is this a realistic use case? (I'm not saying it's not; I'm
>>> just asking.)
>>
>> If the non-clue device is audio-only then you will get an audio call. If it is an audio/video device then you will get a basic audio/video call.
>>
>> This can be entirely reasonable. For instance, if you have a clue-capable device on your desktop, you can use it for all of your calls. If the call is being originated from a clue-based conference room, inviting multiple clients, somebody in their car can be included in the call.
> 
> Okay, that makes sense. I wasn’t thinking about “desktop” CLUE devices, I guess.
> 
>>
>>> - "If the device has evidence that the receiver is also CLUE-capable,
>>> for instance due to receiving an initial INVITE with no SDP but
>>> including a "sip.clue" media feature tag,"
>>>   Is it reasonable to remember CLUE support from previous sessions? I suspect
>>>   the answer is  "no", due to SIP forking issues, but I think it's worth
>>>   guidance one way or the other.)
>>
>> This doesn't have to be from a prior session. The initial call may be an offerless invite (e.g., from a 3pcc controller). If the caller indicates support for clue then the callee can respond with an offer of a clue session.
>>
> 
> To be clear, I was wondering if remembering past sessions was an _additional_ way to “know” a peer is clue capable. In particular, if it’s not a good idea it would be worth mentioning that, because I suspect implementors might get creative in that particular direction.

There isn't any real harm in doing this. The worse that will happen is 
that the clue stuff is included in the offer and then rejected in the 
answer. So I have no problem with implementors getting "creative" here.

	Thanks,
	Paul


From nobody Tue Nov 20 12:19:33 2018
Return-Path: <ben@nostrum.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E363E130DDA; Tue, 20 Nov 2018 12:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=unavailable 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 3TZwiOVXtZK5; Tue, 20 Nov 2018 12:19:26 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B57DA130DE0; Tue, 20 Nov 2018 12:19:26 -0800 (PST)
Received: from [10.0.1.24] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id wAKKJJmR049290 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 20 Nov 2018 14:19:20 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.24]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <A998E94D-D0B6-47F4-822D-265A87EA49B2@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_638552CE-707F-47DE-AFD8-169FB9913B59"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
Date: Tue, 20 Nov 2018 14:19:19 -0600
In-Reply-To: <e1321782-7904-c904-93cc-5036880ef195@alum.mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-clue-signaling@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Roni Even <roni.even@mail01.huawei.com>, clue-chairs@ietf.org, clue@ietf.org
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <154273841271.29820.17924219884246634745.idtracker@ietfa.amsl.com> <977036c6-db84-cb8e-c317-46d008e9a81b@comcast.net> <065E26A1-EDB6-4487-804F-882DF4F7101A@nostrum.com> <e1321782-7904-c904-93cc-5036880ef195@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/pZ48fQbR59wFqC_TGPVSYk3DpFs>
Subject: Re: [clue] Ben Campbell's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 20:19:28 -0000

--Apple-Mail=_638552CE-707F-47DE-AFD8-169FB9913B59
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Nov 20, 2018, at 2:15 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>=20
> On 11/20/18 2:39 PM, Ben Campbell wrote:
>>> On Nov 20, 2018, at 1:34 PM, Paul Kyzivat <paul.kyzivat@comcast.net> =
wrote:
>>>=20
>>> On 11/20/18 1:26 PM, Ben Campbell wrote:
>>>=20
>>>> =C2=A74.5.1:
>>>> - What sort of user experience is expected when a CLUE device talks =
to a
>>>> non-CLUE device? Is this a realistic use case? (I'm not saying it's =
not; I'm
>>>> just asking.)
>>>=20
>>> If the non-clue device is audio-only then you will get an audio =
call. If it is an audio/video device then you will get a basic =
audio/video call.
>>>=20
>>> This can be entirely reasonable. For instance, if you have a =
clue-capable device on your desktop, you can use it for all of your =
calls. If the call is being originated from a clue-based conference =
room, inviting multiple clients, somebody in their car can be included =
in the call.
>> Okay, that makes sense. I wasn=E2=80=99t thinking about =E2=80=9Cdeskto=
p=E2=80=9D CLUE devices, I guess.
>>>=20
>>>> - "If the device has evidence that the receiver is also =
CLUE-capable,
>>>> for instance due to receiving an initial INVITE with no SDP but
>>>> including a "sip.clue" media feature tag,"
>>>>  Is it reasonable to remember CLUE support from previous sessions? =
I suspect
>>>>  the answer is  "no", due to SIP forking issues, but I think it's =
worth
>>>>  guidance one way or the other.)
>>>=20
>>> This doesn't have to be from a prior session. The initial call may =
be an offerless invite (e.g., from a 3pcc controller). If the caller =
indicates support for clue then the callee can respond with an offer of =
a clue session.
>>>=20
>> To be clear, I was wondering if remembering past sessions was an =
_additional_ way to =E2=80=9Cknow=E2=80=9D a peer is clue capable. In =
particular, if it=E2=80=99s not a good idea it would be worth mentioning =
that, because I suspect implementors might get creative in that =
particular direction.
>=20
> There isn't any real harm in doing this. The worse that will happen is =
that the clue stuff is included in the offer and then rejected in the =
answer. So I have no problem with implementors getting "creative" here.

Okay. I am fine leaving things as is, unless the authors see value in =
mentioning the possibility.


--Apple-Mail=_638552CE-707F-47DE-AFD8-169FB9913B59
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlv0bEcACgkQgFZKbJXz
1A1iOA//UePMtR5qOc87WZW6jviuNHVyOumlTwDCoh/Plo8P+rhZgYfyUsjqFsrC
UvvikYDckthmFeZgCSqyrmgMOW49mLXUoCXgZ80LeomnhmEwYy0p3fy4ddiQEaj4
WthdBPJzAHzTSFvY6eS/LOsf1j7kgy07pZTQ7uRZrDjspeJd5j3HqPkQMmNGJQy9
ouR6dkd/wF7nVU0FhmN2ux0cl2sW5zgEDorWMiH8frq5smZnlZDRC1JBjZF/wTCX
y711/HrobwJU6qEc5p2X5Huz++sgXGCSdV0gjcThsWoXC0HG4ImxA+PLdj5gD0LV
huRDxtFyhOyphApdsgRSht1dpfiqw8doQdiChr709oTPHxgHjEDS0OVu3CqYdhV0
qtc61CIFgOigOPFiVf1EOtgl+3e+Rs2mtDpAW6pUEAMR8rW/VIhuDYtTy+AAhkw7
SW2mWfow3VRo0sgEXUy6f614ItljsUfGPg+mmY28rr7Tms7zjeclaGjPmZXL3jBI
1f5/C8l3sidZQG0H9e6+sMobVibjD2X8HgawsuDztEggoF14ALYm+z+HfQwJNZAp
CSsjuCGubcggpyUFYSWRgej6lC8TNu6WpbH7uVoEmMY7OAY9jYbXeVofASxldMyw
alVM8fsONoJSY3GF2xRyW4w2K7yGQf3z/88xmx88W5NYDc1nMjo=
=Pe6V
-----END PGP SIGNATURE-----

--Apple-Mail=_638552CE-707F-47DE-AFD8-169FB9913B59--


From nobody Tue Nov 20 13:27:24 2018
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D793124D68; Tue, 20 Nov 2018 13:27:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-clue-signaling@ietf.org, Roni Even <roni.even@huawei.com>, "Daniel C. Burnett" <danielcburnett@gmail.com>, Roni Even <roni.even@mail01.huawei.com>, clue-chairs@ietf.org, roni.even@huawei.com, clue@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154274923410.29769.18226954892657476939.idtracker@ietfa.amsl.com>
Date: Tue, 20 Nov 2018 13:27:14 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/zlGlon-hN-0rnKCcRvMeDiPtwPM>
Subject: [clue] Spencer Dawkins' No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 21:27:14 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-clue-signaling-14: No Objection

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


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


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



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

I agree with Benjamin Kaduk's comment about considering whether
draft-ietf-rtcweb-data-channel should be a normative reference for at least
clue-signaling, but it's worth noting that draft-ietf-rtcweb-data-channel is a
C238 draft in Missref at the RFC Editor, and was approved about the same time
that DTLS 1.2 was published. I'm hoping that there's no reason to look at C238
drafts when we're doing IESG Evaluation for drafts that refer to them (directly
or indirectly), but thought I should ask before CLUE comes out as RFCs.



From nobody Thu Nov 22 03:24:28 2018
Return-Path: <roni.even@huawei.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02800128766; Thu, 22 Nov 2018 03:24:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ecsSPn2QQ7il; Thu, 22 Nov 2018 03:24:24 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 651A71277D2; Thu, 22 Nov 2018 03:24:24 -0800 (PST)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id C34E833FBFAEF; Thu, 22 Nov 2018 11:24:17 +0000 (GMT)
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 22 Nov 2018 11:24:19 +0000
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.89]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0415.000; Thu, 22 Nov 2018 19:24:12 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Eric Rescorla <ekr@rtfm.com>, The IESG <iesg@ietf.org>
CC: "Daniel C. Burnett" <danielcburnett@gmail.com>, "clue@ietf.org" <clue@ietf.org>, "roni.even@mail01.huawei.com" <roni.even@mail01.huawei.com>,  Roni Even <roni.even@mail01.huawei.com>, "clue-chairs@ietf.org" <clue-chairs@ietf.org>, "draft-ietf-clue-signaling@ietf.org" <draft-ietf-clue-signaling@ietf.org>
Thread-Topic: Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
Thread-Index: AQHUgIto2vun7lYtT0WxvGbN4Em2qaVbqbyg
Date: Thu, 22 Nov 2018 11:24:12 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD18C762DF@DGGEMM506-MBX.china.huawei.com>
References: <154268892146.26648.17870778354406192041.idtracker@ietfa.amsl.com>
In-Reply-To: <154268892146.26648.17870778354406192041.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.166]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/QXcQNSyOPYmz3ba9-V42xx0nD8o>
Subject: Re: [clue] Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Nov 2018 11:24:27 -0000

SGksDQpSVFAgcGF5bG9hZHMgZG8gbm90IHJlcXVpcmUgdXNhZ2Ugb2YgU1JUUCBzZWUgUkZDNzIw
MSBhbmQgUkZDNzIwMg0KUm9uaSBFdmVuDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpG
cm9tOiBFcmljIFJlc2NvcmxhIFttYWlsdG86ZWtyQHJ0Zm0uY29tXSANClNlbnQ6IFR1ZXNkYXks
IE5vdmVtYmVyIDIwLCAyMDE4IDY6NDIgQU0NClRvOiBUaGUgSUVTRw0KQ2M6IERhbmllbCBDLiBC
dXJuZXR0OyBjbHVlQGlldGYub3JnOyByb25pLmV2ZW5AbWFpbDAxLmh1YXdlaS5jb207IFJvbmkg
RXZlbjsgY2x1ZS1jaGFpcnNAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtY2x1ZS1zaWduYWxpbmdAaWV0
Zi5vcmcNClN1YmplY3Q6IEVyaWMgUmVzY29ybGEncyBObyBPYmplY3Rpb24gb24gZHJhZnQtaWV0
Zi1jbHVlLXNpZ25hbGluZy0xNDogKHdpdGggQ09NTUVOVCkNCg0KRXJpYyBSZXNjb3JsYSBoYXMg
ZW50ZXJlZCB0aGUgZm9sbG93aW5nIGJhbGxvdCBwb3NpdGlvbiBmb3INCmRyYWZ0LWlldGYtY2x1
ZS1zaWduYWxpbmctMTQ6IE5vIE9iamVjdGlvbg0KDQpXaGVuIHJlc3BvbmRpbmcsIHBsZWFzZSBr
ZWVwIHRoZSBzdWJqZWN0IGxpbmUgaW50YWN0IGFuZCByZXBseSB0byBhbGwgZW1haWwgYWRkcmVz
c2VzIGluY2x1ZGVkIGluIHRoZSBUbyBhbmQgQ0MgbGluZXMuIChGZWVsIGZyZWUgdG8gY3V0IHRo
aXMgaW50cm9kdWN0b3J5IHBhcmFncmFwaCwgaG93ZXZlci4pDQoNCg0KUGxlYXNlIHJlZmVyIHRv
IGh0dHBzOi8vd3d3LmlldGYub3JnL2llc2cvc3RhdGVtZW50L2Rpc2N1c3MtY3JpdGVyaWEuaHRt
bA0KZm9yIG1vcmUgaW5mb3JtYXRpb24gYWJvdXQgSUVTRyBESVNDVVNTIGFuZCBDT01NRU5UIHBv
c2l0aW9ucy4NCg0KDQpUaGUgZG9jdW1lbnQsIGFsb25nIHdpdGggb3RoZXIgYmFsbG90IHBvc2l0
aW9ucywgY2FuIGJlIGZvdW5kIGhlcmU6DQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2Rv
Yy9kcmFmdC1pZXRmLWNsdWUtc2lnbmFsaW5nLw0KDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KQ09NTUVO
VDoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCg0KUmljaCB2ZXJzaW9uIG9mIHRoaXMgcmV2aWV3IGF0Og0KaHR0
cHM6Ly9tb3pwaGFiLWlldGYuZGV2c3ZjZGV2Lm1vemF3cy5uZXQvRDQwOTkNCg0KDQoNCkNPTU1F
TlRTDQpTIDEyLg0KPiAgICAgIHZpYSBEVExTLVNSVFAgW1JGQzU3NjNdIG9uIENMVUUtY29udHJv
bGxlZCBSVFAgIm09IiBsaW5lcy4gIEFsbCBDTFVFLQ0KPiAgICAgIGNvbnRyb2xsZWQgUlRQICJt
IiBsaW5lcyBtdXN0IGJlIHNlY3VyZWQgYW5kIGltcGxlbWVudGVkIHVzaW5nDQo+ICAgICAgbWVj
aGFuaXNtcyBzdWNoIGFzIFNSVFAgW1JGQzM3MTFdLiAgQ0xVRSBpbXBsZW1lbnRhdGlvbnMgTUFZ
IGNob29zZQ0KPiAgICAgIG5vdCB0byByZXF1aXJlIHRoZSB1c2Ugb2YgU1JUUCB0byBzZWN1cmUg
bGVnYWN5IChub24tQ0xVRS1jb250cm9sbGVkKQ0KPiAgICAgIG1lZGlhIGZvciBiYWNrd2FyZHMg
Y29tcGF0aWJpbGl0eSB3aXRoIG9sZGVyIFNJUCBjbGllbnRzIHRoYXQgYXJlDQo+ICAgICAgaW5j
YXBhYmxlIG9mIHN1cHBvcnRpbmcgaXQuDQoNCkl0IHNlZW1zIGxpa2UgeW91IG5lZWQgbW9yZSB0
aGFuIHN1cHBvcnQsIHlvdSBhbHNvIG5lZWQgdG8gcmVxdWlyZSB0aGUgdXNlIG9mIERUTFMtU1JU
UCwgbm8/DQoNCg0K


From nobody Thu Nov 22 07:28:00 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C84F412DF72 for <clue@ietfa.amsl.com>; Thu, 22 Nov 2018 07:27:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.357
X-Spam-Level: 
X-Spam-Status: No, score=-3.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wKjtoD4Vm3C for <clue@ietfa.amsl.com>; Thu, 22 Nov 2018 07:27:52 -0800 (PST)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 784A712D84C for <clue@ietf.org>; Thu, 22 Nov 2018 07:27:48 -0800 (PST)
Received: by mail-lj1-x234.google.com with SMTP id s5-v6so8286121ljd.12 for <clue@ietf.org>; Thu, 22 Nov 2018 07:27:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kGxrA9CKyXeSP8DzDuBRz7zsQgH3XpSB3FNlBwDKYVY=; b=0y6yb0AxPRqfx1kuzOkA9QbFy+0lgaXeAGTj5uZtvDODmSi+2t5e9WeY2g/vmPYrk+ IcFSX4ZVtqQSTvFWqlJODM9anFmi/4boR0ihKwYc6pX3UswyIR/r+6SoplmV+aWUMbGj AhtAeMIZ1y/YO+P5umsmb6w9ghwLtlLn0GyldpQjrtH4k6sDN1n7Dhjcm+gDVnoCryxL FnuhamPkCoWLM15zsncSFPpL6KOzMxQvQN9AaA4YsPWLOSlLBmkLOBpegnGQAGoujDZA EZmfXi2GC0a4ki0gvlEHLPD7iViozxXOTPbr+E+ZQc8u9N/UAT3Qokh0sGvw/ythPA6X lfWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kGxrA9CKyXeSP8DzDuBRz7zsQgH3XpSB3FNlBwDKYVY=; b=dKWfvqRz5CBPLayXrfoGiONIpww2Vlz34FcPP5DQpjhKPlPtRmVMmLelNte/QIi/B1 rgA4AboWTLXiUryao0Q+2s9MnzCBgn/gVz7xrQ0HYI/E7b51b6HMRGqU9ZN7phEh9xfc v/YQiv49rcoBjImtWj7CSxxFpRLzIQkRbhcZNhOLHpV7snGbE5zcmO87AvxexhwXkc+a chMh3x1kUP04zorSmpXA+Ij8OhaAWeeaZ8OAzs/D5qY8Mb1zx3Vctd8tuw9aidC9H4Ma Jn0Nw3PY5kwSZT7tiZLIeQXLMD2kVL4pP/iJRANIeflWHx5es2yUmchxGaVTqvQCn8RY twCw==
X-Gm-Message-State: AGRZ1gK3ZqmTh6Qkhr75gzD6nn+CDBQYA6yuNV3JhXWJ/7iuQEYKxAvx sblVCV2bX239ceQJ87U048UjCVPqHnpyIl+C71sg6g==
X-Google-Smtp-Source: AFSGD/VgDGQXcqt0k4WrkJTvzUIjapet8PLYJpjtiDuMAVdz2Dp9YNn2vGng5spYZ0mKpCMHA0Ay3uYOnqRtGjiYPiE=
X-Received: by 2002:a2e:1551:: with SMTP id 17-v6mr7251855ljv.68.1542900466622;  Thu, 22 Nov 2018 07:27:46 -0800 (PST)
MIME-Version: 1.0
References: <154268892146.26648.17870778354406192041.idtracker@ietfa.amsl.com> <6E58094ECC8D8344914996DAD28F1CCD18C762DF@DGGEMM506-MBX.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD18C762DF@DGGEMM506-MBX.china.huawei.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 22 Nov 2018 07:27:09 -0800
Message-ID: <CABcZeBMcQxZuRUFx=tz==C5eCc8zNBrxkKaZfBa+gYnyaV3FOQ@mail.gmail.com>
To: Roni Even <roni.even@huawei.com>
Cc: IESG <iesg@ietf.org>, Daniel Burnett <danielcburnett@gmail.com>, clue@ietf.org, roni.even@mail01.huawei.com, clue-chairs@ietf.org,  draft-ietf-clue-signaling@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003cbcca057b428217"
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/nrL_Lu-oVJRvuLSBplzLSn5WtWM>
Subject: Re: [clue] Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Nov 2018 15:27:54 -0000

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

The problem is that this is in the context of amplification attacks

   Beyond the need to secure the constituent protocols, the use of CLUE
   does impose additional security concerns.  One area of increased risk
   involves the potential for a malicious party to subvert a CLUE-
   capable device to attack a third party by driving large volumes of
   media (particularly video) traffic at them by establishing a
   connection to the CLUE-capable device and directing the media to the
   victim.  While this is a risk for all media devices, a CLUE-capable
   device may allow the attacker to configure multiple media streams to
   be sent, significantly increasing the volume of traffic directed at
   the victim.

   This attack can be prevented by ensuring that the media recipient
   intends to receive the media packets.  As such all CLUE-capable
   devices MUST support key negotiation and receiver intent assurance
   via DTLS-SRTP [RFC5763] on CLUE-controlled RTP "m=" lines.

And so if you don't require DTLS-SRTP or ICE than in fact there is no
amplification
attack defense.

-Ekr


On Thu, Nov 22, 2018 at 3:24 AM Roni Even (A) <roni.even@huawei.com> wrote:

> Hi,
> RTP payloads do not require usage of SRTP see RFC7201 and RFC7202
> Roni Even
>
> -----Original Message-----
> From: Eric Rescorla [mailto:ekr@rtfm.com]
> Sent: Tuesday, November 20, 2018 6:42 AM
> To: The IESG
> Cc: Daniel C. Burnett; clue@ietf.org; roni.even@mail01.huawei.com; Roni
> Even; clue-chairs@ietf.org; draft-ietf-clue-signaling@ietf.org
> Subject: Eric Rescorla's No Objection on draft-ietf-clue-signaling-14:
> (with COMMENT)
>
> Eric Rescorla has entered the following ballot position for
> draft-ietf-clue-signaling-14: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-clue-signaling/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Rich version of this review at:
> https://mozphab-ietf.devsvcdev.mozaws.net/D4099
>
>
>
> COMMENTS
> S 12.
> >      via DTLS-SRTP [RFC5763] on CLUE-controlled RTP "m=" lines.  All
> CLUE-
> >      controlled RTP "m" lines must be secured and implemented using
> >      mechanisms such as SRTP [RFC3711].  CLUE implementations MAY choose
> >      not to require the use of SRTP to secure legacy
> (non-CLUE-controlled)
> >      media for backwards compatibility with older SIP clients that are
> >      incapable of supporting it.
>
> It seems like you need more than support, you also need to require the use
> of DTLS-SRTP, no?
>
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div>The problem is that this is in the c=
ontext of amplification attacks</div><div><br></div><div>=C2=A0=C2=A0 Beyon=
d the need to secure the constituent protocols, the use of CLUE<br>=C2=A0=
=C2=A0 does impose additional security concerns.=C2=A0 One area of increase=
d risk<br>=C2=A0=C2=A0 involves the potential for a malicious party to subv=
ert a CLUE-<br>=C2=A0=C2=A0 capable device to attack a third party by drivi=
ng large volumes of<br>=C2=A0=C2=A0 media (particularly video) traffic at t=
hem by establishing a<br>=C2=A0=C2=A0 connection to the CLUE-capable device=
 and directing the media to the<br>=C2=A0=C2=A0 victim.=C2=A0 While this is=
 a risk for all media devices, a CLUE-capable<br>=C2=A0=C2=A0 device may al=
low the attacker to configure multiple media streams to<br>=C2=A0=C2=A0 be =
sent, significantly increasing the volume of traffic directed at<br>=C2=A0=
=C2=A0 the victim.<br><br>=C2=A0=C2=A0 This attack can be prevented by ensu=
ring that the media recipient<br>=C2=A0=C2=A0 intends to receive the media =
packets.=C2=A0 As such all CLUE-capable<br>=C2=A0=C2=A0 devices MUST suppor=
t key negotiation and receiver intent assurance<br>=C2=A0=C2=A0 via DTLS-SR=
TP [RFC5763] on CLUE-controlled RTP &quot;m=3D&quot; lines.</div><div><br><=
/div><div>And so if you don&#39;t require DTLS-SRTP or ICE than in fact the=
re is no amplification</div><div>attack defense.</div><div><br></div><div>-=
Ekr</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r">On Thu, Nov 22, 2018 at 3:24 AM Roni Even (A) &lt;<a href=3D"mailto:roni=
.even@huawei.com">roni.even@huawei.com</a>&gt; wrote:<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">Hi,<br>
RTP payloads do not require usage of SRTP see RFC7201 and RFC7202<br>
Roni Even<br>
<br>
-----Original Message-----<br>
From: Eric Rescorla [mailto:<a href=3D"mailto:ekr@rtfm.com" target=3D"_blan=
k">ekr@rtfm.com</a>] <br>
Sent: Tuesday, November 20, 2018 6:42 AM<br>
To: The IESG<br>
Cc: Daniel C. Burnett; <a href=3D"mailto:clue@ietf.org" target=3D"_blank">c=
lue@ietf.org</a>; <a href=3D"mailto:roni.even@mail01.huawei.com" target=3D"=
_blank">roni.even@mail01.huawei.com</a>; Roni Even; <a href=3D"mailto:clue-=
chairs@ietf.org" target=3D"_blank">clue-chairs@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-clue-signaling@ietf.org" target=3D"_blank">draft-ietf-clue-s=
ignaling@ietf.org</a><br>
Subject: Eric Rescorla&#39;s No Objection on draft-ietf-clue-signaling-14: =
(with COMMENT)<br>
<br>
Eric Rescorla has entered the following ballot position for<br>
draft-ietf-clue-signaling-14: No Objection<br>
<br>
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 introduc=
tory paragraph, however.)<br>
<br>
<br>
Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss-crit=
eria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/iesg/s=
tatement/discuss-criteria.html</a><br>
for more information about IESG DISCUSS and COMMENT positions.<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-clue-signaling/" rel=
=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ie=
tf-clue-signaling/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
Rich version of this review at:<br>
<a href=3D"https://mozphab-ietf.devsvcdev.mozaws.net/D4099" rel=3D"noreferr=
er" target=3D"_blank">https://mozphab-ietf.devsvcdev.mozaws.net/D4099</a><b=
r>
<br>
<br>
<br>
COMMENTS<br>
S 12.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 via DTLS-SRTP [RFC5763] on CLUE-controlled RTP &qu=
ot;m=3D&quot; lines.=C2=A0 All CLUE-<br>
&gt;=C2=A0 =C2=A0 =C2=A0 controlled RTP &quot;m&quot; lines must be secured=
 and implemented using<br>
&gt;=C2=A0 =C2=A0 =C2=A0 mechanisms such as SRTP [RFC3711].=C2=A0 CLUE impl=
ementations MAY choose<br>
&gt;=C2=A0 =C2=A0 =C2=A0 not to require the use of SRTP to secure legacy (n=
on-CLUE-controlled)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 media for backwards compatibility with older SIP c=
lients that are<br>
&gt;=C2=A0 =C2=A0 =C2=A0 incapable of supporting it.<br>
<br>
It seems like you need more than support, you also need to require the use =
of DTLS-SRTP, no?<br>
<br>
<br>
</blockquote></div></div>

--0000000000003cbcca057b428217--


From nobody Sat Nov 24 21:41:20 2018
Return-Path: <roni.even@huawei.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CEE8128D0C; Sat, 24 Nov 2018 21:41:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ke01V4cHDZaV; Sat, 24 Nov 2018 21:41:08 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 EAD29123FFD; Sat, 24 Nov 2018 21:41:07 -0800 (PST)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 3FDF8195D279A; Sun, 25 Nov 2018 05:41:04 +0000 (GMT)
Received: from lhreml707-chm.china.huawei.com (10.201.108.56) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 25 Nov 2018 05:41:05 +0000
Received: from lhreml707-chm.china.huawei.com (10.201.108.56) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Sun, 25 Nov 2018 05:41:04 +0000
Received: from DGGEMM422-HUB.china.huawei.com (10.1.198.39) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Sun, 25 Nov 2018 05:41:03 +0000
Received: from DGGEMM506-MBS.china.huawei.com ([169.254.4.74]) by dggemm422-hub.china.huawei.com ([10.1.198.39]) with mapi id 14.03.0415.000; Sun, 25 Nov 2018 13:41:00 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: IESG <iesg@ietf.org>, Daniel Burnett <danielcburnett@gmail.com>, "clue@ietf.org" <clue@ietf.org>, "roni.even@mail01.huawei.com" <roni.even@mail01.huawei.com>, "clue-chairs@ietf.org" <clue-chairs@ietf.org>,  "draft-ietf-clue-signaling@ietf.org" <draft-ietf-clue-signaling@ietf.org>
Thread-Topic: Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
Thread-Index: AQHUgIto2vun7lYtT0WxvGbN4Em2qaVbqbyg//++u4CABJiZEA==
Date: Sun, 25 Nov 2018 05:40:59 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD18C7B5DE@DGGEMM506-MBS.china.huawei.com>
References: <154268892146.26648.17870778354406192041.idtracker@ietfa.amsl.com> <6E58094ECC8D8344914996DAD28F1CCD18C762DF@DGGEMM506-MBX.china.huawei.com> <CABcZeBMcQxZuRUFx=tz==C5eCc8zNBrxkKaZfBa+gYnyaV3FOQ@mail.gmail.com>
In-Reply-To: <CABcZeBMcQxZuRUFx=tz==C5eCc8zNBrxkKaZfBa+gYnyaV3FOQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.166]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD18C7B5DEDGGEMM506MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/PyKUSJtpNR8UVAG6P9y4KMb4fHg>
Subject: Re: [clue] Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Nov 2018 05:41:11 -0000

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

SGksDQpUaGUgcG9pbnQgdGhhdCBpcyBtYWRlIHRoYXQgaW4gZ2VuZXJhbCBDTFVFIGlzIHNpbWls
YXIgdG8gbm8gQ0xVRSBSVFAgbWVkaWEgY2FsbHMuIFRoZSBkaWZmZXJlbmNlIGlzIHRoYXQgc2lu
Y2UgdGhlIEVQIG1heSBvcGVuIG1vcmUgdGhhbiBvbmUgUlRQIHZpZGVvIGNoYW5uZWwgdGhlcmUg
aXMgYSBncmVhdGVyIHJpc2sgb2Ygc2VuZGluZyBtb3JlIG1lZGlhIHRvIHRoZSB2aWN0aW0uIFJG
QzcyMDEgZGlzY3VzcyB0aGUgb3B0aW9ucyB0byBzZWN1cmUgdGhlIG1lZGlhIGFuZCB0aGlzIGhv
bGRzIGZvciB0aGlzIGNhc2UgdG9vLg0KDQpSb25pDQoNCkZyb206IEVyaWMgUmVzY29ybGEgW21h
aWx0bzpla3JAcnRmbS5jb21dDQpTZW50OiBUaHVyc2RheSwgTm92ZW1iZXIgMjIsIDIwMTggNToy
NyBQTQ0KVG86IFJvbmkgRXZlbiAoQSkNCkNjOiBJRVNHOyBEYW5pZWwgQnVybmV0dDsgY2x1ZUBp
ZXRmLm9yZzsgcm9uaS5ldmVuQG1haWwwMS5odWF3ZWkuY29tOyBjbHVlLWNoYWlyc0BpZXRmLm9y
ZzsgZHJhZnQtaWV0Zi1jbHVlLXNpZ25hbGluZ0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IEVyaWMg
UmVzY29ybGEncyBObyBPYmplY3Rpb24gb24gZHJhZnQtaWV0Zi1jbHVlLXNpZ25hbGluZy0xNDog
KHdpdGggQ09NTUVOVCkNCg0KVGhlIHByb2JsZW0gaXMgdGhhdCB0aGlzIGlzIGluIHRoZSBjb250
ZXh0IG9mIGFtcGxpZmljYXRpb24gYXR0YWNrcw0KDQogICBCZXlvbmQgdGhlIG5lZWQgdG8gc2Vj
dXJlIHRoZSBjb25zdGl0dWVudCBwcm90b2NvbHMsIHRoZSB1c2Ugb2YgQ0xVRQ0KICAgZG9lcyBp
bXBvc2UgYWRkaXRpb25hbCBzZWN1cml0eSBjb25jZXJucy4gIE9uZSBhcmVhIG9mIGluY3JlYXNl
ZCByaXNrDQogICBpbnZvbHZlcyB0aGUgcG90ZW50aWFsIGZvciBhIG1hbGljaW91cyBwYXJ0eSB0
byBzdWJ2ZXJ0IGEgQ0xVRS0NCiAgIGNhcGFibGUgZGV2aWNlIHRvIGF0dGFjayBhIHRoaXJkIHBh
cnR5IGJ5IGRyaXZpbmcgbGFyZ2Ugdm9sdW1lcyBvZg0KICAgbWVkaWEgKHBhcnRpY3VsYXJseSB2
aWRlbykgdHJhZmZpYyBhdCB0aGVtIGJ5IGVzdGFibGlzaGluZyBhDQogICBjb25uZWN0aW9uIHRv
IHRoZSBDTFVFLWNhcGFibGUgZGV2aWNlIGFuZCBkaXJlY3RpbmcgdGhlIG1lZGlhIHRvIHRoZQ0K
ICAgdmljdGltLiAgV2hpbGUgdGhpcyBpcyBhIHJpc2sgZm9yIGFsbCBtZWRpYSBkZXZpY2VzLCBh
IENMVUUtY2FwYWJsZQ0KICAgZGV2aWNlIG1heSBhbGxvdyB0aGUgYXR0YWNrZXIgdG8gY29uZmln
dXJlIG11bHRpcGxlIG1lZGlhIHN0cmVhbXMgdG8NCiAgIGJlIHNlbnQsIHNpZ25pZmljYW50bHkg
aW5jcmVhc2luZyB0aGUgdm9sdW1lIG9mIHRyYWZmaWMgZGlyZWN0ZWQgYXQNCiAgIHRoZSB2aWN0
aW0uDQoNCiAgIFRoaXMgYXR0YWNrIGNhbiBiZSBwcmV2ZW50ZWQgYnkgZW5zdXJpbmcgdGhhdCB0
aGUgbWVkaWEgcmVjaXBpZW50DQogICBpbnRlbmRzIHRvIHJlY2VpdmUgdGhlIG1lZGlhIHBhY2tl
dHMuICBBcyBzdWNoIGFsbCBDTFVFLWNhcGFibGUNCiAgIGRldmljZXMgTVVTVCBzdXBwb3J0IGtl
eSBuZWdvdGlhdGlvbiBhbmQgcmVjZWl2ZXIgaW50ZW50IGFzc3VyYW5jZQ0KICAgdmlhIERUTFMt
U1JUUCBbUkZDNTc2M10gb24gQ0xVRS1jb250cm9sbGVkIFJUUCAibT0iIGxpbmVzLg0KDQpBbmQg
c28gaWYgeW91IGRvbid0IHJlcXVpcmUgRFRMUy1TUlRQIG9yIElDRSB0aGFuIGluIGZhY3QgdGhl
cmUgaXMgbm8gYW1wbGlmaWNhdGlvbg0KYXR0YWNrIGRlZmVuc2UuDQoNCi1Fa3INCg0KDQpPbiBU
aHUsIE5vdiAyMiwgMjAxOCBhdCAzOjI0IEFNIFJvbmkgRXZlbiAoQSkgPHJvbmkuZXZlbkBodWF3
ZWkuY29tPG1haWx0bzpyb25pLmV2ZW5AaHVhd2VpLmNvbT4+IHdyb3RlOg0KSGksDQpSVFAgcGF5
bG9hZHMgZG8gbm90IHJlcXVpcmUgdXNhZ2Ugb2YgU1JUUCBzZWUgUkZDNzIwMSBhbmQgUkZDNzIw
Mg0KUm9uaSBFdmVuDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBFcmljIFJl
c2NvcmxhIFttYWlsdG86ZWtyQHJ0Zm0uY29tPG1haWx0bzpla3JAcnRmbS5jb20+XQ0KU2VudDog
VHVlc2RheSwgTm92ZW1iZXIgMjAsIDIwMTggNjo0MiBBTQ0KVG86IFRoZSBJRVNHDQpDYzogRGFu
aWVsIEMuIEJ1cm5ldHQ7IGNsdWVAaWV0Zi5vcmc8bWFpbHRvOmNsdWVAaWV0Zi5vcmc+OyByb25p
LmV2ZW5AbWFpbDAxLmh1YXdlaS5jb208bWFpbHRvOnJvbmkuZXZlbkBtYWlsMDEuaHVhd2VpLmNv
bT47IFJvbmkgRXZlbjsgY2x1ZS1jaGFpcnNAaWV0Zi5vcmc8bWFpbHRvOmNsdWUtY2hhaXJzQGll
dGYub3JnPjsgZHJhZnQtaWV0Zi1jbHVlLXNpZ25hbGluZ0BpZXRmLm9yZzxtYWlsdG86ZHJhZnQt
aWV0Zi1jbHVlLXNpZ25hbGluZ0BpZXRmLm9yZz4NClN1YmplY3Q6IEVyaWMgUmVzY29ybGEncyBO
byBPYmplY3Rpb24gb24gZHJhZnQtaWV0Zi1jbHVlLXNpZ25hbGluZy0xNDogKHdpdGggQ09NTUVO
VCkNCg0KRXJpYyBSZXNjb3JsYSBoYXMgZW50ZXJlZCB0aGUgZm9sbG93aW5nIGJhbGxvdCBwb3Np
dGlvbiBmb3INCmRyYWZ0LWlldGYtY2x1ZS1zaWduYWxpbmctMTQ6IE5vIE9iamVjdGlvbg0KDQpX
aGVuIHJlc3BvbmRpbmcsIHBsZWFzZSBrZWVwIHRoZSBzdWJqZWN0IGxpbmUgaW50YWN0IGFuZCBy
ZXBseSB0byBhbGwgZW1haWwgYWRkcmVzc2VzIGluY2x1ZGVkIGluIHRoZSBUbyBhbmQgQ0MgbGlu
ZXMuIChGZWVsIGZyZWUgdG8gY3V0IHRoaXMgaW50cm9kdWN0b3J5IHBhcmFncmFwaCwgaG93ZXZl
ci4pDQoNCg0KUGxlYXNlIHJlZmVyIHRvIGh0dHBzOi8vd3d3LmlldGYub3JnL2llc2cvc3RhdGVt
ZW50L2Rpc2N1c3MtY3JpdGVyaWEuaHRtbA0KZm9yIG1vcmUgaW5mb3JtYXRpb24gYWJvdXQgSUVT
RyBESVNDVVNTIGFuZCBDT01NRU5UIHBvc2l0aW9ucy4NCg0KDQpUaGUgZG9jdW1lbnQsIGFsb25n
IHdpdGggb3RoZXIgYmFsbG90IHBvc2l0aW9ucywgY2FuIGJlIGZvdW5kIGhlcmU6DQpodHRwczov
L2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLWNsdWUtc2lnbmFsaW5nLw0KDQoN
Cg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KQ09NTUVOVDoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KUmljaCB2ZXJzaW9u
IG9mIHRoaXMgcmV2aWV3IGF0Og0KaHR0cHM6Ly9tb3pwaGFiLWlldGYuZGV2c3ZjZGV2Lm1vemF3
cy5uZXQvRDQwOTkNCg0KDQoNCkNPTU1FTlRTDQpTIDEyLg0KPiAgICAgIHZpYSBEVExTLVNSVFAg
W1JGQzU3NjNdIG9uIENMVUUtY29udHJvbGxlZCBSVFAgIm09IiBsaW5lcy4gIEFsbCBDTFVFLQ0K
PiAgICAgIGNvbnRyb2xsZWQgUlRQICJtIiBsaW5lcyBtdXN0IGJlIHNlY3VyZWQgYW5kIGltcGxl
bWVudGVkIHVzaW5nDQo+ICAgICAgbWVjaGFuaXNtcyBzdWNoIGFzIFNSVFAgW1JGQzM3MTFdLiAg
Q0xVRSBpbXBsZW1lbnRhdGlvbnMgTUFZIGNob29zZQ0KPiAgICAgIG5vdCB0byByZXF1aXJlIHRo
ZSB1c2Ugb2YgU1JUUCB0byBzZWN1cmUgbGVnYWN5IChub24tQ0xVRS1jb250cm9sbGVkKQ0KPiAg
ICAgIG1lZGlhIGZvciBiYWNrd2FyZHMgY29tcGF0aWJpbGl0eSB3aXRoIG9sZGVyIFNJUCBjbGll
bnRzIHRoYXQgYXJlDQo+ICAgICAgaW5jYXBhYmxlIG9mIHN1cHBvcnRpbmcgaXQuDQoNCkl0IHNl
ZW1zIGxpa2UgeW91IG5lZWQgbW9yZSB0aGFuIHN1cHBvcnQsIHlvdSBhbHNvIG5lZWQgdG8gcmVx
dWlyZSB0aGUgdXNlIG9mIERUTFMtU1JUUCwgbm8/DQoNCg==

--_000_6E58094ECC8D8344914996DAD28F1CCD18C7B5DEDGGEMM506MBSchi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0
YXRlLCBkaXYuTXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxl
LWxpbms6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206
LjAwMDFwdDsNCglmb250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMt
c2VyaWYiO30NCnNwYW4uQmFsbG9vblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJCYWxsb29u
IFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJC
YWxsb29uIFRleHQiOw0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpzcGFu
LkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERl
ZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4w
aW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjEN
Cgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHht
bD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3ht
bD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6
ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBl
bGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxp
bms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj5IaSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+VGhlIHBvaW50IHRoYXQgaXMg
bWFkZSB0aGF0IGluIGdlbmVyYWwgQ0xVRSBpcyBzaW1pbGFyIHRvIG5vIENMVUUgUlRQIG1lZGlh
IGNhbGxzLiBUaGUgZGlmZmVyZW5jZSBpcyB0aGF0IHNpbmNlIHRoZSBFUCBtYXkgb3BlbiBtb3Jl
IHRoYW4gb25lIFJUUCB2aWRlbyBjaGFubmVsDQogdGhlcmUgaXMgYSBncmVhdGVyIHJpc2sgb2Yg
c2VuZGluZyBtb3JlIG1lZGlhIHRvIHRoZSB2aWN0aW0uIFJGQzcyMDEgZGlzY3VzcyB0aGUgb3B0
aW9ucyB0byBzZWN1cmUgdGhlIG1lZGlhIGFuZCB0aGlzIGhvbGRzIGZvciB0aGlzIGNhc2UgdG9v
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+Um9uaTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij4gRXJpYyBSZXNjb3JsYSBbbWFpbHRvOmVrckBydGZtLmNvbV0NCjxicj4NCjxiPlNlbnQ6PC9i
PiBUaHVyc2RheSwgTm92ZW1iZXIgMjIsIDIwMTggNToyNyBQTTxicj4NCjxiPlRvOjwvYj4gUm9u
aSBFdmVuIChBKTxicj4NCjxiPkNjOjwvYj4gSUVTRzsgRGFuaWVsIEJ1cm5ldHQ7IGNsdWVAaWV0
Zi5vcmc7IHJvbmkuZXZlbkBtYWlsMDEuaHVhd2VpLmNvbTsgY2x1ZS1jaGFpcnNAaWV0Zi5vcmc7
IGRyYWZ0LWlldGYtY2x1ZS1zaWduYWxpbmdAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4g
UmU6IEVyaWMgUmVzY29ybGEncyBObyBPYmplY3Rpb24gb24gZHJhZnQtaWV0Zi1jbHVlLXNpZ25h
bGluZy0xNDogKHdpdGggQ09NTUVOVCk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPlRoZSBwcm9ibGVtIGlzIHRoYXQgdGhpcyBpcyBpbiB0aGUgY29u
dGV4dCBvZiBhbXBsaWZpY2F0aW9uIGF0dGFja3M8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7Jm5ic3A7IEJleW9uZCB0aGUgbmVlZCB0
byBzZWN1cmUgdGhlIGNvbnN0aXR1ZW50IHByb3RvY29scywgdGhlIHVzZSBvZiBDTFVFPGJyPg0K
Jm5ic3A7Jm5ic3A7IGRvZXMgaW1wb3NlIGFkZGl0aW9uYWwgc2VjdXJpdHkgY29uY2VybnMuJm5i
c3A7IE9uZSBhcmVhIG9mIGluY3JlYXNlZCByaXNrPGJyPg0KJm5ic3A7Jm5ic3A7IGludm9sdmVz
IHRoZSBwb3RlbnRpYWwgZm9yIGEgbWFsaWNpb3VzIHBhcnR5IHRvIHN1YnZlcnQgYSBDTFVFLTxi
cj4NCiZuYnNwOyZuYnNwOyBjYXBhYmxlIGRldmljZSB0byBhdHRhY2sgYSB0aGlyZCBwYXJ0eSBi
eSBkcml2aW5nIGxhcmdlIHZvbHVtZXMgb2Y8YnI+DQombmJzcDsmbmJzcDsgbWVkaWEgKHBhcnRp
Y3VsYXJseSB2aWRlbykgdHJhZmZpYyBhdCB0aGVtIGJ5IGVzdGFibGlzaGluZyBhPGJyPg0KJm5i
c3A7Jm5ic3A7IGNvbm5lY3Rpb24gdG8gdGhlIENMVUUtY2FwYWJsZSBkZXZpY2UgYW5kIGRpcmVj
dGluZyB0aGUgbWVkaWEgdG8gdGhlPGJyPg0KJm5ic3A7Jm5ic3A7IHZpY3RpbS4mbmJzcDsgV2hp
bGUgdGhpcyBpcyBhIHJpc2sgZm9yIGFsbCBtZWRpYSBkZXZpY2VzLCBhIENMVUUtY2FwYWJsZTxi
cj4NCiZuYnNwOyZuYnNwOyBkZXZpY2UgbWF5IGFsbG93IHRoZSBhdHRhY2tlciB0byBjb25maWd1
cmUgbXVsdGlwbGUgbWVkaWEgc3RyZWFtcyB0bzxicj4NCiZuYnNwOyZuYnNwOyBiZSBzZW50LCBz
aWduaWZpY2FudGx5IGluY3JlYXNpbmcgdGhlIHZvbHVtZSBvZiB0cmFmZmljIGRpcmVjdGVkIGF0
PGJyPg0KJm5ic3A7Jm5ic3A7IHRoZSB2aWN0aW0uPGJyPg0KPGJyPg0KJm5ic3A7Jm5ic3A7IFRo
aXMgYXR0YWNrIGNhbiBiZSBwcmV2ZW50ZWQgYnkgZW5zdXJpbmcgdGhhdCB0aGUgbWVkaWEgcmVj
aXBpZW50PGJyPg0KJm5ic3A7Jm5ic3A7IGludGVuZHMgdG8gcmVjZWl2ZSB0aGUgbWVkaWEgcGFj
a2V0cy4mbmJzcDsgQXMgc3VjaCBhbGwgQ0xVRS1jYXBhYmxlPGJyPg0KJm5ic3A7Jm5ic3A7IGRl
dmljZXMgTVVTVCBzdXBwb3J0IGtleSBuZWdvdGlhdGlvbiBhbmQgcmVjZWl2ZXIgaW50ZW50IGFz
c3VyYW5jZTxicj4NCiZuYnNwOyZuYnNwOyB2aWEgRFRMUy1TUlRQIFtSRkM1NzYzXSBvbiBDTFVF
LWNvbnRyb2xsZWQgUlRQICZxdW90O209JnF1b3Q7IGxpbmVzLjxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BbmQgc28gaWYgeW91IGRvbid0IHJl
cXVpcmUgRFRMUy1TUlRQIG9yIElDRSB0aGFuIGluIGZhY3QgdGhlcmUgaXMgbm8gYW1wbGlmaWNh
dGlvbjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
YXR0YWNrIGRlZmVuc2UuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPi1Fa3I8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5PbiBUaHUsIE5vdiAyMiwgMjAxOCBhdCAzOjI0IEFNIFJvbmkgRXZl
biAoQSkgJmx0OzxhIGhyZWY9Im1haWx0bzpyb25pLmV2ZW5AaHVhd2VpLmNvbSI+cm9uaS5ldmVu
QGh1YXdlaS5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2Nr
cXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7
cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6
MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+
SGksPGJyPg0KUlRQIHBheWxvYWRzIGRvIG5vdCByZXF1aXJlIHVzYWdlIG9mIFNSVFAgc2VlIFJG
QzcyMDEgYW5kIFJGQzcyMDI8YnI+DQpSb25pIEV2ZW48YnI+DQo8YnI+DQotLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLTxicj4NCkZyb206IEVyaWMgUmVzY29ybGEgW21haWx0bzo8YSBocmVmPSJt
YWlsdG86ZWtyQHJ0Zm0uY29tIiB0YXJnZXQ9Il9ibGFuayI+ZWtyQHJ0Zm0uY29tPC9hPl0NCjxi
cj4NClNlbnQ6IFR1ZXNkYXksIE5vdmVtYmVyIDIwLCAyMDE4IDY6NDIgQU08YnI+DQpUbzogVGhl
IElFU0c8YnI+DQpDYzogRGFuaWVsIEMuIEJ1cm5ldHQ7IDxhIGhyZWY9Im1haWx0bzpjbHVlQGll
dGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+Y2x1ZUBpZXRmLm9yZzwvYT47DQo8YSBocmVmPSJtYWls
dG86cm9uaS5ldmVuQG1haWwwMS5odWF3ZWkuY29tIiB0YXJnZXQ9Il9ibGFuayI+cm9uaS5ldmVu
QG1haWwwMS5odWF3ZWkuY29tPC9hPjsgUm9uaSBFdmVuOw0KPGEgaHJlZj0ibWFpbHRvOmNsdWUt
Y2hhaXJzQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+Y2x1ZS1jaGFpcnNAaWV0Zi5vcmc8L2E+
OyA8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi1jbHVlLXNpZ25hbGluZ0BpZXRmLm9yZyIgdGFy
Z2V0PSJfYmxhbmsiPg0KZHJhZnQtaWV0Zi1jbHVlLXNpZ25hbGluZ0BpZXRmLm9yZzwvYT48YnI+
DQpTdWJqZWN0OiBFcmljIFJlc2NvcmxhJ3MgTm8gT2JqZWN0aW9uIG9uIGRyYWZ0LWlldGYtY2x1
ZS1zaWduYWxpbmctMTQ6ICh3aXRoIENPTU1FTlQpPGJyPg0KPGJyPg0KRXJpYyBSZXNjb3JsYSBo
YXMgZW50ZXJlZCB0aGUgZm9sbG93aW5nIGJhbGxvdCBwb3NpdGlvbiBmb3I8YnI+DQpkcmFmdC1p
ZXRmLWNsdWUtc2lnbmFsaW5nLTE0OiBObyBPYmplY3Rpb248YnI+DQo8YnI+DQpXaGVuIHJlc3Bv
bmRpbmcsIHBsZWFzZSBrZWVwIHRoZSBzdWJqZWN0IGxpbmUgaW50YWN0IGFuZCByZXBseSB0byBh
bGwgZW1haWwgYWRkcmVzc2VzIGluY2x1ZGVkIGluIHRoZSBUbyBhbmQgQ0MgbGluZXMuIChGZWVs
IGZyZWUgdG8gY3V0IHRoaXMgaW50cm9kdWN0b3J5IHBhcmFncmFwaCwgaG93ZXZlci4pPGJyPg0K
PGJyPg0KPGJyPg0KUGxlYXNlIHJlZmVyIHRvIDxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3Jn
L2llc2cvc3RhdGVtZW50L2Rpc2N1c3MtY3JpdGVyaWEuaHRtbCIgdGFyZ2V0PSJfYmxhbmsiPg0K
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvaWVzZy9zdGF0ZW1lbnQvZGlzY3Vzcy1jcml0ZXJpYS5odG1s
PC9hPjxicj4NCmZvciBtb3JlIGluZm9ybWF0aW9uIGFib3V0IElFU0cgRElTQ1VTUyBhbmQgQ09N
TUVOVCBwb3NpdGlvbnMuPGJyPg0KPGJyPg0KPGJyPg0KVGhlIGRvY3VtZW50LCBhbG9uZyB3aXRo
IG90aGVyIGJhbGxvdCBwb3NpdGlvbnMsIGNhbiBiZSBmb3VuZCBoZXJlOjxicj4NCjxhIGhyZWY9
Imh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtY2x1ZS1zaWduYWxp
bmcvIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh
ZnQtaWV0Zi1jbHVlLXNpZ25hbGluZy88L2E+PGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLTxicj4NCkNPTU1FTlQ6PGJyPg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCjxicj4NClJpY2gg
dmVyc2lvbiBvZiB0aGlzIHJldmlldyBhdDo8YnI+DQo8YSBocmVmPSJodHRwczovL21venBoYWIt
aWV0Zi5kZXZzdmNkZXYubW96YXdzLm5ldC9ENDA5OSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8v
bW96cGhhYi1pZXRmLmRldnN2Y2Rldi5tb3phd3MubmV0L0Q0MDk5PC9hPjxicj4NCjxicj4NCjxi
cj4NCjxicj4NCkNPTU1FTlRTPGJyPg0KUyAxMi48YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJz
cDsgdmlhIERUTFMtU1JUUCBbUkZDNTc2M10gb24gQ0xVRS1jb250cm9sbGVkIFJUUCAmcXVvdDtt
PSZxdW90OyBsaW5lcy4mbmJzcDsgQWxsIENMVUUtPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5i
c3A7IGNvbnRyb2xsZWQgUlRQICZxdW90O20mcXVvdDsgbGluZXMgbXVzdCBiZSBzZWN1cmVkIGFu
ZCBpbXBsZW1lbnRlZCB1c2luZzxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyBtZWNoYW5p
c21zIHN1Y2ggYXMgU1JUUCBbUkZDMzcxMV0uJm5ic3A7IENMVUUgaW1wbGVtZW50YXRpb25zIE1B
WSBjaG9vc2U8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgbm90IHRvIHJlcXVpcmUgdGhl
IHVzZSBvZiBTUlRQIHRvIHNlY3VyZSBsZWdhY3kgKG5vbi1DTFVFLWNvbnRyb2xsZWQpPGJyPg0K
Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7IG1lZGlhIGZvciBiYWNrd2FyZHMgY29tcGF0aWJpbGl0
eSB3aXRoIG9sZGVyIFNJUCBjbGllbnRzIHRoYXQgYXJlPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsg
Jm5ic3A7IGluY2FwYWJsZSBvZiBzdXBwb3J0aW5nIGl0Ljxicj4NCjxicj4NCkl0IHNlZW1zIGxp
a2UgeW91IG5lZWQgbW9yZSB0aGFuIHN1cHBvcnQsIHlvdSBhbHNvIG5lZWQgdG8gcmVxdWlyZSB0
aGUgdXNlIG9mIERUTFMtU1JUUCwgbm8/PGJyPg0KPGJyPg0KPG86cD48L286cD48L3A+DQo8L2Js
b2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_6E58094ECC8D8344914996DAD28F1CCD18C7B5DEDGGEMM506MBSchi_--


From nobody Sun Nov 25 05:15:21 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A460A12D7F8 for <clue@ietfa.amsl.com>; Sun, 25 Nov 2018 05:15:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.358
X-Spam-Level: 
X-Spam-Status: No, score=-3.358 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id juJHR46fDPeJ for <clue@ietfa.amsl.com>; Sun, 25 Nov 2018 05:15:17 -0800 (PST)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 0BE791288EB for <clue@ietf.org>; Sun, 25 Nov 2018 05:15:17 -0800 (PST)
Received: by mail-lj1-x233.google.com with SMTP id v15-v6so14095903ljh.13 for <clue@ietf.org>; Sun, 25 Nov 2018 05:15:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OHE8MZlcMklEh2Xb9nbzXuXzUGjqZ+lWLO5sobXTlR0=; b=gycV5Goh5anRSqvTBU8Wf5A8Oq1os1r0VbNwyFzkh/5Gqw4mYqi/fbaZEArK8qDAF5 nLkSGao48FoXAM7NQds1TCHE1LE0jMjilZc8l4iS3NZGP3dfKghQp4930N0oMkkw5dvI sCUwHS3hpqGPAZ1i27BTparkOBNVcrpoOTaQYOVh//El7l29Q/m8LHTeRSsDX1l5Hf6e KqauYddNyp9hTVqswm0gQJqhxYeJ8+nakkDKNNQATZta2zFd2w0jlpazBlwwRBfJaStk +Xhv/4fSeDlSzC3rB0kM7nQh4O5PhXl+s6cisqNnNDYhHKMMB5iai1+Z84ipff9D8wqw ZA+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OHE8MZlcMklEh2Xb9nbzXuXzUGjqZ+lWLO5sobXTlR0=; b=CtjlhYJRm6t2x+WlPSVgoyHUVqEI/wzb5kpAfX+acZZfQTP3k76WYzpj4rrtfx7kOb Hdc3y/rI53Lggxo9UKfu/c2Sg1oaX9PMJRYMmdmxgqQKBAucgyUZoXwp3W6xYKhlNL1v Le31tBZ6JBrDhxo0CDVIdP5JX4loPaWSFpb+Agsc2mxsIFAZ+phllgFHcqq9kiThs4NH 7IxKel1cvIBG7/VjABdBjYoRZZkIbV143wb5IGKby3HVIQscYrOm2t5ZWK+Yc/uvP6A0 gwCnZhnLhvRz1aaJOiR+y3YUVlePTpQLohp6NuZTPj27RIB59BRl/2oKIqc/JcuLUHq5 AetQ==
X-Gm-Message-State: AGRZ1gJ0efmyALzVrxxFcsor1DDNyD7wDjFdzdXUNLG3yGClY2WoB315 KRbF4MCq7wZsCUZWUjiA82gQ9ubTB3t0xPDf6DOrJQ==
X-Google-Smtp-Source: AFSGD/UZEljZ90J+SniBbs7veaah8VHjLGu4CfI3Vq6ZlfjAxGtyjBP2h//u49wA4tEqmH8TIKeOw0PbXWpSSAKp1B4=
X-Received: by 2002:a2e:1551:: with SMTP id 17-v6mr14399876ljv.68.1543151715212;  Sun, 25 Nov 2018 05:15:15 -0800 (PST)
MIME-Version: 1.0
References: <154268892146.26648.17870778354406192041.idtracker@ietfa.amsl.com> <6E58094ECC8D8344914996DAD28F1CCD18C762DF@DGGEMM506-MBX.china.huawei.com> <CABcZeBMcQxZuRUFx=tz==C5eCc8zNBrxkKaZfBa+gYnyaV3FOQ@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD18C7B5DE@DGGEMM506-MBS.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD18C7B5DE@DGGEMM506-MBS.china.huawei.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 25 Nov 2018 05:14:36 -0800
Message-ID: <CABcZeBOPPojS2zsR6uZCagcs7yBBmtMW9rcyPw_gEK44u7GH1w@mail.gmail.com>
To: Roni Even <roni.even@huawei.com>
Cc: IESG <iesg@ietf.org>, Daniel Burnett <danielcburnett@gmail.com>, clue@ietf.org, roni.even@mail01.huawei.com, clue-chairs@ietf.org,  draft-ietf-clue-signaling@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d1f706057b7d01e7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/IZ88oQnz1lrGOA7afE17bTYzvKA>
Subject: Re: [clue] Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Nov 2018 13:15:20 -0000

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

On Sat, Nov 24, 2018 at 9:41 PM Roni Even (A) <roni.even@huawei.com> wrote:

> Hi,
>
> The point that is made that in general CLUE is similar to no CLUE RTP
> media calls. The difference is that since the EP may open more than one RTP
> video channel there is a greater risk of sending more media to the victim.
>

Yes, but in order to have a useful countermeasure, that needs to be
mandatory, and yours is not.

-Ekr


RFC7201 discuss the options to secure the media and this holds for this
> case too.
>



>
> Roni
>
>
>
> *From:* Eric Rescorla [mailto:ekr@rtfm.com]
> *Sent:* Thursday, November 22, 2018 5:27 PM
> *To:* Roni Even (A)
> *Cc:* IESG; Daniel Burnett; clue@ietf.org; roni.even@mail01.huawei.com;
> clue-chairs@ietf.org; draft-ietf-clue-signaling@ietf.org
> *Subject:* Re: Eric Rescorla's No Objection on
> draft-ietf-clue-signaling-14: (with COMMENT)
>
>
>
> The problem is that this is in the context of amplification attacks
>
>
>
>    Beyond the need to secure the constituent protocols, the use of CLUE
>    does impose additional security concerns.  One area of increased risk
>    involves the potential for a malicious party to subvert a CLUE-
>    capable device to attack a third party by driving large volumes of
>    media (particularly video) traffic at them by establishing a
>    connection to the CLUE-capable device and directing the media to the
>    victim.  While this is a risk for all media devices, a CLUE-capable
>    device may allow the attacker to configure multiple media streams to
>    be sent, significantly increasing the volume of traffic directed at
>    the victim.
>
>    This attack can be prevented by ensuring that the media recipient
>    intends to receive the media packets.  As such all CLUE-capable
>    devices MUST support key negotiation and receiver intent assurance
>    via DTLS-SRTP [RFC5763] on CLUE-controlled RTP "m=" lines.
>
>
>
> And so if you don't require DTLS-SRTP or ICE than in fact there is no
> amplification
>
> attack defense.
>
>
>
> -Ekr
>
>
>
>
>
> On Thu, Nov 22, 2018 at 3:24 AM Roni Even (A) <roni.even@huawei.com>
> wrote:
>
> Hi,
> RTP payloads do not require usage of SRTP see RFC7201 and RFC7202
> Roni Even
>
> -----Original Message-----
> From: Eric Rescorla [mailto:ekr@rtfm.com]
> Sent: Tuesday, November 20, 2018 6:42 AM
> To: The IESG
> Cc: Daniel C. Burnett; clue@ietf.org; roni.even@mail01.huawei.com; Roni
> Even; clue-chairs@ietf.org; draft-ietf-clue-signaling@ietf.org
> Subject: Eric Rescorla's No Objection on draft-ietf-clue-signaling-14:
> (with COMMENT)
>
> Eric Rescorla has entered the following ballot position for
> draft-ietf-clue-signaling-14: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-clue-signaling/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Rich version of this review at:
> https://mozphab-ietf.devsvcdev.mozaws.net/D4099
>
>
>
> COMMENTS
> S 12.
> >      via DTLS-SRTP [RFC5763] on CLUE-controlled RTP "m=" lines.  All
> CLUE-
> >      controlled RTP "m" lines must be secured and implemented using
> >      mechanisms such as SRTP [RFC3711].  CLUE implementations MAY choose
> >      not to require the use of SRTP to secure legacy
> (non-CLUE-controlled)
> >      media for backwards compatibility with older SIP clients that are
> >      incapable of supporting it.
>
> It seems like you need more than support, you also need to require the use
> of DTLS-SRTP, no?
>
>

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

<div dir=3D"ltr"><br><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Sat=
, Nov 24, 2018 at 9:41 PM Roni Even (A) &lt;<a href=3D"mailto:roni.even@hua=
wei.com">roni.even@huawei.com</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div class=3D"m_2838869128507060734WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi,<u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The point that is made th=
at in general CLUE is similar to no CLUE RTP media calls. The difference is=
 that since the EP may open more than one RTP video channel
 there is a greater risk of sending more media to the victim.</span></p></d=
iv></div></blockquote><div><br></div><div>Yes, but in order to have a usefu=
l countermeasure, that needs to be mandatory, and yours is not.</div><div><=
br></div><div>-Ekr</div><div><br></div><div> <br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div class=3D=
"m_2838869128507060734WordSection1"><p class=3D"MsoNormal"><span style=3D"f=
ont-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;colo=
r:#1f497d"> RFC7201 discuss the options to secure the media and this holds =
for this case too.</span></p></div></div></blockquote><div><br></div><div><=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple"=
 lang=3D"EN-US"><div class=3D"m_2838869128507060734WordSection1"><p class=
=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Roni<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Eric Res=
corla [mailto:<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.co=
m</a>]
<br>
<b>Sent:</b> Thursday, November 22, 2018 5:27 PM<br>
<b>To:</b> Roni Even (A)<br>
<b>Cc:</b> IESG; Daniel Burnett; <a href=3D"mailto:clue@ietf.org" target=3D=
"_blank">clue@ietf.org</a>; <a href=3D"mailto:roni.even@mail01.huawei.com" =
target=3D"_blank">roni.even@mail01.huawei.com</a>; <a href=3D"mailto:clue-c=
hairs@ietf.org" target=3D"_blank">clue-chairs@ietf.org</a>; <a href=3D"mail=
to:draft-ietf-clue-signaling@ietf.org" target=3D"_blank">draft-ietf-clue-si=
gnaling@ietf.org</a><br>
<b>Subject:</b> Re: Eric Rescorla&#39;s No Objection on draft-ietf-clue-sig=
naling-14: (with COMMENT)<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">The problem is that this is in the context of amplif=
ication attacks<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0=C2=A0 Beyond the need to secure the constitue=
nt protocols, the use of CLUE<br>
=C2=A0=C2=A0 does impose additional security concerns.=C2=A0 One area of in=
creased risk<br>
=C2=A0=C2=A0 involves the potential for a malicious party to subvert a CLUE=
-<br>
=C2=A0=C2=A0 capable device to attack a third party by driving large volume=
s of<br>
=C2=A0=C2=A0 media (particularly video) traffic at them by establishing a<b=
r>
=C2=A0=C2=A0 connection to the CLUE-capable device and directing the media =
to the<br>
=C2=A0=C2=A0 victim.=C2=A0 While this is a risk for all media devices, a CL=
UE-capable<br>
=C2=A0=C2=A0 device may allow the attacker to configure multiple media stre=
ams to<br>
=C2=A0=C2=A0 be sent, significantly increasing the volume of traffic direct=
ed at<br>
=C2=A0=C2=A0 the victim.<br>
<br>
=C2=A0=C2=A0 This attack can be prevented by ensuring that the media recipi=
ent<br>
=C2=A0=C2=A0 intends to receive the media packets.=C2=A0 As such all CLUE-c=
apable<br>
=C2=A0=C2=A0 devices MUST support key negotiation and receiver intent assur=
ance<br>
=C2=A0=C2=A0 via DTLS-SRTP [RFC5763] on CLUE-controlled RTP &quot;m=3D&quot=
; lines.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">And so if you don&#39;t require DTLS-SRTP or ICE tha=
n in fact there is no amplification<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">attack defense.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-Ekr<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Thu, Nov 22, 2018 at 3:24 AM Roni Even (A) &lt;<a=
 href=3D"mailto:roni.even@huawei.com" target=3D"_blank">roni.even@huawei.co=
m</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Hi,<br>
RTP payloads do not require usage of SRTP see RFC7201 and RFC7202<br>
Roni Even<br>
<br>
-----Original Message-----<br>
From: Eric Rescorla [mailto:<a href=3D"mailto:ekr@rtfm.com" target=3D"_blan=
k">ekr@rtfm.com</a>]
<br>
Sent: Tuesday, November 20, 2018 6:42 AM<br>
To: The IESG<br>
Cc: Daniel C. Burnett; <a href=3D"mailto:clue@ietf.org" target=3D"_blank">c=
lue@ietf.org</a>;
<a href=3D"mailto:roni.even@mail01.huawei.com" target=3D"_blank">roni.even@=
mail01.huawei.com</a>; Roni Even;
<a href=3D"mailto:clue-chairs@ietf.org" target=3D"_blank">clue-chairs@ietf.=
org</a>; <a href=3D"mailto:draft-ietf-clue-signaling@ietf.org" target=3D"_b=
lank">
draft-ietf-clue-signaling@ietf.org</a><br>
Subject: Eric Rescorla&#39;s No Objection on draft-ietf-clue-signaling-14: =
(with COMMENT)<br>
<br>
Eric Rescorla has entered the following ballot position for<br>
draft-ietf-clue-signaling-14: No Objection<br>
<br>
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 introduc=
tory paragraph, however.)<br>
<br>
<br>
Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss-crit=
eria.html" target=3D"_blank">
https://www.ietf.org/iesg/statement/discuss-criteria.html</a><br>
for more information about IESG DISCUSS and COMMENT positions.<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-clue-signaling/" tar=
get=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-clue-signaling/<=
/a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
Rich version of this review at:<br>
<a href=3D"https://mozphab-ietf.devsvcdev.mozaws.net/D4099" target=3D"_blan=
k">https://mozphab-ietf.devsvcdev.mozaws.net/D4099</a><br>
<br>
<br>
<br>
COMMENTS<br>
S 12.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 via DTLS-SRTP [RFC5763] on CLUE-controlled RTP &qu=
ot;m=3D&quot; lines.=C2=A0 All CLUE-<br>
&gt;=C2=A0 =C2=A0 =C2=A0 controlled RTP &quot;m&quot; lines must be secured=
 and implemented using<br>
&gt;=C2=A0 =C2=A0 =C2=A0 mechanisms such as SRTP [RFC3711].=C2=A0 CLUE impl=
ementations MAY choose<br>
&gt;=C2=A0 =C2=A0 =C2=A0 not to require the use of SRTP to secure legacy (n=
on-CLUE-controlled)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 media for backwards compatibility with older SIP c=
lients that are<br>
&gt;=C2=A0 =C2=A0 =C2=A0 incapable of supporting it.<br>
<br>
It seems like you need more than support, you also need to require the use =
of DTLS-SRTP, no?<br>
<br>
<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div></div>

--000000000000d1f706057b7d01e7--


From nobody Sun Nov 25 09:35:38 2018
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8142412896A; Sun, 25 Nov 2018 09:35:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SvYDwyYmbJ84; Sun, 25 Nov 2018 09:35:12 -0800 (PST)
Received: from alum-mailsec-scanner-8.mit.edu (alum-mailsec-scanner-8.mit.edu [18.7.68.20]) by ietfa.amsl.com (Postfix) with ESMTP id 667181288EB;  Sun, 25 Nov 2018 09:35:11 -0800 (PST)
X-AuditID: 12074414-347ff70000006380-8e-5bfadd4d0dc0
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 2C.4D.25472.D4DDAFB5; Sun, 25 Nov 2018 12:35:09 -0500 (EST)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id wAPHZ6Or005782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 25 Nov 2018 12:35:07 -0500
To: Eric Rescorla <ekr@rtfm.com>, Roni Even <roni.even@huawei.com>
Cc: IESG <iesg@ietf.org>, Daniel Burnett <danielcburnett@gmail.com>, clue@ietf.org, roni.even@mail01.huawei.com, clue-chairs@ietf.org, draft-ietf-clue-signaling@ietf.org
References: <154268892146.26648.17870778354406192041.idtracker@ietfa.amsl.com> <6E58094ECC8D8344914996DAD28F1CCD18C762DF@DGGEMM506-MBX.china.huawei.com> <CABcZeBMcQxZuRUFx=tz==C5eCc8zNBrxkKaZfBa+gYnyaV3FOQ@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD18C7B5DE@DGGEMM506-MBS.china.huawei.com> <CABcZeBOPPojS2zsR6uZCagcs7yBBmtMW9rcyPw_gEK44u7GH1w@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <b9922f72-932c-a509-95c2-c86765d5ce6d@alum.mit.edu>
Date: Sun, 25 Nov 2018 12:36:01 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CABcZeBOPPojS2zsR6uZCagcs7yBBmtMW9rcyPw_gEK44u7GH1w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrBKsWRmVeSWpSXmKPExsUixO6iqOt391e0wdLzohZfJy1hs9h/6jKz xcad2hbvL21isljx+hy7xYw/E5ktPh07z2LxpOUHswOHx85Zd9k9Wo68ZfVYsuQnk8eOzQ9Y PSY/bmMOYI3isklJzcksSy3St0vgyji47hFbwV/Wio5vp1kaGHezdDFyckgImEisfnmMqYuR i0NI4CCTxLor05ghnIdMEqevHmAGqRIWiJaYdrSFDcQWEXCS2P+7B6yDWWA3o8Se13eg2r8w SUx/v40JpIpNQEtizqH/YDt4Bewlntx7DhTn4GARUJXY/5gTJCwqkCbxt3MJI0SJoMTJmU/A yjkFAiW6Vl8BW8YsYCYxb/NDZghbXOLWk/lMELa8xPa3c5gnMArMQtI+C0nLLCQts5C0LGBk WcUol5hTmqubm5iZU5yarFucnJiXl1qka6GXm1mil5pSuokREh0iOxiPnJQ7xCjAwajEw5ux +me0EGtiWXFl7iFGSQ4mJVHe+Y6/ooX4kvJTKjMSizPii0pzUosPMUpwMCuJ8PLYA5XzpiRW VqUW5cOkpDlYlMR5mU32RgkJpCeWpGanphakFsFkZTg4lCR4o+4ADRUsSk1PrUjLzClBSDNx cIIM5wEafgikhre4IDG3ODMdIn+K0Zhjz9emGcwcq2Z0zGAWYsnLz0uVEucVBCkVACnNKM2D mwZLcK8YxYGeE+bNA6niASZHuHmvgFYxAa2Sn/8dZFVJIkJKqoFxVX390w2Ku62Km162s2+d 2x+yhN2V28lya1J9663HH1kOd1zJuq54xKdgKrNw4L6FD739SgNeHMxXm3+U9fKxMOaF07UZ JWq/bPy2eJZU656C9mWhQl+nf4x6+/otX++8mpPGExacffruUelDWUnhmZuqKv/m60UmVt1t c0pzX3D034ty3QBTJZbijERDLeai4kQATKUrgksDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/JdPawyt_PEADiQ0iLM5VW7CHxNU>
Subject: Re: [clue] Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Nov 2018 17:35:14 -0000

On 11/25/18 8:14 AM, Eric Rescorla wrote:
> 
> 
> On Sat, Nov 24, 2018 at 9:41 PM Roni Even (A) <roni.even@huawei.com 
> <mailto:roni.even@huawei.com>> wrote:
> 
>     Hi,____
> 
>     The point that is made that in general CLUE is similar to no CLUE
>     RTP media calls. The difference is that since the EP may open more
>     than one RTP video channel there is a greater risk of sending more
>     media to the victim.
> 
> 
> Yes, but in order to have a useful countermeasure, that needs to be 
> mandatory, and yours is not.

But one of the goals of clue is to be backward compatible with regular 
sip calls. If we impose constraints on the media over and above those 
required for regular sip calls then we lose that.

	Thanks,
	Paul


From nobody Sun Nov 25 11:30:17 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 786A7130DCA for <clue@ietfa.amsl.com>; Sun, 25 Nov 2018 11:30:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.358
X-Spam-Level: 
X-Spam-Status: No, score=-3.358 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dlXbYo_g-5q6 for <clue@ietfa.amsl.com>; Sun, 25 Nov 2018 11:30:14 -0800 (PST)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 CF381124C04 for <clue@ietf.org>; Sun, 25 Nov 2018 11:30:13 -0800 (PST)
Received: by mail-lj1-x22f.google.com with SMTP id c19-v6so14588827lja.5 for <clue@ietf.org>; Sun, 25 Nov 2018 11:30:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rA+Kw7uR5fgNvVl9tEJkb2CXwtFEZ4JunwpNWISQ6BA=; b=nISc/bJ5zGU1IHwNsyaZQsAk2Hr6teIePobT+tjXmnNNo7XtHQQITQEcfFtnUystOO N+gWQMLn+FFS3gFv4bSBqwyuj8pNbJ26MMgCsSR1KL20UpEZ3RUMnoQJFBi2jpFlmyy1 ML7xkDpQLtZYa/1pVARuSgEEOT564WoMV452V/XvzCUXIBI4wsp7Z75gyR9ZY83mRwOz 7tZ7pmr0AZtvPQwdk3VDw5EmBHdQTqySZFEuhzKc3BOpJRbOZFVLCkODSfV9S7vAqw22 jzlSp5OhT+xJxhOg0olOhFk61OtlTQ3gJttRNTiYIQUrb7vJ5hiNjQr9+1oHCySL7KGW LSLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rA+Kw7uR5fgNvVl9tEJkb2CXwtFEZ4JunwpNWISQ6BA=; b=W0ufgY9QkDcuHyNdMvW4+fV7wWWeZYdw2nvwB/SeiNoap17mZzzVBv/H2tkrpSj5Lt jEfSSECYsspLH0VtIxw/38DLrPvWtCVlgcepdmNke2ICDfNQBx9HQ8vzX+mdKY51ajP+ ZDRPHnrqp4uECFp+oMvtzxYEkvVFDzLXMzMHMIW9KGxsgyI9AzQcYf/U9cHhIr58P4y/ 34zbFxCI1Rc/LUusz0ziDrj+XlWLdlezfjnH5fvBM8Dj/PAB7vS7I7C/KzUd3BrKpq3m Cnr6z7eJtbYmngtvKXZSQDqytIu+2CC1M9u1PQQz5g1u38oQstMhBul95KEb67UwX1TK XeCg==
X-Gm-Message-State: AA+aEWZXg1ZrL6C3dosE9aBmfB1345csZYjRfhll8RVQPjYvbDA3/xOZ UC4eMYcVR3Ovr1ckmbCz+1j1yYi8nc9JUxwyL8jzZQ==
X-Google-Smtp-Source: AFSGD/XEKppLgjkp881mMb60uRbhi/JxO7Eas/pTzr/5kv5LvUznPNDqj7mfalQmpf0i/wmIfSXLUDDQbZ9MdkCn5Tc=
X-Received: by 2002:a2e:9a84:: with SMTP id p4-v6mr14812367lji.73.1543174211931;  Sun, 25 Nov 2018 11:30:11 -0800 (PST)
MIME-Version: 1.0
References: <154268892146.26648.17870778354406192041.idtracker@ietfa.amsl.com> <6E58094ECC8D8344914996DAD28F1CCD18C762DF@DGGEMM506-MBX.china.huawei.com> <CABcZeBMcQxZuRUFx=tz==C5eCc8zNBrxkKaZfBa+gYnyaV3FOQ@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD18C7B5DE@DGGEMM506-MBS.china.huawei.com> <CABcZeBOPPojS2zsR6uZCagcs7yBBmtMW9rcyPw_gEK44u7GH1w@mail.gmail.com> <b9922f72-932c-a509-95c2-c86765d5ce6d@alum.mit.edu>
In-Reply-To: <b9922f72-932c-a509-95c2-c86765d5ce6d@alum.mit.edu>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 25 Nov 2018 11:29:34 -0800
Message-ID: <CABcZeBNb4nG7U9KdMLCT8f4oOYXqWydM_1JQPbfceSu31+Bg1A@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: Roni Even <roni.even@huawei.com>, IESG <iesg@ietf.org>,  Daniel Burnett <danielcburnett@gmail.com>, clue@ietf.org, roni.even@mail01.huawei.com,  clue-chairs@ietf.org, draft-ietf-clue-signaling@ietf.org
Content-Type: multipart/alternative; boundary="000000000000baa370057b823e3d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/fGBdlxV9SKT_SklR9XjJAfzOiXs>
Subject: Re: [clue] Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Nov 2018 19:30:15 -0000

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

On Sun, Nov 25, 2018 at 9:35 AM Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> On 11/25/18 8:14 AM, Eric Rescorla wrote:
> >
> >
> > On Sat, Nov 24, 2018 at 9:41 PM Roni Even (A) <roni.even@huawei.com
> > <mailto:roni.even@huawei.com>> wrote:
> >
> >     Hi,____
> >
> >     The point that is made that in general CLUE is similar to no CLUE
> >     RTP media calls. The difference is that since the EP may open more
> >     than one RTP video channel there is a greater risk of sending more
> >     media to the victim.
> >
> >
> > Yes, but in order to have a useful countermeasure, that needs to be
> > mandatory, and yours is not.
>
> But one of the goals of clue is to be backward compatible with regular
> sip calls. If we impose constraints on the media over and above those
> required for regular sip calls then we lose that.
>

ISTM that that's already not true for these media flows, because 4.4.1
requires them to
be inactive and you need to use an SCTP/DTLS control channel to negotiate
them.
What I'm saying is that those other flows should also have a consent check

-Ekr


>         Thanks,
>         Paul
>

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

<div dir=3D"ltr"><br><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Sun=
, Nov 25, 2018 at 9:35 AM Paul Kyzivat &lt;<a href=3D"mailto:pkyzivat@alum.=
mit.edu" target=3D"_blank">pkyzivat@alum.mit.edu</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">On 11/25/18 8:14 AM, Eric Rescorla wrote:<br>
&gt; <br>
&gt; <br>
&gt; On Sat, Nov 24, 2018 at 9:41 PM Roni Even (A) &lt;<a href=3D"mailto:ro=
ni.even@huawei.com" target=3D"_blank">roni.even@huawei.com</a> <br>
&gt; &lt;mailto:<a href=3D"mailto:roni.even@huawei.com" target=3D"_blank">r=
oni.even@huawei.com</a>&gt;&gt; wrote:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Hi,____<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0The point that is made that in general CLUE is simi=
lar to no CLUE<br>
&gt;=C2=A0 =C2=A0 =C2=A0RTP media calls. The difference is that since the E=
P may open more<br>
&gt;=C2=A0 =C2=A0 =C2=A0than one RTP video channel there is a greater risk =
of sending more<br>
&gt;=C2=A0 =C2=A0 =C2=A0media to the victim.<br>
&gt; <br>
&gt; <br>
&gt; Yes, but in order to have a useful countermeasure, that needs to be <b=
r>
&gt; mandatory, and yours is not.<br>
<br>
But one of the goals of clue is to be backward compatible with regular <br>
sip calls. If we impose constraints on the media over and above those <br>
required for regular sip calls then we lose that.<br></blockquote><div><br>=
</div><div>ISTM that that&#39;s already not true for these media flows, bec=
ause 4.4.1 requires them to</div><div>be inactive and you need to use an SC=
TP/DTLS control channel to negotiate them.</div><div>What I&#39;m saying is=
 that those other flows should also have a consent check<br></div><div><br>=
</div><div>-Ekr</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Thanks,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Paul<br>
</blockquote></div></div>

--000000000000baa370057b823e3d--


From nobody Mon Nov 26 11:48:54 2018
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39FA112D84C; Mon, 26 Nov 2018 11:48:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 1L-w6c285YAg; Mon, 26 Nov 2018 11:48:37 -0800 (PST)
Received: from alum-mailsec-scanner-6.mit.edu (alum-mailsec-scanner-6.mit.edu [18.7.68.18]) by ietfa.amsl.com (Postfix) with ESMTP id 2DF5B130F8E;  Mon, 26 Nov 2018 11:48:36 -0800 (PST)
X-AuditID: 12074412-41bff70000007195-65-5bfc4e1401a6
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id 45.93.29077.41E4CFB5; Mon, 26 Nov 2018 14:48:36 -0500 (EST)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id wAQJmXYj022267 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 26 Nov 2018 14:48:34 -0500
To: Eric Rescorla <ekr@rtfm.com>
Cc: Roni Even <roni.even@huawei.com>, IESG <iesg@ietf.org>, Daniel Burnett <danielcburnett@gmail.com>, clue@ietf.org, roni.even@mail01.huawei.com, clue-chairs@ietf.org, draft-ietf-clue-signaling@ietf.org
References: <154268892146.26648.17870778354406192041.idtracker@ietfa.amsl.com> <6E58094ECC8D8344914996DAD28F1CCD18C762DF@DGGEMM506-MBX.china.huawei.com> <CABcZeBMcQxZuRUFx=tz==C5eCc8zNBrxkKaZfBa+gYnyaV3FOQ@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD18C7B5DE@DGGEMM506-MBS.china.huawei.com> <CABcZeBOPPojS2zsR6uZCagcs7yBBmtMW9rcyPw_gEK44u7GH1w@mail.gmail.com> <b9922f72-932c-a509-95c2-c86765d5ce6d@alum.mit.edu> <CABcZeBNb4nG7U9KdMLCT8f4oOYXqWydM_1JQPbfceSu31+Bg1A@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <e8a805d2-762d-6cd7-bed5-4518e943453c@alum.mit.edu>
Date: Mon, 26 Nov 2018 14:48:33 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CABcZeBNb4nG7U9KdMLCT8f4oOYXqWydM_1JQPbfceSu31+Bg1A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrBKsWRmVeSWpSXmKPExsUixO6iqCvi9yfa4PA+YYuvk5awWew/dZnZ YuNObYv3lzYxWax4fY7dYsaficwWn46dZ7F40vKD2YHDY+esu+weLUfesnosWfKTyWPH5ges HpMftzEHsEZx2aSk5mSWpRbp2yVwZTQ8SCn4zVPxYfN7lgbGA5xdjJwcEgImEosf/mPrYuTi EBI4yCSx6vVqFgjnIZPEuQsn2ECqhAWiJaYdbQGzRQQUJH79OQFWxCzwjFHiVucsqI6PzBK3 H55nBqliE9CSmHPoPwuIzStgL7Fy00tGEJtFQFXidcNtsBpRgTSJv51LGCFqBCVOznwCVs8p ECixf/MhJhCbWcBMYt7mh8wQtrjErSfzoeLyEs1bZzNPYBSYhaR9FpKWWUhaZiFpWcDIsopR LjGnNFc3NzEzpzg1Wbc4OTEvL7VI10wvN7NELzWldBMjJDqEdjCuPyl3iFGAg1GJh3fD99/R QqyJZcWVuYcYJTmYlER5Pf4ChfiS8lMqMxKLM+KLSnNSiw8xSnAwK4nw+i4ByvGmJFZWpRbl w6SkOViUxHmZTfZGCQmkJ5akZqemFqQWwWRlODiUJHgVfP9ECwkWpaanVqRl5pQgpJk4OEGG 8wANP+ADVMNbXJCYW5yZDpE/xWjMsedr0wxmjlUzOmYwC7Hk5eelSonzxoCMEwApzSjNg5sG S3CvGMWBnhPmXQ0ykAeYHOHmvQJaxQS06tpEkD+KSxIRUlINjKvST4Rf0X1oPXXd/v+KM4Ki zdiaI3SAgXy56WVX8/+vpjs72Mz2v9iykLekz/POKjdTCy323NZjYkZKdXwWOizpxl+9C6pq WgxuRHmU7DZQyjzWmy5859mbxzdEMwsD1T7Mu8fKOU1jdXGE1rwdC/uEFtikeTV+fmqoL38u YnXQOdbzSj5KLMUZiYZazEXFiQBs+guXSwMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/dMjYvcdyHo5-Vz8MU-iWs4Zpfrs>
Subject: Re: [clue] Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2018 19:48:40 -0000

On 11/25/18 2:29 PM, Eric Rescorla wrote:
> 
> 
> On Sun, Nov 25, 2018 at 9:35 AM Paul Kyzivat <pkyzivat@alum.mit.edu 
> <mailto:pkyzivat@alum.mit.edu>> wrote:
> 
>     On 11/25/18 8:14 AM, Eric Rescorla wrote:
>      >
>      >
>      > On Sat, Nov 24, 2018 at 9:41 PM Roni Even (A)
>     <roni.even@huawei.com <mailto:roni.even@huawei.com>
>      > <mailto:roni.even@huawei.com <mailto:roni.even@huawei.com>>> wrote:
>      >
>      >     Hi,____
>      >
>      >     The point that is made that in general CLUE is similar to no CLUE
>      >     RTP media calls. The difference is that since the EP may open
>     more
>      >     than one RTP video channel there is a greater risk of sending
>     more
>      >     media to the victim.
>      >
>      >
>      > Yes, but in order to have a useful countermeasure, that needs to be
>      > mandatory, and yours is not.
> 
>     But one of the goals of clue is to be backward compatible with regular
>     sip calls. If we impose constraints on the media over and above those
>     required for regular sip calls then we lose that.
> 
> 
> ISTM that that's already not true for these media flows, because 4.4.1 
> requires them to
> be inactive and you need to use an SCTP/DTLS control channel to 
> negotiate them.
> What I'm saying is that those other flows should also have a consent check

I was more concerned with the basic audio and/or video in the initial 
invite, before it is known whether the answerer supports clue. I don't 
have a particular problem with putting further restrictions on the clue 
controlled media.

	Thanks,
	Paul


From nobody Tue Nov 27 01:55:22 2018
Return-Path: <rohanse2@cisco.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A74E1276D0; Tue, 27 Nov 2018 01:55:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.96
X-Spam-Level: 
X-Spam-Status: No, score=-15.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xJSZY9Zz-ij3; Tue, 27 Nov 2018 01:55:18 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7880127B4C; Tue, 27 Nov 2018 01:55:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6102; q=dns/txt; s=iport; t=1543312518; x=1544522118; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ajQaWqXZcaaclsBYYVOPpuS53cUEfedNJr0RsRozkR0=; b=in+ugy+BFkzzkS8ocUgceC92vlXmCwUl+fCvkQaQ/mcJTWoEjDr4zmLw EYH3uaOggun16GCvMQc9UZMT2fasBAsPaR/+P6UfsMTffjZ0HoygaUJfX a2NAwisruEfAMDd3g7EQxfbUSWBE0ibbOFauMo07jG2ewHlOhT2xD/obG I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AEAACnE/1b/40NJK1kDgwBAQEBAQI?= =?us-ascii?q?BAQEBBwIBAQEBgVEFAQEBAQsBgVUuZoECJwqDb4gYjhODRYVKjjGBegsBASW?= =?us-ascii?q?ERwIXhBkiNAkNAQMBAQIBAQJtHAyFPAEBAQEDIxFFDAQCAQgOAwQBAQECAiM?= =?us-ascii?q?DAgICHxEUAQgIAgQBDQUIgxqBaQMVD6UYgS+EMQMNQIMIDYIXBYELiDqCSII?= =?us-ascii?q?WgRGDEoJXRwICAQEWhEuCVwKBKgGILYE9lEkuBgMChnqDLYNbgyQgkQuNRoE?= =?us-ascii?q?KiUACERSBJx84gVVwgW6BToInFxKITIUEO0ExAY1RgR8BAQ?=
X-IronPort-AV: E=Sophos;i="5.56,286,1539648000"; d="scan'208";a="491705988"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Nov 2018 09:55:16 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id wAR9tG2n029053 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 27 Nov 2018 09:55:16 GMT
Received: from xch-rcd-016.cisco.com (173.37.102.26) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 27 Nov 2018 03:55:15 -0600
Received: from xch-rcd-016.cisco.com ([173.37.102.26]) by XCH-RCD-016.cisco.com ([173.37.102.26]) with mapi id 15.00.1395.000; Tue, 27 Nov 2018 03:55:15 -0600
From: "Rob Hanton (rohanse2)" <rohanse2@cisco.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Eric Rescorla <ekr@rtfm.com>
CC: Roni Even <roni.even@huawei.com>, IESG <iesg@ietf.org>, Daniel Burnett <danielcburnett@gmail.com>, "clue@ietf.org" <clue@ietf.org>, "roni.even@mail01.huawei.com" <roni.even@mail01.huawei.com>, "clue-chairs@ietf.org" <clue-chairs@ietf.org>, "draft-ietf-clue-signaling@ietf.org" <draft-ietf-clue-signaling@ietf.org>
Thread-Topic: Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
Thread-Index: AQHUgItlNzV1mBjQhkStyjijOx0gwqVcD0cAgABD4YCABBM5gIAAfr0AgABJCoCAAB+6AIABl6KAgACEumA=
Date: Tue, 27 Nov 2018 09:55:15 +0000
Message-ID: <8524dc46c43e4f5084fbbd2e566f9c28@XCH-RCD-016.cisco.com>
References: <154268892146.26648.17870778354406192041.idtracker@ietfa.amsl.com> <6E58094ECC8D8344914996DAD28F1CCD18C762DF@DGGEMM506-MBX.china.huawei.com> <CABcZeBMcQxZuRUFx=tz==C5eCc8zNBrxkKaZfBa+gYnyaV3FOQ@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD18C7B5DE@DGGEMM506-MBS.china.huawei.com> <CABcZeBOPPojS2zsR6uZCagcs7yBBmtMW9rcyPw_gEK44u7GH1w@mail.gmail.com> <b9922f72-932c-a509-95c2-c86765d5ce6d@alum.mit.edu> <CABcZeBNb4nG7U9KdMLCT8f4oOYXqWydM_1JQPbfceSu31+Bg1A@mail.gmail.com> <e8a805d2-762d-6cd7-bed5-4518e943453c@alum.mit.edu>
In-Reply-To: <e8a805d2-762d-6cd7-bed5-4518e943453c@alum.mit.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.138.252]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.27, xch-aln-017.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/AfJ0tzHc6B3XlYwxJMh7xurCE14>
Subject: Re: [clue] Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2018 09:55:20 -0000

V2UgZGlkIGhhdmUgc3BlY2lmaWMgcHJvdGVjdGlvbnMgYXMgbWFuZGFudG9yeSB0byB1c2UgaW4g
ZWFybGllciBkcmFmdHMuIEZyb20gdmVyc2lvbiAwNToNCg0KICAgLi4uIGRpc2N1c3Npb24gb2Yg
dmlkZW8gaGFtbWVyIGF0dGFjayAuLi4NCiAgIFRoaXMgYXR0YWNrIGNhbiBiZSBwcmV2ZW50ZWQg
YnkgZW5zdXJpbmcgdGhhdCB0aGUgbWVkaWEgcmVjaXBpZW50DQogICBpbnRlbmRzIHRvIHJlY2Vp
dmUgdGhlIG1lZGlhIHBhY2tldHMuICBCZWNhdXNlIG9mIHRoZSB3YXkgdGhhdCBDTFVFDQogICBj
YW4gaW5jcmVhc2UgdGhlIHNldmVyaXR5IG9mIHRoaXMgYXR0YWNrLCBhcyB3ZWxsIGFzIGJlY2F1
c2Ugb2YgdGhlDQogICBnZW5lcmFsIGluY3JlYXNlZCBhd2FyZW5lc3Mgb2YgdGhlIG5lZWQgdG8g
c2VjdXJlIGNyaXRpY2FsIHBheWxvYWRzLA0KICAgYSBDTFVFLWNhcGFibGUgZGV2aWNlIE1VU1Qg
c2VjdXJlIGFsbCBDTFVFLWNvbnRyb2xsZWQgUlRQICJtIiBsaW5lcw0KICAgdXNpbmcgU1JUUCBb
UkZDMzcxMV0sIGFuZCBNVVNUIHN1cHBvcnQgYW5kIHVzZSBrZXkgbmVnb3RpYXRpb24gYW5kDQog
ICByZWNlaXZlciBpbnRlbnQgYXNzdXJhbmNlIHZpYSBEVExTIFtSRkM1NzYzXSBvbiB0aGVzZSAi
bSIgbGluZXMuICBGb3INCiAgIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5LCB0aGlzIGlzIG5vdCBh
IG1hbmRhdG9yeSByZXF1aXJlbWVudCBmb3Igbm9uLQ0KICAgQ0xVRS1jb250cm9sbGVkICJtIiBs
aW5lcy4NCg0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1jbHVl
LXNpZ25hbGluZy8wNS8/aW5jbHVkZV90ZXh0PTENCg0KVGhpcyB3YXMgdGhlbiBjaGFuZ2VkIGlu
IHZlcnNpb24gMDYgYW5kIG9ud2FyZHMgZm9sbG93aW5nIHRoZSBkaXNjdXNzaW9uIGF0IElFVEYg
OTIgYW5kIGxhdGVyIHdoZXJlIHRoZXJlIHdhcyBvcHBvc2l0aW9uIHRvIG1ha2luZyB0aGUgdXNl
IG9mIERUTFMvU1JUUCBtYW5kYXRvcnkgdG8gdXNlLiBJZiBJIHJlY2FsbCB0aGUgdHdvIG1ham9y
IGNvbmNlcm5zIHBlb3BsZSBoYWQgd2VyZToNCjEpIFRoaXMgcHJldmVudHMgaW1wbGVtZW50YXRp
b25zIHVzaW5nIGEgc3VwZXJpb3IgbWVjaGFuaXNtIHNob3VsZCBvbmUgYmUgZGV2ZWxvcGVkDQoy
KSBUaGlzIHByZXZlbnRzIHR3byBkZXZpY2VzIGZyb20gdGhlIHNhbWUgdmVuZG9yIHVzaW5nIHNv
bWUgYWx0ZXJuYXRlIG1lYW5zIG9mIGF1dGhlbnRpY2F0aW9uIChwb3RlbnRpYWxseSBwcm9wcmll
dGFyeSkgdGhhdCB3b3VsZCByZWR1Y2UgdGhlIG5lZWQgZm9yIERUTFMvU1JUUA0KKE1pbnV0ZXM6
IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL21pbnV0ZXMtOTItY2x1ZS8gKQ0KDQpT
byB3aGlsZSBldmVyeW9uZSBhZ3JlZWQgdGhhdCBEVExTL1NSVFAgc2hvdWxkIGJlIG1hbmRhdG9y
eSB0byBpbXBsZW1lbnQgc28gaXQgd2FzIGFsd2F5cyBhdmFpbGFibGUsIGNvbnNlbnN1cyBlbmRl
ZCB1cCBiZWluZyByZW1vdmluZyB0aGUgcmVxdWlyZW1lbnQgdG8gdXNlIERUTFMvU1JUUCBhbmQg
aW5zdGVhZCBoYXZpbmcgbW9yZSBnZW5lcmljIGxhbmd1YWdlOg0KDQogICBUaGlzIGF0dGFjayBj
YW4gYmUgcHJldmVudGVkIGJ5IGVuc3VyaW5nIHRoYXQgdGhlIG1lZGlhIHJlY2lwaWVudA0KICAg
aW50ZW5kcyB0byByZWNlaXZlIHRoZSBtZWRpYSBwYWNrZXRzLiAgQXMgc3VjaCBhbGwgQ0xVRS1j
YXBhYmxlDQogICBkZXZpY2VzIE1VU1Qgc3VwcG9ydCBrZXkgbmVnb3RpYXRpb24gYW5kIHJlY2Vp
dmVyIGludGVudCBhc3N1cmFuY2UNCiAgIHZpYSBEVExTLVNSVFAgW1JGQzU3NjNdIG9uIENMVUUt
Y29udHJvbGxlZCBSVFAgIm09IiBsaW5lcy4gIEFsbCBDTFVFLQ0KICAgY29udHJvbGxlZCBSVFAg
Im0iIGxpbmVzIG11c3QgYmUgc2VjdXJlZCBhbmQgaW1wbGVtZW50ZWQgdXNpbmcNCiAgIG1lY2hh
bmlzbXMgc3VjaCBhcyBTUlRQIFtSRkMzNzExXS4gIENMVUUgaW1wbGVtZW50YXRpb25zIE1BWSBj
aG9vc2UNCiAgIG5vdCB0byByZXF1aXJlIHRoZSB1c2Ugb2YgU1JUUCB0byBzZWN1cmUgbGVnYWN5
IChub24tQ0xVRS1jb250cm9sbGVkKQ0KICAgbWVkaWEgZm9yIGJhY2t3YXJkcyBjb21wYXRpYmls
aXR5IHdpdGggb2xkZXIgU0lQIGNsaWVudHMgdGhhdCBhcmUNCiAgIGluY2FwYWJsZSBvZiBzdXBw
b3J0aW5nIGl0Lg0KDQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRm
LWNsdWUtc2lnbmFsaW5nLz9pbmNsdWRlX3RleHQ9MQ0KDQpBbGwgZHJhZnRzIGhhdmUgYWx3YXlz
IGhhZCBhbiBleGNlcHRpb24gZm9yIG5vbi1DTFVFLWNvbnRyb2xsZWQgbGluZXMgZm9yIGJhY2t3
YXJkcyBjb21wYXRpYmlsaXR5Lg0KDQpSb2INCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
CkZyb206IFBhdWwgS3l6aXZhdCA8cGt5eml2YXRAYWx1bS5taXQuZWR1PiANClNlbnQ6IDI2IE5v
dmVtYmVyIDIwMTggMTk6NDkNClRvOiBFcmljIFJlc2NvcmxhIDxla3JAcnRmbS5jb20+DQpDYzog
Um9uaSBFdmVuIDxyb25pLmV2ZW5AaHVhd2VpLmNvbT47IElFU0cgPGllc2dAaWV0Zi5vcmc+OyBE
YW5pZWwgQnVybmV0dCA8ZGFuaWVsY2J1cm5ldHRAZ21haWwuY29tPjsgY2x1ZUBpZXRmLm9yZzsg
cm9uaS5ldmVuQG1haWwwMS5odWF3ZWkuY29tOyBjbHVlLWNoYWlyc0BpZXRmLm9yZzsgZHJhZnQt
aWV0Zi1jbHVlLXNpZ25hbGluZ0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IEVyaWMgUmVzY29ybGEn
cyBObyBPYmplY3Rpb24gb24gZHJhZnQtaWV0Zi1jbHVlLXNpZ25hbGluZy0xNDogKHdpdGggQ09N
TUVOVCkNCg0KT24gMTEvMjUvMTggMjoyOSBQTSwgRXJpYyBSZXNjb3JsYSB3cm90ZToNCj4gDQo+
IA0KPiBPbiBTdW4sIE5vdiAyNSwgMjAxOCBhdCA5OjM1IEFNIFBhdWwgS3l6aXZhdCA8cGt5eml2
YXRAYWx1bS5taXQuZWR1IA0KPiA8bWFpbHRvOnBreXppdmF0QGFsdW0ubWl0LmVkdT4+IHdyb3Rl
Og0KPiANCj4gICAgIE9uIDExLzI1LzE4IDg6MTQgQU0sIEVyaWMgUmVzY29ybGEgd3JvdGU6DQo+
ICAgICAgPg0KPiAgICAgID4NCj4gICAgICA+IE9uIFNhdCwgTm92IDI0LCAyMDE4IGF0IDk6NDEg
UE0gUm9uaSBFdmVuIChBKQ0KPiAgICAgPHJvbmkuZXZlbkBodWF3ZWkuY29tIDxtYWlsdG86cm9u
aS5ldmVuQGh1YXdlaS5jb20+DQo+ICAgICAgPiA8bWFpbHRvOnJvbmkuZXZlbkBodWF3ZWkuY29t
IDxtYWlsdG86cm9uaS5ldmVuQGh1YXdlaS5jb20+Pj4gd3JvdGU6DQo+ICAgICAgPg0KPiAgICAg
ID7CoCDCoCDCoEhpLF9fX18NCj4gICAgICA+DQo+ICAgICAgPsKgIMKgIMKgVGhlIHBvaW50IHRo
YXQgaXMgbWFkZSB0aGF0IGluIGdlbmVyYWwgQ0xVRSBpcyBzaW1pbGFyIHRvIG5vIENMVUUNCj4g
ICAgICA+wqAgwqAgwqBSVFAgbWVkaWEgY2FsbHMuIFRoZSBkaWZmZXJlbmNlIGlzIHRoYXQgc2lu
Y2UgdGhlIEVQIG1heSBvcGVuDQo+ICAgICBtb3JlDQo+ICAgICAgPsKgIMKgIMKgdGhhbiBvbmUg
UlRQIHZpZGVvIGNoYW5uZWwgdGhlcmUgaXMgYSBncmVhdGVyIHJpc2sgb2Ygc2VuZGluZw0KPiAg
ICAgbW9yZQ0KPiAgICAgID7CoCDCoCDCoG1lZGlhIHRvIHRoZSB2aWN0aW0uDQo+ICAgICAgPg0K
PiAgICAgID4NCj4gICAgICA+IFllcywgYnV0IGluIG9yZGVyIHRvIGhhdmUgYSB1c2VmdWwgY291
bnRlcm1lYXN1cmUsIHRoYXQgbmVlZHMgdG8gYmUNCj4gICAgICA+IG1hbmRhdG9yeSwgYW5kIHlv
dXJzIGlzIG5vdC4NCj4gDQo+ICAgICBCdXQgb25lIG9mIHRoZSBnb2FscyBvZiBjbHVlIGlzIHRv
IGJlIGJhY2t3YXJkIGNvbXBhdGlibGUgd2l0aCByZWd1bGFyDQo+ICAgICBzaXAgY2FsbHMuIElm
IHdlIGltcG9zZSBjb25zdHJhaW50cyBvbiB0aGUgbWVkaWEgb3ZlciBhbmQgYWJvdmUgdGhvc2UN
Cj4gICAgIHJlcXVpcmVkIGZvciByZWd1bGFyIHNpcCBjYWxscyB0aGVuIHdlIGxvc2UgdGhhdC4N
Cj4gDQo+IA0KPiBJU1RNIHRoYXQgdGhhdCdzIGFscmVhZHkgbm90IHRydWUgZm9yIHRoZXNlIG1l
ZGlhIGZsb3dzLCBiZWNhdXNlIDQuNC4xIA0KPiByZXF1aXJlcyB0aGVtIHRvIGJlIGluYWN0aXZl
IGFuZCB5b3UgbmVlZCB0byB1c2UgYW4gU0NUUC9EVExTIGNvbnRyb2wgDQo+IGNoYW5uZWwgdG8g
bmVnb3RpYXRlIHRoZW0uDQo+IFdoYXQgSSdtIHNheWluZyBpcyB0aGF0IHRob3NlIG90aGVyIGZs
b3dzIHNob3VsZCBhbHNvIGhhdmUgYSBjb25zZW50IA0KPiBjaGVjaw0KDQpJIHdhcyBtb3JlIGNv
bmNlcm5lZCB3aXRoIHRoZSBiYXNpYyBhdWRpbyBhbmQvb3IgdmlkZW8gaW4gdGhlIGluaXRpYWwg
aW52aXRlLCBiZWZvcmUgaXQgaXMga25vd24gd2hldGhlciB0aGUgYW5zd2VyZXIgc3VwcG9ydHMg
Y2x1ZS4gSSBkb24ndCBoYXZlIGEgcGFydGljdWxhciBwcm9ibGVtIHdpdGggcHV0dGluZyBmdXJ0
aGVyIHJlc3RyaWN0aW9ucyBvbiB0aGUgY2x1ZSBjb250cm9sbGVkIG1lZGlhLg0KDQoJVGhhbmtz
LA0KCVBhdWwNCg==


From nobody Tue Nov 27 07:12:11 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B599130DDA for <clue@ietfa.amsl.com>; Tue, 27 Nov 2018 07:12:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.358
X-Spam-Level: 
X-Spam-Status: No, score=-3.358 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t40EK-xwiDeP for <clue@ietfa.amsl.com>; Tue, 27 Nov 2018 07:11:59 -0800 (PST)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 97289130DE1 for <clue@ietf.org>; Tue, 27 Nov 2018 07:11:55 -0800 (PST)
Received: by mail-lj1-x22f.google.com with SMTP id u6-v6so20371479ljd.1 for <clue@ietf.org>; Tue, 27 Nov 2018 07:11:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DMmvcJDNDF8MgZMlmIuxh/nKOtjYl4QKOcB5Kcpvs6Y=; b=UfubqsegGsnh0DtSjbk9dQvzEd658ksz52tX+yNKs0+IQSK6c+Rw+d5yrnPNPQaA8y jrtZJ1jIunBrq4teKYY4F33neubuHvsjyXNdUdqckGH9bMXqvaenNaUr0DX17Fh95gCD jIyNayJ4E8w7S4sKbiCNqc+NxTwDcqMZ/UqKXrHNyUZM9LUuGm4IbUl7txD6zu76yIvb 73LfktNj0v6pkj7MQRoPII2ofWAXOCStfY6pkMv+1Dqf0vm5GjcSMWcrivAqkV8aywUO WtDw+j76CHmhCzToRbVjK/ie/tQWZ2JnvnHriyxaSmPRRBCwrE8EqJLhJ2L03qCuLs4k jS3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DMmvcJDNDF8MgZMlmIuxh/nKOtjYl4QKOcB5Kcpvs6Y=; b=F2Ua5KpNMaaPJST9WYF6tRKXMBLnqqgZA5/MciVojf4ux6AHeiwANmqverRoMcMju9 Tu3sbfs+umGe41Ovpyt1BowA0vZrEHG++o+CZvP7Eh7zXuPo9Llu+AwVDA+2A+Vt5FHk LE6mnsMBz25gLWtGiR7MToLBJtOq7No5uhtX5sHMlMn5/nMCmMqK29dtaRFx6cMbxXZ1 qXnEi5StTt8hiUzf0Yz3ET9ypGY9ju2kPO7tqpjH0oKo84jKDhGbCiyPRW67z5/oTzB4 kyLDTUxHj9HCKHPQys0ZgffmJZh01c+Y6fBKQkUQivUPYaUNwYgVXL4iICQl6p+RqA0N z44w==
X-Gm-Message-State: AA+aEWbC/gYvMi4J0LDUvihyiBmSZwx86wlwk+ro/+hbWl8UaZ4EnPg7 76+AzXwYt8qQbwJW5DTu3rHW6d8J0N2q0FKHpis0gQ==
X-Google-Smtp-Source: AFSGD/UMtDEUUHteBP8f6YOO0yOEcb8jdac5GwMa4ZrkDZ51mBdjSK6+KSXrDJyPrdYH0hZ2jIsG/YysBjzOAIuD7to=
X-Received: by 2002:a2e:9a84:: with SMTP id p4-v6mr590421lji.73.1543331513757;  Tue, 27 Nov 2018 07:11:53 -0800 (PST)
MIME-Version: 1.0
References: <154268892146.26648.17870778354406192041.idtracker@ietfa.amsl.com> <6E58094ECC8D8344914996DAD28F1CCD18C762DF@DGGEMM506-MBX.china.huawei.com> <CABcZeBMcQxZuRUFx=tz==C5eCc8zNBrxkKaZfBa+gYnyaV3FOQ@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD18C7B5DE@DGGEMM506-MBS.china.huawei.com> <CABcZeBOPPojS2zsR6uZCagcs7yBBmtMW9rcyPw_gEK44u7GH1w@mail.gmail.com> <b9922f72-932c-a509-95c2-c86765d5ce6d@alum.mit.edu> <CABcZeBNb4nG7U9KdMLCT8f4oOYXqWydM_1JQPbfceSu31+Bg1A@mail.gmail.com> <e8a805d2-762d-6cd7-bed5-4518e943453c@alum.mit.edu> <8524dc46c43e4f5084fbbd2e566f9c28@XCH-RCD-016.cisco.com>
In-Reply-To: <8524dc46c43e4f5084fbbd2e566f9c28@XCH-RCD-016.cisco.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 27 Nov 2018 07:11:16 -0800
Message-ID: <CABcZeBNwvzJ98qrCW6tiTozBsKiGJEnVi5MBQz32Udrizp180Q@mail.gmail.com>
To: rohanse2@cisco.com
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, Roni Even <roni.even@huawei.com>, IESG <iesg@ietf.org>,  Daniel Burnett <danielcburnett@gmail.com>, clue@ietf.org, roni.even@mail01.huawei.com,  clue-chairs@ietf.org, draft-ietf-clue-signaling@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a60aca057ba6ded6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/NSrBJVD1rox-lYY8X2IVH-LpzXU>
Subject: Re: [clue] Eric Rescorla's No Objection on draft-ietf-clue-signaling-14: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2018 15:12:01 -0000

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

On Tue, Nov 27, 2018 at 1:55 AM Rob Hanton (rohanse2) <rohanse2@cisco.com>
wrote:

> We did have specific protections as mandantory to use in earlier drafts.
> From version 05:
>
>    ... discussion of video hammer attack ...
>    This attack can be prevented by ensuring that the media recipient
>    intends to receive the media packets.  Because of the way that CLUE
>    can increase the severity of this attack, as well as because of the
>    general increased awareness of the need to secure critical payloads,
>    a CLUE-capable device MUST secure all CLUE-controlled RTP "m" lines
>    using SRTP [RFC3711], and MUST support and use key negotiation and
>    receiver intent assurance via DTLS [RFC5763] on these "m" lines.  For
>    backwards compatibility, this is not a mandatory requirement for non-
>    CLUE-controlled "m" lines.
>
>
> https://datatracker.ietf.org/doc/draft-ietf-clue-signaling/05/?include_text=1
>
> This was then changed in version 06 and onwards following the discussion
> at IETF 92 and later where there was opposition to making the use of
> DTLS/SRTP mandatory to use. If I recall the two major concerns people had
> were:
> 1) This prevents implementations using a superior mechanism should one be
> developed
>

I don't think this is a real objection, If a new mechanism should be
developed, then presumably it would also be documented in an RFC and we
could update this one.

2) This prevents two devices from the same vendor using some alternate
> means of authentication (potentially proprietary) that would reduce the
> need for DTLS/SRTP
> (Minutes: https://datatracker.ietf.org/doc/minutes-92-clue/ )
>

It's not a matter of authentication. It's a matter of path validation. For
instance, if you were to have a situation where you had a cryptographic key
but it did not have an interactive handshake, that would not provide the
correct function. By contrast, ICE would.


So while everyone agreed that DTLS/SRTP should be mandatory to implement so
> it was always available, consensus ended up being removing the requirement
> to use DTLS/SRTP and instead having more generic language:
>
>    This attack can be prevented by ensuring that the media recipient
>    intends to receive the media packets.  As such all CLUE-capable
>    devices MUST support key negotiation and receiver intent assurance
>    via DTLS-SRTP [RFC5763] on CLUE-controlled RTP "m=" lines.  All CLUE-
>    controlled RTP "m" lines must be secured and implemented using
>    mechanisms such as SRTP [RFC3711].  CLUE implementations MAY choose
>    not to require the use of SRTP to secure legacy (non-CLUE-controlled)
>    media for backwards compatibility with older SIP clients that are
>    incapable of supporting it.
>
> https://datatracker.ietf.org/doc/draft-ietf-clue-signaling/?include_text=1


Yes, but the problem is that this doesn't require any kind of consent
validation at all, which creates an unacceptable amplification risk.

It seems to me that there are a number of options here:

1. Require DTLS-SRTP
2. Require ICE
3. Require *some* path-validating consent mechanism

However, just leaving the amplification attack does not seem OK.

-Ekr


>
> All drafts have always had an exception for non-CLUE-controlled lines for
> backwards compatibility.
>
> Rob
>
> -----Original Message-----
> From: Paul Kyzivat <pkyzivat@alum.mit.edu>
> Sent: 26 November 2018 19:49
> To: Eric Rescorla <ekr@rtfm.com>
> Cc: Roni Even <roni.even@huawei.com>; IESG <iesg@ietf.org>; Daniel
> Burnett <danielcburnett@gmail.com>; clue@ietf.org;
> roni.even@mail01.huawei.com; clue-chairs@ietf.org;
> draft-ietf-clue-signaling@ietf.org
> Subject: Re: Eric Rescorla's No Objection on draft-ietf-clue-signaling-14:
> (with COMMENT)
>
> On 11/25/18 2:29 PM, Eric Rescorla wrote:
> >
> >
> > On Sun, Nov 25, 2018 at 9:35 AM Paul Kyzivat <pkyzivat@alum.mit.edu
> > <mailto:pkyzivat@alum.mit.edu>> wrote:
> >
> >     On 11/25/18 8:14 AM, Eric Rescorla wrote:
> >      >
> >      >
> >      > On Sat, Nov 24, 2018 at 9:41 PM Roni Even (A)
> >     <roni.even@huawei.com <mailto:roni.even@huawei.com>
> >      > <mailto:roni.even@huawei.com <mailto:roni.even@huawei.com>>>
> wrote:
> >      >
> >      >     Hi,____
> >      >
> >      >     The point that is made that in general CLUE is similar to no
> CLUE
> >      >     RTP media calls. The difference is that since the EP may open
> >     more
> >      >     than one RTP video channel there is a greater risk of sending
> >     more
> >      >     media to the victim.
> >      >
> >      >
> >      > Yes, but in order to have a useful countermeasure, that needs to
> be
> >      > mandatory, and yours is not.
> >
> >     But one of the goals of clue is to be backward compatible with
> regular
> >     sip calls. If we impose constraints on the media over and above those
> >     required for regular sip calls then we lose that.
> >
> >
> > ISTM that that's already not true for these media flows, because 4.4.1
> > requires them to be inactive and you need to use an SCTP/DTLS control
> > channel to negotiate them.
> > What I'm saying is that those other flows should also have a consent
> > check
>
> I was more concerned with the basic audio and/or video in the initial
> invite, before it is known whether the answerer supports clue. I don't have
> a particular problem with putting further restrictions on the clue
> controlled media.
>
>         Thanks,
>         Paul
>

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

<div dir=3D"ltr"><br><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue=
, Nov 27, 2018 at 1:55 AM Rob Hanton (rohanse2) &lt;<a href=3D"mailto:rohan=
se2@cisco.com">rohanse2@cisco.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">We did have specific protections as mandantory to use in earl=
ier drafts. From version 05:<br>
<br>
=C2=A0 =C2=A0... discussion of video hammer attack ...<br>
=C2=A0 =C2=A0This attack can be prevented by ensuring that the media recipi=
ent<br>
=C2=A0 =C2=A0intends to receive the media packets.=C2=A0 Because of the way=
 that CLUE<br>
=C2=A0 =C2=A0can increase the severity of this attack, as well as because o=
f the<br>
=C2=A0 =C2=A0general increased awareness of the need to secure critical pay=
loads,<br>
=C2=A0 =C2=A0a CLUE-capable device MUST secure all CLUE-controlled RTP &quo=
t;m&quot; lines<br>
=C2=A0 =C2=A0using SRTP [RFC3711], and MUST support and use key negotiation=
 and<br>
=C2=A0 =C2=A0receiver intent assurance via DTLS [RFC5763] on these &quot;m&=
quot; lines.=C2=A0 For<br>
=C2=A0 =C2=A0backwards compatibility, this is not a mandatory requirement f=
or non-<br>
=C2=A0 =C2=A0CLUE-controlled &quot;m&quot; lines.<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-clue-signaling/05/?i=
nclude_text=3D1" rel=3D"noreferrer" target=3D"_blank">https://datatracker.i=
etf.org/doc/draft-ietf-clue-signaling/05/?include_text=3D1</a><br>
<br>
This was then changed in version 06 and onwards following the discussion at=
 IETF 92 and later where there was opposition to making the use of DTLS/SRT=
P mandatory to use. If I recall the two major concerns people had were:<br>
1) This prevents implementations using a superior mechanism should one be d=
eveloped<br></blockquote><div><br></div><div>I don&#39;t think this is a re=
al objection, If a new mechanism should be developed, then presumably it wo=
uld also be documented in an RFC and we could update this one.<br></div><di=
v> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
2) This prevents two devices from the same vendor using some alternate mean=
s of authentication (potentially proprietary) that would reduce the need fo=
r DTLS/SRTP<br>
(Minutes: <a href=3D"https://datatracker.ietf.org/doc/minutes-92-clue/" rel=
=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/minutes-=
92-clue/</a> )<br></blockquote><div><br></div><div>It&#39;s not a matter of=
 authentication. It&#39;s a matter of path validation. For instance, if you=
 were to have a situation where you had a cryptographic key but it did not =
have an interactive handshake, that would not provide the correct function.=
 By contrast, ICE would.</div><div><br></div><div><br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
So while everyone agreed that DTLS/SRTP should be mandatory to implement so=
 it was always available, consensus ended up being removing the requirement=
 to use DTLS/SRTP and instead having more generic language:<br>
<br>
=C2=A0 =C2=A0This attack can be prevented by ensuring that the media recipi=
ent<br>
=C2=A0 =C2=A0intends to receive the media packets.=C2=A0 As such all CLUE-c=
apable<br>
=C2=A0 =C2=A0devices MUST support key negotiation and receiver intent assur=
ance<br>
=C2=A0 =C2=A0via DTLS-SRTP [RFC5763] on CLUE-controlled RTP &quot;m=3D&quot=
; lines.=C2=A0 All CLUE-<br>
=C2=A0 =C2=A0controlled RTP &quot;m&quot; lines must be secured and impleme=
nted using<br>
=C2=A0 =C2=A0mechanisms such as SRTP [RFC3711].=C2=A0 CLUE implementations =
MAY choose<br>
=C2=A0 =C2=A0not to require the use of SRTP to secure legacy (non-CLUE-cont=
rolled)<br>
=C2=A0 =C2=A0media for backwards compatibility with older SIP clients that =
are<br>
=C2=A0 =C2=A0incapable of supporting it.<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-clue-signaling/?incl=
ude_text=3D1" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf=
.org/doc/draft-ietf-clue-signaling/?include_text=3D1</a></blockquote><div><=
br></div><div>Yes, but the problem is that this doesn&#39;t require any kin=
d of consent validation at all, which creates an unacceptable amplification=
 risk.</div><div><br></div><div>It seems to me that there are a number of o=
ptions here:</div><div><br></div><div>1. Require DTLS-SRTP</div><div>2. Req=
uire ICE</div><div>3. Require *some* path-validating consent mechanism</div=
><div><br></div><div>However, just leaving the amplification attack does no=
t seem OK.<br></div><div><br></div><div>-Ekr</div><div><br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><br>
<br>
All drafts have always had an exception for non-CLUE-controlled lines for b=
ackwards compatibility.<br>
<br>
Rob<br>
<br>
-----Original Message-----<br>
From: Paul Kyzivat &lt;<a href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_=
blank">pkyzivat@alum.mit.edu</a>&gt; <br>
Sent: 26 November 2018 19:49<br>
To: Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr=
@rtfm.com</a>&gt;<br>
Cc: Roni Even &lt;<a href=3D"mailto:roni.even@huawei.com" target=3D"_blank"=
>roni.even@huawei.com</a>&gt;; IESG &lt;<a href=3D"mailto:iesg@ietf.org" ta=
rget=3D"_blank">iesg@ietf.org</a>&gt;; Daniel Burnett &lt;<a href=3D"mailto=
:danielcburnett@gmail.com" target=3D"_blank">danielcburnett@gmail.com</a>&g=
t;; <a href=3D"mailto:clue@ietf.org" target=3D"_blank">clue@ietf.org</a>; <=
a href=3D"mailto:roni.even@mail01.huawei.com" target=3D"_blank">roni.even@m=
ail01.huawei.com</a>; <a href=3D"mailto:clue-chairs@ietf.org" target=3D"_bl=
ank">clue-chairs@ietf.org</a>; <a href=3D"mailto:draft-ietf-clue-signaling@=
ietf.org" target=3D"_blank">draft-ietf-clue-signaling@ietf.org</a><br>
Subject: Re: Eric Rescorla&#39;s No Objection on draft-ietf-clue-signaling-=
14: (with COMMENT)<br>
<br>
On 11/25/18 2:29 PM, Eric Rescorla wrote:<br>
&gt; <br>
&gt; <br>
&gt; On Sun, Nov 25, 2018 at 9:35 AM Paul Kyzivat &lt;<a href=3D"mailto:pky=
zivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.edu</a> <br>
&gt; &lt;mailto:<a href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">=
pkyzivat@alum.mit.edu</a>&gt;&gt; wrote:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0On 11/25/18 8:14 AM, Eric Rescorla wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt; On Sat, Nov 24, 2018 at 9:41 PM Roni Even (A)=
<br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"mailto:roni.even@huawei.com" target=
=3D"_blank">roni.even@huawei.com</a> &lt;mailto:<a href=3D"mailto:roni.even=
@huawei.com" target=3D"_blank">roni.even@huawei.com</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt; &lt;mailto:<a href=3D"mailto:roni.even@huawei=
.com" target=3D"_blank">roni.even@huawei.com</a> &lt;mailto:<a href=3D"mail=
to:roni.even@huawei.com" target=3D"_blank">roni.even@huawei.com</a>&gt;&gt;=
&gt; wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0Hi,____<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0The point that is made tha=
t in general CLUE is similar to no CLUE<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0RTP media calls. The diffe=
rence is that since the EP may open<br>
&gt;=C2=A0 =C2=A0 =C2=A0more<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0than one RTP video channel=
 there is a greater risk of sending<br>
&gt;=C2=A0 =C2=A0 =C2=A0more<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0media to the victim.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt; Yes, but in order to have a useful countermea=
sure, that needs to be<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt; mandatory, and yours is not.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0But one of the goals of clue is to be backward comp=
atible with regular<br>
&gt;=C2=A0 =C2=A0 =C2=A0sip calls. If we impose constraints on the media ov=
er and above those<br>
&gt;=C2=A0 =C2=A0 =C2=A0required for regular sip calls then we lose that.<b=
r>
&gt; <br>
&gt; <br>
&gt; ISTM that that&#39;s already not true for these media flows, because 4=
.4.1 <br>
&gt; requires them to be inactive and you need to use an SCTP/DTLS control =
<br>
&gt; channel to negotiate them.<br>
&gt; What I&#39;m saying is that those other flows should also have a conse=
nt <br>
&gt; check<br>
<br>
I was more concerned with the basic audio and/or video in the initial invit=
e, before it is known whether the answerer supports clue. I don&#39;t have =
a particular problem with putting further restrictions on the clue controll=
ed media.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Thanks,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Paul<br>
</blockquote></div></div>

--000000000000a60aca057ba6ded6--

