
From nobody Tue Jan  4 16:07:02 2022
Return-Path: <martin.h.duke@gmail.com>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E7523A215E; Tue,  4 Jan 2022 16:06:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AcAbK1QfjooG; Tue,  4 Jan 2022 16:06:54 -0800 (PST)
Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) (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 8BBC73A215C; Tue,  4 Jan 2022 16:06:54 -0800 (PST)
Received: by mail-ua1-x931.google.com with SMTP id y4so9287935uad.1; Tue, 04 Jan 2022 16:06:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qsGNwlNZ7ispLP8AImfowIA36m7ZtVyVwv9K7DNQKcM=; b=XjJi8tuTnghAEpUQWa0OFk1NqVDAvjLkbCc9L7E6Yw5yHXBkr7bvOxu+IwAWtvH9IL gbBz9bGzoFBWV2VCjUaPukWUyzbrAkzI3wcNEQBlFqnCp1rUT6GKq91SBwXi368K6KIU kONIVTgBg8U/8gmM9dYr1Je+pFYpQzYKr6fZLZWd45J+5jisYxG7i72Bq4LDXddJhlLT U4VsX2gyR/YW/gjAIfJd5uS5QFJ7zYCYAvDqTfW41idj02Ia3/Enzw4SsqlhtTDIiuMH xfJoRl9WlJxn/h5QC6WUM0ED/TRle54bV7zG4FWJXd8mFZ1nVbItQ4gqxMaoavli3L37 XwHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qsGNwlNZ7ispLP8AImfowIA36m7ZtVyVwv9K7DNQKcM=; b=zWNUqDTo+DT26L55ehqW5TWq0yIrXErTmnYkpxQNL4BoEgpXa7nvQ3U196Xyed7O1l HRKRjIV2sPqIUUV1FfwNLoDx/I8sil+aGtq5pQ8WN9pZ+NW4PnhwHlN4+VGOZv7V5D9n tp3HSfrLNmXT9d8y8H/LlLpefBfzGzOrw+xBB+CIYDCwWIIpG3rKh4ViPqDyfbBLbtuG YvmDpJC7Jwx8X8k0rX7EwTHTPb9LtkDcndqdijzmkoUk4eJ9LzoRy81+o3lOktPpP1AD nkkjcAd2oySddgbi98fvlyZ2eQr2Rlbug2AOpSoyp50+YoWRtzzPCA5YcHI5SnkhipS6 x/ig==
X-Gm-Message-State: AOAM530MfpMG4vdAXmyRUDDq82Pw5T1MAoO0qkyUSTalX1qnexDM48cS sKqra+NBwnYAy+1AWopCj/kjJrQ+UPuKBCe9e8w=
X-Google-Smtp-Source: ABdhPJwoUKVRmsxe3MPF/pHhXDoxWKzUn9Zn2bqO0nr4EQCYDP+b8eLfCT8EfhGNbZnJtM/kfgrQsXyDF/1ylQFUjdc=
X-Received: by 2002:a67:e003:: with SMTP id c3mr16673345vsl.32.1641341212269;  Tue, 04 Jan 2022 16:06:52 -0800 (PST)
MIME-Version: 1.0
References: <163890001133.3603.6708235729467005454@ietfa.amsl.com> <47D5FC0F-129A-4227-8280-5DDC2D486BFB@brianrosen.net>
In-Reply-To: <47D5FC0F-129A-4227-8280-5DDC2D486BFB@brianrosen.net>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 4 Jan 2022 16:06:40 -0800
Message-ID: <CAM4esxQ_rP_OMf7OoN4jZYxgvOS+7dtMTCCPk=UaO6La0b2mAA@mail.gmail.com>
To: Brian Rosen <br@brianrosen.net>
Cc: The IESG <iesg@ietf.org>, draft-ietf-rum-rue@ietf.org, rum-chairs@ietf.org, rum@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary="000000000000e9a23005d4ca8731"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/MUXGRPcG7YYvg-eBgIMUVJbz0m0>
Subject: Re: [Rum] Martin Duke's Discuss on draft-ietf-rum-rue-09: (with DISCUSS and COMMENT)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2022 00:07:00 -0000

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

Hi Brian,

Thanks for clearing things up! Replies inline.

Besides the already-proposed changes, the main action item is my scope
followup question to #3.

On Thu, Dec 23, 2021 at 12:14 PM Brian Rosen <br@brianrosen.net> wrote:

> Thank you for your comments.  Please see inline
>
> On Dec 7, 2021, at 1:00 PM, Martin Duke via Datatracker <noreply@ietf.org=
>
> wrote:
>
> Martin Duke has entered the following ballot position for
> draft-ietf-rum-rue-09: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/blog/handling-iesg-ballot-positions/
> for more information about how to handle DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-rum-rue/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Thanks to Bernard Adoba for the TSVART review. It largely informs my
> DISCUSS.
>
> 1. If I understand correctly, this draft is not at all about interoperati=
ng
> with a WebRTC endpoint, instead borrowing some requirements from that
> family of
> specs rather than re-inventing the wheel. That's great, but putting that
> explicitly in the intro would be helpful.
>
> Not quite.  I propose the following additional information in the media
> section where WebRTC specs are discussed:
> To use WebRTC with this document, a gateway that presents a WebRTC server
> interface towards a browser, and a RUE client interface towards a provide=
r
> is assumed.  The gateway would interwork signaling, and as noted below,
> interwork at least any real time text media, in order to allow a standard
> browser baed WebRTC client to be a VRS client.  The combination of the
> browser client and the gateway would be a RUE user.
>
> 2. In particular, the statement that RUE is a "non-browser endpoint" is
> confusing if it's not actually meant to interoperate with WebRTC. I *thin=
k*
> you're attempting to distinguish between WebRTC's browser-only
> requirements and
> endpoint requirements, but I could be wrong here.
>
> See above, but I still may have to just remove that =E2=80=9Cnon browser =
endpoint=E2=80=9D
> text, because it=E2=80=99s confusing people.
>
>
OK, I look forward to seeing the new text.

>
> 3. In Section 5.5, you require conformance with RFC8835 with a few vaguel=
y
> worded exceptions. It would be helpful to actually go through that docume=
nt
> enumerate exactly which normative statements in 8835 do not apply. That
> said,
> I'm not sure I agree with Bernard that 8835 requires *use* of ICE, rather
> than
> support, but maybe we can clarify this in the TSVART thread.
>
> The only reference to 8835 reads:
> Implementations MUST conform to [RFC8835] except for its guidance on the
> WebRTC data channel, which this specification does not use.
>
> I have looked carefully at all mentions of =E2=80=9Cdata channel=E2=80=9D=
 in 8835 and it
> seems really obvious what does and doesn=E2=80=99t apply.  Here is an exa=
mple:
>
>    For data transport over the WebRTC data channel [RFC8831 <https://data=
tracker.ietf.org/doc/html/rfc8831>], WebRTC
>    endpoints MUST support SCTP over DTLS over ICE.  This encapsulation
>    is specified in [RFC8261 <https://datatracker.ietf.org/doc/html/rfc826=
1>].  Negotiation of this transport in the
>    Session Description Protocol (SDP) is defined in [RFC8841 <https://dat=
atracker.ietf.org/doc/html/rfc8841>].  The SCTP
>    extension for I-DATA [RFC8260 <https://datatracker.ietf.org/doc/html/r=
fc8260>] MUST be supported.
>
>    The setup protocol for WebRTC data channels described in [RFC8832 <htt=
ps://datatracker.ietf.org/doc/html/rfc8832>]
>    MUST be supported.
>
>
> None of it applies.  It might not be quite as obvious that because the
> above doesn=E2=80=99t apply, there is no SCTP requirement, but do you thi=
nk we need
> to say that, given that the only discussion of SCTP is in relation to the
> data channel?
> I could call out each one of the data channel statements, but it really
> does seem superfluous.
>

The scope of this isn't clear to me. I would imagine the WebRTC end of the
gateway *does* support the webRTC data channel standards, yes? So the
gateway that you specify in this document is translating the WebRTC data
channel into the Section 6.2 data channel.

Aside from the scoping question,  I'm struggling to find economical
alternative wording that makes it clearer. So I'm OK with keeping the 8835
"data channel" exception.


>
> 4. As Bernard points out, this ambiguity extends to IPv4 and 6 support. T=
he
> 8835 requirements are specific to browsers, so they might not apply. If y=
ou
> require support for both, but not necessarily on the same device, it woul=
d
> be
> good to say so.
>
>
> We require support for IPv4 and IPv6 expressly.  We say:
> Implementations MUST support IPv4 and IPv6.  Dual stack support is NOT
> required and provider implementations MAY support separate interfaces for
> IPv4 and IPv6 by having more than one server in the appropriate SRV recor=
d
> where there is either an A or AAAA record in each server DNS record but n=
ot
> both.  The same version of IP MUST be used for both signaling and media o=
f
> a call unless ICE [RFC8445] is used, in which case candidates may
> explicitly offer IPv4, IPv6 or both for any media stream.
>
> If there is any conflict between that and 8835, I don=E2=80=99t see it.
>

Sorry I missed that text somehow!

>
> 5. In Sec. 6, it says "This specification adopts the media specifications
> for
> WebRTC ([RFC8825])." Is this a normative statement? Must RUEs comply with
> the
> entirety of that document, or is this an informative statement and the re=
al
> requirements are in the subsections of Sec 6? From the discussion, it
> sounds
> like you want to include the requirements for WebRTC "endpoints", but not
> for
> WebRTC "browsers". It would help to clarify all this.
>
> We=E2=80=99re not requiring anything normative from 8825 I think.  Only t=
he parts
> we expressly state. I could add: =E2=80=9Cexplicit requirements from the =
WebRTC
> suite of documents are described below=E2=80=9D.
>

I think that would improve clarity.

>
> It's also possible that my initial understanding is incorrect, in which
> case
> the later points don't make any sense and some explanatory text is needed=
.
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thanks for your work to make the internet more accessible for all.
>
>
>
>
>

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

<div dir=3D"ltr"><div>Hi Brian,</div><div><br></div><div>Thanks for clearin=
g things up! Replies inline.</div><div><br></div><div>Besides the already-p=
roposed changes, the main action item is my scope followup question to #3.<=
/div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Thu, Dec 23, 2021 at 12:14 PM Brian Rosen &lt;<a href=3D"mailto:br@brianr=
osen.net">br@brianrosen.net</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div style=3D"overflow-wrap: break-word;">Thank =
you for your comments.=C2=A0 Please see inline<br><div><br><blockquote type=
=3D"cite"><div>On Dec 7, 2021, at 1:00 PM, Martin Duke via Datatracker &lt;=
<a href=3D"mailto:noreply@ietf.org" target=3D"_blank">noreply@ietf.org</a>&=
gt; wrote:</div><br><div><div>Martin Duke has entered the following ballot =
position for<br>draft-ietf-rum-rue-09: Discuss<br><br>When responding, plea=
se keep the subject line intact and reply to all<br>email addresses include=
d in the To and CC lines. (Feel free to cut this<br>introductory paragraph,=
 however.)<br><br><br>Please refer to <a href=3D"https://www.ietf.org/blog/=
handling-iesg-ballot-positions/" target=3D"_blank">https://www.ietf.org/blo=
g/handling-iesg-ballot-positions/</a><br>for more information about how to =
handle DISCUSS and COMMENT positions.<br><br><br>The document, along with o=
ther ballot positions, can be found here:<br><a href=3D"https://datatracker=
.ietf.org/doc/draft-ietf-rum-rue/" target=3D"_blank">https://datatracker.ie=
tf.org/doc/draft-ietf-rum-rue/</a><br><br><br><br>-------------------------=
---------------------------------------------<br>DISCUSS:<br>--------------=
--------------------------------------------------------<br><br>Thanks to B=
ernard Adoba for the TSVART review. It largely informs my DISCUSS.<br><br>1=
. If I understand correctly, this draft is not at all about interoperating<=
br>with a WebRTC endpoint, instead borrowing some requirements from that fa=
mily of<br>specs rather than re-inventing the wheel. That&#39;s great, but =
putting that<br>explicitly in the intro would be helpful.<br></div></div></=
blockquote>Not quite.=C2=A0 I propose the following additional information =
in the media section where WebRTC specs are discussed:</div><div>To use Web=
RTC with this document, a gateway that presents a WebRTC server interface t=
owards a browser, and a RUE client interface towards a provider is assumed.=
=C2=A0=C2=A0The gateway would interwork=C2=A0signaling, and as noted below,=
 interwork at least any real time text media, in order to allow a standard =
browser baed WebRTC client to be a VRS client.=C2=A0=C2=A0The combination o=
f the browser client=C2=A0and the gateway would be a RUE user.<br><blockquo=
te type=3D"cite"><div><div>2. In particular, the statement that RUE is a &q=
uot;non-browser endpoint&quot; is<br>confusing if it&#39;s not actually mea=
nt to interoperate with WebRTC. I *think*<br>you&#39;re attempting to disti=
nguish between WebRTC&#39;s browser-only requirements and<br>endpoint requi=
rements, but I could be wrong here.<br></div></div></blockquote>See above, =
but I still may have to just remove that =E2=80=9Cnon browser endpoint=E2=
=80=9D text, because it=E2=80=99s confusing people.</div><div><br></div></d=
iv></blockquote><div><br></div><div>OK, I look forward to seeing the new te=
xt.=C2=A0=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 style=3D"overflow-wrap: break-word;"><div><blockquote type=3D"cite"><div><=
div><br>3. In Section 5.5, you require conformance with RFC8835 with a few =
vaguely<br>worded exceptions. It would be helpful to actually go through th=
at document<br>enumerate exactly which normative statements in 8835 do not =
apply. That said,<br>I&#39;m not sure I agree with Bernard that 8835 requir=
es *use* of ICE, rather than<br>support, but maybe we can clarify this in t=
he TSVART thread.<br></div></div></blockquote>The only reference to 8835 re=
ads:</div><div>Implementations MUST conform to [RFC8835]=C2=A0except for it=
s guidance on the WebRTC data channel, which this specification does not us=
e.=C2=A0</div><div><br></div><div>I have looked carefully at all mentions o=
f =E2=80=9Cdata channel=E2=80=9D in 8835 and it seems really obvious what d=
oes and doesn=E2=80=99t apply.=C2=A0 Here is an example:</div><div><br></di=
v><div><pre style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;f=
ont-variant-ligatures:normal">   For data transport over the WebRTC data ch=
annel [<a href=3D"https://datatracker.ietf.org/doc/html/rfc8831" title=3D"&=
quot;WebRTC Data Channels&quot;" target=3D"_blank">RFC8831</a>], WebRTC
   endpoints MUST support SCTP over DTLS over ICE.  This encapsulation
   is specified in [<a href=3D"https://datatracker.ietf.org/doc/html/rfc826=
1" title=3D"&quot;Datagram Transport Layer Security (DTLS) Encapsulation of=
 SCTP Packets&quot;" target=3D"_blank">RFC8261</a>].  Negotiation of this t=
ransport in the
   Session Description Protocol (SDP) is defined in [<a href=3D"https://dat=
atracker.ietf.org/doc/html/rfc8841" title=3D"&quot;Session Description Prot=
ocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol=
 (SCTP) over Datagram Transport Layer Security (DTLS) Transport&quot;" targ=
et=3D"_blank">RFC8841</a>].  The SCTP
   extension for I-DATA [<a href=3D"https://datatracker.ietf.org/doc/html/r=
fc8260" title=3D"&quot;Stream Schedulers and User Message Interleaving for =
the Stream Control Transmission Protocol&quot;" target=3D"_blank">RFC8260</=
a>] MUST be supported.

   The setup protocol for WebRTC data channels described in [<a href=3D"htt=
ps://datatracker.ietf.org/doc/html/rfc8832" title=3D"&quot;WebRTC Data Chan=
nel Establishment Protocol&quot;" target=3D"_blank">RFC8832</a>]
   MUST be supported.
</pre><div><br></div></div><div>None of it applies.=C2=A0 It might not be q=
uite as obvious that because the above doesn=E2=80=99t apply, there is no S=
CTP requirement, but do you think we need to say that, given that the only =
discussion of SCTP is in relation to the data channel?</div><div>I could ca=
ll out each one of the data channel statements, but it really does seem sup=
erfluous.<br></div></div></blockquote><div><br></div><div>The scope of this=
 isn&#39;t clear to me. I would imagine the WebRTC end of the gateway *does=
* support the webRTC data channel standards, yes? So the gateway that you s=
pecify in this document is translating the WebRTC data channel into the Sec=
tion 6.2 data channel.</div><div><br></div><div>Aside from the scoping ques=
tion,=C2=A0 I&#39;m struggling to find economical alternative wording that =
makes it clearer. So I&#39;m OK with keeping the 8835 &quot;data channel&qu=
ot; exception.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div style=3D"overflow-wrap: break-word;"><div><blockquote type=
=3D"cite"><div><div><br>4. As Bernard points out, this ambiguity extends to=
 IPv4 and 6 support. The<br>8835 requirements are specific to browsers, so =
they might not apply. If you<br>require support for both, but not necessari=
ly on the same device, it would be<br>good to say so.<br></div></div></bloc=
kquote><div><br></div>We require support for IPv4 and IPv6 expressly.=C2=A0=
 We say:</div><div>Implementations MUST support IPv4 and IPv6.=C2=A0=C2=A0D=
ual stack support is NOT required and provider implementations MAY support =
separate interfaces for IPv4 and IPv6 by having more than one server in=C2=
=A0the appropriate SRV record where there is either an A or AAAA record in =
each server DNS record but not both.=C2=A0=C2=A0The same version of IP MUST=
 be used for both signaling and media of a call unless=C2=A0ICE [RFC8445]=
=C2=A0is used, in which case candidates may explicitly offer IPv4, IPv6 or =
both for any media stream.=C2=A0</div><div><br></div><div>If there is any c=
onflict between that and 8835, I don=E2=80=99t see it.</div></div></blockqu=
ote><div><br></div><div>Sorry I missed that text somehow!=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div style=3D"overflow-wrap: br=
eak-word;"><div><br><blockquote type=3D"cite"><div><div>5. In Sec. 6, it sa=
ys &quot;This specification adopts the media specifications for<br>WebRTC (=
[RFC8825]).&quot; Is this a normative statement? Must RUEs comply with the<=
br>entirety of that document, or is this an informative statement and the r=
eal<br>requirements are in the subsections of Sec 6? From the discussion, i=
t sounds<br>like you want to include the requirements for WebRTC &quot;endp=
oints&quot;, but not for<br>WebRTC &quot;browsers&quot;. It would help to c=
larify all this.<br></div></div></blockquote>We=E2=80=99re not requiring an=
ything normative from 8825 I think.=C2=A0 Only the parts we expressly state=
. I could add: =E2=80=9Cexplicit requirements from the WebRTC suite of docu=
ments are described below=E2=80=9D.<br></div></div></blockquote><div><br></=
div><div>I think that would improve clarity.=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div style=3D"overflow-wrap: break-word;">=
<div><blockquote type=3D"cite"><div><div><br>It&#39;s also possible that my=
 initial understanding is incorrect, in which case<br>the later points don&=
#39;t make any sense and some explanatory text is needed.<br><br><br>------=
----------------------------------------------------------------<br>COMMENT=
:<br>----------------------------------------------------------------------=
<br><br>Thanks for your work to make the internet more accessible for all.<=
br><br><br><br></div></div></blockquote></div><br></div></blockquote></div>=
</div>

--000000000000e9a23005d4ca8731--


From nobody Mon Jan 10 04:24:38 2022
Return-Path: <evyncke@cisco.com>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A1C73A077D; Mon, 10 Jan 2022 04:24:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.596
X-Spam-Level: 
X-Spam-Status: No, score=-9.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=WqA5mYsN; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=dozcWrii
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 JlMbEYzyUfEE; Mon, 10 Jan 2022 04:24:26 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 310D03A0776; Mon, 10 Jan 2022 04:24:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4842; q=dns/txt; s=iport; t=1641817466; x=1643027066; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=924+83B+0nCGU3D2kY2u/OaPJJ0Wg1YSpqGGuMFCUso=; b=WqA5mYsN8SIWBBlo508iP/Wuywy2wCpkF/6KBrO+14JYuMxGXoJ5NBjQ kkk5Tq0Zl71qJ40u46QFZYARQ1jjokMxRh8E83aAjZULT5HkizKECq5Yw 90cO7UL7PkyuUCXwmS2V1EYDzOMwKuUBiAnC79zKX5KHG0pSWbQF8F8WU w=;
IronPort-PHdr: =?us-ascii?q?A9a23=3A/B4+MxOJtjYLM69yp0cl6ncDWUAX0o4cdiYZ6?= =?us-ascii?q?Zsi3rRJdKnrv5HvJ1fW6vgliljVFZ7a5PRJh6uz0ejgVGUM7IzHvCUEd5pBB?= =?us-ascii?q?BMAgN8dygonBsPNAEbnLfnsOio9GskKVFJs83yhd0ZPH8OrbFzJqXr05jkXS?= =?us-ascii?q?X3C?=
IronPort-Data: =?us-ascii?q?A9a23=3Avln0YKkZHHkZePMPWE5FEVzo5gx7JERdPkR7X?= =?us-ascii?q?Q2eYbSJt1+Wr1GztxJJDWrUMq2KN2H0Kd5ybtu+oRlXucfQzNBqTQFuqHoyH?= =?us-ascii?q?ltH+JHPbTi7wugcHM8zwvUuxyuL1u1GAjX7BJ1yHi+0SiuFaOC79yEljPnQH?= =?us-ascii?q?NIQNcadUsxPbV48IMseoUoLd94R2uaEsPDha++/kYqaT/73YDdJ7wVJ3lc8s?= =?us-ascii?q?Mpvnv/AUMPa41v0tnRmDRxCUcS3e3M9VPrzLonpR5f0rxU9IwK0ewrD5OnRE?= =?us-ascii?q?mLx5RwhDJaulaz2NxFMSb/JNg/IgX1TM0SgqkEd/WppjeBqb7xFNBo/Zzahx?= =?us-ascii?q?7idzP1Aq422QgQkFqbNg+8aFRJfFkmSOIUXpuGbcCfl4Jb7I0ruNiGEL+9VJ?= =?us-ascii?q?Fk1LJ8Z5O9rKWhK6PleLTERKB2Pmoqe2q++YuhhmsplK9PkVKsFp3QlxjHQD?= =?us-ascii?q?Ow9aZHOX6uM4sVXtB88nMlAAbPfatYXLCByaVHafhBnO1oLBtQ5hujArnjya?= =?us-ascii?q?DJwqV+Jq+ww+We75AZr+LL3MdPTYNuRSMMTmEuEzl8qVUyR7goyLteTz3+O9?= =?us-ascii?q?Wihw7OJliLgU4VUH7q9nsOGSWa7ngQ7YCD6n3PhyRVhtnODZg=3D=3D?=
IronPort-HdrOrdr: =?us-ascii?q?A9a23=3Aly07Z6/63aqKecpb++luk+GIdr1zdoMgy1?= =?us-ascii?q?knxilNoENuE/BwxvrBoB1E73DJYW4qKQ4dcdDpAtjmfZtFnaQFobX5To3SIj?= =?us-ascii?q?UO31HYb72KjLGSggEIfhefygcz79YaT0ETMqyUMbE+t7eH3ODaKadj/DDkyt?= =?us-ascii?q?HTuQ629R4EJmsGB9ACnmVE40SgYzBLrWJ9dPwE/e+nl7J6Tk2bCA0qh6qAdx?= =?us-ascii?q?04dtmGg+eOuIPtYBYACRJiwhKJlymU5LnzFAXd9gsCUhtUqI1StFTtokjc3O?= =?us-ascii?q?GOovu7whjT2yv49JJNgubszdNFGYilltUVEDPxkQylDb4RH4Fq/QpF591H2m?= =?us-ascii?q?xayeUkkC1QZ/ibLEmhJV1dlCGdnTUIFgxesUMKh2Xo3EcL6vaJNQ7SQ/Ax9b?= =?us-ascii?q?6xNCGpt3bJeLpHofx2N6XzjesJMfqIplWO2zCDPSsa5XacsD4sl/UegGdYVp?= =?us-ascii?q?ZbYLhNrZYH9EcQC5sYGjnmgbpXXNWGIfusrsq+S2nqIkwxf1MftuCETzA2BF?= =?us-ascii?q?OLU0ICssua33xfm2141VIRwIgakm0b/JwwRpFY76CcW54Y2o1mX4sTd+ZwFe?= =?us-ascii?q?0BScy4BijERg/NKnubJRDiGLscM3zAppbr6PE+5f2sepYP0Jwu8a6xH29wpC?= =?us-ascii?q?o3YQbjGMeO1JpE/lTER3i8Ry3kzoVE651wqtTHNfHW2O24ORgTeueb0oEi6/?= =?us-ascii?q?zgKr+O0chtcorexEPVaPF04zE=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BCBgC1JNxh/5tdJa1aHgEBCxIMQIF?= =?us-ascii?q?OC4FSVQd3WjcxhEeDRwOFOYUOgwIDgSmPDIpqgS4UgREDVAsBAQENAQE1DAQ?= =?us-ascii?q?BAYUGAheDLQIlNAkOAQIEAQEBEgEBBQEBAQIBBgSBCROFaA2GQgEBAQECARI?= =?us-ascii?q?REQwBATcBDwIBCA4KAgImAgICMBUFCwIEDgUWDIJcAYJlAw0hAQ6fTwGBOgK?= =?us-ascii?q?KH3qBMYEBO4FNAQEGBASBSkGDABiCNgMGgRAqgw6EHoJahCwnHIFJRIEVJxy?= =?us-ascii?q?CZz6CYwIDgSgBCggBOIMBN4IukD8GZAQYChkICAgUGy4iDXYCDyAIAjoDkXU?= =?us-ascii?q?EgwdGqXwKg0KKeI5ghXQFLoNwjAmXcoVMkG6NA5QoGAKEaQIEAgQFAg4BAQY?= =?us-ascii?q?1gSw7aXBwFTsqAYI+URkPjiCDcYUUhUp0OAIGAQoBAQMJAYI6ii6CNQEB?=
X-IronPort-AV: E=Sophos;i="5.88,277,1635206400"; d="scan'208";a="966497292"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Jan 2022 12:24:24 +0000
Received: from mail.cisco.com (xbe-rcd-003.cisco.com [173.37.102.18]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 20ACOOqu021375 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Mon, 10 Jan 2022 12:24:24 GMT
Received: from xfe-rcd-004.cisco.com (173.37.227.252) by xbe-rcd-003.cisco.com (173.37.102.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.14; Mon, 10 Jan 2022 06:24:23 -0600
Received: from xfe-rtp-005.cisco.com (64.101.210.235) by xfe-rcd-004.cisco.com (173.37.227.252) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.14; Mon, 10 Jan 2022 06:24:23 -0600
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xfe-rtp-005.cisco.com (64.101.210.235) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.14 via Frontend Transport; Mon, 10 Jan 2022 07:24:23 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GfYvnIz5TnOfpTQ+PE2mw/YfWGzXtTOOEPx+RC9erV9dXK+S5/AuWNX7Gs7lOFt/AvuyDJoUcUS8Q8QHxm9+DGQc785197V3SRqxmpT1u3z77KnWO/D6GHdEAVCC1M3/S7XEivzFSOCej1HoMhI31ejrWYJ8iHFwU6gonKe2c9G1xGgp4r2If2f69V9Y9sGrogw5Zb3l7870zrHDjqritfWCmWU6ortBTP1dwmJOqYI+mVNq2VaFyY59Kwk1vQgK2d1AjAqfOwH8ovOOiKy14DX1lHydCaCEmxrSKzO5ixE6InZK2V5LaBTvRiZtKN7rFKxX42EsJe7AYyWgc40r7Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=924+83B+0nCGU3D2kY2u/OaPJJ0Wg1YSpqGGuMFCUso=; b=cK9p9ynZU2rJPq8bSGF4WDyIs3rqG/ly0m2C1D8G3U1mVi+2Fyr4OMHAIMKXiiCoQi91/Q9jVJn+NKZLgm8cIFLxgxZJcdgDGG0I535ASTzurGh9d/+ea2SnbUkyWBClqhoSAsrPg2CYLDE4ReOVWFqAK6lTvTu2Dk+2bt+jfW/annIZUKz2/TcB2DDk/wxTfiYWSUx3bwwS57cLOE70Ds2cYqvKILgQhfYMZlH1XES24YuYV86ocbr+AvmecSNGr6raTR0LH2s+SJliQxMdIjuGDzuxbFXOGawAzhIK9Tjqa8nY3l1rt0yt9znq3o4PWZI1SYHc7juBMoZARlQMMg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=924+83B+0nCGU3D2kY2u/OaPJJ0Wg1YSpqGGuMFCUso=; b=dozcWriiY2Rrdlxixw1SV+C7yYuV/sEGvRagjPPoKNH0fd9b7mzlisopx0UB3VHyXrsxGvOl8JBT3Bke3U9Xr3z9G0feP2p+9M3JPLPpZeO1JHq9FkDllbuY//xymbAInLxcVflucFJ1xr+5mGu0wyR5La+m7/wRHwsbdZ6pD7s=
Received: from PH0PR11MB4966.namprd11.prod.outlook.com (2603:10b6:510:42::21) by PH0PR11MB5112.namprd11.prod.outlook.com (2603:10b6:510:3b::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4867.9; Mon, 10 Jan 2022 12:24:22 +0000
Received: from PH0PR11MB4966.namprd11.prod.outlook.com ([fe80::143c:310d:4a0:ce8c]) by PH0PR11MB4966.namprd11.prod.outlook.com ([fe80::143c:310d:4a0:ce8c%3]) with mapi id 15.20.4867.012; Mon, 10 Jan 2022 12:24:22 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Brian Rosen <br@brianrosen.net>
CC: The IESG <iesg@ietf.org>, "draft-ietf-rum-rue@ietf.org" <draft-ietf-rum-rue@ietf.org>, "rum-chairs@ietf.org" <rum-chairs@ietf.org>, "rum@ietf.org" <rum@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: =?utf-8?B?w4lyaWMgVnluY2tlJ3MgTm8gT2JqZWN0aW9uIG9uIGRyYWZ0LWlldGYtcnVt?= =?utf-8?Q?-rue-09:_(with_COMMENT)?=
Thread-Index: AQHX+N8jwwCCRhHZhE+ZAzt5GeUQA6xcWQKA
Date: Mon, 10 Jan 2022 12:24:22 +0000
Message-ID: <0602D623-016D-49B3-9A55-A78FEE5C4A09@cisco.com>
References: <163965152396.13166.2829929578945414903@ietfa.amsl.com> <EB8151B7-C0D7-43D8-93C3-F877E01CEAF2@brianrosen.net>
In-Reply-To: <EB8151B7-C0D7-43D8-93C3-F877E01CEAF2@brianrosen.net>
Accept-Language: fr-BE, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.56.21121100
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=cisco.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 941008a6-4a2a-4972-6b2b-08d9d4342211
x-ms-traffictypediagnostic: PH0PR11MB5112:EE_
x-microsoft-antispam-prvs: <PH0PR11MB51122B35DCF24A6818E4B788A9509@PH0PR11MB5112.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Vk8TtO/KkZFvo4NfY9gdrcWt2wFaCBoRF1RQqIFpu2q5lJghJ8EiZrqq05K99+ArV6SSlNeztQJ9WhvWGIWkAPEUBZCYho4wKg4uoHCdmP1q4m24gLFqib7XCviWA9x4OMQuSKCRt70WKVZ8dDe7q0f9HJ9qOfBJ7i76p4G361Yki8CUcUMdzuJtxuptA1nYb66WzbZUGyc6GIQOnhJYTyNXPO8RI4ibvHrFtRSdzk/7rcKukO2R86JIwjqZkrpi5a0909b50IYdoENSnawZQzeXymoKFZWGLxVZR1jsbKvXfe0hPW6AJoXbSqbyIx1FKmSRr6+QhYcp80/cMA35izEuYjpvw4YZBspHZNl+uIIQC+kpzTNKTyZ+RTC782hUmt4b1T0pNRpBixB7NTgOM/L0g/+v85UnHX06oEcap1M/ior1jr6DSsxo7N6cdqt4QThvI/PMmqJOKGY8gbcYvqg7fq+IFVC94/wJnbbjF3F28sR2UPqvbQwpMszQeIrmO27l4rvGUsf14QoNS2r8K3E054FJYgkibraHOlMzo9ydPDQbjFFKUgfSa8vzMMxFd3QPrS90hG+yPoY77ZTlssuDGEa7Zv6ALOp9Z2LWV2pIKtzC9HEFH2or0LjnMYohjO1phZ9/m8SJ+9toAeoTqw1IlBBJg57V8WxYMcuEHj5W8ADe6GU5lI+x24IXziMfW6qoI3uw4bIgBakW/orNl0J7hybQoifeP+TI5fv00gr02K14UzOLGoP7vICMBj3juixjg4cSpBEkRxifMAvzo9ruq7jkCS3HmJn/e5MZESbkETGcXGzbFM36s0Q1Svt2CezgJdQLACwBN78gxJ6JoW4oGeJZhwGdMI+J/J4tV08=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:PH0PR11MB4966.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(366004)(6512007)(2906002)(66946007)(5660300002)(36756003)(66574015)(38070700005)(64756008)(508600001)(66556008)(66476007)(53546011)(71200400001)(4326008)(122000001)(54906003)(6486002)(2616005)(186003)(86362001)(6916009)(38100700002)(76116006)(91956017)(224303003)(66446008)(83380400001)(316002)(966005)(6506007)(8936002)(33656002)(45980500001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?utf-8?B?NExoN2dIV2NyQnZBU3ZTU3RkS0tBbFM3OFVLbkZ3cnRiSUFqSm5tWUN1dldp?= =?utf-8?B?bVV2dGpQQnU3UEVYZXZEOXV1VlkrZzc4SkozSWRoMk1iYVRTaWczdXRmZkd4?= =?utf-8?B?ZFFsSnFCQWF3clUrRFp0TzdLTnovd1RldjNJV3E1aFdNTGVqWTc4VWlIU2NU?= =?utf-8?B?YUlBenlkbzJkOThKWUFzRi90Y1ZONHRJVmxoaUhkQWQzSmlJdWRoSGFSUFh6?= =?utf-8?B?c1ZVTDVySjFBa0JQMmFMbFFYM08zV2RLdEpBR1dvQzIxOHFqTndHa0VIQ2FJ?= =?utf-8?B?N1FPKzhSaG5Ea3E5R2lCZFU3QmNpckV6aXM4a2ZrakFCMUxxbG5KMlhpNFhJ?= =?utf-8?B?d3Q2N0x3QVhvNUdiZSs2cWVkNE40SjN4ZEFQZlEwQXJxcGo3M0gzSm9BN3Y2?= =?utf-8?B?UGhYNjA0YlJoR2FNZTBUaXozSm4zZzVoRXZpYUVrb0cwSVN5a3ZOVEhxdkE1?= =?utf-8?B?SEREcjNQQzNpRGtrbmZJaXlRRU1pVHBEUkcwcmxBdFpVSTlEdElXTXNqblRk?= =?utf-8?B?alg3azMzeWJtMStyc0RzMXRHOTVLemZremJENEdIVHNreHJBei8vcGMxcDlq?= =?utf-8?B?Szh1bktHN3VtK1kzeGI3bVZtcFFRbFFzeis5VE1Qek96WXJtK2FXakN2eU9G?= =?utf-8?B?YW11cStNU25tQ09DMys5K1A1TmFaOFNrRVhhZmJjN0pUcy9lU0Q4dnhwcEY5?= =?utf-8?B?OXhUTTZuaUtCaHdDbkNPVDJNWENhWkRwa2U3RGZVSDhoQUQzbHdyTHl4T1U3?= =?utf-8?B?V2oyZHVQNTFVOXBRQm03eGlnaS9ZMmlSUEZEVCtpVk1LWUJ2VUVSaGpzTERX?= =?utf-8?B?Z1J4MkdmdnFTR3BMWThHUXhpZVp5K2VVVnV3L3MrU3VXQUNxRlZaend4aUta?= =?utf-8?B?S1RFOWkyMlZ5ZWxycXprbk9kejBQSzYxMmk1R2owbnd1Njd0U2pXNkp5bm9w?= =?utf-8?B?bnp4Q1hRUUk0WU9SSW5xR3g0UkZoVk14YzdHUXowR3pCd1g4U2t0TFlEYTJo?= =?utf-8?B?ekVXTFF1MVI4dnFBSS8rMU83V0t5Ni9vY1V5V2lxT1BJc2kvY1lBRDlhYWxI?= =?utf-8?B?Nnp4S2U2K2RidGdrK0lUQXBObDJTNG9WdVBtYlY1Qm9zSmtBeWZPcllvWFlG?= =?utf-8?B?eDc4U0JpUm9GQVJqZFp0VU9OTjVZWitLTXpaaU1ObUliVytlc3B2UU9lcE5s?= =?utf-8?B?ZWdDalJIaitvM04xeVgzZXkvZFZOWUVnZGpVcUZHWkxvR0VvVTJWYWZRdFl2?= =?utf-8?B?QTdnTnlqVm50UVo3b1ZiZ2IrUkJIS0NqVEdCRnZDOWdKSHpDYzBKVUFBcmtu?= =?utf-8?B?c29QL28wTEtFdWZNYStvbjlZNTM3OGhjL001dFFHT3pGQ3ZPU1RCaEtncTFq?= =?utf-8?B?d3piMG05UUJZd2xZREkrWUF6UWFnTlpBSkNjN3pUN2pnSVFyV25BWmszZkEv?= =?utf-8?B?UWFZV0NZaTdqQXJLbjJudjZpSjExVVN0YjRUa1BOY2ZWaG9nb1pqdDVkSGJB?= =?utf-8?B?RnVZSThlZlhvQzl5dlN0ZHZEUXFiajlBYTVwQmFGblk3NG8xTlJWU2hBeFRG?= =?utf-8?B?NHZHU3RIMzJFemR2ZU1JQTExZDh6VGVyQ05LaGVad1hhNkE0UWdqZnJ1eGFi?= =?utf-8?B?SlluR3ZzVGQ5S1NuOGYwSjlDRWhQZm0wekFoOEJDbVdsMVhJVnhxdjhvRXFu?= =?utf-8?B?U1c0UXdlR3dnUkJVS09kL1lGb2JVVHBIWEdkRVdxMHVISlhWWXBQU2NzYjd3?= =?utf-8?B?RDR0eExiVzRRWVRkZytPazBFTzJLdW9lK1RWbTB0T21vUUx1c2phUGJudktn?= =?utf-8?B?VHJWaUhRSzE1M3lCN2djYnY1UVhHVWlwK1NYMnVhZHpyaHpmRnJnalIxeUx3?= =?utf-8?B?ZjJlUllSYllCcnJRMmpHeDlqZEo2N0tjZkhRVFdWQTI4RGZPSExGaWlpbWxY?= =?utf-8?B?akxMc1Rzb1VoQmpTc09uRkNRTTg1WUxHT2JRTWwwT2IxZlc2QVJ1Um9wTGV2?= =?utf-8?B?M1NyWm9IbllqbWFHQVNKVExWalY2aGdPOGlINWtEUytRb21mZlpuTXNyaG9p?= =?utf-8?B?dmcrbmttMkxsV3NMRWp6c3Q3QjFYbXM2bkNjSEdXQzYwd2k2dmk4VEJha05m?= =?utf-8?B?cHFsQ214Nkk5OUtlanZSZVZPL1NTMk04MzNsWjIrVWtVSnE5WGl0Z3NZSHpm?= =?utf-8?B?RkF6VFlNdGNvQUlvNlBKTXQyREZzRlJxSi9mTG9MVEtxZkduaG1ZeHZPU0RY?= =?utf-8?Q?JUsKkJtlpAg9y00pPyybv1AsTUVLyo5/j0weVhNtlM=3D?=
Content-Type: text/plain; charset="utf-8"
Content-ID: <9234D059131AF4438D2EB20FEABEC3FC@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PH0PR11MB4966.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 941008a6-4a2a-4972-6b2b-08d9d4342211
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jan 2022 12:24:22.3027 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Hh5odw6ejmv6XQN3plRP226PWrRBguILiWkic7PhmZT630uSLag3Zbj8QTtyUw04RrWLOHOAqhreltwW8kncRQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH0PR11MB5112
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.18, xbe-rcd-003.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/JFzUmegKl_tjXrhps30hBjFBHTE>
Subject: Re: [Rum]  =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ietf-?= =?utf-8?q?rum-rue-09=3A_=28with_COMMENT=29?=
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2022 12:24:32 -0000

QnJpYW4NCg0KVGhhbmsgeW91IGZvciB5b3VyIHJlcGx5IGFuZCB0aGUgYWRkZWQgcGllY2VzIG9m
IGluZm9ybWF0aW9uLiANCg0KUmVnYXJkcw0KDQotw6lyaWMNCg0KUFM6IHNvcnJ5IGZvciBiZWxh
dGVkIHJlcGx5LCBJIHdhcyBpbiAnZW5kIG9mIHRoZSB5ZWFyIHNodXRkb3duJyB3aGVuIHlvdXIg
bWVzc2FnZSBsYW5kZWQgaW4gbXkgaW5ib3guDQoNCu+7v09uIDI0LzEyLzIwMjEsIDE2OjU4LCAi
QnJpYW4gUm9zZW4iIDxickBicmlhbnJvc2VuLm5ldD4gd3JvdGU6DQoNCiAgICBUaGFua3MgZm9y
IHlvdXIgY29tbWVudHMuICBTZWUgaW5saW5lIGZvciByZXBsaWVzLg0KDQogICAgPiBPbiBEZWMg
MTYsIDIwMjEsIGF0IDU6NDUgQU0sIMOJcmljIFZ5bmNrZSB2aWEgRGF0YXRyYWNrZXIgPG5vcmVw
bHlAaWV0Zi5vcmc+IHdyb3RlOg0KICAgID4gDQogICAgPiDDiXJpYyBWeW5ja2UgaGFzIGVudGVy
ZWQgdGhlIGZvbGxvd2luZyBiYWxsb3QgcG9zaXRpb24gZm9yDQogICAgPiBkcmFmdC1pZXRmLXJ1
bS1ydWUtMDk6IE5vIE9iamVjdGlvbg0KICAgID4gDQogICAgPiBXaGVuIHJlc3BvbmRpbmcsIHBs
ZWFzZSBrZWVwIHRoZSBzdWJqZWN0IGxpbmUgaW50YWN0IGFuZCByZXBseSB0byBhbGwNCiAgICA+
IGVtYWlsIGFkZHJlc3NlcyBpbmNsdWRlZCBpbiB0aGUgVG8gYW5kIENDIGxpbmVzLiAoRmVlbCBm
cmVlIHRvIGN1dCB0aGlzDQogICAgPiBpbnRyb2R1Y3RvcnkgcGFyYWdyYXBoLCBob3dldmVyLikN
CiAgICA+IA0KICAgID4gDQogICAgPiBQbGVhc2UgcmVmZXIgdG8gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvYmxvZy9oYW5kbGluZy1pZXNnLWJhbGxvdC1wb3NpdGlvbnMvDQogICAgPiBmb3IgbW9yZSBp
bmZvcm1hdGlvbiBhYm91dCBob3cgdG8gaGFuZGxlIERJU0NVU1MgYW5kIENPTU1FTlQgcG9zaXRp
b25zLg0KICAgID4gDQogICAgPiANCiAgICA+IFRoZSBkb2N1bWVudCwgYWxvbmcgd2l0aCBvdGhl
ciBiYWxsb3QgcG9zaXRpb25zLCBjYW4gYmUgZm91bmQgaGVyZToNCiAgICA+IGh0dHBzOi8vZGF0
YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtcnVtLXJ1ZS8NCiAgICA+IA0KICAgID4g
DQogICAgPiANCiAgICA+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCiAgICA+IENPTU1FTlQ6DQogICAgPiAtLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tDQogICAgPiANCiAgICA+IFRoYW5rIHlvdSBmb3IgdGhlIHdvcmsgcHV0IGludG8g
dGhpcyBkb2N1bWVudC4gVGhpcyBzZWVtcyBsaWtlIGEgbmljZQ0KICAgID4gZnVuY3Rpb25hbGl0
eSB0byBtYWtlIHRoZSBJbnRlcm5ldCBtb3JlIGluY2x1c2l2ZS4NCiAgICBUaGFua3MNCg0KICAg
ID4gDQogICAgPiBQbGVhc2UgZmluZCBiZWxvdyBzb21lIG5vbi1ibG9ja2luZyBDT01NRU5UIHBv
aW50cyAoYnV0IHJlcGxpZXMgd291bGQgYmUNCiAgICA+IGFwcHJlY2lhdGVkIGV2ZW4gaWYgb25s
eSBmb3IgbXkgb3duIGVkdWNhdGlvbikuDQogICAgPiANCiAgICA+IFNwZWNpYWwgdGhhbmtzIHRv
IFBhdWwgS3l6aXZhdCBmb3IgdGhlIHNoZXBoZXJkJ3Mgd3JpdGUtdXAgaW5jbHVkaW5nIHRoZQ0K
ICAgID4gc2VjdGlvbiBhYm91dCB0aGUgV0cgY29uc2Vuc3VzLiBBbmQgYmVpbmcgaG9uZXN0IGFi
b3V0IHRoZSByb3VnaCBjb25zZW5zdXMgYW5kDQogICAgPiBsYWNrIG9mIGVuZXJneS4gVGhhbmsg
eW91IGFsc28gUGF1bCBmb3IgdGhlIHJldmlldyBvZiB0aGUgMjIyICghISEpIElQUg0KICAgID4g
ZGVjbGFyYXRpb25zICh3aXRoIHNvbWUgZHVwbGljYXRlcykuDQogICAgWWVzLCBQYXVsIGhhcyBi
ZWVuIHJlYWxseSBncmVhdCBhcyBhIGNvLWNoYWlyDQogICAgPiANCiAgICA+IEkgaG9wZSB0aGF0
IHRoaXMgaGVscHMgdG8gaW1wcm92ZSB0aGUgZG9jdW1lbnQsDQogICAgPiANCiAgICA+IFJlZ2Fy
ZHMsDQogICAgPiANCiAgICA+IC3DqXJpYw0KICAgID4gPT0gQ09NTUVOVFMgPT0NCiAgICA+IA0K
ICAgID4gLS0gQWJzdHJhY3QgLS0NCiAgICA+IFBsZWFzZSBleHBhbmQg4oCcSG9I4oCdDQogICAg
RG9uZQ0KDQogICAgPiANCiAgICA+IC0tIFNlY3Rpb24gNCAtLQ0KICAgID4gV2hpbGUgSSBsaWtl
ICJJbXBsZW1lbnRhdGlvbnMgTVVTVCBzdXBwb3J0IElQdjQgYW5kIElQdjYiLCBpdCBtYXkgYmUg
dG9vIHN0cm9uZw0KICAgID4gdGhvdWdoLg0KICAgIFdl4oCZdmUgc3BlbnQgYSBnb29kIGRlYWwg
b2YgdGltZSBvbiB0aGlzIHN1YmplY3QsIGFuZCB3aGlsZSB0aGVyZSBhcmUgcGFydGljaXBhbnRz
IHdobyB3YW50ZWQgdGhpcyBzb2Z0ZW5lZCwgdGhlIGNvbnNlbnN1cyB3YXMgdG8gbGVhdmUgaXQu
DQoNCiAgICA+IA0KICAgID4gLS0gU2VjdGlvbiA2LjcgLS0NCiAgICA+IEluICJSVUUgTVVTVCBt
YWludGFpbiBhbnkgTkFUIGJpbmRpbmdzIGJ5IHBlcmlvZGljYWxseSBzZW5kaW5nIG1lZGlhIHBh
Y2tldHMiLA0KICAgID4gSSB3b25kZXIgd2hldGhlciBpdCBpcyByZXF1aXJlZCBpbiB0aGUgY2Fz
ZSBvZiBJUHY2ICh1c3VhbGx5IG5vIE5BVCBidXQgcGVyaGFwcw0KICAgID4gc3RhdGVmdWwgZGV2
aWNlcyBvbiB0aGUgcGF0aCkuLi4gUGVyaGFwcyBjaGFuZ2UgIk5BVCBiaW5kaW5ncyIgaW50byAi
c3RhdGVzIGluDQogICAgPiB0aGUgbmV0d29yayAoZS5nLiwgTkFUIGJpbmRpbmdzKeKAnSA/DQog
ICAgRG9uZQ0KDQogICAgPiANCiAgICA+IC0tIFNlY3Rpb24gOS4xIC0tDQogICAgPiBJIHdvbmRl
ciB3aHkgdGhlIGZvY3VzIGlzIG9uIHRoZSBjb3VudHJ5IGFuZCBub3QgdGhlIGxhbmd1YWdlLi4u
IEkuZS4sIGluIG15DQogICAgPiBjb3VudHJ5LCBCZWxnaXVtLCB0aGVyZSBhcmUgMyBvZmZpY2lh
bCBsYW5ndWFnZXMgYW5kIGFsbCBvZiB0aGVzZSBsYW5ndWFnZXMgYXJlDQogICAgPiBzaGFyZWQg
d2l0aCBvdGhlciBjb3VudHJpZXMuLi4gSSB3b3VsZCBzdWdnZXN0IHRoYXQgZWl0aGVyIHJlcXVl
c3RpbmcgYnkNCiAgICA+IGxhbmd1YWdlIG9yIGhhdmluZyB0aGUgc3VwcG9ydGVkIGxhbmd1YWdl
KHMpIHJldHVybmVkIGJ5IHRoZSByZXF1ZXN0Lg0KICAgIFRoZXJlIGlzIGEgcGVyLWNvdW50cnkg
bGlzdCBvZiBwcm92aWRlcnMuICBUaGF0IGhhcyB0byBiZSBwZXItY291bnRyeSwgYmVjYXVzZSBp
dOKAmXMgbW9zdCBvZnRlbiBzb21lIGtpbmQgb2YgcmVndWxhdG9yeSB0aGluZywgb3IgYXQgbGVh
c3Qgb3JnYW5pemVkIHdpdGhpbiB0aGUgY291bnRyeS4gIFRoZW4gYW55IGdpdmVuIHByb3ZpZGVy
IGNhbiBzdXBwb3J0IG9uZSBvciBtb3JlIGxhbmd1YWdlcy4gIFRoYXTigJlzIGhvdyB0aGUgbWVj
aGFuaXNtIHdvcmtzLiAgVGhlcmUgaXMgcyByZWdpc3RyeSB0aGF0IHBvaW50cyB0byB0aGUgcHJv
dmlkZXIgbGlzdCwgYW5kIHRoZW4gZWFjaCBwcm92aWRlciBoYXMgY29uZmlndXJhdGlvbiBkYXRh
IHRoYXQgaXMgbGFuZ3VhZ2Ugc2Vuc2l0aXZlLg0KDQogICAgPiANCiAgICA+IA0KICAgID4gDQoN
Cg0K


From nobody Tue Jan 11 05:38:40 2022
Return-Path: <zaheduzzaman.sarker@ericsson.com>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C6F83A107B; Tue, 11 Jan 2022 05:38:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.576, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 YcykC2d7F4eZ; Tue, 11 Jan 2022 05:38:25 -0800 (PST)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2067.outbound.protection.outlook.com [40.107.20.67]) (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 F33C43A107C; Tue, 11 Jan 2022 05:38:24 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JMbHJHcotlLPVhHHgv6deiIVGv1wqKwA4WAUbwgHf6L2SIVwg2r55hugKLvRg9Q5weQzqvpxXQDBam38OhyzWgML/TPF4iJ9olDTzPVlio74TBx0091s6+/C1Wzzwq55TktRKfKEmeGoDpZhjqr4BRoJHYp6Z+pGRlhDNJa+cFQgVA4QtM8QwlJ/fTOMXcbmzkfHcFyjETJ5YQdK+mr9jEY1L8j1XIM8ookAUylkgaZnXfFy5xGXMpvpZStK2fue/AFuOKLDOPeR7J43GkSgAjyHHkkyY1GBI9KGNt0u4QwP6i5MCpEgIQ7FdPtpur/0uEf+FezAQuS7d0Guk8Lv9g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=JTNzBdiladu3+mIuWpXkSfkXo/vCzJR2Z4Q565peceo=; b=egfM5zz62ycsUu4YerPHCCgjW9FyVZgvM1CJkcN6l6fhuS3KoOg6+LvUdDUrDA4fvW4pCf6auo/jtUHI460BHEP7NlvR9yzHsqA7uxyjBJcC71YT3HchxyHilqvsBpaYgo/FrDRdjmajmapLOVnmOHi6xu/9NRSjKE0DUb+kRI2xtAGYnG2qD8Cfx+RmcCToboQHZOMCeMFRq2pA2xzHHqNXBDK6jn9Kp1js3ymCd4O6ZCpyE+91Zl2eeFJuCs0yMl1ppCcaQJ3NMPEeF3WRCmcva6WRRKc0JRYpdWF7Vow+3ctQKr6cfELUwRD4wIcTBoChmtjhHQCVwLkgFnhChA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=JTNzBdiladu3+mIuWpXkSfkXo/vCzJR2Z4Q565peceo=; b=cQIJKaARfgTXSHzNPvdxHfQSHD96HJZUSQ8PWFWC3PGtX1y0PVyir13A4LL6BWnFQC82h5gnxDf33ZuGt7kZuoA00f3OqymEVrhffYxRrkPy0AGgvP0gi9M3XC2bUOwxWQwWn2ORgInPM134fExQFzIgOQvrEEhITKNCbNp+fZ0=
Received: from HE1PR07MB4187.eurprd07.prod.outlook.com (2603:10a6:7:98::23) by HE1PR0701MB2283.eurprd07.prod.outlook.com (2603:10a6:3:2b::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4888.9; Tue, 11 Jan 2022 13:38:21 +0000
Received: from HE1PR07MB4187.eurprd07.prod.outlook.com ([fe80::1160:24d2:41aa:45cc]) by HE1PR07MB4187.eurprd07.prod.outlook.com ([fe80::1160:24d2:41aa:45cc%3]) with mapi id 15.20.4888.008; Tue, 11 Jan 2022 13:38:21 +0000
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
To: Brian Rosen <br@brianrosen.net>
CC: The IESG <iesg@ietf.org>, "draft-ietf-rum-rue@ietf.org" <draft-ietf-rum-rue@ietf.org>, "rum-chairs@ietf.org" <rum-chairs@ietf.org>, "rum@ietf.org" <rum@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: Zaheduzzaman Sarker's Discuss on draft-ietf-rum-rue-09: (with DISCUSS)
Thread-Index: AQHX8TRbrfnf/vtg4UaxBU6m+QHF0axAhkEAgB14VYA=
Date: Tue, 11 Jan 2022 13:38:21 +0000
Message-ID: <4D20AFD9-943C-41F9-882D-7794B3938F88@ericsson.com>
References: <163951822534.4738.15762238627618541835@ietfa.amsl.com> <583F4F4C-C323-45FE-9278-39D612793351@brianrosen.net>
In-Reply-To: <583F4F4C-C323-45FE-9278-39D612793351@brianrosen.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3654.120.0.1.13)
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 055f0c22-1f15-4bc7-4674-08d9d507a299
x-ms-traffictypediagnostic: HE1PR0701MB2283:EE_
x-microsoft-antispam-prvs: <HE1PR0701MB22835AA7B3A30E020CCA0F5F9F519@HE1PR0701MB2283.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 9YYV7FsMSLF07ICPXrpbZiVsM1b9+hyC76idMajwXJL+uRx6anvZX2cuMBC+JKuRNrKAjaxI2y5VGZAhaCWQG9/4QqeHtcvfPbzmwDueCZ2AvVnyPxOE7Crnlx6f7u59RBoz61BdpJkv1uYhQs30QkvzpIM9m9LGDE4oQ8uGBxYMGGEuDBUbRUVncSsDSmAdjGC8PdpCx5RB8gKNgznE/li5nUCaA95ZdAPlZhFg4IjaM56SmcqB/wiqJ4aPgg/ClnNzRVHzjKtRC6wFFLQlDLxG4M9tU4OZDzHXdhiNQe2hnALAP8F5+pdWM1lrQhjDNCJHSFcjBerFRPWY57mk9eQq7fsnsI/sJ824MOpt55fWvBtyXXHaHa0zaPKzNwfLfJIXPA8vT9NV854wxOn09+PTEOxSiqnk/He9Xwt7rEZHXOOtpABdaDZpO+ISflgo7pWFT2rGbEVwcV1NlXfrZ/okbmE6Izs72M+qwH3wMiG0aSQcE2AldsdY0pHhbGiRBp40AUmxEln7GBveKWfaRRly7SIDXYIw2UPY8fX9n4fpMpDV8AEN28PMLh1/TkVN/V06taqbaTZtZGM9kl4KiZYfXz32YRfaBddkMA/lf2osmeiwu+r9ciRCLp3pdrbsOoIrB47bUj5/qxsfuDfxQkPinwOGxMQnHyJqYp8KotteEMRLWFtlJqjv5I1AINO0eHtm39d6VWT0yevNzufYYfB5c2CBx9XAnyYJOd7ZssUGs1oznOqYqWudUB1A+a3VMfyyacyKfjM4SPSc0EN7aVHNmUkUZnPqx0/h/KPMQ4s9zDgoZQY0s6q89dxTMxIurXeLtBYk4dQMmfRPYZ5g/tt19Q8kbrC5fy4tvu+uHN4=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB4187.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(13230001)(4636009)(366004)(6916009)(38100700002)(316002)(76116006)(36756003)(54906003)(508600001)(82960400001)(91956017)(966005)(86362001)(33656002)(66946007)(64756008)(4326008)(38070700005)(8936002)(8676002)(66556008)(66446008)(66476007)(2906002)(5660300002)(83380400001)(71200400001)(122000001)(44832011)(186003)(53546011)(66574015)(26005)(2616005)(6506007)(6486002)(6512007)(99936003)(45980500001)(20210929001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?utf-8?B?dTZwZ1NMN2xtNTNNOVFDcWdRZnpueURocUg1N2dvc2t1YkdzQVF1d2tCbjc2?= =?utf-8?B?OVlPOFgrVGtBNjBpdElQNExKa3R1aTZoSUZoMFBQVDdZcUxGczZmWENhRml0?= =?utf-8?B?OFFsUXlEZ0Y3eEg5bkJpMDlOZHZheldpdjRzejlMSkhLaXpEMlJXYzJUMFhH?= =?utf-8?B?R2Jtd0JmemN5Mld1TGxmWXM2K2Vqa2hEd2o2RnlkRGVYSDM3NGNiSlRDMXlh?= =?utf-8?B?N1JKb0JkaFhtN3hHbVJORU9GUjc2T2Z2QkZLQjBybng1ejFDY3dnTGNYN0NI?= =?utf-8?B?bk5lTFEyTldQNGlwa2t3bENlSTVZUDAxYTltWEJ2RWxkZHB1YzlBTXNwcVZk?= =?utf-8?B?NmJDck5QcUVFN0FDMHlINVFDYmRvUXQ5dkVRSmFxQnFBQlU0RlFER3dDdDI3?= =?utf-8?B?ajFEY0xPUjNnOURBTHlPZThmY1pnOGx3MERYakp5eWs2Y21wSTZmODgvcGNX?= =?utf-8?B?WFg2OVkxR1JONXR5WGx0MTJwM1ltT1ZWbmtWNTdzZlJBcy9RWjVuQnN3MGR2?= =?utf-8?B?Sjg3M2RJVzhvZDFNaHVISmRYVXYza0pPbWE0WjNvOTRpVzMvNkhvN2I3a0s4?= =?utf-8?B?UUFGcmpkdXdraTZIN1pxdDVYV1NQcjZ0OC85MlUvTFQwemNpelVrV2lhN2h3?= =?utf-8?B?bFNDV000bytEcmEzZTMvemJjcnc5dFlYdlQ3NGlveDVGTDJKVHFIeitxZXFF?= =?utf-8?B?c3lLekZDZTJSQjdLZnAyaU9ycW43aTJIdXVYT0pMRXdCalppUDl2ZUU5bDBE?= =?utf-8?B?VHRLQWtMYm8rWE1FeUJjMVNlckRVOVFLRHEvOUdEVVlxUEVqZWlkcndsNkpw?= =?utf-8?B?dzcreXhiK1B4eFgzd0dnZ1RLbWxyaWR2dzh2OTdsSnVUcnBYSnE2T3FsTnNz?= =?utf-8?B?N3BDSUc4U0JFYXR2Sno4QmVrMG9WamxoSGsrNGIyekNka0J2bjZZcjdseU0z?= =?utf-8?B?a2VBb0I1QmdSRkt0aXVUSWd2OGNmL3JydVo3azZCS3FrMVkycndFM1A2aENs?= =?utf-8?B?YkY5cVN0aDFCbTJ4TTJUekF4VFl5RDluSWdIMlRrRjZSODRKTnV4ejJPQTVl?= =?utf-8?B?dHNQVHE4NDlDQzFCR2JmdkgvOFVPS3RWN3pJN0JRamJNZEtQcXdLb2tUOFJw?= =?utf-8?B?VEJhMkVFWjZhcGpXQWQ2S3RHK250NFEzRWVXTEhUMXZ0WkR2SnMxV2FEOWlq?= =?utf-8?B?UWJhdjM4NWhrN1ZEdDB1cUExa01SVmZVZ1VtaStlVVYzdHhXMmRxLzBTaXlY?= =?utf-8?B?OEtEYW42NzFVQkx2ZFMxalpLZXdlMzhBRExiOVFxaHZYNDdONkJUR20zeXhX?= =?utf-8?B?RGE1ZCthS3lEdFB5VFVMSzI1S3RqVTUwNHNiWm8xZzRnR05wbUJaVUg4Snpi?= =?utf-8?B?Qm9lM0p2bzBpUEZzM0NBVWhqa251a3lmTWV6dlg0aE54L28vc3NQVlBOd1p3?= =?utf-8?B?VzNlUXo5NXJ2VnFQdkw3YUptdTZ2NXdOR1VJZFBIakNVVGRkN1dqMWtaaVp3?= =?utf-8?B?OThnTjhPaGhYQ1lGQWlZNVJ5eXYySWZIWk9scGM1QUVYZU80TkFwVzV2bjlx?= =?utf-8?B?UEtDbWlFRTNyNk5tLyszdStRZ0p6R3E2Zjd3eUNTc1VHYUFZZ29MT2lub3Vr?= =?utf-8?B?cDV2MU15amxnOUNqME1teEljZDE3WUUzOEFOanZFSTFpWDA4UFNxNUxDWlg2?= =?utf-8?B?V0NVcVUvcGpjMnpFcElLVWNhQWlyem9mTUM5bE42WGlZZVQ4WUdUT0RqcXpQ?= =?utf-8?B?b1lmeXY4cG1jS25ZUTJkanlPTTFLdG12SDBwSzNYYXpQSmJLb2VTS0h1V3Rz?= =?utf-8?B?UTdDQVVZc3ovYnNBSVZmVGxYRTAwbzFqWVpHS2liUFlpNm1ESDFxaGNRaEll?= =?utf-8?B?RXZQaW1WZkplYWRTUjhWTTNMSVByNmhua0dCZUxnQWFuTmZ6SUQyRTUvNXZu?= =?utf-8?B?aHZXOTFaL0l3QmdnS1F5WHIrVC91TTV4MWxlVDA2THJVU01UU0ljek1hU1hP?= =?utf-8?B?b1gySXhmK08vdVppZEQyUFNGWk5VUzc0VVZNbnlycElUSncrdWxoelZkbHlD?= =?utf-8?B?eENBY1Z6elhZT1hLeHVsb3V0VTNtY2tXeUR4R3NGRS9URVBtSFdwNmxCeWNG?= =?utf-8?B?TFdGQUcya1orTDNaRmdqbEZwb0lKRUE5K1JSMXBRK2FpeGNCZnM3Y3hMTERt?= =?utf-8?B?S0lheHlOMlNTcGFGSndRQ09UTVBaK0YrZ0R4aVlaYzlaeTVKVzZLRTl6RTVK?= =?utf-8?B?MmhmQVpmekpicCt1V2NaVzVtS1plNG5KTzcrdEJTcFJvYVFXQk9sZEtISjAr?= =?utf-8?B?WHpiSzJ3OHhqa0xYNSt4RFlZczJPL1RiU1VhZjJranhVVmNrSVNwUT09?=
Content-Type: multipart/signed; boundary="Apple-Mail=_C66A360D-C99A-484D-A203-FD89578EE1EF"; protocol="application/pkcs7-signature"; micalg=sha-256
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB4187.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 055f0c22-1f15-4bc7-4674-08d9d507a299
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jan 2022 13:38:21.7514 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: rUXY6ppkon9qNxfTzCXA4fDeNLCYXzT2WNhgYJsJFb5tLvRHGvVkQpD8BXcseLrF7xqqhGi35fSEoIzoL1QqTIpGpJCWkg/cAbykmEKv+CcVImxFA6uRhmv9iPO3mErn
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2283
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/yRDiycmOcJe7FcL3fkiLZKbR1pU>
Subject: Re: [Rum] Zaheduzzaman Sarker's Discuss on draft-ietf-rum-rue-09: (with DISCUSS)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2022 13:38:30 -0000

--Apple-Mail=_C66A360D-C99A-484D-A203-FD89578EE1EF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 23 Dec 2021, at 20:36, Brian Rosen <br@brianrosen.net> wrote:
>=20
> Thank you for these comments.
>=20
> We did not have a specific conversation on handling rate control and =
congestion feedback. =20
> The RUE server and client are required to support RTCP, so I think =
that part is easy.  Both ends are required to support the WebRTC media =
spec, so I think if it happened if both RUE clients were implemented =
with WebRTC clients, everything would work the way we expect it to.
>=20
> So I think the issue reduces to a situation where one end is a WebRTC =
client, and the other is not.  They both have to implement the media =
congestion mechanisms.  They both have RTCP to work with.  SDP =
negotiation should work,
This sounds like requirements to me, is this described in the document?
>=20
> I=E2=80=99m down to thinking the gateway doesn=E2=80=99t have to mess =
with this.  It=E2=80=99s possible that the gateway could have more =
expansive goals to be backwards compatible with existing VRS devices =
that don=E2=80=99t conform to this document, and I could imagine that =
there might need to be some work there.  But that would not be covered =
in this document.=20
Would be good to be explicit about this in this document. The thing if =
the gateway does not want to mess with the RTCP signalling then the =
signalling and the negotiation of what to use for rate and congestion =
control need to be end to end. This should be clear in this document.
>=20
> I=E2=80=99m not personally a WebRTC expert although I had help writing =
the text from some folks who were.  So, II easily could be missing =
something here.
>=20
> On =E2=80=9CClarification of the use of ICE=E2=80=9D, I propose to add =
"Implementations MUST implement full ICE, although they MAY interwork =
with User Agents that implement ICE-lite.=E2=80=9D  There is an =
unqualified requirement to support RFC8839.
OK.
>=20
> I propose to add the following text in the media section where we =
introduce the WebRTC media specs:
> To use WebRTC with this document, a gateway that presents a WebRTC =
server interface towards a browser, and a RUE client interface towards a =
provider is assumed.  The gateway would interwork signaling, and as =
noted below, interwork at least any real time text media, in order to =
allow a standard browser baed WebRTC client to be a VRS client.  The =
combination of the browser client and the gateway would be a RUE user.
I think interworking will also be necessary for A/V media traffic

//Zahed
.
>=20
> Since the discussion of WebRTC is limited to the media section, I =
don=E2=80=99t think we need to have more definitions, but I can add them =
if we can show where they would be used.
>=20
> Brian
>=20
>> On Dec 15, 2021, at 3:13 AM, Zaheduzzaman Sarker via Datatracker =
<noreply@ietf.org> wrote:
>>=20
>> Zaheduzzaman Sarker has entered the following ballot position for
>> draft-ietf-rum-rue-09: 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://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af-4544455=
55731-daabe057359b7059&q=3D1&e=3D74bc0e4e-1cad-4540-ae4b-6a8304ba7746&u=3D=
https%3A%2F%2Fwww.ietf.org%2Fblog%2Fhandling-iesg-ballot-positions%2F
>> for more information about how to handle DISCUSS and COMMENT =
positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> =
https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af-4544455=
55731-5f21db66ba2ee3f6&q=3D1&e=3D74bc0e4e-1cad-4540-ae4b-6a8304ba7746&u=3D=
https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-rum-rue%2F
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> DISCUSS:
>> =
----------------------------------------------------------------------
>>=20
>> First of all thanks for working on this technology to make =
communication
>> available and easy for special human beings. (I have worked with them =
to
>> converter text to sign language in my bachelor hence had a special =
feeling
>> while reading this specification).
>>=20
>> I understood from the email discussions on the TSVART review
>> =
(https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af-454445=
555731-b6cf7e1cc91dc9fe&q=3D1&e=3D74bc0e4e-1cad-4540-ae4b-6a8304ba7746&u=3D=
https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Ftsv-art%2FZ_Ne5au4rCHwci=
g8bospMcLyzTc%2F)
>> that in the system RUI is deployed, we will have gateway(s) with two =
legs - one
>> with WebRTC (client <--> gateway) and one with RUI client =
communicating with
>> RUI server (gateway <--> server). With this understanding I have some =
points
>> which I believe worth discussing.
>>=20
>> - WebRTC communication will be congestion and rate controlled. This =
will use
>> RTCP feedbacks to make the rate control and congestion control happen =
in the
>> WebRTC peers. On the WebRTC part of the leg, this RTCP feedbacks will =
be
>> available according to the WebRTC specification. However, this =
specification
>> does not discuss how those RTCP feedback will be converted from the =
RUI
>> server to RUI client (i.e the gateway) direction and vice versa. This =
will
>> require the gateway to have such conversion functions to actually =
work. what
>> is the thinking here? has this been considered? as I am not sure how =
is the
>> network looks like between the RUI client and RUI server, there might =
be the
>> Internet connecting them hence need to have congestion controlled =
traffic.
>>=20
>> - Thanks to Bernard Aboba for a comprehensive TSVART review of this =
draft and
>> I would like to bring some issues, identified in that review, here to =
make
>> sure they are addressed-
>>=20
>>   * clarification on the use of ICE
>>   * clarification on what is a WebRTC client, WebRTC server, gateway, =
RUI
>>   client and RUI server. I believe all four have been conceptually =
used in
>>   the specification without concretely defining their roles. for =
example - if
>>   server is mentioned it need to be distinguishable if it is WebRTC =
server or
>>   RUI server ( I noted that there are servers in this specification =
which are
>>   clearly understandable).
>>=20
>>=20
>>=20
>>=20
>>=20


--Apple-Mail=_C66A360D-C99A-484D-A203-FD89578EE1EF
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCBf4w
ggX6MIID4qADAgECAg8BdUoQAyUVYjB/ZVVBDvMwDQYJKoZIhvcNAQELBQAwRzELMAkGA1UEBhMC
U0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENB
IHYzMB4XDTIwMTAyMTA3MjkyNVoXDTIzMTAyMjA3MjkyNFowYjERMA8GA1UECgwIRXJpY3Nzb24x
HDAaBgNVBAMME1phaGVkdXp6YW1hbiBTYXJrZXIxLzAtBgkqhkiG9w0BCQEWIHphaGVkdXp6YW1h
bi5zYXJrZXJAZXJpY3Nzb24uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmjJb
Zy6kdvqWwiZanvVnqKsb990pSFndyIgFspP9mArDxvEX0oqrBugPRyJSp1KA0KDPo9L3SBHk7pbp
hJDbJAxPdPAbyZ+DMHV/UtQSUUpp8rRoYNEA6Ew3OlG5Sz1Nhq9AcjSKeOZKunnJInh/y435NACo
co2uP/6Gk0XBeB3qE645aIqpbsO3DCUMOWxWIjjTRFQ/TqoUjbIwfw+rO64Y3qEa96Ibj63AoDtt
3gwmtpFkVm5C44XfK7J4LyXIIz4TQqnfxlfoJ+ttFMfV1ZV1OvA7xXj0yO/6btsktlktpgMvow87
HPkSRtsLXQoRhU4E1zclEPWz5SzhUXuOvwIDAQABo4IBxjCCAcIwHwYDVR0jBBgwFoAUHHsZnpec
dqwgPdjc45Fq49stplMwHQYDVR0OBBYEFJlMp3EJ+P/dXOLqvbT718jDfw1mMA4GA1UdDwEB/wQE
AwIFoDBVBgNVHSAETjBMMEoGDCsGAQQBgg8CAwEBEjA6MDgGCCsGAQUFBwIBFixodHRwczovL3Jl
cG9zaXRvcnkudHJ1c3QudGVsaWFzb25lcmEuY29tL0NQUzArBgNVHREEJDAigSB6YWhlZHV6emFt
YW4uc2Fya2VyQGVyaWNzc29uLmNvbTBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9lcmljc3Nvbm5saW5kaXZpZHVhbGNhdjMuY3JsMB0GA1UdJQQWMBQGCCsGAQUF
BwMEBggrBgEFBQcDAjCBggYIKwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIu
dHJ1c3QudGVsaWEuY29tMEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEu
Y29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2My5jZXIwDQYJKoZIhvcNAQELBQADggIBAD1OD1xt
xE0jjc12/QXWWe8Cv2q1ZRn1PwacRWFJMyprPB6CiR6YBnmovYCyvCrNCqzsNaTpQLAQeKxwpmOg
fZ1SrdyqQKjtCiAlQynqV+dX5VAA6kt/fM67jZbU+lmzw3/2mXNQKTnor1Ax2bJjtZB2DzvTmSPd
EybZWxSfMMSsZHA4GLPGEHws+7fHeZ6RSRsAolXPTLGu7gxPkYDtaUzI9M8Z9GKz2UC/wNP2UieR
95h5TnKiqAWLqAxwzcu7GVWIdJ4rzgOenaNg56OM5q87+X90ZSAODWAPnxdDgVGspHbxt2g9cQYb
pkKiHWrOuLIWd8B/oGbE1ruKqcFKC39aYkd7JRlHjkNfU/IpymDoGd3RYMtsJW2JvinuZMmMZ5F5
Xpw1yJuSPrq5tHbPx7S6hjqYhd9VkRLbKkprw9+HJZBrUrhrUx4HVF2/bo+WG9GCTdQUsm8JQt9B
zpRh2ySNBQZfUn1WN3Q+lMcGSdItCNYH6HnXGrAmv+oDZ1pnp9z+NNmDoNMAHaFvwYCFd9/HvjJu
5kL90Fp3UEJQAk6X+2+ElrfNplUz16nAOBvxcY55R5eI9SDD8MmNfADekiMldSwB9LjMrqBhwWeE
UblghhtceJ3iqg35LURo+KXdL3h0/IodZPBYoMLMhMbDdYokIUY+mWW5W1T1WzV9PyWqMYICyjCC
AsYCAQEwWjBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNz
c29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCDwF1ShADJRViMH9lVUEO8zANBglghkgBZQMEAgEFAKCC
AUEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMjIwMTExMTMzODIx
WjAvBgkqhkiG9w0BCQQxIgQgT8+oJ9q4UU0DAMTXR+3+795mHLniq5ffGMdNl5hUmIswaQYJKwYB
BAGCNxAEMVwwWjBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVy
aWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCDwF1ShADJRViMH9lVUEO8zBrBgsqhkiG9w0BCRAC
CzFcoFowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBIHYzAg8BdUoQAyUVYjB/ZVVBDvMwDQYJKoZIhvcNAQELBQAEggEA
gYhW1HsJfpR5licp5RvFqn2Yi31q5sVUv0nspmghj6aUmtjdlwUOrGdx0qbNvxht2afQ9I9Tdx+c
kQXpI5GS70S8YwCd7yTR5/rlSxqd5MSHGTeLqAmhFH093+JiYljrCRSMrcfoNmNwgq7zKJfn22Qa
4TYvl2of1xbcS7PbxcVWo47+NRic9B3FtYxh1QUNKp2CVeeGgcJ/mnFygsaDyvKkHedthAPVP1mb
Wjm8CT6kJU5xYDZ1+bMbzz1ULUM8lTZeUv0EUjfi84QKRHd4o6LPK9TenUtGOmzB8qDe3YcLHmMm
aDr13am8NBVf9x2wFhonNkIMU7QX2LWJzfs8iQAAAAAAAA==

--Apple-Mail=_C66A360D-C99A-484D-A203-FD89578EE1EF--


From nobody Tue Jan 11 10:15:08 2022
Return-Path: <br@brianrosen.net>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 194A53A109F for <rum@ietfa.amsl.com>; Tue, 11 Jan 2022 10:15:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level: 
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20210112.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TeZXmls8egeM for <rum@ietfa.amsl.com>; Tue, 11 Jan 2022 10:14:56 -0800 (PST)
Received: from mail-il1-x134.google.com (mail-il1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (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 1FE5B3A10A1 for <rum@ietf.org>; Tue, 11 Jan 2022 10:14:56 -0800 (PST)
Received: by mail-il1-x134.google.com with SMTP id b1so15313619ilj.2 for <rum@ietf.org>; Tue, 11 Jan 2022 10:14:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ZNMjcl7FyMrxe/G/h7qIojySOg56WlaEJSgBt3YtkvQ=; b=skiyrGt/94DT0+gpPBU2j/bdTbs/LUFYt3E73IgI8pGmVh3u4vy5BIr2CJUtROGQaG 02sj6jtxP7dJm0MidPqZO4287aaq1PfIDVHOHCMbZVpQ4LQDak0bZsicLofv3loCKqkU 2Meq5SL4YBmuNv71RFBu3SMoIcerfK7BSJu4PU5p7f8mqfe+oHXpUasv7aBOhJRYbTlJ RZ5GVJhk3XKq3TTDs9mEerNnbDOd4RL2PjIFrNyqGkyuSaZKzZGaWaHeE+6IeUgNbI2k XxUqClfZl73SekpUzCW3ZGGQymqcYwKH7Mszyt9wIqQtjEVdxJ+5H5lfFHPMduUWyxx/ RWmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ZNMjcl7FyMrxe/G/h7qIojySOg56WlaEJSgBt3YtkvQ=; b=hBeORWYoVPlnaGsac68iAIGmgKb6dsCyHW8QurYfJhwvR0cBgr74Fuv1dZ4v7MMXPN ez2QavbN/ior9FwQPYAqp/1EAWmJtRF/xE7D5Jy1xTukYrjv428G3jQHUQOv4RMnVUwF 8Wqp4KSevcV2oQZ1pv9IcJgs+gL2Bm3OT47mtxFf1jfwK3pxM2sSB6o47yD7rf3P7hUL j0Rh+wa/zdxHwx0XWBurwvbfjDv+O8AocB6sYBX2MFgsx0xbGB11hYugTtXB5gRtntD6 FilFfVMhg0a9aHVA9/UqCZBrkjETbAisjb9C3NOPCRFkAyGx+g/sg49HCubk8msh6MEV dIaw==
X-Gm-Message-State: AOAM533AcSISoRN3cyYf9geMNudvY3QcBfbuvRGbseQm25GQqbuApkQD aOXdMfGYR1UCLfwVHym08M9iYg==
X-Google-Smtp-Source: ABdhPJxnrCVicYGINDXQwaAtpL/+xfDIjEGbG4awRGIRyH89J7k3M4Pn/vWtl+PEC9RNjlEvnr7YmQ==
X-Received: by 2002:a05:6e02:b21:: with SMTP id e1mr3339106ilu.254.1641924894038;  Tue, 11 Jan 2022 10:14:54 -0800 (PST)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id a14sm6281727ilm.48.2022.01.11.10.14.53 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jan 2022 10:14:53 -0800 (PST)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <A292F99E-4E40-4862-B9FE-8C84DF512011@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_150EB26A-8C8E-4A37-97B1-5B87AFA4EF56"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\))
Date: Tue, 11 Jan 2022 13:14:49 -0500
In-Reply-To: <4D20AFD9-943C-41F9-882D-7794B3938F88@ericsson.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-rum-rue@ietf.org" <draft-ietf-rum-rue@ietf.org>, "rum-chairs@ietf.org" <rum-chairs@ietf.org>, "rum@ietf.org" <rum@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
References: <163951822534.4738.15762238627618541835@ietfa.amsl.com> <583F4F4C-C323-45FE-9278-39D612793351@brianrosen.net> <4D20AFD9-943C-41F9-882D-7794B3938F88@ericsson.com>
X-Mailer: Apple Mail (2.3693.20.0.1.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/NOoiUw5oO4waDm6_sesKYAEazZ4>
Subject: Re: [Rum] Zaheduzzaman Sarker's Discuss on draft-ietf-rum-rue-09: (with DISCUSS)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2022 18:15:00 -0000

--Apple-Mail=_150EB26A-8C8E-4A37-97B1-5B87AFA4EF56
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Jan 11, 2022, at 8:38 AM, Zaheduzzaman Sarker =
<zaheduzzaman.sarker@ericsson.com> wrote:
>=20
>=20
>=20
>> On 23 Dec 2021, at 20:36, Brian Rosen <br@brianrosen.net =
<mailto:br@brianrosen.net>> wrote:
>>=20
>> Thank you for these comments.
>>=20
>> We did not have a specific conversation on handling rate control and =
congestion feedback. =20
>> The RUE server and client are required to support RTCP, so I think =
that part is easy.  Both ends are required to support the WebRTC media =
spec, so I think if it happened if both RUE clients were implemented =
with WebRTC clients, everything would work the way we expect it to.
>>=20
>> So I think the issue reduces to a situation where one end is a WebRTC =
client, and the other is not.  They both have to implement the media =
congestion mechanisms.  They both have RTCP to work with.  SDP =
negotiation should work,
> This sounds like requirements to me, is this described in the =
document?
The requirements that both have to implement RTCP, the media congestion =
mechanisms, and SDP negotiations are already in the document, yes.

>>=20
>> I=E2=80=99m down to thinking the gateway doesn=E2=80=99t have to mess =
with this.  It=E2=80=99s possible that the gateway could have more =
expansive goals to be backwards compatible with existing VRS devices =
that don=E2=80=99t conform to this document, and I could imagine that =
there might need to be some work there.  But that would not be covered =
in this document.=20
> Would be good to be explicit about this in this document. The thing if =
the gateway does not want to mess with the RTCP signalling then the =
signalling and the negotiation of what to use for rate and congestion =
control need to be end to end. This should be clear in this document.
But that is why the document requires support for 8825/8834.  I will add =
a statement that "Conformance to this document allows end-to-end RTCP =
and media congestion control for audio and video."  =E2=80=9CAllows=E2=80=9D=
 is the right word, because many provides anchor media.


>> I=E2=80=99m not personally a WebRTC expert although I had help =
writing the text from some folks who were.  So, II easily could be =
missing something here.
>>=20
>> On =E2=80=9CClarification of the use of ICE=E2=80=9D, I propose to =
add "Implementations MUST implement full ICE, although they MAY =
interwork with User Agents that implement ICE-lite.=E2=80=9D  There is =
an unqualified requirement to support RFC8839.
> OK.
>>=20
>> I propose to add the following text in the media section where we =
introduce the WebRTC media specs:
>> To use WebRTC with this document, a gateway that presents a WebRTC =
server interface towards a browser, and a RUE client interface towards a =
provider is assumed.  The gateway would interwork signaling, and as =
noted below, interwork at least any real time text media, in order to =
allow a standard browser baed WebRTC client to be a VRS client.  The =
combination of the browser client and the gateway would be a RUE user.
> I think interworking will also be necessary for A/V media traffic
I certainly hope not.  Between conforming RUEs, there won=E2=80=99t be =
any issues.  The only things I worry about are talking to older devices =
that may not implement all the mechanisms and where SDP negotiation =
might not result in a compatible option.  =20

>=20
> //Zahed
> .
>>=20
>> Since the discussion of WebRTC is limited to the media section, I =
don=E2=80=99t think we need to have more definitions, but I can add them =
if we can show where they would be used.
>>=20
>> Brian
>>=20
>>> On Dec 15, 2021, at 3:13 AM, Zaheduzzaman Sarker via Datatracker =
<noreply@ietf.org> wrote:
>>>=20
>>> Zaheduzzaman Sarker has entered the following ballot position for
>>> draft-ietf-rum-rue-09: 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://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af-4544455=
55731-daabe057359b7059&q=3D1&e=3D74bc0e4e-1cad-4540-ae4b-6a8304ba7746&u=3D=
https%3A%2F%2Fwww.ietf.org%2Fblog%2Fhandling-iesg-ballot-positions%2F =
<https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af-454445=
555731-daabe057359b7059&q=3D1&e=3D74bc0e4e-1cad-4540-ae4b-6a8304ba7746&u=3D=
https%3A%2F%2Fwww.ietf.org%2Fblog%2Fhandling-iesg-ballot-positions%2F>
>>> for more information about how to handle DISCUSS and COMMENT =
positions.
>>>=20
>>>=20
>>> The document, along with other ballot positions, can be found here:
>>> =
https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af-4544455=
55731-5f21db66ba2ee3f6&q=3D1&e=3D74bc0e4e-1cad-4540-ae4b-6a8304ba7746&u=3D=
https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-rum-rue%2F =
<https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af-454445=
555731-5f21db66ba2ee3f6&q=3D1&e=3D74bc0e4e-1cad-4540-ae4b-6a8304ba7746&u=3D=
https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-rum-rue%2F>
>>>=20
>>>=20
>>>=20
>>> =
----------------------------------------------------------------------
>>> DISCUSS:
>>> =
----------------------------------------------------------------------
>>>=20
>>> First of all thanks for working on this technology to make =
communication
>>> available and easy for special human beings. (I have worked with =
them to
>>> converter text to sign language in my bachelor hence had a special =
feeling
>>> while reading this specification).
>>>=20
>>> I understood from the email discussions on the TSVART review
>>> =
(https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af-454445=
555731-b6cf7e1cc91dc9fe&q=3D1&e=3D74bc0e4e-1cad-4540-ae4b-6a8304ba7746&u=3D=
https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Ftsv-art%2FZ_Ne5au4rCHwci=
g8bospMcLyzTc%2F =
<https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af-454445=
555731-b6cf7e1cc91dc9fe&q=3D1&e=3D74bc0e4e-1cad-4540-ae4b-6a8304ba7746&u=3D=
https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Ftsv-art%2FZ_Ne5au4rCHwci=
g8bospMcLyzTc%2F>)
>>> that in the system RUI is deployed, we will have gateway(s) with two =
legs - one
>>> with WebRTC (client <--> gateway) and one with RUI client =
communicating with
>>> RUI server (gateway <--> server). With this understanding I have =
some points
>>> which I believe worth discussing.
>>>=20
>>> - WebRTC communication will be congestion and rate controlled. This =
will use
>>> RTCP feedbacks to make the rate control and congestion control =
happen in the
>>> WebRTC peers. On the WebRTC part of the leg, this RTCP feedbacks =
will be
>>> available according to the WebRTC specification. However, this =
specification
>>> does not discuss how those RTCP feedback will be converted from the =
RUI
>>> server to RUI client (i.e the gateway) direction and vice versa. =
This will
>>> require the gateway to have such conversion functions to actually =
work. what
>>> is the thinking here? has this been considered? as I am not sure how =
is the
>>> network looks like between the RUI client and RUI server, there =
might be the
>>> Internet connecting them hence need to have congestion controlled =
traffic.
>>>=20
>>> - Thanks to Bernard Aboba for a comprehensive TSVART review of this =
draft and
>>> I would like to bring some issues, identified in that review, here =
to make
>>> sure they are addressed-
>>>=20
>>>  * clarification on the use of ICE
>>>  * clarification on what is a WebRTC client, WebRTC server, gateway, =
RUI
>>>  client and RUI server. I believe all four have been conceptually =
used in
>>>  the specification without concretely defining their roles. for =
example - if
>>>  server is mentioned it need to be distinguishable if it is WebRTC =
server or
>>>  RUI server ( I noted that there are servers in this specification =
which are
>>>  clearly understandable).


--Apple-Mail=_150EB26A-8C8E-4A37-97B1-5B87AFA4EF56
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><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jan 11, 2022, at 8:38 AM, Zaheduzzaman Sarker &lt;<a =
href=3D"mailto:zaheduzzaman.sarker@ericsson.com" =
class=3D"">zaheduzzaman.sarker@ericsson.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">On 23 Dec 2021, at 20:36, Brian Rosen =
&lt;<a href=3D"mailto:br@brianrosen.net" =
class=3D"">br@brianrosen.net</a>&gt; wrote:<br class=3D""><br =
class=3D"">Thank you for these comments.<br class=3D""><br class=3D"">We =
did not have a specific conversation on handling rate control and =
congestion feedback. &nbsp;<br class=3D"">The RUE server and client are =
required to support RTCP, so I think that part is easy. &nbsp;Both ends =
are required to support the WebRTC media spec, so I think if it happened =
if both RUE clients were implemented with WebRTC clients, everything =
would work the way we expect it to.<br class=3D""><br class=3D"">So I =
think the issue reduces to a situation where one end is a WebRTC client, =
and the other is not. &nbsp;They both have to implement the media =
congestion mechanisms. &nbsp;They both have RTCP to work with. &nbsp;SDP =
negotiation should work,<br class=3D""></blockquote><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"">This sounds like requirements to =
me, is this described in the document?</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>The requirements =
that both have to implement RTCP, the media congestion mechanisms, and =
SDP negotiations are already in the document, yes.</div><div><br =
class=3D""></div><div><blockquote type=3D"cite" class=3D""><div =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">I=E2=80=99m down to thinking the gateway doesn=E2=80=99t have =
to mess with this. &nbsp;It=E2=80=99s possible that the gateway could =
have more expansive goals to be backwards compatible with existing VRS =
devices that don=E2=80=99t conform to this document, and I could imagine =
that there might need to be some work there. &nbsp;But that would not be =
covered in this document.<span =
class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D""></blockquote><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"">Would be good to be explicit about this in this document. The =
thing if the gateway does not want to mess with the RTCP signalling then =
the signalling and the negotiation of what to use for rate and =
congestion control need to be end to end. This should be clear in this =
document.</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>But that is why the document =
requires support for 8825/8834. &nbsp;I will add a statement that =
"Conformance to this document allows end-to-end RTCP and media =
congestion control for audio and video." &nbsp;=E2=80=9CAllows=E2=80=9D =
is the right word, because many provides anchor media.</div><div><br =
class=3D""></div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><blockquote type=3D"cite" style=3D"font-family:=
 Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">I=E2=80=
=99m not personally a WebRTC expert although I had help writing the text =
from some folks who were. &nbsp;So, II easily could be missing something =
here.<br class=3D""><br class=3D"">On =E2=80=9CClarification of the use =
of ICE=E2=80=9D, I propose to add "Implementations MUST implement full =
ICE, although they MAY interwork with User Agents that implement =
ICE-lite.=E2=80=9D &nbsp;There is an unqualified requirement to support =
RFC8839.<br class=3D""></blockquote><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"">OK.</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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D"">I propose to add the =
following text in the media section where we introduce the WebRTC media =
specs:<br class=3D"">To use WebRTC with this document, a gateway that =
presents a WebRTC server interface towards a browser, and a RUE client =
interface towards a provider is assumed. &nbsp;The gateway would =
interwork signaling, and as noted below, interwork at least any real =
time text media, in order to allow a standard browser baed WebRTC client =
to be a VRS client. &nbsp;The combination of the browser client and the =
gateway would be a RUE user.<br class=3D""></blockquote><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"">I think interworking will also =
be necessary for A/V media traffic</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>I certainly hope =
not. &nbsp;Between conforming RUEs, there won=E2=80=99t be any issues. =
&nbsp;The only things I worry about are talking to older devices that =
may not implement all the mechanisms and where SDP negotiation might not =
result in a compatible option. &nbsp;&nbsp;</div><div><br =
class=3D""></div><div><blockquote type=3D"cite" class=3D""><div =
class=3D""><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"">//Zahed</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"">.</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""><blockquote type=3D"cite" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">Since the discussion of WebRTC is limited to the media =
section, I don=E2=80=99t think we need to have more definitions, but I =
can add them if we can show where they would be used.<br class=3D""><br =
class=3D"">Brian<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">On Dec 15, 2021, at 3:13 AM, Zaheduzzaman Sarker via =
Datatracker &lt;<a href=3D"mailto:noreply@ietf.org" =
class=3D"">noreply@ietf.org</a>&gt; wrote:<br class=3D""><br =
class=3D"">Zaheduzzaman Sarker has entered the following ballot position =
for<br class=3D"">draft-ietf-rum-rue-09: Discuss<br class=3D""><br =
class=3D"">When responding, please keep the subject line intact and =
reply to all<br class=3D"">email addresses included in the To and CC =
lines. (Feel free to cut this<br class=3D"">introductory paragraph, =
however.)<br class=3D""><br class=3D""><br class=3D"">Please refer =
to<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af=
-454445555731-daabe057359b7059&amp;q=3D1&amp;e=3D74bc0e4e-1cad-4540-ae4b-6=
a8304ba7746&amp;u=3Dhttps%3A%2F%2Fwww.ietf.org%2Fblog%2Fhandling-iesg-ball=
ot-positions%2F" =
class=3D"">https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-31327=
3af-454445555731-daabe057359b7059&amp;q=3D1&amp;e=3D74bc0e4e-1cad-4540-ae4=
b-6a8304ba7746&amp;u=3Dhttps%3A%2F%2Fwww.ietf.org%2Fblog%2Fhandling-iesg-b=
allot-positions%2F</a><br class=3D"">for more information about how to =
handle DISCUSS and COMMENT positions.<br class=3D""><br class=3D""><br =
class=3D"">The document, along with other ballot positions, can be found =
here:<br class=3D""><a =
href=3D"https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af=
-454445555731-5f21db66ba2ee3f6&amp;q=3D1&amp;e=3D74bc0e4e-1cad-4540-ae4b-6=
a8304ba7746&amp;u=3Dhttps%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-=
rum-rue%2F" =
class=3D"">https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-31327=
3af-454445555731-5f21db66ba2ee3f6&amp;q=3D1&amp;e=3D74bc0e4e-1cad-4540-ae4=
b-6a8304ba7746&amp;u=3Dhttps%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ie=
tf-rum-rue%2F</a><br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">DISCUSS:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">First of all thanks for working on =
this technology to make communication<br class=3D"">available and easy =
for special human beings. (I have worked with them to<br =
class=3D"">converter text to sign language in my bachelor hence had a =
special feeling<br class=3D"">while reading this specification).<br =
class=3D""><br class=3D"">I understood from the email discussions on the =
TSVART review<br class=3D"">(<a =
href=3D"https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-313273af=
-454445555731-b6cf7e1cc91dc9fe&amp;q=3D1&amp;e=3D74bc0e4e-1cad-4540-ae4b-6=
a8304ba7746&amp;u=3Dhttps%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Ftsv-=
art%2FZ_Ne5au4rCHwcig8bospMcLyzTc%2F" =
class=3D"">https://protect2.fireeye.com/v1/url?k=3D31323334-501d5122-31327=
3af-454445555731-b6cf7e1cc91dc9fe&amp;q=3D1&amp;e=3D74bc0e4e-1cad-4540-ae4=
b-6a8304ba7746&amp;u=3Dhttps%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Ft=
sv-art%2FZ_Ne5au4rCHwcig8bospMcLyzTc%2F</a>)<br class=3D"">that in the =
system RUI is deployed, we will have gateway(s) with two legs - one<br =
class=3D"">with WebRTC (client &lt;--&gt; gateway) and one with RUI =
client communicating with<br class=3D"">RUI server (gateway &lt;--&gt; =
server). With this understanding I have some points<br class=3D"">which =
I believe worth discussing.<br class=3D""><br class=3D"">- WebRTC =
communication will be congestion and rate controlled. This will use<br =
class=3D"">RTCP feedbacks to make the rate control and congestion =
control happen in the<br class=3D"">WebRTC peers. On the WebRTC part of =
the leg, this RTCP feedbacks will be<br class=3D"">available according =
to the WebRTC specification. However, this specification<br =
class=3D"">does not discuss how those RTCP feedback will be converted =
from the RUI<br class=3D"">server to RUI client (i.e the gateway) =
direction and vice versa. This will<br class=3D"">require the gateway to =
have such conversion functions to actually work. what<br class=3D"">is =
the thinking here? has this been considered? as I am not sure how is =
the<br class=3D"">network looks like between the RUI client and RUI =
server, there might be the<br class=3D"">Internet connecting them hence =
need to have congestion controlled traffic.<br class=3D""><br class=3D"">-=
 Thanks to Bernard Aboba for a comprehensive TSVART review of this draft =
and<br class=3D"">I would like to bring some issues, identified in that =
review, here to make<br class=3D"">sure they are addressed-<br =
class=3D""><br class=3D"">&nbsp;* clarification on the use of ICE<br =
class=3D"">&nbsp;* clarification on what is a WebRTC client, WebRTC =
server, gateway, RUI<br class=3D"">&nbsp;client and RUI server. I =
believe all four have been conceptually used in<br class=3D"">&nbsp;the =
specification without concretely defining their roles. for example - =
if<br class=3D"">&nbsp;server is mentioned it need to be distinguishable =
if it is WebRTC server or<br class=3D"">&nbsp;RUI server ( I noted that =
there are servers in this specification which are<br =
class=3D"">&nbsp;clearly =
understandable).</blockquote></blockquote></div></blockquote></div><br =
class=3D""></body></html>=

--Apple-Mail=_150EB26A-8C8E-4A37-97B1-5B87AFA4EF56--


From nobody Wed Jan 12 05:30:40 2022
Return-Path: <zaheduzzaman.sarker@ericsson.com>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC65B3A0C09; Wed, 12 Jan 2022 05:30:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level: 
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.576, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 e1in-GO1E1DP; Wed, 12 Jan 2022 05:30:28 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150080.outbound.protection.outlook.com [40.107.15.80]) (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 AAE883A0C0B; Wed, 12 Jan 2022 05:30:27 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=E4CVyO1QOBO6L/othFgn18HsPFysPm8JYc6MZF2hNZymvZjMUskzpgu92mHp0VO0RJGZaW99OmaIc/DsLqy18c3EsG36Awj7alwnZH2BhVp7Tu151RS02mLLezOuGUCVVmj+6LC5FDw9Tfdnj3txDnVF4kT8YxHfx9hizd/aaTQI8+RcxDdGRk1W/l/aP5S0+gu5DCfIt2aDZafUI2mkb0FYQO4phCK/s5lsHiPIn8AwM+bpmIVi4RArGVPLd1hlPhcTofUy0TvS9HPdDftLtnBnbuhw6i63OscyjPpKq2CYH6OeZC86S156s6ZY1XWPLQy2PyHgw5Gh8xjoGk3FwA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=MZGFIKAppLteTXypAAnKpASsoDJaZNhHS8WTpSk6ctU=; b=YcfWsfCj3G7y3lPVt63ygTiUVBuV3tL8BtDibLXNKy4CMJIbKAQ3n0/ULLwwDIjWvmcZwsTPCVseFT8X6z7K9Ve7G3v+31CrnobXh988AsbnXpF75r5lsSu+ehvZc1p52xElk7w+eM1q8dSzBf0L2yGERkYwRZ18sAUC0uXPxTKR4C6VRTAZKa1ly+2Tvo3KWDRyS1q6108nU4tuXhAfNx7GXsV+3BJbWbbiVuweSlSNnpb9AVmtkrrkcNDOOvaiH/k1hW3etUWo+2oW6f9q9Qr8nlDMy7J6wtJRh7vRdWF+KE8jcj3HwV/9uJUWQashvFHfRPyFiJrFJ50N3tIrkg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MZGFIKAppLteTXypAAnKpASsoDJaZNhHS8WTpSk6ctU=; b=T57beo/IFBm6OJOmfPlL3c+kIbs2wJfIPWEmoR3H7CkRnnwfGA/iDzgEO4HhoLzUZYfYJvo9qW7bP9mqoxUtD1TFBlAtSje56w5LzcWcYWQBTm8N9HITl+eTzzN2UWuemfKZ7MbEflzAsn5n0onab1mb6LHgM3UmTZiSXFAryPQ=
Received: from HE1PR07MB4187.eurprd07.prod.outlook.com (2603:10a6:7:98::23) by VI1PR07MB4093.eurprd07.prod.outlook.com (2603:10a6:803:2d::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4888.4; Wed, 12 Jan 2022 13:30:23 +0000
Received: from HE1PR07MB4187.eurprd07.prod.outlook.com ([fe80::1160:24d2:41aa:45cc]) by HE1PR07MB4187.eurprd07.prod.outlook.com ([fe80::1160:24d2:41aa:45cc%3]) with mapi id 15.20.4888.010; Wed, 12 Jan 2022 13:30:23 +0000
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
To: Brian Rosen <br@brianrosen.net>
CC: Paul Kyzivat <pkyzivat@alum.mit.edu>, "draft-ietf-rum-rue@ietf.org" <draft-ietf-rum-rue@ietf.org>, "rum@ietf.org" <rum@ietf.org>, The IESG <iesg@ietf.org>, "rum-chairs@ietf.org" <rum-chairs@ietf.org>
Thread-Topic: Zaheduzzaman Sarker's Discuss on draft-ietf-rum-rue-09: (with DISCUSS)
Thread-Index: AQHX8TRbrfnf/vtg4UaxBU6m+QHF0axAhkEAgB14VYCAAE0+gIABQtwA
Date: Wed, 12 Jan 2022 13:30:23 +0000
Message-ID: <0B674EBD-CE27-4A41-961A-268854F3F056@ericsson.com>
References: <163951822534.4738.15762238627618541835@ietfa.amsl.com> <583F4F4C-C323-45FE-9278-39D612793351@brianrosen.net> <4D20AFD9-943C-41F9-882D-7794B3938F88@ericsson.com> <A292F99E-4E40-4862-B9FE-8C84DF512011@brianrosen.net>
In-Reply-To: <A292F99E-4E40-4862-B9FE-8C84DF512011@brianrosen.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3654.120.0.1.13)
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4501fec3-b2a5-4391-6912-08d9d5cfafaf
x-ms-traffictypediagnostic: VI1PR07MB4093:EE_
x-microsoft-antispam-prvs: <VI1PR07MB4093BD5937D4B323BFFCD6019F529@VI1PR07MB4093.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: CGZjmM5C3bp8tvl+mAwVYEg/0tFImPF3vStaVTRKRjMlrralAxsQ+wdND2fPQWuy+9NGghAVvCCi7DOuzTRvFKDrTjcK8iKh7JMLd7lDPt0GBRJKVhAPwKOQ8spXap1KH4yZpYf/H4xZTd5/EW27H1kMZMBK1YkaG3L7cy6JUIuvcF4a5omIH/4Z5+GGEzWAElYJ3FpYEkKy7wq751gOzpnU7V3s2pIJvWDwO4T9AbFtwefRYMS+E7Aom75RRA1OyeJuyWTujf5UOSmNuSwbWIunIrmTImWbrNuBxIWtD2DpmVuyCpVdXPe0I8m2ou0TRY5eBwkkRSRXPfDcy9y9ccvoOCf/oHdAfhnWpk2C3o/7PkfF1GfL0iL2l77wUSNM9I/PjGyA2cwFL0keafUcxpbZO0v8rQhOFJI4yJ2JhhkkjvT/kztsEoL4hntIzHm2twI4SER1qhTQd450Lu7bxBmrO5D11rw4lGAZJhz5dsbRn5U23KLIZx/Xr6ETSOk5RpX93IvN18jau32hmk/ghiV4axpyD+TEaxuhXFMUIfxi+xrNG8pQT8L3TSQDZf5xVicGxTL7BafHrLzV7pFH10ZpCcfuejht09kR3ZxVZagqGgd1ZUzlJ5NR6g8cAnXXdNie3MMnUSF2JRcTX/+KD4kSJTAU2FmiokMK+j50a+FfcULRS9FeQjVV1f8GWRgxNJLUOKiPJK6Q9u6rEIstEOnoLW+VXApYMNxPK0otuSSLJ4vHCNlFB+gAPFpR4HzH
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB4187.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(13230001)(4636009)(366004)(66574015)(66476007)(316002)(91956017)(6916009)(64756008)(83380400001)(76116006)(86362001)(82960400001)(6512007)(66946007)(6506007)(54906003)(2906002)(38070700005)(4326008)(2616005)(38100700002)(5660300002)(53546011)(8676002)(6486002)(8936002)(122000001)(508600001)(71200400001)(44832011)(33656002)(186003)(66446008)(66556008)(26005)(99936003)(36756003)(45980500001)(20210929001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?utf-8?B?eXFsV2FrMEU4Y1dCbmd0ZGpDck9NbVJqQ3h0TnBwZGNEUUN4eWhjNzM4R2dY?= =?utf-8?B?cS9QYUd5M1FKcnNMWEtCM2ZUWjBHdmZLcmRQNjZ6K1owbmhsOHhQeXFtZ2JF?= =?utf-8?B?SDZYVzNSNmpobHE4TURQeVlGOVRiempnTFJmajVBK0F0eFZlN0RnUllLdVkx?= =?utf-8?B?dTU0MU9STVd5M2FHTUdYaHZ2N0hBR3Ztdmh5eFFTaDdVaU1GT2ZlMzNVYnZ1?= =?utf-8?B?OGxydW5BMk5DWXVxWlU2OXUySkRJREI4SVF3bEsrczFPczVrQkpaeG03Z09C?= =?utf-8?B?Yno2UEpPdzNMb3dHUnlHUDNRc1lqMmlSWVJ6TzJ6Z1RkVjFvNENuT29ud3Ny?= =?utf-8?B?MWFQNnBLWW5IeDAyTDltMVBBek43ZGVUWDhIbU1JUkI5WnJpWFB6aWZ5bG03?= =?utf-8?B?aHYwWk16T3VOM2t4SHNhNWl1L3l4eU40MkQwK1N1NGk5eUlBTGlySWRhWUh4?= =?utf-8?B?UXU5QjFqdDVYYVMwdVNZQk1LYUo3MTczQ2M4dHJ6d21JVmd0WGN4OXVoYkQy?= =?utf-8?B?OTgrTk93cjJhNjVTOGVUM0VtTkYyYmp1enVSbVRtOUwxTGRCTlo5TWJab0or?= =?utf-8?B?ZzluMWErM0taZnFQY3kxNVJOR3lzWVBVKzJVK0xiWFJISEpPMk5IRnJCQW8w?= =?utf-8?B?TkJzbjl2S3RvanRKY3lBNkhNTUlqMGkza3RmVG1PQ0RHbGxPVzQwZ1J4b1ha?= =?utf-8?B?WWhVb0xiOHhrTzRBQStxcUxueEJvU1BIVk9TaGV0TXJ2T3BFNFduNXVXdDB6?= =?utf-8?B?dnBxS0E0NDhwUmdJcEMwLy91d1lXTVh3aVM4a2l3MEg5enBKWmJDQmJnVUZB?= =?utf-8?B?K2NLZUxOTUs1aXVDMGgzcE15a1RUekN2U0t1K3hrbWtBSGpsSXpNY3Y3T3Vq?= =?utf-8?B?dnllQlRrL2p1aVFWU3gzRGtmQk1PV29HQ3M5cWpqZlRTdmxveHhzR1BwZU1u?= =?utf-8?B?TXdCczJJckxUYWwwK3dNQnVYTG9Nangwcm5OZlRkNTM5enhLclNtSURYYUxC?= =?utf-8?B?ZVpnZ29rS0R1SWU4bis3aDBvWlEyamQ1UkRtUHlLUGg3Z3M4NnhMTlV5SUty?= =?utf-8?B?N2pzQ29jWXFZb2tzajRYNzNGOWVXNTRrYXFUZ3lTWGV0Z0x5ai9MMTdBMDFp?= =?utf-8?B?eVMvNWlPMFZVNUVrOTFVVWFVMzgxME8zTzduUDZ3ZE9iSDV6NHpOTHJlek40?= =?utf-8?B?MnQzT085dFBDNGVoMTBiYzVyVXE2N2ozMUZLUVlpbkVheDQ2TjZhR1VRU1Q3?= =?utf-8?B?SkVkcUFjaVZpU1NWWHRZZnhRMGFjVVF5ZnFqblBzL0NSQXQvNjh6RUk3RE1V?= =?utf-8?B?UzBUa04wcXpZUUVkYlBkYXJOT0MwaGtTNDV5Z255REZoUkJkcnhTTXV6djBV?= =?utf-8?B?M2dBL0RmZ0dhMU04Y3owZCt5K2VGc3FRT2JkYWdNbWNWZlR5K3FBK01Yb3FE?= =?utf-8?B?cmdZTUlyYW1rK3NaV0QxMkcyM1NlZmxtTVdBbnBLMk1ET3BoeUs0bkoweWJD?= =?utf-8?B?YjFlKzZteXRiQkZqTE1qM3k5RVl0MlNGN3BNeWNaUjJmSFJWU3hUS3NHdk1n?= =?utf-8?B?TERvZnhQR05NMVV4dkxiczVRdUdudExWKzJ5ZWNsVm5VSm9OSnN4RU5xNE8y?= =?utf-8?B?bW5qSDhRd1hMNGFFRXdiOUVNNkt3MjFMejJSTWg3ZURLbEhqWERoeVQxS2ht?= =?utf-8?B?N3VnVVUxNkx1ZjlLSFhkK1htbFYxanYyR29UTGc4Rnk5dzV4eGVIRkVmcWxz?= =?utf-8?B?cU5MbnZiM3A1b0tkTnhDLzI4RlFGbGZxVHQwSy9zcUNXeFE0bm96L25HUkhP?= =?utf-8?B?amIrZW9Xa3BVT2JqSjI2OHluOWZYM00rZE9SanU3bnA0Mkk0emJnUGlTQ2d1?= =?utf-8?B?L3hDNVpucUJzQys2ZFJoY3l5OFo1a3k5RVVVYVJ5Z0xZTm5PYnFsZ09YdkVl?= =?utf-8?B?MGd3TnFacUpUT2M3VXZUc1B1L0NyYVRieDNJY0ljcnpPeTlKSHpJdk1SQkNV?= =?utf-8?B?Y25id2MzWldoZWJHVjkrY0ZKeDZXdkdqMDBDbmxIdXIyVTN1QWNDNTM0VlRX?= =?utf-8?B?eWQrbWh4V0xZenF4UDUwREtQbTBDWkNEUE9Xa1NGeExOOFQxQ3huVnBWRHJ1?= =?utf-8?B?dmdOZzdsalJQZGhkeTNuTFByN1pmNEVEWWhIRGhDNWZLTnJvdXVEYXB6aHdp?= =?utf-8?B?SGQvNDlpMGNZNjhwejk1c1BLZmptSXQvSkZHb2dvV1NnbzVEV0w0TUg2b3M5?= =?utf-8?B?UDdrRjlPTStRWExmcHhFWTlCOWQ2VFl1c3lYUk9KYnoyTXdVMUlkN2ZBSjVw?= =?utf-8?B?d1o2SGRKV1VwSmN4RzBDRFRJU29qUktPYU4xQmVJQ1V5NjVuZDU0Zz09?=
Content-Type: multipart/signed; boundary="Apple-Mail=_CAE23B3B-C966-42EC-B144-0F3E9CD6F69E"; protocol="application/pkcs7-signature"; micalg=sha-256
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB4187.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4501fec3-b2a5-4391-6912-08d9d5cfafaf
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jan 2022 13:30:23.1153 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: VG3bZcWxc2FRT5A4RU1XLuJipkTFskp3+FJcc4N/SrB/wIdByzExaXEcoFGk8BhIaU7H0TsPFQEVcunRBOMhFtO5WTVRwntXcuDn8E8B/aYelu1jZr369FZsupFKsMiV
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4093
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/36l7Xb7oHfzmqOvCF5mXfMZ8k10>
Subject: Re: [Rum] Zaheduzzaman Sarker's Discuss on draft-ietf-rum-rue-09: (with DISCUSS)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jan 2022 13:30:33 -0000

--Apple-Mail=_CAE23B3B-C966-42EC-B144-0F3E9CD6F69E
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_70D7F909-D68A-4F66-918E-4BB29617F5BF"


--Apple-Mail=_70D7F909-D68A-4F66-918E-4BB29617F5BF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 11 Jan 2022, at 19:14, Brian Rosen <br@brianrosen.net> wrote:
>=20
>=20
>=20
>> On Jan 11, 2022, at 8:38 AM, Zaheduzzaman Sarker =
<zaheduzzaman.sarker@ericsson.com =
<mailto:zaheduzzaman.sarker@ericsson.com>> wrote:
>>=20
>>=20
>>=20
>>> On 23 Dec 2021, at 20:36, Brian Rosen <br@brianrosen.net =
<mailto:br@brianrosen.net>> wrote:
>>>=20
>>> Thank you for these comments.
>>>=20
>>> We did not have a specific conversation on handling rate control and =
congestion feedback. =20
>>> The RUE server and client are required to support RTCP, so I think =
that part is easy.  Both ends are required to support the WebRTC media =
spec, so I think if it happened if both RUE clients were implemented =
with WebRTC clients, everything would work the way we expect it to.
>>>=20
>>> So I think the issue reduces to a situation where one end is a =
WebRTC client, and the other is not.  They both have to implement the =
media congestion mechanisms.  They both have RTCP to work with.  SDP =
negotiation should work,
>> This sounds like requirements to me, is this described in the =
document?
> The requirements that both have to implement RTCP, the media =
congestion mechanisms, and SDP negotiations are already in the document, =
yes.
Ok. Good.
>=20
>>>=20
>>> I=E2=80=99m down to thinking the gateway doesn=E2=80=99t have to =
mess with this.  It=E2=80=99s possible that the gateway could have more =
expansive goals to be backwards compatible with existing VRS devices =
that don=E2=80=99t conform to this document, and I could imagine that =
there might need to be some work there.  But that would not be covered =
in this document.=20
>> Would be good to be explicit about this in this document. The thing =
if the gateway does not want to mess with the RTCP signalling then the =
signalling and the negotiation of what to use for rate and congestion =
control need to be end to end. This should be clear in this document.
> But that is why the document requires support for 8825/8834.  I will =
add a statement that "Conformance to this document allows end-to-end =
RTCP and media congestion control for audio and video."  =E2=80=9CAllows=E2=
=80=9D is the right word, because many provides anchor media.
Looks good to me.
>=20
>>> I=E2=80=99m not personally a WebRTC expert although I had help =
writing the text from some folks who were.  So, II easily could be =
missing something here.
>>>=20
>>> On =E2=80=9CClarification of the use of ICE=E2=80=9D, I propose to =
add "Implementations MUST implement full ICE, although they MAY =
interwork with User Agents that implement ICE-lite.=E2=80=9D  There is =
an unqualified requirement to support RFC8839.
>> OK.
>>>=20
>>> I propose to add the following text in the media section where we =
introduce the WebRTC media specs:
>>> To use WebRTC with this document, a gateway that presents a WebRTC =
server interface towards a browser, and a RUE client interface towards a =
provider is assumed.  The gateway would interwork signaling, and as =
noted below, interwork at least any real time text media, in order to =
allow a standard browser baed WebRTC client to be a VRS client.  The =
combination of the browser client and the gateway would be a RUE user.
>> I think interworking will also be necessary for A/V media traffic
> I certainly hope not.  Between conforming RUEs, there won=E2=80=99t be =
any issues.  The only things I worry about are talking to older devices =
that may not implement all the mechanisms and where SDP negotiation =
might not result in a compatible option.  =20
And I understand you are saying those use case is out of the scope of =
this document. I would expect this to be explicit in the specification.

//Zahed


--Apple-Mail=_70D7F909-D68A-4F66-918E-4BB29617F5BF
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><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 11 Jan 2022, at 19:14, Brian Rosen &lt;<a =
href=3D"mailto:br@brianrosen.net" class=3D"">br@brianrosen.net</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D"">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; line-break: after-white-space;" class=3D""><br class=3D""><div =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jan 11, 2022, at 8:38 AM, Zaheduzzaman Sarker &lt;<a =
href=3D"mailto:zaheduzzaman.sarker@ericsson.com" =
class=3D"">zaheduzzaman.sarker@ericsson.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">On 23 =
Dec 2021, at 20:36, Brian Rosen &lt;<a href=3D"mailto:br@brianrosen.net" =
class=3D"">br@brianrosen.net</a>&gt; wrote:<br class=3D""><br =
class=3D"">Thank you for these comments.<br class=3D""><br class=3D"">We =
did not have a specific conversation on handling rate control and =
congestion feedback. &nbsp;<br class=3D"">The RUE server and client are =
required to support RTCP, so I think that part is easy. &nbsp;Both ends =
are required to support the WebRTC media spec, so I think if it happened =
if both RUE clients were implemented with WebRTC clients, everything =
would work the way we expect it to.<br class=3D""><br class=3D"">So I =
think the issue reduces to a situation where one end is a WebRTC client, =
and the other is not. &nbsp;They both have to implement the media =
congestion mechanisms. &nbsp;They both have RTCP to work with. &nbsp;SDP =
negotiation should work,<br class=3D""></blockquote><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"">This sounds like requirements to =
me, is this described in the document?</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>The requirements =
that both have to implement RTCP, the media congestion mechanisms, and =
SDP negotiations are already in the document, =
yes.</div></div></div></blockquote>Ok. Good.<br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D""><br class=3D""></div><div =
class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">I=E2=80=99m down to thinking the gateway doesn=E2=80=99t have =
to mess with this. &nbsp;It=E2=80=99s possible that the gateway could =
have more expansive goals to be backwards compatible with existing VRS =
devices that don=E2=80=99t conform to this document, and I could imagine =
that there might need to be some work there. &nbsp;But that would not be =
covered in this document.<span =
class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D""></blockquote><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"">Would be good to be explicit about this in this document. The =
thing if the gateway does not want to mess with the RTCP signalling then =
the signalling and the negotiation of what to use for rate and =
congestion control need to be end to end. This should be clear in this =
document.</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>But that is why the document =
requires support for 8825/8834. &nbsp;I will add a statement that =
"Conformance to this document allows end-to-end RTCP and media =
congestion control for audio and video." &nbsp;=E2=80=9CAllows=E2=80=9D =
is the right word, because many provides anchor =
media.</div></div></div></blockquote>Looks good to me.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;" class=3D""><div class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">I=E2=80=99m not personally a WebRTC =
expert although I had help writing the text from some folks who were. =
&nbsp;So, II easily could be missing something here.<br class=3D""><br =
class=3D"">On =E2=80=9CClarification of the use of ICE=E2=80=9D, I =
propose to add "Implementations MUST implement full ICE, although they =
MAY interwork with User Agents that implement ICE-lite.=E2=80=9D =
&nbsp;There is an unqualified requirement to support RFC8839.<br =
class=3D""></blockquote><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"">OK.</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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D"">I propose to add the =
following text in the media section where we introduce the WebRTC media =
specs:<br class=3D"">To use WebRTC with this document, a gateway that =
presents a WebRTC server interface towards a browser, and a RUE client =
interface towards a provider is assumed. &nbsp;The gateway would =
interwork signaling, and as noted below, interwork at least any real =
time text media, in order to allow a standard browser baed WebRTC client =
to be a VRS client. &nbsp;The combination of the browser client and the =
gateway would be a RUE user.<br class=3D""></blockquote><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"">I think interworking will also =
be necessary for A/V media traffic</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>I certainly hope =
not. &nbsp;Between conforming RUEs, there won=E2=80=99t be any issues. =
&nbsp;The only things I worry about are talking to older devices that =
may not implement all the mechanisms and where SDP negotiation might not =
result in a compatible option. =
&nbsp;&nbsp;</div></div></div></blockquote>And I understand you are =
saying those use case is out of the scope of this document. I would =
expect this to be explicit in the specification.</div><div><br =
class=3D""></div><div>//Zahed</div><br class=3D""></body></html>=

--Apple-Mail=_70D7F909-D68A-4F66-918E-4BB29617F5BF--

--Apple-Mail=_CAE23B3B-C966-42EC-B144-0F3E9CD6F69E
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCBf4w
ggX6MIID4qADAgECAg8BdUoQAyUVYjB/ZVVBDvMwDQYJKoZIhvcNAQELBQAwRzELMAkGA1UEBhMC
U0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENB
IHYzMB4XDTIwMTAyMTA3MjkyNVoXDTIzMTAyMjA3MjkyNFowYjERMA8GA1UECgwIRXJpY3Nzb24x
HDAaBgNVBAMME1phaGVkdXp6YW1hbiBTYXJrZXIxLzAtBgkqhkiG9w0BCQEWIHphaGVkdXp6YW1h
bi5zYXJrZXJAZXJpY3Nzb24uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmjJb
Zy6kdvqWwiZanvVnqKsb990pSFndyIgFspP9mArDxvEX0oqrBugPRyJSp1KA0KDPo9L3SBHk7pbp
hJDbJAxPdPAbyZ+DMHV/UtQSUUpp8rRoYNEA6Ew3OlG5Sz1Nhq9AcjSKeOZKunnJInh/y435NACo
co2uP/6Gk0XBeB3qE645aIqpbsO3DCUMOWxWIjjTRFQ/TqoUjbIwfw+rO64Y3qEa96Ibj63AoDtt
3gwmtpFkVm5C44XfK7J4LyXIIz4TQqnfxlfoJ+ttFMfV1ZV1OvA7xXj0yO/6btsktlktpgMvow87
HPkSRtsLXQoRhU4E1zclEPWz5SzhUXuOvwIDAQABo4IBxjCCAcIwHwYDVR0jBBgwFoAUHHsZnpec
dqwgPdjc45Fq49stplMwHQYDVR0OBBYEFJlMp3EJ+P/dXOLqvbT718jDfw1mMA4GA1UdDwEB/wQE
AwIFoDBVBgNVHSAETjBMMEoGDCsGAQQBgg8CAwEBEjA6MDgGCCsGAQUFBwIBFixodHRwczovL3Jl
cG9zaXRvcnkudHJ1c3QudGVsaWFzb25lcmEuY29tL0NQUzArBgNVHREEJDAigSB6YWhlZHV6emFt
YW4uc2Fya2VyQGVyaWNzc29uLmNvbTBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9lcmljc3Nvbm5saW5kaXZpZHVhbGNhdjMuY3JsMB0GA1UdJQQWMBQGCCsGAQUF
BwMEBggrBgEFBQcDAjCBggYIKwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIu
dHJ1c3QudGVsaWEuY29tMEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEu
Y29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2My5jZXIwDQYJKoZIhvcNAQELBQADggIBAD1OD1xt
xE0jjc12/QXWWe8Cv2q1ZRn1PwacRWFJMyprPB6CiR6YBnmovYCyvCrNCqzsNaTpQLAQeKxwpmOg
fZ1SrdyqQKjtCiAlQynqV+dX5VAA6kt/fM67jZbU+lmzw3/2mXNQKTnor1Ax2bJjtZB2DzvTmSPd
EybZWxSfMMSsZHA4GLPGEHws+7fHeZ6RSRsAolXPTLGu7gxPkYDtaUzI9M8Z9GKz2UC/wNP2UieR
95h5TnKiqAWLqAxwzcu7GVWIdJ4rzgOenaNg56OM5q87+X90ZSAODWAPnxdDgVGspHbxt2g9cQYb
pkKiHWrOuLIWd8B/oGbE1ruKqcFKC39aYkd7JRlHjkNfU/IpymDoGd3RYMtsJW2JvinuZMmMZ5F5
Xpw1yJuSPrq5tHbPx7S6hjqYhd9VkRLbKkprw9+HJZBrUrhrUx4HVF2/bo+WG9GCTdQUsm8JQt9B
zpRh2ySNBQZfUn1WN3Q+lMcGSdItCNYH6HnXGrAmv+oDZ1pnp9z+NNmDoNMAHaFvwYCFd9/HvjJu
5kL90Fp3UEJQAk6X+2+ElrfNplUz16nAOBvxcY55R5eI9SDD8MmNfADekiMldSwB9LjMrqBhwWeE
UblghhtceJ3iqg35LURo+KXdL3h0/IodZPBYoMLMhMbDdYokIUY+mWW5W1T1WzV9PyWqMYICyjCC
AsYCAQEwWjBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNz
c29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCDwF1ShADJRViMH9lVUEO8zANBglghkgBZQMEAgEFAKCC
AUEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMjIwMTEyMTMzMDIy
WjAvBgkqhkiG9w0BCQQxIgQgxtq/rSWc2qM7vDpgp7PEn29LyvzacDRRA23Z26CWtrUwaQYJKwYB
BAGCNxAEMVwwWjBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVy
aWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCDwF1ShADJRViMH9lVUEO8zBrBgsqhkiG9w0BCRAC
CzFcoFowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBIHYzAg8BdUoQAyUVYjB/ZVVBDvMwDQYJKoZIhvcNAQELBQAEggEA
ZRTAScj29KOi51k9mINSDSFiTO9BMvQU1hu6Vmj/5HPbI00tKLBOiPhBkftY3MFyLjQFqTZyuxDm
h8JgY9MefNTnCF3XVcEdWtofSRVFpH/BAhNM1V6mLcQWdAIdhy0OGAYPGQvpa+akyR41s8jFwacu
FHv8Zdb1NRq9hyyZzB2EOtP69bAVrw8++QPZ3Y25pD9hvzB1nc80NKk8mY/h0jn4bhIzZsbGCyZx
2iSaUupCoCECiewTGSsb3mQ4p6Rg39xE58sD0dVnszum1nWMsGgBbA7DbU2H3FrDQm5rkq+Tzd2v
yzCxTyG4acolnZWk4Npof2Vk22XfrO3dJQIdYgAAAAAAAA==

--Apple-Mail=_CAE23B3B-C966-42EC-B144-0F3E9CD6F69E--


From nobody Wed Jan 12 08:42:32 2022
Return-Path: <br@brianrosen.net>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6CE63A141C for <rum@ietfa.amsl.com>; Wed, 12 Jan 2022 08:42:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level: 
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20210112.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id weUFYE6cfI0j for <rum@ietfa.amsl.com>; Wed, 12 Jan 2022 08:42:26 -0800 (PST)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 0E1E33A141F for <rum@ietf.org>; Wed, 12 Jan 2022 08:42:26 -0800 (PST)
Received: by mail-io1-xd33.google.com with SMTP id u8so4514440iol.5 for <rum@ietf.org>; Wed, 12 Jan 2022 08:42:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=flR9ZW+YYygZh8tCWqc2cd4/QFGlMyaKSSj1vvliAXg=; b=F9bMmeXkt5z1q4a0CbFLZ1GFBdIG4EslTO9pT8eB/70Y+zlf8YLvgpjRjZVrQjaLgT QSJsNu85KRLAMyKZrBMPTWpM2pp64jq28SGaFV7hQ51X59ZHf4cOCoHqSpcZ2v3d0LSW yWCnJ+Xfbib6PQeRT3d2LPuYSAYBXdCnTfODrHM8ocTrSLgXY80DQVV8XBz6xrA2rnPS 6nnbfyK0OQbAgRrC0L7N/oWrA5zcny2JM+s+EqGDgNO+li6TypmW+hUfF5il563D7Iqs NnSGQkLYV5jaBR35/7ZnDGrP3JXTWWYt2fk6CsyL6kyD+SYd4PftpiRTtgqYvH063GtO S6hQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=flR9ZW+YYygZh8tCWqc2cd4/QFGlMyaKSSj1vvliAXg=; b=1kL/ozHzWuYjoa+Sxm9ezl/jDtqukUiTX++PhsG93bZxTlhg90/jfwK8Avhmas+NqP BVvM4rSBP+VTz00mcZ5Hb/wxTK3OTlRNNPBityzoPz/9qjxglqHWGYEH1MMyvFA8UgN3 CerAmry6zpo0zsIftZxnTxqF5jsHCNX8F75uJjapLzw7FnylG6f4nheIpKDD8hhP5ObQ KVsVmwn2AWdW9tqcthpALhare4Do5Y4mQiCtptPeLosnG3Wt5KNTXmAqz0DtNrRtsvb1 2TrbPVHN02Rs9Rh8nIXdaq1YNFf/Rurjfq1f+JS0PLojopc3iJzmlI5arCWtrwYspWVy 30HQ==
X-Gm-Message-State: AOAM530kbRb3rRojei10tfWHYe2+uh0v2v1jJb9NJadGmUjfv06vqpzD jMAJUEDIO1Dx5/oaJ9OPEUVhEw==
X-Google-Smtp-Source: ABdhPJwTOR5t7mUsBScyNxybMKhucBsbAMLDzz2bMJ+CuamCxJSYj5cbsnDVvcjCwxhapNx1GNZWxA==
X-Received: by 2002:a02:a898:: with SMTP id l24mr264929jam.290.1642005744316;  Wed, 12 Jan 2022 08:42:24 -0800 (PST)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id g6sm207653iow.34.2022.01.12.08.42.23 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Jan 2022 08:42:23 -0800 (PST)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <3E20B6A0-6EE3-4028-8E13-6CD5C804CF4E@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_07A3DCED-EF90-454E-A6A6-66B7562A5A84"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\))
Date: Wed, 12 Jan 2022 11:42:20 -0500
In-Reply-To: <0B674EBD-CE27-4A41-961A-268854F3F056@ericsson.com>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "draft-ietf-rum-rue@ietf.org" <draft-ietf-rum-rue@ietf.org>, "rum@ietf.org" <rum@ietf.org>, The IESG <iesg@ietf.org>, "rum-chairs@ietf.org" <rum-chairs@ietf.org>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
References: <163951822534.4738.15762238627618541835@ietfa.amsl.com> <583F4F4C-C323-45FE-9278-39D612793351@brianrosen.net> <4D20AFD9-943C-41F9-882D-7794B3938F88@ericsson.com> <A292F99E-4E40-4862-B9FE-8C84DF512011@brianrosen.net> <0B674EBD-CE27-4A41-961A-268854F3F056@ericsson.com>
X-Mailer: Apple Mail (2.3693.20.0.1.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/tOOKf_WTWaSE093sNHSYXnUssEc>
Subject: Re: [Rum] Zaheduzzaman Sarker's Discuss on draft-ietf-rum-rue-09: (with DISCUSS)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jan 2022 16:42:31 -0000

--Apple-Mail=_07A3DCED-EF90-454E-A6A6-66B7562A5A84
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On the last point, the text already says:
While there are some accommodations in this document to maximize =
backwards compatibility with other devices and services that are used to =
provide VRS service, backwards compatibility is not a requirement, and =
some interwork may be required to allow direct video calls to older =
devices.=20

> On Jan 12, 2022, at 8:30 AM, Zaheduzzaman Sarker =
<zaheduzzaman.sarker@ericsson.com> wrote:
>=20
>=20
>=20
>> On 11 Jan 2022, at 19:14, Brian Rosen <br@brianrosen.net =
<mailto:br@brianrosen.net>> wrote:
>>=20
>>=20
>>=20
>>> On Jan 11, 2022, at 8:38 AM, Zaheduzzaman Sarker =
<zaheduzzaman.sarker@ericsson.com =
<mailto:zaheduzzaman.sarker@ericsson.com>> wrote:
>>>=20
>>>=20
>>>=20
>>>> On 23 Dec 2021, at 20:36, Brian Rosen <br@brianrosen.net =
<mailto:br@brianrosen.net>> wrote:
>>>>=20
>>>> Thank you for these comments.
>>>>=20
>>>> We did not have a specific conversation on handling rate control =
and congestion feedback. =20
>>>> The RUE server and client are required to support RTCP, so I think =
that part is easy.  Both ends are required to support the WebRTC media =
spec, so I think if it happened if both RUE clients were implemented =
with WebRTC clients, everything would work the way we expect it to.
>>>>=20
>>>> So I think the issue reduces to a situation where one end is a =
WebRTC client, and the other is not.  They both have to implement the =
media congestion mechanisms.  They both have RTCP to work with.  SDP =
negotiation should work,
>>> This sounds like requirements to me, is this described in the =
document?
>> The requirements that both have to implement RTCP, the media =
congestion mechanisms, and SDP negotiations are already in the document, =
yes.
> Ok. Good.
>>=20
>>>>=20
>>>> I=E2=80=99m down to thinking the gateway doesn=E2=80=99t have to =
mess with this.  It=E2=80=99s possible that the gateway could have more =
expansive goals to be backwards compatible with existing VRS devices =
that don=E2=80=99t conform to this document, and I could imagine that =
there might need to be some work there.  But that would not be covered =
in this document.=20
>>> Would be good to be explicit about this in this document. The thing =
if the gateway does not want to mess with the RTCP signalling then the =
signalling and the negotiation of what to use for rate and congestion =
control need to be end to end. This should be clear in this document.
>> But that is why the document requires support for 8825/8834.  I will =
add a statement that "Conformance to this document allows end-to-end =
RTCP and media congestion control for audio and video."  =E2=80=9CAllows=E2=
=80=9D is the right word, because many provides anchor media.
> Looks good to me.
>>=20
>>>> I=E2=80=99m not personally a WebRTC expert although I had help =
writing the text from some folks who were.  So, II easily could be =
missing something here.
>>>>=20
>>>> On =E2=80=9CClarification of the use of ICE=E2=80=9D, I propose to =
add "Implementations MUST implement full ICE, although they MAY =
interwork with User Agents that implement ICE-lite.=E2=80=9D  There is =
an unqualified requirement to support RFC8839.
>>> OK.
>>>>=20
>>>> I propose to add the following text in the media section where we =
introduce the WebRTC media specs:
>>>> To use WebRTC with this document, a gateway that presents a WebRTC =
server interface towards a browser, and a RUE client interface towards a =
provider is assumed.  The gateway would interwork signaling, and as =
noted below, interwork at least any real time text media, in order to =
allow a standard browser baed WebRTC client to be a VRS client.  The =
combination of the browser client and the gateway would be a RUE user.
>>> I think interworking will also be necessary for A/V media traffic
>> I certainly hope not.  Between conforming RUEs, there won=E2=80=99t =
be any issues.  The only things I worry about are talking to older =
devices that may not implement all the mechanisms and where SDP =
negotiation might not result in a compatible option.  =20
> And I understand you are saying those use case is out of the scope of =
this document. I would expect this to be explicit in the specification.
>=20
> //Zahed


--Apple-Mail=_07A3DCED-EF90-454E-A6A6-66B7562A5A84
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"">On =
the last point, the text already says:<div class=3D""><div =
style=3D"margin: 0px; font-stretch: normal; line-height: normal; =
font-family: Menlo; color: rgba(0, 0, 0, 0.85); background-color: =
rgb(255, 255, 255);" class=3D"">While there are some accommodations in =
this document to maximize backwards compatibility with other devices and =
services that are used to provide VRS service, backwards compatibility =
is not a requirement, and some interwork may be required to allow direct =
video calls to older devices.&nbsp;</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Jan 12, 2022, at 8:30 AM, =
Zaheduzzaman Sarker &lt;<a =
href=3D"mailto:zaheduzzaman.sarker@ericsson.com" =
class=3D"">zaheduzzaman.sarker@ericsson.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><div 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""><br =
class=3D"Apple-interchange-newline"><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On 11 Jan 2022, at 19:14, Brian =
Rosen &lt;<a href=3D"mailto:br@brianrosen.net" =
class=3D"">br@brianrosen.net</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><br class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Jan =
11, 2022, at 8:38 AM, Zaheduzzaman Sarker &lt;<a =
href=3D"mailto:zaheduzzaman.sarker@ericsson.com" =
class=3D"">zaheduzzaman.sarker@ericsson.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><br class=3D"" =
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;"><br class=3D"" =
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;"><blockquote =
type=3D"cite" class=3D"" style=3D"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;">On 23 Dec 2021, =
at 20:36, Brian Rosen &lt;<a href=3D"mailto:br@brianrosen.net" =
class=3D"">br@brianrosen.net</a>&gt; wrote:<br class=3D""><br =
class=3D"">Thank you for these comments.<br class=3D""><br class=3D"">We =
did not have a specific conversation on handling rate control and =
congestion feedback. &nbsp;<br class=3D"">The RUE server and client are =
required to support RTCP, so I think that part is easy. &nbsp;Both ends =
are required to support the WebRTC media spec, so I think if it happened =
if both RUE clients were implemented with WebRTC clients, everything =
would work the way we expect it to.<br class=3D""><br class=3D"">So I =
think the issue reduces to a situation where one end is a WebRTC client, =
and the other is not. &nbsp;They both have to implement the media =
congestion mechanisms. &nbsp;They both have RTCP to work with. &nbsp;SDP =
negotiation should work,<br class=3D""></blockquote><span class=3D"" =
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;">This sounds like requirements to me, is =
this described in the document?</span><br class=3D"" 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;"></div></blockquote>The requirements that both =
have to implement RTCP, the media congestion mechanisms, and SDP =
negotiations are already in the document, =
yes.</div></div></div></blockquote>Ok. Good.<br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div class=3D""><br class=3D""></div><div =
class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D"" style=3D"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;"><br class=3D"">I=E2=80=99m down to thinking the gateway doesn=E2=80=
=99t have to mess with this. &nbsp;It=E2=80=99s possible that the =
gateway could have more expansive goals to be backwards compatible with =
existing VRS devices that don=E2=80=99t conform to this document, and I =
could imagine that there might need to be some work there. &nbsp;But =
that would not be covered in this document.<span =
class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D""></blockquote><span class=3D"" 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;">Would =
be good to be explicit about this in this document. The thing if the =
gateway does not want to mess with the RTCP signalling then the =
signalling and the negotiation of what to use for rate and congestion =
control need to be end to end. This should be clear in this =
document.</span><br class=3D"" 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;"></div></blockquote>But that is why the document =
requires support for 8825/8834. &nbsp;I will add a statement that =
"Conformance to this document allows end-to-end RTCP and media =
congestion control for audio and video." &nbsp;=E2=80=9CAllows=E2=80=9D =
is the right word, because many provides anchor =
media.</div></div></div></blockquote>Looks good to me.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;"><div class=3D""><br class=3D""><blockquote=
 type=3D"cite" class=3D""><div class=3D""><blockquote type=3D"cite" =
class=3D"" style=3D"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;">I=E2=80=99m not personally a WebRTC expert =
although I had help writing the text from some folks who were. &nbsp;So, =
II easily could be missing something here.<br class=3D""><br class=3D"">On=
 =E2=80=9CClarification of the use of ICE=E2=80=9D, I propose to add =
"Implementations MUST implement full ICE, although they MAY interwork =
with User Agents that implement ICE-lite.=E2=80=9D &nbsp;There is an =
unqualified requirement to support RFC8839.<br =
class=3D""></blockquote><span class=3D"" 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;">OK.</span><br class=3D"" 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;"><blockquote type=3D"cite" class=3D"" =
style=3D"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;"><br class=3D"">I propose to add the following =
text in the media section where we introduce the WebRTC media specs:<br =
class=3D"">To use WebRTC with this document, a gateway that presents a =
WebRTC server interface towards a browser, and a RUE client interface =
towards a provider is assumed. &nbsp;The gateway would interwork =
signaling, and as noted below, interwork at least any real time text =
media, in order to allow a standard browser baed WebRTC client to be a =
VRS client. &nbsp;The combination of the browser client and the gateway =
would be a RUE user.<br class=3D""></blockquote><span class=3D"" =
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;">I think interworking will also be necessary =
for A/V media traffic</span><br class=3D"" 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;"></div></blockquote>I certainly hope not. =
&nbsp;Between conforming RUEs, there won=E2=80=99t be any issues. =
&nbsp;The only things I worry about are talking to older devices that =
may not implement all the mechanisms and where SDP negotiation might not =
result in a compatible option. =
&nbsp;&nbsp;</div></div></div></blockquote>And I understand you are =
saying those use case is out of the scope of this document. I would =
expect this to be explicit in the specification.</div><div =
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""><br =
class=3D""></div><div 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"">//Zahed</div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_07A3DCED-EF90-454E-A6A6-66B7562A5A84--


From nobody Thu Jan 13 00:37:22 2022
Return-Path: <zaheduzzaman.sarker@ericsson.com>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 193483A0C3C; Thu, 13 Jan 2022 00:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.675
X-Spam-Level: 
X-Spam-Status: No, score=-2.675 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.576, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 Sz_YrWO76AcJ; Thu, 13 Jan 2022 00:37:05 -0800 (PST)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on20624.outbound.protection.outlook.com [IPv6:2a01:111:f400:7e1b::624]) (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 6AEAE3A0C38; Thu, 13 Jan 2022 00:37:04 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kJlV56eVMcTRj8bWnuyOi/MdcquWJDIfas/lqc/IMxV+S3iYYslCgtrR4F0WAwprT+67zr+/I7f2D0I6LqbEaKibYcTPApNdL44qqdVim5yWFN48wkt7S0PywDAO1uurrN2nbOpScZZw6AxOIbfQe26ZqwnxM1Xtw75cxDINJ9gaMLQjLQCDiXRI10cqqbe/nGTanZ/o0NTUEWruCsF5DT6zQMA/Jxzr1LyvJiLPqNRXcw5iyYSiL8VQ/Bvtb/p0OQDZrLRDBtJfVPQaNTerbiqR/DqjB5SnYYTbu7M8HFa3FaejRy1W9NfX4zi/ZBumgwVoT5E9p6z00ek/OCjdTA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=vmrEPkQN1064LH4tIVv+PKTAL3frdIcEMLqOSC/gNPQ=; b=j5W62OPHS0ImOuM0Cb3wJGiGHwICI9bZB+P+FsjtOTFfYvidtTH3Dxen9bWhLYHhUT0QhKM1f23Psl39o0NXtZhzabqqb093hbDyZWd0odVHBFUhPmHvkmsFR9jDmXRcyrTp048G5D6fjH+PUtHkC5Q4EiLhLaTfeiUyenFWja3+A7TEcLiBL8I51jGnmCrDyRjConT66uBUAgutCQ9H/VGOZpNjVUiG4Fst1n7VtlzRS7Zlr3whodOxKvIYXldsLD6JIdIYOn9Ia+wKXyBpJdto7vsnj0lhGlYv5iHDtOfqmj9bIoTg/fkyDIAUgVEmo+daDEAW5CoVZLog+GlEFw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vmrEPkQN1064LH4tIVv+PKTAL3frdIcEMLqOSC/gNPQ=; b=uBPeNBoOeCYnF4PHj0ZzTQIWVTq6losclhZ55VAJEHWxA89e2ZBcfV0guGI2i1WL5XHXkPQCTpzq9CfbzKcnUHSUw2MXwARPe4pPyJeEFHM9QhIEfTeCZMGArCyWYiDBN7Le2ypu0WG+hWO3IQ7n6Rkhhw1ZIijgy4KupCHSEco=
Received: from HE1PR07MB4187.eurprd07.prod.outlook.com (2603:10a6:7:98::23) by HE1PR0701MB2585.eurprd07.prod.outlook.com (2603:10a6:3:90::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4909.2; Thu, 13 Jan 2022 08:36:57 +0000
Received: from HE1PR07MB4187.eurprd07.prod.outlook.com ([fe80::1160:24d2:41aa:45cc]) by HE1PR07MB4187.eurprd07.prod.outlook.com ([fe80::1160:24d2:41aa:45cc%3]) with mapi id 15.20.4888.010; Thu, 13 Jan 2022 08:36:57 +0000
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
To: Brian Rosen <br@brianrosen.net>
CC: Paul Kyzivat <pkyzivat@alum.mit.edu>, "draft-ietf-rum-rue@ietf.org" <draft-ietf-rum-rue@ietf.org>, "rum@ietf.org" <rum@ietf.org>, The IESG <iesg@ietf.org>, "rum-chairs@ietf.org" <rum-chairs@ietf.org>
Thread-Topic: Zaheduzzaman Sarker's Discuss on draft-ietf-rum-rue-09: (with DISCUSS)
Thread-Index: AQHX8TRbrfnf/vtg4UaxBU6m+QHF0axAhkEAgB14VYCAAE0+gIABQtwAgAA1ogCAAQq3AA==
Date: Thu, 13 Jan 2022 08:36:57 +0000
Message-ID: <19B94737-7D3B-446A-A3CD-428C8AA787B7@ericsson.com>
References: <163951822534.4738.15762238627618541835@ietfa.amsl.com> <583F4F4C-C323-45FE-9278-39D612793351@brianrosen.net> <4D20AFD9-943C-41F9-882D-7794B3938F88@ericsson.com> <A292F99E-4E40-4862-B9FE-8C84DF512011@brianrosen.net> <0B674EBD-CE27-4A41-961A-268854F3F056@ericsson.com> <3E20B6A0-6EE3-4028-8E13-6CD5C804CF4E@brianrosen.net>
In-Reply-To: <3E20B6A0-6EE3-4028-8E13-6CD5C804CF4E@brianrosen.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3654.120.0.1.13)
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ed5ddbb8-cc62-4cde-09c0-08d9d66fdc5f
x-ms-traffictypediagnostic: HE1PR0701MB2585:EE_
x-microsoft-antispam-prvs: <HE1PR0701MB2585C55AC3FAAEB067A431F29F539@HE1PR0701MB2585.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: aWRPelMQxh7/8AIVHYyqSTTEuDnBOQGl5uNA+Y1HiTQShc2EYslVjXXnWCdUIDKuqxHB3+ChL5tSnHGnD4HVsbBclp2LlwiOIhvNJdUhDdFgMO1iGmW46JI96TbFB27m2RwxtieNUTKXKDiSPCEchJrntRF2R+v75d2gtJtTfjb8DEtc4EcTpweVdugbrwAdbhvjm/QX+/oqbWotvoZUp+JgwZp37AqfCW0sQEVvNxv7NiWy53bKlsUtb4HzI9Drd8tX9CV4JIzp/J4hxNZ+vKROVsOkuigN0muBxsuXgvGRNVaMcyK6ENl7Iq5pE7Gxp5Zugpav6YwOrVsc9m6ADqEZhcu+QUo3La7WbGSYQr5qEsuZtB5e30YUGXFHXZxslwo02/O3aItBsyzYLyz5kv360mtn6gDA5xXbimg0LWox75GNdoSyZAXkl2VZ6+RsJM3DP51Nu9V+jhrV8TY9HTahru3iR1mHmRO1rVxlueQXlbQdy+EXTRB8+867WLIvp6ttIt0Hcz2m2deyQ8ZXpNeuf3pwN3jHl0yxf7v5r5KtGtWsCVX2BqBBWe65WZztM8GVXDTH8UY6BWQ9NZgrKVPS7BdAIfuDiTpNYNI08phbA1OhjnjxsnNALqDs3bow6jSe9SHrk66FEwT2Mf7xIGm+j/gTezW7MFAtsQaJ3IntV1VRnjLB4pi/3J8EzFtyevwI/gFcw9ImaSaPelu0n0T4+unm9yUcZT8pH1r/Ut3y/pW+2LqPYuzLSxEbCcZz
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB4187.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(13230001)(4636009)(366004)(82960400001)(38100700002)(86362001)(6486002)(316002)(66574015)(122000001)(33656002)(5660300002)(508600001)(76116006)(91956017)(6506007)(6916009)(38070700005)(6512007)(83380400001)(66446008)(2616005)(99936003)(2906002)(186003)(44832011)(54906003)(26005)(8676002)(64756008)(36756003)(4326008)(66946007)(66476007)(66556008)(71200400001)(8936002)(53546011)(45980500001)(20210929001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?utf-8?B?QkU3dGF4V2wzaXpLZGdPNkNPOFAzZmlkN0J5M2tla3NKbVRIN0FVY21DWDBC?= =?utf-8?B?MkFkUEY3V3NxZnRBTE1KYnp5MkUxaldzQTRlaTlGSEFkMytMbVVPUzlVZHJn?= =?utf-8?B?RXVDd0pSQWF4V2pTS3BDMUU4TnJsYnJIRS9uTzRPOWd2MVpjZUlmeHNqWERn?= =?utf-8?B?ajJsbnFnU1RMSUY0Y0wyb0xHUFlmM3RmSU9nRGZIV2g4eW1RUElkaTVjT2hZ?= =?utf-8?B?d0JCNEhUNmU4LzZCT1hJTDBDZ2dWV0pEYmU1cXJVUjZMem5pbUpYdHJTaVhD?= =?utf-8?B?SHduOFVWWHBEMTg2MlcvNHI2L25CYm04K0wxVkxYUHFUN1lzVTZubHgwSDJF?= =?utf-8?B?WC80NmpObG9ZcThXV2FpNE5QZWlXRE5zQW9KMWthK0lzM21LdlFiT1VqZWZp?= =?utf-8?B?VEVPeXRWYlQ2Q1VyNEt4YkY1MVBDQTM3TnNMVk5rNGJyMjdTUUlPRzE5TXlS?= =?utf-8?B?NU52Q2FsL1RjZlF0OWs3dk5iY3RBTXNubnZKR2VkcHRtQW5uSTFjN0dkMDRJ?= =?utf-8?B?R1lLdjVQQzRRZ0h2M1JsTlAyTUk5S1hIRXZENm40THFpbVJaZGNYMUpobTlK?= =?utf-8?B?UXdvSDU0WnNSS0hrdlVvKzlZVXQ2UitHNjNwcGFpT1N3REZyRHFDb2laT2JG?= =?utf-8?B?WjYzUXhpcFNCZDlLL3hSQ2VpdmVnNi9IZjJqV0pXandZQWQyZWNBRzIzRW4x?= =?utf-8?B?dU9iK2NnQ2M3S3BBdkNIUkFBTmFucmxnQ1dKUjZVdTd1ZzNoOVlNMXlqV0cw?= =?utf-8?B?MTZIR1FvMDBBMUx5a2w4cllJTzNvNmhkS0NEdDdMMlo4d0hoUkwwY0Vydmt1?= =?utf-8?B?VTh6dWJoR0hwajZneHdrNlNJemFMV1pzN3l4RldmYUNWSHcvSmtSdzdSNUhQ?= =?utf-8?B?ZWRUZ2FrcmYwa3NGbk1xVk1hZFVkWFNLUnB0L3Z1Wlo5ZTBQVisxa3I0Rjdt?= =?utf-8?B?VmwybmpvWWcxbjFkTDdpbUhEYzlKN1ltVldreG41aWZJMmt1ZXBQbTd1c1lD?= =?utf-8?B?bzM0K3JmSDdkQjkzSWVjVU1Pb1dab0EzdjY2ZFBEcE8xd2ZtUGJpcmFRdS80?= =?utf-8?B?ejc3UVZ3VzBmR3NkY250Qk1JbFF3S1Zoakx2S1kxTlpKb0xackp4ZjFzL3hV?= =?utf-8?B?OUVlczc2VmQxbE13bjZPWG13L2VHd2dRSm5ZaUFpanNQMDU4VEpwaS8rSEhN?= =?utf-8?B?c09Lak1EVldoQTMrWXB0c0pRQ0dqMkErcjNrNnpxVmRnbEZhZFlXTEppb0JJ?= =?utf-8?B?anFBY1N6S0x5TG1tbjBINlNVKzg5ZVBaT2NCMWN2d2czV05uYk1vMURvVi90?= =?utf-8?B?dVdDZ09BaGtWWlZON1FWVU5CY0cyTXl6a3ZDNDArUnZQQ0VnbE1vbWVLckNZ?= =?utf-8?B?SmdJTTBtbm9FVFpnSDJxNW00dGQ3RGZkY05lYWZpTCt5bjF4YWN4anMxeUtF?= =?utf-8?B?NXpJQWsyVWVURE9kWmtSdnpUQjJ2UzdXd2xEV0NRcHQ0QUl4NzRDNzNGL3Qx?= =?utf-8?B?aFhSTEcwNXEvS3FKNnBuMHFsQ2ZjWlo4RmJPM0FNQUM3azhiamo2cVZVbGho?= =?utf-8?B?d1R1SVdDN1RPbDg4d0hlYVpZNGNoK1V0UXhWQWNaUTI3VE1lRnAyRFVFRVpl?= =?utf-8?B?cklqZndDczJsdko3L3U1SStwYlErU1BpZSt5RUtIRW5qTUU0TXlXTnZDdjE5?= =?utf-8?B?MFlGYjB5TXVCQWlIeEJ4WkkzNm03eGNZKzk0SEJkWWxyeG1QMk5PMnJyd2RQ?= =?utf-8?B?d0xhTDZyMmZDZ0ZLem1qcTcxWTE3S3V3WlEvQ3M5bDhHYXlJVS9paVdwbEMw?= =?utf-8?B?eVViTHA5bURCUGtzN3RhYithWWFMSWNDZjdUZVU5T1NPbnZuckpCWkxFUmVL?= =?utf-8?B?eHE4MHRhRFhEMlFLT2ZrZ2d3VUhPeWlZQ3ZVRHRhSWZrdC9ZWHp1UXorUFF3?= =?utf-8?B?a3VlOUFsZm1tRFlIajRHNHRKRmJRdnNzZ0JDOGZEdVpOMEhuQStPaGNsRnRK?= =?utf-8?B?QXhhQU1MR0MwZHExS3Y1UCtUVUplWHE2eDhuNllOWFc2VWN2V2N3N24wT3l0?= =?utf-8?B?elpRQTVOS00ySVcxbDZaNzBkTHpjb1AvS1RnbXpTQ1NMTUpNQk0yaDRjc0FM?= =?utf-8?B?ZUNrbDJHUk5jZkVRejVWUlNXbk51aU9QTU1xbXBzK3FKTUtRNnNrN09BblU2?= =?utf-8?B?UGJrTGw4SmxMekNhbGx5aXE5cG80WjlCOFZGTU02Ym94aDh4ODdXbDB6SzdF?= =?utf-8?B?OFErNnFOK2F0V25BMUROL05Rc3piN0ZWSE5nN1o1dkZRTGVnT2QwWkVBZ1pQ?= =?utf-8?B?aWtyaWZYMk93UDJ1L1BRdi9MNGpqSkZ1YkNMSDFmaHp0THZTbjRvdz09?=
Content-Type: multipart/signed; boundary="Apple-Mail=_A4A93EE7-629F-45AA-8D9B-1F06CEA18C7F"; protocol="application/pkcs7-signature"; micalg=sha-256
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB4187.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ed5ddbb8-cc62-4cde-09c0-08d9d66fdc5f
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jan 2022 08:36:57.5315 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: n/GFkcA/0dzvAkHdyVxtC6pYrQDOA6hHBr60D3rhKYKNL+nNjkQQjnJ9HIxA9V/Z9E9PYVlz4zokvITxakJLXV7cYmC5EDAA3j8EIg/DB6pwuZIZjoD33EfRQuNwq99K
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2585
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/d-nUEB9lQhwo59IxkZrPJL3DZlQ>
Subject: Re: [Rum] Zaheduzzaman Sarker's Discuss on draft-ietf-rum-rue-09: (with DISCUSS)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2022 08:37:11 -0000

--Apple-Mail=_A4A93EE7-629F-45AA-8D9B-1F06CEA18C7F
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_BFA9BE8E-F313-4407-9E27-F4346F9F3B4F"


--Apple-Mail=_BFA9BE8E-F313-4407-9E27-F4346F9F3B4F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

The statement in the specification actually raises some confusions. =
Like, section 6.3 says backward compatibility is desired, now given the =
context of the Section 6.3 my interpretation would be the backward =
compatibility is scoped there to codec of choice. But then the referred =
text makes me think that it is not only coded but also end to end video =
we are talking about. So old devices those are not WebRTC compatible =
comes into play which =E2=80=9Cmay=E2=80=9D require some interworking =
which is not provided in this specification.  That is why I think it =
would be better to mention where the implementers should and should not =
care about backward compatibility and to what extend. I will suggest to =
add statements along the lines what you wrote for video traffic - =
=E2=80=9Colder devices that may not implement all the mechanisms and =
where SDP negotiation might not result in a compatible option=E2=80=9D =
hence media session should not be established. The main point here is =
that we don=E2=80=99t want non-congestion controlled media traffic in =
the Internet ( RFC8834), Hence if a gateway has a leg where we have =
older devices those are not capable of congestion/rate controlled media =
then even if they support desired video codec the end to end video =
session must not be established. I was really hoping that as RUI claims =
to be non-browser webRTC client, older devices that does not implement =
all the mechanisms are completely out of scope of RUI profile, =20

//Zahed

> On 12 Jan 2022, at 17:42, Brian Rosen <br@brianrosen.net> wrote:
>=20
> On the last point, the text already says:
> While there are some accommodations in this document to maximize =
backwards compatibility with other devices and services that are used to =
provide VRS service, backwards compatibility is not a requirement, and =
some interwork may be required to allow direct video calls to older =
devices.=20
>=20
>> On Jan 12, 2022, at 8:30 AM, Zaheduzzaman Sarker =
<zaheduzzaman.sarker@ericsson.com =
<mailto:zaheduzzaman.sarker@ericsson.com>> wrote:
>>=20
>>=20
>>=20
>>> On 11 Jan 2022, at 19:14, Brian Rosen <br@brianrosen.net =
<mailto:br@brianrosen.net>> wrote:
>>>=20
>>>=20
>>>=20
>>>> On Jan 11, 2022, at 8:38 AM, Zaheduzzaman Sarker =
<zaheduzzaman.sarker@ericsson.com =
<mailto:zaheduzzaman.sarker@ericsson.com>> wrote:
>>>>=20
>>>>=20
>>>>=20
>>>>> On 23 Dec 2021, at 20:36, Brian Rosen <br@brianrosen.net =
<mailto:br@brianrosen.net>> wrote:
>>>>>=20
>>>>> Thank you for these comments.
>>>>>=20
>>>>> We did not have a specific conversation on handling rate control =
and congestion feedback. =20
>>>>> The RUE server and client are required to support RTCP, so I think =
that part is easy.  Both ends are required to support the WebRTC media =
spec, so I think if it happened if both RUE clients were implemented =
with WebRTC clients, everything would work the way we expect it to.
>>>>>=20
>>>>> So I think the issue reduces to a situation where one end is a =
WebRTC client, and the other is not.  They both have to implement the =
media congestion mechanisms.  They both have RTCP to work with.  SDP =
negotiation should work,
>>>> This sounds like requirements to me, is this described in the =
document?
>>> The requirements that both have to implement RTCP, the media =
congestion mechanisms, and SDP negotiations are already in the document, =
yes.
>> Ok. Good.
>>>=20
>>>>>=20
>>>>> I=E2=80=99m down to thinking the gateway doesn=E2=80=99t have to =
mess with this.  It=E2=80=99s possible that the gateway could have more =
expansive goals to be backwards compatible with existing VRS devices =
that don=E2=80=99t conform to this document, and I could imagine that =
there might need to be some work there.  But that would not be covered =
in this document.=20
>>>> Would be good to be explicit about this in this document. The thing =
if the gateway does not want to mess with the RTCP signalling then the =
signalling and the negotiation of what to use for rate and congestion =
control need to be end to end. This should be clear in this document.
>>> But that is why the document requires support for 8825/8834.  I will =
add a statement that "Conformance to this document allows end-to-end =
RTCP and media congestion control for audio and video."  =E2=80=9CAllows=E2=
=80=9D is the right word, because many provides anchor media.
>> Looks good to me.
>>>=20
>>>>> I=E2=80=99m not personally a WebRTC expert although I had help =
writing the text from some folks who were.  So, II easily could be =
missing something here.
>>>>>=20
>>>>> On =E2=80=9CClarification of the use of ICE=E2=80=9D, I propose to =
add "Implementations MUST implement full ICE, although they MAY =
interwork with User Agents that implement ICE-lite.=E2=80=9D  There is =
an unqualified requirement to support RFC8839.
>>>> OK.
>>>>>=20
>>>>> I propose to add the following text in the media section where we =
introduce the WebRTC media specs:
>>>>> To use WebRTC with this document, a gateway that presents a WebRTC =
server interface towards a browser, and a RUE client interface towards a =
provider is assumed.  The gateway would interwork signaling, and as =
noted below, interwork at least any real time text media, in order to =
allow a standard browser baed WebRTC client to be a VRS client.  The =
combination of the browser client and the gateway would be a RUE user.
>>>> I think interworking will also be necessary for A/V media traffic
>>> I certainly hope not.  Between conforming RUEs, there won=E2=80=99t =
be any issues.  The only things I worry about are talking to older =
devices that may not implement all the mechanisms and where SDP =
negotiation might not result in a compatible option.  =20
>> And I understand you are saying those use case is out of the scope of =
this document. I would expect this to be explicit in the specification.
>>=20
>> //Zahed
>=20


--Apple-Mail=_BFA9BE8E-F313-4407-9E27-F4346F9F3B4F
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"">The =
statement in the specification actually raises some confusions. Like, =
section 6.3 says backward compatibility is desired, now given the =
context of the Section 6.3 my interpretation would be the backward =
compatibility is scoped there to codec of choice. But then the referred =
text makes me think that it is not only coded but also end to end video =
we are talking about. So old devices those are not WebRTC compatible =
comes into play which =E2=80=9Cmay=E2=80=9D require some interworking =
which is not provided in this specification. &nbsp;That is why I think =
it would be better to mention where the implementers should and should =
not care about backward compatibility and to what extend. I will suggest =
to add statements along the lines what you wrote for video traffic - =
=E2=80=9C<span style=3D"font-size: 12px;" class=3D"">older devices that =
may not implement all the mechanisms and where SDP negotiation might not =
result in a compatible option</span>=E2=80=9D hence media session should =
not be established. The main point here is that we don=E2=80=99t want =
non-congestion controlled media traffic in the Internet ( RFC8834), =
Hence if a gateway has a leg where we have older devices those are not =
capable of congestion/rate controlled media then even if they support =
desired video codec the end to end video session must not be =
established. I was really hoping that as RUI claims to be non-browser =
webRTC client, older devices that does not implement all the mechanisms =
are completely out of scope of RUI profile, &nbsp;<br class=3D""><div =
class=3D""><br class=3D""></div><div class=3D"">//Zahed</div><div =
class=3D""><div class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On 12 Jan 2022, at 17:42, Brian Rosen &lt;<a =
href=3D"mailto:br@brianrosen.net" class=3D"">br@brianrosen.net</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D"">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; line-break: after-white-space;" class=3D"">On the last point, the =
text already says:<div class=3D""><div style=3D"margin: 0px; =
font-stretch: normal; line-height: normal; font-family: Menlo; =
background-color: rgb(255, 255, 255);" class=3D"">While there are some =
accommodations in this document to maximize backwards compatibility with =
other devices and services that are used to provide VRS service, =
backwards compatibility is not a requirement, and some interwork may be =
required to allow direct video calls to older devices.&nbsp;</div><div =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jan 12, 2022, at 8:30 AM, Zaheduzzaman Sarker &lt;<a =
href=3D"mailto:zaheduzzaman.sarker@ericsson.com" =
class=3D"">zaheduzzaman.sarker@ericsson.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
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""><br =
class=3D"Apple-interchange-newline"><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On 11 Jan 2022, at 19:14, Brian =
Rosen &lt;<a href=3D"mailto:br@brianrosen.net" =
class=3D"">br@brianrosen.net</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><br class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Jan =
11, 2022, at 8:38 AM, Zaheduzzaman Sarker &lt;<a =
href=3D"mailto:zaheduzzaman.sarker@ericsson.com" =
class=3D"">zaheduzzaman.sarker@ericsson.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><br class=3D"" =
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;"><br class=3D"" =
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;"><blockquote =
type=3D"cite" class=3D"" style=3D"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;">On 23 Dec 2021, =
at 20:36, Brian Rosen &lt;<a href=3D"mailto:br@brianrosen.net" =
class=3D"">br@brianrosen.net</a>&gt; wrote:<br class=3D""><br =
class=3D"">Thank you for these comments.<br class=3D""><br class=3D"">We =
did not have a specific conversation on handling rate control and =
congestion feedback. &nbsp;<br class=3D"">The RUE server and client are =
required to support RTCP, so I think that part is easy. &nbsp;Both ends =
are required to support the WebRTC media spec, so I think if it happened =
if both RUE clients were implemented with WebRTC clients, everything =
would work the way we expect it to.<br class=3D""><br class=3D"">So I =
think the issue reduces to a situation where one end is a WebRTC client, =
and the other is not. &nbsp;They both have to implement the media =
congestion mechanisms. &nbsp;They both have RTCP to work with. &nbsp;SDP =
negotiation should work,<br class=3D""></blockquote><span class=3D"" =
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;">This sounds like requirements to me, is =
this described in the document?</span><br class=3D"" 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;"></div></blockquote>The requirements that both =
have to implement RTCP, the media congestion mechanisms, and SDP =
negotiations are already in the document, =
yes.</div></div></div></blockquote>Ok. Good.<br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div class=3D""><br class=3D""></div><div =
class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D"" style=3D"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;"><br class=3D"">I=E2=80=99m down to thinking the gateway doesn=E2=80=
=99t have to mess with this. &nbsp;It=E2=80=99s possible that the =
gateway could have more expansive goals to be backwards compatible with =
existing VRS devices that don=E2=80=99t conform to this document, and I =
could imagine that there might need to be some work there. &nbsp;But =
that would not be covered in this document.<span =
class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D""></blockquote><span class=3D"" 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;">Would =
be good to be explicit about this in this document. The thing if the =
gateway does not want to mess with the RTCP signalling then the =
signalling and the negotiation of what to use for rate and congestion =
control need to be end to end. This should be clear in this =
document.</span><br class=3D"" 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;"></div></blockquote>But that is why the document =
requires support for 8825/8834. &nbsp;I will add a statement that =
"Conformance to this document allows end-to-end RTCP and media =
congestion control for audio and video." &nbsp;=E2=80=9CAllows=E2=80=9D =
is the right word, because many provides anchor =
media.</div></div></div></blockquote>Looks good to me.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;"><div class=3D""><br class=3D""><blockquote=
 type=3D"cite" class=3D""><div class=3D""><blockquote type=3D"cite" =
class=3D"" style=3D"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;">I=E2=80=99m not personally a WebRTC expert =
although I had help writing the text from some folks who were. &nbsp;So, =
II easily could be missing something here.<br class=3D""><br class=3D"">On=
 =E2=80=9CClarification of the use of ICE=E2=80=9D, I propose to add =
"Implementations MUST implement full ICE, although they MAY interwork =
with User Agents that implement ICE-lite.=E2=80=9D &nbsp;There is an =
unqualified requirement to support RFC8839.<br =
class=3D""></blockquote><span class=3D"" 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;">OK.</span><br class=3D"" 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;"><blockquote type=3D"cite" class=3D"" =
style=3D"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;"><br class=3D"">I propose to add the following =
text in the media section where we introduce the WebRTC media specs:<br =
class=3D"">To use WebRTC with this document, a gateway that presents a =
WebRTC server interface towards a browser, and a RUE client interface =
towards a provider is assumed. &nbsp;The gateway would interwork =
signaling, and as noted below, interwork at least any real time text =
media, in order to allow a standard browser baed WebRTC client to be a =
VRS client. &nbsp;The combination of the browser client and the gateway =
would be a RUE user.<br class=3D""></blockquote><span class=3D"" =
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;">I think interworking will also be necessary =
for A/V media traffic</span><br class=3D"" 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;"></div></blockquote>I certainly hope not. =
&nbsp;Between conforming RUEs, there won=E2=80=99t be any issues. =
&nbsp;The only things I worry about are talking to older devices that =
may not implement all the mechanisms and where SDP negotiation might not =
result in a compatible option. =
&nbsp;&nbsp;</div></div></div></blockquote>And I understand you are =
saying those use case is out of the scope of this document. I would =
expect this to be explicit in the specification.</div><div =
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""><br =
class=3D""></div><div 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"">//Zahed</div></div></blockquote></div><br =
class=3D""></div></div></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_BFA9BE8E-F313-4407-9E27-F4346F9F3B4F--

--Apple-Mail=_A4A93EE7-629F-45AA-8D9B-1F06CEA18C7F
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCBf4w
ggX6MIID4qADAgECAg8BdUoQAyUVYjB/ZVVBDvMwDQYJKoZIhvcNAQELBQAwRzELMAkGA1UEBhMC
U0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENB
IHYzMB4XDTIwMTAyMTA3MjkyNVoXDTIzMTAyMjA3MjkyNFowYjERMA8GA1UECgwIRXJpY3Nzb24x
HDAaBgNVBAMME1phaGVkdXp6YW1hbiBTYXJrZXIxLzAtBgkqhkiG9w0BCQEWIHphaGVkdXp6YW1h
bi5zYXJrZXJAZXJpY3Nzb24uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmjJb
Zy6kdvqWwiZanvVnqKsb990pSFndyIgFspP9mArDxvEX0oqrBugPRyJSp1KA0KDPo9L3SBHk7pbp
hJDbJAxPdPAbyZ+DMHV/UtQSUUpp8rRoYNEA6Ew3OlG5Sz1Nhq9AcjSKeOZKunnJInh/y435NACo
co2uP/6Gk0XBeB3qE645aIqpbsO3DCUMOWxWIjjTRFQ/TqoUjbIwfw+rO64Y3qEa96Ibj63AoDtt
3gwmtpFkVm5C44XfK7J4LyXIIz4TQqnfxlfoJ+ttFMfV1ZV1OvA7xXj0yO/6btsktlktpgMvow87
HPkSRtsLXQoRhU4E1zclEPWz5SzhUXuOvwIDAQABo4IBxjCCAcIwHwYDVR0jBBgwFoAUHHsZnpec
dqwgPdjc45Fq49stplMwHQYDVR0OBBYEFJlMp3EJ+P/dXOLqvbT718jDfw1mMA4GA1UdDwEB/wQE
AwIFoDBVBgNVHSAETjBMMEoGDCsGAQQBgg8CAwEBEjA6MDgGCCsGAQUFBwIBFixodHRwczovL3Jl
cG9zaXRvcnkudHJ1c3QudGVsaWFzb25lcmEuY29tL0NQUzArBgNVHREEJDAigSB6YWhlZHV6emFt
YW4uc2Fya2VyQGVyaWNzc29uLmNvbTBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9lcmljc3Nvbm5saW5kaXZpZHVhbGNhdjMuY3JsMB0GA1UdJQQWMBQGCCsGAQUF
BwMEBggrBgEFBQcDAjCBggYIKwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIu
dHJ1c3QudGVsaWEuY29tMEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEu
Y29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2My5jZXIwDQYJKoZIhvcNAQELBQADggIBAD1OD1xt
xE0jjc12/QXWWe8Cv2q1ZRn1PwacRWFJMyprPB6CiR6YBnmovYCyvCrNCqzsNaTpQLAQeKxwpmOg
fZ1SrdyqQKjtCiAlQynqV+dX5VAA6kt/fM67jZbU+lmzw3/2mXNQKTnor1Ax2bJjtZB2DzvTmSPd
EybZWxSfMMSsZHA4GLPGEHws+7fHeZ6RSRsAolXPTLGu7gxPkYDtaUzI9M8Z9GKz2UC/wNP2UieR
95h5TnKiqAWLqAxwzcu7GVWIdJ4rzgOenaNg56OM5q87+X90ZSAODWAPnxdDgVGspHbxt2g9cQYb
pkKiHWrOuLIWd8B/oGbE1ruKqcFKC39aYkd7JRlHjkNfU/IpymDoGd3RYMtsJW2JvinuZMmMZ5F5
Xpw1yJuSPrq5tHbPx7S6hjqYhd9VkRLbKkprw9+HJZBrUrhrUx4HVF2/bo+WG9GCTdQUsm8JQt9B
zpRh2ySNBQZfUn1WN3Q+lMcGSdItCNYH6HnXGrAmv+oDZ1pnp9z+NNmDoNMAHaFvwYCFd9/HvjJu
5kL90Fp3UEJQAk6X+2+ElrfNplUz16nAOBvxcY55R5eI9SDD8MmNfADekiMldSwB9LjMrqBhwWeE
UblghhtceJ3iqg35LURo+KXdL3h0/IodZPBYoMLMhMbDdYokIUY+mWW5W1T1WzV9PyWqMYICyjCC
AsYCAQEwWjBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNz
c29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCDwF1ShADJRViMH9lVUEO8zANBglghkgBZQMEAgEFAKCC
AUEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMjIwMTEzMDgzNjU2
WjAvBgkqhkiG9w0BCQQxIgQgDgv5DtCZYgLTGrm1+rlP38XyDuG208xJQ/u9+z4gzVAwaQYJKwYB
BAGCNxAEMVwwWjBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVy
aWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCDwF1ShADJRViMH9lVUEO8zBrBgsqhkiG9w0BCRAC
CzFcoFowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBIHYzAg8BdUoQAyUVYjB/ZVVBDvMwDQYJKoZIhvcNAQELBQAEggEA
P6VJBPRPcmTMm8rsQtbSNZ18zC9UvAg/q/ivdyf6nDAbza/VUghvqyValKFQReS/UZ3mywhRWxNQ
e4cm/EiT8KbmKCx07YPowPyNcIRe36usgW73+9olH6V0ACVbJVK8kdCFxejmUkViI+CF1F8czy6p
bNkaTmF3mZyA+8z/x0EDSP4PWftBHaMMKaqV44xW05Jf6HwXIEZgjmiy7TqM02zG3qVAXelukUWS
M+rbG6WltOj7NzU0/KY8BnTLFddYsklRldkJYKyxlL0V0Tl0dy4djt3Q6/Ngj8sNW64cCFWqyyDP
KYg6czwOwRvi8c8w2R4eDG4L/mHharAKVJl5XgAAAAAAAA==

--Apple-Mail=_A4A93EE7-629F-45AA-8D9B-1F06CEA18C7F--


From nobody Wed Jan 19 15:09:46 2022
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rum@ietf.org
Delivered-To: rum@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB9C3A20A0; Wed, 19 Jan 2022 15:09:44 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: rum@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: rum@ietf.org
Message-ID: <164263378435.31694.1161443700591327194@ietfa.amsl.com>
Date: Wed, 19 Jan 2022 15:09:44 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/O2ZglDwqKVpQqsqVcjpHYvVoa7U>
Subject: [Rum] I-D Action: draft-ietf-rum-rue-10.txt
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jan 2022 23:09:45 -0000

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

        Title           : Interoperability Profile for Relay User Equipment
        Author          : Brian Rosen
	Filename        : draft-ietf-rum-rue-10.txt
	Pages           : 41
	Date            : 2022-01-19

Abstract:
   Video Relay Service (VRS) is a term used to describe a method by
   which a hearing person can communicate with a deaf, hard of hearing
   or hearing impaired user using an interpreter ("Communications
   Assistant") connected via a videophone to the deaf/hard of hearing/
   hearing impaired user and an audio telephone call to the hearing
   user.  The CA interprets using sign language on the videophone link
   and voice on the telephone link.  Often the interpreters may be
   employed by a company or agency termed a "provider" in this document.
   The provider also provides a video service that allows users to
   connect video devices to their service, and subsequently to CAs and
   other deaf/hard of hearing/hearing impaired users.  It is desirable
   that the videophones used by the deaf, hard of hearing or hearing
   impaired user conform to a standard so that any device may be used
   with any provider and that direct video calls between deaf, hard of
   hearing or hearing impaired users work.  This document describes the
   interface between a videophone and a provider.


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

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-rum-rue-10.html

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


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



From nobody Thu Jan 20 01:50:26 2022
Return-Path: <noreply@ietf.org>
X-Original-To: rum@ietf.org
Delivered-To: rum@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CA3E33A1ECA; Thu, 20 Jan 2022 01:50:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Zaheduzzaman Sarker via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-rum-rue@ietf.org, rum-chairs@ietf.org, rum@ietf.org, pkyzivat@alum.mit.edu, pkyzivat@alum.mit.edu
X-Test-IDTracker: no
X-IETF-IDTracker: 7.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>
Message-ID: <164267222299.5998.10748858545754900420@ietfa.amsl.com>
Date: Thu, 20 Jan 2022 01:50:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/K7l0SQiXSo_WGsicY5IIYa4gBXw>
Subject: [Rum] Zaheduzzaman Sarker's No Objection on draft-ietf-rum-rue-10: (with COMMENT)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jan 2022 09:50:24 -0000

Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-rum-rue-10: 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/blog/handling-iesg-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


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



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

Thanks for addressing the comments in the Discuss. The changes made in version -10 look good to me.




From nobody Thu Jan 20 06:51:33 2022
Return-Path: <br@brianrosen.net>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C06BB3A1497 for <rum@ietfa.amsl.com>; Thu, 20 Jan 2022 06:51:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level: 
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20210112.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BaSD5PS3558s for <rum@ietfa.amsl.com>; Thu, 20 Jan 2022 06:51:26 -0800 (PST)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 7951E3A1491 for <rum@ietf.org>; Thu, 20 Jan 2022 06:51:26 -0800 (PST)
Received: by mail-io1-xd2f.google.com with SMTP id f24so7268369ioc.0 for <rum@ietf.org>; Thu, 20 Jan 2022 06:51:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Lf+9w7lGN3EkDz56s4E7v7Q5IUhhXw4lJUZ8HJdoWHc=; b=HXlcqDzXofX3k2lNQDoyGwxyCXLKrNTXVrIhTswTp1UlfgXDefBHXTz/SA1zNz894C cZXzfnWsn5JRVPgWxKyPQr34G5uVtRBAZAWx/8IKzM2IeF0YckW+MuUZhqCSrYVaFJyj eUNyekExrj2L2we6hIfEDEGpAzyp2b8MCyX5SZmfhd4TdOlKMJo1D+PDWx9o796Mbz9K XfOM/lKw8GlOTe5KiIStTIGeyVNbSYAogkiIR9U4kWzy4bd01hntjwqRkoPYorE2j+3m FNEVQhjOPkr5lZOUN+4/rUSipb2wsbhtpYSzg3TpGKqmYvi9mpbH+IAJ65vphj1MeNXC +ZaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Lf+9w7lGN3EkDz56s4E7v7Q5IUhhXw4lJUZ8HJdoWHc=; b=rCyS0anihJhqhR8Xvzja2b/FOzXZnakfWd+XfZi5fR8dkBSxsINzxfJCfgKItO0Mb7 b71KOadqIMAUBQulXjcxgczRA2aoFahnE+0lKRWkF2zhWARXm+EvInzf3VKyDN024PLZ 8q8+gP7IJYEVlk4jsRrfmJQZGn42D7mgfTLIJwpzgVvSIe5RS6ZlRFAo11TDvv4K4Qfa 4PL2E6XLacRgN+bFGNTksmQI/AC5bZ5aQJouJoanDQzHi1IFppTYgV6x8xuX7v2jfRaH w0526vqPoUZl0gaikWK3uAg9HSs2/lZiI4YUDpdkLKJwM39hG06BvF6RZPLWIO3HN29A VvWA==
X-Gm-Message-State: AOAM532YhhNUpOanQzlRCRSOK5APIPVDbdmyjm3Hxy5HFPHt/qN7k7Py 2WSzYBAWWqh+RbbxpEFSzKFnSQ==
X-Google-Smtp-Source: ABdhPJwDs9aA23kok7v1yZWxV50aTjp/fCKzsQYtzXd3LzpXTE7WyOPLe5cdFiZYzrACMOZes0K5bA==
X-Received: by 2002:a02:7159:: with SMTP id n25mr15926440jaf.29.1642690284069;  Thu, 20 Jan 2022 06:51:24 -0800 (PST)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id e9sm1555273ilu.43.2022.01.20.06.51.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jan 2022 06:51:23 -0800 (PST)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <66F541E4-3415-49A8-A4C6-577F179A295E@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B34B1B9C-EE02-454F-B2E8-7198475E5EB8"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\))
Date: Thu, 20 Jan 2022 09:51:22 -0500
In-Reply-To: <CAM4esxQ_rP_OMf7OoN4jZYxgvOS+7dtMTCCPk=UaO6La0b2mAA@mail.gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-rum-rue@ietf.org, rum-chairs@ietf.org, rum@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
To: Martin Duke <martin.h.duke@gmail.com>
References: <163890001133.3603.6708235729467005454@ietfa.amsl.com> <47D5FC0F-129A-4227-8280-5DDC2D486BFB@brianrosen.net> <CAM4esxQ_rP_OMf7OoN4jZYxgvOS+7dtMTCCPk=UaO6La0b2mAA@mail.gmail.com>
X-Mailer: Apple Mail (2.3693.20.0.1.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/ZDnPg5gGGIpUCus7Z0JWiDzpWdA>
Subject: Re: [Rum] Martin Duke's Discuss on draft-ietf-rum-rue-09: (with DISCUSS and COMMENT)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jan 2022 14:51:31 -0000

--Apple-Mail=_B34B1B9C-EE02-454F-B2E8-7198475E5EB8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I submitted a -10 which I hope addresses your issues.

Brian


> On Jan 4, 2022, at 7:06 PM, Martin Duke <martin.h.duke@gmail.com> =
wrote:
>=20
> Hi Brian,
>=20
> Thanks for clearing things up! Replies inline.
>=20
> Besides the already-proposed changes, the main action item is my scope =
followup question to #3.
>=20
> On Thu, Dec 23, 2021 at 12:14 PM Brian Rosen <br@brianrosen.net =
<mailto:br@brianrosen.net>> wrote:
> Thank you for your comments.  Please see inline
>=20
>> On Dec 7, 2021, at 1:00 PM, Martin Duke via Datatracker =
<noreply@ietf.org <mailto:noreply@ietf.org>> wrote:
>>=20
>> Martin Duke has entered the following ballot position for
>> draft-ietf-rum-rue-09: 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/blog/handling-iesg-ballot-positions/ =
<https://www.ietf.org/blog/handling-iesg-ballot-positions/>
>> for more information about how to handle DISCUSS and COMMENT =
positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-rum-rue/ =
<https://datatracker.ietf.org/doc/draft-ietf-rum-rue/>
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> DISCUSS:
>> =
----------------------------------------------------------------------
>>=20
>> Thanks to Bernard Adoba for the TSVART review. It largely informs my =
DISCUSS.
>>=20
>> 1. If I understand correctly, this draft is not at all about =
interoperating
>> with a WebRTC endpoint, instead borrowing some requirements from that =
family of
>> specs rather than re-inventing the wheel. That's great, but putting =
that
>> explicitly in the intro would be helpful.
> Not quite.  I propose the following additional information in the =
media section where WebRTC specs are discussed:
> To use WebRTC with this document, a gateway that presents a WebRTC =
server interface towards a browser, and a RUE client interface towards a =
provider is assumed.  The gateway would interwork signaling, and as =
noted below, interwork at least any real time text media, in order to =
allow a standard browser baed WebRTC client to be a VRS client.  The =
combination of the browser client and the gateway would be a RUE user.
>> 2. In particular, the statement that RUE is a "non-browser endpoint" =
is
>> confusing if it's not actually meant to interoperate with WebRTC. I =
*think*
>> you're attempting to distinguish between WebRTC's browser-only =
requirements and
>> endpoint requirements, but I could be wrong here.
> See above, but I still may have to just remove that =E2=80=9Cnon =
browser endpoint=E2=80=9D text, because it=E2=80=99s confusing people.
>=20
>=20
> OK, I look forward to seeing the new text. =20
>>=20
>> 3. In Section 5.5, you require conformance with RFC8835 with a few =
vaguely
>> worded exceptions. It would be helpful to actually go through that =
document
>> enumerate exactly which normative statements in 8835 do not apply. =
That said,
>> I'm not sure I agree with Bernard that 8835 requires *use* of ICE, =
rather than
>> support, but maybe we can clarify this in the TSVART thread.
> The only reference to 8835 reads:
> Implementations MUST conform to [RFC8835] except for its guidance on =
the WebRTC data channel, which this specification does not use.=20
>=20
> I have looked carefully at all mentions of =E2=80=9Cdata channel=E2=80=9D=
 in 8835 and it seems really obvious what does and doesn=E2=80=99t =
apply.  Here is an example:
>=20
>    For data transport over the WebRTC data channel [RFC8831 =
<https://datatracker.ietf.org/doc/html/rfc8831>], WebRTC
>    endpoints MUST support SCTP over DTLS over ICE.  This encapsulation
>    is specified in [RFC8261 =
<https://datatracker.ietf.org/doc/html/rfc8261>].  Negotiation of this =
transport in the
>    Session Description Protocol (SDP) is defined in [RFC8841 =
<https://datatracker.ietf.org/doc/html/rfc8841>].  The SCTP
>    extension for I-DATA [RFC8260 =
<https://datatracker.ietf.org/doc/html/rfc8260>] MUST be supported.
>=20
>    The setup protocol for WebRTC data channels described in [RFC8832 =
<https://datatracker.ietf.org/doc/html/rfc8832>]
>    MUST be supported.
>=20
> None of it applies.  It might not be quite as obvious that because the =
above doesn=E2=80=99t apply, there is no SCTP requirement, but do you =
think we need to say that, given that the only discussion of SCTP is in =
relation to the data channel?
> I could call out each one of the data channel statements, but it =
really does seem superfluous.
>=20
> The scope of this isn't clear to me. I would imagine the WebRTC end of =
the gateway *does* support the webRTC data channel standards, yes? So =
the gateway that you specify in this document is translating the WebRTC =
data channel into the Section 6.2 data channel.
>=20
> Aside from the scoping question,  I'm struggling to find economical =
alternative wording that makes it clearer. So I'm OK with keeping the =
8835 "data channel" exception.
> =20
>>=20
>> 4. As Bernard points out, this ambiguity extends to IPv4 and 6 =
support. The
>> 8835 requirements are specific to browsers, so they might not apply. =
If you
>> require support for both, but not necessarily on the same device, it =
would be
>> good to say so.
>=20
> We require support for IPv4 and IPv6 expressly.  We say:
> Implementations MUST support IPv4 and IPv6.  Dual stack support is NOT =
required and provider implementations MAY support separate interfaces =
for IPv4 and IPv6 by having more than one server in the appropriate SRV =
record where there is either an A or AAAA record in each server DNS =
record but not both.  The same version of IP MUST be used for both =
signaling and media of a call unless ICE [RFC8445] is used, in which =
case candidates may explicitly offer IPv4, IPv6 or both for any media =
stream.=20
>=20
> If there is any conflict between that and 8835, I don=E2=80=99t see =
it.
>=20
> Sorry I missed that text somehow!=20
>=20
>> 5. In Sec. 6, it says "This specification adopts the media =
specifications for
>> WebRTC ([RFC8825])." Is this a normative statement? Must RUEs comply =
with the
>> entirety of that document, or is this an informative statement and =
the real
>> requirements are in the subsections of Sec 6? =46rom the discussion, =
it sounds
>> like you want to include the requirements for WebRTC "endpoints", but =
not for
>> WebRTC "browsers". It would help to clarify all this.
> We=E2=80=99re not requiring anything normative from 8825 I think.  =
Only the parts we expressly state. I could add: =E2=80=9Cexplicit =
requirements from the WebRTC suite of documents are described below=E2=80=9D=
.
>=20
> I think that would improve clarity.=20
>>=20
>> It's also possible that my initial understanding is incorrect, in =
which case
>> the later points don't make any sense and some explanatory text is =
needed.
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> Thanks for your work to make the internet more accessible for all.


--Apple-Mail=_B34B1B9C-EE02-454F-B2E8-7198475E5EB8
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"">I =
submitted a -10 which I hope addresses your issues.<div class=3D""><br =
class=3D""></div><div class=3D"">Brian</div><div class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jan 4, 2022, at 7:06 PM, Martin Duke &lt;<a =
href=3D"mailto:martin.h.duke@gmail.com" =
class=3D"">martin.h.duke@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><div dir=3D"ltr" 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 class=3D"">Hi Brian,</div><div =
class=3D""><br class=3D""></div><div class=3D"">Thanks for clearing =
things up! Replies inline.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Besides the already-proposed changes, the main action item is =
my scope followup question to #3.</div><br class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec =
23, 2021 at 12:14 PM Brian Rosen &lt;<a href=3D"mailto:br@brianrosen.net" =
class=3D"">br@brianrosen.net</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin: 0px =
0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; =
border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div =
style=3D"overflow-wrap: break-word;" class=3D"">Thank you for your =
comments.&nbsp; Please see inline<br class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Dec =
7, 2021, at 1:00 PM, Martin Duke via Datatracker &lt;<a =
href=3D"mailto:noreply@ietf.org" target=3D"_blank" =
class=3D"">noreply@ietf.org</a>&gt; wrote:</div><br class=3D""><div =
class=3D""><div class=3D"">Martin Duke has entered the following ballot =
position for<br class=3D"">draft-ietf-rum-rue-09: Discuss<br =
class=3D""><br class=3D"">When responding, please keep the subject line =
intact and reply to all<br class=3D"">email addresses included in the To =
and CC lines. (Feel free to cut this<br class=3D"">introductory =
paragraph, however.)<br class=3D""><br class=3D""><br class=3D"">Please =
refer to<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://www.ietf.org/blog/handling-iesg-ballot-positions/" =
target=3D"_blank" =
class=3D"">https://www.ietf.org/blog/handling-iesg-ballot-positions/</a><b=
r class=3D"">for more information about how to handle DISCUSS and =
COMMENT positions.<br class=3D""><br class=3D""><br class=3D"">The =
document, along with other ballot positions, can be found here:<br =
class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-rum-rue/" =
target=3D"_blank" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-rum-rue/</a><br =
class=3D""><br class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">DISCUSS:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">Thanks to Bernard Adoba for the =
TSVART review. It largely informs my DISCUSS.<br class=3D""><br =
class=3D"">1. If I understand correctly, this draft is not at all about =
interoperating<br class=3D"">with a WebRTC endpoint, instead borrowing =
some requirements from that family of<br class=3D"">specs rather than =
re-inventing the wheel. That's great, but putting that<br =
class=3D"">explicitly in the intro would be helpful.<br =
class=3D""></div></div></blockquote>Not quite.&nbsp; I propose the =
following additional information in the media section where WebRTC specs =
are discussed:</div><div class=3D"">To use WebRTC with this document, a =
gateway that presents a WebRTC server interface towards a browser, and a =
RUE client interface towards a provider is assumed.&nbsp;&nbsp;The =
gateway would interwork&nbsp;signaling, and as noted below, interwork at =
least any real time text media, in order to allow a standard browser =
baed WebRTC client to be a VRS client.&nbsp;&nbsp;The combination of the =
browser client&nbsp;and the gateway would be a RUE user.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"">2. In particular, the statement that RUE is a "non-browser =
endpoint" is<br class=3D"">confusing if it's not actually meant to =
interoperate with WebRTC. I *think*<br class=3D"">you're attempting to =
distinguish between WebRTC's browser-only requirements and<br =
class=3D"">endpoint requirements, but I could be wrong here.<br =
class=3D""></div></div></blockquote>See above, but I still may have to =
just remove that =E2=80=9Cnon browser endpoint=E2=80=9D text, because =
it=E2=80=99s confusing people.</div><div class=3D""><br =
class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">OK, I look forward to seeing the new =
text.&nbsp;&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin: =
0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; =
border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div =
style=3D"overflow-wrap: break-word;" class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">3. In Section 5.5, you require conformance =
with RFC8835 with a few vaguely<br class=3D"">worded exceptions. It =
would be helpful to actually go through that document<br =
class=3D"">enumerate exactly which normative statements in 8835 do not =
apply. That said,<br class=3D"">I'm not sure I agree with Bernard that =
8835 requires *use* of ICE, rather than<br class=3D"">support, but maybe =
we can clarify this in the TSVART thread.<br =
class=3D""></div></div></blockquote>The only reference to 8835 =
reads:</div><div class=3D"">Implementations MUST conform to =
[RFC8835]&nbsp;except for its guidance on the WebRTC data channel, which =
this specification does not use.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">I have looked carefully at all mentions =
of =E2=80=9Cdata channel=E2=80=9D in 8835 and it seems really obvious =
what does and doesn=E2=80=99t apply.&nbsp; Here is an example:</div><div =
class=3D""><br class=3D""></div><div class=3D""><pre style=3D"font-size: =
13.3333px; margin-top: 0px; margin-bottom: 0px; font-variant-ligatures: =
normal;" class=3D"">   For data transport over the WebRTC data channel =
[<a href=3D"https://datatracker.ietf.org/doc/html/rfc8831" =
title=3D"&quot;WebRTC Data Channels&quot;" target=3D"_blank" =
class=3D"">RFC8831</a>], WebRTC
   endpoints MUST support SCTP over DTLS over ICE.  This encapsulation
   is specified in [<a =
href=3D"https://datatracker.ietf.org/doc/html/rfc8261" =
title=3D"&quot;Datagram Transport Layer Security (DTLS) Encapsulation of =
SCTP Packets&quot;" target=3D"_blank" class=3D"">RFC8261</a>].  =
Negotiation of this transport in the
   Session Description Protocol (SDP) is defined in [<a =
href=3D"https://datatracker.ietf.org/doc/html/rfc8841" =
title=3D"&quot;Session Description Protocol (SDP) Offer/Answer =
Procedures for Stream Control Transmission Protocol (SCTP) over Datagram =
Transport Layer Security (DTLS) Transport&quot;" target=3D"_blank" =
class=3D"">RFC8841</a>].  The SCTP
   extension for I-DATA [<a =
href=3D"https://datatracker.ietf.org/doc/html/rfc8260" =
title=3D"&quot;Stream Schedulers and User Message Interleaving for the =
Stream Control Transmission Protocol&quot;" target=3D"_blank" =
class=3D"">RFC8260</a>] MUST be supported.

   The setup protocol for WebRTC data channels described in [<a =
href=3D"https://datatracker.ietf.org/doc/html/rfc8832" =
title=3D"&quot;WebRTC Data Channel Establishment Protocol&quot;" =
target=3D"_blank" class=3D"">RFC8832</a>]
   MUST be supported.
</pre><div class=3D""><br class=3D""></div></div><div class=3D"">None of =
it applies.&nbsp; It might not be quite as obvious that because the =
above doesn=E2=80=99t apply, there is no SCTP requirement, but do you =
think we need to say that, given that the only discussion of SCTP is in =
relation to the data channel?</div><div class=3D"">I could call out each =
one of the data channel statements, but it really does seem =
superfluous.<br class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">The scope of this isn't clear to me. I =
would imagine the WebRTC end of the gateway *does* support the webRTC =
data channel standards, yes? So the gateway that you specify in this =
document is translating the WebRTC data channel into the Section 6.2 =
data channel.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Aside from the scoping question,&nbsp; I'm struggling to find =
economical alternative wording that makes it clearer. So I'm OK with =
keeping the 8835 "data channel" exception.</div><div =
class=3D"">&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin: =
0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; =
border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div =
style=3D"overflow-wrap: break-word;" class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">4. As Bernard points out, this ambiguity =
extends to IPv4 and 6 support. The<br class=3D"">8835 requirements are =
specific to browsers, so they might not apply. If you<br =
class=3D"">require support for both, but not necessarily on the same =
device, it would be<br class=3D"">good to say so.<br =
class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div>We require support for IPv4 and IPv6 expressly.&nbsp; =
We say:</div><div class=3D"">Implementations MUST support IPv4 and =
IPv6.&nbsp;&nbsp;Dual stack support is NOT required and provider =
implementations MAY support separate interfaces for IPv4 and IPv6 by =
having more than one server in&nbsp;the appropriate SRV record where =
there is either an A or AAAA record in each server DNS record but not =
both.&nbsp;&nbsp;The same version of IP MUST be used for both signaling =
and media of a call unless&nbsp;ICE [RFC8445]&nbsp;is used, in which =
case candidates may explicitly offer IPv4, IPv6 or both for any media =
stream.&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D"">If=
 there is any conflict between that and 8835, I don=E2=80=99t see =
it.</div></div></blockquote><div class=3D""><br class=3D""></div><div =
class=3D"">Sorry I missed that text somehow!&nbsp;</div><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-style: solid; border-left-color: =
rgb(204, 204, 204); padding-left: 1ex;"><div style=3D"overflow-wrap: =
break-word;" class=3D""><div class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"">5. In Sec. 6, =
it says "This specification adopts the media specifications for<br =
class=3D"">WebRTC ([RFC8825])." Is this a normative statement? Must RUEs =
comply with the<br class=3D"">entirety of that document, or is this an =
informative statement and the real<br class=3D"">requirements are in the =
subsections of Sec 6? =46rom the discussion, it sounds<br class=3D"">like =
you want to include the requirements for WebRTC "endpoints", but not =
for<br class=3D"">WebRTC "browsers". It would help to clarify all =
this.<br class=3D""></div></div></blockquote>We=E2=80=99re not requiring =
anything normative from 8825 I think.&nbsp; Only the parts we expressly =
state. I could add: =E2=80=9Cexplicit requirements from the WebRTC suite =
of documents are described below=E2=80=9D.<br =
class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">I think that would improve =
clarity.&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin: =
0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; =
border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div =
style=3D"overflow-wrap: break-word;" class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">It's also possible that my initial =
understanding is incorrect, in which case<br class=3D"">the later points =
don't make any sense and some explanatory text is needed.<br =
class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">Thanks for your work to make the =
internet more accessible for =
all.</div></div></blockquote></div></div></blockquote></div></div></div></=
blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_B34B1B9C-EE02-454F-B2E8-7198475E5EB8--


From nobody Thu Jan 20 06:53:12 2022
Return-Path: <br@brianrosen.net>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05CB73A149B for <rum@ietfa.amsl.com>; Thu, 20 Jan 2022 06:53:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level: 
X-Spam-Status: No, score=-1.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, WEIRD_QUOTING=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20210112.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M4h3YWM0QXef for <rum@ietfa.amsl.com>; Thu, 20 Jan 2022 06:52:58 -0800 (PST)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 73E113A14B2 for <rum@ietf.org>; Thu, 20 Jan 2022 06:52:58 -0800 (PST)
Received: by mail-io1-xd31.google.com with SMTP id v6so7201928iom.6 for <rum@ietf.org>; Thu, 20 Jan 2022 06:52:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=HUdCO/53mcGN/Gqpr1IbRuj5RQA0W+BwvuQs+QE4s7w=; b=VVA46oq+Wzs0tD92Bh1BCgPSxqvUcyR/ho5zn9351Ziuq9eIidRV30fg7LfDGMvHCw +VAyVasb+xQQfEloxlfTWMastVKmZcu2nUW2JtOEHmhh2n3ivS84mx3IxE5Nq3IZcJ41 TL0MS1SxvRxP6Ic7gfXe93GThxYTn9nb5ABtIx+DL1pKd/BRl/8HEhnVGSZfBjY1HQOc BvIslvr3noaTLZyWe5F3fACQyyeJoWh1vg5g2kPQKMdwNrtK0ZrnZR1GoDGsX/p79fOi v8d4HHc1Ucc736+ZSvL4JwDsTaEtb6UykRJ7kyrPrg5iwyMbHL5EeL9DFVOCXM5WGV/D CExw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=HUdCO/53mcGN/Gqpr1IbRuj5RQA0W+BwvuQs+QE4s7w=; b=iXU1YifWW+CcWslV/0OGzNZ+00CKK10t0zNyMcBheXcgdt1NkjxNLeCeJfzU6vIAB9 vcSen4gWfOGzBZo8/7IRiwQQ3yNcLnDg9prN0nb0dbQwlr39P5K8ljtwphGGYoqhRdwu SIUw1//SIHsomNVuRawJh55v5YVealJzAtmiIY01YxGQLAgJfLu8HoMveCOqaNr49/T8 o1EZiMgtEWTjJNKO/WMY6jQAs+FOa6To9aN73wDz0m426NooGlDV3U7x8c+Gq+nLCzPv oGTM9xHfrCNV7w2MhuxDwuGnK0mUmUbaTlO3ABb6vQhPvrGxK1f2y2ath3X1xDbDVXBi Iizg==
X-Gm-Message-State: AOAM533nKUo3P2GiRo02WNqHDojv0Zwdkef42UAnWRfKWdusPd8tQ0P1 q1rePOl4BotdlcNhoiHKHpTlzQ==
X-Google-Smtp-Source: ABdhPJz+pbaxOjZijP+ZVv3hMFAOFFQDfOz2OjDND3zzISTNEGKy9t/Bw1ir9CpicwtmnxF2NPjxAA==
X-Received: by 2002:a6b:ef09:: with SMTP id k9mr8061677ioh.204.1642690376626;  Thu, 20 Jan 2022 06:52:56 -0800 (PST)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id x6sm1485338ill.78.2022.01.20.06.52.55 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jan 2022 06:52:55 -0800 (PST)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <C47695EF-2AAB-487E-9268-082C6FE07495@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_994F0239-D099-454F-A1D9-245E562F056B"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\))
Date: Thu, 20 Jan 2022 09:52:54 -0500
In-Reply-To: <20211225022238.GE11486@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-rum-rue@ietf.org, rum-chairs@ietf.org, rum@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
To: Benjamin Kaduk <kaduk@mit.edu>
References: <163960332431.21178.16224624731772159181@ietfa.amsl.com> <E2D4B9B5-1C4E-4EB2-8278-9EA82EA150CE@brianrosen.net> <20211225022238.GE11486@mit.edu>
X-Mailer: Apple Mail (2.3693.20.0.1.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/JDDHBkOvxDRQoYhpcR5kxtVry1U>
Subject: Re: [Rum] Benjamin Kaduk's Discuss on draft-ietf-rum-rue-09: (with DISCUSS and COMMENT)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jan 2022 14:53:07 -0000

--Apple-Mail=_994F0239-D099-454F-A1D9-245E562F056B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Benjamin

I submitted a -10 which I hope addresses all remaining issues.

Brian

> On Dec 24, 2021, at 9:22 PM, Benjamin Kaduk <kaduk@mit.edu> wrote:
>=20
> Hi Brian,
>=20
> Also inline
>=20
> On Fri, Dec 24, 2021 at 03:58:21PM -0500, Brian Rosen wrote:
>> Benjamin
>>=20
>> Thanks for the close read of this document.  Comments inline
>>=20
>>> On Dec 16, 2021, at 2:52 AM, Benjamin Kaduk via Datatracker =
<noreply@ietf.org> wrote:
>>>=20
>>> Benjamin Kaduk has entered the following ballot position for
>>> draft-ietf-rum-rue-09: 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/blog/handling-iesg-ballot-positions/
>>> for more information about how to handle DISCUSS and COMMENT =
positions.
>>>=20
>>>=20
>>> The document, along with other ballot positions, can be found here:
>>> https://datatracker.ietf.org/doc/draft-ietf-rum-rue/
>>>=20
>>>=20
>>>=20
>>> =
----------------------------------------------------------------------
>>> DISCUSS:
>>> =
----------------------------------------------------------------------
>>>=20
>>> Thanks for writing this document; it's an important topic and I look
>>> forward to seeing interoperability in this space.
>>>=20
>>> However, I don't think this document is quite ready for publication =
yet,
>>> as it has a number of internal inconsistencies (and at least one
>>> external inconsistency with IETF procedures) that would get in the =
way
>>> of interoperable implementation.
>>>=20
>>> (1) The procedure for substituting an entryPoint from the provider =
list into
>>> the OpenAPI interface description for obtaining configuration data
>>> appears to be incompatible with BCP 190.  Though there's not quite
>>> enough detail for me to be able to tell exactly what behavior is
>>> intended, the procedure of "replace localhost in the template with =
the
>>> value from provider discovery" seems like it implies that the value =
from
>>> provider discovery is just a hostname, and that we are requiring the =
RUM
>>> services to be accessible via HTTP at path /rum/v1 on that machine.  =
The
>>> URI path namespace is under control of the owner of the host, and we
>>> cannot assert that we will occupy that portion of the namespace.  =
The
>>> current version of BCP 190, RFC 8820, does allow us to say =
(effectively)
>>> "delegate a subtree of the path namespace to the protocol" by =
letting
>>> the owner of the host pick what base path to use for the protocol =
(even
>>> that would not have been allowed by its predecessor, RFC 7320), but =
we
>>> do need to let that host-specific path prefix be indicated somehow,
>>> whether by URL template or allowing a base path to be indicated in =
the
>>> provider discovery process.
>> There is no restriction that the provider discovery returns a host =
name.  It=E2=80=99s string substitution that will be used for the entry =
points of the interface.  It could be =
"interface.external.example.com/rum/rue/opemapi/generic =
<http://interface.external.example.com/rum/rue/opemapi/generic><http://int=
erface.external.example.com/rum/rue/opemapi/generic =
<http://interface.external.example.com/rum/rue/opemapi/generic>>=E2=80=9D.=
  Whatever the string is, it=E2=80=99s substituted for =E2=80=9Clocalhost=E2=
=80=9D and that is used to find the server and define the entry points.  =
After that string substitution, the path will end in, for example, =
=E2=80=9C../rum/v1/ProviderConfig=E2=80=9D.  I think that should be 8820 =
compatible.  I edited the descriptions of the mechanism to describe the =
parameters as strings to make it obvious that it is string substitution. =
=20
>>=20
>> I hope that=E2=80=99s enough to address the concern.
>=20
> Yes, that should work; thanks for the clarification.
>=20
>>>=20
>>> (2) There are a lot of inconsistencies about the parameters and data
>>> format of the various API responses as specified in prose, OpenAPI
>>> description, and examples.  In particular, we also fail to make a =
clear
>>> statement about whether the prose or the OpenAPI description is
>>> normative and takes precedence in case of disagreement.
>>>=20
>>> I'll list a bunch of things here; I made a fairly careful reading =
but am
>>> not willing to assert that this is a comprehensive listing.  (A =
number
>>> of them also get comments in the section-by-section comments; sorry
>>> about that duplication.)
>> I am sorry we made these many uncaught mistakes.  I=E2=80=99m having =
someone else go through and see if we can find more of them.
>=20
> Thanks.  (In reading the other ADs' reviews, I see that my list was
> definitely not comprehensive, since I missed the case mismatch on "v1" =
vs
> "V1" :)
>=20
>>> Sections 9.2.1 and 9.2.2 list configuration data items in the
>>> "configuration data for new user sign up and dial around" and
>>> "configuration data for the RUE" configuration retrieval APIs, and =
per
>>> the note at the end of =C2=A79.2 they include the REQUIRED data =
items.
>>> However, there are a couple data items that are mentioned elsewhere =
in
>>> the document as if they are always going to be present, but are not
>>> present in these lists of required configuration parameters.  In
>>> particular we talk about the "provider-domain" as coming from the
>>> configuration, and it appears in examples, but is not mentioned in =
the
>>> prose or OpenAPI format description.
>> This is an error.  It appears to be the result of several changes to =
the interface that resulted in the OpenAPI localhost substitution =
discussed above. =20
>> Somehow, we deleted provider-domain.
>> I replaced it in both the description and the OpenAPI yaml.
>>=20
>>=20
>>> The prose (and some examples) refer to an "outbound-proxies" RUE
>>> configuration element, but =C2=A79.2.2 and the OpenAPI description =
list the
>>> singular "outbound-proxy" (and with the corresponding difference in
>>> format/structure).
>> Fixed.  It should be proxies plural throughout now.
>>=20
>>>=20
>>> The prose mentions "credentials" from the configuration, but no
>>> parameter of that name appears (there is some mention of password =
under
>>> "carddav" but that seems insufficiently generic to match all =
instances;
>>> sip-password also exists).
>> The first instance of credentials said:
>>       The registrar MAY authenticate using SIP digest authentication. =
The credentials to be used (username and password) MUST be supplied =
within the credentials
>> This is standard sip terminology.  The configuration has the username =
(constructed from the phone number and the provider-domain) and the =
sip-password (or as described in the sip-password description) are the =
credentials.=20
>=20
> Okay, we can keep with the standard terminology.  I would suggest, =
then,
> that all instances of "credentials" (with quotes, usually as =
'''matching
> "credentials" from the configuration''') be modified to use an =
unquoted
> word, so as to avoid implying that there is a JSON element by that =
name.
>=20
>> It does occur to me, although no one raised in in reviews, that =
sometimes there is an actual username that is used, instead of the phone =
number.  I added that as optional (use the phone number if it=E2=80=99s =
not present), and reworded the text.
>>>=20
>>> "display-name" appears in the example in Figure 5 but is not listed =
in
>>> =C2=A79.2.2
>> Fixed
>>>=20
>>> The prose for the provider configuration resource indicates that the
>>> dialAround property is mandatory (it is not marked as "(OPTIONAL)"), =
but
>>> the OpenAPI specification does not list this property as required.
>> Fixed.
>>>=20
>>> The prose for the provider configuration's "signup" property says =
that
>>> it is an array of JSON objects, but the OpenAPI description says =
that it
>>> is just a single object (not an array).  Likewise for "dialAround" =
and
>>> "helpDesk=E2=80=9D.
>> Fixed.  Should have been arrays
>>>=20
>>> The prose for "phone-number" specifies E.164 format, but the OpenAPI
>>> description does not.
>> Fixed
>>=20
>>>=20
>>> "carddav" is triply inconsistent: the prose says username, password, =
and
>>> domain name are separated by "@" (presumably, in a single string), =
but
>>> the example only shows username and domain name in user@domain form, =
and
>>> the OpenAPI description says it should be an object with separate
>>> properties for username/password/domain, as well as an additional
>>> "sendLocationWithRegistration" property that is probably not =
supposed to
>>> be a child of "carddav=E2=80=9D.
>> Fixed
>>>=20
>>> (repeating from the previous), the "sendLocationWithRegistration"
>>> property is listed as belonging to the "carddav" object in the =
OpenAPI
>>> description, though the prose and example indicate it should be a
>>> property of the toplevel configuration object.
>> Fixed
>>>=20
>>> The prose and OpenAPI description indicate that "ice-servers" is an
>>> array of strings, but the example has an array of objects that use =
the
>>> dictionary key to indicate whether each URI is a TURN or STUN =
server.
>> Fixed
>>>=20
>>>=20
>>> =
----------------------------------------------------------------------
>>> COMMENT:
>>> =
----------------------------------------------------------------------
>>>=20
>>> There are a number of references to "the configuration" in the body =
text
>>> prior to =C2=A79.2 where the configuration service is discussed.  =
E.g., the
>>> first paragraph of =C2=A75.1 gives a hard requirement for =
registration and
>>> then makes a conditional reference to "the configuration" without =
any
>>> prose discussing how configuration retrieval interacts with
>>> registration.  it may be useful to have a brief introductory mention =
of
>>> the data flow involving registration and configuration retrieval and =
how
>>> the two initialization processes (don't) interact.
>> I added some text in the top of the SIP Signaling section.
>>=20
>>>=20
>>> I have a high-level comment or two about password usage in this
>>> document.  I recognize that we're constrained in practice by the =
current
>>> state of SIP specification and the deployed ecosystem, but while
>>> username/password may currently be the lowest common denominator for
>>> authentication, it's far from best current practice.  In a scenario
>>> like the one here, where the RUE is a dedicated (often hardware)
>>> product talking over a fixed protocol to a nearly fixed small set of
>>> providers, there's plenty of scope for using strong cryptography to
>>> authenticate the RUE, including public-key cryptography where the
>>> verifier does not need to store any per-user secret information.  At
>>> present, Digest seems to be the strongest mechanism in the registry =
for
>>> usage with SIP, but I would advise assuming that that will change in =
the
>>> future and writing the spec and implementation in a way that is
>>> compatible with stronger authentication schemes.
>> We had a big discussion on the use of OAuth, which is specified for =
use in SIP.  While there were strong proponents of supporting OAuth, it =
failed to gain consensus.  It=E2=80=99s just not how SIP is deployed.
>> I could rename the username/password things to try to anticipate some =
more robust mechanism, but the text has to change anyway and it didn=E2=80=
=99t seem worth it.  A really, really important characteristic of a =
device like this is if power fails, and is restored, calls can arrive.  =
This means you cannot require any user interaction on a power start.  =
This really is at odds with how a lot of mechanisms work.  We thought =
about installing certs and using mutual auth.  Again NO sip systems we =
know do that.  Installing certs securely with no user interaction is =
hard.  There was no consensus to try to do that here.  I personally =
don=E2=80=99t like the security situation we have, but we don=E2=80=99t =
have any alternatives we could realistically deploy.
>=20
> Indeed, compatibility with the deployed reality trumps ideological =
purity
> (though that doesn't keep us from documenting the weaknesses of what's
> deployed).  Thanks for confirming.
>=20
>>>=20
>>> Furthermore, this document in several places (I note a few in the
>>> per-secton comments) recommends or even requires the reuse of a
>>> username/password pair across multiple services.  Best practices are =
to
>>> use any given password at exactly one service.  In this regard one =
can
>>> roughly model the password as analogous to a pre-shared key -- it is
>>> useful for authenticating a peer in the sense that if the value is =
known
>>> only to two entities, and the party you're communicating with proves
>>> that they know the value, they must be the only other party that =
knows
>>> the secret value.  But once you reuse the password at multiple =
services,
>>> that logic falls apart, as the party you're communicating with could =
be
>>> the user, or it could be another service that shares the secret.
>>> Granted, when used with digest the password itself is not sent to =
the
>>> server for every authentication, but the server typically has access =
to
>>> it at some point, and even possession of the password hash in a
>>> verification database allows for offline brute-force attack, which =
has
>>> become comparatively cheap in recent years and even the availability =
of
>>> dedicated hardware for password cracking.
>> We could force the secondary services to have separate passwords.  =
Since they all come from the same config, they are all supplied by the =
default provider, and they all identify the same user, albeit on =
different service deployments, we didn=E2=80=99t think there really was =
much difference.  The one place I would be very reluctant to force =
separate credentials is stun/turn, were it=E2=80=99s just too common to =
use the same credentials. There is no value in protecting, say the =
configuration service independently of the sip service or the turn =
service.  It really doesn=E2=80=99t matter at all. =20
>=20
> The main value in separate passwords for the secondary services would =
be
> that compromise of one such service does not imply full compromise of =
the
> "account".  As above, though, what people are willing to deploy is the =
main
> consideration for me -- I don't feel a need to "require" something =
with an
> RFC 6919 "MUST (BUT WE KNOW YOU WON'T)".
>=20
>>>=20
>>> In particular, SHA-512 is not considered to be a best-practice hash
>>> function for password hashing, since it is highly parallelizable and =
not
>>> "memory-hard".  RFC 9106 specifies Argon2 (via the IRTF CFRG), the
>>> winner of the password hashing competition; it is the state of the =
art
>>> for password hashing, and even prior to that publication we had =
scrypt
>>> available in RFC 7914 that is a significant improvement on the SHA-2
>>> family of functions.  That said, it's not currently listed in the =
IANA
>>> registry for hash algorithms for HTTP (and SIP) digest =
authentication,
>>> so I am not sure that we can usefully advocate for its usage at the
>>> present time.
>> We only very recently deprecated RC4, and I=E2=80=99d bet 99,99% of =
sip services deployed still use it.  I was able to make this spec use =
SHA-512, but that=E2=80=99s the very best we can do in a profile.  We =
could try to get some of the SIP guys to put through an RFC to support =
Argon2, but that would have to happen before this doc could use it.
>=20
> Agreed.
>=20
>>=20
>>>=20
>>> Section 4
>>>=20
>>> Thanks for mandating RFC 7525 compliance.  I note that
>>> draft-ietf-uta-rfc7525bis is in progress in the UTA WG.  Though it =
will
>>> probably be published after this document, it may be a useful
>>> informative reference with forward-looking guidance on how to best
>>> secure TLS.
>> I=E2=80=99ll try to remember that for when this doc gets an update.
>>=20
>>>=20
>>>  All text data payloads not otherwise constrained by a specification
>>>  in another standards document MUST be encoded as Unicode UTF-8.
>>>=20
>>> I think we'd typically reference RFC 8259 here.
>> I=E2=80=99m worried that there might be some incompatibility between =
8259 and OpenAPI.  OpenAPI references=20
>> https://datatracker.ietf.org/doc/html/draft-wright-json-schema-00 =
<https://datatracker.ietf.org/doc/html/draft-wright-json-schema-00> =
<https://datatracker.ietf.org/doc/html/draft-wright-json-schema-00 =
<https://datatracker.ietf.org/doc/html/draft-wright-json-schema-00>>!!!!
>> The text is specific to string content and not JSON format.
>=20
> It seems likely that I got my RFC numbers confused here and I meant to =
say
> 3629 for UTF-8 itself.  Sorry about that.
>=20
> The 8259 reference might still be relevant, as JSON Schema still uses =
JSON
> (but, predating 8259, it references 7159 instead), but I didn't look =
for an
> appropriate place to put it.
>=20
>>>=20
>>> Section 5.1
>>>=20
>>>  The registrar MAY authenticate using SIP digest authentication.  =
The
>>>  credentials to be used (username and password) MUST be supplied
>>>  within the credentials section of the configuration and identified =
by
>>>  the realm the registrar uses in a digest challenge.  This username/
>>>=20
>>> Which entity is authenticating to which other entity here?  The =
phrasing
>>> "<X> MAY authenticate" implies that it is X that is authenticating =
to
>>> some other entity, but that does not seem to correspond to my model =
of
>>> the flow here, where the RUE is authenticating to the registrar.  If =
the
>>> flow is to be the other way, we would say "the registrar MAY
>>> authenticate the RUE using SIP digest authentication=E2=80=9D.
>> I'll make that change.  The registrar authenticates the RUE
>>>=20
>>> Also, I note that (HTTP) SCRAM authentication has superior security
>>> properties to Digest, but unfortunately I don't see any evidence =
that
>>> its use for SIP is defined yet.
>> Yeah, yet another weakness.
>>=20
>>>=20
>>> Section 5.2.1
>>>=20
>>>  The SIP URIs in the To field and the Request-URI MUST be formatted =
as
>>>  specified in subsection Section 5.4 using the destination phone
>>>  number, or as SIP URIs, as provided in the configuration
>>>  (Section 9.2).  [...]
>>>=20
>>> I'm not sure that I'm unpacking this properly.  (The construction =
"the
>>> SIP URIs MUST be formatted as [...], or as SIP URIs", makes me =
wonder
>>> if there are somehow non-SIP URIs involved even though we start off =
with
>>> "the SIP URIs".)  Is the idea that I either take the URI directly =
from
>>> the configuration ("as-is") or I format it as per =C2=A75.4 but not =
anything
>>> else?
>> There are two ways you specify the =46rom and To header fields in SIP =
when you are using telephone numbers and not usernames. =20
>> One is a SIP URI sip:2025551212@red.example.com;user=3Dphone. =20
>> The other is a TEL URI: tel:2025551212.=20
>> Phone number and domain come from the configuration.  Does that help?
>=20
> Uh...maybe.
> Do we need to s/or as SIP URIs/or as TEL URIs/?  I don't see how the
> current text allows the TEL version that you describe.
>=20
> I'd also consider making the "as provided in the configuration" clause =
a
> separate sentence, like "the phone number and domain (if applicable) =
are
> provided in the configuration (Section 9.2)".
>=20
>>>=20
>>> Section 5.2.2
>>>=20
>>>  party telephone number.  In two-stage dial-around, the To URI is =
the
>>>  front door URI (see Section 9.2) of the dial-around provider and =
the
>>>  domain of the URI is the provider domain from the configuration.  =
The
>>>=20
>>> Is "the URI" in "the domain of the URI" referring to "the To URI", =
or
>>> some other URI (the Request-URI, perhaps)?
>> Yeah, that=E2=80=99s pretty awkward.  I shortened it to:
>> In two-stage dial-around, the To URI is the front door URI (see =
Section 9.2) of the dial-around provider.
>>>=20
>>>=20
>>> The prose lists the call originator as (VRS user) +1-555-222-0001, =
but
>>> the URIs in Figure 1 that are not the call recipient appear as
>>> +18135551212; are those numbers supposed to be different like that?
>> I fixed the telephone numbers being wrong.  The deletion of the =
dashes follows text in 5.4
>=20
> Right, I just meant the actual numbers.  Thanks.
>=20
>>>=20
>>> Section 5.2.3
>>>=20
>>>  owner".  The URI MAY be an HTTPS URI or Content-Indirect URL.  The
>>>  latter is defined by [RFC2392] to locate message body parts.  This
>>>=20
>>> RFC 2392 seems to define a "Content-ID" URI (with "cid" scheme) but =
not
>>> a "Content-Indirect" URL.
>> Fixed.  I can=E2=80=99t tell you how many times I have made that =
mistake.
>>=20
>>>=20
>>> Section 5.2.5
>>>=20
>>>  Implementations MUST implement Additional Data, [RFC7852].  RUE
>>>  devices MUST implement Data Provider, Device Implementation and
>>>  Owner/Subscriber Information blocks.
>>>=20
>>> The string "Device Implementation" does not seem to appear in RFC =
7852,
>>> though "Device Information" does.
>> Fixed
>>=20
>>>=20
>>> Section 7.1
>>>=20
>>>  of an email address.  If the request triggers a challenge for =
digest
>>>  authentication credentials, the RUE MUST continue using matching
>>>  "credentials" from the configuration.  If no matching credentials =
are
>>>  configured, the RUE MUST use the SIP credentials from the
>>>  configuration.  [...]
>>>=20
>>> Do we really want a MUST-level requirement to reuse the SIP =
credentials?
>>> Best practices for credentials are to have a 1:1 relationship =
between
>>> credentials and where they are used and this sort of reuse is =
basically
>>> the polar opposite.
>> See above.
>>=20
>>>=20
>>> Section 9.1
>>>=20
>>>  non-mandatory-to use functions and SHALL NOT delete any objects,
>>>  members of objects or functions.  This means an implementation of a
>>>  specific major version and minor version is backwards compatible =
with
>>>  all minor versions of the major version.  [...]
>>>=20
>>> (This might all be covered by Rob's discuss point; I will read the
>>> replies on that thread and you don't need to duplicate content here =
for
>>> my benefit.)
>>> This statement doesn't seem to contain enough information to be =
useful.
>>> I think that a statement about backwards (or forwards) compatibility
>>> should be specific about whether it applies to the implementation of =
the
>>> client or the web service, and that backwards compatibility would
>>> require that the implementation in question interoperate with a peer =
at
>>> any same or previous minor version.  Just saying "compatible with =
all
>>> minor versions of the major version" would also make a statement =
about
>>> forward compatibility, which I think is allowable under these rules =
for
>>> what is allowed to change in minor versions, and it would be useful =
to
>>> make a statement about forward compatibility.
>> I added: "Either may have any higher or lower minor revision and =
interoperate with its counterpart with the same major version." =20
>> after "Backwards compatibility applies to both the server and the =
client."
>>=20
>> I think that avoids having to talk about forwards compatibility. =20
>>>=20
>>> Section 9.2
>>>=20
>>>  The interface to obtain configuration data is described by an =
OpenAPI
>>>  [OpenAPI] interface description.  In that interface description, =
the
>>>  "servers" component is specified as "localhost".  The entry point
>>>  obtained from the provider list (Section 9.1) is sutituted for
>>>  "localhost" to obtain the server prefix of the interface.  [...]
>>>=20
>>> I note that the OpenAPI description for /Versions has an override =
for
>>> "servers", and the value listed there does not include the string
>>> "localhost".  Some clarity that it is also expected to be affected =
by
>>> this kind of substitution seems in order.
>> That=E2=80=99s an error.  Changed the server override in Versions to:
>>      - url: https://localhost/rum
>>=20
>>>=20
>>>=20
>>>  In both the queries, an optional parameter may be provided to the
>>>  interface which is an API Key.  The implementation MAY have an API
>>>  Key obtained from the provider and specific to the implementation.
>>>  The method the API Key is obtained is not specified in this =
document.
>>>  The provider MAY refuse to provide service to an implementation
>>>  presenting an API Key it does not recognize.
>>>=20
>>> I note that the IETF does have a standard for conveying =
authorization
>>> information on the web -- OAuth 2.0.  It may not be a direct =
"drop-in"
>>> fit here, due to the need for a preexisting relationship with an
>>> authorization server, but perhaps it is worth mentioning as an =
option
>>> in addition to this provider-specific "API key" protocol?
>> This isn=E2=80=99t a user authorization.  It=E2=80=99s a developer =
authorization.
>> OAuth can=E2=80=99t be used, because the developer can=E2=80=99t =
provide credentials when the device connects.
>=20
> Oh, that kind of API key.  Then we get to pull in the security
> considerations for attempting to keep secret a value that's shipped in =
the
> software binary and sent on the wire (something that repeatedly =
doesn't
> happen for the official mobile apps for popular services)...
>=20
>>>=20
>>>  Also in both queries, the RUE device provides a required parameter
>>>  which contains an instance identifier.  This parameter MUST be the
>>>  same value each time this instance (same implementation on same
>>>  device) queries the interface.  This MAY be used by the provider, =
for
>>>  example, to associate a location with the instance for emergency
>>>  calls.
>>>=20
>>> Is there any cryptography to provide assurance that the instance
>>> identifier is indeed always used only by the one single instance?  =
The
>>> description here sounds roughly like a bearer token, which is far =
from
>>> best practice for this sort of thing.  Indeed, in other contexts a =
given
>>> instance is often identified solely by its public key, and must
>>> authenticate with the corresponding private key in order to act as =
the
>>> identified instance.
>> No, and I don=E2=80=99t think it=E2=80=99s needed,  A typical use =
case here is a device in your home and one on your phone that has the =
same credentials and phone number.  We just need to differentiate them. =
It=E2=80=99s not a security property.
>> The consequences of confusion is fairly low.  As stated above, we did =
go through some discussions of provisioning private keys to each device =
and gave up due to the complexity vs the sophistication of the user.  =
There really isn=E2=80=99t any reasonable plug and play mechanism here.  =
We can=E2=80=99t use anything like Acme.=20
>=20
> Thanks for the background; I don't see a need to re-hash that.
>=20
> Though the description above makes me wonder if the instance ID is =
scoped
> to a given user/credentials?  That would be better in some ways, I =
think.
>=20
>>>=20
>>>  The configuration API also provides the same version mechanism as
>>>  specified above in Section 9.1.  The version of the configuration
>>>  service MAY be different than the version of the provider list
>>>  service.
>>>=20
>>> Not only that, but the services are expected to be versioned
>>> independently, so there is no particular relationship between =
version
>>> X.Y of the one and version X.Y of the other=E2=80=A6right?
>> That=E2=80=99s correct
>>>=20
>>> Actually, having gone and looked further, the OpenAPI document seems
>>> to indicate that there's a single /Versions resource common across =
the
>>> /Providers, /ProviderConfig, and /RueConfig APIs, which makes me
>>> confused as to how the versions of the two services might actually =
be
>>> different (let alone versioned independently).
>> There are two services (the provider list service and the =
configuration service).
>> The former has one entry point, the latter has two: the provider =
config and the device config.
>>=20
>> The two services have different versions.  The two entry points in =
the configuration service have the same version.
>=20
> That looks like the key insight that I was missing.  Any chance we =
could
> get that sentiment expressed in the document?
>=20
>> The way this mechanism is designed, you can make an implementation =
that works on several (or all) major versions and any minor version of =
each major version.
>> For server implementation, if it support multiple versions, each one =
has a separate URI (the version is in the URI).  The client composes the =
URI it wishes to use by looking at the Versions entry point for the =
service to find a compatible version and uses that and uses the version =
to choose an Open API yaml (and the code the yaml generates).
>>=20
>>>=20
>>> Section 9.2.1
>>>=20
>>>     -  uri: a URI to the website for creating a new account in the
>>>        supported language.  The new user signup URI may only =
initiate
>>>        creation of a new account.  Various vetting, approval and =
other
>>>        processes may be needed, which could take time, before the
>>>        account is established.  The result of creating a new account
>>>        would be a username and password, which would be manually
>>>=20
>>> I strongly suggest using a more generic phrasing (e.g., "would be
>>> account credentials (e.g., username and password)") to allow for
>>> seamless transition to stronger authentication technologies without
>>> specification change.
>> Done
>>=20
>>>=20
>>> Section 9.2.2
>>>=20
>>>  *  lifetime: (optional) Specifies how long (in seconds) the RUE MAY
>>>     cache the configuration values.  Values may not be valid when
>>>     lifetime expires.  If the RUE caches configuration values, it =
MUST
>>>     cryptographically protect them.  [...]
>>>=20
>>> In other contexts, "cryptographically protect" would mean to =
encrypt,
>>> cryptographically sign, or compute a keyed MAC over the data.  If =
the
>>> intent here is just to record a cryptographic checksum of the data,
>>> that's probably better stated in terms of a checksum.
>>>=20
>>> In particular, this current text gives no indication of what threat =
the
>>> cryptography is supposed to protect against, so implementations are
>>> unlikely actually provide uniform protection against the intended
>>> threat.
>> I added some text so it now reads:
>> it MUST cryptographically protect them against unauthorized =
disclosure (e.g. by other applications on the platform the RUE is built =
on).=20
>=20
> Thanks!
>=20
>>>=20
>>>  *  sip-password: (optional) a password used for SIP, STUN and TURN
>>>     authentication.  The RUE device retains this data, which must be
>>>     stored securely.  [...]
>>>=20
>>> Akin to the above, this doesn't indicate what threat "stored =
securely"
>>> is intended to protect against.  While I would *hope* that "protect
>>> passwords" is instinctive to developers, I wouldn't want to rely on =
it.
>> I added the same text to that.
>>=20
>>>=20
>>>     password MUST be used.  If it was never supplied, the password
>>>     used to authenticate to the configuration service is used for =
SIP,
>>>     STUN and TURN.
>>>=20
>>> In the general case, this directive is a gaping security hole =
(exposing
>>> the RUE's SIP credentials to arbitrary external STUN/TURN servers, =
for
>>> example).  I think we must qualify that the reuse of credentials is =
only
>>> for the servers listed in the "ice-servers" configuration directive.
>>> (And ideally we would not encourage reuse of credentials at all.)
>> Edited to say =E2=80=9Cis used for SIP, as well as STUN and TURN =
servers mentioned in this configuration."
>=20
> Thanks.
>=20
>>>=20
>>>  *  carddav: (optional) A username, password and domain name
>>>     (separated by ""@"") identifying a "CardDAV" server and account
>>>     that can be used to synchronize the RUE's contact list with the
>>>     contact list managed by the provider.  If username or password =
are
>>>     not supplied, the main account credentials are used.
>>>=20
>>> There are three data items but only one separator listed.  Is this
>>> really to be "username@password@domain"?
>>> It would be great if we could make ourselves more generic than
>>> username+password as credentials, and (as mentioned previously) =
avoid
>>> reuse of credentials.
>> I fixed this to have separate fields in an object in the config.
>> I don=E2=80=99t know any other usable authentication mechanism for =
cardav in this environment, but I=E2=80=99m far from an expert.
>=20
> I suspect that I'm even farther from expert than you are...
>=20
>>>=20
>>>  *  ice-servers: (optional) An array of URLs identifying STUN and =
TURN
>>>     servers available for use by the RUE for establishing media
>>>     streams in calls via the provider.
>>>=20
>>> Is any given entry required to offer both STUN and TURN services, or =
can
>>> a server provide just one or the other?  Both this text and my
>>> understanding of the OpenAPI description seem to indicate that this =
is a
>>> flat list intermingling STUN and TURN servers, but the example in =
Figure
>>> 5 seems to show each element of the array being a JSON object that
>>> contains one or more of the keys "stun" and "turn".  The structure =
in
>>> that example would obviate any confusion about which services are
>>> offered, and is probably preferred.
>> I fixed the OpenApi to use the strings (=E2=80=9Cstun=E2=80=9D and =
=E2=80=9Cturn=E2=80=9D).
>>=20
>>>=20
>>> Section 9.2.3
>>>=20
>>>      "contacts": "https://red.example.net:443/contacts/1dess45awd",
>>>=20
>>> I suggest putting a bit more entropy in the URL, in the vein of
>>> https://www.w3.org/2001/tag/doc/capability-urls/ (even if this =
resource
>>> is likely to require the username+password authentication discussed
>>> earlier).
>> Made it a V4 UUID (3617b719-2c3a-46f4-9c13-538f7efd0b21)
>>>=20
>>>      "carddav": "bob@red.example.com" ,
>>>=20
>>> The prose indicates this should contain a password as well as the
>>> username and domain name that are present.  How is the password
>>> specified?
>> This is fixed to have separate fields for domain, username and =
password
>>>=20
>>> Section 9.3
>>>=20
>>> Given the "are formally specified" language, I expect that the =
intent is
>>> for the OpenAPI description to be normative and take precedence in =
case
>>> of conflict with the prose/examples.  It's probably worth stating =
that
>>> explicitly.
>> Done.
>>=20
>>>=20
>>>         - in: query
>>>           name: instanceId
>>>           schema:
>>>             type: string
>>>           required: true
>>>           description: Unique string for this implementation
>>>                        on this device
>>>=20
>>> Is this self-assigned by the client or assigned by some external
>>> authority?  The allocation procedure is important for ensuring that =
the
>>> instance IDs are actually globally unique (with high probability).
>>> (Note that this parameter is used in both /ProviderConfig and
>>> /RueConfig.)
>> Self assigned by the client.  There is no dependence on this for =
Provider config.
>>=20
>> I=E2=80=99ll suggest it be something like a UUID.
>>>=20
>>> Section 10.2
>>>=20
>>> The rest of the document does not appear to contain any text =
covering
>>> the usage of the "rue-owner" purpose value.  Should we say something
>>> about when it's used and what semantics it conveys?
>> See Section 5.2.3. I added a cross reference.
>>=20
>>>=20
>>> Section 11
>>>=20
>>> I think we should make some statement that incorporates by reference =
the
>>> security considerations of the protocols being profiled.  There are
>>> perhaps too many to list individually, so something like "this =
document
>>> requires implementation and use of a number of other specifications =
in
>>> order to fulfil the RUE profile; the security considerations =
described
>>> in those documents apply accordingly to the RUE interactions" would
>>> probably work.
>> Done
>>=20
>>>=20
>>> It is perhaps obvious, but when a CA participates in a conversation =
they
>>> have access to the content of the conversation even though it is
>>> nominally a conversation between the two endpoints.  I think we =
should
>>> still state this explicitly, and perhaps note that there is an
>>> expectation that the CA will keep the communication contents in
>>> confidence, often backed by contractual or legal requirements.
>> Done
>>=20
>>>=20
>>> There's probably also something useful to say to compare the privacy
>>> properties of one-stage vs two-stage dial-around, in terms of which
>>> entities have access to information about the communicating =
endpoints.
>> Well the only difference is the CA has access to the called party =
number, but they usually have access to that anyway because of how =
dropped calls are handled.
>=20
> Okay.
>=20
>>=20
>>> I am not entirely sure if the referenced documents already cover =
this,
>>> but having the provider maintain the user's contacts database means =
that
>>> there is increased risk surface for unauthorized disclosure of that
>>> information (compared to it being maintained locally).
>> Yeah, but:
>> Locally maintained contacts are really hard to handle when you change =
devices
>> Locally maintained contacts don=E2=80=99t sync across devices.
>> I=E2=80=99ll put something here if you really think we need it, but =
getting the providers to manage contacts was a very hard fight that only =
recently became common (the US regulator now requires it).  Before, it =
was a vendor lock in.
>=20
> I'll defer to your domain expertise.
>=20
> Thanks for all the other good stuff (above and below) that I didn't =
reply
> on.  I look forward to the -10 (in the new year, presumably).
>=20
> -Ben
>=20
>>>=20
>>> Since different providers (within a given country) may have =
different
>>> policies, we might want to caution RUE implementations to have a =
user
>>> interaction step before proceeding to actually register with any =
given
>>> provider.
>> Done
>>=20
>>>=20
>>> NITS
>>>=20
>>> No need to reply to any of these; if you disagree, that's fine.
>>>=20
>>> Section 5.2.1
>>>=20
>>>  Negotiated media MUST follow the guidelines specified in Section 6 =
of
>>>  this document.
>>>=20
>>> If they MUST be followed, are they really guidelines, or =
requirements?
>> Changed to requirements
>>=20
>>>=20
>>> Section 5.2.3
>>>=20
>>>  To identify the owner of a RUE, the initial INVITE for a call from =
a
>>>  RUE, or the 200 OK accepting a call by a RUE, identifies the owner =
by
>>>=20
>>> I think s/the 200 OK accepting a call by a RUE/the 200 OK a RUE uses =
to
>>> accept a call/ would avoid ambiguity about whether this binds as
>>> (accepting a (call by a RUE)) vs ((accepting [of] a call) by a RUE).
>> Done
>>=20
>>>=20
>>> Section 9.1
>>>=20
>>>  provider names for a country code suitable for display, with a
>>>  corresponding a entry point to obtain information about that
>>>  provider.
>>>=20
>>> s/corresponding a/corresponding/
>> Fixed
>>=20
>>>=20
>>> Section 9.2
>>>=20
>>>  HTTPs web service.  There are two entry points.  One is used =
without
>>>  user credentials or parameters, the response includes configuration
>>>  data for new user sign up and dial around.  The other uses the
>>>=20
>>> Comma splice.
>> Did something, but maybe not what you wanted
>>=20
>>>=20
>>> Section 9.2.2
>>>=20
>>>  *  videomail: (optional) An SIP or HTTPS URI that can be called to
>>>     retrieve video mail messages.
>>>=20
>>> Can an HTTPS URI really "be called"?  (This text also appears in =
=C2=A79.3.)
>> Changed to =E2=80=9Cused"


--Apple-Mail=_994F0239-D099-454F-A1D9-245E562F056B
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"">Benjamin<div class=3D""><br class=3D""></div><div class=3D"">I =
submitted a -10 which I hope addresses all remaining issues.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Brian<br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Dec 24, 2021, at 9:22 PM, Benjamin Kaduk &lt;<a =
href=3D"mailto:kaduk@mit.edu" class=3D"">kaduk@mit.edu</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" 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"">Hi Brian,</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""><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"">Also inline</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""><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"">On Fri, Dec 24, 2021 at 03:58:21PM -0500, Brian Rosen =
wrote:</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""><blockquote type=3D"cite" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D"">Benjamin<br class=3D""><br class=3D"">Thanks for the close =
read of this document. &nbsp;Comments inline<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">On Dec 16, 2021, at 2:52 =
AM, Benjamin Kaduk via Datatracker &lt;<a href=3D"mailto:noreply@ietf.org"=
 class=3D"">noreply@ietf.org</a>&gt; wrote:<br class=3D""><br =
class=3D"">Benjamin Kaduk has entered the following ballot position =
for<br class=3D"">draft-ietf-rum-rue-09: Discuss<br class=3D""><br =
class=3D"">When responding, please keep the subject line intact and =
reply to all<br class=3D"">email addresses included in the To and CC =
lines. (Feel free to cut this<br class=3D"">introductory paragraph, =
however.)<br class=3D""><br class=3D""><br class=3D"">Please refer to <a =
href=3D"https://www.ietf.org/blog/handling-iesg-ballot-positions/" =
class=3D"">https://www.ietf.org/blog/handling-iesg-ballot-positions/</a><b=
r class=3D"">for more information about how to handle DISCUSS and =
COMMENT positions.<br class=3D""><br class=3D""><br class=3D"">The =
document, along with other ballot positions, can be found here:<br =
class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-rum-rue/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-rum-rue/</a><br =
class=3D""><br class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">DISCUSS:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">Thanks for writing this document; =
it's an important topic and I look<br class=3D"">forward to seeing =
interoperability in this space.<br class=3D""><br class=3D"">However, I =
don't think this document is quite ready for publication yet,<br =
class=3D"">as it has a number of internal inconsistencies (and at least =
one<br class=3D"">external inconsistency with IETF procedures) that =
would get in the way<br class=3D"">of interoperable implementation.<br =
class=3D""><br class=3D"">(1) The procedure for substituting an =
entryPoint from the provider list into<br class=3D"">the OpenAPI =
interface description for obtaining configuration data<br =
class=3D"">appears to be incompatible with BCP 190. &nbsp;Though there's =
not quite<br class=3D"">enough detail for me to be able to tell exactly =
what behavior is<br class=3D"">intended, the procedure of "replace =
localhost in the template with the<br class=3D"">value from provider =
discovery" seems like it implies that the value from<br =
class=3D"">provider discovery is just a hostname, and that we are =
requiring the RUM<br class=3D"">services to be accessible via HTTP at =
path /rum/v1 on that machine. &nbsp;The<br class=3D"">URI path namespace =
is under control of the owner of the host, and we<br class=3D"">cannot =
assert that we will occupy that portion of the namespace. &nbsp;The<br =
class=3D"">current version of BCP 190, RFC 8820, does allow us to say =
(effectively)<br class=3D"">"delegate a subtree of the path namespace to =
the protocol" by letting<br class=3D"">the owner of the host pick what =
base path to use for the protocol (even<br class=3D"">that would not =
have been allowed by its predecessor, RFC 7320), but we<br class=3D"">do =
need to let that host-specific path prefix be indicated somehow,<br =
class=3D"">whether by URL template or allowing a base path to be =
indicated in the<br class=3D"">provider discovery process.<br =
class=3D""></blockquote>There is no restriction that the provider =
discovery returns a host name. &nbsp;It=E2=80=99s string substitution =
that will be used for the entry points of the interface. &nbsp;It could =
be "<a =
href=3D"http://interface.external.example.com/rum/rue/opemapi/generic" =
class=3D"">interface.external.example.com/rum/rue/opemapi/generic</a>&lt;<=
a href=3D"http://interface.external.example.com/rum/rue/opemapi/generic" =
class=3D"">http://interface.external.example.com/rum/rue/opemapi/generic</=
a>&gt;=E2=80=9D. &nbsp;Whatever the string is, it=E2=80=99s substituted =
for =E2=80=9Clocalhost=E2=80=9D and that is used to find the server and =
define the entry points. &nbsp;After that string substitution, the path =
will end in, for example, =E2=80=9C../rum/v1/ProviderConfig=E2=80=9D. =
&nbsp;I think that should be 8820 compatible. &nbsp;I edited the =
descriptions of the mechanism to describe the parameters as strings to =
make it obvious that it is string substitution. &nbsp;<br class=3D""><br =
class=3D"">I hope that=E2=80=99s enough to address the concern.<br =
class=3D""></blockquote><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"">Yes, that should work; thanks for the =
clarification.</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">(2) There are a lot of inconsistencies about =
the parameters and data<br class=3D"">format of the various API =
responses as specified in prose, OpenAPI<br class=3D"">description, and =
examples. &nbsp;In particular, we also fail to make a clear<br =
class=3D"">statement about whether the prose or the OpenAPI description =
is<br class=3D"">normative and takes precedence in case of =
disagreement.<br class=3D""><br class=3D"">I'll list a bunch of things =
here; I made a fairly careful reading but am<br class=3D"">not willing =
to assert that this is a comprehensive listing. &nbsp;(A number<br =
class=3D"">of them also get comments in the section-by-section comments; =
sorry<br class=3D"">about that duplication.)<br class=3D""></blockquote>I =
am sorry we made these many uncaught mistakes. &nbsp;I=E2=80=99m having =
someone else go through and see if we can find more of them.<br =
class=3D""></blockquote><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"">Thanks. &nbsp;(In reading the other ADs' reviews, I see that =
my list was</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"">definitely =
not comprehensive, since I missed the case mismatch on "v1" vs</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"">"V1" :)</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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" class=3D"">Sections 9.2.1 and 9.2.2 =
list configuration data items in the<br class=3D"">"configuration data =
for new user sign up and dial around" and<br class=3D"">"configuration =
data for the RUE" configuration retrieval APIs, and per<br class=3D"">the =
note at the end of =C2=A79.2 they include the REQUIRED data items.<br =
class=3D"">However, there are a couple data items that are mentioned =
elsewhere in<br class=3D"">the document as if they are always going to =
be present, but are not<br class=3D"">present in these lists of required =
configuration parameters. &nbsp;In<br class=3D"">particular we talk =
about the "provider-domain" as coming from the<br =
class=3D"">configuration, and it appears in examples, but is not =
mentioned in the<br class=3D"">prose or OpenAPI format description.<br =
class=3D""></blockquote>This is an error. &nbsp;It appears to be the =
result of several changes to the interface that resulted in the OpenAPI =
localhost substitution discussed above. &nbsp;<br class=3D"">Somehow, we =
deleted provider-domain.<br class=3D"">I replaced it in both the =
description and the OpenAPI yaml.<br class=3D""><br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">The prose (and some =
examples) refer to an "outbound-proxies" RUE<br class=3D"">configuration =
element, but =C2=A79.2.2 and the OpenAPI description list the<br =
class=3D"">singular "outbound-proxy" (and with the corresponding =
difference in<br class=3D"">format/structure).<br =
class=3D""></blockquote>Fixed. &nbsp;It should be proxies plural =
throughout now.<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">The prose mentions "credentials" from the =
configuration, but no<br class=3D"">parameter of that name appears =
(there is some mention of password under<br class=3D"">"carddav" but =
that seems insufficiently generic to match all instances;<br =
class=3D"">sip-password also exists).<br class=3D""></blockquote>The =
first instance of credentials said:<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The registrar MAY =
authenticate using SIP digest authentication. The credentials to be used =
(username and password) MUST be supplied within the credentials<br =
class=3D"">This is standard sip terminology. &nbsp;The configuration has =
the username (constructed from the phone number and the provider-domain) =
and the sip-password (or as described in the sip-password description) =
are the credentials.<span class=3D"Apple-converted-space">&nbsp;</span><br=
 class=3D""></blockquote><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"">Okay, we can keep with the standard terminology. &nbsp;I =
would suggest, then,</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"">that all instances of "credentials" (with quotes, usually as =
'''matching</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"">"credentials" =
from the configuration''') be modified to use an unquoted</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"">word, so as to avoid implying =
that there is a JSON element by that name.</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">It does occur to me, although no one =
raised in in reviews, that sometimes there is an actual username that is =
used, instead of the phone number. &nbsp;I added that as optional (use =
the phone number if it=E2=80=99s not present), and reworded the text.<br =
class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">"display-name" appears in the example in Figure 5 but is not =
listed in<br class=3D"">=C2=A79.2.2<br class=3D""></blockquote>Fixed<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">The prose =
for the provider configuration resource indicates that the<br =
class=3D"">dialAround property is mandatory (it is not marked as =
"(OPTIONAL)"), but<br class=3D"">the OpenAPI specification does not list =
this property as required.<br class=3D""></blockquote>Fixed.<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">The prose =
for the provider configuration's "signup" property says that<br =
class=3D"">it is an array of JSON objects, but the OpenAPI description =
says that it<br class=3D"">is just a single object (not an array). =
&nbsp;Likewise for "dialAround" and<br class=3D"">"helpDesk=E2=80=9D.<br =
class=3D""></blockquote>Fixed. &nbsp;Should have been arrays<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">The prose =
for "phone-number" specifies E.164 format, but the OpenAPI<br =
class=3D"">description does not.<br class=3D""></blockquote>Fixed<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">"carddav" is triply inconsistent: the prose says username, =
password, and<br class=3D"">domain name are separated by "@" =
(presumably, in a single string), but<br class=3D"">the example only =
shows username and domain name in user@domain form, and<br class=3D"">the =
OpenAPI description says it should be an object with separate<br =
class=3D"">properties for username/password/domain, as well as an =
additional<br class=3D"">"sendLocationWithRegistration" property that is =
probably not supposed to<br class=3D"">be a child of "carddav=E2=80=9D.<br=
 class=3D""></blockquote>Fixed<br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">(repeating from the previous), the =
"sendLocationWithRegistration"<br class=3D"">property is listed as =
belonging to the "carddav" object in the OpenAPI<br =
class=3D"">description, though the prose and example indicate it should =
be a<br class=3D"">property of the toplevel configuration object.<br =
class=3D""></blockquote>Fixed<br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">The prose and OpenAPI description indicate =
that "ice-servers" is an<br class=3D"">array of strings, but the example =
has an array of objects that use the<br class=3D"">dictionary key to =
indicate whether each URI is a TURN or STUN server.<br =
class=3D""></blockquote>Fixed<br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">There are a number of references to =
"the configuration" in the body text<br class=3D"">prior to =C2=A79.2 =
where the configuration service is discussed. &nbsp;E.g., the<br =
class=3D"">first paragraph of =C2=A75.1 gives a hard requirement for =
registration and<br class=3D"">then makes a conditional reference to =
"the configuration" without any<br class=3D"">prose discussing how =
configuration retrieval interacts with<br class=3D"">registration. =
&nbsp;it may be useful to have a brief introductory mention of<br =
class=3D"">the data flow involving registration and configuration =
retrieval and how<br class=3D"">the two initialization processes (don't) =
interact.<br class=3D""></blockquote>I added some text in the top of the =
SIP Signaling section.<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><br class=3D"">I have a high-level comment or =
two about password usage in this<br class=3D"">document. &nbsp;I =
recognize that we're constrained in practice by the current<br =
class=3D"">state of SIP specification and the deployed ecosystem, but =
while<br class=3D"">username/password may currently be the lowest common =
denominator for<br class=3D"">authentication, it's far from best current =
practice. &nbsp;In a scenario<br class=3D"">like the one here, where the =
RUE is a dedicated (often hardware)<br class=3D"">product talking over a =
fixed protocol to a nearly fixed small set of<br class=3D"">providers, =
there's plenty of scope for using strong cryptography to<br =
class=3D"">authenticate the RUE, including public-key cryptography where =
the<br class=3D"">verifier does not need to store any per-user secret =
information. &nbsp;At<br class=3D"">present, Digest seems to be the =
strongest mechanism in the registry for<br class=3D"">usage with SIP, =
but I would advise assuming that that will change in the<br =
class=3D"">future and writing the spec and implementation in a way that =
is<br class=3D"">compatible with stronger authentication schemes.<br =
class=3D""></blockquote>We had a big discussion on the use of OAuth, =
which is specified for use in SIP. &nbsp;While there were strong =
proponents of supporting OAuth, it failed to gain consensus. =
&nbsp;It=E2=80=99s just not how SIP is deployed.<br class=3D"">I could =
rename the username/password things to try to anticipate some more =
robust mechanism, but the text has to change anyway and it didn=E2=80=99t =
seem worth it. &nbsp;A really, really important characteristic of a =
device like this is if power fails, and is restored, calls can arrive. =
&nbsp;This means you cannot require any user interaction on a power =
start. &nbsp;This really is at odds with how a lot of mechanisms work. =
&nbsp;We thought about installing certs and using mutual auth. =
&nbsp;Again NO sip systems we know do that. &nbsp;Installing certs =
securely with no user interaction is hard. &nbsp;There was no consensus =
to try to do that here. &nbsp;I personally don=E2=80=99t like the =
security situation we have, but we don=E2=80=99t have any alternatives =
we could realistically deploy.<br class=3D""></blockquote><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"">Indeed, compatibility with the =
deployed reality trumps ideological purity</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"">(though that doesn't keep us from documenting the weaknesses =
of what's</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"">deployed). =
&nbsp;Thanks for confirming.</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">Furthermore, this document in several places =
(I note a few in the<br class=3D"">per-secton comments) recommends or =
even requires the reuse of a<br class=3D"">username/password pair across =
multiple services. &nbsp;Best practices are to<br class=3D"">use any =
given password at exactly one service. &nbsp;In this regard one can<br =
class=3D"">roughly model the password as analogous to a pre-shared key =
-- it is<br class=3D"">useful for authenticating a peer in the sense =
that if the value is known<br class=3D"">only to two entities, and the =
party you're communicating with proves<br class=3D"">that they know the =
value, they must be the only other party that knows<br class=3D"">the =
secret value. &nbsp;But once you reuse the password at multiple =
services,<br class=3D"">that logic falls apart, as the party you're =
communicating with could be<br class=3D"">the user, or it could be =
another service that shares the secret.<br class=3D"">Granted, when used =
with digest the password itself is not sent to the<br class=3D"">server =
for every authentication, but the server typically has access to<br =
class=3D"">it at some point, and even possession of the password hash in =
a<br class=3D"">verification database allows for offline brute-force =
attack, which has<br class=3D"">become comparatively cheap in recent =
years and even the availability of<br class=3D"">dedicated hardware for =
password cracking.<br class=3D""></blockquote>We could force the =
secondary services to have separate passwords. &nbsp;Since they all come =
from the same config, they are all supplied by the default provider, and =
they all identify the same user, albeit on different service =
deployments, we didn=E2=80=99t think there really was much difference. =
&nbsp;The one place I would be very reluctant to force separate =
credentials is stun/turn, were it=E2=80=99s just too common to use the =
same credentials. There is no value in protecting, say the configuration =
service independently of the sip service or the turn service. &nbsp;It =
really doesn=E2=80=99t matter at all. &nbsp;<br =
class=3D""></blockquote><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 main value in separate passwords for the secondary =
services would be</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"">that compromise of one such service does not imply full =
compromise of the</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"">"account". &nbsp;As above, though, what people are willing to =
deploy is the main</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"">consideration for me -- I don't feel a need to "require" =
something with an</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"">RFC 6919 "MUST (BUT WE KNOW YOU WON'T)".</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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">In =
particular, SHA-512 is not considered to be a best-practice hash<br =
class=3D"">function for password hashing, since it is highly =
parallelizable and not<br class=3D"">"memory-hard". &nbsp;RFC 9106 =
specifies Argon2 (via the IRTF CFRG), the<br class=3D"">winner of the =
password hashing competition; it is the state of the art<br class=3D"">for=
 password hashing, and even prior to that publication we had scrypt<br =
class=3D"">available in RFC 7914 that is a significant improvement on =
the SHA-2<br class=3D"">family of functions. &nbsp;That said, it's not =
currently listed in the IANA<br class=3D"">registry for hash algorithms =
for HTTP (and SIP) digest authentication,<br class=3D"">so I am not sure =
that we can usefully advocate for its usage at the<br class=3D"">present =
time.<br class=3D""></blockquote>We only very recently deprecated RC4, =
and I=E2=80=99d bet 99,99% of sip services deployed still use it. =
&nbsp;I was able to make this spec use SHA-512, but that=E2=80=99s the =
very best we can do in a profile. &nbsp;We could try to get some of the =
SIP guys to put through an RFC to support Argon2, but that would have to =
happen before this doc could use it.<br class=3D""></blockquote><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"">Agreed.</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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">Section =
4<br class=3D""><br class=3D"">Thanks for mandating RFC 7525 compliance. =
&nbsp;I note that<br class=3D"">draft-ietf-uta-rfc7525bis is in progress =
in the UTA WG. &nbsp;Though it will<br class=3D"">probably be published =
after this document, it may be a useful<br class=3D"">informative =
reference with forward-looking guidance on how to best<br =
class=3D"">secure TLS.<br class=3D""></blockquote>I=E2=80=99ll try to =
remember that for when this doc gets an update.<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">&nbsp;All =
text data payloads not otherwise constrained by a specification<br =
class=3D"">&nbsp;in another standards document MUST be encoded as =
Unicode UTF-8.<br class=3D""><br class=3D"">I think we'd typically =
reference RFC 8259 here.<br class=3D""></blockquote>I=E2=80=99m worried =
that there might be some incompatibility between 8259 and OpenAPI. =
&nbsp;OpenAPI references<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/html/draft-wright-json-schema-00"=
 =
class=3D"">https://datatracker.ietf.org/doc/html/draft-wright-json-schema-=
00</a><span class=3D"Apple-converted-space">&nbsp;</span>&lt;<a =
href=3D"https://datatracker.ietf.org/doc/html/draft-wright-json-schema-00"=
 =
class=3D"">https://datatracker.ietf.org/doc/html/draft-wright-json-schema-=
00</a>&gt;!!!!<br class=3D"">The text is specific to string content and =
not JSON format.<br class=3D""></blockquote><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"">It seems likely that I got my RFC numbers confused here and I =
meant to say</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"">3629 for =
UTF-8 itself. &nbsp;Sorry about that.</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""><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 8259 reference might still be relevant, as JSON Schema =
still uses JSON</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"">(but, predating 8259, it references 7159 instead), but I =
didn't look for an</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"">appropriate place to put it.</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">Section 5.1<br class=3D""><br =
class=3D"">&nbsp;The registrar MAY authenticate using SIP digest =
authentication. &nbsp;The<br class=3D"">&nbsp;credentials to be used =
(username and password) MUST be supplied<br class=3D"">&nbsp;within the =
credentials section of the configuration and identified by<br =
class=3D"">&nbsp;the realm the registrar uses in a digest challenge. =
&nbsp;This username/<br class=3D""><br class=3D"">Which entity is =
authenticating to which other entity here? &nbsp;The phrasing<br =
class=3D"">"&lt;X&gt; MAY authenticate" implies that it is X that is =
authenticating to<br class=3D"">some other entity, but that does not =
seem to correspond to my model of<br class=3D"">the flow here, where the =
RUE is authenticating to the registrar. &nbsp;If the<br class=3D"">flow =
is to be the other way, we would say "the registrar MAY<br =
class=3D"">authenticate the RUE using SIP digest authentication=E2=80=9D.<=
br class=3D""></blockquote>I'll make that change. &nbsp;The registrar =
authenticates the RUE<br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">Also, I note that (HTTP) SCRAM authentication =
has superior security<br class=3D"">properties to Digest, but =
unfortunately I don't see any evidence that<br class=3D"">its use for =
SIP is defined yet.<br class=3D""></blockquote>Yeah, yet another =
weakness.<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">Section 5.2.1<br class=3D""><br =
class=3D"">&nbsp;The SIP URIs in the To field and the Request-URI MUST =
be formatted as<br class=3D"">&nbsp;specified in subsection Section 5.4 =
using the destination phone<br class=3D"">&nbsp;number, or as SIP URIs, =
as provided in the configuration<br class=3D"">&nbsp;(Section 9.2). =
&nbsp;[...]<br class=3D""><br class=3D"">I'm not sure that I'm unpacking =
this properly. &nbsp;(The construction "the<br class=3D"">SIP URIs MUST =
be formatted as [...], or as SIP URIs", makes me wonder<br class=3D"">if =
there are somehow non-SIP URIs involved even though we start off with<br =
class=3D"">"the SIP URIs".) &nbsp;Is the idea that I either take the URI =
directly from<br class=3D"">the configuration ("as-is") or I format it =
as per =C2=A75.4 but not anything<br class=3D"">else?<br =
class=3D""></blockquote>There are two ways you specify the =46rom and To =
header fields in SIP when you are using telephone numbers and not =
usernames. &nbsp;<br class=3D"">One is a SIP URI <a =
href=3D"sip:2025551212@red.example.com;user=3Dphone" =
class=3D"">sip:2025551212@red.example.com;user=3Dphone</a>. &nbsp;<br =
class=3D"">The other is a TEL URI: <a href=3D"tel:2025551212" =
class=3D"">tel:2025551212</a>.<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">Phone number =
and domain come from the configuration. &nbsp;Does that help?<br =
class=3D""></blockquote><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"">Uh...maybe.</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"">Do we need to s/or as SIP URIs/or as TEL URIs/? &nbsp;I don't =
see how the</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"">current text =
allows the TEL version that you describe.</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""><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"">I'd also consider making the "as provided in the =
configuration" clause a</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"">separate sentence, like "the phone number and domain (if =
applicable) are</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"">provided in the configuration (Section 9.2)".</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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">Section =
5.2.2<br class=3D""><br class=3D"">&nbsp;party telephone number. =
&nbsp;In two-stage dial-around, the To URI is the<br =
class=3D"">&nbsp;front door URI (see Section 9.2) of the dial-around =
provider and the<br class=3D"">&nbsp;domain of the URI is the provider =
domain from the configuration. &nbsp;The<br class=3D""><br class=3D"">Is =
"the URI" in "the domain of the URI" referring to "the To URI", or<br =
class=3D"">some other URI (the Request-URI, perhaps)?<br =
class=3D""></blockquote>Yeah, that=E2=80=99s pretty awkward. &nbsp;I =
shortened it to:<br class=3D"">In two-stage dial-around, the To URI is =
the front door URI (see Section 9.2) of the dial-around provider.<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D""><br =
class=3D"">The prose lists the call originator as (VRS user) =
+1-555-222-0001, but<br class=3D"">the URIs in Figure 1 that are not the =
call recipient appear as<br class=3D"">+18135551212; are those numbers =
supposed to be different like that?<br class=3D""></blockquote>I fixed =
the telephone numbers being wrong. &nbsp;The deletion of the dashes =
follows text in 5.4<br class=3D""></blockquote><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"">Right, I just meant the actual numbers. =
&nbsp;Thanks.</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""><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""><blockquote type=3D"cite" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">Section =
5.2.3<br class=3D""><br class=3D"">&nbsp;owner". &nbsp;The URI MAY be an =
HTTPS URI or Content-Indirect URL. &nbsp;The<br class=3D"">&nbsp;latter =
is defined by [RFC2392] to locate message body parts. &nbsp;This<br =
class=3D""><br class=3D"">RFC 2392 seems to define a "Content-ID" URI =
(with "cid" scheme) but not<br class=3D"">a "Content-Indirect" URL.<br =
class=3D""></blockquote>Fixed. &nbsp;I can=E2=80=99t tell you how many =
times I have made that mistake.<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><br class=3D"">Section 5.2.5<br class=3D""><br =
class=3D"">&nbsp;Implementations MUST implement Additional Data, =
[RFC7852]. &nbsp;RUE<br class=3D"">&nbsp;devices MUST implement Data =
Provider, Device Implementation and<br class=3D"">&nbsp;Owner/Subscriber =
Information blocks.<br class=3D""><br class=3D"">The string "Device =
Implementation" does not seem to appear in RFC 7852,<br class=3D"">though =
"Device Information" does.<br class=3D""></blockquote>Fixed<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">Section 7.1<br class=3D""><br class=3D"">&nbsp;of an email =
address. &nbsp;If the request triggers a challenge for digest<br =
class=3D"">&nbsp;authentication credentials, the RUE MUST continue using =
matching<br class=3D"">&nbsp;"credentials" from the configuration. =
&nbsp;If no matching credentials are<br class=3D"">&nbsp;configured, the =
RUE MUST use the SIP credentials from the<br =
class=3D"">&nbsp;configuration. &nbsp;[...]<br class=3D""><br =
class=3D"">Do we really want a MUST-level requirement to reuse the SIP =
credentials?<br class=3D"">Best practices for credentials are to have a =
1:1 relationship between<br class=3D"">credentials and where they are =
used and this sort of reuse is basically<br class=3D"">the polar =
opposite.<br class=3D""></blockquote>See above.<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">Section =
9.1<br class=3D""><br class=3D"">&nbsp;non-mandatory-to use functions =
and SHALL NOT delete any objects,<br class=3D"">&nbsp;members of objects =
or functions. &nbsp;This means an implementation of a<br =
class=3D"">&nbsp;specific major version and minor version is backwards =
compatible with<br class=3D"">&nbsp;all minor versions of the major =
version. &nbsp;[...]<br class=3D""><br class=3D"">(This might all be =
covered by Rob's discuss point; I will read the<br class=3D"">replies on =
that thread and you don't need to duplicate content here for<br =
class=3D"">my benefit.)<br class=3D"">This statement doesn't seem to =
contain enough information to be useful.<br class=3D"">I think that a =
statement about backwards (or forwards) compatibility<br class=3D"">should=
 be specific about whether it applies to the implementation of the<br =
class=3D"">client or the web service, and that backwards compatibility =
would<br class=3D"">require that the implementation in question =
interoperate with a peer at<br class=3D"">any same or previous minor =
version. &nbsp;Just saying "compatible with all<br class=3D"">minor =
versions of the major version" would also make a statement about<br =
class=3D"">forward compatibility, which I think is allowable under these =
rules for<br class=3D"">what is allowed to change in minor versions, and =
it would be useful to<br class=3D"">make a statement about forward =
compatibility.<br class=3D""></blockquote>I added: "Either may have any =
higher or lower minor revision and interoperate with its counterpart =
with the same major version." &nbsp;<br class=3D"">after "Backwards =
compatibility applies to both the server and the client."<br =
class=3D""><br class=3D"">I think that avoids having to talk about =
forwards compatibility. &nbsp;<br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">Section 9.2<br class=3D""><br =
class=3D"">&nbsp;The interface to obtain configuration data is described =
by an OpenAPI<br class=3D"">&nbsp;[OpenAPI] interface description. =
&nbsp;In that interface description, the<br class=3D"">&nbsp;"servers" =
component is specified as "localhost". &nbsp;The entry point<br =
class=3D"">&nbsp;obtained from the provider list (Section 9.1) is =
sutituted for<br class=3D"">&nbsp;"localhost" to obtain the server =
prefix of the interface. &nbsp;[...]<br class=3D""><br class=3D"">I note =
that the OpenAPI description for /Versions has an override for<br =
class=3D"">"servers", and the value listed there does not include the =
string<br class=3D"">"localhost". &nbsp;Some clarity that it is also =
expected to be affected by<br class=3D"">this kind of substitution seems =
in order.<br class=3D""></blockquote>That=E2=80=99s an error. =
&nbsp;Changed the server override in Versions to:<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- url: <a =
href=3D"https://localhost/rum" class=3D"">https://localhost/rum</a><br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D""><br class=3D"">&nbsp;In both the queries, an optional =
parameter may be provided to the<br class=3D"">&nbsp;interface which is =
an API Key. &nbsp;The implementation MAY have an API<br =
class=3D"">&nbsp;Key obtained from the provider and specific to the =
implementation.<br class=3D"">&nbsp;The method the API Key is obtained =
is not specified in this document.<br class=3D"">&nbsp;The provider MAY =
refuse to provide service to an implementation<br =
class=3D"">&nbsp;presenting an API Key it does not recognize.<br =
class=3D""><br class=3D"">I note that the IETF does have a standard for =
conveying authorization<br class=3D"">information on the web -- OAuth =
2.0. &nbsp;It may not be a direct "drop-in"<br class=3D"">fit here, due =
to the need for a preexisting relationship with an<br =
class=3D"">authorization server, but perhaps it is worth mentioning as =
an option<br class=3D"">in addition to this provider-specific "API key" =
protocol?<br class=3D""></blockquote>This isn=E2=80=99t a user =
authorization. &nbsp;It=E2=80=99s a developer authorization.<br =
class=3D"">OAuth can=E2=80=99t be used, because the developer can=E2=80=99=
t provide credentials when the device connects.<br =
class=3D""></blockquote><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"">Oh, that kind of API key. &nbsp;Then we get to pull in the =
security</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"">considerations =
for attempting to keep secret a value that's shipped in the</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"">software binary and sent on the =
wire (something that repeatedly doesn't</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"">happen for the official mobile apps for popular =
services)...</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""><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""><blockquote type=3D"cite" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">&nbsp;Also =
in both queries, the RUE device provides a required parameter<br =
class=3D"">&nbsp;which contains an instance identifier. &nbsp;This =
parameter MUST be the<br class=3D"">&nbsp;same value each time this =
instance (same implementation on same<br class=3D"">&nbsp;device) =
queries the interface. &nbsp;This MAY be used by the provider, for<br =
class=3D"">&nbsp;example, to associate a location with the instance for =
emergency<br class=3D"">&nbsp;calls.<br class=3D""><br class=3D"">Is =
there any cryptography to provide assurance that the instance<br =
class=3D"">identifier is indeed always used only by the one single =
instance? &nbsp;The<br class=3D"">description here sounds roughly like a =
bearer token, which is far from<br class=3D"">best practice for this =
sort of thing. &nbsp;Indeed, in other contexts a given<br =
class=3D"">instance is often identified solely by its public key, and =
must<br class=3D"">authenticate with the corresponding private key in =
order to act as the<br class=3D"">identified instance.<br =
class=3D""></blockquote>No, and I don=E2=80=99t think it=E2=80=99s =
needed, &nbsp;A typical use case here is a device in your home and one =
on your phone that has the same credentials and phone number. &nbsp;We =
just need to differentiate them. It=E2=80=99s not a security =
property.<br class=3D"">The consequences of confusion is fairly low. =
&nbsp;As stated above, we did go through some discussions of =
provisioning private keys to each device and gave up due to the =
complexity vs the sophistication of the user. &nbsp;There really isn=E2=80=
=99t any reasonable plug and play mechanism here. &nbsp;We can=E2=80=99t =
use anything like Acme.<span =
class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D""></blockquote><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"">Thanks for the background; I don't see a need to re-hash =
that.</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""><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"">Though the =
description above makes me wonder if the instance ID is scoped</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"">to a given user/credentials? =
&nbsp;That would be better in some ways, I think.</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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">&nbsp;The =
configuration API also provides the same version mechanism as<br =
class=3D"">&nbsp;specified above in Section 9.1. &nbsp;The version of =
the configuration<br class=3D"">&nbsp;service MAY be different than the =
version of the provider list<br class=3D"">&nbsp;service.<br =
class=3D""><br class=3D"">Not only that, but the services are expected =
to be versioned<br class=3D"">independently, so there is no particular =
relationship between version<br class=3D"">X.Y of the one and version =
X.Y of the other=E2=80=A6right?<br class=3D""></blockquote>That=E2=80=99s =
correct<br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">Actually, having gone and looked further, the OpenAPI =
document seems<br class=3D"">to indicate that there's a single /Versions =
resource common across the<br class=3D"">/Providers, /ProviderConfig, =
and /RueConfig APIs, which makes me<br class=3D"">confused as to how the =
versions of the two services might actually be<br class=3D"">different =
(let alone versioned independently).<br class=3D""></blockquote>There =
are two services (the provider list service and the configuration =
service).<br class=3D"">The former has one entry point, the latter has =
two: the provider config and the device config.<br class=3D""><br =
class=3D"">The two services have different versions. &nbsp;The two entry =
points in the configuration service have the same version.<br =
class=3D""></blockquote><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"">That looks like the key insight that I was missing. &nbsp;Any =
chance we could</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"">get that sentiment expressed in the document?</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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">The =
way this mechanism is designed, you can make an implementation that =
works on several (or all) major versions and any minor version of each =
major version.<br class=3D"">For server implementation, if it support =
multiple versions, each one has a separate URI (the version is in the =
URI). &nbsp;The client composes the URI it wishes to use by looking at =
the Versions entry point for the service to find a compatible version =
and uses that and uses the version to choose an Open API yaml (and the =
code the yaml generates).<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><br class=3D"">Section 9.2.1<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;- &nbsp;uri: a URI to the website for =
creating a new account in the<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;supported language. =
&nbsp;The new user signup URI may only initiate<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;creation of a new =
account. &nbsp;Various vetting, approval and other<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;processes may be =
needed, which could take time, before the<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;account is =
established. &nbsp;The result of creating a new account<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;would be a username =
and password, which would be manually<br class=3D""><br class=3D"">I =
strongly suggest using a more generic phrasing (e.g., "would be<br =
class=3D"">account credentials (e.g., username and password)") to allow =
for<br class=3D"">seamless transition to stronger authentication =
technologies without<br class=3D"">specification change.<br =
class=3D""></blockquote>Done<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><br class=3D"">Section 9.2.2<br class=3D""><br =
class=3D"">&nbsp;* &nbsp;lifetime: (optional) Specifies how long (in =
seconds) the RUE MAY<br class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;cache the =
configuration values. &nbsp;Values may not be valid when<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;lifetime expires. &nbsp;If the RUE =
caches configuration values, it MUST<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;cryptographically protect them. =
&nbsp;[...]<br class=3D""><br class=3D"">In other contexts, =
"cryptographically protect" would mean to encrypt,<br =
class=3D"">cryptographically sign, or compute a keyed MAC over the data. =
&nbsp;If the<br class=3D"">intent here is just to record a cryptographic =
checksum of the data,<br class=3D"">that's probably better stated in =
terms of a checksum.<br class=3D""><br class=3D"">In particular, this =
current text gives no indication of what threat the<br =
class=3D"">cryptography is supposed to protect against, so =
implementations are<br class=3D"">unlikely actually provide uniform =
protection against the intended<br class=3D"">threat.<br =
class=3D""></blockquote>I added some text so it now reads:<br =
class=3D"">it MUST cryptographically protect them against unauthorized =
disclosure (e.g. by other applications on the platform the RUE is built =
on).<span class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D""></blockquote><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"">Thanks!</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">&nbsp;* &nbsp;sip-password: (optional) a =
password used for SIP, STUN and TURN<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;authentication. &nbsp;The RUE device =
retains this data, which must be<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;stored securely. &nbsp;[...]<br =
class=3D""><br class=3D"">Akin to the above, this doesn't indicate what =
threat "stored securely"<br class=3D"">is intended to protect against. =
&nbsp;While I would *hope* that "protect<br class=3D"">passwords" is =
instinctive to developers, I wouldn't want to rely on it.<br =
class=3D""></blockquote>I added the same text to that.<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;password MUST be used. &nbsp;If it =
was never supplied, the password<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;used to authenticate to the =
configuration service is used for SIP,<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;STUN and TURN.<br class=3D""><br =
class=3D"">In the general case, this directive is a gaping security hole =
(exposing<br class=3D"">the RUE's SIP credentials to arbitrary external =
STUN/TURN servers, for<br class=3D"">example). &nbsp;I think we must =
qualify that the reuse of credentials is only<br class=3D"">for the =
servers listed in the "ice-servers" configuration directive.<br =
class=3D"">(And ideally we would not encourage reuse of credentials at =
all.)<br class=3D""></blockquote>Edited to say =E2=80=9Cis used for SIP, =
as well as STUN and TURN servers mentioned in this configuration."<br =
class=3D""></blockquote><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"">Thanks.</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">&nbsp;* &nbsp;carddav: (optional) A username, =
password and domain name<br class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;(separated =
by ""@"") identifying a "CardDAV" server and account<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;that can be used to synchronize the =
RUE's contact list with the<br class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;contact =
list managed by the provider. &nbsp;If username or password are<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;not supplied, the main account =
credentials are used.<br class=3D""><br class=3D"">There are three data =
items but only one separator listed. &nbsp;Is this<br class=3D"">really =
to be "username@password@domain"?<br class=3D"">It would be great if we =
could make ourselves more generic than<br class=3D"">username+password =
as credentials, and (as mentioned previously) avoid<br class=3D"">reuse =
of credentials.<br class=3D""></blockquote>I fixed this to have separate =
fields in an object in the config.<br class=3D"">I don=E2=80=99t know =
any other usable authentication mechanism for cardav in this =
environment, but I=E2=80=99m far from an expert.<br =
class=3D""></blockquote><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"">I suspect that I'm even farther from expert than you =
are...</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""><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""><blockquote type=3D"cite" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">&nbsp;* =
&nbsp;ice-servers: (optional) An array of URLs identifying STUN and =
TURN<br class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;servers available for use by =
the RUE for establishing media<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;streams in calls via the provider.<br =
class=3D""><br class=3D"">Is any given entry required to offer both STUN =
and TURN services, or can<br class=3D"">a server provide just one or the =
other? &nbsp;Both this text and my<br class=3D"">understanding of the =
OpenAPI description seem to indicate that this is a<br class=3D"">flat =
list intermingling STUN and TURN servers, but the example in Figure<br =
class=3D"">5 seems to show each element of the array being a JSON object =
that<br class=3D"">contains one or more of the keys "stun" and "turn". =
&nbsp;The structure in<br class=3D"">that example would obviate any =
confusion about which services are<br class=3D"">offered, and is =
probably preferred.<br class=3D""></blockquote>I fixed the OpenApi to =
use the strings (=E2=80=9Cstun=E2=80=9D and =E2=80=9Cturn=E2=80=9D).<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">Section 9.2.3<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"contacts": "<a =
href=3D"https://red.example.net:443/contacts/1dess45awd" =
class=3D"">https://red.example.net:443/contacts/1dess45awd</a>",<br =
class=3D""><br class=3D"">I suggest putting a bit more entropy in the =
URL, in the vein of<br class=3D""><a =
href=3D"https://www.w3.org/2001/tag/doc/capability-urls/" =
class=3D"">https://www.w3.org/2001/tag/doc/capability-urls/</a> (even if =
this resource<br class=3D"">is likely to require the username+password =
authentication discussed<br class=3D"">earlier).<br =
class=3D""></blockquote>Made it a V4 UUID =
(3617b719-2c3a-46f4-9c13-538f7efd0b21)<br class=3D""><blockquote =
type=3D"cite" class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"carddav": "<a =
href=3D"mailto:bob@red.example.com" class=3D"">bob@red.example.com</a>" =
,<br class=3D""><br class=3D"">The prose indicates this should contain a =
password as well as the<br class=3D"">username and domain name that are =
present. &nbsp;How is the password<br class=3D"">specified?<br =
class=3D""></blockquote>This is fixed to have separate fields for =
domain, username and password<br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">Section 9.3<br class=3D""><br class=3D"">Given =
the "are formally specified" language, I expect that the intent is<br =
class=3D"">for the OpenAPI description to be normative and take =
precedence in case<br class=3D"">of conflict with the prose/examples. =
&nbsp;It's probably worth stating that<br class=3D"">explicitly.<br =
class=3D""></blockquote>Done.<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- in: =
query<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;nam=
e: instanceId<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;sch=
ema:<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;type: string<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;req=
uired: true<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;des=
cription: Unique string for this implementation<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;on this device<br class=3D""><br class=3D"">Is this self-assigned by =
the client or assigned by some external<br class=3D"">authority? =
&nbsp;The allocation procedure is important for ensuring that the<br =
class=3D"">instance IDs are actually globally unique (with high =
probability).<br class=3D"">(Note that this parameter is used in both =
/ProviderConfig and<br class=3D"">/RueConfig.)<br =
class=3D""></blockquote>Self assigned by the client. &nbsp;There is no =
dependence on this for Provider config.<br class=3D""><br =
class=3D"">I=E2=80=99ll suggest it be something like a UUID.<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">Section =
10.2<br class=3D""><br class=3D"">The rest of the document does not =
appear to contain any text covering<br class=3D"">the usage of the =
"rue-owner" purpose value. &nbsp;Should we say something<br =
class=3D"">about when it's used and what semantics it conveys?<br =
class=3D""></blockquote>See Section 5.2.3. I added a cross reference.<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">Section 11<br class=3D""><br class=3D"">I think we should =
make some statement that incorporates by reference the<br =
class=3D"">security considerations of the protocols being profiled. =
&nbsp;There are<br class=3D"">perhaps too many to list individually, so =
something like "this document<br class=3D"">requires implementation and =
use of a number of other specifications in<br class=3D"">order to fulfil =
the RUE profile; the security considerations described<br class=3D"">in =
those documents apply accordingly to the RUE interactions" would<br =
class=3D"">probably work.<br class=3D""></blockquote>Done<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">It is perhaps obvious, but when a CA participates in a =
conversation they<br class=3D"">have access to the content of the =
conversation even though it is<br class=3D"">nominally a conversation =
between the two endpoints. &nbsp;I think we should<br class=3D"">still =
state this explicitly, and perhaps note that there is an<br =
class=3D"">expectation that the CA will keep the communication contents =
in<br class=3D"">confidence, often backed by contractual or legal =
requirements.<br class=3D""></blockquote>Done<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">There's =
probably also something useful to say to compare the privacy<br =
class=3D"">properties of one-stage vs two-stage dial-around, in terms of =
which<br class=3D"">entities have access to information about the =
communicating endpoints.<br class=3D""></blockquote>Well the only =
difference is the CA has access to the called party number, but they =
usually have access to that anyway because of how dropped calls are =
handled.<br class=3D""></blockquote><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"">Okay.</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D"">I am not entirely sure if the referenced =
documents already cover this,<br class=3D"">but having the provider =
maintain the user's contacts database means that<br class=3D"">there is =
increased risk surface for unauthorized disclosure of that<br =
class=3D"">information (compared to it being maintained locally).<br =
class=3D""></blockquote>Yeah, but:<br class=3D"">Locally maintained =
contacts are really hard to handle when you change devices<br =
class=3D"">Locally maintained contacts don=E2=80=99t sync across =
devices.<br class=3D"">I=E2=80=99ll put something here if you really =
think we need it, but getting the providers to manage contacts was a =
very hard fight that only recently became common (the US regulator now =
requires it). &nbsp;Before, it was a vendor lock in.<br =
class=3D""></blockquote><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"">I'll defer to your domain expertise.</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""><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"">Thanks for all the other good =
stuff (above and below) that I didn't reply</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"">on. &nbsp;I look forward to the =
-10 (in the new year, presumably).</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""><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"">-Ben</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">Since different providers (within a given =
country) may have different<br class=3D"">policies, we might want to =
caution RUE implementations to have a user<br class=3D"">interaction =
step before proceeding to actually register with any given<br =
class=3D"">provider.<br class=3D""></blockquote>Done<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">NITS<br =
class=3D""><br class=3D"">No need to reply to any of these; if you =
disagree, that's fine.<br class=3D""><br class=3D"">Section 5.2.1<br =
class=3D""><br class=3D"">&nbsp;Negotiated media MUST follow the =
guidelines specified in Section 6 of<br class=3D"">&nbsp;this =
document.<br class=3D""><br class=3D"">If they MUST be followed, are =
they really guidelines, or requirements?<br =
class=3D""></blockquote>Changed to requirements<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">Section =
5.2.3<br class=3D""><br class=3D"">&nbsp;To identify the owner of a RUE, =
the initial INVITE for a call from a<br class=3D"">&nbsp;RUE, or the 200 =
OK accepting a call by a RUE, identifies the owner by<br class=3D""><br =
class=3D"">I think s/the 200 OK accepting a call by a RUE/the 200 OK a =
RUE uses to<br class=3D"">accept a call/ would avoid ambiguity about =
whether this binds as<br class=3D"">(accepting a (call by a RUE)) vs =
((accepting [of] a call) by a RUE).<br class=3D""></blockquote>Done<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">Section 9.1<br class=3D""><br class=3D"">&nbsp;provider names =
for a country code suitable for display, with a<br =
class=3D"">&nbsp;corresponding a entry point to obtain information about =
that<br class=3D"">&nbsp;provider.<br class=3D""><br =
class=3D"">s/corresponding a/corresponding/<br =
class=3D""></blockquote>Fixed<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><br class=3D"">Section 9.2<br class=3D""><br =
class=3D"">&nbsp;HTTPs web service. &nbsp;There are two entry points. =
&nbsp;One is used without<br class=3D"">&nbsp;user credentials or =
parameters, the response includes configuration<br class=3D"">&nbsp;data =
for new user sign up and dial around. &nbsp;The other uses the<br =
class=3D""><br class=3D"">Comma splice.<br class=3D""></blockquote>Did =
something, but maybe not what you wanted<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">Section =
9.2.2<br class=3D""><br class=3D"">&nbsp;* &nbsp;videomail: (optional) =
An SIP or HTTPS URI that can be called to<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;retrieve video mail messages.<br =
class=3D""><br class=3D"">Can an HTTPS URI really "be called"? =
&nbsp;(This text also appears in =C2=A79.3.)<br =
class=3D""></blockquote>Changed to =
=E2=80=9Cused"</blockquote></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_994F0239-D099-454F-A1D9-245E562F056B--


From nobody Thu Jan 20 06:54:02 2022
Return-Path: <br@brianrosen.net>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C87D93A14C5 for <rum@ietfa.amsl.com>; Thu, 20 Jan 2022 06:53:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level: 
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20210112.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11QqloW8wkms for <rum@ietfa.amsl.com>; Thu, 20 Jan 2022 06:53:51 -0800 (PST)
Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 723DC3A14BD for <rum@ietf.org>; Thu, 20 Jan 2022 06:53:51 -0800 (PST)
Received: by mail-il1-x131.google.com with SMTP id r16so5167828ile.8 for <rum@ietf.org>; Thu, 20 Jan 2022 06:53:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=4nzVgKmSkaPc+0ecj5AP1mpimnupSquiQP6EuRB56Hg=; b=xvVpy0AVxRWE3B9gznI6Rp3pdXSYNMEKRn2AZ9Zx2OZwlIiTjQN/ZVabEs9OghPcIx 5Xtjgc8U4qjisHuSPQ+UfjUvQKI2DyjKGAb0EIIgKQfWwTiesnP4AvUjn1fnZ7K1I9sx F9zWZMG88cDNgmiTcaQenjNl56LI/9o58OQE3e98g3uAFWmDu7Jl6t5Yuk6ua+OG5+wl d3O/ObN+quIuqEuBKDWvwPQWONy9vdaJ+uFwgoCM2eCDD2bcmO1Q2OIXrFs1hOo1NFQh Qv69I58U+jLPX6IK+1gXczFkeU5lfasMr74wHwSDzhLPn7JzdPnPrHnSZeEZ02bWFz6Q 3pAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=4nzVgKmSkaPc+0ecj5AP1mpimnupSquiQP6EuRB56Hg=; b=U39QppnNvj9NMRkBVreJM+UHv/p8TFfNuEalwA7AOfF6QdlxyydhDt7bzawFdIur5F yoTS87TvivvzvCVEKYuWKm608SeT5QP+pMtK4EwuX39c/lbn/VA+5UVQctZoHQjsvAfS yVJhFQIP/NjFOvGuRqRTKhXf6jiNKMeDQSRB7dJPjzjIL0SfoawR8Gp87fA7kz8FV+Nl DuFXN31QUqLHDFFACalyoqldxLkWB2gEEv/fKy9RnH6e5i8LSnQGKjLENMuNsMdXT5b8 6qwzbN/IU4s0AfOI49qhM9Qe+Ztw0KUeRJ+tNto8AuiM2BMkzp+UgLm7nmsuXnzuBARL KA3w==
X-Gm-Message-State: AOAM533B0CfyKqzR3RnUMkAy24XCvoNCP2BbPud8Y8Keo9FCl3TxBDCg u5HPeWjwZRCra/ounnU/A1QPMg==
X-Google-Smtp-Source: ABdhPJzOGHnYRiLSfqRNncf7eyxFJfcM8iF5qfANKDHBjuVj4xloqxBZXRiyESqUatY2KiIMaVQDlA==
X-Received: by 2002:a05:6e02:1bc1:: with SMTP id x1mr8764244ilv.68.1642690429680;  Thu, 20 Jan 2022 06:53:49 -0800 (PST)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id x6sm1485338ill.78.2022.01.20.06.53.48 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jan 2022 06:53:49 -0800 (PST)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <ECF95B5B-AF48-4C9F-A0E9-F52D602BE604@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4069DAD9-E536-46D0-BAFB-9ED0A62A2585"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\))
Date: Thu, 20 Jan 2022 09:53:48 -0500
In-Reply-To: <64AD6B8B-9D35-4269-AD74-FD8755F21F2D@brianrosen.net>
Cc: The IESG <iesg@ietf.org>, draft-ietf-rum-rue@ietf.org, rum-chairs@ietf.org, rum@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
To: Roman Danyliw <rdd@cert.org>
References: <163960605716.22037.6925953082119136922@ietfa.amsl.com> <64AD6B8B-9D35-4269-AD74-FD8755F21F2D@brianrosen.net>
X-Mailer: Apple Mail (2.3693.20.0.1.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/UL50la3GD-Zxz8wVDPGSSbz1I0Q>
Subject: Re: [Rum] Roman Danyliw's Discuss on draft-ietf-rum-rue-09: (with DISCUSS and COMMENT)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jan 2022 14:53:56 -0000

--Apple-Mail=_4069DAD9-E536-46D0-BAFB-9ED0A62A2585
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Roman

Does the -10 version I submitted address your issues?

Brian


> On Dec 23, 2021, at 4:56 PM, Brian Rosen <br@brianrosen.net> wrote:
>=20
> Thank you for your comments.  Responses inline
>=20
>> On Dec 15, 2021, at 5:07 PM, Roman Danyliw via Datatracker =
<noreply@ietf.org> wrote:
>>=20
>> Roman Danyliw has entered the following ballot position for
>> draft-ietf-rum-rue-09: 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/blog/handling-iesg-ballot-positions/
>> for more information about how to handle DISCUSS and COMMENT =
positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-rum-rue/
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> DISCUSS:
>> =
----------------------------------------------------------------------
>>=20
>> ** Is there a reason that credential re-use is being suggested as a =
fall back.=20
>> It seems risky to reuse the credentials across services.
> This is really how sip services commonly work and I=E2=80=99m =
reluctant to disallow what is widely implemented
>=20
>> This fall-back also
>> appears to contradict the guidance in Section 5.1. which says =E2=80=9C=
This
>> username/password combination SHOULD NOT be the same as that used for =
other
>> purposes, such as retrieving the RUE configuration=E2=80=9D.
> I will change this to add "except as expressly described below=E2=80=9D
> The configuration service is new, and thus we can say don=E2=80=99t =
reuse credentials for that.
>=20
>=20
>> See:
>>=20
>> -- Section 7.1.  Per access to the CardDAV server, =E2=80=9C[i]f no =
matching
>> credentials are configured, the RUE MUST use the SIP credentials from =
the
>> configuration.=E2=80=9D
>>=20
>> -- Section 9.2.2.  sip-password says =E2=80=9CIf it was never =
supplied, the password
>> used to authenticate to the configuration service is used for SIP, =
STUN and
>> TURN.=E2=80=9D
>>=20
>> -- Section 9.2.2.  carddav field says that =E2=80=9CIf username or =
password are not
>> supplied, the main account credentials are used. =E2=80=9C
>>=20
>> ** Is there a reason that a minimum transport requirements of using =
HTTPS is
>> not defined for accessing the SIP-supporting elements of this =
architecture.
> I=E2=80=99m confused by this.  HTTPS and SIP are mutually exclusive.  =
Did you mean TLS instead of HTTPS?
> But you said =E2=80=9Cminimum transport=E2=80=9D and not =
=E2=80=9Csecurity=E2=80=9D so I=E2=80=99m even more confused.  Sorry.
>=20
> We specify RFC7525 and 8446 in General Requirements for TLS.
>=20
>>=20
>> -- Section 7.1.  Access to the CardDAV service?  Does the guidance in =
Section
>> 7.2 (The RUE stores/retrieves the contact list (address book) by =
issuing an
>> HTTPS POST or GET request.) imply that?
> There are two services: a contact list import and a CardDAV service, =
which is a contact sync.  Both are subject to the TLS requirements
>>=20
>> -- Section 9.  Using the overall API? Does the guidance in Section =
9.2 (A RUE
>> device may retrieve a provider configuration the using a simple HTTPs =
web
>> service) imply that?
> Again it=E2=80=99s an HTTPS service, so subject to the General =
Requirements TLS specs
>>=20
>> -- Section 9.2.1.  For the URI configuration options noted in this =
section
>> (e.g., the uri in signup)?
> Same
>>=20
>> ** Section 11.  There are more than 10 20 normative SIP protocol =
references in
>> this document.  Which of their security considerations apply?
> All of them.  That=E2=80=99s pretty normal sip stuff.
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> Thank you to Russ Mundy for the SECDIR review.
>>=20
>> ** Section 2.  Thanks for defining all of this terminology up front.  =
As many
>> of these are components in the architecture, I would have benefit =
from a
>> diagram early in the document showing how these components integrate. =
**
> I am diagram challenged, but I will see what I can do.
>=20
>> Section 5.1.  The paragraph starting with =E2=80=9CThe registrar MAY =
authenticate using
>> SIP digest authentication =E2=80=A6=E2=80=9D, should likely say that =
the technique for
>> provisioning the credentials is out of scope for this profile.
> Actually, they come in the configuration service.
>=20
>>=20
>> ** Section 8.  Typo. s/mechansism/mechanism/
> Fixed
>=20
>> ** Section 9.1
>> IANA has established a registry that contains
>>  a two letter country code and an entry point string.
>>=20
>> Recommend adding a forward reference to Section 10.1.
> Added
>=20
>>=20
>> ** Section 9.1.
>>  For example,
>>  if the entryPoint is "example.com <http://example.com/>", the =
provider list would be
>>  obtained from https://example.com/rum/V1/Providers =
<https://example.com/rum/V1/Providers>.
>>=20
>> This example doesn=E2=80=99t match the syntax of Section 9.3.  =
=E2=80=9CV1=E2=80=9D here and =E2=80=9Cv1=E2=80=9D in
>> Section 9.3.
> Fixed
>>=20
>> ** Section 9.2.  It would be helpful in this narrative text for the =
input
>> values names to match the actual field names used in the API in =
Section 9.3.=20
>> Specifically, =E2=80=9CAPI Key=E2=80=9D is =E2=80=9CapiKey=E2=80=9D, =
and =E2=80=9Cinstance identifier=E2=80=9D is =E2=80=9CinstanceId=E2=80=9D
> Fixed.=20
>=20
>>=20
>> ** Section 9.2.1.  Per the language value in the signup configuration =
option,
>> please provide a reference to the IAN language subtag registry
>> =
(https://www.iana.org/assignments/language-subtag-registry/language-subtag=
-registry =
<https://www.iana.org/assignments/language-subtag-registry/language-subtag=
-registry>).
> I put it inline as a link.  Should it be an actual reference?
>=20
>>=20
>> ** Section 9.2.2.  sendLocationWithRegistation is listed as a =
stand-alone field
>> here, but in Section 9.3, it is shown to be part of the carddav =
object.  Which
>> is correct?
> Ho, that=E2=80=99s an actual error.  It should be a separate field.  =
Fixed
>>=20
>> ** Section 9.2.3.  Figure 4.  This example is not conformance to the =
previously
>> described syntax.  All of the values of the =E2=80=9Curi=E2=80=9D =
fields should be a URI, but
>> all of them are missing a scheme.
> Fixed
>=20
>>=20
>> ** Section 9.3.  [OpenAPI] needs to be a normative reference as its =
syntax is
>> needed to understand this section.
> Reluctantly fixed.  We have too many normative references :)


--Apple-Mail=_4069DAD9-E536-46D0-BAFB-9ED0A62A2585
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"">Roman<div class=3D""><br class=3D""></div><div class=3D"">Does =
the -10 version I submitted address your issues?</div><div class=3D""><br =
class=3D""></div><div class=3D"">Brian</div><div class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Dec 23, 2021, at 4:56 PM, Brian Rosen &lt;<a =
href=3D"mailto:br@brianrosen.net" class=3D"">br@brianrosen.net</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" 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"">Thank you for your comments. &nbsp;Responses inline</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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">On =
Dec 15, 2021, at 5:07 PM, Roman Danyliw via Datatracker &lt;<a =
href=3D"mailto:noreply@ietf.org" class=3D"">noreply@ietf.org</a>&gt; =
wrote:<br class=3D""><br class=3D"">Roman Danyliw has entered the =
following ballot position for<br class=3D"">draft-ietf-rum-rue-09: =
Discuss<br class=3D""><br class=3D"">When responding, please keep the =
subject line intact and reply to all<br class=3D"">email addresses =
included in the To and CC lines. (Feel free to cut this<br =
class=3D"">introductory paragraph, however.)<br class=3D""><br =
class=3D""><br class=3D"">Please refer to <a =
href=3D"https://www.ietf.org/blog/handling-iesg-ballot-positions/" =
class=3D"">https://www.ietf.org/blog/handling-iesg-ballot-positions/</a><b=
r class=3D"">for more information about how to handle DISCUSS and =
COMMENT positions.<br class=3D""><br class=3D""><br class=3D"">The =
document, along with other ballot positions, can be found here:<br =
class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-rum-rue/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-rum-rue/</a><br =
class=3D""><br class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">DISCUSS:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">** Is there a reason that =
credential re-use is being suggested as a fall back.<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">It seems =
risky to reuse the credentials across services.<br =
class=3D""></blockquote><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"">This is really how sip services commonly work and I=E2=80=99m =
reluctant to disallow what is widely implemented</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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">This =
fall-back also<br class=3D"">appears to contradict the guidance in =
Section 5.1. which says =E2=80=9CThis<br class=3D"">username/password =
combination SHOULD NOT be the same as that used for other<br =
class=3D"">purposes, such as retrieving the RUE configuration=E2=80=9D.<br=
 class=3D""></blockquote><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"">I will change this to add "except as expressly described =
below=E2=80=9D</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 configuration service is new, and thus we can say don=E2=80=
=99t reuse credentials for that.</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""><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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">See:<br class=3D""><br class=3D"">-- =
Section 7.1. &nbsp;Per access to the CardDAV server, =E2=80=9C[i]f no =
matching<br class=3D"">credentials are configured, the RUE MUST use the =
SIP credentials from the<br class=3D"">configuration.=E2=80=9D<br =
class=3D""><br class=3D"">-- Section 9.2.2. &nbsp;sip-password says =
=E2=80=9CIf it was never supplied, the password<br class=3D"">used to =
authenticate to the configuration service is used for SIP, STUN and<br =
class=3D"">TURN.=E2=80=9D<br class=3D""><br class=3D"">-- Section 9.2.2. =
&nbsp;carddav field says that =E2=80=9CIf username or password are =
not<br class=3D"">supplied, the main account credentials are used. =
=E2=80=9C<br class=3D""><br class=3D"">** Is there a reason that a =
minimum transport requirements of using HTTPS is<br class=3D"">not =
defined for accessing the SIP-supporting elements of this =
architecture.<br class=3D""></blockquote><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"">I=E2=80=99m confused by this. &nbsp;HTTPS and SIP are =
mutually exclusive. &nbsp;Did you mean TLS instead of HTTPS?</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"">But you said =E2=80=9Cminimum =
transport=E2=80=9D and not =E2=80=9Csecurity=E2=80=9D so I=E2=80=99m =
even more confused. &nbsp;Sorry.</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""><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"">We specify RFC7525 and 8446 in General Requirements for =
TLS.</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""><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""><blockquote type=3D"cite" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">-- Section 7.1. &nbsp;Access to the CardDAV service? =
&nbsp;Does the guidance in Section<br class=3D"">7.2 (The RUE =
stores/retrieves the contact list (address book) by issuing an<br =
class=3D"">HTTPS POST or GET request.) imply that?<br =
class=3D""></blockquote><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"">There are two services: a contact list import and a CardDAV =
service, which is a contact sync. &nbsp;Both are subject to the TLS =
requirements</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""><blockquote type=3D"cite" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">-- Section 9. &nbsp;Using the overall API? Does the guidance =
in Section 9.2 (A RUE<br class=3D"">device may retrieve a provider =
configuration the using a simple HTTPs web<br class=3D"">service) imply =
that?<br class=3D""></blockquote><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"">Again it=E2=80=99s an HTTPS service, so subject to the =
General Requirements TLS specs</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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D"">-- Section 9.2.1. =
&nbsp;For the URI configuration options noted in this section<br =
class=3D"">(e.g., the uri in signup)?<br class=3D""></blockquote><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"">Same</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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">** Section 11. &nbsp;There are more than 10 20 normative SIP =
protocol references in<br class=3D"">this document. &nbsp;Which of their =
security considerations apply?<br class=3D""></blockquote><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"">All of them. &nbsp;That=E2=80=99s =
pretty normal sip stuff.</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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">Thank you to Russ Mundy for the =
SECDIR review.<br class=3D""><br class=3D"">** Section 2. &nbsp;Thanks =
for defining all of this terminology up front. &nbsp;As many<br =
class=3D"">of these are components in the architecture, I would have =
benefit from a<br class=3D"">diagram early in the document showing how =
these components integrate. **<br class=3D""></blockquote><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"">I am diagram challenged, but I =
will see what I can do.</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">Section 5.1. &nbsp;The paragraph =
starting with =E2=80=9CThe registrar MAY authenticate using<br =
class=3D"">SIP digest authentication =E2=80=A6=E2=80=9D, should likely =
say that the technique for<br class=3D"">provisioning the credentials is =
out of scope for this profile.<br class=3D""></blockquote><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"">Actually, they come in the =
configuration service.</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D"">** Section 8. =
&nbsp;Typo. s/mechansism/mechanism/<br class=3D""></blockquote><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"">Fixed</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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">** =
Section 9.1<br class=3D"">IANA has established a registry that =
contains<br class=3D"">&nbsp;a two letter country code and an entry =
point string.<br class=3D""><br class=3D"">Recommend adding a forward =
reference to Section 10.1.<br class=3D""></blockquote><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"">Added</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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">** Section 9.1.<br class=3D"">&nbsp;For example,<br =
class=3D"">&nbsp;if the entryPoint is "<a href=3D"http://example.com/" =
class=3D"">example.com</a>", the provider list would be<br =
class=3D"">&nbsp;obtained from<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://example.com/rum/V1/Providers" =
class=3D"">https://example.com/rum/V1/Providers</a>.<br class=3D""><br =
class=3D"">This example doesn=E2=80=99t match the syntax of Section 9.3. =
&nbsp;=E2=80=9CV1=E2=80=9D here and =E2=80=9Cv1=E2=80=9D in<br =
class=3D"">Section 9.3.<br class=3D""></blockquote><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"">Fixed</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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">** Section 9.2. &nbsp;It would be helpful in this narrative =
text for the input<br class=3D"">values names to match the actual field =
names used in the API in Section 9.3.<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">Specifically, =
=E2=80=9CAPI Key=E2=80=9D is =E2=80=9CapiKey=E2=80=9D, and =E2=80=9Cinstan=
ce identifier=E2=80=9D is =E2=80=9CinstanceId=E2=80=9D<br =
class=3D""></blockquote><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"">Fixed.<span =
class=3D"Apple-converted-space">&nbsp;</span></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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">** Section 9.2.1. &nbsp;Per the language value in the signup =
configuration option,<br class=3D"">please provide a reference to the =
IAN language subtag registry<br class=3D"">(<a =
href=3D"https://www.iana.org/assignments/language-subtag-registry/language=
-subtag-registry" =
class=3D"">https://www.iana.org/assignments/language-subtag-registry/langu=
age-subtag-registry</a>).<br class=3D""></blockquote><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"">I put it inline as a link. =
&nbsp;Should it be an actual reference?</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D"">** Section 9.2.2. =
&nbsp;sendLocationWithRegistation is listed as a stand-alone field<br =
class=3D"">here, but in Section 9.3, it is shown to be part of the =
carddav object. &nbsp;Which<br class=3D"">is correct?<br =
class=3D""></blockquote><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"">Ho, that=E2=80=99s an actual error. &nbsp;It should be a =
separate field. &nbsp;Fixed</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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D"">** Section 9.2.3. =
&nbsp;Figure 4. &nbsp;This example is not conformance to the =
previously<br class=3D"">described syntax. &nbsp;All of the values of =
the =E2=80=9Curi=E2=80=9D fields should be a URI, but<br class=3D"">all =
of them are missing a scheme.<br class=3D""></blockquote><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"">Fixed</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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">** Section 9.3. &nbsp;[OpenAPI] needs to be a normative =
reference as its syntax is<br class=3D"">needed to understand this =
section.<br class=3D""></blockquote><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"">Reluctantly fixed. &nbsp;We have too many normative =
references :)</span></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_4069DAD9-E536-46D0-BAFB-9ED0A62A2585--


From nobody Thu Jan 20 06:54:43 2022
Return-Path: <br@brianrosen.net>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD5C3A14C7 for <rum@ietfa.amsl.com>; Thu, 20 Jan 2022 06:54:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level: 
X-Spam-Status: No, score=-1.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20210112.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OlqlHtTggC-5 for <rum@ietfa.amsl.com>; Thu, 20 Jan 2022 06:54:37 -0800 (PST)
Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF4DE3A14C6 for <rum@ietf.org>; Thu, 20 Jan 2022 06:54:36 -0800 (PST)
Received: by mail-il1-x12e.google.com with SMTP id r15so5173955ilj.7 for <rum@ietf.org>; Thu, 20 Jan 2022 06:54:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=D0d/bzscEBaWLVaL8QTA3cNTdZYFawsYGfwpVwiGWg4=; b=bION7Ou1gr/ARaEx+YJ8W9YZvVn2oTSrjHUHzas4mHiGdUYMPfm+ikiDyYSX0JR5lJ CRVc8c+KzrNcs9/br+2R8G4309kUtLNTjACoboe+wiHB4XJEgVUQ4zXmJyYLWmlhjTi4 a/lg0YyvuL8QoN8+BPMsZKcRxfUTbZiTfcVb30f22ibpIb+WUswlGWaX6KcKqkqrdvEA Qa5ztD4+9AcDM7OtWwUYiLQ3dh72gJuM3h9RN+GMvTIWA1D95LepJ4+VfcXuVnR/8Cxr xCEo5uCn/gkdS++704AZcovb24apnmmfj+o6RhYx/jGTl9x8YYaup6ipnqTgan/M/9MC MXaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=D0d/bzscEBaWLVaL8QTA3cNTdZYFawsYGfwpVwiGWg4=; b=Djq4K5OYQaXYYYJYD6Pvxr05PxYl2C/xaA3LLO+f99qmAQI35uaaWLeT+8PJnJZyCf w0gvEYi/hEs9Hh0yonwDfDqxTtiavfTD4HrjPxKAsnjWKQXxCzRGpNq50sFnZFr+nbgb piP3541n+QzIGJGU+RCjwV9JSpy3su5uRSHupLcS4VirEU8c6HkqLWpNUsA+f6e41fVS hoob7/JjDlX2o3IVedU4I/RK0jq7JvKnXywVZgnMR8DCvdaXU1dfZ5mBFCp22vnl4i0U 31XyUTeGdiMzsX8yx4NNnBJ6OsAoLXr0q1i/iJ3S2B5wn44WCd4hRc+nZabCC4DraNNP yqfg==
X-Gm-Message-State: AOAM533lmHTpHefLAEzFAVs35S5ijYr2jUtpYCBA33qyln184ts60XkG iugnr7Y5aNlqRS/ldwuZPPV3GA==
X-Google-Smtp-Source: ABdhPJzzDeXgssUE93jfQyqAwTCWe+blL76GsGsbldElGevFmIp3TPKEWNa1hx9eeIzFCzcSK1WWwA==
X-Received: by 2002:a05:6e02:4c3:: with SMTP id f3mr5523089ils.157.1642690475159;  Thu, 20 Jan 2022 06:54:35 -0800 (PST)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id x6sm1485338ill.78.2022.01.20.06.54.33 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jan 2022 06:54:34 -0800 (PST)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <661930ED-EDE1-464C-9664-45F2FE1355A7@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6AA21666-5E2C-46BE-B080-764EF1B39675"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\))
Date: Thu, 20 Jan 2022 09:54:33 -0500
In-Reply-To: <3A2D8BEA-23D0-4EE8-8EFE-CCE6B3EB0AFD@brianrosen.net>
Cc: The IESG <iesg@ietf.org>, draft-ietf-rum-rue@ietf.org, rum-chairs@ietf.org, rum@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
To: Robert Wilton <rwilton@cisco.com>
References: <163957183657.10054.2789790212865898062@ietfa.amsl.com> <3A2D8BEA-23D0-4EE8-8EFE-CCE6B3EB0AFD@brianrosen.net>
X-Mailer: Apple Mail (2.3693.20.0.1.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/rFprY5nZUIxB6LKcFaQDe9Rj1dk>
Subject: Re: [Rum] Robert Wilton's Discuss on draft-ietf-rum-rue-09: (with DISCUSS and COMMENT)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jan 2022 14:54:41 -0000

--Apple-Mail=_6AA21666-5E2C-46BE-B080-764EF1B39675
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Rob

I submitted a -10 which I hope is satisfactory to you.

Brian


> On Dec 23, 2021, at 4:16 PM, Brian Rosen <br@brianrosen.net> wrote:
>=20
> Thank you for your comments.  Please see inline
>=20
>> On Dec 15, 2021, at 7:37 AM, Robert Wilton via Datatracker =
<noreply@ietf.org> wrote:
>>=20
>> Robert Wilton has entered the following ballot position for
>> draft-ietf-rum-rue-09: 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/blog/handling-iesg-ballot-positions/
>> for more information about how to handle DISCUSS and COMMENT =
positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-rum-rue/
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> DISCUSS:
>> =
----------------------------------------------------------------------
>>=20
>> There are a couple of points related to versioning that I would like =
to see
>> clarified, but I hope that it should be fairly easy to do so.
>>=20
>> 1.
>>  This means an implementation of a
>>  specific major version and minor version is backwards compatible =
with
>>  all minor versions of the major version.
>>=20
>> Is it actually compatible with all other minor versions, or only =
other minor
>> versions with a greater minor version number.  E.g., could an =
implementation be
>> coded to use/expect a object added in a minor version but that is not =
present
>> in preceding minor versions?
> All other minor versions. =20
>=20
> It has to be truly optional.  You can do things like add two =
parameters, a and b, and say if a is provided b must be provided, but it =
has to work if neither are there, and even if an implementation provided =
a but not b, an earlier version would ignore a.
>=20
>>=20
>> 2.
>>  The configuration API also provides the same version mechanism as
>>  specified above in Section 9.1.  The version of the configuration
>>  service MAY be different than the version of the provider list
>>  service.
>>=20
>> It wasn't obvious to me, that for a given provider, how this is =
communicated.=20
>> I'm not that familiar with OpenAPI, but looks like the /Versions path =
is a top
>> level API path, and the data that is contains seems to just be =
version numbers.
>> Hence, how would a client know which versions apply to provider list =
service
>> and/or which versions apply to the provide configuration service.
> =E2=80=98
> First of all, the Provider list is not available at alll providers.  =
It=E2=80=99s only available at a service that is one per country.  So =
one entity normally doesn=E2=80=99t supply both the Provider and the =
ProviderConfig entry points.
> To be really pedantic, I suppose that it=E2=80=99s actually possible =
for it to be one entity, and then that statement that there are separate =
versions wouldn=E2=80=99t apply.  So I guess I will change the text to:
> Unless the per-country provider list service is operated by a provider =
at the same base URI as that provider=E2=80=99s configuration service, =
the version of the configuration service MAY be different from the =
version of the provider list service.
>=20
>>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> Hi Brian,
>>=20
>> Thank you for working on this.  This technology is quite a long way =
outside of
>> my expertise, and hence my review is primarily focused on the =
Configuration
>> section (section 9).
>>=20
>> Nit: when used with the following interface =3D>  when used with the =
following
>> OpenAPI interface
> Fixed
>>=20
>> Nit: with a corresponding a entry point -> with a corresponding entry =
point
> Fixed
>>=20
>>  Minor version definitions
>>  SHALL only add objects, non-required members of existing objects, =
and
>>  non-mandatory-to use functions and SHALL NOT delete any objects,
>>  members of objects or functions.
>>=20
>> Would "delete or change" be more correct than just "delete" here?
> Added =E2=80=9Cor change"
>>=20
>> Somewhat related to the discuss comment, but it wasn't clear to me =
why the
>> versioning is described as part of the "Rue Provider Selection" =
section and I
>> think that the document would arguably be clearer if the versioning =
moved to
>> its own separate 9.X section, making it clear that the versioning =
applies to
>> the entire API?
> I will do that
>=20
>>=20
>> Nit: The method the API Key is obtained is not specified in this =
document. =3D>
>> Perhaps "The method used to obtain the API key =E2=80=A6"
> Fixed
>>=20
>>  The provider MAY refuse to provide service to an implementation
>>  presenting an API Key it does not recognize.
>>=20
>> Why is this not a MUST?
> Well, suppose a provider doesn=E2=80=99t implement an API key, but the =
client supplies one.  That would not be recognized by the provider, but =
it doesn=E2=80=99t care, so it provides service.
>=20
>>=20
>> Is the "instance-identifier" arbitrarily chosen by the client?  =
Otherwise, it
>> wasn't clear to me how a client would discover or know what
>> "instance-identifier" to use.  It might be helpful if the text =
clarified this,
> I added that text
>=20
>> and possibly even the parameter name could be changed to make it more =
obvious
>> that it is a client provided value?
> =E2=80=9CclientInstanceId=E2=80=9D wouldn=E2=80=99t help.  It would =
have to be =E2=80=9CclientProvidedInstanceId=E2=80=9D.  That seems to be =
a bit much as a parameter name.  I=E2=80=99ll do it if you think it=E2=80=99=
s important, but I=E2=80=99m inclined to just leave the explanatory text =
specifying that it=E2=80=99s client provided.
>>=20
>> Regards,
>> Rob


--Apple-Mail=_6AA21666-5E2C-46BE-B080-764EF1B39675
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"">Rob<div class=3D""><br class=3D""></div><div class=3D"">I =
submitted a -10 which I hope is satisfactory to you.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Brian</div><div =
class=3D""><br class=3D""><div class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Dec 23, 2021, at 4:16 PM, =
Brian Rosen &lt;<a href=3D"mailto:br@brianrosen.net" =
class=3D"">br@brianrosen.net</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" 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"">Thank you for your comments. &nbsp;Please see =
inline</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""><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""><blockquote type=3D"cite" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">On =
Dec 15, 2021, at 7:37 AM, Robert Wilton via Datatracker &lt;<a =
href=3D"mailto:noreply@ietf.org" class=3D"">noreply@ietf.org</a>&gt; =
wrote:<br class=3D""><br class=3D"">Robert Wilton has entered the =
following ballot position for<br class=3D"">draft-ietf-rum-rue-09: =
Discuss<br class=3D""><br class=3D"">When responding, please keep the =
subject line intact and reply to all<br class=3D"">email addresses =
included in the To and CC lines. (Feel free to cut this<br =
class=3D"">introductory paragraph, however.)<br class=3D""><br =
class=3D""><br class=3D"">Please refer to <a =
href=3D"https://www.ietf.org/blog/handling-iesg-ballot-positions/" =
class=3D"">https://www.ietf.org/blog/handling-iesg-ballot-positions/</a><b=
r class=3D"">for more information about how to handle DISCUSS and =
COMMENT positions.<br class=3D""><br class=3D""><br class=3D"">The =
document, along with other ballot positions, can be found here:<br =
class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-rum-rue/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-rum-rue/</a><br =
class=3D""><br class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">DISCUSS:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">There are a couple of points =
related to versioning that I would like to see<br class=3D"">clarified, =
but I hope that it should be fairly easy to do so.<br class=3D""><br =
class=3D"">1.<br class=3D"">&nbsp;This means an implementation of a<br =
class=3D"">&nbsp;specific major version and minor version is backwards =
compatible with<br class=3D"">&nbsp;all minor versions of the major =
version.<br class=3D""><br class=3D"">Is it actually compatible with all =
other minor versions, or only other minor<br class=3D"">versions with a =
greater minor version number. &nbsp;E.g., could an implementation be<br =
class=3D"">coded to use/expect a object added in a minor version but =
that is not present<br class=3D"">in preceding minor versions?<br =
class=3D""></blockquote><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"">All other minor versions. &nbsp;</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""><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"">It has to be truly optional. =
&nbsp;You can do things like add two parameters, a and b, and say if a =
is provided b must be provided, but it has to work if neither are there, =
and even if an implementation provided a but not b, an earlier version =
would ignore a.</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D"">2.<br =
class=3D"">&nbsp;The configuration API also provides the same version =
mechanism as<br class=3D"">&nbsp;specified above in Section 9.1. =
&nbsp;The version of the configuration<br class=3D"">&nbsp;service MAY =
be different than the version of the provider list<br =
class=3D"">&nbsp;service.<br class=3D""><br class=3D"">It wasn't obvious =
to me, that for a given provider, how this is communicated.<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">I'm not that =
familiar with OpenAPI, but looks like the /Versions path is a top<br =
class=3D"">level API path, and the data that is contains seems to just =
be version numbers.<br class=3D"">Hence, how would a client know which =
versions apply to provider list service<br class=3D"">and/or which =
versions apply to the provide configuration service.<br =
class=3D""></blockquote><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"">=E2=80=98</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"">First of all, the Provider list is not available at alll =
providers. &nbsp;It=E2=80=99s only available at a service that is one =
per country. &nbsp;So one entity normally doesn=E2=80=99t supply both =
the Provider and the ProviderConfig entry points.</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"">To be really pedantic, I suppose =
that it=E2=80=99s actually possible for it to be one entity, and then =
that statement that there are separate versions wouldn=E2=80=99t apply. =
&nbsp;So I guess I will change the text to:</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"">Unless the per-country provider =
list service is operated by a provider at the same base URI as that =
provider=E2=80=99s configuration service, the version of the =
configuration service MAY be different from the version of the provider =
list service.</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""><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""><blockquote type=3D"cite" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">Hi Brian,<br class=3D""><br =
class=3D"">Thank you for working on this. &nbsp;This technology is quite =
a long way outside of<br class=3D"">my expertise, and hence my review is =
primarily focused on the Configuration<br class=3D"">section (section =
9).<br class=3D""><br class=3D"">Nit: when used with the following =
interface =3D&gt; &nbsp;when used with the following<br class=3D"">OpenAPI=
 interface<br class=3D""></blockquote><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"">Fixed</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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D"">Nit: with a =
corresponding a entry point -&gt; with a corresponding entry point<br =
class=3D""></blockquote><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"">Fixed</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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D"">&nbsp;Minor version =
definitions<br class=3D"">&nbsp;SHALL only add objects, non-required =
members of existing objects, and<br class=3D"">&nbsp;non-mandatory-to =
use functions and SHALL NOT delete any objects,<br =
class=3D"">&nbsp;members of objects or functions.<br class=3D""><br =
class=3D"">Would "delete or change" be more correct than just "delete" =
here?<br class=3D""></blockquote><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"">Added =E2=80=9Cor change"</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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D"">Somewhat related to =
the discuss comment, but it wasn't clear to me why the<br =
class=3D"">versioning is described as part of the "Rue Provider =
Selection" section and I<br class=3D"">think that the document would =
arguably be clearer if the versioning moved to<br class=3D"">its own =
separate 9.X section, making it clear that the versioning applies to<br =
class=3D"">the entire API?<br class=3D""></blockquote><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"">I will do that</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""><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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">Nit: The method the API Key is obtained is not specified in =
this document. =3D&gt;<br class=3D"">Perhaps "The method used to obtain =
the API key =E2=80=A6"<br class=3D""></blockquote><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"">Fixed</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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">&nbsp;The provider MAY refuse to provide service to an =
implementation<br class=3D"">&nbsp;presenting an API Key it does not =
recognize.<br class=3D""><br class=3D"">Why is this not a MUST?<br =
class=3D""></blockquote><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"">Well, suppose a provider doesn=E2=80=99t implement an API =
key, but the client supplies one. &nbsp;That would not be recognized by =
the provider, but it doesn=E2=80=99t care, so it provides =
service.</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""><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""><blockquote type=3D"cite" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">Is the "instance-identifier" arbitrarily chosen by the =
client? &nbsp;Otherwise, it<br class=3D"">wasn't clear to me how a =
client would discover or know what<br class=3D"">"instance-identifier" =
to use. &nbsp;It might be helpful if the text clarified this,<br =
class=3D""></blockquote><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"">I added that text</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""><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""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">and possibly even the parameter name =
could be changed to make it more obvious<br class=3D"">that it is a =
client provided value?<br class=3D""></blockquote><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"">=E2=80=9CclientInstanceId=E2=80=9D=
 wouldn=E2=80=99t help. &nbsp;It would have to be =
=E2=80=9CclientProvidedInstanceId=E2=80=9D. &nbsp;That seems to be a bit =
much as a parameter name. &nbsp;I=E2=80=99ll do it if you think it=E2=80=99=
s important, but I=E2=80=99m inclined to just leave the explanatory text =
specifying that it=E2=80=99s client provided.</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""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"">Regards,<br =
class=3D"">Rob</blockquote></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_6AA21666-5E2C-46BE-B080-764EF1B39675--


From nobody Thu Jan 20 06:58:07 2022
Return-Path: <rwilton@cisco.com>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09B043A14F0; Thu, 20 Jan 2022 06:58:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.596
X-Spam-Level: 
X-Spam-Status: No, score=-9.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=c4eqvNCl; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Tp9FOZPU
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 UFfxFiJWDeUw; Thu, 20 Jan 2022 06:57:59 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 583A63A14EA; Thu, 20 Jan 2022 06:57:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9218; q=dns/txt; s=iport; t=1642690679; x=1643900279; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=OxJHClOue2tKARMoDy3xlD6fIMhola4gL/IGsTI6yV4=; b=c4eqvNCl5EPXLu7S139uTk3hlSUzNzBwTivXZE1JPds1ZM58Cs1awYxP MeQg2f6eZiwPDIcokLiCHNo1KkdCYpOLSdxnF4ET3NJsV+ib92NCMyx8d Ei1sNoGw/uESvCwJ9KK17zH0jn6ue5OlwGCJncvARkxCqqfzZgoE8dWVK g=;
X-IPAS-Result: =?us-ascii?q?A0ALAACld+lhl5ldJa1aHAEBAQEBAQcBARIBAQQEAQFAg?= =?us-ascii?q?UYHAQELAYFRVn5aNzGESINHA4RZYIUOgwIDmx6BLhSBEQNUCwEBAQ0BATUMB?= =?us-ascii?q?AEBhQUCF4M+AiU0CQ4BAgQBAQEBAwIDAQEBAQUBAQUBAQECAQYEFAEBAQEBA?= =?us-ascii?q?QEBJAYMBQ43hWgNhkIBAQEBAxIRBA0MAQEpDgELBAIBCA4DBAEBAQICJgICA?= =?us-ascii?q?jAVCAgCBA4FCBqCYgGCZQMuAQ6hMwGBOgKKH3p/MoEBO4FNAQEGBASBSkGDA?= =?us-ascii?q?hiCNwMGgRAqAYMNhB6HByccgUlEgRVDgmc+gmMCA4EoARIBI4MWN4IukVYBB?= =?us-ascii?q?htCBCIZGAR7BhNCKAIPZJF8BAeDAEaKBY0wklwKg0WKfI5hhhIVg3GMD5d0k?= =?us-ascii?q?3OCUY0KlCYEhQQCBAIEBQIOAQEGgWE5a3BwFTuCaVEZD44gGR6DOoUUhUp0O?= =?us-ascii?q?AIGAQoBAQMJkDoBAQ?=
IronPort-PHdr: A9a23:7KEIvh2NZOr60uM/smDPr1BlVkEcU/3cMg0U788hjLRDOuSm8o/5N UPSrfNqkBfSXIrd5v4F7oies63pVWEap5rUtncEfc9AUhYfgpAQmAotSMeOFUz8KqvsaCo3V MRPXVNo5Te1K09QTc3/fFbV5Ha16G16Jw==
IronPort-Data: A9a23:a38N26r3Z6UMrG1lC2gdSd1VucdeBmLAZRIvgKrLsJaIsI4StFCzt garIBnQb6rbYmb8etx3at/noRsF7cPQnIBhSVBk+SE1FHsQoOPIVI+TRqvS04x+DSFioGZPt Zh2hgzodZhsJpPkS5TE3oHJ9RGQ74nQLlbHILOCanAZqTNMEn9700o6wbZh2OaEvPDga++zk YKqyyHgEAfNNw5cagr4PIra9XuDFNyr0N8plgRWicJj5TcypFFJZH4rHpxdGlOjKmVi8kFWc M6YpF2x1juxEx7AkbpJmJ6jGqEBaua60QRjFhO6VoD66iWuqBDe3Y4gF9kZaGF+ugm2nslh8 PNilpaASg4Aa/ikdOQ1C3G0EglkNqFAvbTAO3X664qYzlbNdD3nxPAG4EMeZNJDvL0oRzAVs 6VFc1jhbTjb7w6y6KikS+1wgcILJ8jwN4RZsXZlpd3cJaZ8EcifGPiTvre02h8Ntp1RRvLfd fYdaGYwYSbvZRJiFHwIXcdWcOCA3ymjLGIwREiujbI08nrS0gVt+LHpLd+Tf92WA8hZgy6wv H/D12X0Hh9cM8aQoRKf73fpje/GnDngcIMfCLP+8eRl6HWf3GUdFFgXWEe15OOkjwukRt93K kEI9Gwpt6da3E2mVdbVXhCkrjiDpBF0c9BKO+cg6QiL0K3P7gDfAGUYJgOtc/Q8v8MwADctz FLMxZXiBCdkt/ueTnf1GqqoQS2aIgs2KG4kTB44cgoc8+HFj6I5vhHGZ4M2eEKqteHdFTb1y jGMiSExgbQPkMIGv5lXG3ia31pAQbCUFWYIChXrsnGNtVkoONH/D2C8wR2Ks6kYdtnxokyp5 SBcw6CjAPYy4YZhfcBnaN8MF7Gg/fqeNzu0bbVHQMR5p23FF5JOgeltDNxWPkxlNIMPfiXkJ RWVsgJK75gVN3yvBUOWX25TI5l3pUQDPY24PhwxUjaoSsMpHONg1Ho1DXN8J0i3zCARfVgXY P93i/qEA3cAErhAxzGrXeob2rJD7nlgmTmNHM+jl0T3iuP2iJuppVEtbQTmggcRsf3snekp2 4032zaikk8GC7SuPkE7D6ZKcghWRZTEOXwGg5UHKrHcSuaXMGogEPTWiagwYJBomr89qws71 i/VZ6Os83Km3SevAVzTMhhLMeqzNb4i/ClTFXF9Yj6VN40LPN/HAFE3LMNnI9HKNYVLkJZJc hXyU5zQW6sUEmWepW11gFuUhNUKSSlHTDmmZ0KNCAXTtbY6L+AV0rcIpjfSyRQ=
IronPort-HdrOrdr: A9a23:ycV6NaFjreErdEChpLqFSpHXdLJyesId70hD6qkvc31om52j+f xGws516fatskdvZJkh8erwX5VoMkmsi6KdhrNhfItKPTOW9ldASbsD0WKM+UyaJ8STzJ856U 4kSdkDNDSSNyk7sS+Z2njDLz9I+rDum8rE6Za8vhVQpENRGtxdBmxCe2Cm+zhNNXF77O0CZe OhD6R81l6dUEVSSv7+KmgOXuDFqdGOvonhewQ6Cxku7xTLpS+06ZbheiLonSs2Yndq+/MP4G LFmwv26uGIqPeg0CLR0GfV8tB/hMbh8N1eH8aB4/JlaAkEyzzYIbiJaYfy+wzdk9vfrmrCV+ O8+ivICv4Dr085uFvF+ScFlTOQiwrGoEWSuGNwyUGT0fARAghKUfaoQeliA0fkA41KhqAg7E sD5RPri7NHSRzHhyjz/N7OSlVjkVe1u2MrlaoJg2VYSpZ2Us4dkWUzxjIfLH47JlOx1GnnKp gYMOjMoPJNNV+KZXHQuWdihNSqQ3QoBx+DBkwPoNac3TRalG1wixJw/r1Rol4QsJYmD5VU7e XNNapl0LlIU88NdKp4QOMMW9G+BGDBSQ/FdGiSPVPkHqcaPG+lke+63JwloOWxPJAYxpo7n5 rMFFteqG4pYkrrTdaD2ZVamyq9CFlVnQ6dg/22y6IJz4EUdYCbRxFrEmpe4fdIi89vdvHmZw ==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.88,302,1635206400"; d="scan'208";a="828043513"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 20 Jan 2022 14:57:58 +0000
Received: from mail.cisco.com (xbe-aln-005.cisco.com [173.36.7.20]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 20KEvvRB026779 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Thu, 20 Jan 2022 14:57:57 GMT
Received: from xfe-aln-003.cisco.com (173.37.135.123) by xbe-aln-005.cisco.com (173.36.7.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.14; Thu, 20 Jan 2022 08:57:57 -0600
Received: from xfe-rtp-002.cisco.com (64.101.210.232) by xfe-aln-003.cisco.com (173.37.135.123) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.14; Thu, 20 Jan 2022 08:57:57 -0600
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xfe-rtp-002.cisco.com (64.101.210.232) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.14 via Frontend Transport; Thu, 20 Jan 2022 09:57:56 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=V+pjTSbUAk20PqA6bt+W3MoUq3QUsMAcSbLzDSHBWIWaNZAkWhj+qGxUrzHM71exn6YVKgR4LC3AXE0RmRRHWfhr+bkxK9937OISTYp6IVQqCjo2oxlb+lmFVUbZc4Joe7zK6NXxeWsIFF5q1Ax2EhkswLTqO+Lt1Ppfjks24LQ8akGa7y0xPtFwTOxgdHuSVcgWom+2jor3mhcS69JRNOunkfe/hbzYOijJkEJoJvUyDAw8j5j5WKQ+UfybJhrwZ1dwL1BgoMc5M8VI76nJsQ2YeptSgUVsccYnr+11butMU9N1LOpiIdQOQjmKePaoOz3ILMMjwzEg4ZPPzZYDhQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=OxJHClOue2tKARMoDy3xlD6fIMhola4gL/IGsTI6yV4=; b=c5lakJe0tmZ+M8J3sBtHxqJzARRLnWEYdIUzZCF9WtsmRSoiPlXodOv1YfJzKDNS4ru60YWKX1ZaqJVRf1H9CEgTwaZsIAB9AizoTAKs0zw4i1cKqN3WMzgFZsVS5QV105iin2EmykGP6u16U+Qe8qQbK90MDDnaXY8DGg+VfFIpfhccEMbVEDSDbTOcDUFbPOReQIHKEGeF3PFMUqrjReYLARUrQxIPZQ8bM8aNgv7VLoawbKVDTqVKBzkvPJE6pzzAG7bhYny0K9hOFYaELONB/3NgflF8wUpGQ7dsSNvZAt77AnlRNKPOWYg8J1ctoLgCkGb0ePgDoERcyRdMbA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=OxJHClOue2tKARMoDy3xlD6fIMhola4gL/IGsTI6yV4=; b=Tp9FOZPU3IhFasxKcHL86VvbDIgCvSRt+hipZXnEBjOaSMZOqle/OI6rvcNuRUf7NltDH5SV7kuuJ9WXEJcN2tVaZYY06prsa39erwyIhJUlawOnT0XS0yVBzkDRqFV7lQD1SPSBANk5wlX58HYmso3/hQIpbL3AMDi151MRNdI=
Received: from BY5PR11MB4196.namprd11.prod.outlook.com (2603:10b6:a03:1ce::13) by BYAPR11MB3048.namprd11.prod.outlook.com (2603:10b6:a03:89::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4888.12; Thu, 20 Jan 2022 14:57:55 +0000
Received: from BY5PR11MB4196.namprd11.prod.outlook.com ([fe80::c13b:f3ae:bbbe:2af4]) by BY5PR11MB4196.namprd11.prod.outlook.com ([fe80::c13b:f3ae:bbbe:2af4%3]) with mapi id 15.20.4909.010; Thu, 20 Jan 2022 14:57:55 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Brian Rosen <br@brianrosen.net>
CC: The IESG <iesg@ietf.org>, "draft-ietf-rum-rue@ietf.org" <draft-ietf-rum-rue@ietf.org>, "rum-chairs@ietf.org" <rum-chairs@ietf.org>, "rum@ietf.org" <rum@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: Robert Wilton's Discuss on draft-ietf-rum-rue-09: (with DISCUSS and COMMENT)
Thread-Index: AQHX8bCN1F+TUmIEYEaUAy27RN+CjqxAoUMAgCuWPyA=
Date: Thu, 20 Jan 2022 14:57:55 +0000
Message-ID: <BY5PR11MB4196309AF96FFBCF91E0BF01B55A9@BY5PR11MB4196.namprd11.prod.outlook.com>
References: <163957183657.10054.2789790212865898062@ietfa.amsl.com> <3A2D8BEA-23D0-4EE8-8EFE-CCE6B3EB0AFD@brianrosen.net>
In-Reply-To: <3A2D8BEA-23D0-4EE8-8EFE-CCE6B3EB0AFD@brianrosen.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=cisco.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: df6e6847-d484-412c-0654-08d9dc253d6e
x-ms-traffictypediagnostic: BYAPR11MB3048:EE_
x-microsoft-antispam-prvs: <BYAPR11MB304809FC717BABDA90C6B4FBB55A9@BYAPR11MB3048.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: m5T3ARnYyjB50LFpS3kVETKdMmIrlXB+Cjf6OdxmvCO0GlOWmlLfk5+40imlnznXDw+VtAbpQlaA6N3LitbaJR9Exvo0LVv/vKyZUOsAULFjCv6jpvPeiKQTEhvwYJi7OeQfIxloRjjDxvRBSJQMRL6I4JUsKjWRyt03capu/7F57nUz/DkY322mMSiO0cmBDFtTMj7/PXUSaAxfDNlZJckautWumBkGvf8bKGHP7GJGrEEJ0nb5jYztcAumhRg+jVJ9qPlh0EswwInbOXHITJ7bEJmileoMK2UddBayt3pbH45U7EeZKdgmQ29TL9fT19gZn4ZqxvdOa/M3jDzZVB2AMyh1HVWfkPmAdsGF0Ja/ZhnnbK5EyTt6m6GQPHz2uAjrZff7GFogIMSmqfSsy8FVJXfBFs0hYQvZ1BBic3OABjvCGTQVO9Sir8jpwQAsN+j4hhI29souXz51uirxzWoMEvqKl7ebagyFZmcPA7VYjks9kD2IM1qJjEDPV5ZsWsDMQUyJ8oGkp2xuqITfcXdnRvmhSpeoQVYkgs1VX1PuSWgA2CRkaR/ZSP/FIcRS2BZsuYYQA61/tBe2pRHpvLU7kMwKBeHYV+3JvulmhPtMI4/hF+G4p56EvGaWojRV+bSUO/aRlYIUP/vtbPa3pIs3X2afCf8Qr+yxKXppcBze2Fa/QbLibCaG6RUxLQLYmjHcQ6tDnU3AI7eJK3BEGd6MVCNvKAMpQTtBnxuTLGwqjuBKd8fUGxx51RCU5vOVrZCr3BY4qJ/fFFYq0aWwluHv5ri2hVbXLU1C5HIVKiNEAK8RvgdomBRNZ8pjjf7lDUvwcFRE08wMtp10F8tvIg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BY5PR11MB4196.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(366004)(5660300002)(122000001)(966005)(8676002)(4326008)(6506007)(38100700002)(53546011)(33656002)(26005)(76116006)(54906003)(66946007)(8936002)(52536014)(66476007)(508600001)(186003)(86362001)(64756008)(71200400001)(66446008)(38070700005)(9686003)(66556008)(55016003)(316002)(2906002)(6916009)(83380400001)(7696005); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?utf-8?B?TU9mbmZxMTVEa2xQUGdrcitrbHlpV2NyMkprQXd0L09GdldqdXl6Vms2TXdk?= =?utf-8?B?K0l0RENzdVRUVTJSVzJ3ZU1vbnFBeVhDa1JVR0NoY1JtcFVRQVdLbStKWTgx?= =?utf-8?B?bkdBSUlnQUk4MHY0N05mYVFFSHRuUVl3WWI0S2lSSTVuV29xNEpSTENCM212?= =?utf-8?B?YStCM0hCa1JIaHdxcTAwbzAvSVJNMTJjMTJ1ODZlMGZJWTNkdTg0ZVFTejFU?= =?utf-8?B?aVBKUi9nbHNoYWlMWFJhOFRHWHlqZWdONlhQOTFpSXZUTzBCOWJ4WVJ0cUFW?= =?utf-8?B?NHdkaTRvN3h6a3NUQkxPVXNrdjNxb01BVUhUbGJRMjVhVkhVK2lmMkFaY3Zh?= =?utf-8?B?a0FIcGM3d0RYTEZCR3V5d3Fmc2JoVDJSdW5UY3FRdmpMVjBNZXo4U0pxcTBG?= =?utf-8?B?ZHpjOS9zSGpyZStFdkFhQXpiRWZmT2dJaTl6dkNCQ2hFN093L0szbXJ4ZE1s?= =?utf-8?B?dDJVNHRoZGI1Y1ZGNlBVcDFmc2F6QjhBZ2NDTit5MTRkTEFlTXlmaFdUNzV2?= =?utf-8?B?Rm10ZjJ1eHN6MWNvOGtZTWtaZEplMXlBRER2TWRxNjRweExCMDNiQWNRRzRG?= =?utf-8?B?Nnc0dUR5R0lBUEpmT1VHWFBndDcvV3QzVER1Z0NGd2EwNFJBYkVmbUFKem9S?= =?utf-8?B?ZFJqQXJiRitJYmpmdmdJVmV1M09XWnc0azRIUTkwQU1VRkJuYWxmY0U0ZHQz?= =?utf-8?B?WTlla1Z0Y0ZDVFF0Z3h2azAxZGFOczJMMVdVWkhNclp4YXl0YmwrZzBibzRG?= =?utf-8?B?V3VzY2ozeS9JNXpOdDFBRmI4UTJHUDJ2SzdCcVVZNlFHbU5MRjJBSFROZnRo?= =?utf-8?B?Z2hiOVd6ei9QOXgwdGZlYkZjRzYwclo3M2JNdkd3SmNoZFpvam1adzhsSEZW?= =?utf-8?B?amxrU2N5MUthc3NCYllhcUhkei92Qzd3SHZ2ZnNkNk8rZG1jcXdLak5EVnIz?= =?utf-8?B?VkxRWnZLTEYvQVFFbWN0eVk4aldqSTVTbzVjcmpLNWFkYVdVR0ZFd0d1WUZX?= =?utf-8?B?b1lzZTBKc0hBdCs1TGQzNUgvekdRRWxYQW5HcU1EQURqamlhNVdmVGpTQlQ1?= =?utf-8?B?M1lkNVZwZ04zOHZ5QnZLbG1mc1U0M3R5R29TSnY4TENIZVhrUFBtMzhoU2ov?= =?utf-8?B?eEp4VXllN2xLTmdLakNSNjgyWW96Z2NTN2lJcHRweis0d0hLbmpIZ3VuZXVR?= =?utf-8?B?SEJMVnVneTVNUDJ4V0ZLNXU0eDdXR0ljdFFtbHRMZVR1eUF5UWFJRlArSktx?= =?utf-8?B?Y3VIMHl1NDdUUFVuWFluMEg3d081ZW56ak53Umc0d2d0WFloQ2RLbjN3NVh2?= =?utf-8?B?THhLRG1vcHgzZ1c0cmxMRVBUWC9uNUd3VnRKelJuOWQ1c290RmJpaGU5WGN0?= =?utf-8?B?bVc4djFGL3FxdkU0dk5WODFpczJGUjR2NmlmQW5heWtxZjdmNCtBZTJPcnNr?= =?utf-8?B?NVdOY09STE5EK3VVMC9jUXY2Q0JWc1dFdVJNelZYRmkyK3BSSHNyZHNlWnFj?= =?utf-8?B?dGk1dVFqTEt1UGxSMVpsMVVvU09rS0FiNHV1WkdTL0hjUVlLVEE5NWZIa2JB?= =?utf-8?B?Vkc4a2QvWjgxbkh6YXl1NTQwQWRSYXJZWEp0RWJsa0JXTVlobFhEaU1NYldH?= =?utf-8?B?cGc5SStQbmIwTHpXZkxCbk5HNnY1eTg0bUVIeWZCV3U4aW5CQ1JodVNmRWxk?= =?utf-8?B?QTljYzJ2MEZtQkdPQ2d2anpGbWpyU2tWZzZKaGxFYXRRMHo5Q0hSMnovYzRW?= =?utf-8?B?OUdwekN1S1p4WUQ5NHlaMG1Pakg1K0dkcGtmYTVCM3JxK0dmVTB6Z3NFMFhk?= =?utf-8?B?UHVCQ3BlTDg1dlpkMWJTcDJ2Vm5CY0Q2OS94LzgzTENjRy9DUXp5dDZnLzg1?= =?utf-8?B?UXJTS0dRKzNlMllJUGFrdWdhUS9Zd1EwZDU1TW4yK0lvTlozRzk5dTErMm5y?= =?utf-8?B?U1ZvaEJTcE9hd2Z6dVE1RGJBZ081QjNzWnIzdExiSHpMNkd0SzUrVTVzWlRz?= =?utf-8?B?ZG5RK0ZWeVZwcWQyNk5ndk1xSjBlQTF2cnFwYkZmbnMvR1RMK2VycnI1UVk4?= =?utf-8?B?TFVTSmVnTkZ3bWM1LytSdTNTR1lMem41OHV4VGVnMGV2bEZvYmkwYTBYRm4w?= =?utf-8?B?Wkorc05sZzBZN2ErVldxRnFleXcwWDM3ajJQK1NvRkJMbnIzWUpqTWlDT2x1?= =?utf-8?Q?as6tekYAZU+PKSHbCEsNzFU=3D?=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BY5PR11MB4196.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: df6e6847-d484-412c-0654-08d9dc253d6e
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Jan 2022 14:57:55.0907 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Ib4Xyjl1/WGYHf8cxmXQLuSwNO05WIx2FVfyAaEkfgL+f1cVEo7EyFwPCg+NP5HuDHh8PdfYexbPtarLNMa3Jw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3048
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.20, xbe-aln-005.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/a2hvoVP2Jc-dcYBBgiqcHE-B6SM>
Subject: Re: [Rum] Robert Wilton's Discuss on draft-ietf-rum-rue-09: (with DISCUSS and COMMENT)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jan 2022 14:58:04 -0000

SGkgQnJpYW4sDQoNClRoYW5rcyBmb3IgdGhlIGNvbW1lbnRzIGFuZCBzb3JyeSBmb3IgdGhlIHNs
b3cgcmVwbHkuDQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBCcmlh
biBSb3NlbiA8YnJAYnJpYW5yb3Nlbi5uZXQ+DQo+IFNlbnQ6IDIzIERlY2VtYmVyIDIwMjEgMjE6
MTYNCj4gVG86IFJvYiBXaWx0b24gKHJ3aWx0b24pIDxyd2lsdG9uQGNpc2NvLmNvbT4NCj4gQ2M6
IFRoZSBJRVNHIDxpZXNnQGlldGYub3JnPjsgZHJhZnQtaWV0Zi1ydW0tcnVlQGlldGYub3JnOyBy
dW0tDQo+IGNoYWlyc0BpZXRmLm9yZzsgcnVtQGlldGYub3JnOyBQYXVsIEt5eml2YXQgPHBreXpp
dmF0QGFsdW0ubWl0LmVkdT4NCj4gU3ViamVjdDogUmU6IFJvYmVydCBXaWx0b24ncyBEaXNjdXNz
IG9uIGRyYWZ0LWlldGYtcnVtLXJ1ZS0wOTogKHdpdGggRElTQ1VTUw0KPiBhbmQgQ09NTUVOVCkN
Cj4gDQo+IFRoYW5rIHlvdSBmb3IgeW91ciBjb21tZW50cy4gIFBsZWFzZSBzZWUgaW5saW5lDQo+
IA0KPiA+IE9uIERlYyAxNSwgMjAyMSwgYXQgNzozNyBBTSwgUm9iZXJ0IFdpbHRvbiB2aWEgRGF0
YXRyYWNrZXINCj4gPG5vcmVwbHlAaWV0Zi5vcmc+IHdyb3RlOg0KPiA+DQo+ID4gUm9iZXJ0IFdp
bHRvbiBoYXMgZW50ZXJlZCB0aGUgZm9sbG93aW5nIGJhbGxvdCBwb3NpdGlvbiBmb3INCj4gPiBk
cmFmdC1pZXRmLXJ1bS1ydWUtMDk6IERpc2N1c3MNCj4gPg0KPiA+IFdoZW4gcmVzcG9uZGluZywg
cGxlYXNlIGtlZXAgdGhlIHN1YmplY3QgbGluZSBpbnRhY3QgYW5kIHJlcGx5IHRvIGFsbA0KPiA+
IGVtYWlsIGFkZHJlc3NlcyBpbmNsdWRlZCBpbiB0aGUgVG8gYW5kIENDIGxpbmVzLiAoRmVlbCBm
cmVlIHRvIGN1dCB0aGlzDQo+ID4gaW50cm9kdWN0b3J5IHBhcmFncmFwaCwgaG93ZXZlci4pDQo+
ID4NCj4gPg0KPiA+IFBsZWFzZSByZWZlciB0byBodHRwczovL3d3dy5pZXRmLm9yZy9ibG9nL2hh
bmRsaW5nLWllc2ctYmFsbG90LXBvc2l0aW9ucy8NCj4gPiBmb3IgbW9yZSBpbmZvcm1hdGlvbiBh
Ym91dCBob3cgdG8gaGFuZGxlIERJU0NVU1MgYW5kIENPTU1FTlQNCj4gcG9zaXRpb25zLg0KPiA+
DQo+ID4NCj4gPiBUaGUgZG9jdW1lbnQsIGFsb25nIHdpdGggb3RoZXIgYmFsbG90IHBvc2l0aW9u
cywgY2FuIGJlIGZvdW5kIGhlcmU6DQo+ID4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
b2MvZHJhZnQtaWV0Zi1ydW0tcnVlLw0KPiA+DQo+ID4NCj4gPg0KPiA+IC0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0N
Cj4gPiBESVNDVVNTOg0KPiA+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gPg0KPiA+IFRoZXJlIGFyZSBhIGNv
dXBsZSBvZiBwb2ludHMgcmVsYXRlZCB0byB2ZXJzaW9uaW5nIHRoYXQgSSB3b3VsZCBsaWtlIHRv
IHNlZQ0KPiA+IGNsYXJpZmllZCwgYnV0IEkgaG9wZSB0aGF0IGl0IHNob3VsZCBiZSBmYWlybHkg
ZWFzeSB0byBkbyBzby4NCj4gPg0KPiA+IDEuDQo+ID4gICBUaGlzIG1lYW5zIGFuIGltcGxlbWVu
dGF0aW9uIG9mIGENCj4gPiAgIHNwZWNpZmljIG1ham9yIHZlcnNpb24gYW5kIG1pbm9yIHZlcnNp
b24gaXMgYmFja3dhcmRzIGNvbXBhdGlibGUgd2l0aA0KPiA+ICAgYWxsIG1pbm9yIHZlcnNpb25z
IG9mIHRoZSBtYWpvciB2ZXJzaW9uLg0KPiA+DQo+ID4gSXMgaXQgYWN0dWFsbHkgY29tcGF0aWJs
ZSB3aXRoIGFsbCBvdGhlciBtaW5vciB2ZXJzaW9ucywgb3Igb25seSBvdGhlciBtaW5vcg0KPiA+
IHZlcnNpb25zIHdpdGggYSBncmVhdGVyIG1pbm9yIHZlcnNpb24gbnVtYmVyLiAgRS5nLiwgY291
bGQgYW4NCj4gaW1wbGVtZW50YXRpb24gYmUNCj4gPiBjb2RlZCB0byB1c2UvZXhwZWN0IGEgb2Jq
ZWN0IGFkZGVkIGluIGEgbWlub3IgdmVyc2lvbiBidXQgdGhhdCBpcyBub3QNCj4gcHJlc2VudA0K
PiA+IGluIHByZWNlZGluZyBtaW5vciB2ZXJzaW9ucz8NCj4gQWxsIG90aGVyIG1pbm9yIHZlcnNp
b25zLg0KPiANCj4gSXQgaGFzIHRvIGJlIHRydWx5IG9wdGlvbmFsLiAgWW91IGNhbiBkbyB0aGlu
Z3MgbGlrZSBhZGQgdHdvIHBhcmFtZXRlcnMsIGEgYW5kDQo+IGIsIGFuZCBzYXkgaWYgYSBpcyBw
cm92aWRlZCBiIG11c3QgYmUgcHJvdmlkZWQsIGJ1dCBpdCBoYXMgdG8gd29yayBpZiBuZWl0aGVy
DQo+IGFyZSB0aGVyZSwgYW5kIGV2ZW4gaWYgYW4gaW1wbGVtZW50YXRpb24gcHJvdmlkZWQgYSBi
dXQgbm90IGIsIGFuIGVhcmxpZXINCj4gdmVyc2lvbiB3b3VsZCBpZ25vcmUgYS4NCg0KT2theS4g
IFRoYW5rcyBmb3IgY29uZmlybWluZy4NCg0KPiANCj4gPg0KPiA+IDIuDQo+ID4gICBUaGUgY29u
ZmlndXJhdGlvbiBBUEkgYWxzbyBwcm92aWRlcyB0aGUgc2FtZSB2ZXJzaW9uIG1lY2hhbmlzbSBh
cw0KPiA+ICAgc3BlY2lmaWVkIGFib3ZlIGluIFNlY3Rpb24gOS4xLiAgVGhlIHZlcnNpb24gb2Yg
dGhlIGNvbmZpZ3VyYXRpb24NCj4gPiAgIHNlcnZpY2UgTUFZIGJlIGRpZmZlcmVudCB0aGFuIHRo
ZSB2ZXJzaW9uIG9mIHRoZSBwcm92aWRlciBsaXN0DQo+ID4gICBzZXJ2aWNlLg0KPiA+DQo+ID4g
SXQgd2Fzbid0IG9idmlvdXMgdG8gbWUsIHRoYXQgZm9yIGEgZ2l2ZW4gcHJvdmlkZXIsIGhvdyB0
aGlzIGlzDQo+IGNvbW11bmljYXRlZC4NCj4gPiBJJ20gbm90IHRoYXQgZmFtaWxpYXIgd2l0aCBP
cGVuQVBJLCBidXQgbG9va3MgbGlrZSB0aGUgL1ZlcnNpb25zIHBhdGggaXMgYSB0b3ANCj4gPiBs
ZXZlbCBBUEkgcGF0aCwgYW5kIHRoZSBkYXRhIHRoYXQgaXMgY29udGFpbnMgc2VlbXMgdG8ganVz
dCBiZSB2ZXJzaW9uDQo+IG51bWJlcnMuDQo+ID4gSGVuY2UsIGhvdyB3b3VsZCBhIGNsaWVudCBr
bm93IHdoaWNoIHZlcnNpb25zIGFwcGx5IHRvIHByb3ZpZGVyIGxpc3QNCj4gc2VydmljZQ0KPiA+
IGFuZC9vciB3aGljaCB2ZXJzaW9ucyBhcHBseSB0byB0aGUgcHJvdmlkZSBjb25maWd1cmF0aW9u
IHNlcnZpY2UuDQo+IOKAmA0KPiBGaXJzdCBvZiBhbGwsIHRoZSBQcm92aWRlciBsaXN0IGlzIG5v
dCBhdmFpbGFibGUgYXQgYWxsbCBwcm92aWRlcnMuICBJdOKAmXMgb25seSBhdmFpbGFibGUNCj4g
YXQgYSBzZXJ2aWNlIHRoYXQgaXMgb25lIHBlciBjb3VudHJ5LiAgU28gb25lIGVudGl0eSBub3Jt
YWxseSBkb2VzbuKAmXQgc3VwcGx5DQo+IGJvdGggdGhlIFByb3ZpZGVyIGFuZCB0aGUgUHJvdmlk
ZXJDb25maWcgZW50cnkgcG9pbnRzLg0KPiBUbyBiZSByZWFsbHkgcGVkYW50aWMsIEkgc3VwcG9z
ZSB0aGF0IGl04oCZcyBhY3R1YWxseSBwb3NzaWJsZSBmb3IgaXQgdG8gYmUgb25lDQo+IGVudGl0
eSwgYW5kIHRoZW4gdGhhdCBzdGF0ZW1lbnQgdGhhdCB0aGVyZSBhcmUgc2VwYXJhdGUgdmVyc2lv
bnMgd291bGRu4oCZdA0KPiBhcHBseS4gIFNvIEkgZ3Vlc3MgSSB3aWxsIGNoYW5nZSB0aGUgdGV4
dCB0bzoNCj4gVW5sZXNzIHRoZSBwZXItY291bnRyeSBwcm92aWRlciBsaXN0IHNlcnZpY2UgaXMg
b3BlcmF0ZWQgYnkgYSBwcm92aWRlciBhdCB0aGUNCj4gc2FtZSBiYXNlIFVSSSBhcyB0aGF0IHBy
b3ZpZGVy4oCZcyBjb25maWd1cmF0aW9uIHNlcnZpY2UsIHRoZSB2ZXJzaW9uIG9mIHRoZQ0KPiBj
b25maWd1cmF0aW9uIHNlcnZpY2UgTUFZIGJlIGRpZmZlcmVudCBmcm9tIHRoZSB2ZXJzaW9uIG9m
IHRoZSBwcm92aWRlciBsaXN0DQo+IHNlcnZpY2UuDQoNClRoaXMgcHJvcG9zZWQgcmVzb2x1dGlv
biB0ZXh0IGlzIGZpbmUgd2l0aCBtZSwgc28gSSdsbCBjbGVhciBteSBkaXNjdXNzLg0KDQpBbHRl
cm5hdGl2ZWx5LCB5b3UgY291bGQgbWFrZSBpdCBzdGF0ZSB0aGF0IHRoZSB2ZXJzaW9uaW5nIGlu
Zm9ybWF0aW9uIGFwcGxpZXMgdG8gQVBJcyBhdCB0aGUgc2FtZSBiYXNlIFVSSSwgc28gaWYgYm90
aCBhcmUgYXZhaWxhYmxlIGF0IHRoZSBzYW1lIFVSTCBlbmQgcG9pbnQgdGhlbiB0aGV5IG11c3Qg
YmUgdGhlIHNhbWUgdmVyc2lvbiwgYnV0IG90aGVyd2lzZSB0aGV5IGFyZSBhbGxvd2VkIHRvIGJl
IGRpZmZlcmVudC4NCg0KDQo+IA0KPiA+DQo+ID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+IENPTU1FTlQ6
DQo+ID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+DQo+ID4gSGkgQnJpYW4sDQo+ID4NCj4gPiBUaGFuayB5
b3UgZm9yIHdvcmtpbmcgb24gdGhpcy4gIFRoaXMgdGVjaG5vbG9neSBpcyBxdWl0ZSBhIGxvbmcg
d2F5IG91dHNpZGUNCj4gb2YNCj4gPiBteSBleHBlcnRpc2UsIGFuZCBoZW5jZSBteSByZXZpZXcg
aXMgcHJpbWFyaWx5IGZvY3VzZWQgb24gdGhlDQo+IENvbmZpZ3VyYXRpb24NCj4gPiBzZWN0aW9u
IChzZWN0aW9uIDkpLg0KPiA+DQo+ID4gTml0OiB3aGVuIHVzZWQgd2l0aCB0aGUgZm9sbG93aW5n
IGludGVyZmFjZSA9PiAgd2hlbiB1c2VkIHdpdGggdGhlDQo+IGZvbGxvd2luZw0KPiA+IE9wZW5B
UEkgaW50ZXJmYWNlDQo+IEZpeGVkDQo+ID4NCj4gPiBOaXQ6IHdpdGggYSBjb3JyZXNwb25kaW5n
IGEgZW50cnkgcG9pbnQgLT4gd2l0aCBhIGNvcnJlc3BvbmRpbmcgZW50cnkgcG9pbnQNCj4gRml4
ZWQNCj4gPg0KPiA+ICAgTWlub3IgdmVyc2lvbiBkZWZpbml0aW9ucw0KPiA+ICAgU0hBTEwgb25s
eSBhZGQgb2JqZWN0cywgbm9uLXJlcXVpcmVkIG1lbWJlcnMgb2YgZXhpc3Rpbmcgb2JqZWN0cywg
YW5kDQo+ID4gICBub24tbWFuZGF0b3J5LXRvIHVzZSBmdW5jdGlvbnMgYW5kIFNIQUxMIE5PVCBk
ZWxldGUgYW55IG9iamVjdHMsDQo+ID4gICBtZW1iZXJzIG9mIG9iamVjdHMgb3IgZnVuY3Rpb25z
Lg0KPiA+DQo+ID4gV291bGQgImRlbGV0ZSBvciBjaGFuZ2UiIGJlIG1vcmUgY29ycmVjdCB0aGFu
IGp1c3QgImRlbGV0ZSIgaGVyZT8NCj4gQWRkZWQg4oCcb3IgY2hhbmdlIg0KPiA+DQo+ID4gU29t
ZXdoYXQgcmVsYXRlZCB0byB0aGUgZGlzY3VzcyBjb21tZW50LCBidXQgaXQgd2Fzbid0IGNsZWFy
IHRvIG1lIHdoeQ0KPiB0aGUNCj4gPiB2ZXJzaW9uaW5nIGlzIGRlc2NyaWJlZCBhcyBwYXJ0IG9m
IHRoZSAiUnVlIFByb3ZpZGVyIFNlbGVjdGlvbiIgc2VjdGlvbiBhbmQgSQ0KPiA+IHRoaW5rIHRo
YXQgdGhlIGRvY3VtZW50IHdvdWxkIGFyZ3VhYmx5IGJlIGNsZWFyZXIgaWYgdGhlIHZlcnNpb25p
bmcgbW92ZWQNCj4gdG8NCj4gPiBpdHMgb3duIHNlcGFyYXRlIDkuWCBzZWN0aW9uLCBtYWtpbmcg
aXQgY2xlYXIgdGhhdCB0aGUgdmVyc2lvbmluZyBhcHBsaWVzIHRvDQo+ID4gdGhlIGVudGlyZSBB
UEk/DQo+IEkgd2lsbCBkbyB0aGF0DQo+IA0KPiA+DQo+ID4gTml0OiBUaGUgbWV0aG9kIHRoZSBB
UEkgS2V5IGlzIG9idGFpbmVkIGlzIG5vdCBzcGVjaWZpZWQgaW4gdGhpcyBkb2N1bWVudC4NCj4g
PT4NCj4gPiAgUGVyaGFwcyAiVGhlIG1ldGhvZCB1c2VkIHRvIG9idGFpbiB0aGUgQVBJIGtleSDi
gKYiDQo+IEZpeGVkDQo+ID4NCj4gPiAgIFRoZSBwcm92aWRlciBNQVkgcmVmdXNlIHRvIHByb3Zp
ZGUgc2VydmljZSB0byBhbiBpbXBsZW1lbnRhdGlvbg0KPiA+ICAgcHJlc2VudGluZyBhbiBBUEkg
S2V5IGl0IGRvZXMgbm90IHJlY29nbml6ZS4NCj4gPg0KPiA+IFdoeSBpcyB0aGlzIG5vdCBhIE1V
U1Q/DQo+IFdlbGwsIHN1cHBvc2UgYSBwcm92aWRlciBkb2VzbuKAmXQgaW1wbGVtZW50IGFuIEFQ
SSBrZXksIGJ1dCB0aGUgY2xpZW50DQo+IHN1cHBsaWVzIG9uZS4gIFRoYXQgd291bGQgbm90IGJl
IHJlY29nbml6ZWQgYnkgdGhlIHByb3ZpZGVyLCBidXQgaXQgZG9lc27igJl0DQo+IGNhcmUsIHNv
IGl0IHByb3ZpZGVzIHNlcnZpY2UuDQoNCk9rYXkuDQoNCj4gDQo+ID4NCj4gPiBJcyB0aGUgImlu
c3RhbmNlLWlkZW50aWZpZXIiIGFyYml0cmFyaWx5IGNob3NlbiBieSB0aGUgY2xpZW50PyAgT3Ro
ZXJ3aXNlLCBpdA0KPiA+IHdhc24ndCBjbGVhciB0byBtZSBob3cgYSBjbGllbnQgd291bGQgZGlz
Y292ZXIgb3Iga25vdyB3aGF0DQo+ID4gImluc3RhbmNlLWlkZW50aWZpZXIiIHRvIHVzZS4gIEl0
IG1pZ2h0IGJlIGhlbHBmdWwgaWYgdGhlIHRleHQgY2xhcmlmaWVkIHRoaXMsDQo+IEkgYWRkZWQg
dGhhdCB0ZXh0DQo+IA0KPiA+IGFuZCBwb3NzaWJseSBldmVuIHRoZSBwYXJhbWV0ZXIgbmFtZSBj
b3VsZCBiZSBjaGFuZ2VkIHRvIG1ha2UgaXQgbW9yZQ0KPiBvYnZpb3VzDQo+ID4gdGhhdCBpdCBp
cyBhIGNsaWVudCBwcm92aWRlZCB2YWx1ZT8NCj4g4oCcY2xpZW50SW5zdGFuY2VJZOKAnSB3b3Vs
ZG7igJl0IGhlbHAuICBJdCB3b3VsZCBoYXZlIHRvIGJlDQo+IOKAnGNsaWVudFByb3ZpZGVkSW5z
dGFuY2VJZOKAnS4gIFRoYXQgc2VlbXMgdG8gYmUgYSBiaXQgbXVjaCBhcyBhIHBhcmFtZXRlcg0K
PiBuYW1lLiAgSeKAmWxsIGRvIGl0IGlmIHlvdSB0aGluayBpdOKAmXMgaW1wb3J0YW50LCBidXQg
SeKAmW0gaW5jbGluZWQgdG8ganVzdCBsZWF2ZSB0aGUNCj4gZXhwbGFuYXRvcnkgdGV4dCBzcGVj
aWZ5aW5nIHRoYXQgaXTigJlzIGNsaWVudCBwcm92aWRlZC4NCg0KSnVzdCBhZGRpbmcgdGhlIGV4
cGxhbmF0b3J5IHRleHQgaXMgZmluZSB3aXRoIG1lLiAgVGhhbmtzIGZvciBjaGVja2luZy4NCg0K
UmVnYXJkcywNClJvYg0KDQoNCj4gPg0KPiA+IFJlZ2FyZHMsDQo+ID4gUm9iDQo+ID4NCj4gPg0K
PiA+DQoNCg==


From nobody Mon Jan 24 12:51:48 2022
Return-Path: <noreply@ietf.org>
X-Original-To: rum@ietf.org
Delivered-To: rum@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8342E3A0C1A; Mon, 24 Jan 2022 12:51:46 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-rum-rue@ietf.org, rum-chairs@ietf.org, rum@ietf.org, pkyzivat@alum.mit.edu, pkyzivat@alum.mit.edu
X-Test-IDTracker: no
X-IETF-IDTracker: 7.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <164305750569.13490.3059330084181158513@ietfa.amsl.com>
Date: Mon, 24 Jan 2022 12:51:46 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/N_hfZI281YKywvSkdx5odu_u5dU>
Subject: [Rum] Martin Duke's No Objection on draft-ietf-rum-rue-10: (with COMMENT)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 20:51:47 -0000

Martin Duke has entered the following ballot position for
draft-ietf-rum-rue-10: 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/blog/handling-iesg-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


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



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

Thanks for addressing my DISCUSS, and your work to make the internet more accessible for all.




From nobody Mon Jan 24 12:52:20 2022
Return-Path: <martin.h.duke@gmail.com>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6778B3A0C25; Mon, 24 Jan 2022 12:52:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cMlHuFv_tMP5; Mon, 24 Jan 2022 12:52:10 -0800 (PST)
Received: from mail-vk1-xa30.google.com (mail-vk1-xa30.google.com [IPv6:2607:f8b0:4864:20::a30]) (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 E3F5C3A0C02; Mon, 24 Jan 2022 12:52:09 -0800 (PST)
Received: by mail-vk1-xa30.google.com with SMTP id w17so6899856vko.9; Mon, 24 Jan 2022 12:52:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=L44R+A8naY85UD7QeQJ7CCAmVzk4aWY5nG5apX2F1sE=; b=NfYhTQOhuzTlFr4vmwwh1bBcmi+RX6YvZetd8GrLIL1iQ2T7zMjNMYvRTrd6wippfw MfeGFEbzVaJAbpSQuJLKEFFMwOdGzPu4+l8Lpk61ZG6tM2D3HwZw7fawpjo0qq/vY2wc UoFZw/2Ay6mh/1YQTEyR/6YoCuYkk5Pd2aDCx9aXOJ1HDUQxGomCJKrjTPIRXAdH5w4t 3rwl38DEovmE0nU3Edr9Cj3IIp+ERFFnL2x+D2CzT8emK8dvei+DqOmnZbbWxJqoXAUD gdMbo6GPxBMGvangsi9swFgImYTmZ3fKOwZFh1KMzecrg0qFfcC2g4/zMxTu5DA3uISm 7Orw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=L44R+A8naY85UD7QeQJ7CCAmVzk4aWY5nG5apX2F1sE=; b=qrknyKEbGBQeHBHg5mR6F6su+/A5ygTc2Gk4kEFNY/IKfS7/wMin7gLpwvl03AmHKQ QeUWmM8suVK/mC9rNmFrfeBtxQfrv1FSLimjiIMtXJIKp04oKQiBoxTG+/3lD/uHljuj BvXkw/hr6zAZaOonI+Tjk28/x46cFVkT+T+Bt00g4NvqmUj6H+JITVEFLWpppA4walT0 tylowg46CMVrOMTR081D3rGM4T0OyTrPu94KJ5YTD4vSc/Qq+RC9LyjrclCKmh6iK3JC wZ7xqVQ/8Yx+rydnLmAA1iCk7R0YjhTq+X++81co2tRokjPGoR18SZ1it99YbGT85NdX JP0A==
X-Gm-Message-State: AOAM5318kSSLG7jaL7zKimOnd2Rk1G4ERjTTmlW3Y6VLzTF+AbclCJZo XmFGVs8/II3GsSqyYtD2OUZme3nD44ltTeDcKyZ6kxsE
X-Google-Smtp-Source: ABdhPJykpBIIBZTlzBdB+PuTV8YoqKofuk5ToGt7pVGZBoWiM/F+hc/vXdtgQ6Y3dDka6gAKf+Gunn4rSeHdv/A7Kso=
X-Received: by 2002:a05:6122:130a:: with SMTP id e10mr3205248vkp.39.1643057527959;  Mon, 24 Jan 2022 12:52:07 -0800 (PST)
MIME-Version: 1.0
References: <163890001133.3603.6708235729467005454@ietfa.amsl.com> <47D5FC0F-129A-4227-8280-5DDC2D486BFB@brianrosen.net> <CAM4esxQ_rP_OMf7OoN4jZYxgvOS+7dtMTCCPk=UaO6La0b2mAA@mail.gmail.com> <66F541E4-3415-49A8-A4C6-577F179A295E@brianrosen.net>
In-Reply-To: <66F541E4-3415-49A8-A4C6-577F179A295E@brianrosen.net>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Mon, 24 Jan 2022 12:51:56 -0800
Message-ID: <CAM4esxTtyDxFiDLRy8rGsUBdCzANK41iy67GmzzM-9_U32S7rg@mail.gmail.com>
To: Brian Rosen <br@brianrosen.net>
Cc: The IESG <iesg@ietf.org>, draft-ietf-rum-rue@ietf.org, rum-chairs@ietf.org, rum@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary="0000000000004cb5d305d65a242d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/vw4gmpcaW6v4xxGXZGsGHWkdUiI>
Subject: Re: [Rum] Martin Duke's Discuss on draft-ietf-rum-rue-09: (with DISCUSS and COMMENT)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 20:52:15 -0000

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

Yep, cleared, thanks.

On Thu, Jan 20, 2022 at 6:51 AM Brian Rosen <br@brianrosen.net> wrote:

> I submitted a -10 which I hope addresses your issues.
>
> Brian
>
>
> On Jan 4, 2022, at 7:06 PM, Martin Duke <martin.h.duke@gmail.com> wrote:
>
> Hi Brian,
>
> Thanks for clearing things up! Replies inline.
>
> Besides the already-proposed changes, the main action item is my scope
> followup question to #3.
>
> On Thu, Dec 23, 2021 at 12:14 PM Brian Rosen <br@brianrosen.net> wrote:
>
>> Thank you for your comments.  Please see inline
>>
>> On Dec 7, 2021, at 1:00 PM, Martin Duke via Datatracker <noreply@ietf.or=
g>
>> wrote:
>>
>> Martin Duke has entered the following ballot position for
>> draft-ietf-rum-rue-09: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/blog/handling-iesg-ballot-positions=
/
>> for more information about how to handle DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-rum-rue/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> Thanks to Bernard Adoba for the TSVART review. It largely informs my
>> DISCUSS.
>>
>> 1. If I understand correctly, this draft is not at all about
>> interoperating
>> with a WebRTC endpoint, instead borrowing some requirements from that
>> family of
>> specs rather than re-inventing the wheel. That's great, but putting that
>> explicitly in the intro would be helpful.
>>
>> Not quite.  I propose the following additional information in the media
>> section where WebRTC specs are discussed:
>> To use WebRTC with this document, a gateway that presents a WebRTC serve=
r
>> interface towards a browser, and a RUE client interface towards a provid=
er
>> is assumed.  The gateway would interwork signaling, and as noted below,
>> interwork at least any real time text media, in order to allow a standar=
d
>> browser baed WebRTC client to be a VRS client.  The combination of the
>> browser client and the gateway would be a RUE user.
>>
>> 2. In particular, the statement that RUE is a "non-browser endpoint" is
>> confusing if it's not actually meant to interoperate with WebRTC. I
>> *think*
>> you're attempting to distinguish between WebRTC's browser-only
>> requirements and
>> endpoint requirements, but I could be wrong here.
>>
>> See above, but I still may have to just remove that =E2=80=9Cnon browser
>> endpoint=E2=80=9D text, because it=E2=80=99s confusing people.
>>
>>
> OK, I look forward to seeing the new text.
>
>>
>> 3. In Section 5.5, you require conformance with RFC8835 with a few vague=
ly
>> worded exceptions. It would be helpful to actually go through that
>> document
>> enumerate exactly which normative statements in 8835 do not apply. That
>> said,
>> I'm not sure I agree with Bernard that 8835 requires *use* of ICE, rathe=
r
>> than
>> support, but maybe we can clarify this in the TSVART thread.
>>
>> The only reference to 8835 reads:
>> Implementations MUST conform to [RFC8835] except for its guidance on the
>> WebRTC data channel, which this specification does not use.
>>
>> I have looked carefully at all mentions of =E2=80=9Cdata channel=E2=80=
=9D in 8835 and it
>> seems really obvious what does and doesn=E2=80=99t apply.  Here is an ex=
ample:
>>
>>    For data transport over the WebRTC data channel [RFC8831 <https://dat=
atracker.ietf.org/doc/html/rfc8831>], WebRTC
>>    endpoints MUST support SCTP over DTLS over ICE.  This encapsulation
>>    is specified in [RFC8261 <https://datatracker.ietf.org/doc/html/rfc82=
61>].  Negotiation of this transport in the
>>    Session Description Protocol (SDP) is defined in [RFC8841 <https://da=
tatracker.ietf.org/doc/html/rfc8841>].  The SCTP
>>    extension for I-DATA [RFC8260 <https://datatracker.ietf.org/doc/html/=
rfc8260>] MUST be supported.
>>
>>    The setup protocol for WebRTC data channels described in [RFC8832 <ht=
tps://datatracker.ietf.org/doc/html/rfc8832>]
>>    MUST be supported.
>>
>>
>> None of it applies.  It might not be quite as obvious that because the
>> above doesn=E2=80=99t apply, there is no SCTP requirement, but do you th=
ink we need
>> to say that, given that the only discussion of SCTP is in relation to th=
e
>> data channel?
>> I could call out each one of the data channel statements, but it really
>> does seem superfluous.
>>
>
> The scope of this isn't clear to me. I would imagine the WebRTC end of th=
e
> gateway *does* support the webRTC data channel standards, yes? So the
> gateway that you specify in this document is translating the WebRTC data
> channel into the Section 6.2 data channel.
>
> Aside from the scoping question,  I'm struggling to find economical
> alternative wording that makes it clearer. So I'm OK with keeping the 883=
5
> "data channel" exception.
>
>
>>
>> 4. As Bernard points out, this ambiguity extends to IPv4 and 6 support.
>> The
>> 8835 requirements are specific to browsers, so they might not apply. If
>> you
>> require support for both, but not necessarily on the same device, it
>> would be
>> good to say so.
>>
>>
>> We require support for IPv4 and IPv6 expressly.  We say:
>> Implementations MUST support IPv4 and IPv6.  Dual stack support is NOT
>> required and provider implementations MAY support separate interfaces fo=
r
>> IPv4 and IPv6 by having more than one server in the appropriate SRV reco=
rd
>> where there is either an A or AAAA record in each server DNS record but =
not
>> both.  The same version of IP MUST be used for both signaling and media =
of
>> a call unless ICE [RFC8445] is used, in which case candidates may
>> explicitly offer IPv4, IPv6 or both for any media stream.
>>
>> If there is any conflict between that and 8835, I don=E2=80=99t see it.
>>
>
> Sorry I missed that text somehow!
>
>>
>> 5. In Sec. 6, it says "This specification adopts the media specification=
s
>> for
>> WebRTC ([RFC8825])." Is this a normative statement? Must RUEs comply wit=
h
>> the
>> entirety of that document, or is this an informative statement and the
>> real
>> requirements are in the subsections of Sec 6? From the discussion, it
>> sounds
>> like you want to include the requirements for WebRTC "endpoints", but no=
t
>> for
>> WebRTC "browsers". It would help to clarify all this.
>>
>> We=E2=80=99re not requiring anything normative from 8825 I think.  Only =
the parts
>> we expressly state. I could add: =E2=80=9Cexplicit requirements from the=
 WebRTC
>> suite of documents are described below=E2=80=9D.
>>
>
> I think that would improve clarity.
>
>>
>> It's also possible that my initial understanding is incorrect, in which
>> case
>> the later points don't make any sense and some explanatory text is neede=
d.
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> Thanks for your work to make the internet more accessible for all.
>>
>>
>

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

<div dir=3D"ltr">Yep, cleared, thanks.</div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jan 20, 2022 at 6:51 AM Brian=
 Rosen &lt;<a href=3D"mailto:br@brianrosen.net">br@brianrosen.net</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=
=3D"overflow-wrap: break-word;">I submitted a -10 which I hope addresses yo=
ur issues.<div><br></div><div>Brian</div><div><br><div><br><blockquote type=
=3D"cite"><div>On Jan 4, 2022, at 7:06 PM, Martin Duke &lt;<a href=3D"mailt=
o:martin.h.duke@gmail.com" target=3D"_blank">martin.h.duke@gmail.com</a>&gt=
; wrote:</div><br><div><div dir=3D"ltr" style=3D"font-family:Helvetica;font=
-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;le=
tter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;wh=
ite-space:normal;word-spacing:0px;text-decoration:none"><div>Hi Brian,</div=
><div><br></div><div>Thanks for clearing things up! Replies inline.</div><d=
iv><br></div><div>Besides the already-proposed changes, the main action ite=
m is my scope followup question to #3.</div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 23, 2021 at 12:14 PM Bria=
n Rosen &lt;<a href=3D"mailto:br@brianrosen.net" target=3D"_blank">br@brian=
rosen.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div>Thank you for your comments.=C2=A0 Please see inline<br><di=
v><br><blockquote type=3D"cite"><div>On Dec 7, 2021, at 1:00 PM, Martin Duk=
e via Datatracker &lt;<a href=3D"mailto:noreply@ietf.org" target=3D"_blank"=
>noreply@ietf.org</a>&gt; wrote:</div><br><div><div>Martin Duke has entered=
 the following ballot position for<br>draft-ietf-rum-rue-09: Discuss<br><br=
>When responding, please keep the subject line intact and reply to all<br>e=
mail addresses included in the To and CC lines. (Feel free to cut this<br>i=
ntroductory paragraph, however.)<br><br><br>Please refer to<span>=C2=A0</sp=
an><a href=3D"https://www.ietf.org/blog/handling-iesg-ballot-positions/" ta=
rget=3D"_blank">https://www.ietf.org/blog/handling-iesg-ballot-positions/</=
a><br>for more information about how to handle DISCUSS and COMMENT position=
s.<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-rum-rue/" =
target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-rum-rue/</a><=
br><br><br><br>------------------------------------------------------------=
----------<br>DISCUSS:<br>-------------------------------------------------=
---------------------<br><br>Thanks to Bernard Adoba for the TSVART review.=
 It largely informs my DISCUSS.<br><br>1. If I understand correctly, this d=
raft is not at all about interoperating<br>with a WebRTC endpoint, instead =
borrowing some requirements from that family of<br>specs rather than re-inv=
enting the wheel. That&#39;s great, but putting that<br>explicitly in the i=
ntro would be helpful.<br></div></div></blockquote>Not quite.=C2=A0 I propo=
se the following additional information in the media section where WebRTC s=
pecs are discussed:</div><div>To use WebRTC with this document, a gateway t=
hat presents a WebRTC server interface towards a browser, and a RUE client =
interface towards a provider is assumed.=C2=A0=C2=A0The gateway would inter=
work=C2=A0signaling, and as noted below, interwork at least any real time t=
ext media, in order to allow a standard browser baed WebRTC client to be a =
VRS client.=C2=A0=C2=A0The combination of the browser client=C2=A0and the g=
ateway would be a RUE user.<br><blockquote type=3D"cite"><div><div>2. In pa=
rticular, the statement that RUE is a &quot;non-browser endpoint&quot; is<b=
r>confusing if it&#39;s not actually meant to interoperate with WebRTC. I *=
think*<br>you&#39;re attempting to distinguish between WebRTC&#39;s browser=
-only requirements and<br>endpoint requirements, but I could be wrong here.=
<br></div></div></blockquote>See above, but I still may have to just remove=
 that =E2=80=9Cnon browser endpoint=E2=80=9D text, because it=E2=80=99s con=
fusing people.</div><div><br></div></div></blockquote><div><br></div><div>O=
K, I look forward to seeing the new text.=C2=A0=C2=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div><div><blockquote type=3D"cite"><div>=
<div><br>3. In Section 5.5, you require conformance with RFC8835 with a few=
 vaguely<br>worded exceptions. It would be helpful to actually go through t=
hat document<br>enumerate exactly which normative statements in 8835 do not=
 apply. That said,<br>I&#39;m not sure I agree with Bernard that 8835 requi=
res *use* of ICE, rather than<br>support, but maybe we can clarify this in =
the TSVART thread.<br></div></div></blockquote>The only reference to 8835 r=
eads:</div><div>Implementations MUST conform to [RFC8835]=C2=A0except for i=
ts guidance on the WebRTC data channel, which this specification does not u=
se.=C2=A0</div><div><br></div><div>I have looked carefully at all mentions =
of =E2=80=9Cdata channel=E2=80=9D in 8835 and it seems really obvious what =
does and doesn=E2=80=99t apply.=C2=A0 Here is an example:</div><div><br></d=
iv><div><pre style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;=
font-variant-ligatures:normal">   For data transport over the WebRTC data c=
hannel [<a href=3D"https://datatracker.ietf.org/doc/html/rfc8831" title=3D"=
&quot;WebRTC Data Channels&quot;" target=3D"_blank">RFC8831</a>], WebRTC
   endpoints MUST support SCTP over DTLS over ICE.  This encapsulation
   is specified in [<a href=3D"https://datatracker.ietf.org/doc/html/rfc826=
1" title=3D"&quot;Datagram Transport Layer Security (DTLS) Encapsulation of=
 SCTP Packets&quot;" target=3D"_blank">RFC8261</a>].  Negotiation of this t=
ransport in the
   Session Description Protocol (SDP) is defined in [<a href=3D"https://dat=
atracker.ietf.org/doc/html/rfc8841" title=3D"&quot;Session Description Prot=
ocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol=
 (SCTP) over Datagram Transport Layer Security (DTLS) Transport&quot;" targ=
et=3D"_blank">RFC8841</a>].  The SCTP
   extension for I-DATA [<a href=3D"https://datatracker.ietf.org/doc/html/r=
fc8260" title=3D"&quot;Stream Schedulers and User Message Interleaving for =
the Stream Control Transmission Protocol&quot;" target=3D"_blank">RFC8260</=
a>] MUST be supported.

   The setup protocol for WebRTC data channels described in [<a href=3D"htt=
ps://datatracker.ietf.org/doc/html/rfc8832" title=3D"&quot;WebRTC Data Chan=
nel Establishment Protocol&quot;" target=3D"_blank">RFC8832</a>]
   MUST be supported.
</pre><div><br></div></div><div>None of it applies.=C2=A0 It might not be q=
uite as obvious that because the above doesn=E2=80=99t apply, there is no S=
CTP requirement, but do you think we need to say that, given that the only =
discussion of SCTP is in relation to the data channel?</div><div>I could ca=
ll out each one of the data channel statements, but it really does seem sup=
erfluous.<br></div></div></blockquote><div><br></div><div>The scope of this=
 isn&#39;t clear to me. I would imagine the WebRTC end of the gateway *does=
* support the webRTC data channel standards, yes? So the gateway that you s=
pecify in this document is translating the WebRTC data channel into the Sec=
tion 6.2 data channel.</div><div><br></div><div>Aside from the scoping ques=
tion,=C2=A0 I&#39;m struggling to find economical alternative wording that =
makes it clearer. So I&#39;m OK with keeping the 8835 &quot;data channel&qu=
ot; exception.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div><div><blockquote type=3D"cite"><div><div><br>4. As Bernard=
 points out, this ambiguity extends to IPv4 and 6 support. The<br>8835 requ=
irements are specific to browsers, so they might not apply. If you<br>requi=
re support for both, but not necessarily on the same device, it would be<br=
>good to say so.<br></div></div></blockquote><div><br></div>We require supp=
ort for IPv4 and IPv6 expressly.=C2=A0 We say:</div><div>Implementations MU=
ST support IPv4 and IPv6.=C2=A0=C2=A0Dual stack support is NOT required and=
 provider implementations MAY support separate interfaces for IPv4 and IPv6=
 by having more than one server in=C2=A0the appropriate SRV record where th=
ere is either an A or AAAA record in each server DNS record but not both.=
=C2=A0=C2=A0The same version of IP MUST be used for both signaling and medi=
a of a call unless=C2=A0ICE [RFC8445]=C2=A0is used, in which case candidate=
s may explicitly offer IPv4, IPv6 or both for any media stream.=C2=A0</div>=
<div><br></div><div>If there is any conflict between that and 8835, I don=
=E2=80=99t see it.</div></div></blockquote><div><br></div><div>Sorry I miss=
ed that text somehow!=C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div><div><br><blockquote type=3D"cite"><div><div>5. In Sec. 6, it =
says &quot;This specification adopts the media specifications for<br>WebRTC=
 ([RFC8825]).&quot; Is this a normative statement? Must RUEs comply with th=
e<br>entirety of that document, or is this an informative statement and the=
 real<br>requirements are in the subsections of Sec 6? From the discussion,=
 it sounds<br>like you want to include the requirements for WebRTC &quot;en=
dpoints&quot;, but not for<br>WebRTC &quot;browsers&quot;. It would help to=
 clarify all this.<br></div></div></blockquote>We=E2=80=99re not requiring =
anything normative from 8825 I think.=C2=A0 Only the parts we expressly sta=
te. I could add: =E2=80=9Cexplicit requirements from the WebRTC suite of do=
cuments are described below=E2=80=9D.<br></div></div></blockquote><div><br>=
</div><div>I think that would improve clarity.=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div><div><blockquote type=3D"cite"><div><=
div><br>It&#39;s also possible that my initial understanding is incorrect, =
in which case<br>the later points don&#39;t make any sense and some explana=
tory text is needed.<br><br><br>-------------------------------------------=
---------------------------<br>COMMENT:<br>--------------------------------=
--------------------------------------<br><br>Thanks for your work to make =
the internet more accessible for all.</div></div></blockquote></div></div><=
/blockquote></div></div></div></blockquote></div><br></div></div></blockquo=
te></div>

--0000000000004cb5d305d65a242d--


From nobody Mon Jan 31 13:37:07 2022
Return-Path: <session-request@ietf.org>
X-Original-To: rum@ietf.org
Delivered-To: rum@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 353933A190C; Mon, 31 Jan 2022 13:37:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: pkyzivat@alum.mit.edu, rum-chairs@ietf.org, rum@ietf.org, superuser@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164366502440.23874.1688432312451295745@ietfa.amsl.com>
Date: Mon, 31 Jan 2022 13:37:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/ea5tZHJn4ct_9nr2KODzNwe7GJU>
Subject: [Rum] rum - Not having a session at IETF 113
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jan 2022 21:37:05 -0000

Paul Kyzivat, a chair of the rum working group, indicated that the rum working group does not plan to hold a session at IETF 113.

This message was generated and sent by the IETF Meeting Session Request Tool.



