
From nobody Sat Jun  1 04:46:49 2019
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C52EF120221 for <mmusic@ietfa.amsl.com>; Sat,  1 Jun 2019 04:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 IvvIgLIOHpoL for <mmusic@ietfa.amsl.com>; Sat,  1 Jun 2019 04:46:45 -0700 (PDT)
Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (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 E8847120298 for <mmusic@ietf.org>; Sat,  1 Jun 2019 04:46:44 -0700 (PDT)
Received: by mail-vs1-xe33.google.com with SMTP id c24so8431669vsp.7 for <mmusic@ietf.org>; Sat, 01 Jun 2019 04:46:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KhynwbIceXd73DhfG1z31ElMni9Tx+VQUdvHSBuLbvA=; b=HOaB0qOt2SeMfSowqdCq1pS4/PBUGWpx+v9j81XeJwOUpLhE6f9XX0RrEDsWgy+FsT dVN//0fomAgwZe8dTmpW9mSLIuhQOBOWp18gg/A/BgM7uEa+lyKijIdLdL2osbeQunow 9MbkUraZmUcx+y472IzjBV9mCKXFsMypKY3evUHIjQsGF5fz+yGP2GPSweBZSdRmpyko i6MIudwnH2yb4TDW6m4iJzqyKn2qWi6QHyxw5p07NRhuhbJkx4ZqnmVw5I/OY29b/mAz EiO0oUb/flRGRDaHhmSnywGvMbEylN2e8CE1U9+Um7Pg5Hnwe46UWVKOI1zFq0MP3StO U8LA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KhynwbIceXd73DhfG1z31ElMni9Tx+VQUdvHSBuLbvA=; b=cYS5EX9eferh7s0+8kOg8T4bWalM7JB5sYGx6Fe24UaiSvuG8OXzmPzzvsTiRCz0JC 7o83FhD2K89BOk+XhRkeTCE+B9k2kscsNslIyNYE5TlMJrJP3m2N3Ab2FT3cNhrjbWBf 6tS2+yo3/xUf/vI7sJRw5ra+0Iwt+VMqbjTejzA7OjKplrnHUlL3Wx/eTqlzivFp4m4H 5vHHJUdbJdu/5zIcgn6sfdGfvh9SU+LVAVLiV81DWcEGxWkjCCUSPt1os+jEb4eG5iXv JLhNgWm89Vtdv8zPcDuCoyPHscG+LHRuL5Cye19HdyeKZUE1JVh9W9x7GFpgIVLB+Rtb HmYA==
X-Gm-Message-State: APjAAAWmzfsuEP3LZNEHjLaXcOdLsIsNMR15yNxe+hnwhWs3X0STJjbz iC7DCbGHiRhNuVzMk/4GnqgrFBAiU/NpIOzbPX4=
X-Google-Smtp-Source: APXvYqynm6E5T2EJe25QuVyMCqfHvZHvvmjgaDCztixHfS34VEa6g6E+9mjrYBSh9JwfHfMO2p4Em+/ZAJiTPF+D3nU=
X-Received: by 2002:a67:d007:: with SMTP id r7mr1900527vsi.184.1559389604009;  Sat, 01 Jun 2019 04:46:44 -0700 (PDT)
MIME-Version: 1.0
References: <155895828521.742.9442906172366273232@ietfa.amsl.com> <CAMRcRGSdYfRp2QVcjECYhFHeAOG5+XgxOprqofGPBoKYFys4xQ@mail.gmail.com> <CAD5OKxuN0JzsARip5VxtjNiV_KK4R+XPiUFovbMMvVg=LwVphg@mail.gmail.com> <CAMRcRGTKd_N-Dxr_zqNu6kae6Aru_ytkQMtV=SNusrB6ipRuGg@mail.gmail.com> <CAD5OKxvTXCnmDdgzZ+B6vVtYt1cKCb2oa00cuVCA-D6s_4480g@mail.gmail.com> <CAMRcRGQScm4wFFeFd-RLtQdc3nRgMkdajAFEKqQEnJ=XkQR_uw@mail.gmail.com> <CAD5OKxum0EcoKCF9zvK_3hfzVjevOW4+eBYh+fpPtW+Ht+0VRw@mail.gmail.com>
In-Reply-To: <CAD5OKxum0EcoKCF9zvK_3hfzVjevOW4+eBYh+fpPtW+Ht+0VRw@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Sat, 1 Jun 2019 17:16:31 +0530
Message-ID: <CAMRcRGSC9T4VbrjEA=pcb1vyPy6e6RV0GOmj3E9Ev0OrWsE04Q@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, Flemming Andreasen <fandreas@cisco.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000069db90058a41afa5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/cLguYe2uKJ0okkcfdLsfR1XiLVk>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-28.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2019 11:46:48 -0000

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

Hi Roman

   I see your point. Will update to clarify the answerer behvaior as
suggested.

Thanks
Suhas

On Sat, Jun 1, 2019 at 2:42 AM Roman Shpount <roman@telurix.com> wrote:

> Hi Suhas,
>
> On Fri, May 31, 2019 at 1:30 AM Suhas Nandakumar <suhasietf@gmail.com>
> wrote:
>
>> On Fri, May 31, 2019 at 12:08 AM Roman Shpount <roman@telurix.com> wrote=
:
>>
>>> On Wed, May 29, 2019 at 10:03 PM Suhas Nandakumar <suhasietf@gmail.com>
>>> wrote:
>>>
>>>> On Thu, May 30, 2019 at 4:34 AM Roman Shpount <roman@telurix.com>
>>>> wrote:
>>>>
>>>>> One of the remaining issues is in Section 3.2.5. Since you have
>>>>> removed the note that "If this condition is not met, the agents MUST
>>>>> process the SDP based on normal [RFC3264] procedures, without using a=
ny of
>>>>> the ICE mechanisms described in the remainder of this specification",=
 the
>>>>> document no longer states what happens when "a=3Dice-mismatch" attrib=
ute is
>>>>> included in the answer.
>>>>>
>>>>> To clarify this we need to change current text that states:
>>>>>
>>>>> The presence of certain application layer gateways MAY modify the
>>>>> transport address information as described in Section 8.2.2.  The beh=
avior
>>>>> of the responding agent in such a situation is implementation defined=
.
>>>>> Informally, the responding agent MAY consider the mismatched transpor=
t
>>>>> address information as a plausible new candidate learnt from the peer=
 and
>>>>> continue its ICE processing with that transport address included.
>>>>> Alternatively, the responding agent MAY include an "a=3Dice-mismatch"
>>>>> attribute in its answer and MAY also omit a=3Dcandidate attributes fo=
r such
>>>>> data streams.
>>>>>
>>>>>
>>>>> To the following:
>>>>>
>>>>> The presence of certain application layer gateways MAY modify the
>>>>> transport address information as described in Section 8.2.2.  The beh=
avior
>>>>> of the responding agent in such a situation is implementation defined=
.
>>>>> Informally, the responding agent MAY consider the mismatched transpor=
t
>>>>> address information as a plausible new candidate learnt from the peer=
 and
>>>>> continue its ICE processing with that transport address included.  *A=
lternatively,
>>>>> the responding agent MAY include an "a=3Dice-mismatch" attribute in i=
ts
>>>>> answer for such data streams.  If agent chooses to include an
>>>>> "a=3Dice-mismatch" attribute in its answer for a data stream, then it=
 MUST
>>>>> also, for this data stream, omit "a=3Dcandidate" attributes, MUST ter=
minate
>>>>> the usage of ICE procedures, and MUST instead use **procedures
>>>>> defined in **[RFC3264]  .*
>>>>>
>>>>>
>>>>>
>>>> The point 3 in that para covers this aspect. So this section as a whol=
e
>>>> covers the scenarios you describe above.
>>>>
>>>> 3.  In some cases, controlling/initiator agent may receive the SDP
>>>>        answer that may omit "a=3Dcandidate" attributes for the data
>>>>        stream, and instead include a media level "a=3Dice-mismatch"
>>>>        attribute.  This signals to the offerer that the answerer
>>>>        supports ICE, but that ICE processing was not used for this dat=
a
>>>>        stream.  In this case, ICE processing MUST be terminated for th=
is
>>>>        data stream and [RFC3264] procedures MUST be followed instead.
>>>>
>>>>
>>> There are couple of issues with the current text:
>>>
>>> 1. Reading the current text reader might assume that it is acceptable t=
o
>>> include a=3Dice-mismatch and still include a=3Dcandidate in the data st=
ream in
>>> the answer. This is not the case.
>>>
>>> [Suhas] Also for this, i see point 3 covers this
>>
>>  In some cases, controlling/initiator agent may receive the SDP
>>        answer that may omit "a=3Dcandidate" attributes for the data
>>        stream, and instead include a media level "a=3Dice-mismatch"
>>        attribute
>>
>>
>>
>>
>>> 2. The text in point 3 states that offerer is not going to use ICE
>>> procedures for the data stream which includes a=3Dice-mismatch and will=
 use
>>> RFC3264 instead. Nothing specifies that the answerer is supposed to sto=
p
>>> using ICE procedures when including a=3Dice-mismatch.
>>>
>>
>>
>> (Suhas) Doesn=E2=80=99t this piece in point 3 say exactly that behavior =
on the
>> answerer side when it sets ice-mismatch for a data stream
>>
>> This signals to the offerer that the answerer
>>        supports ICE, but that ICE processing was not used for this data
>>        stream.
>>
>>
>>>
> Once again, this tells how the answer is supposed to be interpreted, but
> you have removed the language that specified what responding agent is
> supposed to do. There is nothing in the current document that says that
> agent which generates the answer with "a=3Dice-mismatch" MUST stop using =
ICE
> for this specific data stream. Also, current language says that "the
> responding agent MAY include an "a=3Dice-mismatch" attribute in its answe=
r
> and MAY also omit a=3Dcandidate attributes for such data streams", which =
I
> would interpret that responding agent MAY include "a=3Dice-mismatch" and =
not
> omit "a=3Dcandidate". Behavior of the agent that receives an m=3D line wi=
th
> both "a=3Dice-mismatch" and  "a=3Dcandidate" is also unspecified. It shou=
ld be
> illegal to generates such session descriptions.
>
> Regards,
> _____________
> Roman Shpount
>
>

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

<div dir=3D"ltr">Hi Roman<div><br></div><div>=C2=A0 =C2=A0I see your point.=
 Will update to clarify the answerer behvaior as suggested.</div><div><br><=
/div><div>Thanks</div><div>Suhas</div></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jun 1, 2019 at 2:42 AM Roman =
Shpount &lt;<a href=3D"mailto:roman@telurix.com">roman@telurix.com</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div dir=3D"ltr"><div><div class=3D"gmail-m_-5868305088928798684gm=
ail_signature">Hi Suhas,</div><div class=3D"gmail-m_-5868305088928798684gma=
il_signature"><br></div><div dir=3D"ltr" class=3D"gmail-m_-5868305088928798=
684gmail_signature">On Fri, May 31, 2019 at 1:30 AM Suhas Nandakumar &lt;<a=
 href=3D"mailto:suhasietf@gmail.com" target=3D"_blank">suhasietf@gmail.com<=
/a>&gt; wrote:<br></div></div></div><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div><div>On Fri, Ma=
y 31, 2019 at 12:08 AM Roman Shpount &lt;<a href=3D"mailto:roman@telurix.co=
m" target=3D"_blank">roman@telurix.com</a>&gt; wrote:<br></div></div><div><=
div class=3D"gmail_quote"><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><div><div><div class=3D"gmail-m_-5868305088928798684gmail-m_622727487=
903714812m_6555128525063485850m_7375540959713555906gmail_signature">On Wed,=
 May 29, 2019 at 10:03 PM Suhas Nandakumar &lt;<a href=3D"mailto:suhasietf@=
gmail.com" target=3D"_blank">suhasietf@gmail.com</a>&gt; wrote:<br></div></=
div></div><div class=3D"gmail_quote"><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><div>On Thu, May 30, 2019 at 4:34 AM Roman Shpount &l=
t;<a href=3D"mailto:roman@telurix.com" target=3D"_blank">roman@telurix.com<=
/a>&gt; wrote:<br></div></div><div class=3D"gmail_quote"><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>One of the remaining issues is i=
n Section 3.2.5. Since you have removed the note that &quot;If this conditi=
on is not met, the agents MUST process the SDP based=C2=A0on normal [RFC326=
4] procedures, without using any of the ICE=C2=A0mechanisms described in th=
e remainder of this specification&quot;, the document no longer states what=
 happens when &quot;a=3Dice-mismatch&quot; attribute is included in the ans=
wer.</div><div><br></div><div>To clarify this we need to change current tex=
t that states:</div><div><br></div><blockquote style=3D"margin:0px 0px 0px =
40px;border:none;padding:0px"><div>The presence of certain application laye=
r gateways MAY modify the transport address information as described in Sec=
tion 8.2.2.=C2=A0 The behavior of the responding agent in such a situation =
is implementation defined.=C2=A0 Informally, the responding agent MAY consi=
der the mismatched transport address information as a plausible new candida=
te learnt from the peer and continue its ICE processing with that transport=
 address included.=C2=A0 Alternatively, the responding agent MAY include an=
 &quot;a=3Dice-mismatch&quot; attribute in its answer and MAY also omit a=
=3Dcandidate attributes for such data streams.=C2=A0=C2=A0</div></blockquot=
e><div><br></div><div>To the following:</div><div><br></div><div><blockquot=
e style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div>The presen=
ce of certain application layer gateways MAY modify the transport address i=
nformation as described in Section 8.2.2.=C2=A0 The behavior of the respond=
ing agent in such a situation is implementation defined.=C2=A0 Informally, =
the responding agent MAY consider the mismatched transport address informat=
ion as a plausible new candidate learnt from the peer and continue its ICE =
processing with that transport address included. =C2=A0<b>Alternatively, th=
e responding agent MAY include an &quot;a=3Dice-mismatch&quot; attribute in=
 its answer for such data streams.=C2=A0 If agent chooses to include an &qu=
ot;a=3Dice-mismatch&quot; attribute in its answer for a data stream, then i=
t MUST also, for this data stream, omit &quot;a=3Dcandidate&quot; attribute=
s, MUST terminate the usage of ICE procedures, and MUST instead use=C2=A0</=
b><b>procedures defined in=C2=A0</b><b>[RFC3264]=C2=A0 .</b></div></blockqu=
ote><div><br></div></div></div></blockquote><div><br></div><div>The point 3=
 in that para covers this aspect. So this section as a whole covers the sce=
narios you describe above.</div><div><br></div><div><pre style=3D"box-sizin=
g:border-box;overflow:auto;font-family:&quot;PT Mono&quot;,Monaco,monospace=
;font-size:14px;padding:10px;margin-top:0px;margin-bottom:10.5px;line-heigh=
t:1.214;color:rgb(0,0,0);word-break:break-all;background-color:rgb(255,253,=
245);border:1px solid rgb(204,204,204);border-radius:4px">3.  In some cases=
, controlling/initiator agent may receive the SDP
       answer that may omit &quot;a=3Dcandidate&quot; attributes for the da=
ta
       stream, and instead include a media level &quot;a=3Dice-mismatch&quo=
t;
       attribute.  This signals to the offerer that the answerer
       supports ICE, but that ICE processing was not used for this data
       stream.  In this case, ICE processing MUST be terminated for this
       data stream and [RFC3264] procedures MUST be followed instead.</pre>=
</div></div></div></blockquote><div><br></div><div>There are couple of issu=
es with the current text:</div><div><br></div><div>1. Reading the current t=
ext reader might assume that it is acceptable to include a=3Dice-mismatch a=
nd still include a=3Dcandidate in the data stream in the answer. This is no=
t the case.</div><div><br></div></div></div></blockquote><div>[Suhas] Also =
for this, i see point 3 covers this=C2=A0</div><div><pre style=3D"box-sizin=
g:border-box;overflow:auto;font-family:&quot;PT Mono&quot;,Monaco,monospace=
;font-size:14px;padding:10px;margin-top:0px;margin-bottom:10.5px;line-heigh=
t:1.214;color:rgb(0,0,0);word-break:break-all;background-color:rgb(255,253,=
245);border:1px solid rgb(204,204,204);border-radius:4px"> In some cases, c=
ontrolling/initiator agent may receive the SDP
       answer that may omit &quot;a=3Dcandidate&quot; attributes for the da=
ta
       stream, and instead include a media level &quot;a=3Dice-mismatch&quo=
t;
       attribute</pre></div><div><br></div><div>=C2=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div><div class=3D"gmail_quote"><div></d=
iv><div>2. The text in point 3 states that offerer is not going to use ICE =
procedures for the data stream which includes a=3Dice-mismatch and will use=
 RFC3264 instead. Nothing specifies that the answerer is supposed to stop u=
sing ICE procedures when including a=3Dice-mismatch.</div><div></div></div>=
</div></blockquote><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div>=
<div dir=3D"auto">(Suhas) Doesn=E2=80=99t this piece in point 3 say exactly=
 that behavior on the answerer side when it sets ice-mismatch for a data st=
ream</div><div dir=3D"auto"><pre style=3D"box-sizing:border-box;overflow:au=
to;font-family:&quot;PT Mono&quot;,Monaco,monospace;font-size:14px;padding:=
10px;margin-top:0px;margin-bottom:10.5px;line-height:1.214;color:rgb(0,0,0)=
;word-break:break-all;background-color:rgb(255,253,245);border:1px solid rg=
b(204,204,204);border-radius:4px">This signals to the offerer that the answ=
erer
       supports ICE, but that ICE processing was not used for this data
       stream.</pre></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><div class=3D"gmail_quote"><br></div></div></blockquote></div></div><=
/div></blockquote><div><br></div>Once again, this tells how the answer is s=
upposed to be interpreted, but you have removed the language that specified=
 what responding agent is supposed to do. There is nothing in the current d=
ocument that says that agent which generates the answer with &quot;a=3Dice-=
mismatch&quot; MUST stop using ICE for this specific data stream. Also, cur=
rent language says that &quot;the responding agent MAY include an &quot;a=
=3Dice-mismatch&quot; attribute in its answer and MAY also omit a=3Dcandida=
te attributes for such data streams&quot;, which I would interpret that res=
ponding agent MAY include &quot;a=3Dice-mismatch&quot; and not omit &quot;a=
=3Dcandidate&quot;. Behavior of the agent that receives an m=3D line with b=
oth &quot;a=3Dice-mismatch&quot; and =C2=A0&quot;a=3Dcandidate&quot; is als=
o unspecified. It should be illegal to generates such session descriptions.=
</div><div class=3D"gmail_quote"><br><div>Regards,</div>_____________<br>Ro=
man Shpount<br class=3D"gmail-m_-5868305088928798684gmail-Apple-interchange=
-newline"><div>=C2=A0</div></div></div>
</blockquote></div>

--00000000000069db90058a41afa5--


From nobody Sat Jun  1 05:01:29 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DA84F120274; Sat,  1 Jun 2019 05:01:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mmusic@ietf.org
Message-ID: <155939048775.17273.13936885338207300192@ietfa.amsl.com>
Date: Sat, 01 Jun 2019 05:01:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/P1JUHwAFb7k3B7orDUu2YcC8wkU>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-30.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2019 12:01:28 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : Session Description Protocol (SDP) Offer/Answer procedures for Interactive Connectivity Establishment (ICE)
        Authors         : Marc Petit-Huguenin
                          Suhas Nandakumar
                          Ari Keranen
	Filename        : draft-ietf-mmusic-ice-sip-sdp-30.txt
	Pages           : 42
	Date            : 2019-06-01

Abstract:
   This document describes Session Description Protocol (SDP) Offer/
   Answer procedures for carrying out Interactive Connectivity
   Establishment (ICE) between the agents.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-30
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-30

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-30


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Jun  1 05:02:32 2019
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33911120386 for <mmusic@ietfa.amsl.com>; Sat,  1 Jun 2019 05:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 FRjmbH9eSJ_L for <mmusic@ietfa.amsl.com>; Sat,  1 Jun 2019 05:02:29 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 E681712034E for <mmusic@ietf.org>; Sat,  1 Jun 2019 05:02:28 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id b10so8440387vsp.5 for <mmusic@ietf.org>; Sat, 01 Jun 2019 05:02:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=x8Is1rQN1bz6SnYSEEvqsjaA1rXNgPOKecq6tyFF9M0=; b=UYAh1gJhCoulk2+AbBiwRdzy4oOCnCX/Pg/rE4BTWjJV6fIIpRretZR6sj5hfOBSUA ncP7bA0h7pWhdoAfUjK5Wk9/EOGsHtuBIDo2Eu68Dr6/ZOUTYnFm3nf2zxVvIPDblW8L k4nc1/TVY40td9CyhUTSI9vYiL5tUNZqK/PVDdI+JZW+idYgChkFqnZ+DQPtxFYuTyOT 8+dXPufxYePQ2RlpSzgCs2QDNfMDf89TtIJWZ5wIjIsknfH74/luucX3/4i3B6dUTrw+ WQhlTHaGi+/r6lyQZG9jCL35WCmXhYEb5s43u441+oLWFJ15Be5y8imCiZDNqTKGGDrs 00SA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=x8Is1rQN1bz6SnYSEEvqsjaA1rXNgPOKecq6tyFF9M0=; b=TcUXrsCzNNz/EZoQ5AiAppZ1Hse0qHLNDqpYi5yRoTwamjbjE/37+g/cxMQ63/HgLA QPVLH9OXjyszwJ/ILi61lI+SuFqgItMqCsbN6Uru7p/jx6zh0nfwVUDqAWkqWNKCI5ee kaU6uux/Jzlq79UTsKSyYwyZmHVY7QNpOd0DAQhZrMeAvJLTxuV7tvF4LU3TMqQTXT// EdjelmK/uc1R1MxRslGWgRlZHaiVQhHcl8MlAXwob4dRiqv2SlU3JBaZuCAEz0DQsOeX KK7ZR3JdN8GugYZ5IJHR4fHRy0RYJrNlxu6OuONPX329oxcgPinRW8yNXhii8HdPgG5/ bTuQ==
X-Gm-Message-State: APjAAAV8L1T+44Adr1gZ4XhODEZapfg/BsAG5joEjludadMtHcSxwlzu 5QpNHJ8XdruW0FWWx89ZtuDibPwiNfpUqDkRiRKd3lqaWZY=
X-Google-Smtp-Source: APXvYqzkbgwVBl3H9tXQqS1KIRYrlIaw1Zf+/mIQygPxjxk7bC5nvRPkVhOvYWkmC9GSsvx8UN77WQwqVuqCICQIBPU=
X-Received: by 2002:a67:db06:: with SMTP id z6mr3397649vsj.69.1559390546652; Sat, 01 Jun 2019 05:02:26 -0700 (PDT)
MIME-Version: 1.0
References: <155939048775.17273.13936885338207300192@ietfa.amsl.com>
In-Reply-To: <155939048775.17273.13936885338207300192@ietfa.amsl.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Sat, 1 Jun 2019 17:32:14 +0530
Message-ID: <CAMRcRGQpzMtmWYXEtq0oDp=1J52eXFWiGxX_vJLaOUuhNMWtGg@mail.gmail.com>
To: mmusic WG <mmusic@ietf.org>
Cc: Roman Shpount <roman@telurix.com>, Flemming Andreasen <fandreas@cisco.com>
Content-Type: multipart/alternative; boundary="0000000000009972d5058a41e7cd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/bqPz1sMi5558qzAhk2loISzX-9w>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-30.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2019 12:02:31 -0000

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

Version 30 address answerer ice-mismatch clarification suggestions

Thanks
Suhas

On Sat, Jun 1, 2019 at 5:31 PM <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multiparty Multimedia Session Control WG
> of the IETF.
>
>         Title           : Session Description Protocol (SDP) Offer/Answer
> procedures for Interactive Connectivity Establishment (ICE)
>         Authors         : Marc Petit-Huguenin
>                           Suhas Nandakumar
>                           Ari Keranen
>         Filename        : draft-ietf-mmusic-ice-sip-sdp-30.txt
>         Pages           : 42
>         Date            : 2019-06-01
>
> Abstract:
>    This document describes Session Description Protocol (SDP) Offer/
>    Answer procedures for carrying out Interactive Connectivity
>    Establishment (ICE) between the agents.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-30
> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-30
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-30
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">Version 30 address answerer ice-mismatch clarification sug=
gestions<div><br></div><div>Thanks</div><div>Suhas</div></div><br><div clas=
s=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jun 1, 2019=
 at 5:31 PM &lt;<a href=3D"mailto:internet-drafts@ietf.org">internet-drafts=
@ietf.org</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"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Multiparty Multimedia Session Control WG o=
f the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Session Description Protocol (SDP) Offer/Answer procedures for Interactive=
 Connectivity Establishment (ICE)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Marc=
 Petit-Huguenin<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Suhas Nandakumar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ari Keranen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mmusic-ice-sip-sdp-30.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 42<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2019-06-01<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes Session Description Protocol (SDP) Off=
er/<br>
=C2=A0 =C2=A0Answer procedures for carrying out Interactive Connectivity<br=
>
=C2=A0 =C2=A0Establishment (ICE) between the agents.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/"=
 rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draf=
t-ietf-mmusic-ice-sip-sdp/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-30" re=
l=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-m=
music-ice-sip-sdp-30</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-=
sdp-30" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d=
oc/html/draft-ietf-mmusic-ice-sip-sdp-30</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-ice-sip-sd=
p-30" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?url=
2=3Ddraft-ietf-mmusic-ice-sip-sdp-30</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div>

--0000000000009972d5058a41e7cd--


From nobody Sat Jun  1 16:06:21 2019
Return-Path: <fandreas@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E84BD120045 for <mmusic@ietfa.amsl.com>; Sat,  1 Jun 2019 16:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level: 
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f4ccmUQP-A4z for <mmusic@ietfa.amsl.com>; Sat,  1 Jun 2019 16:06:16 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A58C11200CE for <mmusic@ietf.org>; Sat,  1 Jun 2019 16:06:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9458; q=dns/txt; s=iport; t=1559430376; x=1560639976; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=LImOkO8lzuva1fyh12DL5xlCjHYPmhQISt10dPYZxfc=; b=aXmpbzxrpsFI5nG2pWOMPTq6wtsvu/PrTdzxexT7w0D0f/jRvNFkgnBm teEe482YAh851IF8ibqkwsiKH5dCOBeamUMazAat57vsDR+Z9ml6Wcqld 0mTIcjjnnzSp/OVb8Hfm5zRMbfk/SqoCgF9x3y+V8zr9c0mIjkUdHt9Hs 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AHAAD3A/Nc/5RdJa1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUQUBAQEBCwGCEGlRATIohBSIHIxTJYlQiQ2GAIF7CQEBAQ4?= =?us-ascii?q?YAQoMAQGDekYCgwQjNAkOAQMBAQQBAQIBBG0cDIVLAQEEAQEhSwsQCQIYJwM?= =?us-ascii?q?CAicfEQYBDAYCAQGDHgGBdhQPjXqbaoEvH4QXAg5BQIMegUaBNAGLWReBQD+?= =?us-ascii?q?BEScMgl8+gmEBAQIBARaEUYJYBKh5CYIPhj+MbQYbgiJohgmDWyeJWY0Ahwu?= =?us-ascii?q?PO4FPOIFYTSMVGiGCbAmCEheIYYVbIwMwkAcBAQ?=
X-IronPort-AV: E=Sophos;i="5.60,540,1549929600";  d="scan'208,217";a="280842028"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Jun 2019 23:06:15 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTP id x51N6EIX013575; Sat, 1 Jun 2019 23:06:15 GMT
To: Suhas Nandakumar <suhasietf@gmail.com>, mmusic WG <mmusic@ietf.org>
References: <155939048775.17273.13936885338207300192@ietfa.amsl.com> <CAMRcRGQpzMtmWYXEtq0oDp=1J52eXFWiGxX_vJLaOUuhNMWtGg@mail.gmail.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <d77b3cbf-1e59-3602-91ff-d7afa058b3c4@cisco.com>
Date: Sat, 1 Jun 2019 19:06:14 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGQpzMtmWYXEtq0oDp=1J52eXFWiGxX_vJLaOUuhNMWtGg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------670E8059610FD6E5EE31DE89"
Content-Language: en-US
X-Outbound-SMTP-Client: 10.118.10.19, rtp-fandreas-2-8812.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Tmhli6ymOXWxogcZeb6raFjfVt8>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-30.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2019 23:06:19 -0000

This is a multi-part message in MIME format.
--------------670E8059610FD6E5EE31DE89
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Thank you for the updated document Suhas. I have read through it and it 
generally looks good to me. One question though:

Section 3.3.4 says:
<quote>

    Once the state of each check list is Completed, and if the agent is
    the controlling agent, it nominates a candidate pair [RFC8445] and
    checks for each data stream whether the nominated pair matches the
    default candidate pair.  If there are one or more data streams with a
    match, and the peer did not indicate support for the 'ice2' ice-
    option, the controlling agent MUST generate a subsequent offer
    (Section 3.4.1), in which the connection address, port and transport
    protocol in the "c=" and "m=" lines associated with each data stream
    match the corresponding local information of the nominated pair for
    that data stream.
</quote>

In the second sentence, shouldn't it rather be if there is a line with a 
mismatch instead of a match ?

Thanks

-- Flemming



On 6/1/19 8:02 AM, Suhas Nandakumar wrote:
> Version 30 address answerer ice-mismatch clarification suggestions
>
> Thanks
> Suhas
>
> On Sat, Jun 1, 2019 at 5:31 PM <internet-drafts@ietf.org 
> <mailto:internet-drafts@ietf.org>> wrote:
>
>
>     A New Internet-Draft is available from the on-line Internet-Drafts
>     directories.
>     This draft is a work item of the Multiparty Multimedia Session
>     Control WG of the IETF.
>
>             Title           : Session Description Protocol (SDP)
>     Offer/Answer procedures for Interactive Connectivity Establishment
>     (ICE)
>             Authors         : Marc Petit-Huguenin
>                               Suhas Nandakumar
>                               Ari Keranen
>             Filename        : draft-ietf-mmusic-ice-sip-sdp-30.txt
>             Pages           : 42
>             Date            : 2019-06-01
>
>     Abstract:
>        This document describes Session Description Protocol (SDP) Offer/
>        Answer procedures for carrying out Interactive Connectivity
>        Establishment (ICE) between the agents.
>
>
>     The IETF datatracker status page for this draft is:
>     https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>
>     There are also htmlized versions available at:
>     https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-30
>     https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-30
>
>     A diff from the previous version is available at:
>     https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-30
>
>
>     Please note that it may take a couple of minutes from the time of
>     submission
>     until the htmlized version and diff are available at
>     tools.ietf.org <http://tools.ietf.org>.
>
>     Internet-Drafts are also available by anonymous FTP at:
>     ftp://ftp.ietf.org/internet-drafts/
>
>     _______________________________________________
>     mmusic mailing list
>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>     https://www.ietf.org/mailman/listinfo/mmusic
>


--------------670E8059610FD6E5EE31DE89
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Thank you for the updated document Suhas. I have read through it and
    it generally looks good to me. One question though: <br>
    <br>
    Section 3.3.4 says:<br>
    &lt;quote&gt;<br>
    <pre style="color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial; overflow-wrap: break-word; white-space: pre-wrap;">   Once the state of each check list is Completed, and if the agent is
   the controlling agent, it nominates a candidate pair [RFC8445] and
   checks for each data stream whether the nominated pair matches the
   default candidate pair.  If there are one or more data streams with a
   match, and the peer did not indicate support for the 'ice2' ice-
   option, the controlling agent MUST generate a subsequent offer
   (Section 3.4.1), in which the connection address, port and transport
   protocol in the "c=" and "m=" lines associated with each data stream
   match the corresponding local information of the nominated pair for
   that data stream.
&lt;/quote&gt;
</pre>
    In the second sentence, shouldn't it rather be if there is a line
    with a mismatch instead of a match ? <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming <br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 6/1/19 8:02 AM, Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMRcRGQpzMtmWYXEtq0oDp=1J52eXFWiGxX_vJLaOUuhNMWtGg@mail.gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div dir="ltr">Version 30 address answerer ice-mismatch
        clarification suggestions
        <div><br>
        </div>
        <div>Thanks</div>
        <div>Suhas</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Sat, Jun 1, 2019 at 5:31 PM
          &lt;<a href="mailto:internet-drafts@ietf.org"
            moz-do-not-send="true">internet-drafts@ietf.org</a>&gt;
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
          A New Internet-Draft is available from the on-line
          Internet-Drafts directories.<br>
          This draft is a work item of the Multiparty Multimedia Session
          Control WG of the IETF.<br>
          <br>
                  Title           : Session Description Protocol (SDP)
          Offer/Answer procedures for Interactive Connectivity
          Establishment (ICE)<br>
                  Authors         : Marc Petit-Huguenin<br>
                                    Suhas Nandakumar<br>
                                    Ari Keranen<br>
                  Filename        : draft-ietf-mmusic-ice-sip-sdp-30.txt<br>
                  Pages           : 42<br>
                  Date            : 2019-06-01<br>
          <br>
          Abstract:<br>
             This document describes Session Description Protocol (SDP)
          Offer/<br>
             Answer procedures for carrying out Interactive Connectivity<br>
             Establishment (ICE) between the agents.<br>
          <br>
          <br>
          The IETF datatracker status page for this draft is:<br>
          <a
            href="https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/</a><br>
          <br>
          There are also htmlized versions available at:<br>
          <a
            href="https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-30"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-30</a><br>
          <a
href="https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-30"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-30</a><br>
          <br>
          A diff from the previous version is available at:<br>
          <a
href="https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-30"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-30</a><br>
          <br>
          <br>
          Please note that it may take a couple of minutes from the time
          of submission<br>
          until the htmlized version and diff are available at <a
            href="http://tools.ietf.org" rel="noreferrer"
            target="_blank" moz-do-not-send="true">tools.ietf.org</a>.<br>
          <br>
          Internet-Drafts are also available by anonymous FTP at:<br>
          <a href="ftp://ftp.ietf.org/internet-drafts/" rel="noreferrer"
            target="_blank" moz-do-not-send="true">ftp://ftp.ietf.org/internet-drafts/</a><br>
          <br>
          _______________________________________________<br>
          mmusic mailing list<br>
          <a href="mailto:mmusic@ietf.org" target="_blank"
            moz-do-not-send="true">mmusic@ietf.org</a><br>
          <a href="https://www.ietf.org/mailman/listinfo/mmusic"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
        </blockquote>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------670E8059610FD6E5EE31DE89--


From nobody Sat Jun  1 20:07:47 2019
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61D73120091 for <mmusic@ietfa.amsl.com>; Sat,  1 Jun 2019 20:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 Gncm1FIuzJ_L for <mmusic@ietfa.amsl.com>; Sat,  1 Jun 2019 20:07:43 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 0F866120041 for <mmusic@ietf.org>; Sat,  1 Jun 2019 20:07:43 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id z11so9182940vsq.9 for <mmusic@ietf.org>; Sat, 01 Jun 2019 20:07:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/qn60/UpnoISjH+7pPNnrTsaQsyTRJ2SbwXXbkfTzNc=; b=cP0YqiQcOYnaXUal+knaC7HX8qcCiOifCnjeKrXeR2LgmxkpKY46+9PZr6MijTmp4x IJ3HIvWVpWKCJeKrKqX6e+J7eqY+tyap5ehqIYjWxjt/oqUqu3ttMRG0gQXQ/EXUxMxb EIAtqV+CpUMYcXsWeCI1/hXZvx+E/uIFqAHWCga/Q8MuNdaYg7v0C/YXVT4SRJ2X4wOK xChslTwaWNRgtDqQP03Wme/khdcK7LbXq4s8ALBzIVhI1jd8Ri50oi1SaG6CjMkbaQSF PmFrzcXyKgcjggcaZtTSx8xtafeGjGkg2mViXLYb0Yy9PohQRC2lVN6pF5SGI5Na0dEO 620Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/qn60/UpnoISjH+7pPNnrTsaQsyTRJ2SbwXXbkfTzNc=; b=Kv1LPybL7dM8awl2HRRGwyj2Dg+hbDd0j1kmdQHRRIfm1hEC/TDpXQL6eX7ubhVhpe N4IGxrL+ZpWXTPvGWz05eZS0Rge7rdKJ/87okKjf3T9D34vE84zPPZ5BRnZTfsEpymXf uPAjIYgSDeOFJz4AJnOxYb/LDKklyux0IObsVseu0VQoQXlY/6qO01jCIuKrpeWAQuHU M9TfwCo3uE0RSAbBRsTC9IYF7BBA8b1C5+kVXF9WO7L7OQF0XChlHRWm9N35NFjOAh0/ WKjV3GOoFiYpsB+nqccuWkKHEz0OW0e0HqvH4Hmzsq1LtAIdUltJbY5bbdeCG4x8HM6v 8lNg==
X-Gm-Message-State: APjAAAXWSvoBgOAnzUADxN0fkI+dbUepZOoq2opx3u5ivBmw/Ly2wsdV psbykdPnz2zOlQ9ATrl/273NZgsuso0t3IzUMvU=
X-Google-Smtp-Source: APXvYqyqMGIdb2jTdSC2lHdcVuD1aD5HZSpuFHQ/7SKSHJ5h19Wa47GXEjEncJbTdCA6zvj7gGPEim++/C0JDM1lj2A=
X-Received: by 2002:a67:db06:: with SMTP id z6mr4871414vsj.69.1559444862110; Sat, 01 Jun 2019 20:07:42 -0700 (PDT)
MIME-Version: 1.0
References: <155939048775.17273.13936885338207300192@ietfa.amsl.com> <CAMRcRGQpzMtmWYXEtq0oDp=1J52eXFWiGxX_vJLaOUuhNMWtGg@mail.gmail.com> <d77b3cbf-1e59-3602-91ff-d7afa058b3c4@cisco.com>
In-Reply-To: <d77b3cbf-1e59-3602-91ff-d7afa058b3c4@cisco.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Sun, 2 Jun 2019 08:37:29 +0530
Message-ID: <CAMRcRGS74-G_rQY66uAg2k9KKydX6UtNGWjPqH+qQLMYkjRx6g@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Cc: mmusic WG <mmusic@ietf.org>, Roman Shpount <roman@telurix.com>
Content-Type: multipart/alternative; boundary="0000000000000d8e16058a4e8d15"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Oz-ikPD6_aLdSPRKSFkZO0xK5Iw>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-30.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jun 2019 03:07:46 -0000

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

Hi Flemming
Good catch. will fix in the next version

Thanks
Suhas

On Sun, Jun 2, 2019 at 4:36 AM Flemming Andreasen <fandreas@cisco.com>
wrote:

> Thank you for the updated document Suhas. I have read through it and it
> generally looks good to me. One question though:
>
> Section 3.3.4 says:
> <quote>
>
>    Once the state of each check list is Completed, and if the agent is
>    the controlling agent, it nominates a candidate pair [RFC8445] and
>    checks for each data stream whether the nominated pair matches the
>    default candidate pair.  If there are one or more data streams with a
>    match, and the peer did not indicate support for the 'ice2' ice-
>    option, the controlling agent MUST generate a subsequent offer
>    (Section 3.4.1), in which the connection address, port and transport
>    protocol in the "c=" and "m=" lines associated with each data stream
>    match the corresponding local information of the nominated pair for
>    that data stream.
> </quote>
>
> In the second sentence, shouldn't it rather be if there is a line with a
> mismatch instead of a match ?
>
> Thanks
>
> -- Flemming
>
>
>
> On 6/1/19 8:02 AM, Suhas Nandakumar wrote:
>
> Version 30 address answerer ice-mismatch clarification suggestions
>
> Thanks
> Suhas
>
> On Sat, Jun 1, 2019 at 5:31 PM <internet-drafts@ietf.org> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Multiparty Multimedia Session Control WG
>> of the IETF.
>>
>>         Title           : Session Description Protocol (SDP) Offer/Answer
>> procedures for Interactive Connectivity Establishment (ICE)
>>         Authors         : Marc Petit-Huguenin
>>                           Suhas Nandakumar
>>                           Ari Keranen
>>         Filename        : draft-ietf-mmusic-ice-sip-sdp-30.txt
>>         Pages           : 42
>>         Date            : 2019-06-01
>>
>> Abstract:
>>    This document describes Session Description Protocol (SDP) Offer/
>>    Answer procedures for carrying out Interactive Connectivity
>>    Establishment (ICE) between the agents.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-30
>> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-30
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-30
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>
>

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

<div dir=3D"ltr"><div>Hi Flemming</div>Good catch. will fix in the next ver=
sion<br><div><br></div><div>Thanks</div><div>Suhas</div></div><br><div clas=
s=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Jun 2, 2019=
 at 4:36 AM Flemming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com">fa=
ndreas@cisco.com</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);pa=
dding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF">
    Thank you for the updated document Suhas. I have read through it and
    it generally looks good to me. One question though: <br>
    <br>
    Section 3.3.4 says:<br>
    &lt;quote&gt;<br>
    <pre style=3D"color:rgb(0,0,0);font-style:normal;font-variant-ligatures=
:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text=
-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-deco=
ration-style:initial;text-decoration-color:initial;white-space:pre-wrap">  =
 Once the state of each check list is Completed, and if the agent is
   the controlling agent, it nominates a candidate pair [RFC8445] and
   checks for each data stream whether the nominated pair matches the
   default candidate pair.  If there are one or more data streams with a
   match, and the peer did not indicate support for the &#39;ice2&#39; ice-
   option, the controlling agent MUST generate a subsequent offer
   (Section 3.4.1), in which the connection address, port and transport
   protocol in the &quot;c=3D&quot; and &quot;m=3D&quot; lines associated w=
ith each data stream
   match the corresponding local information of the nominated pair for
   that data stream.
&lt;/quote&gt;
</pre>
    In the second sentence, shouldn&#39;t it rather be if there is a line
    with a mismatch instead of a match ? <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming <br>
    <br>
    <br>
    <br>
    <div class=3D"gmail-m_-6613409998738561362moz-cite-prefix">On 6/1/19 8:=
02 AM, Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Version 30 address answerer ice-mismatch
        clarification suggestions
        <div><br>
        </div>
        <div>Thanks</div>
        <div>Suhas</div>
      </div>
      <br>
      <div class=3D"gmail_quote">
        <div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jun 1, 2019 at 5:31 P=
M
          &lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank"=
>internet-drafts@ietf.org</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"><br>
          A New Internet-Draft is available from the on-line
          Internet-Drafts directories.<br>
          This draft is a work item of the Multiparty Multimedia Session
          Control WG of the IETF.<br>
          <br>
          =C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0: Session Description Protocol (SDP)
          Offer/Answer procedures for Interactive Connectivity
          Establishment (ICE)<br>
          =C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0: Marc Petit-Huguenin<br>
          =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Suhas Nandakumar<br>
          =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Ari Keranen<br>
          =C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 draft-ietf-mmusic-ice-sip-sdp-30.txt<br>
          =C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0: 42<br>
          =C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 : 2019-06-01<br>
          <br>
          Abstract:<br>
          =C2=A0 =C2=A0This document describes Session Description Protocol=
 (SDP)
          Offer/<br>
          =C2=A0 =C2=A0Answer procedures for carrying out Interactive Conne=
ctivity<br>
          =C2=A0 =C2=A0Establishment (ICE) between the agents.<br>
          <br>
          <br>
          The IETF datatracker status page for this draft is:<br>
          <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice=
-sip-sdp/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/doc/draft-ietf-mmusic-ice-sip-sdp/</a><br>
          <br>
          There are also htmlized versions available at:<br>
          <a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-=
sdp-30" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/dr=
aft-ietf-mmusic-ice-sip-sdp-30</a><br>
          <a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mmusi=
c-ice-sip-sdp-30" rel=3D"noreferrer" target=3D"_blank">https://datatracker.=
ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-30</a><br>
          <br>
          A diff from the previous version is available at:<br>
          <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-=
ice-sip-sdp-30" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/r=
fcdiff?url2=3Ddraft-ietf-mmusic-ice-sip-sdp-30</a><br>
          <br>
          <br>
          Please note that it may take a couple of minutes from the time
          of submission<br>
          until the htmlized version and diff are available at <a href=3D"h=
ttp://tools.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</=
a>.<br>
          <br>
          Internet-Drafts are also available by anonymous FTP at:<br>
          <a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer=
" target=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
          <br>
          _______________________________________________<br>
          mmusic mailing list<br>
          <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.=
org</a><br>
          <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</=
a><br>
        </blockquote>
      </div>
    </blockquote>
    <br>
  </div>

</blockquote></div>

--0000000000000d8e16058a4e8d15--


From nobody Sat Jun  1 21:21:53 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE3B120059; Sat,  1 Jun 2019 21:21:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mmusic@ietf.org
Message-ID: <155944930400.24112.11116803058885166596@ietfa.amsl.com>
Date: Sat, 01 Jun 2019 21:21:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/pEMuerox0KcSZettCWbyLfhNQaU>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-msrp-usage-data-channel-11.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jun 2019 04:21:44 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : MSRP over Data Channels
        Authors         : Keith Drage
                          Maridi R. Makaraju (Raju)
                          Juergen Stoetzer-Bradler
                          Richard Ejzak
                          Jerome Marcon
                          Jose M. Recio
	Filename        : draft-ietf-mmusic-msrp-usage-data-channel-11.txt
	Pages           : 19
	Date            : 2019-06-01

Abstract:
   This document specifies how the Message Session Relay Protocol (MSRP)
   can be instantiated as a data channel sub-protocol, using the SDP
   offer/answer exchange-based generic data channel negotiation
   framework.  Two network configurations are documented: a WebRTC end-
   to-end configuration (connecting two MSRP over data channel
   endpoints), and a gateway configuration (connecting an MSRP over data
   channel endpoint with an MSRP over TCP or TLS endpoint).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-msrp-usage-data-channel/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-msrp-usage-data-channel-11
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-msrp-usage-data-channel-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-msrp-usage-data-channel-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Jun  1 21:37:42 2019
Return-Path: <jose@ch3m4.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A95651200B3 for <mmusic@ietfa.amsl.com>; Sat,  1 Jun 2019 21:37:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ch3m4.com header.b=G6OSmaSs; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Woe7QwdP
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 6-wb1I5jFOpc for <mmusic@ietfa.amsl.com>; Sat,  1 Jun 2019 21:37:38 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEDB7120059 for <mmusic@ietf.org>; Sat,  1 Jun 2019 21:37:37 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id D7C86B36; Sun,  2 Jun 2019 00:37:36 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Sun, 02 Jun 2019 00:37:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ch3m4.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm3; bh=7dzcAeBz0OVvqgaQjktLa1nB/we maRYqL5BMzPWTPxA=; b=G6OSmaSsdVp2X4t7AlWiY4umjlW4+wIExsx4d8FKklH nk0JLG5owbtsKZGScP46n4jPSVm9qEmDUffZiSoq25onfJc/S/km2SebnAIjjPEN +lE3uckKy5zruXB0kCzmt0AOn5S2LmyYwyfSx0bx2jiCTAWixbDZxoI1PYOK8uK0 IVfHYV3VeDhjqlczm7WK2Ipq4ZVIdP0PEXpaVMLhqRHchZPV8qouVt5rqP/vccCA FTjJmkdhiUAhckrpoGtKW4iYsh9WUuD2YaqML/okJGwKDePc7RXbqzXRBwSvHhOx mO+l2xtJBlhs3bhf9xg7+fs6b8RYszODXiOijGxOM+g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=7dzcAe Bz0OVvqgaQjktLa1nB/wemaRYqL5BMzPWTPxA=; b=Woe7QwdP2NYY/L+0rxIxIk lUaGjkLhyudraDOX2Oh2FXPXyWzyWhewYjEzHo5QgbsP3eORweatlyh5hVcMMrGm iUO+qnaqhUnKt3T0vcmXluHJc8kvi4zMLKbtw+dRHPpRUzh1Zn8ffgNef+VptfOk GZWOmINm09lFoWLe41D99kRGVdrCfcfbdgejxgqyonKnCnKX6OUd+PJtXVUnCpiB zZJeAHjrc53Um0DvssfLalzZGzVxrZcIXlaoyTp5rMoeCcelpKNHv4rO2Ro0nsOY JSku5XTPbU5hLg6AwzSkq2TKIGFUVazH226nqNY8EsmPia/Ux7PDMyRQwR7HTDZw ==
X-ME-Sender: <xms:j1LzXKfQJj6E9IFh_fVSrW1L5sAFHJU_6p1MCndVL34bXvnl8UuS4Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudefgedgkeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtsegrtderredtfeejnecuhfhrohhmpeflohhsvgcu ofcutfgvtghiohcuoehjohhsvgestghhfehmgedrtghomheqnecukfhppeduuddvrddule elrdduledtrdduledtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehjohhsvgestghhfehm gedrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:kFLzXN2ThV0BDlgDLbk_WIFEjtStAI4caQ47u4jtp3I33IZDMFnyrw> <xmx:kFLzXLh6RnyfIIfVBxZZOBB8jzoa2wxfKhlwd_sKndqLqTkAPinQ5Q> <xmx:kFLzXLSYYSLPCUIHvXIpzq_vYL66id7EyrZT1uN4-GvvmaqlWiKe_g> <xmx:kFLzXMYIYmHueU7ORYHERl805nVL5irmC3NBEqsCLXPRUG39Av75DQ>
Received: from [192.168.0.102] (unknown [112.199.190.190]) by mail.messagingengine.com (Postfix) with ESMTPA id BAE49380073; Sun,  2 Jun 2019 00:37:34 -0400 (EDT)
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <61D3ED98-04FA-4746-BCDE-37BD38907803@ericsson.com> <bc4535ee-7d65-e35e-5e9e-604446bf9d0f@ch3m4.com> <E24A4C62-CBCB-47F0-973F-0BF253AC4A31@ericsson.com> <b3e42338-f785-2bb3-6b29-63427f4ec75e@ch3m4.com> <AF298CE5-C2B8-41FD-A179-5030D8945187@ericsson.com>
From: Jose M Recio <jose@ch3m4.com>
Message-ID: <efd6c0a8-667c-7201-cb02-84f28357624b@ch3m4.com>
Date: Sun, 2 Jun 2019 12:37:31 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <AF298CE5-C2B8-41FD-A179-5030D8945187@ericsson.com>
Content-Type: multipart/alternative; boundary="------------6660AAB0DE563B2AC29B01EB"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Q-IZPyVX09hGcdxYZZ1Z3lJ4atw>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-msrp-usage-data-channel-10.txt - Comment on msrp-cema attribute
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jun 2019 04:37:41 -0000

This is a multi-part message in MIME format.
--------------6660AAB0DE563B2AC29B01EB
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Just posted updated draft based on your (and mail list) feedback. Main 
changes: removed cema attribute being optional, make it explicit that 
path shall not be used for transport negotiation neither for the direct 
end-to-end architecture nor for the GW one.

Following up on this comment:
> Regarding the GW, I think that also needs more text. For example, *IF* 
> the data channel MSRP client inserts multiple path attributes, will 
> the GW then copy paste those in the outgoing legacy MSRP message? I 
> assume it will, but there is very little detail on the GW procedures.
GW has two modes of operation: B2BUA, where there's nothing furthermore 
specified; and transport level gateway. In the second case, the draft 
already specifies that relays SHALL NOT be requested by the dc endpoint; 
and as the GW just operates at transport level, I think it's fair to 
leave any MSRP behavior (such as forwarding path attributes) as per MSRP 
specs.

What do you think?


On 31/05/19 18:51, Christer Holmberg wrote:
>
> What is the status regarding this?
>
> Regards,
>
> Christer
>
> *From: *Jose M Recio <jose@ch3m4.com>
> *Date: *Thursday, 25 April 2019 at 14.29
> *To: *Christer Holmberg <christer.holmberg@ericsson.com>, 
> "mmusic@ietf.org" <mmusic@ietf.org>
> *Subject: *Re: [MMUSIC] I-D Action: 
> draft-ietf-mmusic-msrp-usage-data-channel-10.txt - Comment on 
> msrp-cema attribute
>
> On 23/4/19 4:32 AM, Christer Holmberg wrote:
>
>     Keep in mind (and that should probably better described in the document) that the normal MSRP routing procedures don't apply. The MSRP messages will be routed in the data channel, which is established between the SIP peers (or whatever signaling protocol is used). I guess proxies and application servers can look at the top-most path attribute, but that is not going to be the primary routing input. I don't think the draft says anything about that - it just seems to assume that the data channel will end up in the intended MSRP peer.
>
>
> It indeed assumes that the data channel endpoint will be a MSRP peer, 
> either another endpoint or a MSRP GW. If that's not clear enough it 
> should be made more explicit.
>
> If the endpoint is a GW, messages can be relayed, similar to the 
> scenario where the connection to the GW is done using TLS, or 
> WebSockets, instead of dc.
>


--------------6660AAB0DE563B2AC29B01EB
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Just posted updated draft based on your (and mail list) feedback.
      Main changes: removed cema attribute being optional, make it
      explicit that path shall not be used for transport negotiation
      neither for the direct end-to-end architecture nor for the GW one.<br>
    </p>
    Following up on this comment:<br>
    <blockquote type="cite">Regarding the GW, I think that also needs
      more text. For example, *IF* the data channel MSRP client inserts
      multiple path attributes, will the GW then copy paste those in the
      outgoing legacy MSRP message? I assume it will, but there is very
      little detail on the GW procedures.<br>
    </blockquote>
    GW has two modes of operation: B2BUA, where there's nothing
    furthermore specified; and transport level gateway. In the second
    case, the draft already specifies that relays SHALL NOT be requested
    by the dc endpoint; and as the GW just operates at transport level,
    I think it's fair to leave any MSRP behavior (such as forwarding
    path attributes) as per MSRP specs. <br>
    <br>
    What do you think?<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 31/05/19 18:51, Christer Holmberg
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:AF298CE5-C2B8-41FD-A179-5030D8945187@ericsson.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 2.0cm 70.85pt 2.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style>
      <div class="WordSection1">
        <p class="MsoNormal"><span lang="EN-US">What is the status
            regarding this?<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">Regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">Christer<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
        <div style="border:none;border-top:solid #B5C4DF
          1.0pt;padding:3.0pt 0cm 0cm 0cm">
          <p class="MsoNormal"><b><span
                style="font-size:12.0pt;color:black">From: </span></b><span
              style="font-size:12.0pt;color:black">Jose M Recio
              <a class="moz-txt-link-rfc2396E" href="mailto:jose@ch3m4.com">&lt;jose@ch3m4.com&gt;</a><br>
              <b>Date: </b>Thursday, 25 April 2019 at 14.29<br>
              <b>To: </b>Christer Holmberg
              <a class="moz-txt-link-rfc2396E" href="mailto:christer.holmberg@ericsson.com">&lt;christer.holmberg@ericsson.com&gt;</a>, <a class="moz-txt-link-rfc2396E" href="mailto:mmusic@ietf.org">"mmusic@ietf.org"</a>
              <a class="moz-txt-link-rfc2396E" href="mailto:mmusic@ietf.org">&lt;mmusic@ietf.org&gt;</a><br>
              <b>Subject: </b>Re: [MMUSIC] I-D Action:
              draft-ietf-mmusic-msrp-usage-data-channel-10.txt - Comment
              on msrp-cema attribute<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p> </o:p></p>
        </div>
        <div>
          <pre>On 23/4/19 4:32 AM, Christer Holmberg wrote:<o:p></o:p></pre>
        </div>
        <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
          <pre>Keep in mind (and that should probably better described in the document) that the normal MSRP routing procedures don't apply. The MSRP messages will be routed in the data channel, which is established between the SIP peers (or whatever signaling protocol is used). I guess proxies and application servers can look at the top-most path attribute, but that is not going to be the primary routing input. I don't think the draft says anything about that - it just seems to assume that the data channel will end up in the intended MSRP peer.<o:p></o:p></pre>
        </blockquote>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
            <tt>It indeed assumes that the data channel endpoint will be
              a MSRP peer, either another endpoint or a MSRP GW. If
              that's not clear enough it should be made more explicit.</tt><br>
            <br>
            <tt>If the endpoint is a GW, messages can be relayed,
              similar to the scenario where the connection to the GW is
              done using TLS, or WebSockets, instead of dc.</tt></span>
          <o:p></o:p></p>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------6660AAB0DE563B2AC29B01EB--


From nobody Sun Jun  2 04:17:37 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CF1CA120041; Sun,  2 Jun 2019 04:17:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mmusic@ietf.org
Message-ID: <155947424976.21503.8756374820269494435@ietfa.amsl.com>
Date: Sun, 02 Jun 2019 04:17:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/RshAtKcCBhOPjRsArJPSS75ghxY>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-31.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jun 2019 11:17:30 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : Session Description Protocol (SDP) Offer/Answer procedures for Interactive Connectivity Establishment (ICE)
        Authors         : Marc Petit-Huguenin
                          Suhas Nandakumar
                          Ari Keranen
	Filename        : draft-ietf-mmusic-ice-sip-sdp-31.txt
	Pages           : 42
	Date            : 2019-06-02

Abstract:
   This document describes Session Description Protocol (SDP) Offer/
   Answer procedures for carrying out Interactive Connectivity
   Establishment (ICE) between the agents.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-31
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-31

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-31


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Jun  3 07:37:02 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 718B11202BB; Mon,  3 Jun 2019 07:36:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NAheBa3GoRsM; Mon,  3 Jun 2019 07:36:50 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 585711202B5; Mon,  3 Jun 2019 07:36:38 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x53EaTgM016864 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 3 Jun 2019 10:36:30 -0400
To: Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
Cc: draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
References: <155907213212.25802.10923362703417281306.idtracker@ietfa.amsl.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <da24d89f-79cc-3fcc-aaad-4753cc552b3b@alum.mit.edu>
Date: Mon, 3 Jun 2019 10:36:29 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <155907213212.25802.10923362703417281306.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/X77vpQZU63L_QqGnf6CR8foRdhI>
Subject: Re: [MMUSIC] Alissa Cooper's Discuss on draft-ietf-mmusic-rfc4566bis-35: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2019 14:36:53 -0000

Alissa,

On 5/28/19 3:35 PM, Alissa Cooper via Datatracker wrote:

> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> Section 8.2.8:
> 
> "In the RFC specifications that register new values for SDP "media",
>     "proto", "fmt", "bwtype", "nettype", and "addrtype" parameters, the
>     authors MUST include the following information for IANA to place in
>     the appropriate registry:"
> 
> It doesn't look like all the fields that are listed after this text actually
> appear in the registries. For some of these I don't see why the information
> would be put into the registries (e.g., contact name, contact email address,
> since those appear in the RFCs themselves). I think this needs to be clarified.

OK. There are two things going on here: the information that must be 
provided when registering a new value, and then which of those items 
need to appear in the registry. The distinction isn't clear.

For items where the registration requirements are less that "document 
required" the information must be in the registry since there is no 
place else for it to appear. But when a document is required then in 
principle the name of the item and a reference to the document is all 
that is *necessary* in the registry, and any additional information is 
for convenience of access.

I've found that this distinction often isn't clearly made, especially in 
older stuff.

I can look into this further for all the SDP registries.

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Section 5.1:
> 
> Since both this document and RFC 4566 specify version 0 and this version makes
> semantic and syntactic changes, does that mean the protocol versioning is
> non-functional? Or if not, what kinds of changes would require a new version
> number?

It appears that the version field was included in SDP without much 
thought. There are no normative procedures defined for how to deal with 
differing version numbers, so I expect that the result of attempting to 
change the version number is unknown. Probably many implementations 
would not notice, while some might reject a version other than zero.

Given that we have gone 20 years without a version number change, I 
wouldn't attempt one now. Along the way the rule with changes has always 
been to do them in a backward compatible way. AFAIK that is true with 
the changes in this document as well.

> Section 7:
> 
> "Use of the "k=" line poses a significant security risk, since it
>     conveys session encryption keys in the clear.  SDP MUST NOT be used
>     to convey keying material, unless it can be guaranteed that the
>     channel over which the SDP is delivered is both private and
>     authenticated.  Moreover, the "k=" line provides no way to indicate
>     or negotiate cryptographic key algorithms.  As it provides for only a
>     single symmetric key, rather than separate keys for confidentiality
>     and integrity, its utility is severely limited.  The "k=" line MUST
>     NOT be used, as discussed in Section 5.12."
> 
> It's odd to me that this text was retained from RFC 4566 as-is, except for the
> last sentence. I would have expected this to lead with something like 'Use of
> the "k=" line is obsolete due to security risk.' And then perhaps some of the
> rest of the text could remain by way of explanation why it was obsoleted.

IIRC the existing text was the result of security review comments and 
subsequent discussions. Do you want us to revisit those?

> Section 8.2.8:
> 
> "IANA may refer any registration to the IESG for review, and may
>     request revisions to be made before a registration will be made."
> 
> This is trivially true and would be better left out, using RFC 8126 as the
> definitive guidance instead.

I never noticed this. I checked, and it has been present in exactly this 
form since RFC2327 in 1998. I don't recall seeing any language like this 
in any other IANA considerations section. I'm inclined to simply remove it.

	Thanks,
	Paul


From nobody Mon Jun  3 10:24:59 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0021D1206F6; Mon,  3 Jun 2019 10:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M3xLjBzBVXrX; Mon,  3 Jun 2019 10:24:47 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B516F12072D; Mon,  3 Jun 2019 10:24:27 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x53HOIcC029222 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 3 Jun 2019 13:24:19 -0400
To: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic@ietf.org
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu>
Date: Mon, 3 Jun 2019 13:24:18 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/1In-h8K6fRKUtwig_ST2Yvd66eg>
Subject: Re: [MMUSIC] Alexey Melnikov's No Objection on draft-ietf-mmusic-rfc4566bis-35: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2019 17:24:50 -0000

Alexey,

Thank you for your careful review and comments. I've included some 
followup for you inline below.

On 5/30/19 8:50 AM, Alexey Melnikov via Datatracker wrote:
> Alexey Melnikov has entered the following ballot position for
> draft-ietf-mmusic-rfc4566bis-35: No Objection

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thank you for a well written document. Below are mostly nits, but I think they
> will help first time implementors.
> 
> In Section 1:
> 
> electronic mail using the MIME   extensions [RFC5322]
> 
> This needs another reference for MIME. E.g. RFC 2045.

I don't understand. This paragraph is referencing examples of protocols 
that can be used to *transport* SDP. RFC5322 references the mail message 
format that would be used to encapsulate SDP if it were transported via 
email. (Though it doesn't actually mention the *transport* protocols 
used for mail messages.)

ISTM that it is the containing protocols that should reference rfc2045. 
RFC5322 does so, and so says how to carry SDP in mail messages. SIP is 
itself effectively an extension to RFC2045 though it doesn't say so.

I don't object to adding a reference to RFC2045, I just don't know how 
to fit it in appropriately.

> In 3.1 “media types” need a Normative reference.
> 
> In 4.1:
> 
>   Some media types may   redefine this behavior, but this is NOT RECOMMENDED
>   since it complicates implementations (including middleboxes that must parse
>   the addresses to open Network Address Translation (NAT) or firewall
>   pinholes).
> 
> Can you give an example of such redefinition?

IIUC this is simply an escape hatch for unusual types of media. 
Currently there are no *media types* that redefine this. In reality, the 
case where address and port are impacted is with <nettype> and 
<addrtype>s that don't have the same notion of address and port. For 
instance, RFC7195 defines a way of specifying circuit switched PSTN 
connections, using <nettype> PSTN and <addrtype> E164. These are used 
with existing <media> audio. There is no notion of port here. To comply 
with syntax requirements is calls for using port 9.

I will try to rework the text here to explain the situation more generally.

> In 4.3: the first mention of URI needs a Normative Reference.

OK

> In 4.5: ISO 8859-1 needs a reference.

OK.

> In 5.3:
> 
>     The "s=" line MUST NOT be empty and SHOULD contain ISO 10646
>     characters (but see also the "a=charset" attribute)
> 
> Does this mean that it is affected by a=charset?
> Why SHOULD?
> The text is 5.4 is better, if the intention is the same.

I agree. Will change.

> In 5.5:
> 
> “WWW clients“
> 
> URIs are used by many types of clients. Suggest dropping “WWW”.

OK. Another legacy from 20 years ago.

> In 6.10:
> 
>     Note that a character set specified MUST still prohibit the use of
>     bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
> 
> This doesn’t actually say what you intended. None of the common charsets
> prohibit these bytes. I think you meant that when using such charsets, these
> characters MUST NOT be used in values.

Agree. Will change.

We have recently had some discussion of a=charset. It seems that the 
intent is lost in time and we are left trying to infer it.

I don't recall what the state of character set definitions was in 1998 
when this was first published. But it appears that they got carried away 
and over-generalized. It is easy to understand how one might choose to 
use ISO 8859-1 rather than UTF-8 since they are closely related and 
byte-oriented. But it is unclear how one might use some other registered 
charsets, such as EBCDIC, or other encodings of ISO 10646, such as UTF-16.

The bottom line is that use of alternate charsets other than 8859-1 is 
underspecified. We considered revamping the definition of charset, but 
didn't want to open that can of worms, since in practice it isn't an issue.

> In 6.11:
> 
>     The "sdplang" attribute value must be a single [RFC5646] language tag
>     in the US-ASCII subset of UTF-8
> 
> Is “fr-ca” allowed here?

I don't know what the original authors had in mind, but I assume so.

> Can you point to a specific ABNF in RFC 5646?

This section already says:

              sdplang-value = Language-Tag
              ; Language-Tag defined in RFC5646

Doesn't that cover it?

> Also, “in the US-ASCII subset of UTF-8“ is either redundant or confusing, as
> language tags are always in U-ASCII.

I'll take it out.

> In 8.1:
> 
>    Encoding considerations:         SDP files are primarily UTF-8 format text
> 
> This is not correct use of this field. I think you should say “8bit” or
> “binary” here.

OK. It appears that 8bit is appropriate here.

> In 8.2.2:
> 
>     Registrations MUST reference an RFC describing the protocol.
>     Such an RFC MAY be Experimental or Informational, although it is
>     preferable that it be Standards Track.
> 
> I just want to confirm that an Independent Stream RFC is allowed here?

I don't believe there is any intent to exclude this.


From nobody Mon Jun  3 11:44:37 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33848120435; Mon,  3 Jun 2019 11:44:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XRfeHzkM8NPP; Mon,  3 Jun 2019 11:44:24 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93E49120427; Mon,  3 Jun 2019 11:44:24 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x53IiJhC002653 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 3 Jun 2019 14:44:20 -0400
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic@ietf.org
References: <155922686313.22081.12209259015077736906.idtracker@ietfa.amsl.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <df7509c8-5bba-fcc2-5d75-3cc179266cf8@alum.mit.edu>
Date: Mon, 3 Jun 2019 14:44:18 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <155922686313.22081.12209259015077736906.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ZhABjs84OiQ7IUglDZuod1Q-nMk>
Subject: Re: [MMUSIC] Benjamin Kaduk's No Objection on draft-ietf-mmusic-rfc4566bis-35: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2019 18:44:28 -0000

Benjamin,

Thank you for your comments. I've included followup inline below.

On 5/30/19 10:34 AM, Benjamin Kaduk via Datatracker wrote:
> Benjamin Kaduk has entered the following ballot position for
> draft-ietf-mmusic-rfc4566bis-35: No Objection

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I reviewed the diff from RFC 4566 but didn't make it quite all the way
> through the full document itself.  What I did find in that partial read
> suggests that a full read-through by the authors may find some lingering
> stale language or minor internal inconsistencies.

There really hasn't been an attempt to thoroughly remove stale (dated) 
language. Fundamentally this is a 21 year old document that has been 
tidied up a bit. Anyone that started over today to define something new 
for the same purpose would surely define something very different. We've 
only been trying to fix areas where there has been confusion or 
ambiguity has been found, or where new concerns (e.g., security) have 
needed to be addressed.

> Another broad topic (with more comments throughout) is that an early and
> clear discussion of time representation may be helpful, and arguably
> does not need to refer to NTP time at all.  (This is especially so when
> we refer to "NTP time format" and RFC 5905, which lists three
> formats, none of which have a straightforward translation to numeric
> strings without fraction part.)

Good point. It appears that the intent is for the value to be seconds 
since the beginning of NTP Era 0 ("0 h 1 January 1900 UTC"). We can 
either reference that directly, or, since that starting point isn't 
likely to be changed in NTP, simply state it. Which of those would you 
prefer?

> Section 4
> 
>                                     SDP is primarily intended for use in
>     an internetwork, although it is sufficiently general that it can
>     describe multimedia conferences in other network environments.  [...]
> 
> nit(?): this verbiage ("internetwork") feels quite dated.

Does "... primarily intended for use with Internet protocols, although 
..." work for you?

> Section 4.1
> 
>                                                      Some media types may
>     redefine this behavior, but this is NOT RECOMMENDED since it
>     complicates implementations (including middleboxes that must parse
>     the addresses to open Network Address Translation (NAT) or firewall
>     pinholes).
> 
> (Similarly for "firewall pinholes".)

Do you have a suggestion. This still seems ok to me.

> Section 4.3
> 
> The usual security considerations about (potentially) referencing remote
> content would seem to apply.  Perhaps a RFC 3986 reference (or more)
> would be appropriate.

Will adding a reference to [RFC3986] be sufficient?

> Section 4.6
> 
> Perhaps we should mention here that this categorization mechanism is
> deprecated/obsolete?

Section 4.6??? Did you mean 4.4?

Since a=cat has been declared obsolete, I'm inclined to simply remove 
section 4.4.

> Section 5
> 
>     An SDP description is entirely textual.  SDP field names and
>     attribute names use only the US-ASCII subset of UTF-8 [RFC3629], but
>     textual fields and attribute values MAY use the full ISO 10646
>     character set in UTF-8 encoding, or some other character set defined
>     by the "a=charset:" attribute.  [...]
> 
> nit: here (and in Section 4.4 just above) may be the only times we
> include the colon when discussing an "a=" attribute; consistency would
> seem to suggest removing the colons.

OK.

>                                    However, since SDP may be used in
>     environments where the maximum permissible size of a session
>     description is limited, the encoding is deliberately compact.  Also,
>     since descriptions may be transported via very unreliable means or
>     damaged by an intermediate caching server, the encoding was designed
>     with strict order and formatting rules so that most errors would
>     result in malformed session descriptions that could be detected
>     easily and discarded.  This also allows rapid discarding of encrypted
>     session descriptions for which a receiver does not have the correct
>     key.
> 
> I don't really see why the "rapid discarding" property follows from the
> compactness of the encoding, when the correct key for the encrypted
> description is not known.

I'm inclined to simply remove that last sentence. I'd remove the whole 
paragraph, but keeping it may provide insight into why the protocol is 
as weird and crufty as it is.

> Section 5.x
> 
> It's interesting to note that while the SDP attributes (Sections 6.x)
> got ABNF constructions for their values, the type descriptions here
> are still presented in a somewhat informal syntax (that, e.g., relies on
> implicitly stating that fields are whitespace-separated).

It is an interesting point. The best rationale I can give is that *not* 
having ABNF got to be a serious problem for attributes, because there 
are a lot of them, and new ones get defined regularly (with complex 
syntax) and the syntax was often recognized as being ambiguous. So we 
wanted to demand ABNF for future extensions, and felt we should make the 
ones defined in this document comply with that.

OTOH, the other fields are revised/extended much more rarely, so it 
hasn't been a problem. And so there is much less motivation to "rock the 
boat" by changing the manner of defining them.

> Section 5.2
> 
>     <sess-id>  is a numeric string such that the tuple of <username>,
>        <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a
>        globally unique identifier for the session.  The method of <sess-
>        id> allocation is up to the creating tool, but it has been
>        suggested that a Network Time Protocol (NTP) format timestamp be
>        used to ensure uniqueness [RFC5905].
> 
> (et seq) There is not a single "NTP format timestamp"; RFC 5905 provides
> three different formats.  If any of the three is fine, that should be
> stated, and if a single distinguished one is preferred, that should also
> be stated.
> Furthermore, the three formats all include multiple fields and not a
> rule for presenting them as a "numeric string" as described here, which
> on the face of it seems to exclude fractions.  ("numeric string" does
> not seem to be specifically defined by this document.)

I'm inclined to change this to suggest the same format as used for t=, 
as discussed above.

Because the values of these fields is only loosely specified there is no 
*guarantee* that the combination provides the intended uniqueness. But 
there are so many implementations deployed that it would be impossible 
to redefine to make such a guarantee. In practice it isn't a problem - 
things are unique *enough*.

> Section 5.3
> 
>     The "s=" line MUST NOT be empty and SHOULD contain ISO 10646
>     characters (but see also the "a=charset" attribute).  [...]
> 
> Is this perhaps intended to be "SHOULD only contain"?
> (Similarly in following subsections.)

I received other comments on this and will work on it.

> Section 5.9
> 
>     The first and second sub-fields of the time-field give the start and
>     stop times, respectively, for the session.  These values are the
>     decimal representation of Network Time Protocol (NTP) time values in
>     seconds since 1900 [RFC5905].  To convert these values to UNIX time
>     (UTC), subtract decimal 2208988800.
> 
> Looking at the time formats listed in RFC 5905, one perhaps wonders if
> the values used by SDP are more appropriately described informally as
> just "seconds since the Unix epoch" without specific reference to NTP
> (both here and elsewhere in the document).
> 
>     NTP timestamps are elsewhere represented by 64-bit values, which wrap
>     sometime in the year 2036.  [...]
> 
> I don't understand what this is referring to.  Is this perhaps the "32
> bits of seconds and 32 bits of fraction" format, which suffers from the
> y2038 (note '8', not '6') problem?

See my earlier comments.

> Section 6.2
> 
> Perhaps "this was to assist" would be more fitting, given the obsolete
> nature of a=keywds.

OK.

> Section 6.9
> 
>     This specifies the type of the multimedia conference.  Suggested
>     values are "broadcast", "meeting", "moderated", "test", and "H332".
> 
> nit: I don't think these are "suggested" values; they are the only ones
> allowed by the ABNF.

Good point. Will fix.

>     "recvonly" should be the default for "type:broadcast" sessions,
>     "type:meeting" should imply "sendrecv", and "type:moderated" should
>     indicate the use of a floor control tool and that the media tools are
>     started so as to mute new sites joining the multimedia conference.
> 
> There seems to be redundancy here with the "SHOULD" in Section 6.7 about
> "sendrecv" being the default for non-broadcast non-H322 sessions.

Thanks for pointing this out. This needs work, since IMO it is wrong to 
use "default" here. At best these are recommendations for what the 
creator of and SDP body should do.

> Section 6.11
> 
> Is it intentional to lose the language about "order of importance" of
> multiple languages?

Yes.

This is describing what is used in the text of the SDP body. It isn't 
saying anything about future use. RFC8373 defines 'hlang-send' and 
'hlang-recv' for indicating preferences of languages to use in media.

	Thanks,
	Paul


From nobody Mon Jun  3 12:54:52 2019
Return-Path: <barryleiba@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8864712083A; Mon,  3 Jun 2019 12:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YN1eIgYu9BTq; Mon,  3 Jun 2019 12:54:41 -0700 (PDT)
Received: from mail-it1-f172.google.com (mail-it1-f172.google.com [209.85.166.172]) (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 DFE76120837; Mon,  3 Jun 2019 12:54:40 -0700 (PDT)
Received: by mail-it1-f172.google.com with SMTP id s16so28616413ita.2; Mon, 03 Jun 2019 12:54:40 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=uDhtfS2jPxdnQoOHrn9hAKzV/ILvAuyEJ11dJjaUt3g=; b=a/Di3TlmykFoOrv/cYpwwPn5AR2mCa3PPv0iVF6EmZXfTMC3i2buyKIzb5TqTf/Dmf zH2EdnP8+YIO7J0TQ9Zy5hUY1d0eVjPaF2oJejju+Rf/q9M/FLeaAlx4KDA4OS7ESLZJ qsWZR05vL7MEhyihgJdtWBwZr8wFXg2Chu/D4cD9F4XsagWpwsMmTecaGGsxEjLqCXBC RdekGMr9145Jpi0R9SlZCeDg6Ss6oW2aPknaAKTtfsDlhrhL2bcj2dILesz/19r+Au/1 fuaz1V9aAvOk+WQ6uxygJUHgmeQGO1BLgjOBjxo1tcMOpR/D+CjagIVDeVrZNFunjq1a PEPQ==
X-Gm-Message-State: APjAAAUugiNV9sBX7HUhHryVP3Xke/dQu11vOImZURGQtetI4uIQvFFk hglKQcgR9uHL2zKY+9hFHZHZtKwP1DH/FhnvOKQ=
X-Google-Smtp-Source: APXvYqyk94c5W91qoLJ1uQ03z06YyoTrh8NbaoE4k5bwU7sbRnButuZ+6YbXD4jvt4xH1zm6A11teFTNChl9g6Rrgsk=
X-Received: by 2002:a24:47c3:: with SMTP id t186mr2465581itb.86.1559591679829;  Mon, 03 Jun 2019 12:54:39 -0700 (PDT)
MIME-Version: 1.0
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu>
In-Reply-To: <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 3 Jun 2019 21:54:28 +0200
Message-ID: <CALaySJJjwG26NLCJqFdo2yW_JhYCYbY+ADHENa490XqM539U2A@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>,  Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org,  draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/iTyjSpfstzfm7XeZG6TN7aHDH5U>
Subject: Re: [MMUSIC] Alexey Melnikov's No Objection on draft-ietf-mmusic-rfc4566bis-35: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2019 19:54:43 -0000

Hi, Paul.  Sticking my oar in with Alexey's here, just on a couple of items=
:

> > In Section 1:
> >
> > electronic mail using the MIME   extensions [RFC5322]
> >
> > This needs another reference for MIME. E.g. RFC 2045.
>
> I don't understand. This paragraph is referencing examples of protocols
> that can be used to *transport* SDP. RFC5322 references the mail message
> format that would be used to encapsulate SDP if it were transported via
> email. (Though it doesn't actually mention the *transport* protocols
> used for mail messages.)
>
> ISTM that it is the containing protocols that should reference rfc2045.
> RFC5322 does so, and so says how to carry SDP in mail messages. SIP is
> itself effectively an extension to RFC2045 though it doesn't say so.

Alexey's point is that you explicitly mention "MIME extensions" and
don't provide a reference for it.  I'll go a bit farther to say that
you're not just talking about message *format* here, but also SMTP as
the transport (more correctly, application-layer) protocol, yes?  So
this should say something more like, "electronic mail [RFC5321] using
the MIME extensions [RFC2045]".  I don't think you need 5322, because
822 is cited by 2045, and that is obsoleted by 2822, and that by 5322.
But I think you do need to cite SMTP and MIME.

> > In 6.10:
> >
> >     Note that a character set specified MUST still prohibit the use of
> >     bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
> >
> > This doesn=E2=80=99t actually say what you intended. None of the common=
 charsets
> > prohibit these bytes. I think you meant that when using such charsets, =
these
> > characters MUST NOT be used in values.

Adding to what Alexey says, and maybe clarifying a bit: Character set
and encoding are different things.  The character set is the
abstraction of the characters used, and the encoding is how they're
represented.  The encoding is what creates the bytes on the wire.  One
problem is that "ASCII" refers to both, so it's confusing.  But with
Unicode, "Unicode" is the character set and "UTF-8" is (usually) the
encoding.

But your point here is that the three byte values you list MUST NOT
appear in the string, and that has nothing to do with the character
set or the encoding.  Those three bytes are prohibited.

You say that quite well in Section 5:

   Text-containing fields such as the session-name-field and
   information-field are octet strings that may contain any octet with
   the exceptions of 0x00 (Nul), 0x0a (ASCII newline), and 0x0d (ASCII
   carriage return).

... and in 5.13:

   Attribute values are octet strings, and MAY use any octet value
   except 0x00 (Nul), 0x0A (LF), and 0x0D (CR).

But in 6.10 I think you want something more like this:

OLD
   Note that a character set specified MUST still prohibit the use of
   bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).  Character sets requiring
   the use of these characters MUST define a quoting mechanism that
   prevents these bytes from appearing within text fields.
NEW
   Note that the restriction specified in Section 5 applies: these strings
   MUST NOT contain the bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
   Character encodings that use these bytes MUST define a quoting
   mechanism that prevents these bytes from appearing within the text
   strings.
END

> I don't recall what the state of character set definitions was in 1998
> when this was first published. But it appears that they got carried away
> and over-generalized. It is easy to understand how one might choose to
> use ISO 8859-1 rather than UTF-8 since they are closely related and
> byte-oriented. But it is unclear how one might use some other registered
> charsets, such as EBCDIC, or other encodings of ISO 10646, such as UTF-16=
.
>
> The bottom line is that use of alternate charsets other than 8859-1 is
> underspecified. We considered revamping the definition of charset, but
> didn't want to open that can of worms, since in practice it isn't an issu=
e.

I appreciate that, and I think this isn't the place to tackle that.
So we just need to get the text here to accurately reflect what you're
trying to say.

Hoping to be helpful,
Barry


From nobody Mon Jun  3 13:17:32 2019
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E127120843 for <mmusic@ietfa.amsl.com>; Mon,  3 Jun 2019 13:17:32 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sGobL3sCN38o for <mmusic@ietfa.amsl.com>; Mon,  3 Jun 2019 13:17:30 -0700 (PDT)
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (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 F029112083E for <mmusic@ietf.org>; Mon,  3 Jun 2019 13:17:29 -0700 (PDT)
Received: by mail-pg1-x52b.google.com with SMTP id d30so8904740pgm.7 for <mmusic@ietf.org>; Mon, 03 Jun 2019 13:17:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=IvAqeC/53r8en2Ed5ENgaFJpVNtcUGdUDF9JZY5eQ+o=; b=nJtPWpQQH2VGsJL9L5G5ueT7hm1PXpukHtUCC3z6CKCFa7/gTj3uFCfDSTgcaS9i0a epzY67rs96GtZrGRORbf0Pg6tTSNR1DsRJUiTdU1fQHEalZ3c6yse6SS00d5KVb7GFjB JWQzc+i58egW6mMVCmrOM9h8X35/lvK39PVDuptbejx4dviLMEmOuriHcaj8GGBoVT0W f5WdVYT6YcdmvhMknbiB5ozjNCCVewefqv0wn+u2LzhRXxPWrEy++qiidAt9q0yOAbpP OYyMx8ubRDN31aT9wmIWuLizsqBkUaZ5exltbEgjfktiuO1t0AGB+28Q4AQ5uG3cPiOc 4WyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=IvAqeC/53r8en2Ed5ENgaFJpVNtcUGdUDF9JZY5eQ+o=; b=LYW6xFMIcVel/MkXw3hJavG1JAPnCwauixyds/kVKGbS+0AgOrSo//AT9zTlI5/nQA Wq/valq8tTbi5fHqJjYSz5HQKFRB/EERb9dazJyCpHbrad53XSCChUQH7seofjmKGPL7 NzfQXTgwrOT3vgsokAqzWi9ah8nkVAR6uykg7tmS6SewyIPuxnQZ2//xercDpGdcTs6l b9MEETK5QS6y4seZxz90SWFI0SBhmtm3MkNOuznLQJz6UgZK4LtTQLAnu3YlBrbEwJ2J dA40WAPXREVLFjph9M9h6E0/PruyCj0o7P6zbfuubvOLxqcmrukm3uAXy8IbA4q9XJ8y dlsg==
X-Gm-Message-State: APjAAAX8ESzI3VAvqU8DhD6qczOf0N6OTkhx+8bSwCcQmCLU3vHXdHyV he6bZQCdJLbKTvIviKaTvuhyegzyfqA=
X-Google-Smtp-Source: APXvYqwymtr1tXTvqW2lJ3IhnqHBeVCbAHDTcHFDBw9FUkVmi4YCODfKwRplLcU0YXJR3SrXsl9FUA==
X-Received: by 2002:a17:90a:380d:: with SMTP id w13mr17536509pjb.138.1559593049265;  Mon, 03 Jun 2019 13:17:29 -0700 (PDT)
Received: from mail-pf1-f179.google.com (mail-pf1-f179.google.com. [209.85.210.179]) by smtp.gmail.com with ESMTPSA id y7sm28669856pja.26.2019.06.03.13.17.28 for <mmusic@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Mon, 03 Jun 2019 13:17:28 -0700 (PDT)
Received: by mail-pf1-f179.google.com with SMTP id u22so11244426pfm.3 for <mmusic@ietf.org>; Mon, 03 Jun 2019 13:17:28 -0700 (PDT)
X-Received: by 2002:aa7:8193:: with SMTP id g19mr26168502pfi.162.1559593048195;  Mon, 03 Jun 2019 13:17:28 -0700 (PDT)
MIME-Version: 1.0
References: <155947424976.21503.8756374820269494435@ietfa.amsl.com>
In-Reply-To: <155947424976.21503.8756374820269494435@ietfa.amsl.com>
From: Roman Shpount <roman@telurix.com>
Date: Mon, 3 Jun 2019 16:17:17 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuEp8pK9G042QTpRvLG3CsW6T8vtDP8G5C2VVzke4RzKg@mail.gmail.com>
Message-ID: <CAD5OKxuEp8pK9G042QTpRvLG3CsW6T8vtDP8G5C2VVzke4RzKg@mail.gmail.com>
To: mmusic WG <mmusic@ietf.org>, Suhas Nandakumar <suhasietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000a1c929058a710d9d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/SmuTYY67ERmf7V-5ESHV0gXX3rU>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-31.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2019 20:17:32 -0000

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

Hi Suhas,

I think there is an error introduced in this version. Old language was

It indicates that the offer arrived with a default destination for a media
component that didn't have a corresponding candidate attribute.

New language:

It indicates that the *offerer* arrived with a default destination for a
media component that didn't have a corresponding candidate attribute.

Since this language talks about session description (offer), old language
was correct. The offerer (an ICE agent) did not actually arrive anywhere.

If you want, you can make this more clear by changing this sentence to the
following:

It indicates, to the offerer, that the other party received a session
description with a default destination for a media component that didn't
have a corresponding candidate attribute.

Regards,
_____________
Roman Shpount


On Sun, Jun 2, 2019 at 7:18 AM <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multiparty Multimedia Session Control WG
> of the IETF.
>
>         Title           : Session Description Protocol (SDP) Offer/Answer
> procedures for Interactive Connectivity Establishment (ICE)
>         Authors         : Marc Petit-Huguenin
>                           Suhas Nandakumar
>                           Ari Keranen
>         Filename        : draft-ietf-mmusic-ice-sip-sdp-31.txt
>         Pages           : 42
>         Date            : 2019-06-02
>
> Abstract:
>    This document describes Session Description Protocol (SDP) Offer/
>    Answer procedures for carrying out Interactive Connectivity
>    Establishment (ICE) between the agents.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-31
> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-31
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-31
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">Hi Suhas,<div><br></div><div>I think there is an error int=
roduced in this version. Old language was</div><div><br></div><div>It indic=
ates that the offer arrived with a default destination for a media componen=
t that=C2=A0didn&#39;t have a corresponding candidate attribute.</div><div>=
<br></div><div>New language:</div><div><br></div><div>It indicates that the=
 <b>offerer</b> arrived with a default destination for a media component th=
at=C2=A0didn&#39;t have a corresponding candidate attribute.=C2=A0</div><di=
v><br></div><div>Since this language talks about session description (offer=
), old language was correct. The offerer (an ICE agent) did not actually ar=
rive anywhere.</div><div><br></div><div>If you want, you can make this more=
 clear by changing this sentence to the following:</div><div><br></div><div=
>It indicates, to the offerer, that the other party received a session desc=
ription with a default destination for a media component that=C2=A0didn&#39=
;t have a corresponding candidate attribute.=C2=A0=C2=A0</div><div><br></di=
v><div>Regards,<br clear=3D"all"><div><div dir=3D"ltr" class=3D"gmail_signa=
ture" data-smartmail=3D"gmail_signature">_____________<br>Roman Shpount</di=
v></div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Sun, Jun 2, 2019 at 7:18 AM &lt;<a href=3D"mailto:inte=
rnet-drafts@ietf.org">internet-drafts@ietf.org</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Multiparty Multimedia Session Control WG o=
f the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Session Description Protocol (SDP) Offer/Answer procedures for Interactive=
 Connectivity Establishment (ICE)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Marc=
 Petit-Huguenin<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Suhas Nandakumar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ari Keranen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mmusic-ice-sip-sdp-31.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 42<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2019-06-02<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes Session Description Protocol (SDP) Off=
er/<br>
=C2=A0 =C2=A0Answer procedures for carrying out Interactive Connectivity<br=
>
=C2=A0 =C2=A0Establishment (ICE) between the agents.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/"=
 rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draf=
t-ietf-mmusic-ice-sip-sdp/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-31" re=
l=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-m=
music-ice-sip-sdp-31</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-=
sdp-31" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d=
oc/html/draft-ietf-mmusic-ice-sip-sdp-31</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-ice-sip-sd=
p-31" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?url=
2=3Ddraft-ietf-mmusic-ice-sip-sdp-31</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div>

--000000000000a1c929058a710d9d--


From nobody Mon Jun  3 13:18:14 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E59C120843; Mon,  3 Jun 2019 13:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dbBC7H-7AzS8; Mon,  3 Jun 2019 13:18:11 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EA8C12083E; Mon,  3 Jun 2019 13:18:11 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x53KI1q3009520 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 3 Jun 2019 16:18:02 -0400
To: Barry Leiba <barryleiba@computer.org>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic@ietf.org
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <CALaySJJjwG26NLCJqFdo2yW_JhYCYbY+ADHENa490XqM539U2A@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <44efd3cc-0bc4-578f-8e9f-564b1a451a78@alum.mit.edu>
Date: Mon, 3 Jun 2019 16:18:00 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <CALaySJJjwG26NLCJqFdo2yW_JhYCYbY+ADHENa490XqM539U2A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/nR61r0hj1lRTZcFgY9yj-tDXZCQ>
Subject: Re: [MMUSIC] Alexey Melnikov's No Objection on draft-ietf-mmusic-rfc4566bis-35: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2019 20:18:13 -0000

Barry,

Thank you for sticking your oar in. I think I can use your text.

	Thanks,
	Paul

On 6/3/19 3:54 PM, Barry Leiba wrote:
> Hi, Paul.  Sticking my oar in with Alexey's here, just on a couple of items:
> 
>>> In Section 1:
>>>
>>> electronic mail using the MIME   extensions [RFC5322]
>>>
>>> This needs another reference for MIME. E.g. RFC 2045.
>>
>> I don't understand. This paragraph is referencing examples of protocols
>> that can be used to *transport* SDP. RFC5322 references the mail message
>> format that would be used to encapsulate SDP if it were transported via
>> email. (Though it doesn't actually mention the *transport* protocols
>> used for mail messages.)
>>
>> ISTM that it is the containing protocols that should reference rfc2045.
>> RFC5322 does so, and so says how to carry SDP in mail messages. SIP is
>> itself effectively an extension to RFC2045 though it doesn't say so.
> 
> Alexey's point is that you explicitly mention "MIME extensions" and
> don't provide a reference for it.  I'll go a bit farther to say that
> you're not just talking about message *format* here, but also SMTP as
> the transport (more correctly, application-layer) protocol, yes?  So
> this should say something more like, "electronic mail [RFC5321] using
> the MIME extensions [RFC2045]".  I don't think you need 5322, because
> 822 is cited by 2045, and that is obsoleted by 2822, and that by 5322.
> But I think you do need to cite SMTP and MIME.
> 
>>> In 6.10:
>>>
>>>      Note that a character set specified MUST still prohibit the use of
>>>      bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
>>>
>>> This doesn’t actually say what you intended. None of the common charsets
>>> prohibit these bytes. I think you meant that when using such charsets, these
>>> characters MUST NOT be used in values.
> 
> Adding to what Alexey says, and maybe clarifying a bit: Character set
> and encoding are different things.  The character set is the
> abstraction of the characters used, and the encoding is how they're
> represented.  The encoding is what creates the bytes on the wire.  One
> problem is that "ASCII" refers to both, so it's confusing.  But with
> Unicode, "Unicode" is the character set and "UTF-8" is (usually) the
> encoding.
> 
> But your point here is that the three byte values you list MUST NOT
> appear in the string, and that has nothing to do with the character
> set or the encoding.  Those three bytes are prohibited.
> 
> You say that quite well in Section 5:
> 
>     Text-containing fields such as the session-name-field and
>     information-field are octet strings that may contain any octet with
>     the exceptions of 0x00 (Nul), 0x0a (ASCII newline), and 0x0d (ASCII
>     carriage return).
> 
> ... and in 5.13:
> 
>     Attribute values are octet strings, and MAY use any octet value
>     except 0x00 (Nul), 0x0A (LF), and 0x0D (CR).
> 
> But in 6.10 I think you want something more like this:
> 
> OLD
>     Note that a character set specified MUST still prohibit the use of
>     bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).  Character sets requiring
>     the use of these characters MUST define a quoting mechanism that
>     prevents these bytes from appearing within text fields.
> NEW
>     Note that the restriction specified in Section 5 applies: these strings
>     MUST NOT contain the bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
>     Character encodings that use these bytes MUST define a quoting
>     mechanism that prevents these bytes from appearing within the text
>     strings.
> END
> 
>> I don't recall what the state of character set definitions was in 1998
>> when this was first published. But it appears that they got carried away
>> and over-generalized. It is easy to understand how one might choose to
>> use ISO 8859-1 rather than UTF-8 since they are closely related and
>> byte-oriented. But it is unclear how one might use some other registered
>> charsets, such as EBCDIC, or other encodings of ISO 10646, such as UTF-16


From nobody Mon Jun  3 13:36:59 2019
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EFFF1204BE for <mmusic@ietfa.amsl.com>; Mon,  3 Jun 2019 13:36:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 ThRcbi_A0-_l for <mmusic@ietfa.amsl.com>; Mon,  3 Jun 2019 13:36:55 -0700 (PDT)
Received: from mail-vk1-xa2f.google.com (mail-vk1-xa2f.google.com [IPv6:2607:f8b0:4864:20::a2f]) (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 6215E12045E for <mmusic@ietf.org>; Mon,  3 Jun 2019 13:36:55 -0700 (PDT)
Received: by mail-vk1-xa2f.google.com with SMTP id r23so3120467vkd.12 for <mmusic@ietf.org>; Mon, 03 Jun 2019 13:36:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ykAJzwE2ex/0Ss8YdmofEu7pSkiiIkybyPI3CE/jeoQ=; b=qASeuslJLmT2gd1werUiWIco6GSzEpF+mM0j1iKDHkfrtkQsrDYhGuovKWB63Rt7mi vc37u1pWwGjKX/HEcobz1rkmWURVzdk4emFwpKJtxfqNbtzQzOMFcYD89RLkxRUjIozV SflJTUxYPu+YtAbRgB7q6+Dt6PJ+409mZf+ebCvdaYXCf0L/6Y94uoDXnVRrR7O3mSid Jlsj7tECg0+1oBafjUP2/us14DuzVB1pcAX9/EO6a95yILdvCI1CQPshUBJtBr/QCSFB aXFhjwsV3094/J9PXQwmd6yBAeulWvWNmLj90yRhOV/9FtbxT3J5TNUb8AbdjiM4v/vV RpTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ykAJzwE2ex/0Ss8YdmofEu7pSkiiIkybyPI3CE/jeoQ=; b=ncNzC3k/ilYAQ4p/pEJX0Z0FruvgAeu5q2qsU2AJwK3668XmsyQRNDkM4yODLLdha9 K/wo79zteIQlxTsVAYBayWqytRvFcvGQO4KbxS8YcgxJ0/rSwiM6y0YhzWPOGhIHMVdY xRD5hEjFKmVGbETly/aLy9Om/i5HFdW+RUk0G96n7CbFjeJmAgDiQj1e0dx92+lnDJ9e n6BZyQ5bK9HN6CQ13OoczL7FxgqNjXLhul7lcw6yrA/WVhLVHQNzmpXrLZM3OPpOcnNB xSPGpniAwZ8EjfUhC/pdOE+QgXqmSzze3anG9KveFd3LAn78rJoyDJ52ZSEpCaPiqcBQ jcpg==
X-Gm-Message-State: APjAAAW05DX6egZZR8Ubr9PFeOFy5L9PrGVk0sncaDvNwNVsdCBZQRkD Hg83XHc1A/nkUVa/AYP5g0zKv5pcVEvnkjH/cm52onZ4Lr4=
X-Google-Smtp-Source: APXvYqwaGhQWPAOA8/9n8/fUSzB3BrAytUJ/43ubri1K8QrKyxYHSdGauTXfYviCw7g3fhSpfuqheIsU87IXNuPf90k=
X-Received: by 2002:a1f:9f94:: with SMTP id i142mr9788011vke.22.1559594214344;  Mon, 03 Jun 2019 13:36:54 -0700 (PDT)
MIME-Version: 1.0
References: <155947424976.21503.8756374820269494435@ietfa.amsl.com> <CAD5OKxuEp8pK9G042QTpRvLG3CsW6T8vtDP8G5C2VVzke4RzKg@mail.gmail.com>
In-Reply-To: <CAD5OKxuEp8pK9G042QTpRvLG3CsW6T8vtDP8G5C2VVzke4RzKg@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Mon, 3 Jun 2019 13:36:43 -0700
Message-ID: <CAMRcRGRYscyoDWBBDohgvrkbcfa6rV=_s1qF7DJWq7ZA8pMHLw@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000023cc4a058a715378"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/06mf7Buy4KVUIgGHEjqkrxmTUa8>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-31.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2019 20:36:58 -0000

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

ilhi Roman
, you are right. I noticed it and have already updated my local copy. I
will submit changes with Flemming=E2=80=99s review comments soon

Thanks
Suhas
On Mon, Jun 3, 2019 at 1:17 PM Roman Shpount <roman@telurix.com> wrote:

> Hi Suhas,
>
> I think there is an error introduced in this version. Old language was
>
> It indicates that the offer arrived with a default destination for a medi=
a
> component that didn't have a corresponding candidate attribute.
>
> New language:
>
> It indicates that the *offerer* arrived with a default destination for a
> media component that didn't have a corresponding candidate attribute.
>
> Since this language talks about session description (offer), old language
> was correct. The offerer (an ICE agent) did not actually arrive anywhere.
>
> If you want, you can make this more clear by changing this sentence to th=
e
> following:
>
> It indicates, to the offerer, that the other party received a session
> description with a default destination for a media component that didn't
> have a corresponding candidate attribute.
>
> Regards,
> _____________
>
> Roman Shpount
>
>
> On Sun, Jun 2, 2019 at 7:18 AM <internet-drafts@ietf.org> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Multiparty Multimedia Session Control W=
G
>> of the IETF.
>>
>>         Title           : Session Description Protocol (SDP) Offer/Answe=
r
>> procedures for Interactive Connectivity Establishment (ICE)
>>         Authors         : Marc Petit-Huguenin
>>                           Suhas Nandakumar
>>                           Ari Keranen
>>         Filename        : draft-ietf-mmusic-ice-sip-sdp-31.txt
>>         Pages           : 42
>>         Date            : 2019-06-02
>>
>> Abstract:
>>    This document describes Session Description Protocol (SDP) Offer/
>>    Answer procedures for carrying out Interactive Connectivity
>>    Establishment (ICE) between the agents.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-31
>> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-31
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-ice-sip-sdp-31
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>

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

<div><div dir=3D"auto">ilhi Roman</div><div dir=3D"auto">, you are right. I=
 noticed it and have already updated my local copy. I will submit changes w=
ith Flemming=E2=80=99s review comments soon</div></div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">Thanks</div><div dir=3D"auto">Suhas=C2=A0</div><d=
iv><div class=3D"gmail_quote"><div>On Mon, Jun 3, 2019 at 1:17 PM Roman Shp=
ount &lt;<a href=3D"mailto:roman@telurix.com">roman@telurix.com</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div>Hi Suhas,<div><br></div><d=
iv>I think there is an error introduced in this version. Old language was</=
div><div><br></div><div>It indicates that the offer arrived with a default =
destination for a media component that=C2=A0didn&#39;t have a corresponding=
 candidate attribute.</div><div><br></div><div>New language:</div><div><br>=
</div><div>It indicates that the <b>offerer</b> arrived with a default dest=
ination for a media component that=C2=A0didn&#39;t have a corresponding can=
didate attribute.=C2=A0</div><div><br></div><div>Since this language talks =
about session description (offer), old language was correct. The offerer (a=
n ICE agent) did not actually arrive anywhere.</div><div><br></div><div>If =
you want, you can make this more clear by changing this sentence to the fol=
lowing:</div><div><br></div><div>It indicates, to the offerer, that the oth=
er party received a session description with a default destination for a me=
dia component that=C2=A0didn&#39;t have a corresponding candidate attribute=
.=C2=A0=C2=A0</div><div><br></div><div>Regards,<br clear=3D"all"><div><div =
class=3D"m_7996357895025138705gmail_signature" data-smartmail=3D"gmail_sign=
ature">_____________</div></div></div></div><div><div><div><div class=3D"m_=
7996357895025138705gmail_signature" data-smartmail=3D"gmail_signature"><br>=
Roman Shpount</div></div><br></div></div><br><div class=3D"gmail_quote"><di=
v class=3D"gmail_attr">On Sun, Jun 2, 2019 at 7:18 AM &lt;<a href=3D"mailto=
:internet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Multiparty Multimedia Session Control WG o=
f the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Session Description Protocol (SDP) Offer/Answer procedures for Interactive=
 Connectivity Establishment (ICE)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Marc=
 Petit-Huguenin<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Suhas Nandakumar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ari Keranen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mmusic-ice-sip-sdp-31.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 42<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2019-06-02<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes Session Description Protocol (SDP) Off=
er/<br>
=C2=A0 =C2=A0Answer procedures for carrying out Interactive Connectivity<br=
>
=C2=A0 =C2=A0Establishment (ICE) between the agents.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/"=
 rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draf=
t-ietf-mmusic-ice-sip-sdp/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-31" re=
l=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-m=
music-ice-sip-sdp-31</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-=
sdp-31" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d=
oc/html/draft-ietf-mmusic-ice-sip-sdp-31</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-ice-sip-sd=
p-31" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?url=
2=3Ddraft-ietf-mmusic-ice-sip-sdp-31</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div>
</blockquote></div></div>

--00000000000023cc4a058a715378--


From nobody Mon Jun  3 15:17:42 2019
Return-Path: <kaduk@mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91CB8120862; Mon,  3 Jun 2019 15:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OGW66EutEG7e; Mon,  3 Jun 2019 15:17:31 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 961B4120120; Mon,  3 Jun 2019 15:17:31 -0700 (PDT)
Received: from prolepsis.kaduk.org (c-24-16-119-19.hsd1.wa.comcast.net [24.16.119.19]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x53MHLA0001067 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 3 Jun 2019 18:17:23 -0400
Date: Mon, 3 Jun 2019 15:17:21 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: The IESG <iesg@ietf.org>, fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic@ietf.org
Message-ID: <20190603221717.GF1902@prolepsis.kaduk.org>
References: <155922686313.22081.12209259015077736906.idtracker@ietfa.amsl.com> <df7509c8-5bba-fcc2-5d75-3cc179266cf8@alum.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <df7509c8-5bba-fcc2-5d75-3cc179266cf8@alum.mit.edu>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/sIhFi8eHsxjl_2NBhI7-kqYbk0Y>
Subject: Re: [MMUSIC] Benjamin Kaduk's No Objection on draft-ietf-mmusic-rfc4566bis-35: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2019 22:17:35 -0000

On Mon, Jun 03, 2019 at 02:44:18PM -0400, Paul Kyzivat wrote:
> Benjamin,
> 
> Thank you for your comments. I've included followup inline below.
> 
> On 5/30/19 10:34 AM, Benjamin Kaduk via Datatracker wrote:
> > Benjamin Kaduk has entered the following ballot position for
> > draft-ietf-mmusic-rfc4566bis-35: No Objection
> 
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> > 
> > I reviewed the diff from RFC 4566 but didn't make it quite all the way
> > through the full document itself.  What I did find in that partial read
> > suggests that a full read-through by the authors may find some lingering
> > stale language or minor internal inconsistencies.
> 
> There really hasn't been an attempt to thoroughly remove stale (dated)
> language. Fundamentally this is a 21 year old document that has been tidied
> up a bit. Anyone that started over today to define something new for the
> same purpose would surely define something very different. We've only been
> trying to fix areas where there has been confusion or ambiguity has been
> found, or where new concerns (e.g., security) have needed to be addressed.

I think the RFC Editor is still going to be reviewing the whole thing for
consistency with the current style/practices, so getting a headstart now
would probably be more effective and save some time overall.

> > Another broad topic (with more comments throughout) is that an early and
> > clear discussion of time representation may be helpful, and arguably
> > does not need to refer to NTP time at all.  (This is especially so when
> > we refer to "NTP time format" and RFC 5905, which lists three
> > formats, none of which have a straightforward translation to numeric
> > strings without fraction part.)
> 
> Good point. It appears that the intent is for the value to be seconds since
> the beginning of NTP Era 0 ("0 h 1 January 1900 UTC"). We can either
> reference that directly, or, since that starting point isn't likely to be
> changed in NTP, simply state it. Which of those would you prefer?

The latter seems fine (and IIRC we even have seen RFCs published that just
refer to "seconds since the Unix epoch (excluding leap seconds)" with no
further reference.

> > Section 4
> > 
> >                                     SDP is primarily intended for use in
> >     an internetwork, although it is sufficiently general that it can
> >     describe multimedia conferences in other network environments.  [...]
> > 
> > nit(?): this verbiage ("internetwork") feels quite dated.
> 
> Does "... primarily intended for use with Internet protocols, although ..."
> work for you?

Sure.

> > Section 4.1
> > 
> >                                                      Some media types may
> >     redefine this behavior, but this is NOT RECOMMENDED since it
> >     complicates implementations (including middleboxes that must parse
> >     the addresses to open Network Address Translation (NAT) or firewall
> >     pinholes).
> > 
> > (Similarly for "firewall pinholes".)
> 
> Do you have a suggestion. This still seems ok to me.

If it's okay to you, then no-change is the proper course of action.
(I don't remember encountering "pinholes" previously, and would have
worded it as "to open holes in NATs and/or firewalls".)

> > Section 4.3
> > 
> > The usual security considerations about (potentially) referencing remote
> > content would seem to apply.  Perhaps a RFC 3986 reference (or more)
> > would be appropriate.
> 
> Will adding a reference to [RFC3986] be sufficient?

I would prefer a note about "Use of URIs to indicate remote resources
is subject to the security considerations from [RFC3986]", but just the
reference would be okay.

> > Section 4.6
> > 
> > Perhaps we should mention here that this categorization mechanism is
> > deprecated/obsolete?
> 
> Section 4.6??? Did you mean 4.4?

I clearly did; I'm not sure what I was looking at (especially since
this was 4.5 (not 4.6) in RFC 4566 itself).

> Since a=cat has been declared obsolete, I'm inclined to simply remove
> section 4.4.

That works for me.

> > Section 5
> > 
> >     An SDP description is entirely textual.  SDP field names and
> >     attribute names use only the US-ASCII subset of UTF-8 [RFC3629], but
> >     textual fields and attribute values MAY use the full ISO 10646
> >     character set in UTF-8 encoding, or some other character set defined
> >     by the "a=charset:" attribute.  [...]
> > 
> > nit: here (and in Section 4.4 just above) may be the only times we
> > include the colon when discussing an "a=" attribute; consistency would
> > seem to suggest removing the colons.
> 
> OK.
> 
> >                                    However, since SDP may be used in
> >     environments where the maximum permissible size of a session
> >     description is limited, the encoding is deliberately compact.  Also,
> >     since descriptions may be transported via very unreliable means or
> >     damaged by an intermediate caching server, the encoding was designed
> >     with strict order and formatting rules so that most errors would
> >     result in malformed session descriptions that could be detected
> >     easily and discarded.  This also allows rapid discarding of encrypted
> >     session descriptions for which a receiver does not have the correct
> >     key.
> > 
> > I don't really see why the "rapid discarding" property follows from the
> > compactness of the encoding, when the correct key for the encrypted
> > description is not known.
> 
> I'm inclined to simply remove that last sentence. I'd remove the whole
> paragraph, but keeping it may provide insight into why the protocol is as
> weird and crufty as it is.

OK

> > Section 5.x
> > 
> > It's interesting to note that while the SDP attributes (Sections 6.x)
> > got ABNF constructions for their values, the type descriptions here
> > are still presented in a somewhat informal syntax (that, e.g., relies on
> > implicitly stating that fields are whitespace-separated).
> 
> It is an interesting point. The best rationale I can give is that *not*
> having ABNF got to be a serious problem for attributes, because there are a
> lot of them, and new ones get defined regularly (with complex syntax) and
> the syntax was often recognized as being ambiguous. So we wanted to demand
> ABNF for future extensions, and felt we should make the ones defined in this
> document comply with that.
> 
> OTOH, the other fields are revised/extended much more rarely, so it hasn't
> been a problem. And so there is much less motivation to "rock the boat" by
> changing the manner of defining them.

Indeed.  Changing this seems like more effort than it's worth, at this point
in the process.  (But can I have whitespace in a comma-separated list?  I
assume "no", but have been wrong on many occasions...)

> > Section 5.2
> > 
> >     <sess-id>  is a numeric string such that the tuple of <username>,
> >        <sess-id>, <nettype>, <addrtype>, and <unicast-address> forms a
> >        globally unique identifier for the session.  The method of <sess-
> >        id> allocation is up to the creating tool, but it has been
> >        suggested that a Network Time Protocol (NTP) format timestamp be
> >        used to ensure uniqueness [RFC5905].
> > 
> > (et seq) There is not a single "NTP format timestamp"; RFC 5905 provides
> > three different formats.  If any of the three is fine, that should be
> > stated, and if a single distinguished one is preferred, that should also
> > be stated.
> > Furthermore, the three formats all include multiple fields and not a
> > rule for presenting them as a "numeric string" as described here, which
> > on the face of it seems to exclude fractions.  ("numeric string" does
> > not seem to be specifically defined by this document.)
> 
> I'm inclined to change this to suggest the same format as used for t=, as
> discussed above.
> 
> Because the values of these fields is only loosely specified there is no
> *guarantee* that the combination provides the intended uniqueness. But there
> are so many implementations deployed that it would be impossible to redefine
> to make such a guarantee. In practice it isn't a problem - things are unique
> *enough*.
> 
> > Section 5.3
> > 
> >     The "s=" line MUST NOT be empty and SHOULD contain ISO 10646
> >     characters (but see also the "a=charset" attribute).  [...]
> > 
> > Is this perhaps intended to be "SHOULD only contain"?
> > (Similarly in following subsections.)
> 
> I received other comments on this and will work on it.

Sure, and sorry for not deduplicating my comments -- I simply ran out
of time and sent what I currently had.

-Ben

> > Section 5.9
> > 
> >     The first and second sub-fields of the time-field give the start and
> >     stop times, respectively, for the session.  These values are the
> >     decimal representation of Network Time Protocol (NTP) time values in
> >     seconds since 1900 [RFC5905].  To convert these values to UNIX time
> >     (UTC), subtract decimal 2208988800.
> > 
> > Looking at the time formats listed in RFC 5905, one perhaps wonders if
> > the values used by SDP are more appropriately described informally as
> > just "seconds since the Unix epoch" without specific reference to NTP
> > (both here and elsewhere in the document).
> > 
> >     NTP timestamps are elsewhere represented by 64-bit values, which wrap
> >     sometime in the year 2036.  [...]
> > 
> > I don't understand what this is referring to.  Is this perhaps the "32
> > bits of seconds and 32 bits of fraction" format, which suffers from the
> > y2038 (note '8', not '6') problem?
> 
> See my earlier comments.
> 
> > Section 6.2
> > 
> > Perhaps "this was to assist" would be more fitting, given the obsolete
> > nature of a=keywds.
> 
> OK.
> 
> > Section 6.9
> > 
> >     This specifies the type of the multimedia conference.  Suggested
> >     values are "broadcast", "meeting", "moderated", "test", and "H332".
> > 
> > nit: I don't think these are "suggested" values; they are the only ones
> > allowed by the ABNF.
> 
> Good point. Will fix.
> 
> >     "recvonly" should be the default for "type:broadcast" sessions,
> >     "type:meeting" should imply "sendrecv", and "type:moderated" should
> >     indicate the use of a floor control tool and that the media tools are
> >     started so as to mute new sites joining the multimedia conference.
> > 
> > There seems to be redundancy here with the "SHOULD" in Section 6.7 about
> > "sendrecv" being the default for non-broadcast non-H322 sessions.
> 
> Thanks for pointing this out. This needs work, since IMO it is wrong to use
> "default" here. At best these are recommendations for what the creator of
> and SDP body should do.
> 
> > Section 6.11
> > 
> > Is it intentional to lose the language about "order of importance" of
> > multiple languages?
> 
> Yes.
> 
> This is describing what is used in the text of the SDP body. It isn't saying
> anything about future use. RFC8373 defines 'hlang-send' and 'hlang-recv' for
> indicating preferences of languages to use in media.
> 
> 	Thanks,
> 	Paul


From nobody Mon Jun  3 15:48:22 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE78112011A; Mon,  3 Jun 2019 15:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IgZKzLFE76LA; Mon,  3 Jun 2019 15:48:10 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 817F612006A; Mon,  3 Jun 2019 15:48:10 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x53Mm6c2020342 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 3 Jun 2019 18:48:06 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: =?UTF-8?Q?=c3=89ric_Vyncke?= <evyncke@cisco.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
References: <155860096353.3948.17073187906064821991.idtracker@ietfa.amsl.com> <ce010b1b-3b24-ce89-f733-80dfc6799785@alum.mit.edu>
Message-ID: <8696c636-4e13-5abb-e230-914f31eb4c5e@alum.mit.edu>
Date: Mon, 3 Jun 2019 18:48:05 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <ce010b1b-3b24-ce89-f733-80dfc6799785@alum.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/GVEilh3P69wZJouZvzAjlifBlsI>
Subject: Re: [MMUSIC]  =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ie?= =?utf-8?q?tf-mmusic-rfc4566bis-35=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2019 22:48:12 -0000

Éric,

On 5/28/19 5:32 PM, Paul Kyzivat wrote:

> On 5/23/19 4:42 AM, Éric Vyncke via Datatracker wrote:

>> -- Section 5 --
>>
>> When using IPv4 unicast addresses, please use the example ones.
> 
> Good catch. I agree these need to be fixed. I'll have the scrub the 
> document looking for them.

After looking again I’m not finding any that need fixing. What did you 
see that let you to raise this issue?

	Thanks,
	Paul


From nobody Mon Jun  3 15:55:22 2019
Return-Path: <evyncke@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D91931201A2; Mon,  3 Jun 2019 15:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=XOmBmzRv; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=rwMPqhXs
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 AbFNio8N765I; Mon,  3 Jun 2019 15:55:10 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D17DA1200B7; Mon,  3 Jun 2019 15:55:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=970; q=dns/txt; s=iport; t=1559602510; x=1560812110; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+1LBmZUYObu2HumICLek2vTPnCWyoFZ6JLZwPDYQI/0=; b=XOmBmzRvAlsjIilrjPC3WcwBn4eyC3ttwWGpAhos21wE/y/jwusr+Qdh bY7epnD51B/S4ze2YzIO9ols78gKDJ2aQOfxDM7bti0dt3+jLKsIyNf3S oyVH6j75XuEdZJIOYVYMgYSRVEpm4rkp0tUqGRqnOwQps6bF2B5An8JH2 g=;
IronPort-PHdr: =?us-ascii?q?9a23=3AE3GMQB9rDO97hv9uRHGN82YQeigqvan1NQcJ65?= =?us-ascii?q?0hzqhDabmn44+8ZB7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUER?= =?us-ascii?q?oMiMEYhQslVcObGEvwL/PCZC0hF8MEX1hgrDm2?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CnAAC5pPVc/4gNJK1mDg8BAQUBBwU?= =?us-ascii?q?BgVIHAQsBgT1QA4E/IAQLKIQUg0cDjnWCV5cvgS6BJANUCQEBAQwBAS0CAQG?= =?us-ascii?q?EQAIXgnsjNQgOAQMBAQQBAQIBBG0cDIVLAQEBAgESEREMAQE3AQ8CAQgODAI?= =?us-ascii?q?mAgICMBUFCwIEAQ0FIoMAgWsDDg8BAp09AoE4iF9xgTGCeQEBBYUFGIIPCYE?= =?us-ascii?q?MKAGLWReBQD+BOB+CTD6EW4JzMoImjhqaYwkCgg2TMhuCEhCGcY1bgx2JY5Y?= =?us-ascii?q?eAgQCBAUCDgEBBYFRATWBWHAVZQGCQYIPDBcUgzmKGDtygSmQJAEB?=
X-IronPort-AV: E=Sophos;i="5.60,548,1549929600"; d="scan'208";a="281943980"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 03 Jun 2019 22:55:08 +0000
Received: from XCH-ALN-011.cisco.com (xch-aln-011.cisco.com [173.36.7.21]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x53Mt80J020348 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 3 Jun 2019 22:55:08 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-011.cisco.com (173.36.7.21) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 3 Jun 2019 17:55:07 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 3 Jun 2019 17:55:07 -0500
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 3 Jun 2019 18:55:06 -0400
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=+1LBmZUYObu2HumICLek2vTPnCWyoFZ6JLZwPDYQI/0=; b=rwMPqhXs/xWxRlRSU4PYYLrs6/hHhc21rA7UmoFPL60PWNNnKGbZLizjFr+UIzmQQXIZTjLbfiDESX28MuwEaDHQuKEGVseghMev7KiGCJLPFfR1jqsXtnmPLLHH5C6+PK5itQmpAm/GoRVOXUA7lG5I3RIyPR0nnHWkFHwolr8=
Received: from MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) by MN2PR11MB4047.namprd11.prod.outlook.com (20.179.149.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.22; Mon, 3 Jun 2019 22:55:05 +0000
Received: from MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::1990:d953:1387:d1a7]) by MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::1990:d953:1387:d1a7%7]) with mapi id 15.20.1943.018; Mon, 3 Jun 2019 22:55:05 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, The IESG <iesg@ietf.org>
CC: "draft-ietf-mmusic-rfc4566bis@ietf.org" <draft-ietf-mmusic-rfc4566bis@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "Flemming Andreasen (fandreas)" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: =?utf-8?B?w4lyaWMgVnluY2tlJ3MgTm8gT2JqZWN0aW9uIG9uIGRyYWZ0LWlldGYtbW11?= =?utf-8?Q?sic-rfc4566bis-35:_(with_COMMENT)?=
Thread-Index: AQHVGl5vr0O03h3SNkKuGRrol/E1fqaKFK0A
Date: Mon, 3 Jun 2019 22:55:05 +0000
Message-ID: <9A5FBBEE-00E0-48B9-B548-04AE6BB4D05E@cisco.com>
References: <155860096353.3948.17073187906064821991.idtracker@ietfa.amsl.com> <ce010b1b-3b24-ce89-f733-80dfc6799785@alum.mit.edu> <8696c636-4e13-5abb-e230-914f31eb4c5e@alum.mit.edu>
In-Reply-To: <8696c636-4e13-5abb-e230-914f31eb4c5e@alum.mit.edu>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.19.0.190512
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com; 
x-originating-ip: [2001:420:293:1262:9da5:9843:8a09:2e17]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: efdda915-22c3-4c8e-d8cc-08d6e87684e8
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB4047; 
x-ms-traffictypediagnostic: MN2PR11MB4047:
x-ld-processed: 5ae1af62-9505-4097-a69a-c1553ef7840e,ExtAddr
x-microsoft-antispam-prvs: <MN2PR11MB4047047F8FFF044ACB4CBA54A9140@MN2PR11MB4047.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0057EE387C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(396003)(366004)(376002)(346002)(136003)(199004)(189003)(4744005)(54906003)(110136005)(66556008)(316002)(478600001)(58126008)(256004)(66476007)(6486002)(102836004)(86362001)(6436002)(53546011)(6506007)(76176011)(73956011)(66946007)(91956017)(76116006)(66446008)(5660300002)(68736007)(6512007)(99286004)(7736002)(33656002)(6116002)(2171002)(6246003)(64756008)(81156014)(4326008)(81166006)(305945005)(53936002)(229853002)(36756003)(2906002)(25786009)(8936002)(82746002)(71200400001)(224303003)(486006)(71190400001)(83716004)(2616005)(476003)(14454004)(46003)(446003)(11346002)(186003); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4047; H:MN2PR11MB4144.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: tSj8mMnXW5KeNM4CNO1kvxCr/0qRqqm2Eq12GAeG2qs3OYLm7PvH/H9Gpzh3b1cXD6QJAgmPMYzX+7ZtfS4eR3t41VYMeeWZdNemjYGSeIeeG82EEay/9lB3EIRZpjcGm7YPV0Bqhj95Eyak+ZYS41b8gJVIa79XKFJp+RmbDlFJtUBx6Tnlejotua+BPuzfP4dgHVQWxmiylns+duyf99tc2T37R7NuP6SJPC4JNNg4kJvP75SsvlPIm16xhEJp2LfTa8UcdOFLFcNIhbbnbIuhA6BI+aUD+MDJ3Z4vDB5RKYHULwcYQp04d4OOGWCLURv4xQQR93JHiqrd9TXARBMstXXW86tMaEpVg5mVJvlbqdtSnKQc57RsEhQkM5dS4y2LSIienu1/j8gp66GMrGzO0xJkai4O70d9YVVHvO0=
Content-Type: text/plain; charset="utf-8"
Content-ID: <A6761E97D9F57740871508783B74E41F@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: efdda915-22c3-4c8e-d8cc-08d6e87684e8
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jun 2019 22:55:05.2261 (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: evyncke@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4047
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.21, xch-aln-011.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/1GUTbcxlO9LV3l_X5jBIWBww2hM>
Subject: Re: [MMUSIC]  =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ie?= =?utf-8?q?tf-mmusic-rfc4566bis-35=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2019 22:55:12 -0000

U3VjaCBhcyBpbiBzZWN0aW9uIDUsIGluIHRoZSBleGFtcGxlIFNEUDogIiBvPWpkb2UgMjg5MDg0
NDUyNiAyODkwODQyODA3IElOIElQNCAxOTguNTEuMTAwLjEiDQoNCi3DqXJpYw0KDQrvu79PbiAw
My8wNi8yMDE5LCAxNTo0OCwgIlBhdWwgS3l6aXZhdCIgPHBreXppdmF0QGFsdW0ubWl0LmVkdT4g
d3JvdGU6DQoNCiAgICDDiXJpYywNCiAgICANCiAgICBPbiA1LzI4LzE5IDU6MzIgUE0sIFBhdWwg
S3l6aXZhdCB3cm90ZToNCiAgICANCiAgICA+IE9uIDUvMjMvMTkgNDo0MiBBTSwgw4lyaWMgVnlu
Y2tlIHZpYSBEYXRhdHJhY2tlciB3cm90ZToNCiAgICANCiAgICA+PiAtLSBTZWN0aW9uIDUgLS0N
CiAgICA+Pg0KICAgID4+IFdoZW4gdXNpbmcgSVB2NCB1bmljYXN0IGFkZHJlc3NlcywgcGxlYXNl
IHVzZSB0aGUgZXhhbXBsZSBvbmVzLg0KICAgID4gDQogICAgPiBHb29kIGNhdGNoLiBJIGFncmVl
IHRoZXNlIG5lZWQgdG8gYmUgZml4ZWQuIEknbGwgaGF2ZSB0aGUgc2NydWIgdGhlIA0KICAgID4g
ZG9jdW1lbnQgbG9va2luZyBmb3IgdGhlbS4NCiAgICANCiAgICBBZnRlciBsb29raW5nIGFnYWlu
IEnigJltIG5vdCBmaW5kaW5nIGFueSB0aGF0IG5lZWQgZml4aW5nLiBXaGF0IGRpZCB5b3UgDQog
ICAgc2VlIHRoYXQgbGV0IHlvdSB0byByYWlzZSB0aGlzIGlzc3VlPw0KICAgIA0KICAgIAlUaGFu
a3MsDQogICAgCVBhdWwNCiAgICANCg0K


From nobody Mon Jun  3 20:37:37 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CEF6120033; Mon,  3 Jun 2019 20:37:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mmusic@ietf.org
Message-ID: <155961945536.24598.17183487212731948165@ietfa.amsl.com>
Date: Mon, 03 Jun 2019 20:37:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/LUeZK29xMa9Vp4kD4q4tqGXSPL0>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-32.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 03:37:36 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : Session Description Protocol (SDP) Offer/Answer procedures for Interactive Connectivity Establishment (ICE)
        Authors         : Marc Petit-Huguenin
                          Suhas Nandakumar
                          Ari Keranen
	Filename        : draft-ietf-mmusic-ice-sip-sdp-32.txt
	Pages           : 42
	Date            : 2019-06-03

Abstract:
   This document describes Session Description Protocol (SDP) Offer/
   Answer procedures for carrying out Interactive Connectivity
   Establishment (ICE) between the agents.

   This document obsoletes RFC 5245.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-32
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-32

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-32


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Jun  3 20:39:27 2019
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0BF5120139 for <mmusic@ietfa.amsl.com>; Mon,  3 Jun 2019 20:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 3gjIS797HrWc for <mmusic@ietfa.amsl.com>; Mon,  3 Jun 2019 20:39:22 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 5B85A120033 for <mmusic@ietf.org>; Mon,  3 Jun 2019 20:39:22 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id z11so12622845vsq.9 for <mmusic@ietf.org>; Mon, 03 Jun 2019 20:39:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nXT9JpPo9tv658ZLp9Apo+xEq3yg0J5P/5N1P4wpcPE=; b=ez8CSKB0WxlYLTO7C4gegvuwFYsLI2iVQm4ajZD9v7cDFQvRaeUMgkr35LFejO8mrE nvxJSrDQ9WDh1KlP3d50wx7+UTYAxFRMgXKdix3m9ltrraBb5WBxxg6K9/nLlH6yDezz BBULPtUfpvKt1/3T9pRgKmTwUg8Iyf2OaBYKWWFcsOja3UgopQ8fyvvkHU4UyOjNz2s1 QnYGKMmfE+pdwZSOI9RrcIqjtmY6MFoc6cg3/FCjKhfnhE3TACjwyMqbSXF4JIDb/LM3 KoYh6PZDLhUjEJKL1h04EaKhWO3sZtup9rPbOdECwjNLs0qS8g75du7ADZUjh4VoFcCb nV9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nXT9JpPo9tv658ZLp9Apo+xEq3yg0J5P/5N1P4wpcPE=; b=OVRpidZulRvOlV7nmbhHizrPxFCDUvXsq/hh30abzrjKD+5dEWX6UtlCC/HH8TvzgV kmsrHa4sFolDDEhinQwdOqg4jtyYlfmxyZy4/16+OvKjTUVaW9Z40f3CEhwgdMhaOjG/ EPQABQyUkbF8srTi6s7WNixBDrZBtXo4F4pQc2WTMcyQf0Jip/Fxo1PV4GQ8faxP8WDz W80v6KvbwkMSecRtoE7rTbTxQhAOlhUAulRUoj7c5u+1uKiH+zKKuHAFbXq6daVh99kb SUcNf/J2/TCPpuNi8Q77ddPoLexOFvE5xIbppy/FZ6NotUxxfOEnZkSRyDnw5IES34HT SlsA==
X-Gm-Message-State: APjAAAXny1AAhgQFN8rkk1SGYf3So7dItY9hj3DDmE+OfLELCcQAS/O7 2of7znj60VCZqpNlM5BgMB+Qrrw18S2akDOCCKjVdfvBRt4=
X-Google-Smtp-Source: APXvYqx3XTH8jKTmZ6itfEkhc/n+NBIpl46NgvsGEaPkmFG3RQ0T4+MaL5+4t3g02/TqBC+sOoMpAEYEe4x3NvOQNyY=
X-Received: by 2002:a67:6f87:: with SMTP id k129mr14738056vsc.225.1559619561146;  Mon, 03 Jun 2019 20:39:21 -0700 (PDT)
MIME-Version: 1.0
References: <155961945536.24598.17183487212731948165@ietfa.amsl.com>
In-Reply-To: <155961945536.24598.17183487212731948165@ietfa.amsl.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Mon, 3 Jun 2019 20:39:09 -0700
Message-ID: <CAMRcRGT-hmz2YmGS4Q-dCdpopQtv_g++Mb41CWjjpZEz4XE9rQ@mail.gmail.com>
To: mmusic WG <mmusic@ietf.org>
Cc: Roman Shpount <roman@telurix.com>, Flemming Andreasen <fandreas@cisco.com>
Content-Type: multipart/alternative; boundary="000000000000ed4ea3058a7739b6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/pmU-bqvx0iyG8CQ8ifKKGEY_AXk>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-32.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 03:39:25 -0000

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

Version 32 addresses Flemming's review comments, IDNits error

Thanks
Suhas

On Mon, Jun 3, 2019 at 8:37 PM <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multiparty Multimedia Session Control WG
> of the IETF.
>
>         Title           : Session Description Protocol (SDP) Offer/Answer
> procedures for Interactive Connectivity Establishment (ICE)
>         Authors         : Marc Petit-Huguenin
>                           Suhas Nandakumar
>                           Ari Keranen
>         Filename        : draft-ietf-mmusic-ice-sip-sdp-32.txt
>         Pages           : 42
>         Date            : 2019-06-03
>
> Abstract:
>    This document describes Session Description Protocol (SDP) Offer/
>    Answer procedures for carrying out Interactive Connectivity
>    Establishment (ICE) between the agents.
>
>    This document obsoletes RFC 5245.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-32
> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-32
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-32
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">Version 32 addresses Flemming&#39;s review comments, IDNit=
s error<div><br></div><div>Thanks</div><div>Suhas</div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jun 3, 2019 =
at 8:37 PM &lt;<a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@=
ietf.org</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-le=
ft:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Multiparty Multimedia Session Control WG o=
f the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Session Description Protocol (SDP) Offer/Answer procedures for Interactive=
 Connectivity Establishment (ICE)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Marc=
 Petit-Huguenin<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Suhas Nandakumar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ari Keranen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mmusic-ice-sip-sdp-32.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 42<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2019-06-03<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes Session Description Protocol (SDP) Off=
er/<br>
=C2=A0 =C2=A0Answer procedures for carrying out Interactive Connectivity<br=
>
=C2=A0 =C2=A0Establishment (ICE) between the agents.<br>
<br>
=C2=A0 =C2=A0This document obsoletes RFC 5245.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/"=
 rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draf=
t-ietf-mmusic-ice-sip-sdp/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-32" re=
l=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-m=
music-ice-sip-sdp-32</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-=
sdp-32" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d=
oc/html/draft-ietf-mmusic-ice-sip-sdp-32</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-ice-sip-sd=
p-32" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?url=
2=3Ddraft-ietf-mmusic-ice-sip-sdp-32</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div>

--000000000000ed4ea3058a7739b6--


From nobody Tue Jun  4 05:07:51 2019
Return-Path: <bo.burman@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6E09120033; Tue,  4 Jun 2019 05:07:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 M5b56WDTbCQz; Tue,  4 Jun 2019 05:07:47 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20063.outbound.protection.outlook.com [40.107.2.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A5C612004A; Tue,  4 Jun 2019 05:07:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xuTspy2fv8mhSXcRim3QrVIWzGgdq/0Bw8TdhBLaOA4=; b=pTrM3T+u5nbAnd9gEc7H09fPLb0tvGDbfEFzAhwtIGKnO1HxPxH5zCx3R3aN0BUNfawQ3s4hxmMS2n0fttMNoPWylcR+h4Tg5+ZWT19hWLr4sALx6dBX3GozJsdxugZ/CUYQvhRJ2MY2JjmzQzZFaO0CIA5Gq5tcZwr9k+5TBd4=
Received: from HE1PR07MB3259.eurprd07.prod.outlook.com (10.170.246.26) by HE1PR07MB4411.eurprd07.prod.outlook.com (20.176.167.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1965.9; Tue, 4 Jun 2019 12:07:43 +0000
Received: from HE1PR07MB3259.eurprd07.prod.outlook.com ([fe80::1c47:b690:803a:f2f5]) by HE1PR07MB3259.eurprd07.prod.outlook.com ([fe80::1c47:b690:803a:f2f5%4]) with mapi id 15.20.1965.011; Tue, 4 Jun 2019 12:07:43 +0000
From: Bo Burman <bo.burman@ericsson.com>
To: Roman Shpount <roman@telurix.com>, Martin Thomson <mt@lowentropy.net>, "draft-ietf-mmusic-sdp-uks.authors@ietf.org, " <draft-ietf-mmusic-sdp-uks.authors@ietf.org>
CC: mmusic <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Getting draft-ietf-mmusic-sdp-uks-04 ready for PubReq
Thread-Index: AdUMw3zvW0vhfA0KRLycVMoG67t8YgFybcaAAG5xd4AAiksSgAEW7rrA
Date: Tue, 4 Jun 2019 12:07:43 +0000
Message-ID: <HE1PR07MB32599C3B63042968BBCBCDD98D150@HE1PR07MB3259.eurprd07.prod.outlook.com>
References: <HE1PR07MB3259C69803BEB1913483C7328D0B0@HE1PR07MB3259.eurprd07.prod.outlook.com> <CAD5OKxvfBSs7Yu5xyD7LXgfEW_5-2c_u39935mF8XOTxvLxixg@mail.gmail.com> <1cebc5fa-81ac-455c-9619-48d273177e5b@www.fastmail.com> <CAD5OKxtt8Attax=9-LnndF8RD2D0eFzZVSh-PqCC=9485eTJPw@mail.gmail.com>
In-Reply-To: <CAD5OKxtt8Attax=9-LnndF8RD2D0eFzZVSh-PqCC=9485eTJPw@mail.gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=bo.burman@ericsson.com; 
x-originating-ip: [192.176.1.84]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: acc93758-90b5-4ecc-6e10-08d6e8e53fb5
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(49563074)(7193020); SRVR:HE1PR07MB4411; 
x-ms-traffictypediagnostic: HE1PR07MB4411:
x-microsoft-antispam-prvs: <HE1PR07MB441198546DE621025E9D861C8D150@HE1PR07MB4411.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0058ABBBC7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(396003)(136003)(376002)(366004)(346002)(189003)(51444003)(199004)(53546011)(52536014)(81156014)(74316002)(81166006)(8936002)(4326008)(316002)(9686003)(5660300002)(53936002)(14454004)(76176011)(76116006)(86362001)(73956011)(8676002)(66946007)(7736002)(33656002)(508600001)(71200400001)(66556008)(66476007)(71190400001)(66616009)(64756008)(66446008)(25786009)(26005)(14444005)(68736007)(2906002)(606006)(229853002)(186003)(6436002)(6506007)(99286004)(7696005)(476003)(54896002)(6306002)(446003)(110136005)(102836004)(3846002)(6116002)(55016002)(66066001)(6246003)(486006)(256004)(11346002)(790700001)(44832011)(99936001)(236005); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB4411; H:HE1PR07MB3259.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: CmIgGSixI5DF64MnVqBfEGSOXdYeoeMyDWTMbatvHNHNtQP4SQOn/ucuCRnbPfblMNumWIZuL3c7xX3ij1foUCySY6I06Yivs/hLVdqPmcP/U+k4BRL7Ax7E4HoM2jzks3/YaJCg3nuCx7TMgsxsGNMrTp2IifCxLX4C1aNc2orss+Qml/BOu31xgiHkpmF3JNX9Ol4Yq1Fwevai4Kp3zvskMuAtjrH04YaS1GV8XPLxs0co7MUHrjKtl+TCFP2Ykg1Lq08naTMJxmY0mq9maTjYEHlmBpCZMfWt6ftoUAHlBk6RVoxbFG65fRO8WrQXwQZn//ltewrR4znvtcgwMqww6y8FEkDmbpbqh1x9Mq7nmWcO/PKIpA7oV3unXEEX+AoSPD87+ah5ZO9blkr0TyzxrQmsEr0BYMZfL+aFPEM=
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_00DC_01D51ADE.E05B2830"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: acc93758-90b5-4ecc-6e10-08d6e8e53fb5
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jun 2019 12:07:43.2274 (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: bo.burman@ericsson.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4411
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FBfzLfEoQbCcRMm1_GUhL2OLE1w>
Subject: Re: [MMUSIC] Getting draft-ietf-mmusic-sdp-uks-04 ready for PubReq
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 12:07:50 -0000

------=_NextPart_000_00DC_01D51ADE.E05B2830
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_00DD_01D51ADE.E05B2830"


------=_NextPart_001_00DD_01D51ADE.E05B2830
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Thank you for your review Roman.

=20

Authors, since there are no unaddressed comments beyond the editorial =
ones from Flemming (here =
<https://mailarchive.ietf.org/arch/msg/mmusic/ZewhLMuV3EJ6r6rVsCtSiF4TsaM=
> ), and there seems to be no objections to proceed, please submit an =
update addressing Flemming=E2=80=99s comments that I will then submit =
for publication.

=20

Thanks,

/Bo

MMUSIC co-chair

=20

=20

From: mmusic <mmusic-bounces@ietf.org> On Behalf Of Roman Shpount
Sent: den 30 maj 2019 00:45
To: Martin Thomson <mt@lowentropy.net>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Getting draft-ietf-mmusic-sdp-uks-04 ready for =
PubReq

=20

I have reviewed the document and I have confirmed that the document is =
clear and my understanding is correct.

=20

Thank you, Martin.

_____________

Roman Shpount

=20

=20

On Mon, May 27, 2019 at 12:45 AM Martin Thomson <mt@lowentropy.net =
<mailto:mt@lowentropy.net> > wrote:

On Sat, May 25, 2019, at 10:03, Roman Shpount wrote:
> Sorry for the late question, but is there a scenario where party is=20
> communicating with attacker but believes that it communicates with=20
> patsy?

I don't think so.  I think that would require failures in parts of the =
system that we are assuming to be OK (the IdP in one case, the signaling =
system in the other).  The attacker can swap another entity into a call, =
but not vice versa.

> In all the described attacks, all I see is that one of the attacked=20
> parties is communicating with another but thinks it is communicating=20
> with the attacker. What is the risk associated with this? How this is=20
> different then just setting up a communication channel with attacker=20
> who is re-encoding the data?

This is different because a recipient is able to authenticate the source =
of the media as being the victim.  It is very much like relaying media =
by instantiating a new session and forwarding media, but if context (or =
ambient authority) is used in interpreting that data, the attacker might =
gain something.

Imagine the following conversation:=20

victim: I will buy 10.
response: Are you quite sure?
victim: Yes. Please charge to my account.

If the attacker is selling boxes of cookies and the target is selling =
refrigerators, the result might be surprising.


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Thank you =
for your review Roman.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Authors, =
since there are no unaddressed comments beyond the editorial ones from =
Flemming (<a =
href=3D"https://mailarchive.ietf.org/arch/msg/mmusic/ZewhLMuV3EJ6r6rVsCtS=
iF4TsaM">here</a>), and there seems to be no objections to proceed, =
please submit an update addressing Flemming=E2=80=99s comments that I =
will then submit for publication.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Thanks,<o:p></o:p></p><p =
class=3DMsoNormal>/Bo<o:p></o:p></p><p class=3DMsoNormal>MMUSIC =
co-chair<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b>From:</b> =
mmusic &lt;mmusic-bounces@ietf.org&gt; <b>On Behalf Of </b>Roman =
Shpount<br><b>Sent:</b> den 30 maj 2019 00:45<br><b>To:</b> Martin =
Thomson &lt;mt@lowentropy.net&gt;<br><b>Cc:</b> mmusic =
&lt;mmusic@ietf.org&gt;<br><b>Subject:</b> Re: [MMUSIC] Getting =
draft-ietf-mmusic-sdp-uks-04 ready for =
PubReq<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>I =
have reviewed the document and I have confirmed that the document is =
clear and my understanding is correct.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><p class=3DMsoNormal>Thank =
you, Martin.<o:p></o:p></p><div><p =
class=3DMsoNormal>_____________<o:p></o:p></p></div><div><div><div><p =
class=3DMsoNormal>Roman Shpount<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Mon, May 27, 2019 at 12:45 AM Martin Thomson &lt;<a =
href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt; =
wrote:<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5=
.0pt'><p class=3DMsoNormal>On Sat, May 25, 2019, at 10:03, Roman Shpount =
wrote:<br>&gt; Sorry for the late question, but is there a scenario =
where party is <br>&gt; communicating with attacker but believes that it =
communicates with <br>&gt; patsy?<br><br>I don't think so.&nbsp; I think =
that would require failures in parts of the system that we are assuming =
to be OK (the IdP in one case, the signaling system in the other).&nbsp; =
The attacker can swap another entity into a call, but not vice =
versa.<br><br>&gt; In all the described attacks, all I see is that one =
of the attacked <br>&gt; parties is communicating with another but =
thinks it is communicating <br>&gt; with the attacker. What is the risk =
associated with this? How this is <br>&gt; different then just setting =
up a communication channel with attacker <br>&gt; who is re-encoding the =
data?<br><br>This is different because a recipient is able to =
authenticate the source of the media as being the victim.&nbsp; It is =
very much like relaying media by instantiating a new session and =
forwarding media, but if context (or ambient authority) is used in =
interpreting that data, the attacker might gain =
something.<br><br>Imagine the following conversation: <br><br>victim: I =
will buy 10.<br>response: Are you quite sure?<br>victim: Yes. Please =
charge to my account.<br><br>If the attacker is selling boxes of cookies =
and the target is selling refrigerators, the result might be =
surprising.<o:p></o:p></p></blockquote></div></div></div></body></html>
------=_NextPart_001_00DD_01D51ADE.E05B2830--

------=_NextPart_000_00DC_01D51ADE.E05B2830
Content-Type: application/pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIVXjCCAyAw
ggIIoAMCAQICAR0wDQYJKoZIhvcNAQEFBQAwOTELMAkGA1UEBhMCRkkxDzANBgNVBAoTBlNvbmVy
YTEZMBcGA1UEAxMQU29uZXJhIENsYXNzMiBDQTAeFw0wMTA0MDYwNzI5NDBaFw0yMTA0MDYwNzI5
NDBaMDkxCzAJBgNVBAYTAkZJMQ8wDQYDVQQKEwZTb25lcmExGTAXBgNVBAMTEFNvbmVyYSBDbGFz
czIgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCQF0o1ncrwDZbHRPoWN/xIvb1/
gC01O+FvqGepvwMcTYxvMkfVQWikEwTBNQyahEP8XB3/ibPoFxjNkV/7iePqv05dfBsm03V57eaE
41flrSnE9Doo56V7hDZps/1edr2jLZnTkE4jKH0YY/FUOyaddluXQrL/rvBO7N05lU6DBn/nSUDI
xQGyVFpmHT38+ek8Cp6BuHDwAYvkI1R8yK74kB4AlnLUVM9hI7zq+50CldG2uXE6aQg/D7ThQseI
9T+YqKe6HOBxce9YV4FQelxrdEYOgwOYw46obvJ2Mm4ng8Jz89wY6LST6nVEawRgIHFXh53zvqCQ
Iz2KJOHaIdvDAgMBAAGjMzAxMA8GA1UdEwEB/wQFMAMBAf8wEQYDVR0OBAoECEqgqliE0148MAsG
A1UdDwQEAwIBBjANBgkqhkiG9w0BAQUFAAOCAQEAWs6H+RZyFVdLHdmb56ImMOyTZ9/WLdI0r/c4
pc6rFrmrL3w1y6zQD7RMK/yA72uMkV82dvfbsxsZ6vSyEf1hcUS/KLM6Hb+zQ+ifv9wxCHGwnY3W
NEcykMZlJPegSnwEc485bxeMcrW9S8h6+HuDwyhOnAnqZz+yZwQbwxTa+OdJJJHQHWr6YTnva+ch
dQYH2BK0ISBwQnGB2jyaNr6mWw1qbJofkXv5+e9Cuk5OnswMjZTc2UWcXuxCUGOu9F3EsRLcyjuo
Lp0UWgV1t+zXY+K6NbYECJHo2p2c9ma1GKwKplQmNDPSG8HUfxo6jguqMm7b/E8ln9kyx5ZacKzf
TDCCBX0wggRloAMCAQICEQCH7S4aKCZKxRmqOuu5DaLLMA0GCSqGSIb3DQEBCwUAMDkxCzAJBgNV
BAYTAkZJMQ8wDQYDVQQKEwZTb25lcmExGTAXBgNVBAMTEFNvbmVyYSBDbGFzczIgQ0EwHhcNMTQx
MjA1MDgxOTE1WhcNMjEwNDA1MTAyOTAwWjA3MRQwEgYDVQQKDAtUZWxpYVNvbmVyYTEfMB0GA1UE
AwwWVGVsaWFTb25lcmEgUm9vdCBDQSB2MTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIB
AMK+6yfwIaPzaSZVfp3FVRaRXP3vIb9TgHot0pGMYzHw7CTww6XScnwQbfQ3t+XmfHnqjLWCi65I
tqwA3GV17CpNX8GH9SBlK4GoRz6JI5UwFpB/6FcHSOcZrr9FZ7E3GwYq/t75rH2D+1665I+XZ75L
jo1kB1c4VWk0Nj0TSO9P4tNmHqTPGrdeNjPUtAa9GAH9d4RQAEX1jF3oI7x+/jXh7VB7qTCNGdMJ
jmhnXb88lxhTuylixcpecsHHltTbLaC0H2kD7OriUPEMPPCs81Mt8Bz17Ww5OXOAFshSsCPN4D7c
3TxHoLs1iuKYaIu+5b9y7tL6pe0S7fyYGKkmdtwoSxAgHNN/Fnct7W+A90m7UwW7XWjH1Mh1Fj+J
Wov3F0fUTPHSiXk+TT2YqGHeOh7S+F4D4MHJHIzTjU3TlTazN19jY5szFPAtJmtTfImMMsJu7D0h
ADnJoWjiUIMusDor8zagrC/kb2HCUQk5PotTubtn2txTuXZZNp1D5SDgPTJghSJRt8czu90VL6R4
pgd7gUY2BIbdeTXHlSw7sKMXNeVzH7RcWe/a6hBle3rQf5+ztCo3O3CLm1u5K7fsslESl1MpWtTw
EhDcTwK7EpIvYtQ/aUN8Ddb8WHUBiJ1YFkveupD/RwGJBmr2X7KQarMCpgKIv7NHfirZ1fpoeDVN
AgMBAAGjggGAMIIBfDBOBggrBgEFBQcBAQRCMEAwPgYIKwYBBQUHMAKGMmh0dHA6Ly9jYS50cnVz
dC50ZWxpYXNvbmVyYS5jb20vc29uZXJhY2xhc3MyY2EuY2VyMA8GA1UdEwEB/wQFMAMBAf8wGQYD
VR0gBBIwEDAOBgwrBgEEAYIPAgMBAQIwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBTwj1k4ALP1
j5qWDNXr+nuqF+gTEjCBuQYDVR0fBIGxMIGuMG+gbaBrhmlsZGFwOi8vY3JsLTEudHJ1c3QudGVs
aWFzb25lcmEuY29tL2NuPVNvbmVyYSUyMENsYXNzMiUyMENBLG89U29uZXJhLGM9Rkk/Y2VydGlm
aWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnkwO6A5oDeGNWh0dHA6Ly9jcmwtMi50cnVzdC50ZWxp
YXNvbmVyYS5jb20vc29uZXJhY2xhc3MyY2EuY3JsMBMGA1UdIwQMMAqACEqgqliE0148MA0GCSqG
SIb3DQEBCwUAA4IBAQAQ1elFTM6fGkQ/aRKdkUZicO3Cb9uzBJOpOtFctw+1El0/17lsjoVvJkZB
D3KnUobnrriFdAa+7FAN55KLmZeB/3Y2bG0bB4toSyaVHjOQnQY9M0dv8U852w0Q7GwchKfebLUI
bh9TMt2hI3Xc6j4knFTBUo7C1WAfO51K4bn1irmX6/Ej2VTgiOFsvOAny28W6enFSEQpSHw60VhN
fSttSqTOxyrRR/7kW7Y8yb/3DZDZ/dH6ZCfx/y+BNIv2NuSd85M9HXUzplXXohti4Ql/qeaMn6by
Ius6XlMWZZfkdVRvTuk2PkeC7UmAJ2+/DUWOPpawaytMXVfF4Hvxk34NMIIF7zCCA9egAwIBAgIQ
f/Mn4/Qs3Qmdp7lrbBs+RzANBgkqhkiG9w0BAQsFADBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwI
RXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMwHhcNMTcxMTA3
MDc0MTEyWhcNMjAxMTA3MDc0MTExWjBgMREwDwYDVQQKDAhFcmljc3NvbjESMBAGA1UEAwwJQm8g
QnVybWFuMSUwIwYJKoZIhvcNAQkBFhZiby5idXJtYW5AZXJpY3Nzb24uY29tMRAwDgYDVQQFEwdl
cmFiYnVyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsc7/WHPCPFn8MtdlAsXwPnl7
w0tSyOiso36JZ2OOE6Ztn7+8EmlhFZXV4ThcCyeJOZJG1CM8yIfs3k74gqyblT51tF89wOBarJVi
HQtcf9Jvp4OoYuhRqRda9hUeI8Z4tfqnXQ2OppGecD71Bg4nmovTzsEy3JM7Cd5A7foSGjdoDG5y
szolpQxx/+CJdYF9B2EfVgahCF8MYKCQhW40EaTJFPQm4/uZIQZPbxFw8PgpEIDV/IhG7izKr3gH
n/MNqtCD1yK+itPAlB7ZRAyhBR3qV/qpXU82koT8byMATE7iqmGZnx1k7XwbPE9rdli2cpTMVZ9y
R3nYSL3dnG09lwIDAQABo4IBvDCCAbgwSAYDVR0fBEEwPzA9oDugOYY3aHR0cDovL2NybC50cnVz
dC50ZWxpYS5jb20vZXJpY3Nzb25ubGluZGl2aWR1YWxjYXYzLmNybDCBggYIKwYBBQUHAQEEdjB0
MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIudHJ1c3QudGVsaWEuY29tMEgGCCsGAQUFBzAChjxo
dHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2My5j
ZXIwIQYDVR0RBBowGIEWYm8uYnVybWFuQGVyaWNzc29uLmNvbTBVBgNVHSAETjBMMEoGDCsGAQQB
gg8CAwEBEjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnkudHJ1c3QudGVsaWFzb25l
cmEuY29tL0NQUzAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwHQYDVR0OBBYEFOqTTQsD
K500lkyW3F7vkHyeBQtoMB8GA1UdIwQYMBaAFBx7GZ6XnHasID3Y3OORauPbLaZTMA4GA1UdDwEB
/wQEAwIFoDANBgkqhkiG9w0BAQsFAAOCAgEAy+psdt+fJhnRrYmmLqFMtDDk9CFzkdfjEQFRBNaz
KnIQmBKXGN7UevdGKMgZXjxvO1JljkvjfbPov7IycBac/6y6+kp4hHtkP6/hdPPADxFb2X5/58Wg
c4lWPTCvi8mn+bRtyrH9VAT03M7qIVMOpuq+OTzWVaRZphUT9mDamtcBjsX9UfQ5UsKpFb7Pt8eP
ZQf77LNHv0neNir7irCWgXdYHOksTzN0rCQG7YVyXWTaddlLiBvi2O18fsT3FgopnHhdv4HBG4LH
FtAjqs3PW9W4NhxgEH/1H+U7exFe9+6ZoTaN4D209Jt05Eq74hZSa39Wfnwg+tlr9c62RJ+z97ek
PDpenOo4SV0V4fL4O5d5cjdsFNIpXrrPt0pc5sXsYOTuIvsEgkdDDFP5Ezwu1IgMcX8RTvsEXai/
OIeEMq7lIzJ+h9/gd9rIn9dV4oYaY9X5u9M220+GCb0jcfWeBuQN4+2lbgevqRjU43Oa/cXYGCrQ
vDfdEqT09xMvxM/X1f8HXLw/ikyYlWf0QD4vJ8vE/fVi4NnjASUB8Uge/5daZE/Bg3axh2oywVGW
z8Ecx57ACKhaUUQ16B/Eq6WFalse9yoBP3pKkzkmWOAoLNPnko9TBZD1pQ1Z59AleTT6BmqKThzl
i58mANeLPJQ4JYxpopY6uun7xQZ2LADRi3gwggbCMIIEqqADAgECAhBTuH6D4ZyZKJOwm0kc7Ljr
MA0GCSqGSIb3DQEBCwUAMDcxFDASBgNVBAoMC1RlbGlhU29uZXJhMR8wHQYDVQQDDBZUZWxpYVNv
bmVyYSBSb290IENBIHYxMB4XDTE1MTAyNzEyMTY0NloXDTI1MTAyNzEyMTY0NlowRzELMAkGA1UE
BhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFs
IENBIHYzMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA7PLfAAC4UPKnu9hUt8aT9+PB
qjvUw0Y0tLPOXkO2NC0y2XZks9nJfpWKrNM30k5vu5norG4ZKlF5C+3xc6HuIiGQof1bmFGluNOw
mZQwl3rOJ+E6k0rqJJTerjj4WOxAvWVW1yC5S4Ubppk3Q3cYVVuC3qNGsBIXy3/fDL1sc8Ah8zI/
JumDpjY8fn/U3CRN6mgNKYrr0sZX6VXYgrpT05ZrJldkUgUgMKgbIWWEXEASA36pnb5GqD/RMzSg
Ie8o7YQtIaYB2cmTCLNHjaOL9j1JhNK4bvmbNJ7o58IZYzwNv/G/L/bRosQ9c27U+86DNjrdZnpy
aRaeMyVUn3SlYLaFqoObdh/xNF2NS8CXs/PVtO57HBKHMgZqQvsyQJisSocxFqiMj9VK2WhCBbvo
TvrNDZvLDlDGuE5RuKwFIpHOVOU5lCBgUUBsbpWIXwM6kmH/KC1DC5MtQzmvXkbt7KdBXUAxM0JZ
xf4dS+ACtTDpF9b0vny4DrwaOS0VNXyz1GUOxSqw1wup5dpXbxLZYx1rLRgZqr9uWhLwAPsq66ZQ
of5GL0gY72Ym8/Tm28MeMqku+/zRzdYsmclT9rOdgdgS3b6OMoc5Op0ZPEv/Mx2lFJAVK674ozw2
hiuRTVUmoqBr5AuyCoqCEyn32C7U/V7oqyqx5Yd1c5GsxuOqQFcCAwEAAaOCAbgwggG0MIGKBggr
BgEFBQcBAQR+MHwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9vY3NwLnRydXN0LnRlbGlhc29uZXJhLmNv
bTBLBggrBgEFBQcwAoY/aHR0cDovL3JlcG9zaXRvcnkudHJ1c3QudGVsaWFzb25lcmEuY29tL3Rl
bGlhc29uZXJhcm9vdGNhdjEuY2VyMBIGA1UdEwEB/wQIMAYBAf8CAQAwVQYDVR0gBE4wTDBKBgwr
BgEEAYIPAgMBAQIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlh
c29uZXJhLmNvbS9DUFMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC0zLnRydXN0LnRlbGlh
c29uZXJhLmNvbS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNybDAdBgNVHSUEFjAUBggrBgEFBQcDAgYI
KwYBBQUHAwQwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBQcexmel5x2rCA92NzjkWrj2y2mUzAf
BgNVHSMEGDAWgBTwj1k4ALP1j5qWDNXr+nuqF+gTEjANBgkqhkiG9w0BAQsFAAOCAgEAUFhr8dWM
O7Quq1dDyIynw8sWmpyF/jWSxBjpHUCyhltoFS7Q1CUBD0bOULWmYjmzRwme5pkjTFXpOJZLf9Ha
n1SBbrVcP0JMhRsAvfWZjcF0l/c/jqDMqBARxr8OUWOr0ZWa49Lir3QEs2C+CjGge5tzcLqzQ5pj
WxudrLkSGe+sAThDnXUWXGYk8udGZAamJ55drdw96AV9jWQkMrLIVHKkXVG5Etdx0wiAoTLk1fVt
Lcz11DiaCZSZVPZ3fdSIpIRhDqz8H4sVprPgvLBdK/ajdbiRsehCzzohay3zbXDDTDGwKkR8KUi8
Xt8HDZCRsb/U/C7MC4tVK0SEPOQCo6swZy0rI0RoGzICfsSrZ4JrxANeeSZqCn1A+w0Wz+iqdeP2
PVxW0f1rg4/OG2DSl3uB3Q3NT/lDGJtepti+i5CCKEZcdAOZoviu43sLhqsxSpGjzZidESwovuHe
P+O2bNwwtz1DTsXThBB3+JJHVjmkiLo900GITb/i7IBdLoo4gZms9s1BQ2tm3CJCmpA2XwBTOB6B
8/CtgWUWhyloXd3Wbmv7ZUoqqJFBV9g8Zh5mdZ+RzPTomgCFz/2aNsddI/2G9ZjN4tG6hmocZR2M
5f0MhBv3bo6d5XsLlYwiNJjw5GRqYb8cqqeCaPKkveBJzqgb8ToH7WLoOzmPRCmPlpAxggMCMIIC
/gIBATBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nz
b24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQf/Mn4/Qs3Qmdp7lrbBs+RzAJBgUrDgMCGgUAoIIBfDAY
BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xOTA2MDQxMjA3NDJaMCMG
CSqGSIb3DQEJBDEWBBSyviphNHruOVVetp4a4by9SyUBkjBDBgkqhkiG9w0BCQ8xNjA0MAoGCCqG
SIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCGjBqBgkrBgEEAYI3
EAQxXTBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nz
b24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQf/Mn4/Qs3Qmdp7lrbBs+RzBsBgsqhkiG9w0BCRACCzFd
oFswRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBO
TCBJbmRpdmlkdWFsIENBIHYzAhB/8yfj9CzdCZ2nuWtsGz5HMA0GCSqGSIb3DQEBAQUABIIBAGyS
/4u1OsqWsZ0qsUaPyFY+lfEYFbJr0L6ytcL5jT2s1kcQq1aqecI/+ElK95lcsYy05pzfVCgEmx1E
u+FTsxg+NN0jiPbjC4GWP+A/LMlI0XJ/ci9MbnR9+U7btF51opijGaCC3WHJm7HfdCkZbi8Ag1q7
fOUw194GxA6gQXQQ+eSi88bxzY0/1dapi6gBu9SYgTY9e6UQPu8liPThnYVeKZ/jIwar4i0LYq6Y
7+ClGw+NJhyjMWAnuUXsApGk2SowyLNmnL+zzTx97DrskKRtF3djXRg5ENg5w6doDlTol1XU9qQb
f0HIzJikaCkNwOYEb42BB3sJKnRuVXuDi5IAAAAAAAA=

------=_NextPart_000_00DC_01D51ADE.E05B2830--


From nobody Tue Jun  4 08:54:44 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FABF120025; Tue,  4 Jun 2019 08:54:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w-taZp4epXUb; Tue,  4 Jun 2019 08:54:32 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4EE4120089; Tue,  4 Jun 2019 08:54:26 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x54FsMQ1023560 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 4 Jun 2019 11:54:22 -0400
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic@ietf.org
References: <155922686313.22081.12209259015077736906.idtracker@ietfa.amsl.com> <df7509c8-5bba-fcc2-5d75-3cc179266cf8@alum.mit.edu> <20190603221717.GF1902@prolepsis.kaduk.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <35bf8aaf-f0ed-7d5e-471d-bc455eca5824@alum.mit.edu>
Date: Tue, 4 Jun 2019 11:54:21 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <20190603221717.GF1902@prolepsis.kaduk.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/JOLI44dIAauN6-f9dhzIUJxy1VU>
Subject: Re: [MMUSIC] Benjamin Kaduk's No Objection on draft-ietf-mmusic-rfc4566bis-35: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 15:54:35 -0000

Ben,

Just responding to a few points below. I think we are good now.

On 6/3/19 6:17 PM, Benjamin Kaduk wrote:

>>> I reviewed the diff from RFC 4566 but didn't make it quite all the way
>>> through the full document itself.  What I did find in that partial read
>>> suggests that a full read-through by the authors may find some lingering
>>> stale language or minor internal inconsistencies.
>>
>> There really hasn't been an attempt to thoroughly remove stale (dated)
>> language. Fundamentally this is a 21 year old document that has been tidied
>> up a bit. Anyone that started over today to define something new for the
>> same purpose would surely define something very different. We've only been
>> trying to fix areas where there has been confusion or ambiguity has been
>> found, or where new concerns (e.g., security) have needed to be addressed.
> 
> I think the RFC Editor is still going to be reviewing the whole thing for
> consistency with the current style/practices, so getting a headstart now
> would probably be more effective and save some time overall.

I prefer to wait and see. Doing this preemptively seems like a time sink.

>>> Section 4.3
>>>
>>> The usual security considerations about (potentially) referencing remote
>>> content would seem to apply.  Perhaps a RFC 3986 reference (or more)
>>> would be appropriate.
>>
>> Will adding a reference to [RFC3986] be sufficient?
> 
> I would prefer a note about "Use of URIs to indicate remote resources
> is subject to the security considerations from [RFC3986]", but just the
> reference would be okay.

OK, I'll do the long form.

>>> Section 5.x
>>>
>>> It's interesting to note that while the SDP attributes (Sections 6.x)
>>> got ABNF constructions for their values, the type descriptions here
>>> are still presented in a somewhat informal syntax (that, e.g., relies on
>>> implicitly stating that fields are whitespace-separated).
>>
>> It is an interesting point. The best rationale I can give is that *not*
>> having ABNF got to be a serious problem for attributes, because there are a
>> lot of them, and new ones get defined regularly (with complex syntax) and
>> the syntax was often recognized as being ambiguous. So we wanted to demand
>> ABNF for future extensions, and felt we should make the ones defined in this
>> document comply with that.
>>
>> OTOH, the other fields are revised/extended much more rarely, so it hasn't
>> been a problem. And so there is much less motivation to "rock the boat" by
>> changing the manner of defining them.
> 
> Indeed.  Changing this seems like more effort than it's worth, at this point
> in the process.  (But can I have whitespace in a comma-separated list?  I
> assume "no", but have been wrong on many occasions...)

In general whitespace is only allowed where *specifically* permitted.
  	Thanks,
	Paul


From nobody Tue Jun  4 09:05:08 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD61F120077; Tue,  4 Jun 2019 09:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2F_K1ZSsAbjC; Tue,  4 Jun 2019 09:05:05 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3998312004A; Tue,  4 Jun 2019 09:05:04 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x54G50E5024339 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 4 Jun 2019 12:05:01 -0400
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, The IESG <iesg@ietf.org>
Cc: "Flemming Andreasen (fandreas)" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "draft-ietf-mmusic-rfc4566bis@ietf.org" <draft-ietf-mmusic-rfc4566bis@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <155860096353.3948.17073187906064821991.idtracker@ietfa.amsl.com> <ce010b1b-3b24-ce89-f733-80dfc6799785@alum.mit.edu> <8696c636-4e13-5abb-e230-914f31eb4c5e@alum.mit.edu> <9A5FBBEE-00E0-48B9-B548-04AE6BB4D05E@cisco.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <6e1b7f60-7c16-a94b-acfc-17a5b0f02e59@alum.mit.edu>
Date: Tue, 4 Jun 2019 12:05:00 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <9A5FBBEE-00E0-48B9-B548-04AE6BB4D05E@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/CMXbIFfSucqyCoCYqIbO_W3aU1A>
Subject: Re: [MMUSIC]  =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ie?= =?utf-8?q?tf-mmusic-rfc4566bis-35=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 16:05:07 -0000

Éric,

On 6/3/19 6:55 PM, Eric Vyncke (evyncke) wrote:
> Such as in section 5, in the example SDP: " o=jdoe 2890844526 2890842807 IN IP4 198.51.100.1"

 From RFC5737:

    The blocks 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24 (TEST-NET-2),
    and 203.0.113.0/24 (TEST-NET-3) are provided for use in
    documentation.

Those are the right ones to use aren't they?

	Thanks,
	Paul

> -éric
> 
> ﻿On 03/06/2019, 15:48, "Paul Kyzivat" <pkyzivat@alum.mit.edu> wrote:
> 
>      Éric,
>      
>      On 5/28/19 5:32 PM, Paul Kyzivat wrote:
>      
>      > On 5/23/19 4:42 AM, Éric Vyncke via Datatracker wrote:
>      
>      >> -- Section 5 --
>      >>
>      >> When using IPv4 unicast addresses, please use the example ones.
>      >
>      > Good catch. I agree these need to be fixed. I'll have the scrub the
>      > document looking for them.
>      
>      After looking again I’m not finding any that need fixing. What did you
>      see that let you to raise this issue?
>      
>      	Thanks,
>      	Paul
>      
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> 


From nobody Tue Jun  4 09:14:33 2019
Return-Path: <evyncke@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 710F8120170; Tue,  4 Jun 2019 09:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=mpcn9JNQ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=XwLrSp74
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 MLXbT6IKy2Yl; Tue,  4 Jun 2019 09:14:24 -0700 (PDT)
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 2867F12019F; Tue,  4 Jun 2019 09:14:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2132; q=dns/txt; s=iport; t=1559664853; x=1560874453; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=tC8GG0YcSQh5eDeuoTuAKuc0SnEkB58/UaLE4TkFUEM=; b=mpcn9JNQfOPVWChtdbpA/w/UemOSVIiQsw3nwPFEbeihfoP+uWz5W9+X dGrAirmuM8ON/BtdTGRNtjL8tbsFEVC+U3FdmYSVptGDOW+XPPn0Bkcju Ln58Ioi7J05E8KntEykN8x56fcFqBzgZ73svcakjYMBb/MZ86AewdEwVW c=;
IronPort-PHdr: =?us-ascii?q?9a23=3AQ7wqKhI9p9MVwiGHINmcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeBvad2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUg?= =?us-ascii?q?Mdz8AfngguGsmAXEDlPfjhbCESF8VZX1gj9Ha+YgBY?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BIAACUl/Zc/4wNJK1mDg4BAQEEAQE?= =?us-ascii?q?HBAEBgVEHAQELAYE9UANqVSAECyiEFINHA4RSiiKCV5cvgS6BJANUCQEBAQw?= =?us-ascii?q?BARgLCgIBAYN6RgIXgjsjNAkOAQMBAQQBAQIBBG0cDIVLAQEBAwEBEBERDAE?= =?us-ascii?q?BLAsBDwIBCA4KAgImAgICJQsVBQsCBAENBSKDAAGBagMdAQIMnCQCgTiIX3G?= =?us-ascii?q?BMYJ5AQEFhQUYgg8DBoEMKAGLWReBQD+BOB+CTD6CYQEBgWEXgnMygiaOHpp?= =?us-ascii?q?rCQKCDpM2G4IjhnWNX4MfiWuWJAIEAgQFAg4BAQWBTziBWHAVOyoBgkGCDww?= =?us-ascii?q?XFIM5hRSFBDtygSmQKQEB?=
X-IronPort-AV: E=Sophos;i="5.60,550,1549929600"; d="scan'208";a="282732674"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Jun 2019 16:14:11 +0000
Received: from XCH-RCD-016.cisco.com (xch-rcd-016.cisco.com [173.37.102.26]) by alln-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id x54GEBwN026955 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 4 Jun 2019 16:14:11 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-016.cisco.com (173.37.102.26) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 4 Jun 2019 11:14:11 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 4 Jun 2019 12:14:05 -0400
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 4 Jun 2019 11:14:05 -0500
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=tC8GG0YcSQh5eDeuoTuAKuc0SnEkB58/UaLE4TkFUEM=; b=XwLrSp74UrpaYhhcHQfY1CcZR5L2Eng/F+hp1+23np7TCCwoFX/K3DDotbBY6aESwF3qmzeZkqoa1vU+hQ365WH3wGXnvLMKF/pEjGZxKniy3N3N7+VjXimus/oYPC4F6PFl0VlZ31Ke+XTyqgQdbZedoCb/VG6cdsEGoAyZLug=
Received: from MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) by MN2PR11MB3933.namprd11.prod.outlook.com (10.255.180.211) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.22; Tue, 4 Jun 2019 16:14:03 +0000
Received: from MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::1990:d953:1387:d1a7]) by MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::1990:d953:1387:d1a7%7]) with mapi id 15.20.1943.018; Tue, 4 Jun 2019 16:14:03 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, The IESG <iesg@ietf.org>
CC: "Flemming Andreasen (fandreas)" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "draft-ietf-mmusic-rfc4566bis@ietf.org" <draft-ietf-mmusic-rfc4566bis@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: =?utf-8?B?W01NVVNJQ10gw4lyaWMgVnluY2tlJ3MgTm8gT2JqZWN0aW9uIG9uIGRyYWZ0?= =?utf-8?Q?-ietf-mmusic-rfc4566bis-35:_(with_COMMENT)?=
Thread-Index: AQHVGl5vr0O03h3SNkKuGRrol/E1fqaKFK0AgAGVHAD//40tAA==
Date: Tue, 4 Jun 2019 16:14:03 +0000
Message-ID: <A6EF6181-10A5-4F67-A21C-9D02B8C817F7@cisco.com>
References: <155860096353.3948.17073187906064821991.idtracker@ietfa.amsl.com> <ce010b1b-3b24-ce89-f733-80dfc6799785@alum.mit.edu> <8696c636-4e13-5abb-e230-914f31eb4c5e@alum.mit.edu> <9A5FBBEE-00E0-48B9-B548-04AE6BB4D05E@cisco.com> <6e1b7f60-7c16-a94b-acfc-17a5b0f02e59@alum.mit.edu>
In-Reply-To: <6e1b7f60-7c16-a94b-acfc-17a5b0f02e59@alum.mit.edu>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.19.0.190512
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com; 
x-originating-ip: [2001:420:28b:1272:bc52:4999:db9c:a459]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 759f66d3-8d60-4d0e-a6f6-08d6e907a987
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MN2PR11MB3933; 
x-ms-traffictypediagnostic: MN2PR11MB3933:
x-ms-exchange-purlcount: 1
x-ld-processed: 5ae1af62-9505-4097-a69a-c1553ef7840e,ExtAddr
x-microsoft-antispam-prvs: <MN2PR11MB39335136DF09D854044E7FF1A9150@MN2PR11MB3933.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0058ABBBC7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39860400002)(346002)(136003)(366004)(376002)(199004)(189003)(73956011)(91956017)(486006)(66556008)(76116006)(66476007)(66946007)(46003)(58126008)(71200400001)(82746002)(68736007)(8936002)(64756008)(25786009)(6116002)(186003)(86362001)(99286004)(224303003)(81156014)(81166006)(110136005)(71190400001)(6246003)(316002)(54906003)(83716004)(7736002)(66446008)(229853002)(5660300002)(102836004)(6436002)(6512007)(4326008)(478600001)(256004)(2171002)(14454004)(6486002)(33656002)(446003)(11346002)(53936002)(36756003)(966005)(2616005)(476003)(2906002)(305945005)(6306002)(76176011)(53546011)(6506007); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3933; H:MN2PR11MB4144.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: w3QAlXvR7nOLh65vKDRshQE+fm/3HxUraFX0jI7a1RGjZjYNqNGS5ynE7GEN9v59riUxhPYzL7donwiLd73BbUPyZMKOs3O9nz7GkhfrLKwcuvKypzoQ43GnULXjdJr9k8uZKWJ+39z91ccNXbdkzqTuhJGhLM2FFTzx1lFKPoA4dTZNL7kutHJXe6YgB/P/vO5O7xb0B0Wf1sh51b/4bzzxEpxwutWKIDSyuXII0M5MgDPJSPepVeVGx1b9oVTHB1g2C9pxAyVxfrSngcXTmLDgs5qpohY6nCI4gogscEGRibA7px3IwiTa+Zjp1n5xNHBIqgKW752EjDjr8618c8aJ9pjrvbD3eTGol0EMH6nJUcAF3zgPGKbQ8VYXB0L7FDLurYfDGTZzAvW/so73O6BbfE+VWVRbgbK/KvIcDWI=
Content-Type: text/plain; charset="utf-8"
Content-ID: <DBD12DF69D1FCC4D98AB0C94A0E0EF07@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 759f66d3-8d60-4d0e-a6f6-08d6e907a987
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jun 2019 16:14:03.6057 (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: evyncke@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3933
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.26, xch-rcd-016.cisco.com
X-Outbound-Node: alln-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/G5YjJP6lKJ5JY5D9il86S7jj2Bw>
Subject: Re: [MMUSIC]  =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ie?= =?utf-8?q?tf-mmusic-rfc4566bis-35=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 16:14:27 -0000

TXkgYmFkIFBhdWwuIFRoYW5rcyBmb3IgaGF2aW5nIGNoZWNrZWQuIFdlIGFyZSBhbGwgY2xlYXIu
DQoNCi3DqXJpYw0KDQrvu79PbiAwNC8wNi8yMDE5LCAwOTowNSwgIlBhdWwgS3l6aXZhdCIgPHBr
eXppdmF0QGFsdW0ubWl0LmVkdT4gd3JvdGU6DQoNCiAgICDDiXJpYywNCiAgICANCiAgICBPbiA2
LzMvMTkgNjo1NSBQTSwgRXJpYyBWeW5ja2UgKGV2eW5ja2UpIHdyb3RlOg0KICAgID4gU3VjaCBh
cyBpbiBzZWN0aW9uIDUsIGluIHRoZSBleGFtcGxlIFNEUDogIiBvPWpkb2UgMjg5MDg0NDUyNiAy
ODkwODQyODA3IElOIElQNCAxOTguNTEuMTAwLjEiDQogICAgDQogICAgIEZyb20gUkZDNTczNzoN
CiAgICANCiAgICAgICAgVGhlIGJsb2NrcyAxOTIuMC4yLjAvMjQgKFRFU1QtTkVULTEpLCAxOTgu
NTEuMTAwLjAvMjQgKFRFU1QtTkVULTIpLA0KICAgICAgICBhbmQgMjAzLjAuMTEzLjAvMjQgKFRF
U1QtTkVULTMpIGFyZSBwcm92aWRlZCBmb3IgdXNlIGluDQogICAgICAgIGRvY3VtZW50YXRpb24u
DQogICAgDQogICAgVGhvc2UgYXJlIHRoZSByaWdodCBvbmVzIHRvIHVzZSBhcmVuJ3QgdGhleT8N
CiAgICANCiAgICAJVGhhbmtzLA0KICAgIAlQYXVsDQogICAgDQogICAgPiAtw6lyaWMNCiAgICA+
IA0KICAgID4gT24gMDMvMDYvMjAxOSwgMTU6NDgsICJQYXVsIEt5eml2YXQiIDxwa3l6aXZhdEBh
bHVtLm1pdC5lZHU+IHdyb3RlOg0KICAgID4gDQogICAgPiAgICAgIMOJcmljLA0KICAgID4gICAg
ICANCiAgICA+ICAgICAgT24gNS8yOC8xOSA1OjMyIFBNLCBQYXVsIEt5eml2YXQgd3JvdGU6DQog
ICAgPiAgICAgIA0KICAgID4gICAgICA+IE9uIDUvMjMvMTkgNDo0MiBBTSwgw4lyaWMgVnluY2tl
IHZpYSBEYXRhdHJhY2tlciB3cm90ZToNCiAgICA+ICAgICAgDQogICAgPiAgICAgID4+IC0tIFNl
Y3Rpb24gNSAtLQ0KICAgID4gICAgICA+Pg0KICAgID4gICAgICA+PiBXaGVuIHVzaW5nIElQdjQg
dW5pY2FzdCBhZGRyZXNzZXMsIHBsZWFzZSB1c2UgdGhlIGV4YW1wbGUgb25lcy4NCiAgICA+ICAg
ICAgPg0KICAgID4gICAgICA+IEdvb2QgY2F0Y2guIEkgYWdyZWUgdGhlc2UgbmVlZCB0byBiZSBm
aXhlZC4gSSdsbCBoYXZlIHRoZSBzY3J1YiB0aGUNCiAgICA+ICAgICAgPiBkb2N1bWVudCBsb29r
aW5nIGZvciB0aGVtLg0KICAgID4gICAgICANCiAgICA+ICAgICAgQWZ0ZXIgbG9va2luZyBhZ2Fp
biBJ4oCZbSBub3QgZmluZGluZyBhbnkgdGhhdCBuZWVkIGZpeGluZy4gV2hhdCBkaWQgeW91DQog
ICAgPiAgICAgIHNlZSB0aGF0IGxldCB5b3UgdG8gcmFpc2UgdGhpcyBpc3N1ZT8NCiAgICA+ICAg
ICAgDQogICAgPiAgICAgIAlUaGFua3MsDQogICAgPiAgICAgIAlQYXVsDQogICAgPiAgICAgIA0K
ICAgID4gDQogICAgPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KICAgID4gbW11c2ljIG1haWxpbmcgbGlzdA0KICAgID4gbW11c2ljQGlldGYub3JnDQog
ICAgPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYw0KICAgID4g
DQogICAgDQogICAgDQoNCg==


From nobody Tue Jun  4 09:35:52 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF5B4120148 for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 09:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x65EdQ68IbIm for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 09:35:49 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1638112019C for <mmusic@ietf.org>; Tue,  4 Jun 2019 09:35:15 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x54GZEh7026507 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Tue, 4 Jun 2019 12:35:14 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: mmusic@ietf.org
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu>
Message-ID: <122cfa2d-e1e6-18c9-5418-4e6fa1fe938f@alum.mit.edu>
Date: Tue, 4 Jun 2019 12:35:14 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/LMrDkWL7y6aBG2Wo9wWKfJzFmQw>
Subject: [MMUSIC] HELP: Definition of Media Type suitable for SDP ?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 16:35:51 -0000

I'm working on resolving IESG comments on rfc4566bis. I need some help 
on this one:

> On 5/30/19 8:50 AM, Alexey Melnikov via Datatracker wrote:
>> Alexey Melnikov has entered the following ballot position for
>> draft-ietf-mmusic-rfc4566bis-35: No Objection

...

>> In 3.1 “media types” need a Normative reference.

I've always struggled on this. The "simple" answer to refer to RFC2046. 
That indeed defines the notion of two part names for media types, and 
the IANA registry for those. But it is really focused primarily on those 
things that can exist as body parts in email, sip, etc. While that same 
registry is used for streaming media, it seems clear that not everything 
in that registry is suitable for use as streaming media.

Is there a more suitable reference for definition of the media types 
that SDP is concerned with?

	Thanks,
	Paul


From nobody Tue Jun  4 10:13:52 2019
Return-Path: <csp@csperkins.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1764E1200B3 for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 10:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qTruerwThsEy for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 10:13:49 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 74AE2120046 for <mmusic@ietf.org>; Tue,  4 Jun 2019 10:13:49 -0700 (PDT)
Received: from [82.152.40.192] (port=58340 helo=[192.168.1.139]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1hYD0K-0008GX-1s; Tue, 04 Jun 2019 18:13:48 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <122cfa2d-e1e6-18c9-5418-4e6fa1fe938f@alum.mit.edu>
Date: Tue, 4 Jun 2019 18:13:41 +0100
Cc: mmusic@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3394C534-6B5E-446C-B797-FF6B0A1435BA@csperkins.org>
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <122cfa2d-e1e6-18c9-5418-4e6fa1fe938f@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.104.11)
X-BlackCat-Spam-Score: 14
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9-u34W48LlHqFYCfF0lGsDtedMY>
Subject: Re: [MMUSIC] HELP: Definition of Media Type suitable for SDP ?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 17:13:51 -0000

> On 4 Jun 2019, at 17:35, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> I'm working on resolving IESG comments on rfc4566bis. I need some help =
on this one:
>=20
>> On 5/30/19 8:50 AM, Alexey Melnikov via Datatracker wrote:
>>> Alexey Melnikov has entered the following ballot position for
>>> draft-ietf-mmusic-rfc4566bis-35: No Objection
>=20
> ...
>=20
>>> In 3.1 =E2=80=9Cmedia types=E2=80=9D need a Normative reference.
>=20
> I've always struggled on this. The "simple" answer to refer to =
RFC2046. That indeed defines the notion of two part names for media =
types, and the IANA registry for those. But it is really focused =
primarily on those things that can exist as body parts in email, sip, =
etc. While that same registry is used for streaming media, it seems =
clear that not everything in that registry is suitable for use as =
streaming media.
>=20
> Is there a more suitable reference for definition of the media types =
that SDP is concerned with?


RFC 2046 is obsolete. I think the current version is RFC 6838.

Aside from that, I=E2=80=99m not sure I understand the concern. SDP is a =
general purpose signalling protocol and should be able to negotiate any =
media type. Specific rules for framed media, such as RTP payload =
formats, are described in Section 4.8 of RFC 6838, but those are a =
detail that doesn=E2=80=99t affect SDP.

Colin




--=20
Colin Perkins
https://csperkins.org/





From nobody Tue Jun  4 11:23:04 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1790C12036D for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 11:23:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tcPTcSHBpNfj for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 11:23:01 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B836A12036B for <mmusic@ietf.org>; Tue,  4 Jun 2019 11:23:01 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x54IMukf001708 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 4 Jun 2019 14:22:57 -0400
To: Colin Perkins <csp@csperkins.org>
Cc: mmusic@ietf.org
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <122cfa2d-e1e6-18c9-5418-4e6fa1fe938f@alum.mit.edu> <3394C534-6B5E-446C-B797-FF6B0A1435BA@csperkins.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <04d9a8a4-db77-84f5-47f2-585f3313cf60@alum.mit.edu>
Date: Tue, 4 Jun 2019 14:22:56 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <3394C534-6B5E-446C-B797-FF6B0A1435BA@csperkins.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/tWdlxaihlMgIycne3iBZAxxkmIw>
Subject: Re: [MMUSIC] HELP: Definition of Media Type suitable for SDP ?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 18:23:03 -0000

On 6/4/19 1:13 PM, Colin Perkins wrote:
>> On 4 Jun 2019, at 17:35, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>> I'm working on resolving IESG comments on rfc4566bis. I need some help on this one:
>>
>>> On 5/30/19 8:50 AM, Alexey Melnikov via Datatracker wrote:
>>>> Alexey Melnikov has entered the following ballot position for
>>>> draft-ietf-mmusic-rfc4566bis-35: No Objection
>>
>> ...
>>
>>>> In 3.1 “media types” need a Normative reference.
>>
>> I've always struggled on this. The "simple" answer to refer to RFC2046. That indeed defines the notion of two part names for media types, and the IANA registry for those. But it is really focused primarily on those things that can exist as body parts in email, sip, etc. While that same registry is used for streaming media, it seems clear that not everything in that registry is suitable for use as streaming media.
>>
>> Is there a more suitable reference for definition of the media types that SDP is concerned with?
> 
> 
> RFC 2046 is obsolete. I think the current version is RFC 6838.
> 
> Aside from that, I’m not sure I understand the concern. SDP is a general purpose signalling protocol and should be able to negotiate any media type. Specific rules for framed media, such as RTP payload formats, are described in Section 4.8 of RFC 6838, but those are a detail that doesn’t affect SDP.

Do you mean that it would be fine to use SDP to negotiate the streaming 
of multipart/mixed or text/plain over RTP?

	Thanks,
	Paul


From nobody Tue Jun  4 11:43:07 2019
Return-Path: <adam@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9000120418 for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 11:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 oQZCs8YQjRXr for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 11:43:03 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32EFC12040E for <mmusic@ietf.org>; Tue,  4 Jun 2019 11:43:03 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x54Igmlm081809 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 4 Jun 2019 13:42:50 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1559673770; bh=3wAMBvRvolprwE5/fqAycMWI1jXC1jFr/xCQEdvuD/M=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=rYkU+QU/kYNOuHWTRz3R/NUGHxXJgR4B18ZHSSTvZa704CVpx8sMZUPX3gG7j0nKP CV+ppcPBrVRZJSgnJMAdlmgdmNbTlp5lnuHm70AntRFK8b/1Bn12HSYJXKKoVaAJRn N85virDalt4WAW/BfACRZFIsKgpNzpZJqEk6mUpA=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Colin Perkins <csp@csperkins.org>
Cc: mmusic@ietf.org
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <122cfa2d-e1e6-18c9-5418-4e6fa1fe938f@alum.mit.edu> <3394C534-6B5E-446C-B797-FF6B0A1435BA@csperkins.org> <04d9a8a4-db77-84f5-47f2-585f3313cf60@alum.mit.edu>
From: Adam Roach <adam@nostrum.com>
Message-ID: <fd87f0ab-83ac-d923-ba35-9766dd63d83a@nostrum.com>
Date: Tue, 4 Jun 2019 13:42:43 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <04d9a8a4-db77-84f5-47f2-585f3313cf60@alum.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/NNvJtCiQms9YYSMChv-EqtWux7U>
Subject: Re: [MMUSIC] HELP: Definition of Media Type suitable for SDP ?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 18:43:05 -0000

[as an individual]

On 6/4/19 1:22 PM, Paul Kyzivat wrote:
> On 6/4/19 1:13 PM, Colin Perkins wrote:
>>> On 4 Jun 2019, at 17:35, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>> I'm working on resolving IESG comments on rfc4566bis. I need some 
>>> help on this one:
>>>
>>>> On 5/30/19 8:50 AM, Alexey Melnikov via Datatracker wrote:
>>>>> Alexey Melnikov has entered the following ballot position for
>>>>> draft-ietf-mmusic-rfc4566bis-35: No Objection
>>>
>>> ...
>>>
>>>>> In 3.1 “media types” need a Normative reference.
>>>
>>> I've always struggled on this. The "simple" answer to refer to 
>>> RFC2046. That indeed defines the notion of two part names for media 
>>> types, and the IANA registry for those. But it is really focused 
>>> primarily on those things that can exist as body parts in email, 
>>> sip, etc. While that same registry is used for streaming media, it 
>>> seems clear that not everything in that registry is suitable for use 
>>> as streaming media.
>>>
>>> Is there a more suitable reference for definition of the media types 
>>> that SDP is concerned with?
>>
>>
>> RFC 2046 is obsolete. I think the current version is RFC 6838.
>>
>> Aside from that, I’m not sure I understand the concern. SDP is a 
>> general purpose signalling protocol and should be able to negotiate 
>> any media type. Specific rules for framed media, such as RTP payload 
>> formats, are described in Section 4.8 of RFC 6838, but those are a 
>> detail that doesn’t affect SDP.
>
> Do you mean that it would be fine to use SDP to negotiate the 
> streaming of multipart/mixed or text/plain over RTP? 


As fine as it would be to send an email with a Content-Type of 
"application/sdp".

If someone came along and somehow defined semantics for these, then the 
syntax and registration processes would support that. But MIME doesn't 
do anything to ensure semantic consistency: there are infinite ways to 
send nonsense.

/a


From nobody Tue Jun  4 12:07:15 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A644C1201CC for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 12:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zP5OGowZC1Ao for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 12:07:11 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A127120388 for <mmusic@ietf.org>; Tue,  4 Jun 2019 12:07:10 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x54J79va005263 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Tue, 4 Jun 2019 15:07:09 -0400
To: mmusic@ietf.org
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <122cfa2d-e1e6-18c9-5418-4e6fa1fe938f@alum.mit.edu> <3394C534-6B5E-446C-B797-FF6B0A1435BA@csperkins.org> <04d9a8a4-db77-84f5-47f2-585f3313cf60@alum.mit.edu> <fd87f0ab-83ac-d923-ba35-9766dd63d83a@nostrum.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <19d609a1-5358-23a4-5d2c-a9939c31cc54@alum.mit.edu>
Date: Tue, 4 Jun 2019 15:07:09 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <fd87f0ab-83ac-d923-ba35-9766dd63d83a@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/rHrC_FCjV-MFfyv9LP0yLiLOP0A>
Subject: Re: [MMUSIC] HELP: Definition of Media Type suitable for SDP ?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 19:07:14 -0000

OK, thanks. Then I guess it is 6838.

	Thanks,
	Paul

On 6/4/19 2:42 PM, Adam Roach wrote:
> [as an individual]
> 
> On 6/4/19 1:22 PM, Paul Kyzivat wrote:
>> On 6/4/19 1:13 PM, Colin Perkins wrote:
>>>> On 4 Jun 2019, at 17:35, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>>> I'm working on resolving IESG comments on rfc4566bis. I need some 
>>>> help on this one:
>>>>
>>>>> On 5/30/19 8:50 AM, Alexey Melnikov via Datatracker wrote:
>>>>>> Alexey Melnikov has entered the following ballot position for
>>>>>> draft-ietf-mmusic-rfc4566bis-35: No Objection
>>>>
>>>> ...
>>>>
>>>>>> In 3.1 “media types” need a Normative reference.
>>>>
>>>> I've always struggled on this. The "simple" answer to refer to 
>>>> RFC2046. That indeed defines the notion of two part names for media 
>>>> types, and the IANA registry for those. But it is really focused 
>>>> primarily on those things that can exist as body parts in email, 
>>>> sip, etc. While that same registry is used for streaming media, it 
>>>> seems clear that not everything in that registry is suitable for use 
>>>> as streaming media.
>>>>
>>>> Is there a more suitable reference for definition of the media types 
>>>> that SDP is concerned with?
>>>
>>>
>>> RFC 2046 is obsolete. I think the current version is RFC 6838.
>>>
>>> Aside from that, I’m not sure I understand the concern. SDP is a 
>>> general purpose signalling protocol and should be able to negotiate 
>>> any media type. Specific rules for framed media, such as RTP payload 
>>> formats, are described in Section 4.8 of RFC 6838, but those are a 
>>> detail that doesn’t affect SDP.
>>
>> Do you mean that it would be fine to use SDP to negotiate the 
>> streaming of multipart/mixed or text/plain over RTP? 
> 
> 
> As fine as it would be to send an email with a Content-Type of 
> "application/sdp".
> 
> If someone came along and somehow defined semantics for these, then the 
> syntax and registration processes would support that. But MIME doesn't 
> do anything to ensure semantic consistency: there are infinite ways to 
> send nonsense.
> 
> /a
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Tue Jun  4 12:26:25 2019
Return-Path: <csp@csperkins.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DCB2120397 for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 12:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d32lk6jV8L3a for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 12:26:22 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (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 CEA871202E7 for <mmusic@ietf.org>; Tue,  4 Jun 2019 12:26:21 -0700 (PDT)
Received: from [81.187.2.149] (port=42312 helo=[192.168.0.81]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1hYF4e-0007WP-1S; Tue, 04 Jun 2019 20:26:20 +0100
From: Colin Perkins <csp@csperkins.org>
Message-Id: <2B30C58C-33DD-4801-9D2E-5E07C6E9BC17@csperkins.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9595F91B-62D5-46ED-8276-8650A5AD505F"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 4 Jun 2019 20:26:17 +0100
In-Reply-To: <04d9a8a4-db77-84f5-47f2-585f3313cf60@alum.mit.edu>
Cc: mmusic@ietf.org
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <122cfa2d-e1e6-18c9-5418-4e6fa1fe938f@alum.mit.edu> <3394C534-6B5E-446C-B797-FF6B0A1435BA@csperkins.org> <04d9a8a4-db77-84f5-47f2-585f3313cf60@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.104.11)
X-BlackCat-Spam-Score: 14
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/LN_mgXDev0sY7byjhVsgUJPbjrc>
Subject: Re: [MMUSIC] HELP: Definition of Media Type suitable for SDP ?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 19:26:24 -0000

--Apple-Mail=_9595F91B-62D5-46ED-8276-8650A5AD505F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On 4 Jun 2019, at 19:22, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> On 6/4/19 1:13 PM, Colin Perkins wrote:
>>> On 4 Jun 2019, at 17:35, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>> I'm working on resolving IESG comments on rfc4566bis. I need some =
help on this one:
>>>=20
>>>> On 5/30/19 8:50 AM, Alexey Melnikov via Datatracker wrote:
>>>>> Alexey Melnikov has entered the following ballot position for
>>>>> draft-ietf-mmusic-rfc4566bis-35: No Objection
>>>=20
>>> ...
>>>=20
>>>>> In 3.1 =E2=80=9Cmedia types=E2=80=9D need a Normative reference.
>>>=20
>>> I've always struggled on this. The "simple" answer to refer to =
RFC2046. That indeed defines the notion of two part names for media =
types, and the IANA registry for those. But it is really focused =
primarily on those things that can exist as body parts in email, sip, =
etc. While that same registry is used for streaming media, it seems =
clear that not everything in that registry is suitable for use as =
streaming media.
>>>=20
>>> Is there a more suitable reference for definition of the media types =
that SDP is concerned with?
>> RFC 2046 is obsolete. I think the current version is RFC 6838.
>> Aside from that, I=E2=80=99m not sure I understand the concern. SDP =
is a general purpose signalling protocol and should be able to negotiate =
any media type. Specific rules for framed media, such as RTP payload =
formats, are described in Section 4.8 of RFC 6838, but those are a =
detail that doesn=E2=80=99t affect SDP.
>=20
> Do you mean that it would be fine to use SDP to negotiate the =
streaming of multipart/mixed or text/plain over RTP?


I doubt the media type for multipart/mixed defines how it should be =
carried over RTP so it wouldn=E2=80=99t make sense to negotiate that, =
but SDP should be able to express it as an option.=20

Sending text/plain in RTP might make sense as a timed text format, =
although the text payload formats we have include richer information and =
use different media types.

Colin





--=20
Colin Perkins
https://csperkins.org/





--Apple-Mail=_9595F91B-62D5-46ED-8276-8650A5AD505F
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""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
4 Jun 2019, at 19:22, Paul Kyzivat &lt;<a =
href=3D"mailto:pkyzivat@alum.mit.edu" =
class=3D"">pkyzivat@alum.mit.edu</a>&gt; wrote:</div><div class=3D""><div =
class=3D"">On 6/4/19 1:13 PM, Colin Perkins wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D"">On 4 Jun 2019, at 17:35, Paul Kyzivat &lt;<a =
href=3D"mailto:pkyzivat@alum.mit.edu" =
class=3D"">pkyzivat@alum.mit.edu</a>&gt; wrote:<br class=3D"">I'm =
working on resolving IESG comments on rfc4566bis. I need some help on =
this one:<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">On 5/30/19 8:50 AM, Alexey Melnikov via Datatracker wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D"">Alexey Melnikov has =
entered the following ballot position for<br =
class=3D"">draft-ietf-mmusic-rfc4566bis-35: No Objection<br =
class=3D""></blockquote></blockquote><br class=3D"">...<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D"">In 3.1 =E2=80=9Cmedia types=E2=80=9D need a Normative =
reference.<br class=3D""></blockquote></blockquote><br class=3D"">I've =
always struggled on this. The "simple" answer to refer to RFC2046. That =
indeed defines the notion of two part names for media types, and the =
IANA registry for those. But it is really focused primarily on those =
things that can exist as body parts in email, sip, etc. While that same =
registry is used for streaming media, it seems clear that not everything =
in that registry is suitable for use as streaming media.<br class=3D""><br=
 class=3D"">Is there a more suitable reference for definition of the =
media types that SDP is concerned with?<br class=3D""></blockquote>RFC =
2046 is obsolete. I think the current version is RFC 6838.<br =
class=3D"">Aside from that, I=E2=80=99m not sure I understand the =
concern. SDP is a general purpose signalling protocol and should be able =
to negotiate any media type. Specific rules for framed media, such as =
RTP payload formats, are described in Section 4.8 of RFC 6838, but those =
are a detail that doesn=E2=80=99t affect SDP.<br =
class=3D""></blockquote><br class=3D"">Do you mean that it would be fine =
to use SDP to negotiate the streaming of multipart/mixed or text/plain =
over RTP?<br class=3D""></div></div></blockquote></div><div class=3D""><br=
 class=3D"webkit-block-placeholder"></div><div class=3D"">I doubt the =
media type for multipart/mixed defines how it should be carried over RTP =
so it wouldn=E2=80=99t make sense to negotiate that, but SDP should be =
able to express it as an option.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Sending text/plain in RTP <i =
class=3D"">might</i> make sense as a timed text format, although the =
text payload formats we have include richer information and use =
different media types.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Colin</div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""><br class=3D"">--&nbsp;<br class=3D"">Colin =
Perkins<br class=3D""><a href=3D"https://csperkins.org/" =
class=3D"">https://csperkins.org/</a><br class=3D""><br class=3D""><br =
class=3D""><br class=3D"">

</div>
<br class=3D""></body></html>=

--Apple-Mail=_9595F91B-62D5-46ED-8276-8650A5AD505F--


From nobody Tue Jun  4 12:44:27 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0554F1205E0 for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 12:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1rqvXSOdxWW4 for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 12:44:23 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C72E81205D9 for <mmusic@ietf.org>; Tue,  4 Jun 2019 12:44:22 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x54JiHkc007978 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 4 Jun 2019 15:44:18 -0400
To: Colin Perkins <csp@csperkins.org>
Cc: mmusic@ietf.org
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <122cfa2d-e1e6-18c9-5418-4e6fa1fe938f@alum.mit.edu> <3394C534-6B5E-446C-B797-FF6B0A1435BA@csperkins.org> <04d9a8a4-db77-84f5-47f2-585f3313cf60@alum.mit.edu> <2B30C58C-33DD-4801-9D2E-5E07C6E9BC17@csperkins.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <08b58e81-9eb0-1e00-aa27-648cd6c02ff7@alum.mit.edu>
Date: Tue, 4 Jun 2019 15:44:17 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <2B30C58C-33DD-4801-9D2E-5E07C6E9BC17@csperkins.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3GSmfBoQp-MYoKtc0yLcvkOgAeM>
Subject: Re: [MMUSIC] HELP: Definition of Media Type suitable for SDP ?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 19:44:25 -0000

On 6/4/19 3:26 PM, Colin Perkins wrote:
>> On 4 Jun 2019, at 19:22, Paul Kyzivat <pkyzivat@alum.mit.edu 
>> <mailto:pkyzivat@alum.mit.edu>> wrote:
>> On 6/4/19 1:13 PM, Colin Perkins wrote:
>>>> On 4 Jun 2019, at 17:35, Paul Kyzivat <pkyzivat@alum.mit.edu 
>>>> <mailto:pkyzivat@alum.mit.edu>> wrote:
>>>> I'm working on resolving IESG comments on rfc4566bis. I need some 
>>>> help on this one:
>>>>
>>>>> On 5/30/19 8:50 AM, Alexey Melnikov via Datatracker wrote:
>>>>>> Alexey Melnikov has entered the following ballot position for
>>>>>> draft-ietf-mmusic-rfc4566bis-35: No Objection
>>>>
>>>> ...
>>>>
>>>>>> In 3.1 “media types” need a Normative reference.
>>>>
>>>> I've always struggled on this. The "simple" answer to refer to 
>>>> RFC2046. That indeed defines the notion of two part names for media 
>>>> types, and the IANA registry for those. But it is really focused 
>>>> primarily on those things that can exist as body parts in email, 
>>>> sip, etc. While that same registry is used for streaming media, it 
>>>> seems clear that not everything in that registry is suitable for use 
>>>> as streaming media.
>>>>
>>>> Is there a more suitable reference for definition of the media types 
>>>> that SDP is concerned with?
>>> RFC 2046 is obsolete. I think the current version is RFC 6838.
>>> Aside from that, I’m not sure I understand the concern. SDP is a 
>>> general purpose signalling protocol and should be able to negotiate 
>>> any media type. Specific rules for framed media, such as RTP payload 
>>> formats, are described in Section 4.8 of RFC 6838, but those are a 
>>> detail that doesn’t affect SDP.
>>
>> Do you mean that it would be fine to use SDP to negotiate the 
>> streaming of multipart/mixed or text/plain over RTP?
> 
> I doubt the media type for multipart/mixed defines how it should be 
> carried over RTP so it wouldn’t make sense to negotiate that, but SDP 
> should be able to express it as an option.

That is what I was getting at: ISTM that only those that specify how 
they can be carried over RTP, or some other <proto> valid in an m-line, 
are appropriate for use.

	Thanks,
	Paul


From nobody Tue Jun  4 12:48:34 2019
Return-Path: <csp@csperkins.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C11E412063A for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 12:48:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tf1-PEPFunLI for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 12:48:17 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (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 54E0E1205F3 for <mmusic@ietf.org>; Tue,  4 Jun 2019 12:48:17 -0700 (PDT)
Received: from [81.187.2.149] (port=35932 helo=[192.168.0.81]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1hYFPr-0001e6-D1; Tue, 04 Jun 2019 20:48:15 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <08b58e81-9eb0-1e00-aa27-648cd6c02ff7@alum.mit.edu>
Date: Tue, 4 Jun 2019 20:48:14 +0100
Cc: mmusic@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <13F48BF1-45B5-4C3F-AD86-2CFECDB69626@csperkins.org>
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <122cfa2d-e1e6-18c9-5418-4e6fa1fe938f@alum.mit.edu> <3394C534-6B5E-446C-B797-FF6B0A1435BA@csperkins.org> <04d9a8a4-db77-84f5-47f2-585f3313cf60@alum.mit.edu> <2B30C58C-33DD-4801-9D2E-5E07C6E9BC17@csperkins.org> <08b58e81-9eb0-1e00-aa27-648cd6c02ff7@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.104.11)
X-BlackCat-Spam-Score: 14
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Z0XSLA2cnOL6JZ8dJquipvawmKk>
Subject: Re: [MMUSIC] HELP: Definition of Media Type suitable for SDP ?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 19:48:32 -0000

> On 4 Jun 2019, at 20:44, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> On 6/4/19 3:26 PM, Colin Perkins wrote:
>>> On 4 Jun 2019, at 19:22, Paul Kyzivat <pkyzivat@alum.mit.edu =
<mailto:pkyzivat@alum.mit.edu>> wrote:
>>> On 6/4/19 1:13 PM, Colin Perkins wrote:
>>>>> On 4 Jun 2019, at 17:35, Paul Kyzivat <pkyzivat@alum.mit.edu =
<mailto:pkyzivat@alum.mit.edu>> wrote:
>>>>> I'm working on resolving IESG comments on rfc4566bis. I need some =
help on this one:
>>>>>=20
>>>>>> On 5/30/19 8:50 AM, Alexey Melnikov via Datatracker wrote:
>>>>>>> Alexey Melnikov has entered the following ballot position for
>>>>>>> draft-ietf-mmusic-rfc4566bis-35: No Objection
>>>>>=20
>>>>> ...
>>>>>=20
>>>>>>> In 3.1 =E2=80=9Cmedia types=E2=80=9D need a Normative reference.
>>>>>=20
>>>>> I've always struggled on this. The "simple" answer to refer to =
RFC2046. That indeed defines the notion of two part names for media =
types, and the IANA registry for those. But it is really focused =
primarily on those things that can exist as body parts in email, sip, =
etc. While that same registry is used for streaming media, it seems =
clear that not everything in that registry is suitable for use as =
streaming media.
>>>>>=20
>>>>> Is there a more suitable reference for definition of the media =
types that SDP is concerned with?
>>>> RFC 2046 is obsolete. I think the current version is RFC 6838.
>>>> Aside from that, I=E2=80=99m not sure I understand the concern. SDP =
is a general purpose signalling protocol and should be able to negotiate =
any media type. Specific rules for framed media, such as RTP payload =
formats, are described in Section 4.8 of RFC 6838, but those are a =
detail that doesn=E2=80=99t affect SDP.
>>>=20
>>> Do you mean that it would be fine to use SDP to negotiate the =
streaming of multipart/mixed or text/plain over RTP?
>> I doubt the media type for multipart/mixed defines how it should be =
carried over RTP so it wouldn=E2=80=99t make sense to negotiate that, =
but SDP should be able to express it as an option.
>=20
> That is what I was getting at: ISTM that only those that specify how =
they can be carried over RTP, or some other <proto> valid in an m-line, =
are appropriate for use.


Not everything makes sense to use, but a general purpose negotiation =
protocol should allow you to express the possibility.

--=20
Colin Perkins
https://csperkins.org/





From nobody Tue Jun  4 16:34:07 2019
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0F471203BE for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 16:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hyoxeDJDw5nO for <mmusic@ietfa.amsl.com>; Tue,  4 Jun 2019 16:34:04 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 3152E12017C for <mmusic@ietf.org>; Tue,  4 Jun 2019 16:34:04 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id u22so13656767pfm.3 for <mmusic@ietf.org>; Tue, 04 Jun 2019 16:34:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=f8sAi2c31A8tTrp3GzQvGIp6k18E7B29J6QlwRj8NvA=; b=xDRL+AIgK9M6ocxKcPn3vBSObN6xkXOuzrk9E2Ea1FgOZMb9NAfw0Ro6ga1Zuwr8gi LfG07DlDUVJBWXSGN+fdUyccqDNf0r6nAousyHMFK8ry065hkseFXSvieU7ETrQeCIyA 2QANjC3UVHABuYfMCL33d11MKMLQstIfgdgUorLbFCbC3P8KwHmrv/yDLB/GmBCiAIPI /dJFssNMJB4oxZJKcdwnPZSAacegXSY7fvAL4vXRyA00WPKng5zblIPdNEB4WUl+3F2o bcH0aCxywKEDbPLAZRhaOoLwp+NuDP5opyopq4Hb6Q4d+YxwRa70UQbi7T8rS+B/dKJh yElQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=f8sAi2c31A8tTrp3GzQvGIp6k18E7B29J6QlwRj8NvA=; b=kmjf3jzVzd9X7QBNs2abgJfcbIm93JsCCsHsGWuaovdiH7h2Srux17j0RumIOeYnFw 1Su9FHiTqNt4hnA2qLMXFviWtXkRP4EzmrQdHPztvILSGzbFfUiAMD47hYZNqcHo8GKd iyrpRv9nsvyBLHL8pqhmDnhgonKd+hTSTtndo2E8MjshUzuKlshevw9igYXum37DuF9j 66DJJU5bEtbP5x65CWjguGLq5rmAjWVs330budSMDjt5PTGLRwc/xHlENKFyddJV/d5+ 9lQQKcae5xkk4ALp4wnOaD7L0aYr09R8gWUSUGHR947ms637aYNETFvzpLrNtZbYXuhq pFdQ==
X-Gm-Message-State: APjAAAU+qDpaKdLjHtJXh6PnmXpyjU/xywZ5HtOSfQy1f/WBXNn7YVi7 0RQS9iWqhaeNi7a3EbTpHLoyRkP9FpY=
X-Google-Smtp-Source: APXvYqydQ0UVl+Fo8NigFwfSdLm1S/8Pq4yqSOPBRfrnMRVz1AJxpxQ3mSYARt6DgFRSMTZWer/Vbg==
X-Received: by 2002:a17:90a:bc08:: with SMTP id w8mr2892108pjr.45.1559691243421;  Tue, 04 Jun 2019 16:34:03 -0700 (PDT)
Received: from mail-pf1-f174.google.com (mail-pf1-f174.google.com. [209.85.210.174]) by smtp.gmail.com with ESMTPSA id d7sm8630304pfq.0.2019.06.04.16.34.02 for <mmusic@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jun 2019 16:34:02 -0700 (PDT)
Received: by mail-pf1-f174.google.com with SMTP id x15so3859886pfq.0 for <mmusic@ietf.org>; Tue, 04 Jun 2019 16:34:02 -0700 (PDT)
X-Received: by 2002:aa7:8193:: with SMTP id g19mr34265595pfi.162.1559691242397;  Tue, 04 Jun 2019 16:34:02 -0700 (PDT)
MIME-Version: 1.0
References: <155961945536.24598.17183487212731948165@ietfa.amsl.com> <CAMRcRGT-hmz2YmGS4Q-dCdpopQtv_g++Mb41CWjjpZEz4XE9rQ@mail.gmail.com>
In-Reply-To: <CAMRcRGT-hmz2YmGS4Q-dCdpopQtv_g++Mb41CWjjpZEz4XE9rQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 4 Jun 2019 19:33:52 -0400
X-Gmail-Original-Message-ID: <CAD5OKxvVhUL6VeBS8moZYa0o+Gr5C9PjpXiY0d+4gU9+6ws8=A@mail.gmail.com>
Message-ID: <CAD5OKxvVhUL6VeBS8moZYa0o+Gr5C9PjpXiY0d+4gU9+6ws8=A@mail.gmail.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Cc: mmusic WG <mmusic@ietf.org>, Flemming Andreasen <fandreas@cisco.com>
Content-Type: multipart/alternative; boundary="00000000000076693f058a87eabe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/qpLxk1VeiUNvGEDql3mokwjf7p8>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-32.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2019 23:34:07 -0000

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

I think there is a misspelling in section 3.2.5: scontrolling  should be
controlling.
_____________
Roman Shpount


On Mon, Jun 3, 2019 at 11:39 PM Suhas Nandakumar <suhasietf@gmail.com>
wrote:

> Version 32 addresses Flemming's review comments, IDNits error
>
> Thanks
> Suhas
>
> On Mon, Jun 3, 2019 at 8:37 PM <internet-drafts@ietf.org> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Multiparty Multimedia Session Control WG
>> of the IETF.
>>
>>         Title           : Session Description Protocol (SDP) Offer/Answer
>> procedures for Interactive Connectivity Establishment (ICE)
>>         Authors         : Marc Petit-Huguenin
>>                           Suhas Nandakumar
>>                           Ari Keranen
>>         Filename        : draft-ietf-mmusic-ice-sip-sdp-32.txt
>>         Pages           : 42
>>         Date            : 2019-06-03
>>
>> Abstract:
>>    This document describes Session Description Protocol (SDP) Offer/
>>    Answer procedures for carrying out Interactive Connectivity
>>    Establishment (ICE) between the agents.
>>
>>    This document obsoletes RFC 5245.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-32
>> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-32
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-32
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>

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

<div dir=3D"ltr">I think there is a misspelling in section 3.2.5: scontroll=
ing =C2=A0should be controlling.<div>_____________<br></div><div><div><div =
dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature">Ro=
man Shpount</div></div><br></div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Mon, Jun 3, 2019 at 11:39 PM Suhas Nand=
akumar &lt;<a href=3D"mailto:suhasietf@gmail.com">suhasietf@gmail.com</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div d=
ir=3D"ltr">Version 32 addresses Flemming&#39;s review comments, IDNits erro=
r<div><br></div><div>Thanks</div><div>Suhas</div></div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jun 3, 2019 at 8:3=
7 PM &lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">inte=
rnet-drafts@ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Multiparty Multimedia Session Control WG o=
f the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Session Description Protocol (SDP) Offer/Answer procedures for Interactive=
 Connectivity Establishment (ICE)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Marc=
 Petit-Huguenin<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Suhas Nandakumar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ari Keranen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mmusic-ice-sip-sdp-32.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 42<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2019-06-03<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes Session Description Protocol (SDP) Off=
er/<br>
=C2=A0 =C2=A0Answer procedures for carrying out Interactive Connectivity<br=
>
=C2=A0 =C2=A0Establishment (ICE) between the agents.<br>
<br>
=C2=A0 =C2=A0This document obsoletes RFC 5245.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/"=
 rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draf=
t-ietf-mmusic-ice-sip-sdp/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-32" re=
l=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-m=
music-ice-sip-sdp-32</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-=
sdp-32" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d=
oc/html/draft-ietf-mmusic-ice-sip-sdp-32</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-ice-sip-sd=
p-32" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?url=
2=3Ddraft-ietf-mmusic-ice-sip-sdp-32</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div>
</blockquote></div>

--00000000000076693f058a87eabe--


From nobody Tue Jun  4 20:00:12 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DC2071200B6; Tue,  4 Jun 2019 20:00:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mmusic@ietf.org
Message-ID: <155970360383.28108.14776146965459424084@ietfa.amsl.com>
Date: Tue, 04 Jun 2019 20:00:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/cixFlWfPP35JI2tJD7PBBTFPLxg>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-uks-05.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 03:00:04 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : Unknown Key Share Attacks on uses of TLS with the Session Description Protocol (SDP)
        Authors         : Martin Thomson
                          Eric Rescorla
	Filename        : draft-ietf-mmusic-sdp-uks-05.txt
	Pages           : 18
	Date            : 2019-06-04

Abstract:
   This document describes unknown key-share attacks on the use of
   Datagram Transport Layer Security for the Secure Real-Time Transport
   Protocol (DTLS-SRTP).  Similar attacks are described on the use of
   DTLS-SRTP with the identity bindings used in Web Real-Time
   Communications (WebRTC) and SIP identity.  These attacks are
   difficult to mount, but they cause a victim to be mislead about the
   identity of a communicating peer.  Simple mitigation techniques are
   defined for each.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-uks/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-sdp-uks-05
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-sdp-uks-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-uks-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Jun  4 20:01:06 2019
Return-Path: <mt@lowentropy.net>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5662C120120; Tue,  4 Jun 2019 20:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=isGGkTS0; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=EUSFdkqR
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 FS3LzZqoLk2V; Tue,  4 Jun 2019 20:00:50 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6837120633; Tue,  4 Jun 2019 20:00:49 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D41B522409; Tue,  4 Jun 2019 23:00:48 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Tue, 04 Jun 2019 23:00:48 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type:content-transfer-encoding; s=fm2; bh=nA 9kP+xKGYe3u7HCenC1IKGfFceTl0YQpLHDfSHYeZo=; b=isGGkTS0Yqt9eiEKJu uqrbMaiUVAm4CR15vIQ/8X0xsVkZCCsqqgOXeT3ePU19ccznE6o3Ss+UvGtAtcKR rx3wINY32FFLMzwxRtK5+LWqdl1qVb/+7v09ekXROAGTJSuYP8xGDi85izRzr9SF xvrFatn+Zn0LGMXtF2HI+MyBLMo6tKdcjSOVtQNf/svTkx/2Qf8CHSzLhD4aUGdr D6A0FG+hiLgQegfRtqDhBnR8kivUnDnLcY3Zy2yLi8NHl06zibwHF9yLfPvh4I1u 2x2bZ+8X4X92eBiiC61WdqzjOddcC9xiB6VYjIuvblmoVd9LqTaXB0EKQNQxNOmm tZ3w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=nA9kP+xKGYe3u7HCenC1IKGfFceTl0YQpLHDfSHYe Zo=; b=EUSFdkqRNEMY9XbDhySE/As9YWhzPK4Cr02DNjboLZMt+yP7Lnri4Eag2 b7MaYWZ4r4dBzRuJ4KQyRMHhyS1JDfoGsCrdLR8TMgLNKLZ+sx5Fh1R/z+7yjL5v W56Sxa3/n5r1oqbhjhynii19bIFJc+xa7zwlyDPe4aRxJqUHu0MJLemw2fwesxfe FYrHUj46ysSMXC8KD9YEJs6i5qCkorAJDBztGq7Mgb2cHtd6UO8sSgTKcAc0fFWk 9AHiEm6kZJAV67Leit/qiqMvYUXzOhS280Ny9x+4kuxkvoZqhwlJAZRQILT+0LgK 5jv51FrODW64VtlOvik8fbXB+d6Vg==
X-ME-Sender: <xms:YDD3XOVG6xN1UXFxicZwDD4FqhP0GUgckg8TJLZaCJX6rz-XA9jnMw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudeguddgieehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgfgsehtqhertderreejnecuhfhrohhmpedfofgr rhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigvnhhtrhhophihrdhnvghtqeenuc ffohhmrghinhepihgvthhfrdhorhhgnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmthes lhhofigvnhhtrhhophihrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:YDD3XITUDtecPm77l8nAX6hiRHKFZTm-rGCgm90mocavfNtLvXqE4w> <xmx:YDD3XEL-YZl5fCpjCIAUXd6JzcQxPjjoc3GTsy7Xy97Sn0axlZNyZw> <xmx:YDD3XB1HbHWwVe18YAtAkcmxPBbLvjZHmqE5Urn6pY0G4uApEy2lFg> <xmx:YDD3XBOQYWh-w05Ci8KSWmvULxc1pahhlLdfRZiozdsyXCb2hVpEhg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 18191E00A1; Tue,  4 Jun 2019 23:00:48 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.6-650-g74f8db0-fmstable-20190604v3
Mime-Version: 1.0
Message-Id: <2ed5021f-f9cf-4d48-a0a5-5045984168cd@www.fastmail.com>
In-Reply-To: <HE1PR07MB32599C3B63042968BBCBCDD98D150@HE1PR07MB3259.eurprd07.prod.outlook.com>
References: <HE1PR07MB3259C69803BEB1913483C7328D0B0@HE1PR07MB3259.eurprd07.prod.outlook.com> <CAD5OKxvfBSs7Yu5xyD7LXgfEW_5-2c_u39935mF8XOTxvLxixg@mail.gmail.com> <1cebc5fa-81ac-455c-9619-48d273177e5b@www.fastmail.com> <CAD5OKxtt8Attax=9-LnndF8RD2D0eFzZVSh-PqCC=9485eTJPw@mail.gmail.com> <HE1PR07MB32599C3B63042968BBCBCDD98D150@HE1PR07MB3259.eurprd07.prod.outlook.com>
Date: Wed, 05 Jun 2019 13:00:50 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: "Bo Burman" <bo.burman@ericsson.com>, "Roman Shpount" <roman@telurix.com>,  "draft-ietf-mmusic-sdp-uks.authors@ietf.org, " <draft-ietf-mmusic-sdp-uks.authors@ietf.org>
Cc: mmusic <mmusic@ietf.org>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/QxyFvdEv1qsihahwlqSr3ZWWS7Y>
Subject: Re: [MMUSIC] Getting draft-ietf-mmusic-sdp-uks-04 ready for PubReq
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 03:01:05 -0000

-05 is up.  Thanks.

On Tue, Jun 4, 2019, at 22:07, Bo Burman wrote:
> Thank you for your review Roman.
>=20
>=20
> Authors, since there are no unaddressed comments beyond the editorial=20=

> ones from Flemming (here=20
> <https://mailarchive.ietf.org/arch/msg/mmusic/ZewhLMuV3EJ6r6rVsCtSiF4T=
saM>), and there seems to be no objections to proceed, please submit an =
update addressing Flemming=E2=80=99s comments that I will then submit fo=
r publication.
>=20
>=20
> Thanks,
>=20
> /Bo
>=20
> MMUSIC co-chair
>=20
>=20
>=20
> *From:* mmusic <mmusic-bounces@ietf.org> *On Behalf Of *Roman Shpount
> *Sent:* den 30 maj 2019 00:45
> *To:* Martin Thomson <mt@lowentropy.net>
> *Cc:* mmusic <mmusic@ietf.org>
> *Subject:* Re: [MMUSIC] Getting draft-ietf-mmusic-sdp-uks-04 ready for=
 PubReq
>=20
>=20
> I have reviewed the document and I have confirmed that the document is=
=20
> clear and my understanding is correct.
>=20
>=20
> Thank you, Martin.
>=20
> _____________
>=20
> Roman Shpount
>=20
>=20
>=20
> On Mon, May 27, 2019 at 12:45 AM Martin Thomson <mt@lowentropy.net> wr=
ote:
>=20
> > On Sat, May 25, 2019, at 10:03, Roman Shpount wrote:
> > > Sorry for the late question, but is there a scenario where party i=
s=20
> > > communicating with attacker but believes that it communicates with=
=20
> > > patsy?
> >=20
> > I don't think so. I think that would require failures in parts of th=
e system that we are assuming to be OK (the IdP in one case, the signali=
ng system in the other). The attacker can swap another entity into a cal=
l, but not vice versa.
> >=20
> > > In all the described attacks, all I see is that one of the attacke=
d=20
> > > parties is communicating with another but thinks it is communicati=
ng=20
> > > with the attacker. What is the risk associated with this? How this=
 is=20
> > > different then just setting up a communication channel with attack=
er=20
> > > who is re-encoding the data?
> >=20
> > This is different because a recipient is able to authenticate the so=
urce of the media as being the victim. It is very much like relaying med=
ia by instantiating a new session and forwarding media, but if context (=
or ambient authority) is used in interpreting that data, the attacker mi=
ght gain something.
> >=20
> > Imagine the following conversation:=20
> >=20
> > victim: I will buy 10.
> > response: Are you quite sure?
> > victim: Yes. Please charge to my account.
> >=20
> > If the attacker is selling boxes of cookies and the target is sellin=
g refrigerators, the result might be surprising.
>=20
> Attachments:
> * smime.p7s


From nobody Tue Jun  4 23:40:18 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 655091200B6; Tue,  4 Jun 2019 23:40:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mmusic@ietf.org
Message-ID: <155971681131.27950.9976819490377868894@ietfa.amsl.com>
Date: Tue, 04 Jun 2019 23:40:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/DSc5GQcwvKRw4lemT4XiMhqg1D0>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-33.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 06:40:12 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : Session Description Protocol (SDP) Offer/Answer procedures for Interactive Connectivity Establishment (ICE)
        Authors         : Marc Petit-Huguenin
                          Suhas Nandakumar
                          Ari Keranen
	Filename        : draft-ietf-mmusic-ice-sip-sdp-33.txt
	Pages           : 42
	Date            : 2019-06-04

Abstract:
   This document describes Session Description Protocol (SDP) Offer/
   Answer procedures for carrying out Interactive Connectivity
   Establishment (ICE) between the agents.

   This document obsoletes RFC 5245.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-33
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-33

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-33


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Jun  4 23:42:40 2019
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 270081200B6; Tue,  4 Jun 2019 23:42:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 1Pkd8obum1au; Tue,  4 Jun 2019 23:42:37 -0700 (PDT)
Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (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 E274712003E; Tue,  4 Jun 2019 23:42:36 -0700 (PDT)
Received: by mail-vs1-xe2a.google.com with SMTP id g24so13033059vso.8; Tue, 04 Jun 2019 23:42:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=s0R+DZ9ApKunWa5/GpjhZ6h/FnwC0j/mghElsdauPVM=; b=ekl6wbFsxEQJtqQ5DKBgoWDVT4QbD5dNMmqx7ddCJ0IQBNmQ4LeE6TTH0DgRJmOncT 0tsHv0ZzFyfb1omUEQ/vZ5Ageb7WKnOuorrn/zSTzOdcNYVrOiPSmi3AezYrMzdPlx4q DmZjUiWNtI0oJ701CNh+JMtSWb2CNaKWAoboE6nYZLfQNt2nnAe2WbVfzkYWs0LthyQu QNgisoGgvJUorB9gOVzKRLpkjEZFTpaD/ccL6WaEYmW582+GfT7giW/KphcYAmm/9RyX Fwlv28rc3gWJabXwsB8nRXd3t0avIg7Mppyx4TyxaGfszMi0BrARtEdEtkPdMFZSpiGv NjGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=s0R+DZ9ApKunWa5/GpjhZ6h/FnwC0j/mghElsdauPVM=; b=F+u8EdF4EeeDMWMF34I3FS+wdkHZ8I2DyDT20/h4kto0/eR3TIehGrv0YltTJtKCjo D+APY2bdl33r4jIqdZnpWegqffvuo/XGPd3AMxm0v+umZaMLr6UPjpM2tDObogOCW1cE AeMNMC4rOMovCp76aTyCbsV+jcrChgoP/WMWMrBcrnb4kqQRTSxEu5vJqGPzyKdgggOy ltP/JfKgPdb17a92pU8DxcBR10HGYWRVqIi42Gfh5F/SBq6cLjCjZHwZ6ZZIstmzmLe5 QYu0QxJUvaejGI/15eHWDOZ88dOrRRnJq2xmEpUpVYW4Ld+ILbjq+/QD/Or80jrse/vp KQsw==
X-Gm-Message-State: APjAAAUV2lSaSfTqx8C1XI8t9dDaJt++jubCDGiQC6gLFu6fLpvC5YzO Lzvwxd3RSjAhCxP4lvgbhNMmSFsZupGpoEJouD9mz92b
X-Google-Smtp-Source: APXvYqwzsh732rjRhKIFVGDNu0pTfND6gVPkDlK3bJZM0w9571Cmal0nNYe0T1XO2QIDbR3ehxBfi1N+DCdJRtL4jNA=
X-Received: by 2002:a67:c503:: with SMTP id e3mr9308867vsk.230.1559716955806;  Tue, 04 Jun 2019 23:42:35 -0700 (PDT)
MIME-Version: 1.0
References: <155971681131.27950.9976819490377868894@ietfa.amsl.com>
In-Reply-To: <155971681131.27950.9976819490377868894@ietfa.amsl.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Tue, 4 Jun 2019 23:42:25 -0700
Message-ID: <CAMRcRGQJkkCm5gyPrCfGpGLei3P9-r8afp29NYY80UfcRk1Atw@mail.gmail.com>
To: mmusic WG <mmusic@ietf.org>
Cc: i-d-announce@ietf.org
Content-Type: multipart/alternative; boundary="00000000000019e2ac058a8de739"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/qY5Bd6ZfX_i0juGEh6UBLlU_69w>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-33.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 06:42:39 -0000

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

version 33 fixes last few IDNits and typo

cheers
Suhas

On Tue, Jun 4, 2019 at 11:41 PM <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multiparty Multimedia Session Control WG
> of the IETF.
>
>         Title           : Session Description Protocol (SDP) Offer/Answer
> procedures for Interactive Connectivity Establishment (ICE)
>         Authors         : Marc Petit-Huguenin
>                           Suhas Nandakumar
>                           Ari Keranen
>         Filename        : draft-ietf-mmusic-ice-sip-sdp-33.txt
>         Pages           : 42
>         Date            : 2019-06-04
>
> Abstract:
>    This document describes Session Description Protocol (SDP) Offer/
>    Answer procedures for carrying out Interactive Connectivity
>    Establishment (ICE) between the agents.
>
>    This document obsoletes RFC 5245.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-33
> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-33
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-33
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">version 33 fixes last few IDNits and typo<div><br></div><d=
iv>cheers</div><div>Suhas</div></div><br><div class=3D"gmail_quote"><div di=
r=3D"ltr" class=3D"gmail_attr">On Tue, Jun 4, 2019 at 11:41 PM &lt;<a href=
=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</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"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Multiparty Multimedia Session Control WG o=
f the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Session Description Protocol (SDP) Offer/Answer procedures for Interactive=
 Connectivity Establishment (ICE)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Marc=
 Petit-Huguenin<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Suhas Nandakumar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ari Keranen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mmusic-ice-sip-sdp-33.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 42<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2019-06-04<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes Session Description Protocol (SDP) Off=
er/<br>
=C2=A0 =C2=A0Answer procedures for carrying out Interactive Connectivity<br=
>
=C2=A0 =C2=A0Establishment (ICE) between the agents.<br>
<br>
=C2=A0 =C2=A0This document obsoletes RFC 5245.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/"=
 rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draf=
t-ietf-mmusic-ice-sip-sdp/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-33" re=
l=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-m=
music-ice-sip-sdp-33</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-=
sdp-33" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d=
oc/html/draft-ietf-mmusic-ice-sip-sdp-33</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-ice-sip-sd=
p-33" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?url=
2=3Ddraft-ietf-mmusic-ice-sip-sdp-33</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div>

--00000000000019e2ac058a8de739--


From nobody Wed Jun  5 08:25:25 2019
Return-Path: <noreply@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6997412008D; Wed,  5 Jun 2019 08:25:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Bo Burman via Datatracker <noreply@ietf.org>
To: <adam@nostrum.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: mmusic-chairs@ietf.org, bo.burman@ericsson.com, iesg-secretary@ietf.org, mmusic@ietf.org, Bo Burman <bo.burman@ericsson.com>
Message-ID: <155974832342.22281.448479607806603489.idtracker@ietfa.amsl.com>
Date: Wed, 05 Jun 2019 08:25:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/G2bVAQbD0Z-bLEOrcyKaMMZ5udY>
Subject: [MMUSIC] Publication has been requested for draft-ietf-mmusic-sdp-uks-05
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 15:25:24 -0000

Bo Burman has requested publication of draft-ietf-mmusic-sdp-uks-05 as Proposed Standard on behalf of the MMUSIC working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-uks/


From nobody Wed Jun  5 10:59:52 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAA1F1201D6 for <mmusic@ietfa.amsl.com>; Wed,  5 Jun 2019 10:59:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vLZxAevIPYxy for <mmusic@ietfa.amsl.com>; Wed,  5 Jun 2019 10:59:48 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A618120043 for <mmusic@ietf.org>; Wed,  5 Jun 2019 10:59:48 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x55HxkxN032338 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Wed, 5 Jun 2019 13:59:46 -0400
To: IETF MMUSIC WG <mmusic@ietf.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <836be93f-726d-d22e-4d37-7934fead9cd7@alum.mit.edu>
Date: Wed, 5 Jun 2019 13:59:45 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xAKjQ5EHrrOnC0kq95lgF4KY6GE>
Subject: [MMUSIC] HELP: multiple unicast addresses for layered encoding in SDP ???
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 17:59:51 -0000

While working on rfc4566bis I discovered something I didn't know was 
there, and question:

    Multiple addresses or "c=" lines MAY be specified on a per media
    description basis only if they provide multicast addresses for
    different layers in a hierarchical or layered encoding scheme.
    Multiple addresses or "c=" lines MUST NOT be specified at session
    level.

    The slash notation for multiple addresses described above MUST NOT be
    used for IP unicast addresses.

The syntax doesn't allow the slash format for unicast addresses. But I 
didn't realize that multiple c= lines also aren't allowed. I could swear 
there have been discussions of using this.

Am I just confused? Are multiple unicast c= lines in use in the wild for 
layered encoding?

	Thanks,
	Paul


From nobody Wed Jun  5 11:04:54 2019
Return-Path: <bernard.aboba@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8576312021F for <mmusic@ietfa.amsl.com>; Wed,  5 Jun 2019 11:04:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 hZIcZ8iyN6Ba for <mmusic@ietfa.amsl.com>; Wed,  5 Jun 2019 11:04:50 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 3143A120043 for <mmusic@ietf.org>; Wed,  5 Jun 2019 11:04:50 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id 131so11450749ljf.4 for <mmusic@ietf.org>; Wed, 05 Jun 2019 11:04:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=C81mAvWAPTZuSy3CCI1nP1ZPZVrW9cf4bwEHyjDe4KU=; b=rSadBwpN5Jq7ET0ybqSrz3XGtELbDuLEUXSQPtw9FmccHJftxrt+YbQvLhphLshgPc mtMBytHI/wSdIpZe5oYLGmqh/2WYfsatnAyn9ScUbfyMYlwtJtEBmcXjcFht2PKSYfra kpLtNjUUWngth4HbK/QNALlfKYdDR2ulfMMKeC7vb1XhahFJCsifrtx59a+uIyegsfyR 98OehhMvtjhFDfh02C7mCTUaC8aiyq4VO1Laqi0xUj7Ep2hwpKaS7rKUcOfOYOit0bug F990tlN7zYSahBsDGgB1qFbIfIqti8aph3+kTPgxVW8HrFrK3VKMtaMd8V02Y3R1guEF Edmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=C81mAvWAPTZuSy3CCI1nP1ZPZVrW9cf4bwEHyjDe4KU=; b=sDamCuW7AHh5bOj7ZdqFfAMqm6InA/Q9b02q8yCgERSw8KMa7PZJpsS37GrwokJSuS lawXIx38XluL+Y26gRvvfnkqkFOm6xIofHbHUjD3SgCzN7i+hFaTe9aPIy3hNI5Mviu0 CM9IaD4zV8JmZm1oQCUy0jQ3LJZBegZBsnJYxsc+you/8vlq2az2hQy/cq+xhTUA6EpD 5Bpuk0agvPX9uxPO7WgS/6oBCKojF6UShqvjzooDuDxn43Qq60FwMuBDbNHGZBl2obfd U0WDBC3Qdfg8+LfffNN0Gw7h5aPqoJG1+maXVg92z7hI5neqpFD0lvEXmONO6yjfhcp+ BXlw==
X-Gm-Message-State: APjAAAVdMa6N7Tt2R21Fn5SNEX/U31SKytKxemKpnq33bUwDlMGDv8Ov NSYF7ALrTQKUvMOEgqUarIrHdBn+wBXrBxtZMS4=
X-Google-Smtp-Source: APXvYqxX5IRQJmpPAncik+efNf/CF+9qzEoPS06GnmWQL8UxYRCzlI2jtE8EA08wF80otwxU13Rz+TmDOzQCS7oKO1w=
X-Received: by 2002:a2e:98d5:: with SMTP id s21mr3764554ljj.142.1559757887817;  Wed, 05 Jun 2019 11:04:47 -0700 (PDT)
MIME-Version: 1.0
References: <836be93f-726d-d22e-4d37-7934fead9cd7@alum.mit.edu>
In-Reply-To: <836be93f-726d-d22e-4d37-7934fead9cd7@alum.mit.edu>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Wed, 5 Jun 2019 11:04:36 -0700
Message-ID: <CAOW+2dsGNeMsw5h8rjNiYfCP4c2Mu_7+YDWzS3BEUF31R+VYLg@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: IETF MMUSIC WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d6cadb058a976e61"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Zl0IxC3-wuNrAP-6q3_3wUWqeyM>
Subject: Re: [MMUSIC] HELP: multiple unicast addresses for layered encoding in SDP ???
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 18:04:53 -0000

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

Paul --

I'm not aware of multiple unicast c= lines being used for layered coding,
although there are implementations using multiple SSRCs with a single IP
address.

On Wed, Jun 5, 2019 at 10:59 AM Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> While working on rfc4566bis I discovered something I didn't know was
> there, and question:
>
>     Multiple addresses or "c=" lines MAY be specified on a per media
>     description basis only if they provide multicast addresses for
>     different layers in a hierarchical or layered encoding scheme.
>     Multiple addresses or "c=" lines MUST NOT be specified at session
>     level.
>
>     The slash notation for multiple addresses described above MUST NOT be
>     used for IP unicast addresses.
>
> The syntax doesn't allow the slash format for unicast addresses. But I
> didn't realize that multiple c= lines also aren't allowed. I could swear
> there have been discussions of using this.
>
> Am I just confused? Are multiple unicast c= lines in use in the wild for
> layered encoding?
>
>         Thanks,
>         Paul
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">Paul --<div><br></div><div>I&#39;m not aware of multiple u=
nicast c=3D lines being used for layered coding, although there are impleme=
ntations using multiple SSRCs with a single IP address.=C2=A0</div></div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, =
Jun 5, 2019 at 10:59 AM Paul Kyzivat &lt;<a href=3D"mailto:pkyzivat@alum.mi=
t.edu">pkyzivat@alum.mit.edu</a>&gt; wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">While working on rfc4566bis I discovered someth=
ing I didn&#39;t know was <br>
there, and question:<br>
<br>
=C2=A0 =C2=A0 Multiple addresses or &quot;c=3D&quot; lines MAY be specified=
 on a per media<br>
=C2=A0 =C2=A0 description basis only if they provide multicast addresses fo=
r<br>
=C2=A0 =C2=A0 different layers in a hierarchical or layered encoding scheme=
.<br>
=C2=A0 =C2=A0 Multiple addresses or &quot;c=3D&quot; lines MUST NOT be spec=
ified at session<br>
=C2=A0 =C2=A0 level.<br>
<br>
=C2=A0 =C2=A0 The slash notation for multiple addresses described above MUS=
T NOT be<br>
=C2=A0 =C2=A0 used for IP unicast addresses.<br>
<br>
The syntax doesn&#39;t allow the slash format for unicast addresses. But I =
<br>
didn&#39;t realize that multiple c=3D lines also aren&#39;t allowed. I coul=
d swear <br>
there have been discussions of using this.<br>
<br>
Am I just confused? Are multiple unicast c=3D lines in use in the wild for =
<br>
layered encoding?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Thanks,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Paul<br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div>

--000000000000d6cadb058a976e61--


From nobody Wed Jun  5 12:06:22 2019
Return-Path: <ali.begen@networked.media>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9018C120144 for <mmusic@ietfa.amsl.com>; Wed,  5 Jun 2019 12:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=networked-media.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oJ76PYjRSGuY for <mmusic@ietfa.amsl.com>; Wed,  5 Jun 2019 12:06:19 -0700 (PDT)
Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (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 BBE1E120075 for <mmusic@ietf.org>; Wed,  5 Jun 2019 12:06:18 -0700 (PDT)
Received: by mail-wr1-x42b.google.com with SMTP id e16so12334344wrn.1 for <mmusic@ietf.org>; Wed, 05 Jun 2019 12:06:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked-media.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=N+9MiFFGrqVwsnmcLuBmFCe47KTIdKsJV3MmbUXxEvc=; b=DT9+ZPSiHRah45rbki11sgt6lQE7Cf/qOA6Foss+QwaJoZOqn82jmjOoD8f8BwXlxi LPOGJQIpY8AR9FozPa6MIWSHeJxdH6+Gg4aJuLRu4BNRZbMQrA5uRBO1AjLJHuPnvuYi cP2broaGhYsoRJJtlyf4oFSMtkw+wLkcRcMkkoC/7nDfBkkujYPokImPVqfsBniNgClK LU0HK1SfHHLZ4YUcNVz1tfYsVn7HpDs72nWQQBpAuvTdEiprSrWWL0N6WpCuQMpFa/Zx w7FLLTfBzMR/uxn+b8GvOIrb5qcdxH23SABy7BDVA32XtPO5oZ7IhzvRTk8NluXkuK/l e+tA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=N+9MiFFGrqVwsnmcLuBmFCe47KTIdKsJV3MmbUXxEvc=; b=T04RSBxn1VpJBE/cefcHYQ1msrJJ9IJfIvGaHoZERvBQZPRu3D0Pvyn09rPx+2UzD0 NkGdgkvxVtayun/sl1v+PO71zd+SLrzOW4Fa5ndZtPL4/ewKJjY1nAiYON3wwN8KKs6m NlWp48C/yw8sM4lo7uQzrmLRiEftVmqtozqAttVJOy3hZRurajKpzsRb3tTx20soimYM d2Bq5xceVHqhHAHqdCD70sjtbr0OjxN97KY99YVTrFCzoxQEyqEb4m/v80L+lKFmP/y3 0miGeNgrvnMElOVtXXJgf+eam65NI4xRk+1SeK/gjQDqTPvI2rnZR9N+JVuaL+C26E+e dUfw==
X-Gm-Message-State: APjAAAV3Xx4+V+tZdQZmposz8Vj5JT/BcuaaWfZf11jopAyRh+1KAFz7 KpqdtT8T/swRDUUD20V9ujVXpw==
X-Google-Smtp-Source: APXvYqx6ueQkKyADdn8KI6dVMFaEbFlo8oi4uWTox6mKgLFb4mkht2AmiWx1kk5EthQbGsZYV7FKgg==
X-Received: by 2002:adf:e58f:: with SMTP id l15mr4060982wrm.8.1559761576980; Wed, 05 Jun 2019 12:06:16 -0700 (PDT)
Received: from [192.168.1.202] ([85.105.47.236]) by smtp.gmail.com with ESMTPSA id x11sm18194574wmg.23.2019.06.05.12.06.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Jun 2019 12:06:16 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: "Ali C. Begen" <ali.begen@networked.media>
In-Reply-To: <836be93f-726d-d22e-4d37-7934fead9cd7@alum.mit.edu>
Date: Wed, 5 Jun 2019 22:06:14 +0300
Cc: IETF MMUSIC WG <mmusic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <719E8387-E205-400B-B9DA-23962DAEA597@networked.media>
References: <836be93f-726d-d22e-4d37-7934fead9cd7@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/0mT2lB61aXiiMZ1-RSrankvJHhU>
Subject: Re: [MMUSIC] HELP: multiple unicast addresses for layered encoding in SDP ???
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 19:06:21 -0000

> On Jun 5, 2019, at 8:59 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>=20
> Am I just confused? Are multiple unicast c=3D lines in use in the wild =
for layered encoding?

Not to my knowledge.

-acbegen=


From nobody Wed Jun  5 15:50:11 2019
Return-Path: <adam@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43A7212011D for <mmusic@ietfa.amsl.com>; Wed,  5 Jun 2019 15:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.68
X-Spam-Level: 
X-Spam-Status: No, score=-1.68 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 rzpAG2wSO_LG for <mmusic@ietfa.amsl.com>; Wed,  5 Jun 2019 15:50:07 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30752120043 for <mmusic@ietf.org>; Wed,  5 Jun 2019 15:50:07 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x55Mo4le053515 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 5 Jun 2019 17:50:05 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1559775006; bh=/2TSbJuohrhaOJrdvS+c1RgUeIrRmf0kjB1N09l7mwg=; h=To:From:Subject:Date; b=V0GWmsL1nbSEgETUAKPTkkxDs/T4cdPQFV5mvW9gzeXEQxZLNH3/QxgYefteNoLTn sRFU2wCpGY7i2ePveMr0wjeFDDbSswOTraURXeL0VTgeBjnN6Cbe0wHlMeWOHnadKn 8zMm33diHE93veggMg0icacaYmAu88ShOG5EkBlk=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: draft-ietf-mmusic-sdp-uks@tools.ietf.org, "mmusic@ietf.org" <mmusic@ietf.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <2b3651f8-c2f2-fcd2-1883-16de305391f3@nostrum.com>
Date: Wed, 5 Jun 2019 17:49:59 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9ezwC218CghvH454X_qjOarXQRo>
Subject: [MMUSIC] AD Review: draft-ietf-mmusic-sdp-uks
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 22:50:09 -0000

This is my AD review for draft-ietf-mmusic-sdp-uks. It is
uncharacteristically short, as I have already reviewed earlier
versions of this document and provided feedback to the authors.

None of my comment preclude putting the document into IETF last call.
Please address them along with any other comments that may arise
during the last call process.

Thanks!

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

Please update the abstract to indicate that this document updates
RFC 8122.

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

§1:

 >  entity.  A successful attack leads to the creation of sessions where
 >  peers are confused about the identify of the participants.

Nit: "...identity of..."

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

§4.3:

 >  This is considered benign since these protocols are usually
 >  distinguishable.

Suggest: s/usually/designed to be/

(there are specific forbidden PT values reserved to avoid collisions
with RTCP -- 72 through 76, to be specific)


From nobody Wed Jun  5 15:56:59 2019
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4491F120025; Wed,  5 Jun 2019 15:56:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
CC: mmusic-chairs@ietf.org, adam@nostrum.com, mmusic@ietf.org, draft-ietf-mmusic-sdp-uks@ietf.org, Bo Burman <bo.burman@ericsson.com>, bo.burman@ericsson.com
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <155977540923.22286.7643038643537338814.idtracker@ietfa.amsl.com>
Date: Wed, 05 Jun 2019 15:56:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/mCWH_Gyz9EnyN2qnRvhkEq63Yjw>
Subject: [MMUSIC] Last Call: <draft-ietf-mmusic-sdp-uks-05.txt> (Unknown Key Share Attacks on uses of TLS with the Session Description Protocol (SDP)) to Proposed Standard
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 22:56:49 -0000

The IESG has received a request from the Multiparty Multimedia Session
Control WG (mmusic) to consider the following document: - 'Unknown Key Share
Attacks on uses of TLS with the Session Description
   Protocol (SDP)'
  <draft-ietf-mmusic-sdp-uks-05.txt> as Proposed Standard

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

Abstract


   This document describes unknown key-share attacks on the use of
   Datagram Transport Layer Security for the Secure Real-Time Transport
   Protocol (DTLS-SRTP).  Similar attacks are described on the use of
   DTLS-SRTP with the identity bindings used in Web Real-Time
   Communications (WebRTC) and SIP identity.  These attacks are
   difficult to mount, but they cause a victim to be mislead about the
   identity of a communicating peer.  Simple mitigation techniques are
   defined for each.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-uks/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-uks/ballot/


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





From nobody Wed Jun  5 16:01:30 2019
Return-Path: <mt@lowentropy.net>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEC43120025 for <mmusic@ietfa.amsl.com>; Wed,  5 Jun 2019 16:01:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=aRjhWCts; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=vDsMDpTS
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 JWPVCEXBaJoK for <mmusic@ietfa.amsl.com>; Wed,  5 Jun 2019 16:01:26 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A35EF12009E for <mmusic@ietf.org>; Wed,  5 Jun 2019 16:01:25 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 034E020FBE for <mmusic@ietf.org>; Wed,  5 Jun 2019 19:01:25 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Wed, 05 Jun 2019 19:01:25 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm2; bh=a6Hwj af+fzcQp3JDdAKLTBrqS9OuZEJR0twTl8haC/8=; b=aRjhWCts7nVdV0FRws2Fz dQ8OLAS3Lj/rQbyVsZNlzL+HkuY6epeIcTTnEV21ueOy5RobNu6gI8+D0u91+Qtu Pa2xzBc3X/Oie2dDrlzs+A42GRjKRLT1cRq/QoEdSbzbf2/4dyFpRoTKjzFMgw/b g1jnlUY/1DueAFO06s1jsZtgfUG6E3k8GvuaneTy6Ulbx7t+l1WMFJyV3ShzOM27 IYRt1mNNyOgJRNjtZVOwb8kQpDFe9Oc1v60Lz7pOHDMT3rkAIp49veY/OWOFH28Q xhsQIqsg7pKnu0tIUo/RyJBEMoLSb0eLTHgufUyWSemeB9M1yHrDB3P2ISsZ/RyG w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=a6Hwjaf+fzcQp3JDdAKLTBrqS9OuZEJR0twTl8haC /8=; b=vDsMDpTSJDXGHAZzCjSFEX96E5wxux3L03+z0FSjp5vBLjAx/hVTMizDg woPHdSw/xEcFaHlDd+3Q608iuLsphrJTPYCJpbGMK1/SnfLOg2E05hrs6u5H0eSr yrrIXeWv+/08/KIOHfci5muSuN6EBTJT1A6whbE6Mhz7dPAJIARx7zzxoumYxi52 kcLHZPtlXZ/BUsonnR6SM5mbtL2vFKa4wSueiCLygE8It6XEm52PscahuNTDDy4A 8xo0UeJwRmrUEokLjACCrxxsgmedXIP+KiWARQBXcTIyBjMUvHg7qX6cCSShV8WC yUKVp7Nx5dU8EQy1ioVSAgBi1PkHQ==
X-ME-Sender: <xms:xEn4XFJaCnBOg7_17ZtiCFj-57rpqCzg1hngupxlcNr-GZ3JfPjIMQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudegfedgudejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtgfesth hqredtreerjeenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehl ohifvghnthhrohhphidrnhgvtheqnecuffhomhgrihhnpehgihhthhhusgdrtghomhdpih gvthhfrdhorhhgnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhho phihrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:xEn4XBSit2vboYuh-8huz3UXXyXJXwVqbXYK_VWc4r0wt25kDIET0w> <xmx:xEn4XFoEEQlO8e4gIGDFMgIkA5Umo6cO2D85Y1OVSadlgNXJScO1xA> <xmx:xEn4XOp2TpjLtumau0QOCwWzMVUIYqmXzGRiyghMlVUNXOJdEFvd9w> <xmx:xEn4XI5AEh77oUWFFAJmuYx7ZUNhjAmZKqstUqsZ1XOnPtW_LTA6DA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 8EBF1E00A1; Wed,  5 Jun 2019 19:01:24 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.6-661-g2bffb41-fmstable-20190605v4
Mime-Version: 1.0
Message-Id: <3f495f29-cb3c-472e-897b-6d24da73e2c3@www.fastmail.com>
In-Reply-To: <2b3651f8-c2f2-fcd2-1883-16de305391f3@nostrum.com>
References: <2b3651f8-c2f2-fcd2-1883-16de305391f3@nostrum.com>
Date: Thu, 06 Jun 2019 09:01:25 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/vWZkM5-v_tgJ2UaPcAVFpsBKoKk>
Subject: Re: [MMUSIC] AD Review: draft-ietf-mmusic-sdp-uks
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 23:01:29 -0000

Thanks Adam.  I fixed these on master: https://github.com/martinthomson/=
sdp-uks/commit/5ca01250e8fe193111a76a1d0558ead9306fa3a6

On Thu, Jun 6, 2019, at 08:50, Adam Roach wrote:
> This is my AD review for draft-ietf-mmusic-sdp-uks. It is
> uncharacteristically short, as I have already reviewed earlier
> versions of this document and provided feedback to the authors.
>=20
> None of my comment preclude putting the document into IETF last call.
> Please address them along with any other comments that may arise
> during the last call process.
>=20
> Thanks!
>=20
> ----------------------------------------------------------------------=
-----
>=20
> Please update the abstract to indicate that this document updates
> RFC 8122.
>=20
> ----------------------------------------------------------------------=
-----
>=20
> =C2=A71:
>=20
>  >=C2=A0 entity.=C2=A0 A successful attack leads to the creation of se=
ssions where
>  >=C2=A0 peers are confused about the identify of the participants.
>=20
> Nit: "...identity of..."
>=20
> ----------------------------------------------------------------------=
-----
>=20
> =C2=A74.3:
>=20
>  >=C2=A0 This is considered benign since these protocols are usually
>  >=C2=A0 distinguishable.
>=20
> Suggest: s/usually/designed to be/
>=20
> (there are specific forbidden PT values reserved to avoid collisions
> with RTCP -- 72 through 76, to be specific)
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Thu Jun  6 08:28:59 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A68DB1200EC; Thu,  6 Jun 2019 08:28:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VTqNMUeYqdoZ; Thu,  6 Jun 2019 08:28:56 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0F5A120046; Thu,  6 Jun 2019 08:28:55 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x56FSoDO023147 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 6 Jun 2019 11:28:51 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic@ietf.org
References: <155922686313.22081.12209259015077736906.idtracker@ietfa.amsl.com> <df7509c8-5bba-fcc2-5d75-3cc179266cf8@alum.mit.edu>
Message-ID: <55b948fb-e2f8-a9cd-cb9d-db7d16545b2d@alum.mit.edu>
Date: Thu, 6 Jun 2019 11:28:50 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <df7509c8-5bba-fcc2-5d75-3cc179266cf8@alum.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9r_Zkvf3zeYo0AJGOBQv8PVQYh4>
Subject: Re: [MMUSIC] Benjamin Kaduk's No Objection on draft-ietf-mmusic-rfc4566bis-35: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2019 15:28:58 -0000

Ben,

> On 5/30/19 10:34 AM, Benjamin Kaduk via Datatracker wrote:

>> Section 5

>> nit: here (and in Section 4.4 just above) may be the only times we
>> include the colon when discussing an "a=" attribute; consistency would
>> seem to suggest removing the colons.

On further study I have found that this usage is actually quite 
extensive, so now I'm inclined to leave this alone.

	Thanks,
	Paul


From nobody Thu Jun  6 09:15:45 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F90C1201B3 for <mmusic@ietfa.amsl.com>; Thu,  6 Jun 2019 09:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nRcJ7coxFdWN for <mmusic@ietfa.amsl.com>; Thu,  6 Jun 2019 09:15:32 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42462120165 for <mmusic@ietf.org>; Thu,  6 Jun 2019 09:15:32 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x56GFTBW026469 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Thu, 6 Jun 2019 12:15:30 -0400
To: IETF MMUSIC WG <mmusic@ietf.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <1b4875ca-c1b9-e3f0-7e99-8f686575b383@alum.mit.edu>
Date: Thu, 6 Jun 2019 12:15:29 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/JFunlDDC3YkjKQ_a3Baje7yKaSY>
Subject: [MMUSIC] Resolving IESG issues with RFC4566bis-35: k= security considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2019 16:15:40 -0000

I've been working to resolve the IESG issues with RFC4566bis-35.
I think I have resolved most of them, but I have a couple where I feel I 
need input from the wg. This is one of those:

"k=" Security Considerations:

I had multiple comments on the last paragraph of Section 7 (Security 
Considerations) that discusses "k=". Here is that paragraph:

    Use of the "k=" line poses a significant security risk, since it
    conveys session encryption keys in the clear.  SDP MUST NOT be used
    to convey keying material, unless it can be guaranteed that the
    channel over which the SDP is delivered is both private and
    authenticated.  Moreover, the "k=" line provides no way to indicate
    or negotiate cryptographic key algorithms.  As it provides for only a
    single symmetric key, rather than separate keys for confidentiality
    and integrity, its utility is severely limited.  The "k=" line MUST
    NOT be used, as discussed in Section 5.12.

As I recall there was a lot of wg discussion on this as well as input 
from a security review, so I hesitate to change without wg input.

Comments I received:

Alissa Cooper:

> It's odd to me that this text was retained from RFC 4566 as-is, 
> except for the last sentence. I would have expected this to lead 
> with something like 'Use of the "k=" line is obsolete due to 
> security risk.' And then perhaps some of the rest of the text 
> could remain by way of explanation why it was obsoleted. 

Roman Danyliw:

> I’d like to escalate Alissa’s point about the k= language in 
> Section 7 (Security Considerations).  It looks like the new 
> Section 5.12 removes all of the historical language beyond saying 
> it MUST NOT be used.  This approach makes sense to me.  However, 
> the language in Section 7 could be read as conflicting with that.  Specifically:
> 
>    Use of the "k=" line poses a significant security risk, since it
>    conveys session encryption keys in the clear.  SDP MUST NOT be used
>    to convey keying material, unless it can be guaranteed that the
>    channel over which the SDP is delivered is both private and
>    authenticated.  ...  The "k=" line MUST
>    NOT be used, as discussed in Section 5.12.
> 
> The first sentence makes a strong statement.  The first clause of 
> the second sentence makes a more generic MUST NOT statement but the 
> second clause seems to say that is acceptable under certain 
> circumstances.  The third sentence reiterates that k= MUST NOT be used.  
> 
> How should this be reconciled?  Is the text suggesting that conveying 
> keying materials outside of k= is acceptable over the right kind of 
> channel? 

Colin Perkins responded with:

> I’d be happy for "SDP MUST NOT be used to convey keying material, 
> unless it can be guaranteed that the channel over which the SDP is 
> delivered is both private and authenticated” to change to “SDP 
> MUST NOT be used to convey keying material”.

Is that ok??? This seems consistent with what we agreed on for section 5.12.

	Thanks,
	Paul


From nobody Thu Jun  6 09:34:46 2019
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A175412007A for <mmusic@ietfa.amsl.com>; Thu,  6 Jun 2019 09:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ojv_NyOMSDuv for <mmusic@ietfa.amsl.com>; Thu,  6 Jun 2019 09:34:43 -0700 (PDT)
Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (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 1B411120025 for <mmusic@ietf.org>; Thu,  6 Jun 2019 09:34:42 -0700 (PDT)
Received: by mail-pf1-x42c.google.com with SMTP id u17so1838274pfn.7 for <mmusic@ietf.org>; Thu, 06 Jun 2019 09:34:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rkR/cJthntVR2JNuqMSKO+Tb7b+Fyc9tyCvCBVWQ1IA=; b=qkDk5P9Md3bslA0SlHjoHfzuVheE3rMkCsvga2L6qZRHp9s6gYs6bi6aILy73d9+XS QBdv/gVdSlFSOV2Tv4qSqCRSgTug015VP1zMBGHb3u6uzfxk/+KtXBvNIpNsumBWGN5N 5MnwxQQSLVwgMAHGVCS9thYWlqdGHlkPqMAwI097ETVJCqstg5ytxkU/PYwLkl/SjVJB Zu5xN/kr9Ub3mk1AsU07vXGR9Aew3P2Q7XEkUxOhkPYPLGqAN6hq74t7Nh7lFtqw2O5x +iGgjzpCkACIrTK/JJr2vJ1S/sv5hLoUKM3bxRVtrKdsHB6R2cOiN3MSyq/2j9wDPxdl 4dcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rkR/cJthntVR2JNuqMSKO+Tb7b+Fyc9tyCvCBVWQ1IA=; b=SZ7QScwyNa+xYtH5S8g5W8lq8FbtLC7rF8QzyYsFV3SU0SUNzXSpXVnq309WqpF+ek hOg9+A4zI1pXwyrfaH3TObGhSgVQxF/jY1djqc9rSV6mTVYTBp07jmHFR5vWiBKs9I3p hBOHYlDmgxE8JiLZyURuO7RGSOh3ZU9QKaSkrGVdSmJTitlQzy6Y0XMfnplCF48qUPWz cT3wa0rnNOxJibDatj9GGDTJy9P/LIqaF7BVKXAKwAasQ+7rPdZQRgdVAqPD7gVqVCoG oWVB5Stzwhdl/dJBqb6PlFV3OLJCh1k0rylV/ZsY126SOIqiQrIB52Iu25zW17mhUkg7 LcTg==
X-Gm-Message-State: APjAAAWT5dlAMlfueNkuq2RKSe5fvQdC0V72cAm0HmZ32Aa+ziYUuWKi +wR/yfUOzYTtDe0jBCbBJCwKOvlOeMA=
X-Google-Smtp-Source: APXvYqwRofRxX/DWmPW6kt/3BPC7I9b56JxHPPshRDxap8MtX02zDUiZEUd4aSQbHNMJG8EQkYtp5Q==
X-Received: by 2002:a63:5207:: with SMTP id g7mr4006417pgb.356.1559838882206;  Thu, 06 Jun 2019 09:34:42 -0700 (PDT)
Received: from mail-pl1-f179.google.com (mail-pl1-f179.google.com. [209.85.214.179]) by smtp.gmail.com with ESMTPSA id 5sm2207553pgi.28.2019.06.06.09.34.41 for <mmusic@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Thu, 06 Jun 2019 09:34:41 -0700 (PDT)
Received: by mail-pl1-f179.google.com with SMTP id g9so1137722plm.6 for <mmusic@ietf.org>; Thu, 06 Jun 2019 09:34:41 -0700 (PDT)
X-Received: by 2002:a17:902:324:: with SMTP id 33mr51270792pld.284.1559838881000;  Thu, 06 Jun 2019 09:34:41 -0700 (PDT)
MIME-Version: 1.0
References: <1b4875ca-c1b9-e3f0-7e99-8f686575b383@alum.mit.edu>
In-Reply-To: <1b4875ca-c1b9-e3f0-7e99-8f686575b383@alum.mit.edu>
From: Roman Shpount <roman@telurix.com>
Date: Thu, 6 Jun 2019 12:34:30 -0400
X-Gmail-Original-Message-ID: <CAD5OKxv6WDG3UY9vpopQphnrS9Zudbzpvp8b9d45O3YsiHqQXw@mail.gmail.com>
Message-ID: <CAD5OKxv6WDG3UY9vpopQphnrS9Zudbzpvp8b9d45O3YsiHqQXw@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: IETF MMUSIC WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000068b1df058aaa4aac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/vBct8JNb8LlA53Elzl_t_Qn_9y8>
Subject: Re: [MMUSIC] Resolving IESG issues with RFC4566bis-35: k= security considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2019 16:34:45 -0000

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

On Thu, Jun 6, 2019 at 12:16 PM Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> Colin Perkins responded with:
>
> > I=E2=80=99d be happy for "SDP MUST NOT be used to convey keying materia=
l,
> > unless it can be guaranteed that the channel over which the SDP is
> > delivered is both private and authenticated=E2=80=9D to change to =E2=
=80=9CSDP
> > MUST NOT be used to convey keying material=E2=80=9D.
>
> Is that ok??? This seems consistent with what we agreed on for section
> 5.12.
>

I think the last paragraph in section 7 was also intended to describe
SDES-SRTP (RFC 4568) or any other protocols that distribute keying material
in clear text in SDP . Not allowing to use SDP to distribute keying
material would likely be excessive and would make anything implementing
SDES-SRTP non-compliant, despite the fact that SIPS+SDES-SRTP is perfectly
secure. I do agree that discussing k=3D line in this paragraph is strange
since it is deprecated, but discussing keying material in SDP should remain=
.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div dir=3D"ltr"><div><div dir=3D"ltr" class=3D"gmail_sign=
ature" data-smartmail=3D"gmail_signature">On Thu, Jun 6, 2019 at 12:16 PM P=
aul Kyzivat &lt;<a href=3D"mailto:pkyzivat@alum.mit.edu">pkyzivat@alum.mit.=
edu</a>&gt; wrote:<br></div></div></div><div class=3D"gmail_quote"><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">Colin Perkins responded with:<br>
<br>
&gt; I=E2=80=99d be happy for &quot;SDP MUST NOT be used to convey keying m=
aterial, <br>
&gt; unless it can be guaranteed that the channel over which the SDP is <br=
>
&gt; delivered is both private and authenticated=E2=80=9D to change to =E2=
=80=9CSDP <br>
&gt; MUST NOT be used to convey keying material=E2=80=9D.<br>
<br>
Is that ok??? This seems consistent with what we agreed on for section 5.12=
.<br></blockquote><div><br></div><div>I think the last paragraph in section=
 7 was also intended to describe SDES-SRTP (RFC 4568) or any other protocol=
s that distribute keying material in clear text in SDP . Not allowing to us=
e SDP to distribute keying material would likely be excessive and would mak=
e anything implementing SDES-SRTP non-compliant, despite the fact that SIPS=
+SDES-SRTP is perfectly secure. I do agree that discussing k=3D line in thi=
s paragraph is strange since it is deprecated, but discussing keying materi=
al in SDP should remain.</div><div><br></div><div>Regards,</div>___________=
__<br>Roman Shpount<br class=3D"gmail-Apple-interchange-newline"><div>=C2=
=A0</div></div></div>

--00000000000068b1df058aaa4aac--


From nobody Thu Jun  6 09:57:18 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF0E9120033 for <mmusic@ietfa.amsl.com>; Thu,  6 Jun 2019 09:57:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id th1zXDmlRyIx for <mmusic@ietfa.amsl.com>; Thu,  6 Jun 2019 09:56:59 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6E7212002F for <mmusic@ietf.org>; Thu,  6 Jun 2019 09:56:58 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x56Guu8D029446 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Thu, 6 Jun 2019 12:56:57 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: IETF MMUSIC WG <mmusic@ietf.org>
Message-ID: <d34a9b29-de79-3809-1520-2e2421e441bc@alum.mit.edu>
Date: Thu, 6 Jun 2019 12:56:56 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/1Woefa_vJrevq5y2pkGfZLkR6EI>
Subject: [MMUSIC] Resolving IESG issues with RFC4566bis-35: "a=type" impact on media direction default
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2019 16:57:03 -0000

I've been working to resolve the IESG issues with RFC4566bis-35.
I think I have resolved most of them, but I have a couple where I feel I 
need input from the wg. This is one of those:

"a=type" impact on media direction default:

While I was resolving a comment on Section 6.9 (a=type) I noticed what I 
think may be a new issue. The text says:

    "recvonly" should be the default for "type:broadcast" sessions,
    "type:meeting" should imply "sendrecv", and "type:moderated" should
    indicate the use of a floor control tool and that the media tools are
    started so as to mute new sites joining the multimedia conference.

    Specifying the attribute "type:H332" indicates that this loosely
    coupled session is part of an H.332 session as defined in the ITU
    H.332 specification [ITU.H332.1998].  Media tools should be started
    "recvonly".

This seems to imply that the *default* media direction 
(sendonly/recvonly/...) will vary depending on the value of the type 
attribute. Yet it isn't written in a normative manner. (This language 
dates back to RFC2327.)

My first reaction to this is that while it is written oddly the intent 
is only that these are suggestions for what the creator of the SDP 
should use. But then I also found language about this in section 6.7 
(Media Direction Attributes):

    If none of the media direction attributes is present at either
    session level or media level, "sendrecv" SHOULD be assumed as the
    default for sessions that are not of the multimedia conference type
    "broadcast" or "H332" (see below).

This language was not in RFC2327 - it was added in RFC4566. (Probably by 
me!)

My current thinking is that this is messed up. At the time of the 
writing in RFC2327 the use case in mind was announcements via SAP. This 
really doesn't work right in an offer/answer context.

I'm inclined to take the language about type-specific directionality out 
in both places. Or, if that can't be done for reasons of backward 
compatibility, then perhaps qualify it as only applying in the case of 
announcements.

I need feedback here!

	Thanks,
	Paul




From nobody Thu Jun  6 13:35:52 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CAB34120071; Thu,  6 Jun 2019 13:35:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mmusic@ietf.org
Message-ID: <155985335075.1523.18347038937853044325@ietfa.amsl.com>
Date: Thu, 06 Jun 2019 13:35:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xgpi6Mn091hIhOT6G-SBsT0S-SY>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-34.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2019 20:35:51 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : Session Description Protocol (SDP) Offer/Answer procedures for Interactive Connectivity Establishment (ICE)
        Authors         : Marc Petit-Huguenin
                          Suhas Nandakumar
                          Ari Keranen
	Filename        : draft-ietf-mmusic-ice-sip-sdp-34.txt
	Pages           : 42
	Date            : 2019-06-06

Abstract:
   This document describes Session Description Protocol (SDP) Offer/
   Answer procedures for carrying out Interactive Connectivity
   Establishment (ICE) between the agents.

   This document obsoletes RFC 5245.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-34
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-34

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-34


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Jun  6 13:58:10 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DBD6D12001A; Thu,  6 Jun 2019 13:58:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mmusic@ietf.org
Message-ID: <155985468082.1776.4793486322725020494@ietfa.amsl.com>
Date: Thu, 06 Jun 2019 13:58:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/GjEiHuJWW5lUZI_Urb-50g44kkk>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-35.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2019 20:58:01 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : Session Description Protocol (SDP) Offer/Answer procedures for Interactive Connectivity Establishment (ICE)
        Authors         : Marc Petit-Huguenin
                          Suhas Nandakumar
                          Ari Keranen
	Filename        : draft-ietf-mmusic-ice-sip-sdp-35.txt
	Pages           : 42
	Date            : 2019-06-06

Abstract:
   This document describes Session Description Protocol (SDP) Offer/
   Answer procedures for carrying out Interactive Connectivity
   Establishment (ICE) between the agents.

   This document obsoletes RFC 5245.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-35
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-35

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-35


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Jun  6 14:07:23 2019
Return-Path: <noreply@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7139412013A; Thu,  6 Jun 2019 14:07:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Flemming Andreasen via Datatracker <noreply@ietf.org>
To: <adam@nostrum.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, iesg-secretary@ietf.org, mmusic@ietf.org
Message-ID: <155985524245.1958.18341883867027643168.idtracker@ietfa.amsl.com>
Date: Thu, 06 Jun 2019 14:07:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3ZQb5bCAxOeczmjGdvsyETXue7A>
Subject: [MMUSIC] Publication has been requested for draft-ietf-mmusic-ice-sip-sdp-35
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2019 21:07:23 -0000

Flemming Andreasen has requested publication of draft-ietf-mmusic-ice-sip-sdp-35 as Proposed Standard on behalf of the MMUSIC working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/


From nobody Thu Jun  6 18:11:14 2019
Return-Path: <adam@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD7F120108; Thu,  6 Jun 2019 18:11:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level: 
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 x1kLXQe_BW1t; Thu,  6 Jun 2019 18:11:10 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6979B120077; Thu,  6 Jun 2019 18:11:07 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x571B2FF007535 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 6 Jun 2019 20:11:05 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1559869865; bh=EVJ6RzV+fKIhX9s8nZckowDEXr9E0B+Bi1ehNoyZPIQ=; h=To:From:Subject:Date; b=ki5ReYbDLcTkEnAAECkz7EnfBmyOT3hdhjcvY+TpqE0sRbaF4wOCCAm8UQPOH3e+A pPcNnfapd2EQxAY/sYVksgAyYOHJg/KZh2TIOICKha+baul+5oTtHaqmrMxfmNAGLR IeJ7sWVWpyehckYUhrQTy8DvV3+WhMcCjQBK7MC8=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: draft-ietf-mmusic-ice-sip-sdp@ietf.org, "mmusic@ietf.org" <mmusic@ietf.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <bcc05ce5-08ef-f0aa-4d25-806dd157dffc@nostrum.com>
Date: Thu, 6 Jun 2019 20:10:57 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/XPmziO5SUo-VGN6nI_hj5txbxmw>
Subject: [MMUSIC] AD Review: draft-ietf-mmusic-ice-sip-sdp
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 01:11:13 -0000

This is my AD review for draft-ietf-mmusic-ice-sip-sdp.

Thanks to everyone for the huge amount of work invested in updating
these ICE procedures. My review did not turn up any technical issues, and
I will be progressing the document to IETF Last Call momentarily.

I have a fair number of minor changes that should be made to the
document.  Treat them as you would any other IETF last call comments.

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

§2:

 >  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
 >  "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
 >  "OPTIONAL" in this document are to be interpreted as described in RFC
 >  2119 [RFC2119].

Please update this paragraph to use the text from RFC 8174.

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

§3.1:

 >  corresponds to the [RFC3264] Offer/Answer protocol and the
 >  terminologies offerer and answerer correspond to the initiator and
 >  responder terminologies from [RFC8445] respectively.

Nit: this is a somewhat unconventional use of the word "terminologies," 
and is
slightly awkward in a couple of other ways as well.  Suggest updating as:

    corresponds to the [RFC3264] Offer/Answer protocol, and the
    terms "offerer" and "answerer" correspond to the initiator and
    responder roles from [RFC8445] respectively.


 >  Once the initiating agent has gathered, pruned and prioritized its

Nit: "...gathered, pruned, and prioritized..."
                          ^

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

§3.2.1.2:

 >  Within a "m=" section, each candidate (including the default

Nit: ...an "m=" section...
          ^
---------------------------------------------------------------------------

§3.2.1.6:

 >  bandwidth value of zero [RFC4566], the agent MUST still include ICE
 >  related SDP attributes.

Nit: "...ICE-related..."

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

§3.3.2:

 >  the answerer MUST NOT include any ICE related SDP attributes in the

Nit: "...ICE-related..."

 >  If the answerer detects a possibility of the ICE mismatch, procedures

Nit: "...possibility of an ICE mismatch..."
                         ^^

 >  Note:  <draft-holmberg-ice-pac>> provides guidance on finding working

Nit:  ...[draft-holmberg-ice-pac]...

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

§3.3.3:

 >  On the other hand, if the answer indicates the support for ICE but

Nit: "...indicates support for ice..."

 >  in the answer, as described in (Section 3.2.5), the offerer MUST

Nit: "...described in Section 3.2.5, the offerer MUST..."

 >  Note:  <draft-holmberg-ice-pac>> provides guidance on finding working

Nit:  ...[draft-holmberg-ice-pac]...

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

§3.4.1.1.1:

 >  An agent sets the rest of the ice related fields in the SDP for this

Nit: "...ICE-related..."

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

§3.4.1.1.3:

 >  the SDP for this data stream as if this was an initial offer for that

Nit: "...as if this were..."

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

§3.4.1.2.1:

 >  gathered since the last offer/ answer exchange, including peer

Nit: "...offer/answer..."

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

§3.4.1.2.1:

 >  connection address, port and transport protocol in each "c=" and "m="

Nit: "...connection address, port, and transport protocol..."
                                  ^
---------------------------------------------------------------------------

§3.4.1.3:

 >  If the ICE state is running, a lite implementation MUST include all

Nit: ...state is "running", a lite...

 >  formed identical to the procedures for initial offers.

Nit: "...identically..."

 >  it MUST restart ICE.  Similarly, the username fragments or passwords

Nit: "...fragments and passwords..."

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

§3.4.3.1:

 >  media server during call hold using 3rd party call-control
 >  procedures.  Omitting further details how this is done, this could

Nit: cite RFC 3725 here.

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

§3.4.3.1:

 >     If a pair on the new check list was
 >     also on the previous check list, and its state is not Frozen, its
 >     state is copied over.  Otherwise, its state is set to Frozen.

How is this procedure different than the simpler (and equivalent sounding):

      If a pair on the new check list was also on the previous check list,
      its state is copied over.  Otherwise, its state is set to Frozen.


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

§3.4.3.1.1:

 >  The agent MUST remember the nominated pair in the Valid list for each
 >  component of the data stream, called the previous selected pair prior
 >  to the restart.

This is hard to parse. I think it means to say:

    The agent MUST remember the nominated pair in the Valid list for each
    component of the data stream, called the "previous selected pair", prior
    to the restart.

(note the addition of quotation marks and a comma)

There's a similar confusing lack of quotation marks in section 3.4.3.2.

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

§4.1:

 >  <component-id>:  is a positive integer between 1 and 256 (inclusive)
 >     that identifies the specific component of the dta stream for which

Nit: "...data stream..."


 >  a reference to the document defining the usage of the extension

Nit: missing ending period.

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

§4.4:

 >  The ice-ufrag attribute MUST contain at least 24 bits of randomness,
 >  and the ice-pwd attribute MUST contain at least 128 bits of
 >  randomness.

This is reiterating normative requirements from RFC 8445 section 5.3.
In general, reiterating normative behavior from a related specification
should be avoided.  I would suggest rephrasing as:

    RFC 8445 requires the ice-ufrag attribute to contain at least 24 bits of
    randomness, and the ice-pwd attribute to contain at least 128 bits of
    randomness.

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

§4.6:

 >  Example shows 'rtp+ecn' ice-option SDP line from <<RFC6679>>:

Nit: [RFC6679]

Also, add RFC 6679 to the "Informative References" section.

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

§6.1.1:

 >  the session terminated.  For the ICE lite peers , the agent MUST

Nit: remove the space before the comma.

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

§8.2.1:

 >  Require Header Field in their offer.  UAs that rejects non-ICE offers

Nit: "...that reject non-ICE..."

 >  SHOULD use a 421 response code, together with an Option Tag "ice" in
 >  the Require Header Field in the response.

This normatively reiterates normative language in RFC 5768. Please
change the "SHOULD" to a "will generally" or something similar.

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

§11.1:

 >  [RFC8126]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for
 >             Writing an IANA Considerations Section in RFCs", BCP 26,
 >             RFC 8126, DOI 10.17487/RFC8126, June 2017,
 >             <http://www.rfc-editor.org/info/rfc5226>.
                                                  ^^^^

Nit: the URL should point to RFC 8126.

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

§11.3:

This section provides no new information, and should be removed.

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

Appendix D:

 >  This begs the question -- why is the updated offer/answer exchange

Nit: "This raises the question..."


From nobody Thu Jun  6 18:31:27 2019
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FFEA12008C; Thu,  6 Jun 2019 18:31:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
CC: fandreas@cisco.com, mmusic-chairs@ietf.org, adam@nostrum.com, mmusic@ietf.org, draft-ietf-mmusic-ice-sip-sdp@ietf.org
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <155987107902.1881.5625931968579017083.idtracker@ietfa.amsl.com>
Date: Thu, 06 Jun 2019 18:31:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/M_OaVA9-cb3MuMD9h2Orwl1IFGI>
Subject: [MMUSIC] Last Call: <draft-ietf-mmusic-ice-sip-sdp-35.txt> (Session Description Protocol (SDP) Offer/Answer procedures for Interactive Connectivity Establishment (ICE)) to Proposed Standard
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 01:31:19 -0000

The IESG has received a request from the Multiparty Multimedia Session
Control WG (mmusic) to consider the following document: - 'Session
Description Protocol (SDP) Offer/Answer procedures for
   Interactive Connectivity Establishment (ICE)'
  <draft-ietf-mmusic-ice-sip-sdp-35.txt> as Proposed Standard

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

Abstract


   This document describes Session Description Protocol (SDP) Offer/
   Answer procedures for carrying out Interactive Connectivity
   Establishment (ICE) between the agents.

   This document obsoletes RFC 5245.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/ballot/


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





From nobody Thu Jun  6 22:04:51 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B9FA12000F; Thu,  6 Jun 2019 22:04:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mmusic@ietf.org
Message-ID: <155988389006.1980.1473019379360139284@ietfa.amsl.com>
Date: Thu, 06 Jun 2019 22:04:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/1V8qPCpDebjDzvNMJI8yHLUq2lA>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-36.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 05:04:50 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : Session Description Protocol (SDP) Offer/Answer procedures for Interactive Connectivity Establishment (ICE)
        Authors         : Marc Petit-Huguenin
                          Suhas Nandakumar
                          Ari Keranen
	Filename        : draft-ietf-mmusic-ice-sip-sdp-36.txt
	Pages           : 41
	Date            : 2019-06-06

Abstract:
   This document describes Session Description Protocol (SDP) Offer/
   Answer procedures for carrying out Interactive Connectivity
   Establishment (ICE) between the agents.

   This document obsoletes RFC 5245.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-36
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-36

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-36


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Jun  6 22:05:39 2019
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB9EA120157; Thu,  6 Jun 2019 22:05:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 dFGcvnOqbnBz; Thu,  6 Jun 2019 22:05:33 -0700 (PDT)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (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 1387312018C; Thu,  6 Jun 2019 22:05:33 -0700 (PDT)
Received: by mail-vs1-xe36.google.com with SMTP id n21so418594vsp.12; Thu, 06 Jun 2019 22:05:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fhxPwY1Al0/pTNU2VIDGxqfNdkn2w4o+k6NaUNcQZVE=; b=QHztYbPgj/MkfqPqaoDu2/+pxav7jBBFj5fQGc3MAE8XKwWVM6QVJVreZlyXr8LEdp iaot4FgifUNfzCWOEuemrfDAg/ht4kwTgNJMLI4RT9PAklC1YXz2GzZ/5vPAoBlJM/os ErvNbaZIvpDKQgGi200REH76FyQrE3+/oC2Z7ptL7CVQo88UaoFsnMQ9p91pzb+P6ZWX j5kszZ3XVs71or35Nsw34pjo9aOl+cByx8hPx0Zz9pB7rld5QiMoK4S7XFckahoO7Kpl t5X8lFEOS1HxCrPX5sylujDi/H/QSv+nCNlG6BKoSKtxXOM6D2tizWfI7cT2tbkT8v5R sPjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fhxPwY1Al0/pTNU2VIDGxqfNdkn2w4o+k6NaUNcQZVE=; b=FtrgDAOWos0aH6a1jvt/F89fuIMhvmY4eHolEoX/IseCYxvzy6YZfnLUgLx3yfIFWl Db7s4Xf6DI7K5lXo3mLEMj8YcJKaSShYoRaaDygkzPQ6knXvYnjRqVEy3U5qdhNo+KSE NEgPeOTX3GKNBes0s7QJiDxTRm0bXATHTE8YvUDGFfZ1OCEWGpVRFQnx+Q4ORwZ/A5A2 uCKMRIaGU6VK7jvz3ybAjFK6yRZR6VKHWPHWGBWDiRrJIzfplS8TO/jz3MtFvPvfI0v/ VV288/I6yqS9Cr7kCGaY9PnR9T+me26W90wR3CYeGcCoGWc4UknqJJwvbu8ESd7MggSA KoeA==
X-Gm-Message-State: APjAAAWjk//Mkh5SCKPsRd7J+yVo57BUMlB2E4cMbkJOf+f1UjmZsVeA OV1qI/FATItliZTfDUBVzk1tg3Mth9GhQcRC0+/8BbpG
X-Google-Smtp-Source: APXvYqzxZZEP824DJ0TZFThswRcGSJDiTms6Z1zKaSD2fmI5BRCjuOzUmgdIKtDrKN++RRrFY971NYc234EpNr64rTM=
X-Received: by 2002:a05:6102:414:: with SMTP id d20mr5984745vsq.69.1559883931883;  Thu, 06 Jun 2019 22:05:31 -0700 (PDT)
MIME-Version: 1.0
References: <bcc05ce5-08ef-f0aa-4d25-806dd157dffc@nostrum.com>
In-Reply-To: <bcc05ce5-08ef-f0aa-4d25-806dd157dffc@nostrum.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Thu, 6 Jun 2019 22:05:20 -0700
Message-ID: <CAMRcRGS6QYef-408t4DoqCQpLwKX912MGT-NfAGt41om9xp31A@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: draft-ietf-mmusic-ice-sip-sdp@ietf.org,  "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a69eb8058ab4c74e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Cg7CfzxmwdbWbl4e0gsNEmmbqoo>
Subject: Re: [MMUSIC] AD Review: draft-ietf-mmusic-ice-sip-sdp
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 05:05:37 -0000

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

Thanks Adam for the review. I have submitted version-36 to address the
feedback.

Cheers
Suhas

On Thu, Jun 6, 2019 at 6:11 PM Adam Roach <adam@nostrum.com> wrote:

> This is my AD review for draft-ietf-mmusic-ice-sip-sdp.
>
> Thanks to everyone for the huge amount of work invested in updating
> these ICE procedures. My review did not turn up any technical issues, and
> I will be progressing the document to IETF Last Call momentarily.
>
> I have a fair number of minor changes that should be made to the
> document.  Treat them as you would any other IETF last call comments.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A72:
>
>  >  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>  >  "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
>  >  "OPTIONAL" in this document are to be interpreted as described in RFC
>  >  2119 [RFC2119].
>
> Please update this paragraph to use the text from RFC 8174.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A73.1:
>
>  >  corresponds to the [RFC3264] Offer/Answer protocol and the
>  >  terminologies offerer and answerer correspond to the initiator and
>  >  responder terminologies from [RFC8445] respectively.
>
> Nit: this is a somewhat unconventional use of the word "terminologies,"
> and is
> slightly awkward in a couple of other ways as well.  Suggest updating as:
>
>     corresponds to the [RFC3264] Offer/Answer protocol, and the
>     terms "offerer" and "answerer" correspond to the initiator and
>     responder roles from [RFC8445] respectively.
>
>
>  >  Once the initiating agent has gathered, pruned and prioritized its
>
> Nit: "...gathered, pruned, and prioritized..."
>                           ^
>
> -------------------------------------------------------------------------=
--
>
> =C2=A73.2.1.2:
>
>  >  Within a "m=3D" section, each candidate (including the default
>
> Nit: ...an "m=3D" section...
>           ^
> -------------------------------------------------------------------------=
--
>
> =C2=A73.2.1.6:
>
>  >  bandwidth value of zero [RFC4566], the agent MUST still include ICE
>  >  related SDP attributes.
>
> Nit: "...ICE-related..."
>
> -------------------------------------------------------------------------=
--
>
> =C2=A73.3.2:
>
>  >  the answerer MUST NOT include any ICE related SDP attributes in the
>
> Nit: "...ICE-related..."
>
>  >  If the answerer detects a possibility of the ICE mismatch, procedures
>
> Nit: "...possibility of an ICE mismatch..."
>                          ^^
>
>  >  Note:  <draft-holmberg-ice-pac>> provides guidance on finding working
>
> Nit:  ...[draft-holmberg-ice-pac]...
>
> -------------------------------------------------------------------------=
--
>
> =C2=A73.3.3:
>
>  >  On the other hand, if the answer indicates the support for ICE but
>
> Nit: "...indicates support for ice..."
>
>  >  in the answer, as described in (Section 3.2.5), the offerer MUST
>
> Nit: "...described in Section 3.2.5, the offerer MUST..."
>
>  >  Note:  <draft-holmberg-ice-pac>> provides guidance on finding working
>
> Nit:  ...[draft-holmberg-ice-pac]...
>
> -------------------------------------------------------------------------=
--
>
> =C2=A73.4.1.1.1:
>
>  >  An agent sets the rest of the ice related fields in the SDP for this
>
> Nit: "...ICE-related..."
>
> -------------------------------------------------------------------------=
--
>
> =C2=A73.4.1.1.3:
>
>  >  the SDP for this data stream as if this was an initial offer for that
>
> Nit: "...as if this were..."
>
> -------------------------------------------------------------------------=
--
>
> =C2=A73.4.1.2.1:
>
>  >  gathered since the last offer/ answer exchange, including peer
>
> Nit: "...offer/answer..."
>
> -------------------------------------------------------------------------=
--
>
> =C2=A73.4.1.2.1:
>
>  >  connection address, port and transport protocol in each "c=3D" and "m=
=3D"
>
> Nit: "...connection address, port, and transport protocol..."
>                                   ^
> -------------------------------------------------------------------------=
--
>
> =C2=A73.4.1.3:
>
>  >  If the ICE state is running, a lite implementation MUST include all
>
> Nit: ...state is "running", a lite...
>
>  >  formed identical to the procedures for initial offers.
>
> Nit: "...identically..."
>
>  >  it MUST restart ICE.  Similarly, the username fragments or passwords
>
> Nit: "...fragments and passwords..."
>
> -------------------------------------------------------------------------=
--
>
> =C2=A73.4.3.1:
>
>  >  media server during call hold using 3rd party call-control
>  >  procedures.  Omitting further details how this is done, this could
>
> Nit: cite RFC 3725 here.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A73.4.3.1:
>
>  >     If a pair on the new check list was
>  >     also on the previous check list, and its state is not Frozen, its
>  >     state is copied over.  Otherwise, its state is set to Frozen.
>
> How is this procedure different than the simpler (and equivalent sounding=
):
>
>       If a pair on the new check list was also on the previous check list=
,
>       its state is copied over.  Otherwise, its state is set to Frozen.
>
>
> -------------------------------------------------------------------------=
--
>
> =C2=A73.4.3.1.1:
>
>  >  The agent MUST remember the nominated pair in the Valid list for each
>  >  component of the data stream, called the previous selected pair prior
>  >  to the restart.
>
> This is hard to parse. I think it means to say:
>
>     The agent MUST remember the nominated pair in the Valid list for each
>     component of the data stream, called the "previous selected pair",
> prior
>     to the restart.
>
> (note the addition of quotation marks and a comma)
>
> There's a similar confusing lack of quotation marks in section 3.4.3.2.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A74.1:
>
>  >  <component-id>:  is a positive integer between 1 and 256 (inclusive)
>  >     that identifies the specific component of the dta stream for which
>
> Nit: "...data stream..."
>
>
>  >  a reference to the document defining the usage of the extension
>
> Nit: missing ending period.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A74.4:
>
>  >  The ice-ufrag attribute MUST contain at least 24 bits of randomness,
>  >  and the ice-pwd attribute MUST contain at least 128 bits of
>  >  randomness.
>
> This is reiterating normative requirements from RFC 8445 section 5.3.
> In general, reiterating normative behavior from a related specification
> should be avoided.  I would suggest rephrasing as:
>
>     RFC 8445 requires the ice-ufrag attribute to contain at least 24 bits
> of
>     randomness, and the ice-pwd attribute to contain at least 128 bits of
>     randomness.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A74.6:
>
>  >  Example shows 'rtp+ecn' ice-option SDP line from <<RFC6679>>:
>
> Nit: [RFC6679]
>
> Also, add RFC 6679 to the "Informative References" section.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A76.1.1:
>
>  >  the session terminated.  For the ICE lite peers , the agent MUST
>
> Nit: remove the space before the comma.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A78.2.1:
>
>  >  Require Header Field in their offer.  UAs that rejects non-ICE offers
>
> Nit: "...that reject non-ICE..."
>
>  >  SHOULD use a 421 response code, together with an Option Tag "ice" in
>  >  the Require Header Field in the response.
>
> This normatively reiterates normative language in RFC 5768. Please
> change the "SHOULD" to a "will generally" or something similar.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A711.1:
>
>  >  [RFC8126]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for
>  >             Writing an IANA Considerations Section in RFCs", BCP 26,
>  >             RFC 8126, DOI 10.17487/RFC8126, June 2017,
>  >             <http://www.rfc-editor.org/info/rfc5226>.
>                                                   ^^^^
>
> Nit: the URL should point to RFC 8126.
>
> -------------------------------------------------------------------------=
--
>
> =C2=A711.3:
>
> This section provides no new information, and should be removed.
>
> -------------------------------------------------------------------------=
--
>
> Appendix D:
>
>  >  This begs the question -- why is the updated offer/answer exchange
>
> Nit: "This raises the question..."
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">Thanks Adam for the review. I have submitted version-36 to=
 address the feedback.<div><br></div><div>Cheers</div><div>Suhas</div></div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Th=
u, Jun 6, 2019 at 6:11 PM Adam Roach &lt;<a href=3D"mailto:adam@nostrum.com=
">adam@nostrum.com</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">This is my AD review for draft-ietf-mmusic-ice-sip-sdp.<b=
r>
<br>
Thanks to everyone for the huge amount of work invested in updating<br>
these ICE procedures. My review did not turn up any technical issues, and<b=
r>
I will be progressing the document to IETF Last Call momentarily.<br>
<br>
I have a fair number of minor changes that should be made to the<br>
document.=C2=A0 Treat them as you would any other IETF last call comments.<=
br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A72:<br>
<br>
=C2=A0&gt;=C2=A0 The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quo=
t;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,<br>
=C2=A0&gt;=C2=A0 &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMEN=
DED&quot;, &quot;NOT RECOMMENDED&quot;, &quot;MAY&quot;, and<br>
=C2=A0&gt;=C2=A0 &quot;OPTIONAL&quot; in this document are to be interprete=
d as described in RFC<br>
=C2=A0&gt;=C2=A0 2119 [RFC2119].<br>
<br>
Please update this paragraph to use the text from RFC 8174.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A73.1:<br>
<br>
=C2=A0&gt;=C2=A0 corresponds to the [RFC3264] Offer/Answer protocol and the=
<br>
=C2=A0&gt;=C2=A0 terminologies offerer and answerer correspond to the initi=
ator and<br>
=C2=A0&gt;=C2=A0 responder terminologies from [RFC8445] respectively.<br>
<br>
Nit: this is a somewhat unconventional use of the word &quot;terminologies,=
&quot; <br>
and is<br>
slightly awkward in a couple of other ways as well.=C2=A0 Suggest updating =
as:<br>
<br>
=C2=A0=C2=A0=C2=A0 corresponds to the [RFC3264] Offer/Answer protocol, and =
the<br>
=C2=A0=C2=A0=C2=A0 terms &quot;offerer&quot; and &quot;answerer&quot; corre=
spond to the initiator and<br>
=C2=A0=C2=A0=C2=A0 responder roles from [RFC8445] respectively.<br>
<br>
<br>
=C2=A0&gt;=C2=A0 Once the initiating agent has gathered, pruned and priorit=
ized its<br>
<br>
Nit: &quot;...gathered, pruned, and prioritized...&quot;<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 ^<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A7<a href=3D"http://3.2.1.2" rel=3D"noreferrer" target=3D"_blank">3.2.1=
.2</a>:<br>
<br>
=C2=A0&gt;=C2=A0 Within a &quot;m=3D&quot; section, each candidate (includi=
ng the default<br>
<br>
Nit: ...an &quot;m=3D&quot; section...<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ^<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A7<a href=3D"http://3.2.1.6" rel=3D"noreferrer" target=3D"_blank">3.2.1=
.6</a>:<br>
<br>
=C2=A0&gt;=C2=A0 bandwidth value of zero [RFC4566], the agent MUST still in=
clude ICE<br>
=C2=A0&gt;=C2=A0 related SDP attributes.<br>
<br>
Nit: &quot;...ICE-related...&quot;<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A73.3.2:<br>
<br>
=C2=A0&gt;=C2=A0 the answerer MUST NOT include any ICE related SDP attribut=
es in the<br>
<br>
Nit: &quot;...ICE-related...&quot;<br>
<br>
=C2=A0&gt;=C2=A0 If the answerer detects a possibility of the ICE mismatch,=
 procedures<br>
<br>
Nit: &quot;...possibility of an ICE mismatch...&quot;<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ^^<br=
>
<br>
=C2=A0&gt;=C2=A0 Note:=C2=A0 &lt;draft-holmberg-ice-pac&gt;&gt; provides gu=
idance on finding working<br>
<br>
Nit:=C2=A0 ...[draft-holmberg-ice-pac]...<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A73.3.3:<br>
<br>
=C2=A0&gt;=C2=A0 On the other hand, if the answer indicates the support for=
 ICE but<br>
<br>
Nit: &quot;...indicates support for ice...&quot;<br>
<br>
=C2=A0&gt;=C2=A0 in the answer, as described in (Section 3.2.5), the offere=
r MUST<br>
<br>
Nit: &quot;...described in Section 3.2.5, the offerer MUST...&quot;<br>
<br>
=C2=A0&gt;=C2=A0 Note:=C2=A0 &lt;draft-holmberg-ice-pac&gt;&gt; provides gu=
idance on finding working<br>
<br>
Nit:=C2=A0 ...[draft-holmberg-ice-pac]...<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A73.4.1.1.1:<br>
<br>
=C2=A0&gt;=C2=A0 An agent sets the rest of the ice related fields in the SD=
P for this<br>
<br>
Nit: &quot;...ICE-related...&quot;<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A73.4.1.1.3:<br>
<br>
=C2=A0&gt;=C2=A0 the SDP for this data stream as if this was an initial off=
er for that<br>
<br>
Nit: &quot;...as if this were...&quot;<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A73.4.1.2.1:<br>
<br>
=C2=A0&gt;=C2=A0 gathered since the last offer/ answer exchange, including =
peer<br>
<br>
Nit: &quot;...offer/answer...&quot;<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A73.4.1.2.1:<br>
<br>
=C2=A0&gt;=C2=A0 connection address, port and transport protocol in each &q=
uot;c=3D&quot; and &quot;m=3D&quot;<br>
<br>
Nit: &quot;...connection address, port, and transport protocol...&quot;<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ^<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A7<a href=3D"http://3.4.1.3" rel=3D"noreferrer" target=3D"_blank">3.4.1=
.3</a>:<br>
<br>
=C2=A0&gt;=C2=A0 If the ICE state is running, a lite implementation MUST in=
clude all<br>
<br>
Nit: ...state is &quot;running&quot;, a lite...<br>
<br>
=C2=A0&gt;=C2=A0 formed identical to the procedures for initial offers.<br>
<br>
Nit: &quot;...identically...&quot;<br>
<br>
=C2=A0&gt;=C2=A0 it MUST restart ICE.=C2=A0 Similarly, the username fragmen=
ts or passwords<br>
<br>
Nit: &quot;...fragments and passwords...&quot;<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A7<a href=3D"http://3.4.3.1" rel=3D"noreferrer" target=3D"_blank">3.4.3=
.1</a>:<br>
<br>
=C2=A0&gt;=C2=A0 media server during call hold using 3rd party call-control=
<br>
=C2=A0&gt;=C2=A0 procedures.=C2=A0 Omitting further details how this is don=
e, this could<br>
<br>
Nit: cite RFC 3725 here.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A7<a href=3D"http://3.4.3.1" rel=3D"noreferrer" target=3D"_blank">3.4.3=
.1</a>:<br>
<br>
=C2=A0&gt;=C2=A0=C2=A0=C2=A0=C2=A0 If a pair on the new check list was<br>
=C2=A0&gt;=C2=A0=C2=A0=C2=A0=C2=A0 also on the previous check list, and its=
 state is not Frozen, its<br>
=C2=A0&gt;=C2=A0=C2=A0=C2=A0=C2=A0 state is copied over.=C2=A0 Otherwise, i=
ts state is set to Frozen.<br>
<br>
How is this procedure different than the simpler (and equivalent sounding):=
<br>
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 If a pair on the new check list was also on =
the previous check list,<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 its state is copied over.=C2=A0 Otherwise, i=
ts state is set to Frozen.<br>
<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A73.4.3.1.1:<br>
<br>
=C2=A0&gt;=C2=A0 The agent MUST remember the nominated pair in the Valid li=
st for each<br>
=C2=A0&gt;=C2=A0 component of the data stream, called the previous selected=
 pair prior<br>
=C2=A0&gt;=C2=A0 to the restart.<br>
<br>
This is hard to parse. I think it means to say:<br>
<br>
=C2=A0=C2=A0=C2=A0 The agent MUST remember the nominated pair in the Valid =
list for each<br>
=C2=A0=C2=A0=C2=A0 component of the data stream, called the &quot;previous =
selected pair&quot;, prior<br>
=C2=A0=C2=A0=C2=A0 to the restart.<br>
<br>
(note the addition of quotation marks and a comma)<br>
<br>
There&#39;s a similar confusing lack of quotation marks in section 3.4.3.2.=
<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A74.1:<br>
<br>
=C2=A0&gt;=C2=A0 &lt;component-id&gt;:=C2=A0 is a positive integer between =
1 and 256 (inclusive)<br>
=C2=A0&gt;=C2=A0=C2=A0=C2=A0=C2=A0 that identifies the specific component o=
f the dta stream for which<br>
<br>
Nit: &quot;...data stream...&quot;<br>
<br>
<br>
=C2=A0&gt;=C2=A0 a reference to the document defining the usage of the exte=
nsion<br>
<br>
Nit: missing ending period.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A74.4:<br>
<br>
=C2=A0&gt;=C2=A0 The ice-ufrag attribute MUST contain at least 24 bits of r=
andomness,<br>
=C2=A0&gt;=C2=A0 and the ice-pwd attribute MUST contain at least 128 bits o=
f<br>
=C2=A0&gt;=C2=A0 randomness.<br>
<br>
This is reiterating normative requirements from RFC 8445 section 5.3.<br>
In general, reiterating normative behavior from a related specification<br>
should be avoided.=C2=A0 I would suggest rephrasing as:<br>
<br>
=C2=A0=C2=A0=C2=A0 RFC 8445 requires the ice-ufrag attribute to contain at =
least 24 bits of<br>
=C2=A0=C2=A0=C2=A0 randomness, and the ice-pwd attribute to contain at leas=
t 128 bits of<br>
=C2=A0=C2=A0=C2=A0 randomness.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A74.6:<br>
<br>
=C2=A0&gt;=C2=A0 Example shows &#39;rtp+ecn&#39; ice-option SDP line from &=
lt;&lt;RFC6679&gt;&gt;:<br>
<br>
Nit: [RFC6679]<br>
<br>
Also, add RFC 6679 to the &quot;Informative References&quot; section.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A76.1.1:<br>
<br>
=C2=A0&gt;=C2=A0 the session terminated.=C2=A0 For the ICE lite peers , the=
 agent MUST<br>
<br>
Nit: remove the space before the comma.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A78.2.1:<br>
<br>
=C2=A0&gt;=C2=A0 Require Header Field in their offer.=C2=A0 UAs that reject=
s non-ICE offers<br>
<br>
Nit: &quot;...that reject non-ICE...&quot;<br>
<br>
=C2=A0&gt;=C2=A0 SHOULD use a 421 response code, together with an Option Ta=
g &quot;ice&quot; in<br>
=C2=A0&gt;=C2=A0 the Require Header Field in the response.<br>
<br>
This normatively reiterates normative language in RFC 5768. Please<br>
change the &quot;SHOULD&quot; to a &quot;will generally&quot; or something =
similar.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A711.1:<br>
<br>
=C2=A0&gt;=C2=A0 [RFC8126]=C2=A0 Cotton, M., Leiba, B., and T. Narten, &quo=
t;Guidelines for<br>
=C2=A0&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Writing an IANA Considerations Section in RFCs&quot;, BCP 26,<br>
=C2=A0&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 RFC 8126, DOI 10.17487/RFC8126, June 2017,<br>
=C2=A0&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 &lt;<a href=3D"http://www.rfc-editor.org/info/rfc5226" rel=3D"nor=
eferrer" target=3D"_blank">http://www.rfc-editor.org/info/rfc5226</a>&gt;.<=
br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ^^^^<=
br>
<br>
Nit: the URL should point to RFC 8126.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
=C2=A711.3:<br>
<br>
This section provides no new information, and should be removed.<br>
<br>
---------------------------------------------------------------------------=
<br>
<br>
Appendix D:<br>
<br>
=C2=A0&gt;=C2=A0 This begs the question -- why is the updated offer/answer =
exchange<br>
<br>
Nit: &quot;This raises the question...&quot;<br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div>

--000000000000a69eb8058ab4c74e--


From nobody Fri Jun  7 05:10:41 2019
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B02312003F; Fri,  7 Jun 2019 05:10:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=eBHHNwVE; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=RtVpyJnD
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 9cLi9C5CeVFC; Fri,  7 Jun 2019 05:10:29 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 841881200A4; Fri,  7 Jun 2019 05:10:28 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 0B7A7221B2; Fri,  7 Jun 2019 08:10:27 -0400 (EDT)
Received: from imap1 ([10.202.2.51]) by compute7.internal (MEProxy); Fri, 07 Jun 2019 08:10:27 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type:content-transfer-encoding; s=fm3; bh=SzQCh lVf5s5T2WTlTmcO1lDXYRAgPm31f7JYG9kuo98=; b=eBHHNwVEvLTKh9VzXcAVk +fSMsCDkkky7HuqLdWmnRo1aXPl3k8yCTjTqhKqYKmJu1r4qA3UMMm1HDYMo7jqI +Y7OdG9lkDpfpCcS9po0qk192O5TQlXOU7Etj5NyqGi8A69b/NO6QkAmDH+OOHGy Nvx3/E3To6qv3KTTDI+SvNiBBD6YdJC7H5SQ6GNjrp1hTqs/tGKxPb0gyoFuvD4F bvFuT8f0ItNlHUOKCmB/Y9Y/DeOBmZTW8nmczFi3YkrPggA3a7atWg2HC2qsxkii S1V1AH84NZHo/1P8bN9WbikbzFE16qpG9NG6KVO4dexqHRk1NM5YxpWXhEtA3Mq7 g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=SzQChlVf5s5T2WTlTmcO1lDXYRAgPm31f7JYG9kuo 98=; b=RtVpyJnDzBkywM4McHqsIpR2lBcMsiU8mjNpp9bYVtN9ghrIpatWHEn2o gDpv8hHPAJyQ9w66xwpoYv22R/yYXp89VIBYwHm3mhkxWC37SlYMXYeS02Fn521k M32N6IpHTFpH0P+t9ofAwAjpDlJfK2siAptTXBy7WFEZCrel1LSJEyzEJGRWrFoZ xW0s+Y+BIhdRyAG/C3yksW0cygZUm+x0uQZn96rQhM93CtxrkcRilwFv9L2lir2F wzf5oZUMVxinDgTJnlUdeivYLyaE4igwOC7EUiRgWmQhI9sc7es1OwBnyJqaH5UY /aT2kWTQHi5fosS/Z8b8mr/a/3eCQ==
X-ME-Sender: <xms:MVT6XHRtT7kpHAC67IB7_dfTunvHzwVfNFXwFdVMAqX73TObTQ9I5g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudegiedggeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgfgsehtqhertderreejnecuhfhrohhmpedftehl vgigvgihucfovghlnhhikhhovhdfuceorggrmhgvlhhnihhkohhvsehfrghsthhmrghilh drfhhmqeenucfrrghrrghmpehmrghilhhfrhhomheprggrmhgvlhhnihhkohhvsehfrghs thhmrghilhdrfhhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:MVT6XI_ubH8UeBYXji-0uWHj3_DamkilPhrfMGkSV2UNJscL5IWG0w> <xmx:MVT6XPdxbWH0gnncrHOMYy-CqtmQWOVFcte-HCXAIHTPfq2q6UEfxQ> <xmx:MVT6XClnMWgxlFCjBfeqbkBlXXdjiPp1NHtDjaTawigWP3En0kpLlA> <xmx:M1T6XBC_ACS02RojV7bUn1r9XBv3fHmPsQ10mYo5YhDuJqtFDXcotg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id D9DFEC200A3; Fri,  7 Jun 2019 08:10:25 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.6-663-gf46ad30-fmstable-20190607v1
Mime-Version: 1.0
Message-Id: <d1954b5e-f7bb-40e1-88dc-5565212b517d@www.fastmail.com>
In-Reply-To: <CALaySJJjwG26NLCJqFdo2yW_JhYCYbY+ADHENa490XqM539U2A@mail.gmail.com>
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <CALaySJJjwG26NLCJqFdo2yW_JhYCYbY+ADHENa490XqM539U2A@mail.gmail.com>
Date: Fri, 07 Jun 2019 13:09:57 +0100
From: "Alexey Melnikov" <aamelnikov@fastmail.fm>
To: "Barry Leiba" <barryleiba@computer.org>, "Paul Kyzivat" <pkyzivat@alum.mit.edu>
Cc: "The IESG" <iesg@ietf.org>, "Flemming Andreasen" <fandreas@cisco.com>, mmusic-chairs@ietf.org, draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic@ietf.org
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xQEhXkyoSIBY1_pWnOExS_NsqPk>
Subject: Re: [MMUSIC]  =?utf-8?q?Alexey_Melnikov=27s_No_Objection_on_draft-iet?= =?utf-8?q?f-mmusic-rfc4566bis-35=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 12:10:32 -0000

Hi Barry/Paul,

On Mon, Jun 3, 2019, at 8:54 PM, Barry Leiba wrote:
> Hi, Paul.  Sticking my oar in with Alexey's here, just on a couple of =
items:
>=20
> > > In Section 1:
> > >
> > > electronic mail using the MIME   extensions [RFC5322]
> > >
> > > This needs another reference for MIME. E.g. RFC 2045.
> >
> > I don't understand. This paragraph is referencing examples of protoc=
ols
> > that can be used to *transport* SDP. RFC5322 references the mail mes=
sage
> > format that would be used to encapsulate SDP if it were transported =
via
> > email. (Though it doesn't actually mention the *transport* protocols=

> > used for mail messages.)
> >
> > ISTM that it is the containing protocols that should reference rfc20=
45.
> > RFC5322 does so, and so says how to carry SDP in mail messages. SIP =
is
> > itself effectively an extension to RFC2045 though it doesn't say so.=

>=20
> Alexey's point is that you explicitly mention "MIME extensions" and
> don't provide a reference for it.  I'll go a bit farther to say that
> you're not just talking about message *format* here, but also SMTP as
> the transport (more correctly, application-layer) protocol, yes?  So
> this should say something more like, "electronic mail [RFC5321] using
> the MIME extensions [RFC2045]".  I don't think you need 5322, because
> 822 is cited by 2045, and that is obsoleted by 2822, and that by 5322.=

> But I think you do need to cite SMTP and MIME.

Yes, exactly.

> > > In 6.10:
> > >
> > >     Note that a character set specified MUST still prohibit the us=
e of
> > >     bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
> > >
> > > This doesn=E2=80=99t actually say what you intended. None of the c=
ommon charsets
> > > prohibit these bytes. I think you meant that when using such chars=
ets, these
> > > characters MUST NOT be used in values.
>=20
> Adding to what Alexey says, and maybe clarifying a bit: Character set
> and encoding are different things.  The character set is the
> abstraction of the characters used, and the encoding is how they're
> represented.  The encoding is what creates the bytes on the wire.  One=

> problem is that "ASCII" refers to both, so it's confusing.  But with
> Unicode, "Unicode" is the character set and "UTF-8" is (usually) the
> encoding.

Right. And the term "charset" is encoding of a particular character set.=
 It might be worth using it below.

> But your point here is that the three byte values you list MUST NOT
> appear in the string, and that has nothing to do with the character
> set or the encoding.  Those three bytes are prohibited.
>=20
> You say that quite well in Section 5:
>=20
>    Text-containing fields such as the session-name-field and
>    information-field are octet strings that may contain any octet with=

>    the exceptions of 0x00 (Nul), 0x0a (ASCII newline), and 0x0d (ASCII=

>    carriage return).
>=20
> ... and in 5.13:
>=20
>    Attribute values are octet strings, and MAY use any octet value
>    except 0x00 (Nul), 0x0A (LF), and 0x0D (CR).
>=20
> But in 6.10 I think you want something more like this:
>=20
> OLD
>    Note that a character set specified MUST still prohibit the use of
>    bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).  Character sets requiri=
ng
>    the use of these characters MUST define a quoting mechanism that
>    prevents these bytes from appearing within text fields.
> NEW
>    Note that the restriction specified in Section 5 applies: these str=
ings
>    MUST NOT contain the bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
>    Character encodings that use these bytes MUST define a quoting
>    mechanism that prevents these bytes from appearing within the text
>    strings.
> END

I think this is much better, although "use these bytes" is still ambiguo=
us. E.g. if these bytes are used to shift between encoding modes within =
a particular charset, then there is a problem. If they are just used to =
convey specific characters, it might not be.

However, see my comment below.

> > I don't recall what the state of character set definitions was in 19=
98
> > when this was first published. But it appears that they got carried =
away
> > and over-generalized. It is easy to understand how one might choose =
to
> > use ISO 8859-1 rather than UTF-8 since they are closely related and
> > byte-oriented. But it is unclear how one might use some other regist=
ered
> > charsets, such as EBCDIC, or other encodings of ISO 10646, such as U=
TF-16.
> >
> > The bottom line is that use of alternate charsets other than 8859-1 =
is
> > underspecified. We considered revamping the definition of charset, b=
ut
> > didn't want to open that can of worms, since in practice it isn't an=
 issue.
>=20
> I appreciate that, and I think this isn't the place to tackle that.
> So we just need to get the text here to accurately reflect what you're=

> trying to say.

I would actually suggest that the document should tighten the definition=
 of which charsets are allowed. For textual media types we now recommend=
 use of UTF-8 (which should be the default) and possibly allowing a few =
others.

So I suggest that the new definition of a=3Dcharset be along the lines o=
f "MUST support UTF-8 and US-ASCII. MAY support ISO-8859-1. SHOULD NOT u=
se any other charsets".

> Hoping to be helpful,
> Barry
>


From nobody Fri Jun  7 05:48:43 2019
Return-Path: <session-request@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 33306120110; Fri,  7 Jun 2019 05:48:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, adam@nostrum.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155991172116.19997.14892006580705434919.idtracker@ietfa.amsl.com>
Date: Fri, 07 Jun 2019 05:48:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/keETAS4d2CJ_WlbeTYOx81SPmaI>
Subject: [MMUSIC] mmusic - Not having a session at IETF 105
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 12:48:41 -0000

Flemming Andreasen, a chair of the mmusic working group, indicated that the mmusic working group does not plan to hold a session at IETF 105.

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



From nobody Fri Jun  7 07:07:05 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45D0112003F for <mmusic@ietfa.amsl.com>; Fri,  7 Jun 2019 07:07:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PAX38UnuUxob for <mmusic@ietfa.amsl.com>; Fri,  7 Jun 2019 07:07:03 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCF741200F1 for <mmusic@ietf.org>; Fri,  7 Jun 2019 07:07:02 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x57E6xdx018586 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 7 Jun 2019 10:07:00 -0400
To: Roman Shpount <roman@telurix.com>
Cc: IETF MMUSIC WG <mmusic@ietf.org>
References: <1b4875ca-c1b9-e3f0-7e99-8f686575b383@alum.mit.edu> <CAD5OKxv6WDG3UY9vpopQphnrS9Zudbzpvp8b9d45O3YsiHqQXw@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <ebbdbe2b-6bce-6192-5339-73d23e5f964e@alum.mit.edu>
Date: Fri, 7 Jun 2019 10:06:59 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxv6WDG3UY9vpopQphnrS9Zudbzpvp8b9d45O3YsiHqQXw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/bACYNZRZGgoN2FGxQJohwDe-UaA>
Subject: Re: [MMUSIC] Resolving IESG issues with RFC4566bis-35: k= security considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 14:07:04 -0000

Roman,

On 6/6/19 12:34 PM, Roman Shpount wrote:
> On Thu, Jun 6, 2019 at 12:16 PM Paul Kyzivat <pkyzivat@alum.mit.edu 
> <mailto:pkyzivat@alum.mit.edu>> wrote:
> 
>     Colin Perkins responded with:
> 
>      > I’d be happy for "SDP MUST NOT be used to convey keying material,
>      > unless it can be guaranteed that the channel over which the SDP is
>      > delivered is both private and authenticated” to change to “SDP
>      > MUST NOT be used to convey keying material”.
> 
>     Is that ok??? This seems consistent with what we agreed on for
>     section 5.12.
> 
> 
> I think the last paragraph in section 7 was also intended to describe 
> SDES-SRTP (RFC 4568) or any other protocols that distribute keying 
> material in clear text in SDP . Not allowing to use SDP to distribute 
> keying material would likely be excessive and would make anything 
> implementing SDES-SRTP non-compliant, despite the fact that 
> SIPS+SDES-SRTP is perfectly secure. I do agree that discussing k= line 
> in this paragraph is strange since it is deprecated, but discussing 
> keying material in SDP should remain.

IIUC you are suggesting reducing the last paragraph to the single sentence:

    SDP MUST NOT be used to convey keying material (e.g., using
    "a=crypto" [RFC4568]) unless it can be guaranteed that the channel
    over which the SDP is delivered is both private and authenticated.

Is there a possibility that this might be construed to apply to 
"a=fingerprint"? That is "keying material" in a sense, even though it is 
incomplete.

	Thanks,
	Paul


From nobody Fri Jun  7 07:25:14 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0F971201F8; Fri,  7 Jun 2019 07:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Khb5iuvAWcjG; Fri,  7 Jun 2019 07:25:04 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D910C120219; Fri,  7 Jun 2019 07:24:59 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x57EOosr019843 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 7 Jun 2019 10:24:51 -0400
To: Alexey Melnikov <aamelnikov@fastmail.fm>, Barry Leiba <barryleiba@computer.org>
Cc: The IESG <iesg@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic@ietf.org
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <CALaySJJjwG26NLCJqFdo2yW_JhYCYbY+ADHENa490XqM539U2A@mail.gmail.com> <d1954b5e-f7bb-40e1-88dc-5565212b517d@www.fastmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <1f37b132-98b7-af5e-7997-e0fd095ff207@alum.mit.edu>
Date: Fri, 7 Jun 2019 10:24:50 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <d1954b5e-f7bb-40e1-88dc-5565212b517d@www.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/tvRKvkf2dRAP8VSd3vt-B1HI3fc>
Subject: Re: [MMUSIC] Alexey Melnikov's No Objection on draft-ietf-mmusic-rfc4566bis-35: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 14:25:07 -0000

Alexy,

When we first realized the issues with charset we thought we were very 
near the end of these revisions, and there didn't seem to be much taste 
for opening this can of worms. But the collection of iesg comments have 
led me to do a fair number of revisions. So I will ask again if there is 
willingness to make this kind of change. The main concern is with 
backward compatibility - is there any use in the wild of other charsets. 
I doubt it, but don't have any data to back that up.

(The whole a=charset thing is a pain without much gain. Much trouble 
identifying things that are and aren't charset-dependent.)

	Thanks,
	Paul

On 6/7/19 8:09 AM, Alexey Melnikov wrote:
> Hi Barry/Paul,
> 
> On Mon, Jun 3, 2019, at 8:54 PM, Barry Leiba wrote:
>> Hi, Paul.  Sticking my oar in with Alexey's here, just on a couple of items:
>>
>>>> In Section 1:
>>>>
>>>> electronic mail using the MIME   extensions [RFC5322]
>>>>
>>>> This needs another reference for MIME. E.g. RFC 2045.
>>>
>>> I don't understand. This paragraph is referencing examples of protocols
>>> that can be used to *transport* SDP. RFC5322 references the mail message
>>> format that would be used to encapsulate SDP if it were transported via
>>> email. (Though it doesn't actually mention the *transport* protocols
>>> used for mail messages.)
>>>
>>> ISTM that it is the containing protocols that should reference rfc2045.
>>> RFC5322 does so, and so says how to carry SDP in mail messages. SIP is
>>> itself effectively an extension to RFC2045 though it doesn't say so.
>>
>> Alexey's point is that you explicitly mention "MIME extensions" and
>> don't provide a reference for it.  I'll go a bit farther to say that
>> you're not just talking about message *format* here, but also SMTP as
>> the transport (more correctly, application-layer) protocol, yes?  So
>> this should say something more like, "electronic mail [RFC5321] using
>> the MIME extensions [RFC2045]".  I don't think you need 5322, because
>> 822 is cited by 2045, and that is obsoleted by 2822, and that by 5322.
>> But I think you do need to cite SMTP and MIME.
> 
> Yes, exactly.
> 
>>>> In 6.10:
>>>>
>>>>      Note that a character set specified MUST still prohibit the use of
>>>>      bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
>>>>
>>>> This doesn’t actually say what you intended. None of the common charsets
>>>> prohibit these bytes. I think you meant that when using such charsets, these
>>>> characters MUST NOT be used in values.
>>
>> Adding to what Alexey says, and maybe clarifying a bit: Character set
>> and encoding are different things.  The character set is the
>> abstraction of the characters used, and the encoding is how they're
>> represented.  The encoding is what creates the bytes on the wire.  One
>> problem is that "ASCII" refers to both, so it's confusing.  But with
>> Unicode, "Unicode" is the character set and "UTF-8" is (usually) the
>> encoding.
> 
> Right. And the term "charset" is encoding of a particular character set. It might be worth using it below.
> 
>> But your point here is that the three byte values you list MUST NOT
>> appear in the string, and that has nothing to do with the character
>> set or the encoding.  Those three bytes are prohibited.
>>
>> You say that quite well in Section 5:
>>
>>     Text-containing fields such as the session-name-field and
>>     information-field are octet strings that may contain any octet with
>>     the exceptions of 0x00 (Nul), 0x0a (ASCII newline), and 0x0d (ASCII
>>     carriage return).
>>
>> ... and in 5.13:
>>
>>     Attribute values are octet strings, and MAY use any octet value
>>     except 0x00 (Nul), 0x0A (LF), and 0x0D (CR).
>>
>> But in 6.10 I think you want something more like this:
>>
>> OLD
>>     Note that a character set specified MUST still prohibit the use of
>>     bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).  Character sets requiring
>>     the use of these characters MUST define a quoting mechanism that
>>     prevents these bytes from appearing within text fields.
>> NEW
>>     Note that the restriction specified in Section 5 applies: these strings
>>     MUST NOT contain the bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
>>     Character encodings that use these bytes MUST define a quoting
>>     mechanism that prevents these bytes from appearing within the text
>>     strings.
>> END
> 
> I think this is much better, although "use these bytes" is still ambiguous. E.g. if these bytes are used to shift between encoding modes within a particular charset, then there is a problem. If they are just used to convey specific characters, it might not be.
> 
> However, see my comment below.
> 
>>> I don't recall what the state of character set definitions was in 1998
>>> when this was first published. But it appears that they got carried away
>>> and over-generalized. It is easy to understand how one might choose to
>>> use ISO 8859-1 rather than UTF-8 since they are closely related and
>>> byte-oriented. But it is unclear how one might use some other registered
>>> charsets, such as EBCDIC, or other encodings of ISO 10646, such as UTF-16.
>>>
>>> The bottom line is that use of alternate charsets other than 8859-1 is
>>> underspecified. We considered revamping the definition of charset, but
>>> didn't want to open that can of worms, since in practice it isn't an issue.
>>
>> I appreciate that, and I think this isn't the place to tackle that.
>> So we just need to get the text here to accurately reflect what you're
>> trying to say.
> 
> I would actually suggest that the document should tighten the definition of which charsets are allowed. For textual media types we now recommend use of UTF-8 (which should be the default) and possibly allowing a few others.
> 
> So I suggest that the new definition of a=charset be along the lines of "MUST support UTF-8 and US-ASCII. MAY support ISO-8859-1. SHOULD NOT use any other charsets".
> 
>> Hoping to be helpful,
>> Barry
>>
> 


From nobody Fri Jun  7 07:38:26 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A9CF1200B9 for <mmusic@ietfa.amsl.com>; Fri,  7 Jun 2019 07:38:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uy0c_QR_L4FL for <mmusic@ietfa.amsl.com>; Fri,  7 Jun 2019 07:38:21 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 345E7120105 for <mmusic@ietf.org>; Fri,  7 Jun 2019 07:38:09 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x57Ec7Dx020773 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Fri, 7 Jun 2019 10:38:08 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: IETF MMUSIC WG <mmusic@ietf.org>
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <CALaySJJjwG26NLCJqFdo2yW_JhYCYbY+ADHENa490XqM539U2A@mail.gmail.com> <d1954b5e-f7bb-40e1-88dc-5565212b517d@www.fastmail.com> <1f37b132-98b7-af5e-7997-e0fd095ff207@alum.mit.edu>
Message-ID: <834ef36e-e664-55de-292f-8c7cf3b3b868@alum.mit.edu>
Date: Fri, 7 Jun 2019 10:38:07 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <1f37b132-98b7-af5e-7997-e0fd095ff207@alum.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Uyt65p4qqjcw8fAbF1ArqScDAFQ>
Subject: [MMUSIC] Resolving IESG issues with RFC4566bis-35: a=charset
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 14:38:24 -0000

MMUSIC SDP fans,

The message below already went to mmusic, but here I'm reducing the 
distribution list to only mmusic so we don't spam the iesg with our 
internal discussion.

It seems that Alexy doesn't want to let us sweep the charset issues 
under the rug.

Would his suggestion to restrict the charsets permitted to be used be 
acceptable? Repeating it:

>> I would actually suggest that the document should tighten the definition of which charsets are allowed. For textual media types we now recommend use of UTF-8 (which should be the default) and possibly allowing a few others.
>> 
>> So I suggest that the new definition of a=charset be along the lines of "MUST support UTF-8 and US-ASCII. MAY support ISO-8859-1. SHOULD NOT use any other charsets".

	Thanks,
	Paul

On 6/7/19 10:24 AM, Paul Kyzivat wrote:
> Alexy,
> 
> When we first realized the issues with charset we thought we were very 
> near the end of these revisions, and there didn't seem to be much taste 
> for opening this can of worms. But the collection of iesg comments have 
> led me to do a fair number of revisions. So I will ask again if there is 
> willingness to make this kind of change. The main concern is with 
> backward compatibility - is there any use in the wild of other charsets. 
> I doubt it, but don't have any data to back that up.
> 
> (The whole a=charset thing is a pain without much gain. Much trouble 
> identifying things that are and aren't charset-dependent.)
> 
>      Thanks,
>      Paul
> 
> On 6/7/19 8:09 AM, Alexey Melnikov wrote:
>> Hi Barry/Paul,
>>
>> On Mon, Jun 3, 2019, at 8:54 PM, Barry Leiba wrote:
>>> Hi, Paul.  Sticking my oar in with Alexey's here, just on a couple of 
>>> items:
>>>
>>>>> In Section 1:
>>>>>
>>>>> electronic mail using the MIME   extensions [RFC5322]
>>>>>
>>>>> This needs another reference for MIME. E.g. RFC 2045.
>>>>
>>>> I don't understand. This paragraph is referencing examples of protocols
>>>> that can be used to *transport* SDP. RFC5322 references the mail 
>>>> message
>>>> format that would be used to encapsulate SDP if it were transported via
>>>> email. (Though it doesn't actually mention the *transport* protocols
>>>> used for mail messages.)
>>>>
>>>> ISTM that it is the containing protocols that should reference rfc2045.
>>>> RFC5322 does so, and so says how to carry SDP in mail messages. SIP is
>>>> itself effectively an extension to RFC2045 though it doesn't say so.
>>>
>>> Alexey's point is that you explicitly mention "MIME extensions" and
>>> don't provide a reference for it.  I'll go a bit farther to say that
>>> you're not just talking about message *format* here, but also SMTP as
>>> the transport (more correctly, application-layer) protocol, yes?  So
>>> this should say something more like, "electronic mail [RFC5321] using
>>> the MIME extensions [RFC2045]".  I don't think you need 5322, because
>>> 822 is cited by 2045, and that is obsoleted by 2822, and that by 5322.
>>> But I think you do need to cite SMTP and MIME.
>>
>> Yes, exactly.
>>
>>>>> In 6.10:
>>>>>
>>>>>      Note that a character set specified MUST still prohibit the 
>>>>> use of
>>>>>      bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
>>>>>
>>>>> This doesn’t actually say what you intended. None of the common 
>>>>> charsets
>>>>> prohibit these bytes. I think you meant that when using such 
>>>>> charsets, these
>>>>> characters MUST NOT be used in values.
>>>
>>> Adding to what Alexey says, and maybe clarifying a bit: Character set
>>> and encoding are different things.  The character set is the
>>> abstraction of the characters used, and the encoding is how they're
>>> represented.  The encoding is what creates the bytes on the wire.  One
>>> problem is that "ASCII" refers to both, so it's confusing.  But with
>>> Unicode, "Unicode" is the character set and "UTF-8" is (usually) the
>>> encoding.
>>
>> Right. And the term "charset" is encoding of a particular character 
>> set. It might be worth using it below.
>>
>>> But your point here is that the three byte values you list MUST NOT
>>> appear in the string, and that has nothing to do with the character
>>> set or the encoding.  Those three bytes are prohibited.
>>>
>>> You say that quite well in Section 5:
>>>
>>>     Text-containing fields such as the session-name-field and
>>>     information-field are octet strings that may contain any octet with
>>>     the exceptions of 0x00 (Nul), 0x0a (ASCII newline), and 0x0d (ASCII
>>>     carriage return).
>>>
>>> ... and in 5.13:
>>>
>>>     Attribute values are octet strings, and MAY use any octet value
>>>     except 0x00 (Nul), 0x0A (LF), and 0x0D (CR).
>>>
>>> But in 6.10 I think you want something more like this:
>>>
>>> OLD
>>>     Note that a character set specified MUST still prohibit the use of
>>>     bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).  Character sets 
>>> requiring
>>>     the use of these characters MUST define a quoting mechanism that
>>>     prevents these bytes from appearing within text fields.
>>> NEW
>>>     Note that the restriction specified in Section 5 applies: these 
>>> strings
>>>     MUST NOT contain the bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
>>>     Character encodings that use these bytes MUST define a quoting
>>>     mechanism that prevents these bytes from appearing within the text
>>>     strings.
>>> END
>>
>> I think this is much better, although "use these bytes" is still 
>> ambiguous. E.g. if these bytes are used to shift between encoding 
>> modes within a particular charset, then there is a problem. If they 
>> are just used to convey specific characters, it might not be.
>>
>> However, see my comment below.
>>
>>>> I don't recall what the state of character set definitions was in 1998
>>>> when this was first published. But it appears that they got carried 
>>>> away
>>>> and over-generalized. It is easy to understand how one might choose to
>>>> use ISO 8859-1 rather than UTF-8 since they are closely related and
>>>> byte-oriented. But it is unclear how one might use some other 
>>>> registered
>>>> charsets, such as EBCDIC, or other encodings of ISO 10646, such as 
>>>> UTF-16.
>>>>
>>>> The bottom line is that use of alternate charsets other than 8859-1 is
>>>> underspecified. We considered revamping the definition of charset, but
>>>> didn't want to open that can of worms, since in practice it isn't an 
>>>> issue.
>>>
>>> I appreciate that, and I think this isn't the place to tackle that.
>>> So we just need to get the text here to accurately reflect what you're
>>> trying to say.
>>
>> I would actually suggest that the document should tighten the 
>> definition of which charsets are allowed. For textual media types we 
>> now recommend use of UTF-8 (which should be the default) and possibly 
>> allowing a few others.
>>
>> So I suggest that the new definition of a=charset be along the lines 
>> of "MUST support UTF-8 and US-ASCII. MAY support ISO-8859-1. SHOULD 
>> NOT use any other charsets".
>>
>>> Hoping to be helpful,
>>> Barry
>>>
>>
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Fri Jun  7 08:27:41 2019
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB061201B7 for <mmusic@ietfa.amsl.com>; Fri,  7 Jun 2019 08:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QZkzK9DnR8Mj for <mmusic@ietfa.amsl.com>; Fri,  7 Jun 2019 08:27:28 -0700 (PDT)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 1EF0C1201EC for <mmusic@ietf.org>; Fri,  7 Jun 2019 08:27:28 -0700 (PDT)
Received: by mail-pg1-x533.google.com with SMTP id h2so1359390pgg.1 for <mmusic@ietf.org>; Fri, 07 Jun 2019 08:27:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DdsVulTaBCE0FZDLIe1vg9uTySXycL1oTyh76lMCsew=; b=kEGBngyHK6jpTSxHonipP1Lw5Q7l5ELBXhpcpd5VRfaHzlRWHKycDR3JR2wkO1j/w1 fHAl+1aN39xoQC9jsT1utkxuIilTAgaMzl/DKL+dKxNDFBDljjBTJpRX2HOMPYzyS0MU nqfWS4TiVNCUMQL9XrdIFyQuwbgWhPmgoOBHvMQwWeeP/+HZ8X8kD0RQeaLN4GdWo9rJ etEI00LPuQf7mm15L3KMe4iiMAhKbm1JAj21GOC9QwWdv+V14LJNK1pDZqgC36aWjAm7 UJcRENhzjqY7lnzvofmmDhzhmvyRzpTgtl/1b4+j8HFk1sxk+PjFGg8TlC3LU9dbCamV YTfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DdsVulTaBCE0FZDLIe1vg9uTySXycL1oTyh76lMCsew=; b=NCmJV2Quvvy9bY8lvMX+qNGtlc8ad2INGibDx3ly9PbcDq802UxB3e+Vt67hLOp8g8 bMT7rIz5nrLYGV4Sxq6unM7DlhbpwsLk3BIogmZxOLkYK6l2xbuOvtq3uAXwxTirxCJO Hy8ZfXpKmlM1jzurMS6x4jSBZ0vD5eybfPDv/rSCcx6En7QYXcFk4GLIACYQzskluBDW ZhIJpIxrXWfNPdiFPiwcAVuF12vLumye4SUOopPLLOQWM0CoTd0XuwQM8/fnT/MihCOM naih5XiYSDUCPmVJnlTmrWIqetjETbr2gcDRyRR2XPqUbWy3KjGKQrUyRovDYBmYZnua oEgw==
X-Gm-Message-State: APjAAAWCEJi+ZmnYFKxo6E/Ok5KyNnWp3LWvQOO6kxrPZNvhyTmCz5fG WRK8RKVF/blhBmpfSb746DX4AU3WgLs=
X-Google-Smtp-Source: APXvYqwaIoZsPfSmEWNBJ8RoJifyRRtLNzWPvZExDfNUNs9J+cS4FNgbGT7KR3YoJg5v77plSzM1nw==
X-Received: by 2002:a63:6105:: with SMTP id v5mr3276836pgb.312.1559921247139;  Fri, 07 Jun 2019 08:27:27 -0700 (PDT)
Received: from mail-pg1-f170.google.com (mail-pg1-f170.google.com. [209.85.215.170]) by smtp.gmail.com with ESMTPSA id ds14sm2297167pjb.32.2019.06.07.08.27.26 for <mmusic@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Fri, 07 Jun 2019 08:27:26 -0700 (PDT)
Received: by mail-pg1-f170.google.com with SMTP id s27so1356962pgl.2 for <mmusic@ietf.org>; Fri, 07 Jun 2019 08:27:26 -0700 (PDT)
X-Received: by 2002:a17:90a:b00b:: with SMTP id x11mr6148731pjq.120.1559921246189;  Fri, 07 Jun 2019 08:27:26 -0700 (PDT)
MIME-Version: 1.0
References: <1b4875ca-c1b9-e3f0-7e99-8f686575b383@alum.mit.edu> <CAD5OKxv6WDG3UY9vpopQphnrS9Zudbzpvp8b9d45O3YsiHqQXw@mail.gmail.com> <ebbdbe2b-6bce-6192-5339-73d23e5f964e@alum.mit.edu>
In-Reply-To: <ebbdbe2b-6bce-6192-5339-73d23e5f964e@alum.mit.edu>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 7 Jun 2019 11:27:17 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtXY6dd0wATB_sVo_5yss3fGRo2G+Z5iHVXRfxohGkA7Q@mail.gmail.com>
Message-ID: <CAD5OKxtXY6dd0wATB_sVo_5yss3fGRo2G+Z5iHVXRfxohGkA7Q@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: IETF MMUSIC WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c1bf17058abd77b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/R3u7vyQhHet4_zGLwiuekUwaDG4>
Subject: Re: [MMUSIC] Resolving IESG issues with RFC4566bis-35: k= security considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 15:27:40 -0000

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

Paul,

On Fri, Jun 7, 2019 at 10:07 AM Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> On 6/6/19 12:34 PM, Roman Shpount wrote:
> > On Thu, Jun 6, 2019 at 12:16 PM Paul Kyzivat <pkyzivat@alum.mit.edu
> > <mailto:pkyzivat@alum.mit.edu>> wrote:
> >
> >     Colin Perkins responded with:
> >
> >      > I=E2=80=99d be happy for "SDP MUST NOT be used to convey keying =
material,
> >      > unless it can be guaranteed that the channel over which the SDP =
is
> >      > delivered is both private and authenticated=E2=80=9D to change t=
o =E2=80=9CSDP
> >      > MUST NOT be used to convey keying material=E2=80=9D.
> >
> >     Is that ok??? This seems consistent with what we agreed on for
> >     section 5.12.
> >
> >
> > I think the last paragraph in section 7 was also intended to describe
> > SDES-SRTP (RFC 4568) or any other protocols that distribute keying
> > material in clear text in SDP . Not allowing to use SDP to distribute
> > keying material would likely be excessive and would make anything
> > implementing SDES-SRTP non-compliant, despite the fact that
> > SIPS+SDES-SRTP is perfectly secure. I do agree that discussing k=3D lin=
e
> > in this paragraph is strange since it is deprecated, but discussing
> > keying material in SDP should remain.
>
> IIUC you are suggesting reducing the last paragraph to the single sentenc=
e:
>
>     SDP MUST NOT be used to convey keying material (e.g., using
>     "a=3Dcrypto" [RFC4568]) unless it can be guaranteed that the channel
>     over which the SDP is delivered is both private and authenticated.
>

 Yes, this would work for me.

Is there a possibility that this might be construed to apply to
> "a=3Dfingerprint"? That is "keying material" in a sense, even though it i=
s
> incomplete.
>

I do not think this will apply to "a=3Dfingerprint", since technically
"a=3Dfingerprint" is more like authentication not keying material. When SDP
is used to deliver "a=3Dfingerprint" its content should be authenticated
(signed) but does not have to be private. If you think clarification is
required, it can be added, but I think it is better handled in security
considerations for things that described using DTLS with SDP.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div dir=3D"ltr"><div><div class=3D"gmail_signature" data-=
smartmail=3D"gmail_signature">Paul,</div><div class=3D"gmail_signature" dat=
a-smartmail=3D"gmail_signature"><br></div><div dir=3D"ltr" class=3D"gmail_s=
ignature" data-smartmail=3D"gmail_signature">On Fri, Jun 7, 2019 at 10:07 A=
M Paul Kyzivat &lt;<a href=3D"mailto:pkyzivat@alum.mit.edu">pkyzivat@alum.m=
it.edu</a>&gt; wrote:<br></div></div></div><div class=3D"gmail_quote"><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex">On 6/6/19 12:34 PM, Roman Shpo=
unt wrote:<br>
&gt; On Thu, Jun 6, 2019 at 12:16 PM Paul Kyzivat &lt;<a href=3D"mailto:pky=
zivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.edu</a> <br>
&gt; &lt;mailto:<a href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">=
pkyzivat@alum.mit.edu</a>&gt;&gt; wrote:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Colin Perkins responded with:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt; I=E2=80=99d be happy for &quot;SDP MUST NOT b=
e used to convey keying material,<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt; unless it can be guaranteed that the channel =
over which the SDP is<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt; delivered is both private and authenticated=
=E2=80=9D to change to =E2=80=9CSDP<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &gt; MUST NOT be used to convey keying material=E2=
=80=9D.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Is that ok??? This seems consistent with what we ag=
reed on for<br>
&gt;=C2=A0 =C2=A0 =C2=A0section 5.12.<br>
&gt; <br>
&gt; <br>
&gt; I think the last paragraph in section 7 was also intended to describe =
<br>
&gt; SDES-SRTP (RFC 4568) or any other protocols that distribute keying <br=
>
&gt; material in clear text in SDP . Not allowing to use SDP to distribute =
<br>
&gt; keying material would likely be excessive and would make anything <br>
&gt; implementing SDES-SRTP non-compliant, despite the fact that <br>
&gt; SIPS+SDES-SRTP is perfectly secure. I do agree that discussing k=3D li=
ne <br>
&gt; in this paragraph is strange since it is deprecated, but discussing <b=
r>
&gt; keying material in SDP should remain.<br>
<br>
IIUC you are suggesting reducing the last paragraph to the single sentence:=
<br>
<br>
=C2=A0 =C2=A0 SDP MUST NOT be used to convey keying material (e.g., using<b=
r>
=C2=A0 =C2=A0 &quot;a=3Dcrypto&quot; [RFC4568]) unless it can be guaranteed=
 that the channel<br>
=C2=A0 =C2=A0 over which the SDP is delivered is both private and authentic=
ated.<br></blockquote><div><br></div><div>=C2=A0Yes, this would work for me=
.</div><div><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">Is =
there a possibility that this might be construed to apply to <br>
&quot;a=3Dfingerprint&quot;? That is &quot;keying material&quot; in a sense=
, even though it is <br>
incomplete.<br></blockquote><div><br></div><div>I do not think this will ap=
ply to &quot;a=3Dfingerprint&quot;, since technically &quot;a=3Dfingerprint=
&quot; is more like authentication not keying material. When SDP is used to=
 deliver &quot;a=3Dfingerprint&quot; its content should be authenticated (s=
igned) but does not have to be private. If you think clarification is requi=
red, it can be added, but I think it is better handled in security consider=
ations for things that described using DTLS with SDP.</div><div><br></div><=
div>Regards,</div>_____________<br>Roman Shpount<br class=3D"gmail-Apple-in=
terchange-newline"><div>=C2=A0</div></div></div>

--000000000000c1bf17058abd77b0--


From nobody Fri Jun  7 15:09:59 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62B991200EA for <mmusic@ietfa.amsl.com>; Fri,  7 Jun 2019 15:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IrYPCH9byUtk for <mmusic@ietfa.amsl.com>; Fri,  7 Jun 2019 15:09:56 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73DB81200E9 for <mmusic@ietf.org>; Fri,  7 Jun 2019 15:09:56 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x57M9src019528 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Fri, 7 Jun 2019 18:09:54 -0400
To: mmusic@ietf.org
References: <1b4875ca-c1b9-e3f0-7e99-8f686575b383@alum.mit.edu> <CAD5OKxv6WDG3UY9vpopQphnrS9Zudbzpvp8b9d45O3YsiHqQXw@mail.gmail.com> <ebbdbe2b-6bce-6192-5339-73d23e5f964e@alum.mit.edu>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <51b12a39-4451-34e0-b56a-3a693a79b87e@alum.mit.edu>
Date: Fri, 7 Jun 2019 18:09:54 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <ebbdbe2b-6bce-6192-5339-73d23e5f964e@alum.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/WmnOKJIx3yG2S1Qx3_7A60YhpXA>
Subject: Re: [MMUSIC] Resolving IESG issues with RFC4566bis-35: k= security considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 22:09:58 -0000

OK. I'm going to go with this unless I hear something more in the next 
couple of days. But I would prefer to hear from more people.

	Thanks,
	Paul

On 6/7/19 10:06 AM, Paul Kyzivat wrote:
> Roman,
> 
> On 6/6/19 12:34 PM, Roman Shpount wrote:
>> On Thu, Jun 6, 2019 at 12:16 PM Paul Kyzivat <pkyzivat@alum.mit.edu 
>> <mailto:pkyzivat@alum.mit.edu>> wrote:
>>
>>     Colin Perkins responded with:
>>
>>      > I’d be happy for "SDP MUST NOT be used to convey keying material,
>>      > unless it can be guaranteed that the channel over which the SDP is
>>      > delivered is both private and authenticated” to change to “SDP
>>      > MUST NOT be used to convey keying material”.
>>
>>     Is that ok??? This seems consistent with what we agreed on for
>>     section 5.12.
>>
>>
>> I think the last paragraph in section 7 was also intended to describe 
>> SDES-SRTP (RFC 4568) or any other protocols that distribute keying 
>> material in clear text in SDP . Not allowing to use SDP to distribute 
>> keying material would likely be excessive and would make anything 
>> implementing SDES-SRTP non-compliant, despite the fact that 
>> SIPS+SDES-SRTP is perfectly secure. I do agree that discussing k= line 
>> in this paragraph is strange since it is deprecated, but discussing 
>> keying material in SDP should remain.
> 
> IIUC you are suggesting reducing the last paragraph to the single sentence:
> 
>     SDP MUST NOT be used to convey keying material (e.g., using
>     "a=crypto" [RFC4568]) unless it can be guaranteed that the channel
>     over which the SDP is delivered is both private and authenticated.
> 
> Is there a possibility that this might be construed to apply to 
> "a=fingerprint"? That is "keying material" in a sense, even though it is 
> incomplete.
> 
>      Thanks,
>      Paul
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Fri Jun  7 15:23:41 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AADD112004D for <mmusic@ietfa.amsl.com>; Fri,  7 Jun 2019 15:23:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jiRQOhxSgU-R for <mmusic@ietfa.amsl.com>; Fri,  7 Jun 2019 15:23:36 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 694A31200EA for <mmusic@ietf.org>; Fri,  7 Jun 2019 15:23:36 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x57MNFtI020426 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 7 Jun 2019 18:23:16 -0400
To: mmusic@ietf.org, Mark Handley <M.Handley@cs.ucl.ac.uk>, "'Colin Perkins'" <csp@csperkins.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>, Henning Schulzrinne <hgs@cs.columbia.edu>
References: <d34a9b29-de79-3809-1520-2e2421e441bc@alum.mit.edu>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <e9a262e1-3c05-3a81-4adc-80928b327f60@alum.mit.edu>
Date: Fri, 7 Jun 2019 18:23:15 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <d34a9b29-de79-3809-1520-2e2421e441bc@alum.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/hIF7_CqoMnUNkgXg5dnuB89FJzg>
Subject: Re: [MMUSIC] Resolving IESG issues with RFC4566bis-35: "a=type" impact on media direction default
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 22:23:39 -0000

Anybody? Especially old timers (Mark, Van, Colin, Magnus, Henning) from 
RFC2327 days?.

	Thanks,
	Paul

On 6/6/19 12:56 PM, Paul Kyzivat wrote:
> I've been working to resolve the IESG issues with RFC4566bis-35.
> I think I have resolved most of them, but I have a couple where I feel I 
> need input from the wg. This is one of those:
> 
> "a=type" impact on media direction default:
> 
> While I was resolving a comment on Section 6.9 (a=type) I noticed what I 
> think may be a new issue. The text says:
> 
>     "recvonly" should be the default for "type:broadcast" sessions,
>     "type:meeting" should imply "sendrecv", and "type:moderated" should
>     indicate the use of a floor control tool and that the media tools are
>     started so as to mute new sites joining the multimedia conference.
> 
>     Specifying the attribute "type:H332" indicates that this loosely
>     coupled session is part of an H.332 session as defined in the ITU
>     H.332 specification [ITU.H332.1998].  Media tools should be started
>     "recvonly".
> 
> This seems to imply that the *default* media direction 
> (sendonly/recvonly/...) will vary depending on the value of the type 
> attribute. Yet it isn't written in a normative manner. (This language 
> dates back to RFC2327.)
> 
> My first reaction to this is that while it is written oddly the intent 
> is only that these are suggestions for what the creator of the SDP 
> should use. But then I also found language about this in section 6.7 
> (Media Direction Attributes):
> 
>     If none of the media direction attributes is present at either
>     session level or media level, "sendrecv" SHOULD be assumed as the
>     default for sessions that are not of the multimedia conference type
>     "broadcast" or "H332" (see below).
> 
> This language was not in RFC2327 - it was added in RFC4566. (Probably by 
> me!)
> 
> My current thinking is that this is messed up. At the time of the 
> writing in RFC2327 the use case in mind was announcements via SAP. This 
> really doesn't work right in an offer/answer context.
> 
> I'm inclined to take the language about type-specific directionality out 
> in both places. Or, if that can't be done for reasons of backward 
> compatibility, then perhaps qualify it as only applying in the case of 
> announcements.
> 
> I need feedback here!
> 
>      Thanks,
>      Paul
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> 


From nobody Sat Jun  8 02:38:49 2019
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB57B12008B; Sat,  8 Jun 2019 02:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=iVVtXc8o; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=DNo1Nmq0
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 6lPYeFNYhAVG; Sat,  8 Jun 2019 02:38:44 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3082012006E; Sat,  8 Jun 2019 02:38:44 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 63CFB21F9F; Sat,  8 Jun 2019 05:38:43 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Sat, 08 Jun 2019 05:38:43 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=X jhCO5tVbBPqRZ8fa++uWmh35nbaVIHxC9dhA4OTcYY=; b=iVVtXc8oS/Z8tkuqp nm9B84Zv+4zY8clgP9TDaQbbiosL2V6y3lKeaXXCWRbJRr3oLc6VVMJ1W2T4HDnK vw/RwnjeGyUD/HqCT+7cL38WBm+jqGlI7lFnK0hEhjEfw+2mjlgelLxjXsuuFxMI ZBh8jza8hzOysGhUWTBd+ovmla75SuW3lwJ8bQS0IAmgUVD+ejymhlc/nblNXWdX jJEE0eihacRF4n5QivFcK/2bOn6Td+cjoeJFe0XCHfQ0hqofsyBpDzvidTz0+RgY Fzgwu693pTTZ+NMRW3PIJzdDwcgCmUhMIZAdINfydqsR6vm2Gp7B0QhTz/Iow2R+ W0RWw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=XjhCO5tVbBPqRZ8fa++uWmh35nbaVIHxC9dhA4OTc YY=; b=DNo1Nmq0uEHhEbXD9PTqoY0ILN15NIQURiKCHVD24YYaTc93OmWTJ/JTg jJI8IoO23d1fkFsvZ1UMbVpky7k9F9+ItK3vOaKsDP/yMhvfRVyzt0Pig0etQw5x FGP7DrsVjDmpQ8I2qKUf/nAnV95dcnCWat+AVpbylISdcjy/vzXMoKteFWRmGaJR 0eUPZivEH1DbW/qilkRUJ75n+ogniXQhaVCzsx4juErNlOK6CMi9tjCHPoc7YNFB a8b88X+i07Ez/SnZuSZhbYybPy800il3/ZlwWXpTtd3ck0WsAtBJ5L2uAnsGZ35Z CZZ01sSKRcjh1Q52C07fMkmY1zarQ==
X-ME-Sender: <xms:IoL7XHYyhplMXuC0ES9p4iZkDjoW6Q3euo7KFWCTFemlrR-SFJaazQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudegkedgudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhofgjfffgkfhfvfesthhqmhdthhdtjeenucfhrhhomheptehlvgig vgihucfovghlnhhikhhovhcuoegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmh eqnecukfhppeejjedrleejrddugeehrdehheenucfrrghrrghmpehmrghilhhfrhhomhep rggrmhgvlhhnihhkohhvsehfrghsthhmrghilhdrfhhmnecuvehluhhsthgvrhfuihiivg eptd
X-ME-Proxy: <xmx:IoL7XI9g9foK-hDnNnrWwDNX4Jqgg13JEYALUKh8ROgwiG9ANtaJ_w> <xmx:IoL7XNlrLNzk-WqSKy96jCn5A7ysY_dHqG11Ead0sDUL-frSMEDPWg> <xmx:IoL7XNyWZ09096CfUp76UEagHGpjVUzZaVAbEq8tkbQyU0R1FMc4RA> <xmx:I4L7XA2fLDwdvcI5WUuZV5J_23DYcQ81Yq2vG8JZ9Q24oboGQ2gZUg>
Received: from [192.168.0.12] (cpc121086-nmal24-2-0-cust54.19-2.cable.virginm.net [77.97.145.55]) by mail.messagingengine.com (Postfix) with ESMTPA id 4B46B8005B; Sat,  8 Jun 2019 05:38:41 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPad Mail (16D57)
In-Reply-To: <1f37b132-98b7-af5e-7997-e0fd095ff207@alum.mit.edu>
Date: Sat, 8 Jun 2019 10:38:39 +0100
Cc: Barry Leiba <barryleiba@computer.org>, The IESG <iesg@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, draft-ietf-mmusic-rfc4566bis@ietf.org, mmusic@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2014981-8656-432E-82C2-2FA5ED110DD7@fastmail.fm>
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <CALaySJJjwG26NLCJqFdo2yW_JhYCYbY+ADHENa490XqM539U2A@mail.gmail.com> <d1954b5e-f7bb-40e1-88dc-5565212b517d@www.fastmail.com> <1f37b132-98b7-af5e-7997-e0fd095ff207@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/B4M0nuXVVzfOmg0KsR4uYvi3R-k>
Subject: Re: [MMUSIC] Alexey Melnikov's No Objection on draft-ietf-mmusic-rfc4566bis-35: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jun 2019 09:38:47 -0000

Hi Paul,

> On 7 Jun 2019, at 15:24, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
> Alexy,
>=20
> When we first realized the issues with charset we thought we were very nea=
r the end of these revisions, and there didn't seem to be much taste for ope=
ning this can of worms. But the collection of iesg comments have led me to d=
o a fair number of revisions. So I will ask again if there is willingness to=
 make this kind of change. The main concern is with backward compatibility -=
 is there any use in the wild of other charsets. I doubt it, but don't have a=
ny data to back that up.

For new applications there is no need to support anything other than UTF-8.
But of course this doesn=E2=80=99t help you. In email space there is still q=
uite a lot of non UTF-8 support, but this is mostly due to legacy code.

If it was me, I was just bite the bullet and at least start phasing out non U=
TF-8 (that is why I suggested =E2=80=9CSHOULD NOT use any other charset=E2=80=
=9D). If you don=E2=80=99t start now, you will never be able to deprecate th=
em.

But of course this is for the WG to decide.
>=20
> (The whole a=3Dcharset thing is a pain without much gain. Much trouble ide=
ntifying things that are and aren't charset-dependent.)

I can see that :-)

Best Regards,
Alexey
>=20
>    Thanks,
>    Paul
>=20
>> On 6/7/19 8:09 AM, Alexey Melnikov wrote:
>> Hi Barry/Paul,
>>> On Mon, Jun 3, 2019, at 8:54 PM, Barry Leiba wrote:
>>> Hi, Paul.  Sticking my oar in with Alexey's here, just on a couple of it=
ems:
>>>=20
>>>>> In Section 1:
>>>>>=20
>>>>> electronic mail using the MIME   extensions [RFC5322]
>>>>>=20
>>>>> This needs another reference for MIME. E.g. RFC 2045.
>>>>=20
>>>> I don't understand. This paragraph is referencing examples of protocols=

>>>> that can be used to *transport* SDP. RFC5322 references the mail messag=
e
>>>> format that would be used to encapsulate SDP if it were transported via=

>>>> email. (Though it doesn't actually mention the *transport* protocols
>>>> used for mail messages.)
>>>>=20
>>>> ISTM that it is the containing protocols that should reference rfc2045.=

>>>> RFC5322 does so, and so says how to carry SDP in mail messages. SIP is
>>>> itself effectively an extension to RFC2045 though it doesn't say so.
>>>=20
>>> Alexey's point is that you explicitly mention "MIME extensions" and
>>> don't provide a reference for it.  I'll go a bit farther to say that
>>> you're not just talking about message *format* here, but also SMTP as
>>> the transport (more correctly, application-layer) protocol, yes?  So
>>> this should say something more like, "electronic mail [RFC5321] using
>>> the MIME extensions [RFC2045]".  I don't think you need 5322, because
>>> 822 is cited by 2045, and that is obsoleted by 2822, and that by 5322.
>>> But I think you do need to cite SMTP and MIME.
>> Yes, exactly.
>>>>> In 6.10:
>>>>>=20
>>>>>     Note that a character set specified MUST still prohibit the use of=

>>>>>     bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
>>>>>=20
>>>>> This doesn=E2=80=99t actually say what you intended. None of the commo=
n charsets
>>>>> prohibit these bytes. I think you meant that when using such charsets,=
 these
>>>>> characters MUST NOT be used in values.
>>>=20
>>> Adding to what Alexey says, and maybe clarifying a bit: Character set
>>> and encoding are different things.  The character set is the
>>> abstraction of the characters used, and the encoding is how they're
>>> represented.  The encoding is what creates the bytes on the wire.  One
>>> problem is that "ASCII" refers to both, so it's confusing.  But with
>>> Unicode, "Unicode" is the character set and "UTF-8" is (usually) the
>>> encoding.
>> Right. And the term "charset" is encoding of a particular character set. I=
t might be worth using it below.
>>> But your point here is that the three byte values you list MUST NOT
>>> appear in the string, and that has nothing to do with the character
>>> set or the encoding.  Those three bytes are prohibited.
>>>=20
>>> You say that quite well in Section 5:
>>>=20
>>>    Text-containing fields such as the session-name-field and
>>>    information-field are octet strings that may contain any octet with
>>>    the exceptions of 0x00 (Nul), 0x0a (ASCII newline), and 0x0d (ASCII
>>>    carriage return).
>>>=20
>>> ... and in 5.13:
>>>=20
>>>    Attribute values are octet strings, and MAY use any octet value
>>>    except 0x00 (Nul), 0x0A (LF), and 0x0D (CR).
>>>=20
>>> But in 6.10 I think you want something more like this:
>>>=20
>>> OLD
>>>    Note that a character set specified MUST still prohibit the use of
>>>    bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).  Character sets requiring=

>>>    the use of these characters MUST define a quoting mechanism that
>>>    prevents these bytes from appearing within text fields.
>>> NEW
>>>    Note that the restriction specified in Section 5 applies: these strin=
gs
>>>    MUST NOT contain the bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
>>>    Character encodings that use these bytes MUST define a quoting
>>>    mechanism that prevents these bytes from appearing within the text
>>>    strings.
>>> END
>> I think this is much better, although "use these bytes" is still ambiguou=
s. E.g. if these bytes are used to shift between encoding modes within a par=
ticular charset, then there is a problem. If they are just used to convey sp=
ecific characters, it might not be.
>> However, see my comment below.
>>>> I don't recall what the state of character set definitions was in 1998
>>>> when this was first published. But it appears that they got carried awa=
y
>>>> and over-generalized. It is easy to understand how one might choose to
>>>> use ISO 8859-1 rather than UTF-8 since they are closely related and
>>>> byte-oriented. But it is unclear how one might use some other registere=
d
>>>> charsets, such as EBCDIC, or other encodings of ISO 10646, such as UTF-=
16.
>>>>=20
>>>> The bottom line is that use of alternate charsets other than 8859-1 is
>>>> underspecified. We considered revamping the definition of charset, but
>>>> didn't want to open that can of worms, since in practice it isn't an is=
sue.
>>>=20
>>> I appreciate that, and I think this isn't the place to tackle that.
>>> So we just need to get the text here to accurately reflect what you're
>>> trying to say.
>> I would actually suggest that the document should tighten the definition o=
f which charsets are allowed. For textual media types we now recommend use o=
f UTF-8 (which should be the default) and possibly allowing a few others.
>> So I suggest that the new definition of a=3Dcharset be along the lines of=
 "MUST support UTF-8 and US-ASCII. MAY support ISO-8859-1. SHOULD NOT use an=
y other charsets".
>>> Hoping to be helpful,
>>> Barry
>>>=20
>=20


From nobody Sat Jun  8 10:44:27 2019
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25B621200DB for <mmusic@ietfa.amsl.com>; Sat,  8 Jun 2019 10:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 01pheUUVQg4j for <mmusic@ietfa.amsl.com>; Sat,  8 Jun 2019 10:44:22 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20087.outbound.protection.outlook.com [40.107.2.87]) (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 EFD20120073 for <mmusic@ietf.org>; Sat,  8 Jun 2019 10:44:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=TLxvIvQth9svmbuYiMe0kN8uEmtjDlCYo2qCGnVcV5Q=; b=mTDSuYBQNsLHK7yIgdtqnAHp5OGVNWQhJba/LVdpWlPBVqpW0s4uo5+0YyELeIbek61pRr7Eztq/eMHF0iu12cCmfEIsRKlkdZGmZ5E8q3kGwNUapxeOM6dHk7IBM7TYKaSJzcN3aPuruFHKdZoQus+pJedPUuB31Txy4Nc3AyI=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3131.eurprd07.prod.outlook.com (10.170.245.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1987.7; Sat, 8 Jun 2019 17:44:17 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec69:84fc:5339:d4fd]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec69:84fc:5339:d4fd%7]) with mapi id 15.20.1987.008; Sat, 8 Jun 2019 17:44:17 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>,  Mark Handley <M.Handley@cs.ucl.ac.uk>, 'Colin Perkins' <csp@csperkins.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>, Henning Schulzrinne <hgs@cs.columbia.edu>
Thread-Topic: [MMUSIC] Resolving IESG issues with RFC4566bis-35: "a=type" impact on media direction default
Thread-Index: AQHVHIj0fKDmx0kAH0iezXCuB1VJyqaQxiGAgAF2roA=
Date: Sat, 8 Jun 2019 17:44:17 +0000
Message-ID: <BBB56C03-F402-427D-B3AF-E2FCC76E4362@ericsson.com>
References: <d34a9b29-de79-3809-1520-2e2421e441bc@alum.mit.edu> <e9a262e1-3c05-3a81-4adc-80928b327f60@alum.mit.edu>
In-Reply-To: <e9a262e1-3c05-3a81-4adc-80928b327f60@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.19.0.190512
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [79.134.118.162]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 01c48ccf-369d-4bf3-5dc2-08d6ec38ee31
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:HE1PR07MB3131; 
x-ms-traffictypediagnostic: HE1PR07MB3131:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <HE1PR07MB3131ADA38511F711B48CE9EC93110@HE1PR07MB3131.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0062BDD52C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(136003)(346002)(396003)(366004)(39860400002)(51854002)(189003)(199004)(31014005)(6486002)(53546011)(6246003)(53936002)(68736007)(6306002)(102836004)(6506007)(2171002)(110136005)(86362001)(33656002)(5660300002)(229853002)(14454004)(71200400001)(256004)(44832011)(486006)(66066001)(66946007)(66476007)(966005)(71190400001)(83716004)(73956011)(64756008)(76116006)(66556008)(66446008)(82746002)(446003)(478600001)(2616005)(476003)(2501003)(316002)(25786009)(7736002)(6436002)(305945005)(11346002)(8676002)(8936002)(36756003)(58126008)(81166006)(99286004)(186003)(2906002)(6512007)(76176011)(6116002)(3846002)(26005)(81156014); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3131; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: BK3JkNlshH7UEhMyi+oJv5NEePN6J+CFp7JxKtGCfCgp1Yj44SO9tzDBIM49UqmaA9LKYXhZZSmxbrZKxH9+Z0iyeWxUBOlRaANUy1NZmEh0KK7PdAUZiuiyh7Xdf8IBQloIkl2i6Ty6sN8FMi8r97sI7g2xg5URCSXGIoB5tH8k1EGIWZW/SzRQU9P6vD6Dm+xPUwZiTCEKklSyCn0YKJkdYw5l/5VB9pNjjKcBRo863oe9dZHvnl6zPKJHIwyiTB2iFLgBLMbHn29nJ53at+0HUEhWBfH284Gd+izwPv2rBxLtWfEMs5b9GXNzwEzYfQE0oCvUvk0L0XOwPGfE6X4EU7eiA7Qo/cuiXAMfpApL8GVwlbR3fqfQoZMyagdV1dW+gJZHL+3YwMJ8AfTRdTQksfmKXfRSt+Rm4iUEVYw=
Content-Type: text/plain; charset="utf-8"
Content-ID: <06BB2DF5162A354D804BBD5F7E56850A@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 01c48ccf-369d-4bf3-5dc2-08d6ec38ee31
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jun 2019 17:44:17.6651 (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: christer.holmberg@ericsson.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3131
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/U060LJT3BwZSWrfnG9rTqAk9F1Y>
Subject: Re: [MMUSIC] Resolving IESG issues with RFC4566bis-35: "a=type" impact on media direction default
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jun 2019 17:44:25 -0000

SGksDQoNCkluIG15IG9waW5pb24sIHRoZSBkZWZhdWx0IGRpcmVjdGlvbiB2YWx1ZSBpcyBhbHdh
eXMgInNlbmRyZWN2IiAtIG5vIG1hdHRlciB3aGF0IHRoZSB0eXBlIHZhbHVlIGlzLiBUeXBlIHZh
bHVlcyBjYW4gTk9UIG92ZXJyaWRlIGNvcmUgU0RQIGRlZmF1bHQgdmFsdWVzLCBJTU8uDQoNCklm
ICAicmVjdm9ubHkiIGlzIHRvIGJlIHVzZWQgd2l0aCAidHlwZTpicm9hZGNhc3QiLCB0aGVuIHRo
ZSBlbmRwb2ludHMgbmVlZCB0byBtYWtlIHN1cmUgdGhleSBuZWdvdGlhdGUgInJlY3Zvbmx5Ii4N
Cg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQrvu79PbiAwOC8wNi8yMDE5LCAxLjIzLCAibW11
c2ljIG9uIGJlaGFsZiBvZiBQYXVsIEt5eml2YXQiIDxtbXVzaWMtYm91bmNlc0BpZXRmLm9yZyBv
biBiZWhhbGYgb2YgcGt5eml2YXRAYWx1bS5taXQuZWR1PiB3cm90ZToNCg0KICAgIEFueWJvZHk/
IEVzcGVjaWFsbHkgb2xkIHRpbWVycyAoTWFyaywgVmFuLCBDb2xpbiwgTWFnbnVzLCBIZW5uaW5n
KSBmcm9tIA0KICAgIFJGQzIzMjcgZGF5cz8uDQogICAgDQogICAgCVRoYW5rcywNCiAgICAJUGF1
bA0KICAgIA0KICAgIE9uIDYvNi8xOSAxMjo1NiBQTSwgUGF1bCBLeXppdmF0IHdyb3RlOg0KICAg
ID4gSSd2ZSBiZWVuIHdvcmtpbmcgdG8gcmVzb2x2ZSB0aGUgSUVTRyBpc3N1ZXMgd2l0aCBSRkM0
NTY2YmlzLTM1Lg0KICAgID4gSSB0aGluayBJIGhhdmUgcmVzb2x2ZWQgbW9zdCBvZiB0aGVtLCBi
dXQgSSBoYXZlIGEgY291cGxlIHdoZXJlIEkgZmVlbCBJIA0KICAgID4gbmVlZCBpbnB1dCBmcm9t
IHRoZSB3Zy4gVGhpcyBpcyBvbmUgb2YgdGhvc2U6DQogICAgPiANCiAgICA+ICJhPXR5cGUiIGlt
cGFjdCBvbiBtZWRpYSBkaXJlY3Rpb24gZGVmYXVsdDoNCiAgICA+IA0KICAgID4gV2hpbGUgSSB3
YXMgcmVzb2x2aW5nIGEgY29tbWVudCBvbiBTZWN0aW9uIDYuOSAoYT10eXBlKSBJIG5vdGljZWQg
d2hhdCBJIA0KICAgID4gdGhpbmsgbWF5IGJlIGEgbmV3IGlzc3VlLiBUaGUgdGV4dCBzYXlzOg0K
ICAgID4gDQogICAgPiAgICAgInJlY3Zvbmx5IiBzaG91bGQgYmUgdGhlIGRlZmF1bHQgZm9yICJ0
eXBlOmJyb2FkY2FzdCIgc2Vzc2lvbnMsDQogICAgPiAgICAgInR5cGU6bWVldGluZyIgc2hvdWxk
IGltcGx5ICJzZW5kcmVjdiIsIGFuZCAidHlwZTptb2RlcmF0ZWQiIHNob3VsZA0KICAgID4gICAg
IGluZGljYXRlIHRoZSB1c2Ugb2YgYSBmbG9vciBjb250cm9sIHRvb2wgYW5kIHRoYXQgdGhlIG1l
ZGlhIHRvb2xzIGFyZQ0KICAgID4gICAgIHN0YXJ0ZWQgc28gYXMgdG8gbXV0ZSBuZXcgc2l0ZXMg
am9pbmluZyB0aGUgbXVsdGltZWRpYSBjb25mZXJlbmNlLg0KICAgID4gDQogICAgPiAgICAgU3Bl
Y2lmeWluZyB0aGUgYXR0cmlidXRlICJ0eXBlOkgzMzIiIGluZGljYXRlcyB0aGF0IHRoaXMgbG9v
c2VseQ0KICAgID4gICAgIGNvdXBsZWQgc2Vzc2lvbiBpcyBwYXJ0IG9mIGFuIEguMzMyIHNlc3Np
b24gYXMgZGVmaW5lZCBpbiB0aGUgSVRVDQogICAgPiAgICAgSC4zMzIgc3BlY2lmaWNhdGlvbiBb
SVRVLkgzMzIuMTk5OF0uICBNZWRpYSB0b29scyBzaG91bGQgYmUgc3RhcnRlZA0KICAgID4gICAg
ICJyZWN2b25seSIuDQogICAgPiANCiAgICA+IFRoaXMgc2VlbXMgdG8gaW1wbHkgdGhhdCB0aGUg
KmRlZmF1bHQqIG1lZGlhIGRpcmVjdGlvbiANCiAgICA+IChzZW5kb25seS9yZWN2b25seS8uLi4p
IHdpbGwgdmFyeSBkZXBlbmRpbmcgb24gdGhlIHZhbHVlIG9mIHRoZSB0eXBlIA0KICAgID4gYXR0
cmlidXRlLiBZZXQgaXQgaXNuJ3Qgd3JpdHRlbiBpbiBhIG5vcm1hdGl2ZSBtYW5uZXIuIChUaGlz
IGxhbmd1YWdlIA0KICAgID4gZGF0ZXMgYmFjayB0byBSRkMyMzI3LikNCiAgICA+IA0KICAgID4g
TXkgZmlyc3QgcmVhY3Rpb24gdG8gdGhpcyBpcyB0aGF0IHdoaWxlIGl0IGlzIHdyaXR0ZW4gb2Rk
bHkgdGhlIGludGVudCANCiAgICA+IGlzIG9ubHkgdGhhdCB0aGVzZSBhcmUgc3VnZ2VzdGlvbnMg
Zm9yIHdoYXQgdGhlIGNyZWF0b3Igb2YgdGhlIFNEUCANCiAgICA+IHNob3VsZCB1c2UuIEJ1dCB0
aGVuIEkgYWxzbyBmb3VuZCBsYW5ndWFnZSBhYm91dCB0aGlzIGluIHNlY3Rpb24gNi43IA0KICAg
ID4gKE1lZGlhIERpcmVjdGlvbiBBdHRyaWJ1dGVzKToNCiAgICA+IA0KICAgID4gICAgIElmIG5v
bmUgb2YgdGhlIG1lZGlhIGRpcmVjdGlvbiBhdHRyaWJ1dGVzIGlzIHByZXNlbnQgYXQgZWl0aGVy
DQogICAgPiAgICAgc2Vzc2lvbiBsZXZlbCBvciBtZWRpYSBsZXZlbCwgInNlbmRyZWN2IiBTSE9V
TEQgYmUgYXNzdW1lZCBhcyB0aGUNCiAgICA+ICAgICBkZWZhdWx0IGZvciBzZXNzaW9ucyB0aGF0
IGFyZSBub3Qgb2YgdGhlIG11bHRpbWVkaWEgY29uZmVyZW5jZSB0eXBlDQogICAgPiAgICAgImJy
b2FkY2FzdCIgb3IgIkgzMzIiIChzZWUgYmVsb3cpLg0KICAgID4gDQogICAgPiBUaGlzIGxhbmd1
YWdlIHdhcyBub3QgaW4gUkZDMjMyNyAtIGl0IHdhcyBhZGRlZCBpbiBSRkM0NTY2LiAoUHJvYmFi
bHkgYnkgDQogICAgPiBtZSEpDQogICAgPiANCiAgICA+IE15IGN1cnJlbnQgdGhpbmtpbmcgaXMg
dGhhdCB0aGlzIGlzIG1lc3NlZCB1cC4gQXQgdGhlIHRpbWUgb2YgdGhlIA0KICAgID4gd3JpdGlu
ZyBpbiBSRkMyMzI3IHRoZSB1c2UgY2FzZSBpbiBtaW5kIHdhcyBhbm5vdW5jZW1lbnRzIHZpYSBT
QVAuIFRoaXMgDQogICAgPiByZWFsbHkgZG9lc24ndCB3b3JrIHJpZ2h0IGluIGFuIG9mZmVyL2Fu
c3dlciBjb250ZXh0Lg0KICAgID4gDQogICAgPiBJJ20gaW5jbGluZWQgdG8gdGFrZSB0aGUgbGFu
Z3VhZ2UgYWJvdXQgdHlwZS1zcGVjaWZpYyBkaXJlY3Rpb25hbGl0eSBvdXQgDQogICAgPiBpbiBi
b3RoIHBsYWNlcy4gT3IsIGlmIHRoYXQgY2FuJ3QgYmUgZG9uZSBmb3IgcmVhc29ucyBvZiBiYWNr
d2FyZCANCiAgICA+IGNvbXBhdGliaWxpdHksIHRoZW4gcGVyaGFwcyBxdWFsaWZ5IGl0IGFzIG9u
bHkgYXBwbHlpbmcgaW4gdGhlIGNhc2Ugb2YgDQogICAgPiBhbm5vdW5jZW1lbnRzLg0KICAgID4g
DQogICAgPiBJIG5lZWQgZmVlZGJhY2sgaGVyZSENCiAgICA+IA0KICAgID4gICAgICBUaGFua3Ms
DQogICAgPiAgICAgIFBhdWwNCiAgICA+IA0KICAgID4gDQogICAgPiANCiAgICA+IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICAgPiBtbXVzaWMgbWFp
bGluZyBsaXN0DQogICAgPiBtbXVzaWNAaWV0Zi5vcmcNCiAgICA+IGh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljDQogICAgPiANCiAgICANCiAgICBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KICAgIG1tdXNpYyBtYWlsaW5n
IGxpc3QNCiAgICBtbXVzaWNAaWV0Zi5vcmcNCiAgICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL21tdXNpYw0KICAgIA0KDQo=


From nobody Sat Jun  8 10:52:50 2019
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9F681200DB for <mmusic@ietfa.amsl.com>; Sat,  8 Jun 2019 10:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 7gt3nEtP-rk8 for <mmusic@ietfa.amsl.com>; Sat,  8 Jun 2019 10:52:46 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00071.outbound.protection.outlook.com [40.107.0.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DE3B120106 for <mmusic@ietf.org>; Sat,  8 Jun 2019 10:52:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=95PH0iaLVZfjWgPWJ04LlyYgrcedFvsuLyOxnj/kdRM=; b=U7E0sAwwm3QOMfjIrcgjhGvipDjlxBnkeb6cvE7tKkskRdyKvTd1u+36i8y8iySKD8sjtOWwCmSBUQjjXnh9CpcCEyq+3/BgpLeKduydmq3mMou/tYwbLbG/S2oCEzmKRAKM6eSlyGI+OKen4OW4KtZlQyOAi8ht6pZRxq5KLeE=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3131.eurprd07.prod.outlook.com (10.170.245.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1987.7; Sat, 8 Jun 2019 17:52:43 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec69:84fc:5339:d4fd]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec69:84fc:5339:d4fd%7]) with mapi id 15.20.1987.008; Sat, 8 Jun 2019 17:52:43 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, IETF MMUSIC WG <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Resolving IESG issues with RFC4566bis-35: a=charset
Thread-Index: AQHVHT65eKOky9R93ke35kJypanbCqaSPb6A
Date: Sat, 8 Jun 2019 17:52:43 +0000
Message-ID: <1D536F12-1008-462C-BFF8-876B6A03F274@ericsson.com>
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <CALaySJJjwG26NLCJqFdo2yW_JhYCYbY+ADHENa490XqM539U2A@mail.gmail.com> <d1954b5e-f7bb-40e1-88dc-5565212b517d@www.fastmail.com> <1f37b132-98b7-af5e-7997-e0fd095ff207@alum.mit.edu> <834ef36e-e664-55de-292f-8c7cf3b3b868@alum.mit.edu>
In-Reply-To: <834ef36e-e664-55de-292f-8c7cf3b3b868@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.19.0.190512
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [79.134.118.162]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 906eed1b-f830-47dd-b7f8-08d6ec3a1bb8
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:HE1PR07MB3131; 
x-ms-traffictypediagnostic: HE1PR07MB3131:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <HE1PR07MB31318362F8FD466412A3DB7C93110@HE1PR07MB3131.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0062BDD52C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(366004)(396003)(136003)(376002)(346002)(199004)(189003)(36756003)(8936002)(8676002)(11346002)(305945005)(58126008)(476003)(2616005)(446003)(478600001)(7736002)(6436002)(316002)(25786009)(26005)(81156014)(3846002)(6116002)(81166006)(76176011)(6512007)(2906002)(99286004)(186003)(6506007)(102836004)(6306002)(86362001)(110136005)(33656002)(2171002)(6486002)(68736007)(53546011)(53936002)(6246003)(66476007)(66946007)(486006)(44832011)(256004)(66066001)(66556008)(82746002)(66446008)(966005)(76116006)(64756008)(73956011)(83716004)(71190400001)(5660300002)(71200400001)(229853002)(14454004); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3131; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: LgdYXGKnPlT/FN0jaXi8JiPzB83LTjXc48MuEhb0P3uY3cFnuFFxpUTrWi4gbZCEsBoQ+olHmgDyTy4/aEBbuZBw3cJaFlOX7kp09Hp28KMOavZ1ROi+l5K8A+WKYK+bpOLds6oIIWnJs1D9MLO3j+cRbc+rRmzEICg1clw6LNzAsaTPWxwMECvYK1jqXGl6up86yTR1WLBkfok/ClCRaK8S0tf8aURAIRfCGFJ2LpK4jCAT33CiLM260Xyx+kJ0UeCSj8plj+9JzunA7QFUBkbhb9sBLF2UPcGEF1IdPiZvm6n0a7RlSQDVxsdOJjtEPmiU/3639ZNSNIHFbwU4TSqv2vZEf01Zf4EXSrfa5qEOpfljCbhJMsKZAijuMuAYvLLeTkMrpQuiiFrz0ba0LJipednGPuDK+5fUd+YuHkI=
Content-Type: text/plain; charset="utf-8"
Content-ID: <6C709CCD73D24445A8908C14E7A697D3@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 906eed1b-f830-47dd-b7f8-08d6ec3a1bb8
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jun 2019 17:52:43.5483 (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: christer.holmberg@ericsson.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3131
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/sspyfkLsPHnxfMbiuScqov5ewOA>
Subject: Re: [MMUSIC] Resolving IESG issues with RFC4566bis-35: a=charset
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jun 2019 17:52:50 -0000

SGksDQoNCkkgZG9uJ3QgaGF2ZSBhIHN0cm9uZyBvcGluaW9uLCBidXQgSSB3b3VsZCByZWFsbHkg
bGlrZSB0byBhdm9pZCBhICJNVVNULU1BWS1TSE9VTEQgTk9UIiBkZWZpbml0aW9uLg0KDQpPbmUg
Ym9sZCBhcHByb2FjaCB3b3VsZCBiZSB0byBvbmx5IGFsbG93LCBhbmQgbWFuZGF0ZSBzdXBwb3J0
IG9mLCBhIHNldCBvZiBjaGFyc2V0cy4gVGhlIGRlZmluaXRpb24gYW5kIHVzYWdlIG9mIGFueSBh
ZGRpdGlvbmFsIGNoYXJzZXRzIG5lZWQgdG8gYmUgZGVmaW5lZCBpbiBhIHNlcGFyYXRlIGRvY3Vt
ZW50Lg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoNCu+7v09uIDA3LzA2LzIwMTksIDE3LjM4
LCAibW11c2ljIG9uIGJlaGFsZiBvZiBQYXVsIEt5eml2YXQiIDxtbXVzaWMtYm91bmNlc0BpZXRm
Lm9yZyBvbiBiZWhhbGYgb2YgcGt5eml2YXRAYWx1bS5taXQuZWR1PiB3cm90ZToNCg0KICAgIE1N
VVNJQyBTRFAgZmFucywNCiAgICANCiAgICBUaGUgbWVzc2FnZSBiZWxvdyBhbHJlYWR5IHdlbnQg
dG8gbW11c2ljLCBidXQgaGVyZSBJJ20gcmVkdWNpbmcgdGhlIA0KICAgIGRpc3RyaWJ1dGlvbiBs
aXN0IHRvIG9ubHkgbW11c2ljIHNvIHdlIGRvbid0IHNwYW0gdGhlIGllc2cgd2l0aCBvdXIgDQog
ICAgaW50ZXJuYWwgZGlzY3Vzc2lvbi4NCiAgICANCiAgICBJdCBzZWVtcyB0aGF0IEFsZXh5IGRv
ZXNuJ3Qgd2FudCB0byBsZXQgdXMgc3dlZXAgdGhlIGNoYXJzZXQgaXNzdWVzIA0KICAgIHVuZGVy
IHRoZSBydWcuDQogICAgDQogICAgV291bGQgaGlzIHN1Z2dlc3Rpb24gdG8gcmVzdHJpY3QgdGhl
IGNoYXJzZXRzIHBlcm1pdHRlZCB0byBiZSB1c2VkIGJlIA0KICAgIGFjY2VwdGFibGU/IFJlcGVh
dGluZyBpdDoNCiAgICANCiAgICA+PiBJIHdvdWxkIGFjdHVhbGx5IHN1Z2dlc3QgdGhhdCB0aGUg
ZG9jdW1lbnQgc2hvdWxkIHRpZ2h0ZW4gdGhlIGRlZmluaXRpb24gb2Ygd2hpY2ggY2hhcnNldHMg
YXJlIGFsbG93ZWQuIEZvciB0ZXh0dWFsIG1lZGlhIHR5cGVzIHdlIG5vdyByZWNvbW1lbmQgdXNl
IG9mIFVURi04ICh3aGljaCBzaG91bGQgYmUgdGhlIGRlZmF1bHQpIGFuZCBwb3NzaWJseSBhbGxv
d2luZyBhIGZldyBvdGhlcnMuDQogICAgPj4gDQogICAgPj4gU28gSSBzdWdnZXN0IHRoYXQgdGhl
IG5ldyBkZWZpbml0aW9uIG9mIGE9Y2hhcnNldCBiZSBhbG9uZyB0aGUgbGluZXMgb2YgIk1VU1Qg
c3VwcG9ydCBVVEYtOCBhbmQgVVMtQVNDSUkuIE1BWSBzdXBwb3J0IElTTy04ODU5LTEuIFNIT1VM
RCBOT1QgdXNlIGFueSBvdGhlciBjaGFyc2V0cyIuDQogICAgDQogICAgCVRoYW5rcywNCiAgICAJ
UGF1bA0KICAgIA0KICAgIE9uIDYvNy8xOSAxMDoyNCBBTSwgUGF1bCBLeXppdmF0IHdyb3RlOg0K
ICAgID4gQWxleHksDQogICAgPiANCiAgICA+IFdoZW4gd2UgZmlyc3QgcmVhbGl6ZWQgdGhlIGlz
c3VlcyB3aXRoIGNoYXJzZXQgd2UgdGhvdWdodCB3ZSB3ZXJlIHZlcnkgDQogICAgPiBuZWFyIHRo
ZSBlbmQgb2YgdGhlc2UgcmV2aXNpb25zLCBhbmQgdGhlcmUgZGlkbid0IHNlZW0gdG8gYmUgbXVj
aCB0YXN0ZSANCiAgICA+IGZvciBvcGVuaW5nIHRoaXMgY2FuIG9mIHdvcm1zLiBCdXQgdGhlIGNv
bGxlY3Rpb24gb2YgaWVzZyBjb21tZW50cyBoYXZlIA0KICAgID4gbGVkIG1lIHRvIGRvIGEgZmFp
ciBudW1iZXIgb2YgcmV2aXNpb25zLiBTbyBJIHdpbGwgYXNrIGFnYWluIGlmIHRoZXJlIGlzIA0K
ICAgID4gd2lsbGluZ25lc3MgdG8gbWFrZSB0aGlzIGtpbmQgb2YgY2hhbmdlLiBUaGUgbWFpbiBj
b25jZXJuIGlzIHdpdGggDQogICAgPiBiYWNrd2FyZCBjb21wYXRpYmlsaXR5IC0gaXMgdGhlcmUg
YW55IHVzZSBpbiB0aGUgd2lsZCBvZiBvdGhlciBjaGFyc2V0cy4gDQogICAgPiBJIGRvdWJ0IGl0
LCBidXQgZG9uJ3QgaGF2ZSBhbnkgZGF0YSB0byBiYWNrIHRoYXQgdXAuDQogICAgPiANCiAgICA+
IChUaGUgd2hvbGUgYT1jaGFyc2V0IHRoaW5nIGlzIGEgcGFpbiB3aXRob3V0IG11Y2ggZ2Fpbi4g
TXVjaCB0cm91YmxlIA0KICAgID4gaWRlbnRpZnlpbmcgdGhpbmdzIHRoYXQgYXJlIGFuZCBhcmVu
J3QgY2hhcnNldC1kZXBlbmRlbnQuKQ0KICAgID4gDQogICAgPiAgICAgIFRoYW5rcywNCiAgICA+
ICAgICAgUGF1bA0KICAgID4gDQogICAgPiBPbiA2LzcvMTkgODowOSBBTSwgQWxleGV5IE1lbG5p
a292IHdyb3RlOg0KICAgID4+IEhpIEJhcnJ5L1BhdWwsDQogICAgPj4NCiAgICA+PiBPbiBNb24s
IEp1biAzLCAyMDE5LCBhdCA4OjU0IFBNLCBCYXJyeSBMZWliYSB3cm90ZToNCiAgICA+Pj4gSGks
IFBhdWwuICBTdGlja2luZyBteSBvYXIgaW4gd2l0aCBBbGV4ZXkncyBoZXJlLCBqdXN0IG9uIGEg
Y291cGxlIG9mIA0KICAgID4+PiBpdGVtczoNCiAgICA+Pj4NCiAgICA+Pj4+PiBJbiBTZWN0aW9u
IDE6DQogICAgPj4+Pj4NCiAgICA+Pj4+PiBlbGVjdHJvbmljIG1haWwgdXNpbmcgdGhlIE1JTUUg
ICBleHRlbnNpb25zIFtSRkM1MzIyXQ0KICAgID4+Pj4+DQogICAgPj4+Pj4gVGhpcyBuZWVkcyBh
bm90aGVyIHJlZmVyZW5jZSBmb3IgTUlNRS4gRS5nLiBSRkMgMjA0NS4NCiAgICA+Pj4+DQogICAg
Pj4+PiBJIGRvbid0IHVuZGVyc3RhbmQuIFRoaXMgcGFyYWdyYXBoIGlzIHJlZmVyZW5jaW5nIGV4
YW1wbGVzIG9mIHByb3RvY29scw0KICAgID4+Pj4gdGhhdCBjYW4gYmUgdXNlZCB0byAqdHJhbnNw
b3J0KiBTRFAuIFJGQzUzMjIgcmVmZXJlbmNlcyB0aGUgbWFpbCANCiAgICA+Pj4+IG1lc3NhZ2UN
CiAgICA+Pj4+IGZvcm1hdCB0aGF0IHdvdWxkIGJlIHVzZWQgdG8gZW5jYXBzdWxhdGUgU0RQIGlm
IGl0IHdlcmUgdHJhbnNwb3J0ZWQgdmlhDQogICAgPj4+PiBlbWFpbC4gKFRob3VnaCBpdCBkb2Vz
bid0IGFjdHVhbGx5IG1lbnRpb24gdGhlICp0cmFuc3BvcnQqIHByb3RvY29scw0KICAgID4+Pj4g
dXNlZCBmb3IgbWFpbCBtZXNzYWdlcy4pDQogICAgPj4+Pg0KICAgID4+Pj4gSVNUTSB0aGF0IGl0
IGlzIHRoZSBjb250YWluaW5nIHByb3RvY29scyB0aGF0IHNob3VsZCByZWZlcmVuY2UgcmZjMjA0
NS4NCiAgICA+Pj4+IFJGQzUzMjIgZG9lcyBzbywgYW5kIHNvIHNheXMgaG93IHRvIGNhcnJ5IFNE
UCBpbiBtYWlsIG1lc3NhZ2VzLiBTSVAgaXMNCiAgICA+Pj4+IGl0c2VsZiBlZmZlY3RpdmVseSBh
biBleHRlbnNpb24gdG8gUkZDMjA0NSB0aG91Z2ggaXQgZG9lc24ndCBzYXkgc28uDQogICAgPj4+
DQogICAgPj4+IEFsZXhleSdzIHBvaW50IGlzIHRoYXQgeW91IGV4cGxpY2l0bHkgbWVudGlvbiAi
TUlNRSBleHRlbnNpb25zIiBhbmQNCiAgICA+Pj4gZG9uJ3QgcHJvdmlkZSBhIHJlZmVyZW5jZSBm
b3IgaXQuICBJJ2xsIGdvIGEgYml0IGZhcnRoZXIgdG8gc2F5IHRoYXQNCiAgICA+Pj4geW91J3Jl
IG5vdCBqdXN0IHRhbGtpbmcgYWJvdXQgbWVzc2FnZSAqZm9ybWF0KiBoZXJlLCBidXQgYWxzbyBT
TVRQIGFzDQogICAgPj4+IHRoZSB0cmFuc3BvcnQgKG1vcmUgY29ycmVjdGx5LCBhcHBsaWNhdGlv
bi1sYXllcikgcHJvdG9jb2wsIHllcz8gIFNvDQogICAgPj4+IHRoaXMgc2hvdWxkIHNheSBzb21l
dGhpbmcgbW9yZSBsaWtlLCAiZWxlY3Ryb25pYyBtYWlsIFtSRkM1MzIxXSB1c2luZw0KICAgID4+
PiB0aGUgTUlNRSBleHRlbnNpb25zIFtSRkMyMDQ1XSIuICBJIGRvbid0IHRoaW5rIHlvdSBuZWVk
IDUzMjIsIGJlY2F1c2UNCiAgICA+Pj4gODIyIGlzIGNpdGVkIGJ5IDIwNDUsIGFuZCB0aGF0IGlz
IG9ic29sZXRlZCBieSAyODIyLCBhbmQgdGhhdCBieSA1MzIyLg0KICAgID4+PiBCdXQgSSB0aGlu
ayB5b3UgZG8gbmVlZCB0byBjaXRlIFNNVFAgYW5kIE1JTUUuDQogICAgPj4NCiAgICA+PiBZZXMs
IGV4YWN0bHkuDQogICAgPj4NCiAgICA+Pj4+PiBJbiA2LjEwOg0KICAgID4+Pj4+DQogICAgPj4+
Pj4gICAgICBOb3RlIHRoYXQgYSBjaGFyYWN0ZXIgc2V0IHNwZWNpZmllZCBNVVNUIHN0aWxsIHBy
b2hpYml0IHRoZSANCiAgICA+Pj4+PiB1c2Ugb2YNCiAgICA+Pj4+PiAgICAgIGJ5dGVzIDB4MDAg
KE51bCksIDB4MEEgKExGKSwgYW5kIDB4MGQgKENSKS4NCiAgICA+Pj4+Pg0KICAgID4+Pj4+IFRo
aXMgZG9lc27igJl0IGFjdHVhbGx5IHNheSB3aGF0IHlvdSBpbnRlbmRlZC4gTm9uZSBvZiB0aGUg
Y29tbW9uIA0KICAgID4+Pj4+IGNoYXJzZXRzDQogICAgPj4+Pj4gcHJvaGliaXQgdGhlc2UgYnl0
ZXMuIEkgdGhpbmsgeW91IG1lYW50IHRoYXQgd2hlbiB1c2luZyBzdWNoIA0KICAgID4+Pj4+IGNo
YXJzZXRzLCB0aGVzZQ0KICAgID4+Pj4+IGNoYXJhY3RlcnMgTVVTVCBOT1QgYmUgdXNlZCBpbiB2
YWx1ZXMuDQogICAgPj4+DQogICAgPj4+IEFkZGluZyB0byB3aGF0IEFsZXhleSBzYXlzLCBhbmQg
bWF5YmUgY2xhcmlmeWluZyBhIGJpdDogQ2hhcmFjdGVyIHNldA0KICAgID4+PiBhbmQgZW5jb2Rp
bmcgYXJlIGRpZmZlcmVudCB0aGluZ3MuICBUaGUgY2hhcmFjdGVyIHNldCBpcyB0aGUNCiAgICA+
Pj4gYWJzdHJhY3Rpb24gb2YgdGhlIGNoYXJhY3RlcnMgdXNlZCwgYW5kIHRoZSBlbmNvZGluZyBp
cyBob3cgdGhleSdyZQ0KICAgID4+PiByZXByZXNlbnRlZC4gIFRoZSBlbmNvZGluZyBpcyB3aGF0
IGNyZWF0ZXMgdGhlIGJ5dGVzIG9uIHRoZSB3aXJlLiAgT25lDQogICAgPj4+IHByb2JsZW0gaXMg
dGhhdCAiQVNDSUkiIHJlZmVycyB0byBib3RoLCBzbyBpdCdzIGNvbmZ1c2luZy4gIEJ1dCB3aXRo
DQogICAgPj4+IFVuaWNvZGUsICJVbmljb2RlIiBpcyB0aGUgY2hhcmFjdGVyIHNldCBhbmQgIlVU
Ri04IiBpcyAodXN1YWxseSkgdGhlDQogICAgPj4+IGVuY29kaW5nLg0KICAgID4+DQogICAgPj4g
UmlnaHQuIEFuZCB0aGUgdGVybSAiY2hhcnNldCIgaXMgZW5jb2Rpbmcgb2YgYSBwYXJ0aWN1bGFy
IGNoYXJhY3RlciANCiAgICA+PiBzZXQuIEl0IG1pZ2h0IGJlIHdvcnRoIHVzaW5nIGl0IGJlbG93
Lg0KICAgID4+DQogICAgPj4+IEJ1dCB5b3VyIHBvaW50IGhlcmUgaXMgdGhhdCB0aGUgdGhyZWUg
Ynl0ZSB2YWx1ZXMgeW91IGxpc3QgTVVTVCBOT1QNCiAgICA+Pj4gYXBwZWFyIGluIHRoZSBzdHJp
bmcsIGFuZCB0aGF0IGhhcyBub3RoaW5nIHRvIGRvIHdpdGggdGhlIGNoYXJhY3Rlcg0KICAgID4+
PiBzZXQgb3IgdGhlIGVuY29kaW5nLiAgVGhvc2UgdGhyZWUgYnl0ZXMgYXJlIHByb2hpYml0ZWQu
DQogICAgPj4+DQogICAgPj4+IFlvdSBzYXkgdGhhdCBxdWl0ZSB3ZWxsIGluIFNlY3Rpb24gNToN
CiAgICA+Pj4NCiAgICA+Pj4gICAgIFRleHQtY29udGFpbmluZyBmaWVsZHMgc3VjaCBhcyB0aGUg
c2Vzc2lvbi1uYW1lLWZpZWxkIGFuZA0KICAgID4+PiAgICAgaW5mb3JtYXRpb24tZmllbGQgYXJl
IG9jdGV0IHN0cmluZ3MgdGhhdCBtYXkgY29udGFpbiBhbnkgb2N0ZXQgd2l0aA0KICAgID4+PiAg
ICAgdGhlIGV4Y2VwdGlvbnMgb2YgMHgwMCAoTnVsKSwgMHgwYSAoQVNDSUkgbmV3bGluZSksIGFu
ZCAweDBkIChBU0NJSQ0KICAgID4+PiAgICAgY2FycmlhZ2UgcmV0dXJuKS4NCiAgICA+Pj4NCiAg
ICA+Pj4gLi4uIGFuZCBpbiA1LjEzOg0KICAgID4+Pg0KICAgID4+PiAgICAgQXR0cmlidXRlIHZh
bHVlcyBhcmUgb2N0ZXQgc3RyaW5ncywgYW5kIE1BWSB1c2UgYW55IG9jdGV0IHZhbHVlDQogICAg
Pj4+ICAgICBleGNlcHQgMHgwMCAoTnVsKSwgMHgwQSAoTEYpLCBhbmQgMHgwRCAoQ1IpLg0KICAg
ID4+Pg0KICAgID4+PiBCdXQgaW4gNi4xMCBJIHRoaW5rIHlvdSB3YW50IHNvbWV0aGluZyBtb3Jl
IGxpa2UgdGhpczoNCiAgICA+Pj4NCiAgICA+Pj4gT0xEDQogICAgPj4+ICAgICBOb3RlIHRoYXQg
YSBjaGFyYWN0ZXIgc2V0IHNwZWNpZmllZCBNVVNUIHN0aWxsIHByb2hpYml0IHRoZSB1c2Ugb2YN
CiAgICA+Pj4gICAgIGJ5dGVzIDB4MDAgKE51bCksIDB4MEEgKExGKSwgYW5kIDB4MGQgKENSKS4g
IENoYXJhY3RlciBzZXRzIA0KICAgID4+PiByZXF1aXJpbmcNCiAgICA+Pj4gICAgIHRoZSB1c2Ug
b2YgdGhlc2UgY2hhcmFjdGVycyBNVVNUIGRlZmluZSBhIHF1b3RpbmcgbWVjaGFuaXNtIHRoYXQN
CiAgICA+Pj4gICAgIHByZXZlbnRzIHRoZXNlIGJ5dGVzIGZyb20gYXBwZWFyaW5nIHdpdGhpbiB0
ZXh0IGZpZWxkcy4NCiAgICA+Pj4gTkVXDQogICAgPj4+ICAgICBOb3RlIHRoYXQgdGhlIHJlc3Ry
aWN0aW9uIHNwZWNpZmllZCBpbiBTZWN0aW9uIDUgYXBwbGllczogdGhlc2UgDQogICAgPj4+IHN0
cmluZ3MNCiAgICA+Pj4gICAgIE1VU1QgTk9UIGNvbnRhaW4gdGhlIGJ5dGVzIDB4MDAgKE51bCks
IDB4MEEgKExGKSwgYW5kIDB4MGQgKENSKS4NCiAgICA+Pj4gICAgIENoYXJhY3RlciBlbmNvZGlu
Z3MgdGhhdCB1c2UgdGhlc2UgYnl0ZXMgTVVTVCBkZWZpbmUgYSBxdW90aW5nDQogICAgPj4+ICAg
ICBtZWNoYW5pc20gdGhhdCBwcmV2ZW50cyB0aGVzZSBieXRlcyBmcm9tIGFwcGVhcmluZyB3aXRo
aW4gdGhlIHRleHQNCiAgICA+Pj4gICAgIHN0cmluZ3MuDQogICAgPj4+IEVORA0KICAgID4+DQog
ICAgPj4gSSB0aGluayB0aGlzIGlzIG11Y2ggYmV0dGVyLCBhbHRob3VnaCAidXNlIHRoZXNlIGJ5
dGVzIiBpcyBzdGlsbCANCiAgICA+PiBhbWJpZ3VvdXMuIEUuZy4gaWYgdGhlc2UgYnl0ZXMgYXJl
IHVzZWQgdG8gc2hpZnQgYmV0d2VlbiBlbmNvZGluZyANCiAgICA+PiBtb2RlcyB3aXRoaW4gYSBw
YXJ0aWN1bGFyIGNoYXJzZXQsIHRoZW4gdGhlcmUgaXMgYSBwcm9ibGVtLiBJZiB0aGV5IA0KICAg
ID4+IGFyZSBqdXN0IHVzZWQgdG8gY29udmV5IHNwZWNpZmljIGNoYXJhY3RlcnMsIGl0IG1pZ2h0
IG5vdCBiZS4NCiAgICA+Pg0KICAgID4+IEhvd2V2ZXIsIHNlZSBteSBjb21tZW50IGJlbG93Lg0K
ICAgID4+DQogICAgPj4+PiBJIGRvbid0IHJlY2FsbCB3aGF0IHRoZSBzdGF0ZSBvZiBjaGFyYWN0
ZXIgc2V0IGRlZmluaXRpb25zIHdhcyBpbiAxOTk4DQogICAgPj4+PiB3aGVuIHRoaXMgd2FzIGZp
cnN0IHB1Ymxpc2hlZC4gQnV0IGl0IGFwcGVhcnMgdGhhdCB0aGV5IGdvdCBjYXJyaWVkIA0KICAg
ID4+Pj4gYXdheQ0KICAgID4+Pj4gYW5kIG92ZXItZ2VuZXJhbGl6ZWQuIEl0IGlzIGVhc3kgdG8g
dW5kZXJzdGFuZCBob3cgb25lIG1pZ2h0IGNob29zZSB0bw0KICAgID4+Pj4gdXNlIElTTyA4ODU5
LTEgcmF0aGVyIHRoYW4gVVRGLTggc2luY2UgdGhleSBhcmUgY2xvc2VseSByZWxhdGVkIGFuZA0K
ICAgID4+Pj4gYnl0ZS1vcmllbnRlZC4gQnV0IGl0IGlzIHVuY2xlYXIgaG93IG9uZSBtaWdodCB1
c2Ugc29tZSBvdGhlciANCiAgICA+Pj4+IHJlZ2lzdGVyZWQNCiAgICA+Pj4+IGNoYXJzZXRzLCBz
dWNoIGFzIEVCQ0RJQywgb3Igb3RoZXIgZW5jb2RpbmdzIG9mIElTTyAxMDY0Niwgc3VjaCBhcyAN
CiAgICA+Pj4+IFVURi0xNi4NCiAgICA+Pj4+DQogICAgPj4+PiBUaGUgYm90dG9tIGxpbmUgaXMg
dGhhdCB1c2Ugb2YgYWx0ZXJuYXRlIGNoYXJzZXRzIG90aGVyIHRoYW4gODg1OS0xIGlzDQogICAg
Pj4+PiB1bmRlcnNwZWNpZmllZC4gV2UgY29uc2lkZXJlZCByZXZhbXBpbmcgdGhlIGRlZmluaXRp
b24gb2YgY2hhcnNldCwgYnV0DQogICAgPj4+PiBkaWRuJ3Qgd2FudCB0byBvcGVuIHRoYXQgY2Fu
IG9mIHdvcm1zLCBzaW5jZSBpbiBwcmFjdGljZSBpdCBpc24ndCBhbiANCiAgICA+Pj4+IGlzc3Vl
Lg0KICAgID4+Pg0KICAgID4+PiBJIGFwcHJlY2lhdGUgdGhhdCwgYW5kIEkgdGhpbmsgdGhpcyBp
c24ndCB0aGUgcGxhY2UgdG8gdGFja2xlIHRoYXQuDQogICAgPj4+IFNvIHdlIGp1c3QgbmVlZCB0
byBnZXQgdGhlIHRleHQgaGVyZSB0byBhY2N1cmF0ZWx5IHJlZmxlY3Qgd2hhdCB5b3UncmUNCiAg
ICA+Pj4gdHJ5aW5nIHRvIHNheS4NCiAgICA+Pg0KICAgID4+IEkgd291bGQgYWN0dWFsbHkgc3Vn
Z2VzdCB0aGF0IHRoZSBkb2N1bWVudCBzaG91bGQgdGlnaHRlbiB0aGUgDQogICAgPj4gZGVmaW5p
dGlvbiBvZiB3aGljaCBjaGFyc2V0cyBhcmUgYWxsb3dlZC4gRm9yIHRleHR1YWwgbWVkaWEgdHlw
ZXMgd2UgDQogICAgPj4gbm93IHJlY29tbWVuZCB1c2Ugb2YgVVRGLTggKHdoaWNoIHNob3VsZCBi
ZSB0aGUgZGVmYXVsdCkgYW5kIHBvc3NpYmx5IA0KICAgID4+IGFsbG93aW5nIGEgZmV3IG90aGVy
cy4NCiAgICA+Pg0KICAgID4+IFNvIEkgc3VnZ2VzdCB0aGF0IHRoZSBuZXcgZGVmaW5pdGlvbiBv
ZiBhPWNoYXJzZXQgYmUgYWxvbmcgdGhlIGxpbmVzIA0KICAgID4+IG9mICJNVVNUIHN1cHBvcnQg
VVRGLTggYW5kIFVTLUFTQ0lJLiBNQVkgc3VwcG9ydCBJU08tODg1OS0xLiBTSE9VTEQgDQogICAg
Pj4gTk9UIHVzZSBhbnkgb3RoZXIgY2hhcnNldHMiLg0KICAgID4+DQogICAgPj4+IEhvcGluZyB0
byBiZSBoZWxwZnVsLA0KICAgID4+PiBCYXJyeQ0KICAgID4+Pg0KICAgID4+DQogICAgPiANCiAg
ICA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICAg
PiBtbXVzaWMgbWFpbGluZyBsaXN0DQogICAgPiBtbXVzaWNAaWV0Zi5vcmcNCiAgICA+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljDQogICAgDQogICAgX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCiAgICBtbXVzaWMgbWFp
bGluZyBsaXN0DQogICAgbW11c2ljQGlldGYub3JnDQogICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9tbXVzaWMNCiAgICANCg0K


From nobody Sat Jun  8 13:29:22 2019
Return-Path: <noreply@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 68319120099; Sat,  8 Jun 2019 13:29:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Russ Housley via Datatracker <noreply@ietf.org>
To: <secdir@ietf.org>
Cc: draft-ietf-mmusic-sdp-uks.all@ietf.org, ietf@ietf.org, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Russ Housley <housley@vigilsec.com>
Message-ID: <156002574538.10095.7918697870650906635@ietfa.amsl.com>
Date: Sat, 08 Jun 2019 13:29:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ImkyrFlCYR-jD3DQkSkq9apY8xY>
Subject: [MMUSIC] Secdir last call review of draft-ietf-mmusic-sdp-uks-05
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jun 2019 20:29:06 -0000

Reviewer: Russ Housley
Review result: Has Issues

I reviewed this document as part of the Security Directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the Security Area
Directors.  Document authors, document editors, and WG chairs should
treat these comments just like any other IETF Last Call comments.

Document: draft-ietf-mmusic-sdp-uks-05
Reviewer: Russ Housley
Review Date: 2019-06-08
IETF LC End Date: 2019-06-19
IESG Telechat date: unknown

Summary: Has Issues


Major Concerns:

In Section 2 (and other places), explaining the attack, the authors
correctly explain that  a malicious participant in a protocol claims to
control a key that is in reality controlled by some other actor.  The
confidentiality and access control implications need to be explained.
The malicious actor cannot decrypt the traffic.  However, victum may
release information to the wrong party because of the authentication
failure.  Please add text in Section 2, Section 3.1, and Section 4.1
on this topic.

In Section 3.2, SHA-256 is the only supported hash function.  In some
manner algorithm agility needs to be provided.  This could be done by
using the same hash function as TLS is negotiating elsewhere, by
including a hash algorithm identifier, or explicitly stating that a
new TLS extension will be defined for use with another hash function
if flaws are found in SHA-256.


Minor Concerns:

The title page header and the Introduction indicate that this document
updates RFC 8122, but the Abstract does not mention this.  Please add
this to the Abstract.

In Section 3.2, I think that [SHA] should be an informative reference.
If a normative reference for SHA-256 is needed, please cite FIPS 180.


Nits:

Section 3: I suggested rewording:

   OLD:
   Both SIP and WebRTC identity providers are not
   required to perform this validation.  This is not an issue because
   verifying control of the associated keys is not a necessary condition
   for a secure protocol, nor would it be sufficient to prevent attack
   [SIGMA].

   NEW:
   Neither SIP nor WebRTC identity providers are required to
   perform this validation; however, this is not an issue because
   verifying control of the associated keys is not a necessary condition
   for a secure protocol, nor would it be sufficient to prevent attack
   [SIGMA].


From nobody Sat Jun  8 15:12:49 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 554ED120111 for <mmusic@ietfa.amsl.com>; Sat,  8 Jun 2019 15:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j909ZEd33weV for <mmusic@ietfa.amsl.com>; Sat,  8 Jun 2019 15:12:46 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B2C51200D5 for <mmusic@ietf.org>; Sat,  8 Jun 2019 15:12:45 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x58MBbVr011602 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 8 Jun 2019 18:12:41 -0400
To: Christer Holmberg <christer.holmberg@ericsson.com>, IETF MMUSIC WG <mmusic@ietf.org>
References: <155922060388.22145.12090008162284261785.idtracker@ietfa.amsl.com> <5b944fc8-3f97-55e6-2faf-45bfd11c5837@alum.mit.edu> <CALaySJJjwG26NLCJqFdo2yW_JhYCYbY+ADHENa490XqM539U2A@mail.gmail.com> <d1954b5e-f7bb-40e1-88dc-5565212b517d@www.fastmail.com> <1f37b132-98b7-af5e-7997-e0fd095ff207@alum.mit.edu> <834ef36e-e664-55de-292f-8c7cf3b3b868@alum.mit.edu> <1D536F12-1008-462C-BFF8-876B6A03F274@ericsson.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <15a1e572-dd27-a9c4-ef9d-242ec30f2e7d@alum.mit.edu>
Date: Sat, 8 Jun 2019 18:11:37 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <1D536F12-1008-462C-BFF8-876B6A03F274@ericsson.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/lUn_dc-ihSlcSqe1Kk0icgus9Ec>
Subject: Re: [MMUSIC] Resolving IESG issues with RFC4566bis-35: a=charset
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jun 2019 22:12:48 -0000

On 6/8/19 1:52 PM, Christer Holmberg wrote:
> Hi,
> 
> I don't have a strong opinion, but I would really like to avoid a "MUST-MAY-SHOULD NOT" definition.
> 
> One bold approach would be to only allow, and mandate support of, a set of charsets. The definition and usage of any additional charsets need to be defined in a separate document.

While I think it would be possible to restrict what any new usages do, 
the problem is covering existing usages. (Even though this may be a 
non-existent problem.)

ISTM there is an interesting problem when using any charset that 
includes multibyte sequences. A charset-dependent part always begins 
midway through a line, and consists of a byte-string followed by CR LF. 
The byte-string consists of a sequence of bytes not including NUL, CR, LF.

This means that anywhere that the syntax resolves to byte-string, it 
allows sequences of bytes that may not be valid in the charset in which 
that is interpreted. This is *not* a syntax error. But presumably this 
should be treated as a semantic error in context. This is not currently 
called out anywhere. Seems like it should be.

Maybe if we call out this problem, it can be considered to resolve the 
problem of the ambiguity in using troublesome charsets such as UTF-16. 
But this isn't just a problem with non-default charsets - it can also 
occur with UTF-8. If this is good enough then it is a simple solution to 
the problem.

	Thanks,
	Paul


> Regards,
> 
> Christer
> 
> 
> ﻿On 07/06/2019, 17.38, "mmusic on behalf of Paul Kyzivat" <mmusic-bounces@ietf.org on behalf of pkyzivat@alum.mit.edu> wrote:
> 
>      MMUSIC SDP fans,
>      
>      The message below already went to mmusic, but here I'm reducing the
>      distribution list to only mmusic so we don't spam the iesg with our
>      internal discussion.
>      
>      It seems that Alexy doesn't want to let us sweep the charset issues
>      under the rug.
>      
>      Would his suggestion to restrict the charsets permitted to be used be
>      acceptable? Repeating it:
>      
>      >> I would actually suggest that the document should tighten the definition of which charsets are allowed. For textual media types we now recommend use of UTF-8 (which should be the default) and possibly allowing a few others.
>      >>
>      >> So I suggest that the new definition of a=charset be along the lines of "MUST support UTF-8 and US-ASCII. MAY support ISO-8859-1. SHOULD NOT use any other charsets".
>      
>      	Thanks,
>      	Paul
>      
>      On 6/7/19 10:24 AM, Paul Kyzivat wrote:
>      > Alexy,
>      >
>      > When we first realized the issues with charset we thought we were very
>      > near the end of these revisions, and there didn't seem to be much taste
>      > for opening this can of worms. But the collection of iesg comments have
>      > led me to do a fair number of revisions. So I will ask again if there is
>      > willingness to make this kind of change. The main concern is with
>      > backward compatibility - is there any use in the wild of other charsets.
>      > I doubt it, but don't have any data to back that up.
>      >
>      > (The whole a=charset thing is a pain without much gain. Much trouble
>      > identifying things that are and aren't charset-dependent.)
>      >
>      >      Thanks,
>      >      Paul
>      >
>      > On 6/7/19 8:09 AM, Alexey Melnikov wrote:
>      >> Hi Barry/Paul,
>      >>
>      >> On Mon, Jun 3, 2019, at 8:54 PM, Barry Leiba wrote:
>      >>> Hi, Paul.  Sticking my oar in with Alexey's here, just on a couple of
>      >>> items:
>      >>>
>      >>>>> In Section 1:
>      >>>>>
>      >>>>> electronic mail using the MIME   extensions [RFC5322]
>      >>>>>
>      >>>>> This needs another reference for MIME. E.g. RFC 2045.
>      >>>>
>      >>>> I don't understand. This paragraph is referencing examples of protocols
>      >>>> that can be used to *transport* SDP. RFC5322 references the mail
>      >>>> message
>      >>>> format that would be used to encapsulate SDP if it were transported via
>      >>>> email. (Though it doesn't actually mention the *transport* protocols
>      >>>> used for mail messages.)
>      >>>>
>      >>>> ISTM that it is the containing protocols that should reference rfc2045.
>      >>>> RFC5322 does so, and so says how to carry SDP in mail messages. SIP is
>      >>>> itself effectively an extension to RFC2045 though it doesn't say so.
>      >>>
>      >>> Alexey's point is that you explicitly mention "MIME extensions" and
>      >>> don't provide a reference for it.  I'll go a bit farther to say that
>      >>> you're not just talking about message *format* here, but also SMTP as
>      >>> the transport (more correctly, application-layer) protocol, yes?  So
>      >>> this should say something more like, "electronic mail [RFC5321] using
>      >>> the MIME extensions [RFC2045]".  I don't think you need 5322, because
>      >>> 822 is cited by 2045, and that is obsoleted by 2822, and that by 5322.
>      >>> But I think you do need to cite SMTP and MIME.
>      >>
>      >> Yes, exactly.
>      >>
>      >>>>> In 6.10:
>      >>>>>
>      >>>>>      Note that a character set specified MUST still prohibit the
>      >>>>> use of
>      >>>>>      bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
>      >>>>>
>      >>>>> This doesn’t actually say what you intended. None of the common
>      >>>>> charsets
>      >>>>> prohibit these bytes. I think you meant that when using such
>      >>>>> charsets, these
>      >>>>> characters MUST NOT be used in values.
>      >>>
>      >>> Adding to what Alexey says, and maybe clarifying a bit: Character set
>      >>> and encoding are different things.  The character set is the
>      >>> abstraction of the characters used, and the encoding is how they're
>      >>> represented.  The encoding is what creates the bytes on the wire.  One
>      >>> problem is that "ASCII" refers to both, so it's confusing.  But with
>      >>> Unicode, "Unicode" is the character set and "UTF-8" is (usually) the
>      >>> encoding.
>      >>
>      >> Right. And the term "charset" is encoding of a particular character
>      >> set. It might be worth using it below.
>      >>
>      >>> But your point here is that the three byte values you list MUST NOT
>      >>> appear in the string, and that has nothing to do with the character
>      >>> set or the encoding.  Those three bytes are prohibited.
>      >>>
>      >>> You say that quite well in Section 5:
>      >>>
>      >>>     Text-containing fields such as the session-name-field and
>      >>>     information-field are octet strings that may contain any octet with
>      >>>     the exceptions of 0x00 (Nul), 0x0a (ASCII newline), and 0x0d (ASCII
>      >>>     carriage return).
>      >>>
>      >>> ... and in 5.13:
>      >>>
>      >>>     Attribute values are octet strings, and MAY use any octet value
>      >>>     except 0x00 (Nul), 0x0A (LF), and 0x0D (CR).
>      >>>
>      >>> But in 6.10 I think you want something more like this:
>      >>>
>      >>> OLD
>      >>>     Note that a character set specified MUST still prohibit the use of
>      >>>     bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).  Character sets
>      >>> requiring
>      >>>     the use of these characters MUST define a quoting mechanism that
>      >>>     prevents these bytes from appearing within text fields.
>      >>> NEW
>      >>>     Note that the restriction specified in Section 5 applies: these
>      >>> strings
>      >>>     MUST NOT contain the bytes 0x00 (Nul), 0x0A (LF), and 0x0d (CR).
>      >>>     Character encodings that use these bytes MUST define a quoting
>      >>>     mechanism that prevents these bytes from appearing within the text
>      >>>     strings.
>      >>> END
>      >>
>      >> I think this is much better, although "use these bytes" is still
>      >> ambiguous. E.g. if these bytes are used to shift between encoding
>      >> modes within a particular charset, then there is a problem. If they
>      >> are just used to convey specific characters, it might not be.
>      >>
>      >> However, see my comment below.
>      >>
>      >>>> I don't recall what the state of character set definitions was in 1998
>      >>>> when this was first published. But it appears that they got carried
>      >>>> away
>      >>>> and over-generalized. It is easy to understand how one might choose to
>      >>>> use ISO 8859-1 rather than UTF-8 since they are closely related and
>      >>>> byte-oriented. But it is unclear how one might use some other
>      >>>> registered
>      >>>> charsets, such as EBCDIC, or other encodings of ISO 10646, such as
>      >>>> UTF-16.
>      >>>>
>      >>>> The bottom line is that use of alternate charsets other than 8859-1 is
>      >>>> underspecified. We considered revamping the definition of charset, but
>      >>>> didn't want to open that can of worms, since in practice it isn't an
>      >>>> issue.
>      >>>
>      >>> I appreciate that, and I think this isn't the place to tackle that.
>      >>> So we just need to get the text here to accurately reflect what you're
>      >>> trying to say.
>      >>
>      >> I would actually suggest that the document should tighten the
>      >> definition of which charsets are allowed. For textual media types we
>      >> now recommend use of UTF-8 (which should be the default) and possibly
>      >> allowing a few others.
>      >>
>      >> So I suggest that the new definition of a=charset be along the lines
>      >> of "MUST support UTF-8 and US-ASCII. MAY support ISO-8859-1. SHOULD
>      >> NOT use any other charsets".
>      >>
>      >>> Hoping to be helpful,
>      >>> Barry
>      >>>
>      >>
>      >
>      > _______________________________________________
>      > mmusic mailing list
>      > mmusic@ietf.org
>      > https://www.ietf.org/mailman/listinfo/mmusic
>      
>      _______________________________________________
>      mmusic mailing list
>      mmusic@ietf.org
>      https://www.ietf.org/mailman/listinfo/mmusic
>      
> 


From nobody Sat Jun  8 18:15:57 2019
Return-Path: <adam@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8664512011E; Sat,  8 Jun 2019 18:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 oXEvkfmsepVh; Sat,  8 Jun 2019 18:15:45 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B1ED1200B5; Sat,  8 Jun 2019 18:15:45 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x591FeJp068825 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 8 Jun 2019 20:15:41 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1560042943; bh=8fMpHMECg3wL4y3Dozi6O9eTsA9TMdQoYgM/JkpVTo0=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=LN9D0Ay/e7mVwQbRkSe37cGDiMbVRGQkqf07NID38JOuifE3LvjOFlYDnsOjsz3rT fghA4BzXhRSKmTMhOLZIF188fyTeRkLnlZA2vABobx3sAvmim1NGwh4TJAk5LBPOF8 FYYwS/Dymo03Iekmr3M9Zv2t/a39idFz7jimFH/U=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: Russ Housley <housley@vigilsec.com>, secdir@ietf.org
Cc: draft-ietf-mmusic-sdp-uks.all@ietf.org, ietf@ietf.org, mmusic@ietf.org
References: <156002574538.10095.7918697870650906635@ietfa.amsl.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <ee60f695-c0bf-39c6-0581-47ca92fcb5db@nostrum.com>
Date: Sat, 8 Jun 2019 20:15:34 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <156002574538.10095.7918697870650906635@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/PaQiLUkTbJj-_pB5376gEq9zWfk>
Subject: Re: [MMUSIC] Secdir last call review of draft-ietf-mmusic-sdp-uks-05
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jun 2019 01:15:48 -0000

On 6/8/19 3:29 PM, Russ Housley via Datatracker wrote:
> In Section 3.2, SHA-256 is the only supported hash function.  In some
> manner algorithm agility needs to be provided.  This could be done by
> using the same hash function as TLS is negotiating elsewhere, by
> including a hash algorithm identifier, or explicitly stating that a
> new TLS extension will be defined for use with another hash function
> if flaws are found in SHA-256.


Addressing just this point, as I think it was an oversight. Section 3.2 
contains the text:


>    Note:  Should SHA-256 prove to be inadequate at some point in the
>       future (see [AGILITY]), a new TLS extension can be defined that
>       uses a different hash function.


/a


From nobody Sat Jun  8 18:24:34 2019
Return-Path: <adam@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44AD3120052; Sat,  8 Jun 2019 18:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 es2O7aih4T3y; Sat,  8 Jun 2019 18:24:22 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A06941200C1; Sat,  8 Jun 2019 18:24:22 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x591OJpI070141 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 8 Jun 2019 20:24:21 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1560043462; bh=7NhwZ618HsxzuEg7X1ArEIdw8bIDvWP3eKm3Hvsmww0=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=lVqm8w0/AU/nws+Mn3Raa7hYdAT9mL+o7s63Ii055E7turTDjziBXUnjMjkYpksH2 3PjJ9YStzWQ01iRuRysNMjHXaHoAQ8+c9sSS9Eu5RDhhv/SDawTBVjpCulgn3co533 Z/1Ti5a8Tsb3VcxZ+i8esSA0lEuHET22cxbTk8uE=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: Russ Housley <housley@vigilsec.com>, secdir@ietf.org
Cc: draft-ietf-mmusic-sdp-uks.all@ietf.org, ietf@ietf.org, mmusic@ietf.org
References: <156002574538.10095.7918697870650906635@ietfa.amsl.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <58bd274d-7411-d507-761f-32368874598e@nostrum.com>
Date: Sat, 8 Jun 2019 20:24:14 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <156002574538.10095.7918697870650906635@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/f0wdYICwRYt1vIpB3WMsN6_brJc>
Subject: Re: [MMUSIC] Secdir last call review of draft-ietf-mmusic-sdp-uks-05
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jun 2019 01:24:25 -0000

On 6/8/19 3:29 PM, Russ Housley via Datatracker wrote:
> In Section 3.2, I think that [SHA] should be an informative reference.
> If a normative reference for SHA-256 is needed, please cite FIPS 180.


Russ -- can you explain this suggestion further? RFC 6234 has been in 
the downref registry [1] since 2013, and is frequently referenced 
normatively by Standards-Track RFCs. Is there something special about 
the UKS document that makes this common practice inappropriate for it? 
To be clear, I specifically considered this reference when processing 
the UKS document, and believe the second paragraph of section 3 of RFC 
3967 to be applicable.

/a


____
[1] https://datatracker.ietf.org/doc/downref/


From nobody Mon Jun 10 20:59:43 2019
Return-Path: <mt@lowentropy.net>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFCE1120092; Mon, 10 Jun 2019 20:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=qVWfTLcL; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=uqZscGUP
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 BCx8LaAI2iIF; Mon, 10 Jun 2019 20:59:30 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F4FA12001A; Mon, 10 Jun 2019 20:59:30 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6EA7822502; Mon, 10 Jun 2019 23:59:28 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Mon, 10 Jun 2019 23:59:28 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm2; bh=b6lxHbp0TKVAExiW7wF6xIWKmcYK TChAyLkbQvZ8GCc=; b=qVWfTLcL46FIWKrlPX9kiNXCCZGvX7kIKgeI7qnhaO+r ZYill8khDbQzvEgu0VnReHvzpdep6nUwq9safbkm4ODpLiNepeykYUK6UAxfrPfr FqyvaClxXrrtcJdHZ7ndOspDFFXzPgxggUhUZH6Evkjuo/pPg1A7obcjrKbjOlVy pzBUMev/KLS3pNPsfIT7Gea6XK4n/vnkIMOCMwQzaosz9RcBxGXJ/5fTHg89ngJr 8ERVZAU/oWvnASJoalbhM4I4Skt2aV08R49+l/itQ2lOdi9CQ9iijj+PbbzrSGFW V1IgcjmNm/nNhvetJP4ShDaVloMGwYDH8yw0WT5yLQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=b6lxHb p0TKVAExiW7wF6xIWKmcYKTChAyLkbQvZ8GCc=; b=uqZscGUPy4NV+hBWl55Yxn YRyTsJ20IxoELozV3z/xqBoOcEbiSvdEkYk1AzNIh6xiKBfChNDacNKfvdg+63kP v3iXvE8qvR37+BlweVSoUugZlehPJSb5xYtm+Ms9BMKktV4Ovs4KshqPMJUclJY9 OiQNES+b5hMcNjQjPbPTgh5YSQyWKIg2FrmQobM4tqmvOqY1ModLXZ5Lrg9g4nz3 So2RLyCbanVWJnXAGRJ9lewueDaM6ZFTOVtYexRuqoJ5CR4gs6XLS7FbT6RZ18SX RSa8RRo52yLMjY1cv0onTEJzvGymjP9tgUy54o26EcuvKQ6iE9SSLZRkta19E0Aw ==
X-ME-Sender: <xms:Hyf_XP1jYgoavoXWvl3BXvuLkpr_fmVah_Wx8veoF72CK1IuFdOH7Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudehfedgjeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecuff homhgrihhnpehgihhthhhusgdrtghomhenucfrrghrrghmpehmrghilhhfrhhomhepmhht sehlohifvghnthhrohhphidrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:Hyf_XA9DgVPenJtMaACFjdw_Gaa_etqD5JJoymmh2y4NRVMcf_amYg> <xmx:Hyf_XAunkGUiKHcSaPdMfDz5u5kXyxKh8xk0oQWfZl56xGCtfgxwcQ> <xmx:Hyf_XGrXi-6eQ8NediPvsOb4aMkOPp-KuJLftS4uw9ljcn6TVAMzZw> <xmx:ICf_XG_6Lr3RzcaZTa2yGNmp04bLhvsmovFEbxqTNe79Hud5y4RR9Q>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9C59DE00A1; Mon, 10 Jun 2019 23:59:27 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.6-663-gf46ad30-fmstable-20190607v1
Mime-Version: 1.0
Message-Id: <f273b86d-b575-4633-baaf-6b3a8ff85ee7@www.fastmail.com>
In-Reply-To: <156002574538.10095.7918697870650906635@ietfa.amsl.com>
References: <156002574538.10095.7918697870650906635@ietfa.amsl.com>
Date: Tue, 11 Jun 2019 13:59:31 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: "Russ Housley" <housley@vigilsec.com>, secdir@ietf.org
Cc: draft-ietf-mmusic-sdp-uks.all@ietf.org, ietf@ietf.org, mmusic <mmusic@ietf.org>
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/fEa5P8rdGsR9-LIZIXFvBhTBdqs>
Subject: Re: [MMUSIC] Secdir last call review of draft-ietf-mmusic-sdp-uks-05
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jun 2019 03:59:33 -0000

Thanks Russ!

I've staged changes based on your review.  You can see those here: 
https://github.com/martinthomson/sdp-uks/pull/10

On Sun, Jun 9, 2019, at 06:29, Russ Housley via Datatracker wrote:
> In Section 2 (and other places), explaining the attack, the authors
> correctly explain that  a malicious participant in a protocol claims to
> control a key that is in reality controlled by some other actor.  The
> confidentiality and access control implications need to be explained.
> The malicious actor cannot decrypt the traffic.  However, victum may
> release information to the wrong party because of the authentication
> failure.  Please add text in Section 2, Section 3.1, and Section 4.1
> on this topic.

Thanks for catching this.  It's definitely an important point.

I've added this to S2, and added shorter statements to the other sections.

An unknown key-share attack does not result in the attacker having access to any
confidential information exchanged between victims.  However, the failure in
mutual authentication can enable other attacks.  A victim might send information
to the wrong entity as a result.  Where information is interpreted in context,
misrepresenting that context could lead to the information being misinterpreted.
 
> In Section 3.2, SHA-256 is the only supported hash function.  In some
> manner algorithm agility needs to be provided.  This could be done by
> using the same hash function as TLS is negotiating elsewhere, by
> including a hash algorithm identifier, or explicitly stating that a
> new TLS extension will be defined for use with another hash function
> if flaws are found in SHA-256.

As Adam observed, this is mentioned specifically.  We discussed this point at some length and the document lists the "new extension" path as a way of addressing the need for agility.

> Minor Concerns:
> 
> The title page header and the Introduction indicate that this document
> updates RFC 8122, but the Abstract does not mention this.  Please add
> this to the Abstract.

Done.

> In Section 3.2, I think that [SHA] should be an informative reference.
> If a normative reference for SHA-256 is needed, please cite FIPS 180.

Adam covered this, I think.  I don't know what the rules are here and will be guided by others.


From nobody Mon Jun 17 03:05:43 2019
Return-Path: <noreply@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D3E3D1200F4; Mon, 17 Jun 2019 03:05:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: mmusic@ietf.org, ietf@ietf.org, draft-ietf-mmusic-ice-sip-sdp.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.98.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <156076592979.10786.4565137418480183594@ietfa.amsl.com>
Date: Mon, 17 Jun 2019 03:05:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xsmbgWll5T8X40nMTTKy5Nt01f4>
Subject: [MMUSIC] Genart last call review of draft-ietf-mmusic-ice-sip-sdp-36
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2019 10:05:30 -0000

Reviewer: Stewart Bryant
Review result: Ready with Nits

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

For more information, please see the FAQ at

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

Document: draft-ietf-mmusic-ice-sip-sdp-36
Reviewer: Stewart Bryant
Review Date: 2019-06-17
IETF LC End Date: 2019-06-20
IESG Telechat date: Not scheduled for a telechat

Summary: This is very much a review by a non-specialist. The document is well
written, but has a small number of nits that need looking at before publication.

Major issues: None

Minor issues: None

Nits/editorial comments:

ID-Nits points out the following:
  -- Obsolete informational reference (is this intentional?): RFC 4091
     (Obsoleted by RFC 5245)
  -- Obsolete informational reference (is this intentional?): RFC 4092
     (Obsoleted by RFC 5245)
>From the text it looks like the updated RFC should be the reference that this
memo uses.

====
The following abbreviations are not in the RFC Editor's well known list and
should be expanded on first use:
    STUN
    SDP
    FQDN
    PSTN



From nobody Mon Jun 17 08:34:50 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB20120233 for <mmusic@ietfa.amsl.com>; Mon, 17 Jun 2019 08:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5B9ZOmpquYit for <mmusic@ietfa.amsl.com>; Mon, 17 Jun 2019 08:34:47 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B9D2120254 for <mmusic@ietf.org>; Mon, 17 Jun 2019 08:34:39 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x5HFYCdA031192 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 17 Jun 2019 11:34:13 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: mmusic@ietf.org, Mark Handley <M.Handley@cs.ucl.ac.uk>, "'Colin Perkins'" <csp@csperkins.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>, Henning Schulzrinne <hgs@cs.columbia.edu>
References: <d34a9b29-de79-3809-1520-2e2421e441bc@alum.mit.edu>
Message-ID: <9e5b8ed3-3b3f-35ae-985d-b8da2c78d1de@alum.mit.edu>
Date: Mon, 17 Jun 2019 11:34:12 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <d34a9b29-de79-3809-1520-2e2421e441bc@alum.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/nAY4e_-hB8B3PyBYEcpsZJp85UA>
Subject: Re: [MMUSIC] Resolving IESG issues with RFC4566bis-35: "a=type" impact on media direction default
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2019 15:34:49 -0000

Once more, I'm looking for insight, especially old timers (Mark, Van, 
Colin, Magnus, Henning) from RFC2327 days. If I don't hear anything I'm 
going to change the text so this "type-specific" defaulting of 
directionality no longer appears to be normative.

	Thanks,
	Paul

On 6/6/19 12:56 PM, Paul Kyzivat wrote:
> I've been working to resolve the IESG issues with RFC4566bis-35.
> I think I have resolved most of them, but I have a couple where I feel I 
> need input from the wg. This is one of those:
> 
> "a=type" impact on media direction default:
> 
> While I was resolving a comment on Section 6.9 (a=type) I noticed what I 
> think may be a new issue. The text says:
> 
>     "recvonly" should be the default for "type:broadcast" sessions,
>     "type:meeting" should imply "sendrecv", and "type:moderated" should
>     indicate the use of a floor control tool and that the media tools are
>     started so as to mute new sites joining the multimedia conference.
> 
>     Specifying the attribute "type:H332" indicates that this loosely
>     coupled session is part of an H.332 session as defined in the ITU
>     H.332 specification [ITU.H332.1998].  Media tools should be started
>     "recvonly".
> 
> This seems to imply that the *default* media direction 
> (sendonly/recvonly/...) will vary depending on the value of the type 
> attribute. Yet it isn't written in a normative manner. (This language 
> dates back to RFC2327.)
> 
> My first reaction to this is that while it is written oddly the intent 
> is only that these are suggestions for what the creator of the SDP 
> should use. But then I also found language about this in section 6.7 
> (Media Direction Attributes):
> 
>     If none of the media direction attributes is present at either
>     session level or media level, "sendrecv" SHOULD be assumed as the
>     default for sessions that are not of the multimedia conference type
>     "broadcast" or "H332" (see below).
> 
> This language was not in RFC2327 - it was added in RFC4566. (Probably by 
> me!)
> 
> My current thinking is that this is messed up. At the time of the 
> writing in RFC2327 the use case in mind was announcements via SAP. This 
> really doesn't work right in an offer/answer context.
> 
> I'm inclined to take the language about type-specific directionality out 
> in both places. Or, if that can't be done for reasons of backward 
> compatibility, then perhaps qualify it as only applying in the case of 
> announcements.
> 
> I need feedback here!
> 
>      Thanks,
>      Paul
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> 

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


From nobody Tue Jun 18 10:14:38 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D098120091; Tue, 18 Jun 2019 10:14:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.98.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mmusic@ietf.org
Message-ID: <156087807004.8279.17078588069758754087@ietfa.amsl.com>
Date: Tue, 18 Jun 2019 10:14:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/gGNN_1g7ighwB4Axro_7BGRL2aE>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-rfc4566bis-36.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2019 17:14:30 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : SDP: Session Description Protocol
        Authors         : Ali Begen
                          Paul Kyzivat
                          Colin Perkins
                          Mark Handley
	Filename        : draft-ietf-mmusic-rfc4566bis-36.txt
	Pages           : 62
	Date            : 2019-06-18

Abstract:
   This memo defines the Session Description Protocol (SDP).  SDP is
   intended for describing multimedia sessions for the purposes of
   session announcement, session invitation, and other forms of
   multimedia session initiation.  This document obsoletes RFC 4566.


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

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-rfc4566bis-36
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-rfc4566bis-36

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-rfc4566bis-36


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Jun 18 11:27:12 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6752712041B for <mmusic@ietfa.amsl.com>; Tue, 18 Jun 2019 11:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R2rJGRY_xQo5 for <mmusic@ietfa.amsl.com>; Tue, 18 Jun 2019 11:27:09 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1C0612041A for <mmusic@ietf.org>; Tue, 18 Jun 2019 11:27:08 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x5IIR6eQ009479 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Tue, 18 Jun 2019 14:27:07 -0400
References: <156087807039.8279.7260561886700433766.idtracker@ietfa.amsl.com>
To: IETF MMUSIC WG <mmusic@ietf.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Forwarded-Message-Id: <156087807039.8279.7260561886700433766.idtracker@ietfa.amsl.com>
Message-ID: <8fdacb30-9cba-6827-dd53-146e04d6eb40@alum.mit.edu>
Date: Tue, 18 Jun 2019 14:27:06 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <156087807039.8279.7260561886700433766.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/PvJNQLuNTx2GdzlSv82_D_eRWN4>
Subject: [MMUSIC] UPDATED: draft-ietf-mmusic-rfc4566bis-36.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2019 18:27:11 -0000

Here is updated version of RFC4566bis. The -36 version addresses IESG 
comments.

For just these most recent changes, since -35:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-rfc4566bis-36

For all changes since RFC4566:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-rfc4566bis-36;url1=rfc4566

Of particular note:

The description of a=type said that the values it mentions are 
"suggested", implying that others may be possible without defining any 
way to define semantics for them. This wasn't written in a normative way.

I've reworded the section (6.9) so the listed values are exhaustive. But 
I didn't include any mechanism for backward compatible extensions. I'm 
now thinking we should at least provide a hook for other values and a 
statement that unknown values are to be ignored.

That section also said that a=type:broadcast changes the *default* media 
direction to "recvonly" rather than "sendrecv". Again this used 
non-normative language. And "recvonly" in the SDP wouldn't be the right 
thing in an offer/answer context.

I reworded this to say that various values of a=type ought to be 
accompanied by some other option settings without saying that those 
somehow become default.

I'd especially like to have feedback on the revisions to this section.

The other changes are rather extensive. So I would very much like 
careful review of these changes.

	Thanks,
	Paul


-------- Forwarded Message --------
Subject: New Version Notification for draft-ietf-mmusic-rfc4566bis-36.txt
Resent-From: pkyzivat@alum.mit.edu
Date: Tue, 18 Jun 2019 10:14:30 -0700
From: internet-drafts@ietf.org
To: mmusic-chairs@ietf.org, Mark Handley <m.handley@cs.ucl.ac.uk>, Ali 
Begen <ali.begen@networked.media>, Colin Perkins <csp@csperkins.org>, 
Mark Handley <M.Handley@cs.ucl.ac.uk>, Paul Kyzivat <pkyzivat@alum.mit.edu>


A new version of I-D, draft-ietf-mmusic-rfc4566bis-36.txt
has been successfully submitted by Paul Kyzivat and posted to the
IETF repository.

Name:		draft-ietf-mmusic-rfc4566bis
Revision:	36
Title:		SDP: Session Description Protocol
Document date:	2019-06-18
Group:		mmusic
Pages:		62
URL: 
https://www.ietf.org/internet-drafts/draft-ietf-mmusic-rfc4566bis-36.txt
Status: 
https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc4566bis/
Htmlized:       https://tools.ietf.org/html/draft-ietf-mmusic-rfc4566bis-36
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-rfc4566bis
Diff: 
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-rfc4566bis-36

Abstract:
    This memo defines the Session Description Protocol (SDP).  SDP is
    intended for describing multimedia sessions for the purposes of
    session announcement, session invitation, and other forms of
    multimedia session initiation.  This document obsoletes RFC 4566.

 


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat



From nobody Wed Jun 19 02:12:03 2019
Return-Path: <rdd@cert.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93E86120391; Wed, 19 Jun 2019 02:12:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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 (1024-bit key) header.d=cert.org
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 c6iYrL6nSssi; Wed, 19 Jun 2019 02:11:59 -0700 (PDT)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (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 13C48120448; Wed, 19 Jun 2019 02:11:58 -0700 (PDT)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x5J9BuNd037213; Wed, 19 Jun 2019 05:11:56 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu x5J9BuNd037213
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1560935516; bh=pm+RTxZDvbGD66uYooa9WzUz8CaPx1wdBc3Q70k0vms=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=gEvritq7CmqAiGciVWt5YpLUYLDXkE+E+qNc5cKXSoYePGmv1YiXW98Q7gw2Bnwdc YWrc5/Myy1cZDkTBHG3dYSBcMZsYrMVVh4/V00SppiAZfTUq1TMgfPwzB5ClzEpTRB 7OTBrH9JFwlrJ5QbIK2ez0LFJhFXeqx/5Ayf3ffQ=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x5J9BrLH029190; Wed, 19 Jun 2019 05:11:53 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0439.000; Wed, 19 Jun 2019 05:11:53 -0400
From: Roman Danyliw <rdd@cert.org>
To: "fandreas@cisco.com" <fandreas@cisco.com>, "draft-ietf-mmusic-rfc4566bis@ietf.org" <draft-ietf-mmusic-rfc4566bis@ietf.org>
CC: "mmusic@ietf.org" <mmusic@ietf.org>, Roman Danyliw <rdd@cert.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, The IESG <iesg@ietf.org>
Thread-Topic: Roman Danyliw's Discuss on draft-ietf-mmusic-rfc4566bis-35: (with DISCUSS and COMMENT)
Thread-Index: AQHVFkzPf0v/Ozidc0iyJw+gdT2jvaaizgFg
Date: Wed, 19 Jun 2019 09:11:52 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B339B6C0@marathon>
References: <155915471104.5543.17843194441283384643.idtracker@ietfa.amsl.com>
In-Reply-To: <155915471104.5543.17843194441283384643.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/SsVg5Sg8Vp3lipwPrBcgue0C3vc>
Subject: Re: [MMUSIC] Roman Danyliw's Discuss on draft-ietf-mmusic-rfc4566bis-35: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2019 09:12:02 -0000

SGkhDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaWVzZyBbbWFpbHRv
Omllc2ctYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFJvbWFuIERhbnlsaXcgdmlhDQo+
IERhdGF0cmFja2VyDQo+IFNlbnQ6IFdlZG5lc2RheSwgTWF5IDI5LCAyMDE5IDI6MzIgUE0NCj4g
VG86IFRoZSBJRVNHIDxpZXNnQGlldGYub3JnPg0KPiBDYzogZmFuZHJlYXNAY2lzY28uY29tOyBt
bXVzaWMtY2hhaXJzQGlldGYub3JnOyBkcmFmdC1pZXRmLW1tdXNpYy0NCj4gcmZjNDU2NmJpc0Bp
ZXRmLm9yZzsgbW11c2ljQGlldGYub3JnDQo+IFN1YmplY3Q6IFJvbWFuIERhbnlsaXcncyBEaXNj
dXNzIG9uIGRyYWZ0LWlldGYtbW11c2ljLXJmYzQ1NjZiaXMtMzU6ICh3aXRoDQo+IERJU0NVU1Mg
YW5kIENPTU1FTlQpDQo+IA0KPiBSb21hbiBEYW55bGl3IGhhcyBlbnRlcmVkIHRoZSBmb2xsb3dp
bmcgYmFsbG90IHBvc2l0aW9uIGZvcg0KPiBkcmFmdC1pZXRmLW1tdXNpYy1yZmM0NTY2YmlzLTM1
OiBEaXNjdXNzDQo+IA0KPiBXaGVuIHJlc3BvbmRpbmcsIHBsZWFzZSBrZWVwIHRoZSBzdWJqZWN0
IGxpbmUgaW50YWN0IGFuZCByZXBseSB0byBhbGwgZW1haWwNCj4gYWRkcmVzc2VzIGluY2x1ZGVk
IGluIHRoZSBUbyBhbmQgQ0MgbGluZXMuIChGZWVsIGZyZWUgdG8gY3V0IHRoaXMgaW50cm9kdWN0
b3J5DQo+IHBhcmFncmFwaCwgaG93ZXZlci4pDQo+IA0KPiANCj4gUGxlYXNlIHJlZmVyIHRvIGh0
dHBzOi8vd3d3LmlldGYub3JnL2llc2cvc3RhdGVtZW50L2Rpc2N1c3MtY3JpdGVyaWEuaHRtbA0K
PiBmb3IgbW9yZSBpbmZvcm1hdGlvbiBhYm91dCBJRVNHIERJU0NVU1MgYW5kIENPTU1FTlQgcG9z
aXRpb25zLg0KPiANCj4gDQo+IFRoZSBkb2N1bWVudCwgYWxvbmcgd2l0aCBvdGhlciBiYWxsb3Qg
cG9zaXRpb25zLCBjYW4gYmUgZm91bmQgaGVyZToNCj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRm
Lm9yZy9kb2MvZHJhZnQtaWV0Zi1tbXVzaWMtcmZjNDU2NmJpcy8NCj4gDQo+IA0KPiANCj4gLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KPiBESVNDVVNTOg0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IA0KPiBJ4oCZZCBsaWtl
IHRvIGVzY2FsYXRlIEFsaXNzYeKAmXMgcG9pbnQgYWJvdXQgdGhlIGs9IGxhbmd1YWdlIGluIFNl
Y3Rpb24gNyAoU2VjdXJpdHkNCj4gQ29uc2lkZXJhdGlvbnMpLiAgSXQgbG9va3MgbGlrZSB0aGUg
bmV3IFNlY3Rpb24gNS4xMiByZW1vdmVzIGFsbCBvZiB0aGUNCj4gaGlzdG9yaWNhbCBsYW5ndWFn
ZSBiZXlvbmQgc2F5aW5nIGl0IE1VU1QgTk9UIGJlIHVzZWQuICBUaGlzIGFwcHJvYWNoDQo+IG1h
a2VzIHNlbnNlIHRvIG1lLiAgSG93ZXZlciwgdGhlIGxhbmd1YWdlIGluIFNlY3Rpb24gNyBjb3Vs
ZCBiZSByZWFkIGFzDQo+IGNvbmZsaWN0aW5nIHdpdGggdGhhdC4gIFNwZWNpZmljYWxseToNCj4g
DQo+ICAgIFVzZSBvZiB0aGUgIms9IiBsaW5lIHBvc2VzIGEgc2lnbmlmaWNhbnQgc2VjdXJpdHkg
cmlzaywgc2luY2UgaXQNCj4gICAgY29udmV5cyBzZXNzaW9uIGVuY3J5cHRpb24ga2V5cyBpbiB0
aGUgY2xlYXIuICBTRFAgTVVTVCBOT1QgYmUgdXNlZA0KPiAgICB0byBjb252ZXkga2V5aW5nIG1h
dGVyaWFsLCB1bmxlc3MgaXQgY2FuIGJlIGd1YXJhbnRlZWQgdGhhdCB0aGUNCj4gICAgY2hhbm5l
bCBvdmVyIHdoaWNoIHRoZSBTRFAgaXMgZGVsaXZlcmVkIGlzIGJvdGggcHJpdmF0ZSBhbmQNCj4g
ICAgYXV0aGVudGljYXRlZC4NCj4gICAgLi4uDQo+ICAgIFRoZSAiaz0iIGxpbmUgTVVTVA0KPiAg
ICBOT1QgYmUgdXNlZCwgYXMgZGlzY3Vzc2VkIGluIFNlY3Rpb24gNS4xMi4NCj4gDQo+IFRoZSBm
aXJzdCBzZW50ZW5jZSBtYWtlcyBhIHN0cm9uZyBzdGF0ZW1lbnQuICBUaGUgZmlyc3QgY2xhdXNl
IG9mIHRoZSBzZWNvbmQNCj4gc2VudGVuY2UgbWFrZXMgYSBtb3JlIGdlbmVyaWMgTVVTVCBOT1Qg
c3RhdGVtZW50IGJ1dCB0aGUgc2Vjb25kIGNsYXVzZQ0KPiBzZWVtcyB0byBzYXkgdGhhdCBpcyBh
Y2NlcHRhYmxlIHVuZGVyIGNlcnRhaW4gY2lyY3Vtc3RhbmNlcy4gIFRoZSB0aGlyZA0KPiBzZW50
ZW5jZSByZWl0ZXJhdGVzIHRoYXQgaz0gTVVTVCBOT1QgYmUgdXNlZC4gIEhvdyBzaG91bGQgdGhp
cyBiZQ0KPiByZWNvbmNpbGVkPyAgSXMgdGhlIHRleHQgc3VnZ2VzdGluZyB0aGF0IGNvbnZleWlu
ZyBrZXlpbmcgbWF0ZXJpYWxzIG91dHNpZGUgb2YNCj4gaz0gaXMgYWNjZXB0YWJsZSBvdmVyIHRo
ZSByaWdodCBraW5kIG9mIGNoYW5uZWw/DQoNClRoYW5rcyBmb3IgdGhlIHJldmlzaW9uIHRvIFNl
Y3Rpb24gNyB0byBjbGFyaWZ5IHRoZSBsYW5ndWFnZSB3aXRoaW4gdGhlIHNlY3Rpb24uICBJIHN0
aWxsIHNlZSBhIGNvbmZsaWN0IGJldHdlZW4gdGhlIGd1aWRhbmNlIGluIFNlY3Rpb24gNS4xMiBh
bmQgNy4NCg0KU2VjdGlvbiA1LjEyIHNheXM6DQogICBUaGUgIms9IiBsaW5lIChrZXktZmllbGQp
IGlzIG9ic29sZXRlIGFuZCBNVVNUIE5PVCBiZSB1c2VkLiAgSXQgaXMNCiAgIGluY2x1ZGVkIGlu
IHRoaXMgZG9jdW1lbnQgZm9yIGxlZ2FjeSByZWFzb25zLiAgT25lIE1VU1QgTk9UIGluY2x1ZGUg
YQ0KICAgIms9IiBsaW5lIGluIGFuIFNEUCwgYW5kIE1VU1QgZGlzY2FyZCBpdCBpZiBpdCBpcyBy
ZWNlaXZlZCBpbiBhbiBTRFAuDQoNClRoZSBuZXcgdGV4dCBpbiBTZWN0aW9uIDcgc2F5czoNCiAg
IFNEUCBNVVNUIE5PVCBiZSB1c2VkIHRvIGNvbnZleSBrZXlpbmcgbWF0ZXJpYWwgKGUuZy4sIHVz
aW5nDQogICAiYT1jcnlwdG8iIFtSRkM0NTY4XSkgdW5sZXNzIGl0IGNhbiBiZSBndWFyYW50ZWVk
IHRoYXQgdGhlIGNoYW5uZWwNCiAgIG92ZXIgd2hpY2ggdGhlIFNEUCBpcyBkZWxpdmVyZWQgaXMg
Ym90aCBwcml2YXRlIGFuZCBhdXRoZW50aWNhdGVkLiANCg0KTXkgcmVhZCBpcyB0aGF0IFNlY3Rp
b24gNS4xMiBzYXlzIGRvbid0IHVzZSBrPSBhbmQgZHJvcCBpdCBpZiB5b3Ugc2VlIGl0OyBhbmQg
U2VjdGlvbiA3IHNheXMgZG9uJ3QgdXNlIGs9IHVubGVzcyB5b3UgY2FuIGd1YXJhbnRlZSBjZXJ0
YWluIGNoYW5uZWwgcHJvcGVydGllcy4gIENvbnNpZGVyIHRoZSBzaXR1YXRpb24gd2hlcmUgb25l
IGhhcyB0aGUgcmlnaHQgY2hhbm5lbCBwcm9wZXJ0aWVzIChwZXIgU2VjdGlvbiA3KSwgd2h5IHdv
dWxkIG9uZSB1c2Ugaz0gc2luY2UgU2VjdGlvbiA1LjEyIHdvdWxkIGRpY3RhdGUgdGhhdCB0aGlz
IGs9IHdvdWxkIGdldCBkcm9wcGVkPw0KDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gQ09NTUVOVDoNCj4g
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KPiANCj4gKDEpIFBlciB0aGUgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMg
KFNlY3Rpb24gNykgcGFyYWdyYXBoIG9uIOKAnHNvZnR3YXJlDQo+IHBhcnNpbmcgdGhlIHNlc3Np
b24gc2hvdWxkIHRha2UgYSBmZXcgcHJlY2F1dGlvbnPigJ0sIHRoZSBkaXNjdXNzaW9uIGFib3V0
DQo+IHNvZnR3YXJlIHRha2luZyBhY3Rpb24gaXMgaGVscGZ1bC4gIEnigJlkIGFsc28gcmVjb21t
ZW5kIGV4cGxpY2l0bHkgYWRkaW5nDQo+IGNhdXRpb24gYWJvdXQgYWN0aW5nIG9uIFVSSXMgKGUu
Zy4sIHRoZSBzZWN1cml0eSBjb25zaWRlcmF0aW9ucyBvZiBbUkZDMzk4Nl0pDQo+IHRvIHRoaXMg
c2VjdGlvbi4NCj4gDQo+ICgyKSBTZWN0aW9uIDYuNy4gIFR5cG8uIHMvb2NjdXJlbmNlL29jY3Vy
cmVuY2UvDQoNClRoYW5rcyBmb3IgdGhlIG5ldyB0ZXh0IGluIC0zNiB0byBhZGRyZXNzIHRoaXMg
ZmVlZGJhY2suDQoNClJlZ2FyZHMsDQpSb21hbg0K


From nobody Wed Jun 19 07:45:55 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3114C1205FD; Wed, 19 Jun 2019 07:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id puC2YsAZEu9Y; Wed, 19 Jun 2019 07:45:44 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BEC41205DC; Wed, 19 Jun 2019 07:45:41 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x5JEjZwT025700 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 19 Jun 2019 10:45:35 -0400
To: Roman Danyliw <rdd@cert.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "draft-ietf-mmusic-rfc4566bis@ietf.org" <draft-ietf-mmusic-rfc4566bis@ietf.org>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, The IESG <iesg@ietf.org>
References: <155915471104.5543.17843194441283384643.idtracker@ietfa.amsl.com> <359EC4B99E040048A7131E0F4E113AFC01B339B6C0@marathon>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <9fc12825-f961-4cf3-1e2f-e328b90cebbb@alum.mit.edu>
Date: Wed, 19 Jun 2019 10:45:34 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFC01B339B6C0@marathon>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wkXbea_mpLX1jRyFZ3ApIqRVSvY>
Subject: Re: [MMUSIC] Roman Danyliw's Discuss on draft-ietf-mmusic-rfc4566bis-35: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2019 14:45:46 -0000

Roman,

On 6/19/19 5:11 AM, Roman Danyliw wrote:

> Thanks for the revision to Section 7 to clarify the language within the section.  I still see a conflict between the guidance in Section 5.12 and 7.
> 
> Section 5.12 says:
>     The "k=" line (key-field) is obsolete and MUST NOT be used.  It is
>     included in this document for legacy reasons.  One MUST NOT include a
>     "k=" line in an SDP, and MUST discard it if it is received in an SDP.
> 
> The new text in Section 7 says:
>     SDP MUST NOT be used to convey keying material (e.g., using
>     "a=crypto" [RFC4568]) unless it can be guaranteed that the channel
>     over which the SDP is delivered is both private and authenticated.
> 
> My read is that Section 5.12 says don't use k= and drop it if you see it; and Section 7 says don't use k= unless you can guarantee certain channel properties.  Consider the situation where one has the right channel properties (per Section 7), why would one use k= since Section 5.12 would dictate that this k= would get dropped?

The new section 7 uses a=crypto, which is a different mechanism from k=. 
So I don't see the conflict you are concerned with.

	Thanks,
	Paul


From nobody Wed Jun 19 07:54:41 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C37CA120679; Wed, 19 Jun 2019 07:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yPzUjgfIUt3i; Wed, 19 Jun 2019 07:54:38 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C666412061D; Wed, 19 Jun 2019 07:54:37 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x5JEsUPX026269 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 19 Jun 2019 10:54:30 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: Roman Danyliw <rdd@cert.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "draft-ietf-mmusic-rfc4566bis@ietf.org" <draft-ietf-mmusic-rfc4566bis@ietf.org>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, The IESG <iesg@ietf.org>
References: <155915471104.5543.17843194441283384643.idtracker@ietfa.amsl.com> <359EC4B99E040048A7131E0F4E113AFC01B339B6C0@marathon>
Message-ID: <f96b37a1-06d8-bd78-61a2-eb79cc35d4eb@alum.mit.edu>
Date: Wed, 19 Jun 2019 10:54:30 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFC01B339B6C0@marathon>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/LdToWh98tOpSayJqL_Rl8i85-X0>
Subject: Re: [MMUSIC] Roman Danyliw's Discuss on draft-ietf-mmusic-rfc4566bis-35: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2019 14:54:40 -0000

Roman,

[Adding more info]

On 6/19/19 5:11 AM, Roman Danyliw wrote:

> Thanks for the revision to Section 7 to clarify the language within the section.  I still see a conflict between the guidance in Section 5.12 and 7.
> 
> Section 5.12 says:
>     The "k=" line (key-field) is obsolete and MUST NOT be used.  It is
>     included in this document for legacy reasons.  One MUST NOT include a
>     "k=" line in an SDP, and MUST discard it if it is received in an SDP.
> 
> The new text in Section 7 says:
>     SDP MUST NOT be used to convey keying material (e.g., using
>     "a=crypto" [RFC4568]) unless it can be guaranteed that the channel
>     over which the SDP is delivered is both private and authenticated.
> 
> My read is that Section 5.12 says don't use k= and drop it if you see it; and Section 7 says don't use k= unless you can guarantee certain channel properties.  Consider the situation where one has the right channel properties (per Section 7), why would one use k= since Section 5.12 would dictate that this k= would get dropped?

The new section 7 uses a=crypto [RFC4568], which is a different 
mechanism from k=. So I don't see the conflict you are concerned with.

	Thanks,
	Paul


From nobody Wed Jun 19 07:55:10 2019
Return-Path: <rdd@cert.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 065D412061D; Wed, 19 Jun 2019 07:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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 (1024-bit key) header.d=cert.org
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 cHwGWw14GprC; Wed, 19 Jun 2019 07:55:00 -0700 (PDT)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (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 DA419120664; Wed, 19 Jun 2019 07:54:59 -0700 (PDT)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x5JEstoQ003770; Wed, 19 Jun 2019 10:54:55 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu x5JEstoQ003770
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1560956095; bh=6dsqh7bGQEkUcJKfhZPi6HSwPLUTQwC/5/8AFLYFeAw=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=ZCjhgNAWjI5T+ox/v4uCs168Qn/+QFc86Ok7CYi5tRE3h6OtxbUrZFUWq/KNaKvcX 8bCoykxut6VESIbBdPFopG4M0KITM5eeTqc9BToj5Zapvaiq1RKUak5r0u+R1BlOvW SaJlgqbKia0VoSj85UmqjMARVY9aSBMiwMPXy7QE=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x5JEsstm014004; Wed, 19 Jun 2019 10:54:54 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0439.000; Wed, 19 Jun 2019 10:54:53 -0400
From: Roman Danyliw <rdd@cert.org>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "fandreas@cisco.com" <fandreas@cisco.com>, "draft-ietf-mmusic-rfc4566bis@ietf.org" <draft-ietf-mmusic-rfc4566bis@ietf.org>
CC: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, The IESG <iesg@ietf.org>
Thread-Topic: Roman Danyliw's Discuss on draft-ietf-mmusic-rfc4566bis-35: (with DISCUSS and COMMENT)
Thread-Index: AQHVFkzPf0v/Ozidc0iyJw+gdT2jvaaizgFggACjwAD//73RwA==
Date: Wed, 19 Jun 2019 14:54:52 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B339C1F0@marathon>
References: <155915471104.5543.17843194441283384643.idtracker@ietfa.amsl.com> <359EC4B99E040048A7131E0F4E113AFC01B339B6C0@marathon> <9fc12825-f961-4cf3-1e2f-e328b90cebbb@alum.mit.edu>
In-Reply-To: <9fc12825-f961-4cf3-1e2f-e328b90cebbb@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/8phpT1ozg-oXeaN_uJuFDwu0owU>
Subject: Re: [MMUSIC] Roman Danyliw's Discuss on draft-ietf-mmusic-rfc4566bis-35: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2019 14:55:02 -0000

SGkgUGF1bCENCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpZXNnIFtt
YWlsdG86aWVzZy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgUGF1bCBLeXppdmF0DQo+
IFNlbnQ6IFdlZG5lc2RheSwgSnVuZSAxOSwgMjAxOSAxMDo0NiBBTQ0KPiBUbzogUm9tYW4gRGFu
eWxpdyA8cmRkQGNlcnQub3JnPjsgZmFuZHJlYXNAY2lzY28uY29tOyBkcmFmdC1pZXRmLW1tdXNp
Yy0NCj4gcmZjNDU2NmJpc0BpZXRmLm9yZw0KPiBDYzogbW11c2ljLWNoYWlyc0BpZXRmLm9yZzsg
bW11c2ljQGlldGYub3JnOyBUaGUgSUVTRyA8aWVzZ0BpZXRmLm9yZz4NCj4gU3ViamVjdDogUmU6
IFJvbWFuIERhbnlsaXcncyBEaXNjdXNzIG9uIGRyYWZ0LWlldGYtbW11c2ljLXJmYzQ1NjZiaXMt
MzU6DQo+ICh3aXRoIERJU0NVU1MgYW5kIENPTU1FTlQpDQo+IA0KPiBSb21hbiwNCj4gDQo+IE9u
IDYvMTkvMTkgNToxMSBBTSwgUm9tYW4gRGFueWxpdyB3cm90ZToNCj4gDQo+ID4gVGhhbmtzIGZv
ciB0aGUgcmV2aXNpb24gdG8gU2VjdGlvbiA3IHRvIGNsYXJpZnkgdGhlIGxhbmd1YWdlIHdpdGhp
biB0aGUNCj4gc2VjdGlvbi4gIEkgc3RpbGwgc2VlIGEgY29uZmxpY3QgYmV0d2VlbiB0aGUgZ3Vp
ZGFuY2UgaW4gU2VjdGlvbiA1LjEyIGFuZCA3Lg0KPiA+DQo+ID4gU2VjdGlvbiA1LjEyIHNheXM6
DQo+ID4gICAgIFRoZSAiaz0iIGxpbmUgKGtleS1maWVsZCkgaXMgb2Jzb2xldGUgYW5kIE1VU1Qg
Tk9UIGJlIHVzZWQuICBJdCBpcw0KPiA+ICAgICBpbmNsdWRlZCBpbiB0aGlzIGRvY3VtZW50IGZv
ciBsZWdhY3kgcmVhc29ucy4gIE9uZSBNVVNUIE5PVCBpbmNsdWRlIGENCj4gPiAgICAgIms9IiBs
aW5lIGluIGFuIFNEUCwgYW5kIE1VU1QgZGlzY2FyZCBpdCBpZiBpdCBpcyByZWNlaXZlZCBpbiBh
biBTRFAuDQo+ID4NCj4gPiBUaGUgbmV3IHRleHQgaW4gU2VjdGlvbiA3IHNheXM6DQo+ID4gICAg
IFNEUCBNVVNUIE5PVCBiZSB1c2VkIHRvIGNvbnZleSBrZXlpbmcgbWF0ZXJpYWwgKGUuZy4sIHVz
aW5nDQo+ID4gICAgICJhPWNyeXB0byIgW1JGQzQ1NjhdKSB1bmxlc3MgaXQgY2FuIGJlIGd1YXJh
bnRlZWQgdGhhdCB0aGUgY2hhbm5lbA0KPiA+ICAgICBvdmVyIHdoaWNoIHRoZSBTRFAgaXMgZGVs
aXZlcmVkIGlzIGJvdGggcHJpdmF0ZSBhbmQgYXV0aGVudGljYXRlZC4NCj4gPg0KPiA+IE15IHJl
YWQgaXMgdGhhdCBTZWN0aW9uIDUuMTIgc2F5cyBkb24ndCB1c2Ugaz0gYW5kIGRyb3AgaXQgaWYg
eW91IHNlZSBpdDsgYW5kDQo+IFNlY3Rpb24gNyBzYXlzIGRvbid0IHVzZSBrPSB1bmxlc3MgeW91
IGNhbiBndWFyYW50ZWUgY2VydGFpbiBjaGFubmVsDQo+IHByb3BlcnRpZXMuICBDb25zaWRlciB0
aGUgc2l0dWF0aW9uIHdoZXJlIG9uZSBoYXMgdGhlIHJpZ2h0IGNoYW5uZWwNCj4gcHJvcGVydGll
cyAocGVyIFNlY3Rpb24gNyksIHdoeSB3b3VsZCBvbmUgdXNlIGs9IHNpbmNlIFNlY3Rpb24gNS4x
MiB3b3VsZA0KPiBkaWN0YXRlIHRoYXQgdGhpcyBrPSB3b3VsZCBnZXQgZHJvcHBlZD8NCj4gDQo+
IFRoZSBuZXcgc2VjdGlvbiA3IHVzZXMgYT1jcnlwdG8sIHdoaWNoIGlzIGEgZGlmZmVyZW50IG1l
Y2hhbmlzbSBmcm9tIGs9Lg0KPiBTbyBJIGRvbid0IHNlZSB0aGUgY29uZmxpY3QgeW91IGFyZSBj
b25jZXJuZWQgd2l0aC4NCg0KWW91J3JlIHJpZ2h0LiAgVGhlIHRleHQgd2FzIGNsZWFyLCBidXQg
SSBjb25mbGF0ZWQgdGhlIHR3byBzZWN0aW9ucyBpbiByZS1yZWFkaW5nIG15IGRpc2N1c3MgdGV4
dC4NCg0KVGhhbmtzIGZvciB0aGUgdXBkYXRlZCB0ZXh0LiAgSSd2ZSBjbGVhcmVkIHRoZSBkaXNj
dXNzLg0KDQpSb21hbg0K

