
From nobody Fri Feb  1 09:09:21 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 A39C213106A for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 09:09:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.03
X-Spam-Level: 
X-Spam-Status: No, score=-2.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 UBgditIriV16 for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 09:09:17 -0800 (PST)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (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 637E3130934 for <mmusic@ietf.org>; Fri,  1 Feb 2019 09:09:17 -0800 (PST)
Received: by mail-pf1-x430.google.com with SMTP id w73so3496690pfk.10 for <mmusic@ietf.org>; Fri, 01 Feb 2019 09:09:17 -0800 (PST)
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=YZ0oKaTF9P548qmCWeUeJGbKicw6Jis3S2Z9XYykzzo=; b=0DzLiuCIz9fPI6qJJjKsdsWeSBflPGpn61msvwtHNaxyMSvQAx8Te9gnm0Nm6Tc9vq ADr2qBubBLptPryv2uCGZF7MmIyihZQmIG9Msie1jQ63X3qimuqzDvFAKo8h+jizZPSe Aqu6dyAnhV/JV2pKCxXLL+xFZAPeLTolssWbWuyiSb0I2cbKcbfPA1ot85K6slTfs5JW PSC8HhIrWFnMzmD5/bFTYekMxWPjRoYzeJNZV4YojhDClHTDU8k9h5RsEUd46EdWdJmg r1SjejlVTTTTrRaLlxNCSWHqEeB+H0sZuGuKhQm8CPh6esL6tpZ0Eku7J4CRLbmf6NF9 iNrg==
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=YZ0oKaTF9P548qmCWeUeJGbKicw6Jis3S2Z9XYykzzo=; b=h1HaJLrnRsoAc1qghqqA/w1/sjnmq7rU4/Qw1orMYiw8p6FStV3MpKwXWhcZn3PN5j wNlEeB3fU25K0EBPy33RrQuDlyJTJqgEIkEMRzJw6VFGlEJV1/qrZB3eMnE3qfGSGUh8 PpxD/OCjTZLqNKZW73GYQA4EakpBYyFEsEJ5CNskseD1TrqcSpxcrJCGzi63KdseAnUD XNn0PggyRpu8zQuP2hLAFHrOKTtrBiovlJE1nCl/hnJPYIyOiooNJJvRawSVbbfceygG L5SPMDlY7kyaGkIvTLTQFkqmhSnTe81TuqIpnRlQrmzLXR+7iAzPCBGkBrmrioMJ0jYe p/tw==
X-Gm-Message-State: AHQUAubXzCi7/oiKbYLjCIHihcQYgKeDerZ6+72/m6SWNS3EIXWXNiZX 7vqLOjyT0ddPLkTZKFkCcwhJkg==
X-Google-Smtp-Source: AHgI3IYnpr/16IPQ6yLvI8QizZbJOS/pFfhVzvmppIxKl/gWNCnhyYzADHnZNmceB4PuAl62fVb6Tw==
X-Received: by 2002:a63:9749:: with SMTP id d9mr2900925pgo.415.1549040956754;  Fri, 01 Feb 2019 09:09:16 -0800 (PST)
Received: from mail-pf1-f177.google.com (mail-pf1-f177.google.com. [209.85.210.177]) by smtp.gmail.com with ESMTPSA id u12sm3434123pgo.52.2019.02.01.09.09.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Feb 2019 09:09:15 -0800 (PST)
Received: by mail-pf1-f177.google.com with SMTP id g62so3488988pfd.12; Fri, 01 Feb 2019 09:09:15 -0800 (PST)
X-Received: by 2002:a63:b4c:: with SMTP id a12mr3064102pgl.131.1549040955470;  Fri, 01 Feb 2019 09:09:15 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com>
In-Reply-To: <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 1 Feb 2019 12:09:05 -0500
X-Gmail-Original-Message-ID: <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com>
Message-ID: <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>, Simon Perreault <sperreault@jive.com>
Content-Type: multipart/alternative; boundary="000000000000e4b8c00580d833f5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/y__DNhx3tUKcVdquXcYSTK8CRs4>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 01 Feb 2019 17:09:20 -0000

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

Hi Justin,

I agree regarding #1 in theory, even though in practice a lot of (most)
devices will not accept FQDN in either c= or ICE candidate.

Regarding #2, mmusic-ice-sip-sdp was updated (
https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-24#section-4.1):

   <connection-address>:  is taken from RFC 4566
<https://tools.ietf.org/html/rfc4566> [RFC4566
<https://tools.ietf.org/html/rfc4566>].  It is the
      IP address of the candidate.  When parsing this field, an agent
      can differentiate an IPv4 address and an IPv6 address by presence
      of a colon in its value -- the presence of a colon indicates IPv6.
      An agent MUST ignore candidate lines that include candidates with
      IP address versions that are not supported or recognized.


Specifically, support for FQDN names there was removed due to RFC 8445
implementation issues. I believe Simon Perreault suggested this change.

Regards,
_____________
Roman Shpount


On Fri, Feb 1, 2019 at 12:02 AM Justin Uberti <juberti@google.com> wrote:

> My recommendation here would be that we do c=IN IP6
> 3557773f-5f01-46a4-aa14-54ab35b3d778.local, with either IP4 or IP6
> depending on which type of address is being wrapped.
>
> Re #1: RFC 4566 seems to indicate you can use either IP4 or IP6 for FQDN
> in the c= line.
>
>      unicast-address =     IP4-address / IP6-address / FQDN / extn-addr
>
>
> Re #2: Quoth 5245 <https://tools.ietf.org/html/rfc5245#section-15.1>:
>
>    <connection-address>:  is taken from RFC 4566 <https://tools.ietf.org/html/rfc4566> [RFC4566 <https://tools.ietf.org/html/rfc4566>].  It is the
>       IP address of the candidate, allowing for IPv4 addresses, IPv6
>       addresses, and *fully qualified domain names (FQDNs).*  When parsing
>       this field, an agent can differentiate an IPv4 address and an IPv6
>
>       address by presence of a colon in its value - the presence of a
>       colon indicates IPv6.  An agent MUST ignore candidate lines that
>       include candidates with IP address versions that are not supported
>       or recognized.  An IP address SHOULD be used, but an FQDN MAY be
>       used in place of an IP address.  In that case, when receiving an
>       offer or answer containing an FQDN in an a=candidate attribute,
>       the FQDN is looked up in the DNS first using an AAAA record
>       (assuming the agent supports IPv6), and if no result is found or
>       the agent only supports IPv4, using an A.  If the DNS query
>       returns more than one IP address, one is chosen, and then used for
>       the remainder of ICE processing.
>
>
>
>
>
>
>
>
>
> On Thu, Jan 31, 2019 at 8:43 PM Roman Shpount <roman@telurix.com> wrote:
>
>> On Thu, Jan 31, 2019 at 10:58 PM Justin Uberti <juberti@google.com>
>> wrote:
>>
>>> We can however all agree that "c=IN IP6" is busted:
>>> https://bugs.chromium.org/p/chromium/issues/detail?id=927309
>>>
>>>>
>>>>>
>> I guess one way to interpret this that each address should have a MDNS
>> alias. So, if you are dealing with dual stack host, it should provide two
>> MDNS candidates, one of which is IPv4 and another IPv6. The c= line should
>> specify FQDN for one of those candidates and specify the type (IP4 or IP6).
>>
>> There are two problems:
>>
>> 1. There is no way to know which address type is in the candidate-address
>> when FQDN is used there. Guidance in ice-sip-sdp is talking about the
>> presence of column in IP6 address, but this definitely does not apply to
>> FQDN. It would've been better to specify something like local4 and local6
>> as FQDN suffix in MDNS alias to specify the candidate-address type so that
>> correct DNS request can be issued.
>>
>> 2. A lot (if not most) SDP/ICE implementations do no support parsing FQDN
>> in candidate-address or c= line. This might create interop problems since
>> RFC 5245 specified that candidate-address is an IP Address.
>>
>> Regards,
>> _____________
>> Roman Shpount
>>
>>
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Hi Justin,<div><br></div=
><div>I agree regarding #1 in theory, even though in practice a lot of (mos=
t) devices will not accept FQDN in either c=3D or ICE candidate.</div><div>=
<br></div><div>Regarding #2, mmusic-ice-sip-sdp was updated (<a href=3D"htt=
ps://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-24#section-4.1">http=
s://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-24#section-4.1</a>):<=
/div><div><br></div><div><pre class=3D"gmail-newpage" style=3D"font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)=
">   &lt;connection-address&gt;:  is taken from <a href=3D"https://tools.ie=
tf.org/html/rfc4566">RFC 4566</a> [<a href=3D"https://tools.ietf.org/html/r=
fc4566" title=3D"&quot;SDP: Session Description Protocol&quot;">RFC4566</a>=
].  It is the
      IP address of the candidate.  When parsing this field, an agent
      can differentiate an IPv4 address and an IPv6 address by presence
      of a colon in its value -- the presence of a colon indicates IPv6.
      An agent MUST ignore candidate lines that include candidates with
      IP address versions that are not supported or recognized.</pre><pre c=
lass=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-b=
ottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre>Specifically, suppo=
rt for FQDN names there was removed due to=C2=A0<span style=3D"color:rgb(0,=
0,0)">RFC 8445 implementation issues. I believe=C2=A0</span><font color=3D"=
#000000">Simon Perreault suggested this change.</font></div><div><font colo=
r=3D"#000000"><br></font></div><div><font color=3D"#000000">Regards,<br></f=
ont><div><div dir=3D"ltr" class=3D"gmail_signature">_____________<br>Roman =
Shpount</div></div><br></div></div></div></div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 1, 2019 at 12:02 AM Ju=
stin Uberti &lt;<a href=3D"mailto:juberti@google.com">juberti@google.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"><di=
v dir=3D"ltr"><div dir=3D"ltr"><div>My recommendation here would be that we=
 do c=3DIN IP6 3557773f-5f01-46a4-aa14-54ab35b3d778.local, with either IP4 =
or IP6 depending on which type of address is being wrapped.</div><div><br><=
/div><div>Re #1:=C2=A0RFC 4566 seems to indicate you can use either IP4 or =
IP6 for FQDN in the c=3D line.</div><div><br></div><div><pre class=3D"gmail=
-m_7058075087377128197gmail-newpage" style=3D"font-size:13.3333px;margin-to=
p:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">     unicast-ad=
dress =3D     IP4-address / IP6-address / FQDN / extn-addr
</pre></div><div><br></div>Re #2: Quoth <a href=3D"https://tools.ietf.org/h=
tml/rfc5245#section-15.1" target=3D"_blank">5245</a>:<div><br></div><div><p=
re class=3D"gmail-m_7058075087377128197gmail-newpage" style=3D"font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)=
">   &lt;connection-address&gt;:  is taken from <a href=3D"https://tools.ie=
tf.org/html/rfc4566" target=3D"_blank">RFC 4566</a> [<a href=3D"https://too=
ls.ietf.org/html/rfc4566" title=3D"&quot;SDP: Session Description Protocol&=
quot;" target=3D"_blank">RFC4566</a>].  It is the
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and <b>fully qualified domain names (FQDNs).</b>  When par=
sing
      this field, an agent can differentiate an IPv4 address and an IPv6
</pre><pre class=3D"gmail-m_7058075087377128197gmail-newpage" style=3D"font=
-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rg=
b(0,0,0)">      address by presence of a colon in its value - the presence =
of a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=3Dcandidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.
</pre><pre class=3D"gmail-m_7058075087377128197gmail-newpage" style=3D"font=
-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rg=
b(0,0,0)"><br></pre><pre class=3D"gmail-m_7058075087377128197gmail-newpage"=
 style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before=
:page;color:rgb(0,0,0)"><br></pre><pre class=3D"gmail-m_7058075087377128197=
gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0p=
x;break-before:page;color:rgb(0,0,0)"><br></pre><pre class=3D"gmail-m_70580=
75087377128197gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;ma=
rgin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><pre class=3D=
"gmail-m_7058075087377128197gmail-newpage" style=3D"font-size:13.3333px;mar=
gin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre=
><pre class=3D"gmail-m_7058075087377128197gmail-newpage" style=3D"font-size=
:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0=
,0)"><br></pre><br class=3D"gmail-m_7058075087377128197gmail-Apple-intercha=
nge-newline"></div></div></div><br><div class=3D"gmail_quote"><div dir=3D"l=
tr" class=3D"gmail_attr">On Thu, Jan 31, 2019 at 8:43 PM Roman Shpount &lt;=
<a href=3D"mailto:roman@telurix.com" target=3D"_blank">roman@telurix.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"><di=
v dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div><div dir=3D"ltr" class=
=3D"gmail-m_7058075087377128197gmail-m_4773857553044000712gmail-m_836724976=
9720427912gmail_signature">On Thu, Jan 31, 2019 at 10:58 PM Justin Uberti &=
lt;<a href=3D"mailto:juberti@google.com" target=3D"_blank">juberti@google.c=
om</a>&gt; wrote:<br></div></div></div><div class=3D"gmail_quote"><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">=
<div dir=3D"ltr">We can however all agree that &quot;c=3DIN IP6&quot; is bu=
sted:=C2=A0<a href=3D"https://bugs.chromium.org/p/chromium/issues/detail?id=
=3D927309" target=3D"_blank">https://bugs.chromium.org/p/chromium/issues/de=
tail?id=3D927309</a></div></div></div><div class=3D"gmail_quote"><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><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"><br></blockquote></div></blockquo=
te></div></blockquote><div><br></div><div>I guess one way to interpret this=
 that each address should have a MDNS alias. So, if you are dealing with du=
al stack host, it should provide two MDNS candidates, one of which is IPv4 =
and another IPv6. The c=3D line should specify FQDN for one of those candid=
ates and specify the type (IP4 or IP6).</div><div><br></div><div>There are =
two problems:</div><div><br></div><div>1. There is no way to know which add=
ress type is in the candidate-address when FQDN is used there. Guidance in =
ice-sip-sdp is talking about the presence of column in IP6 address, but thi=
s definitely does not apply to FQDN. It would&#39;ve been better to specify=
 something like local4 and local6 as FQDN suffix in MDNS alias to specify t=
he candidate-address type so that correct DNS request can be issued.</div><=
div><br></div><div>2. A lot (if not most) SDP/ICE implementations do no sup=
port parsing FQDN in candidate-address or c=3D line. This might create inte=
rop problems since RFC 5245 specified that candidate-address is an IP Addre=
ss.</div><div><br></div><div>Regards,</div>_____________<br>Roman Shpount<b=
r class=3D"gmail-m_7058075087377128197gmail-m_4773857553044000712gmail-m_83=
67249769720427912gmail-Apple-interchange-newline"><div>=C2=A0</div></div></=
div></div>
</blockquote></div>
</blockquote></div>

--000000000000e4b8c00580d833f5--


From nobody Fri Feb  1 09:39:45 2019
Return-Path: <juberti@google.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 E642A131124 for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 09:39:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.641
X-Spam-Level: 
X-Spam-Status: No, score=-17.641 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 jgOu-l3BC86B for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 09:39:25 -0800 (PST)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (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 1B2FB131118 for <mmusic@ietf.org>; Fri,  1 Feb 2019 09:39:25 -0800 (PST)
Received: by mail-io1-xd36.google.com with SMTP id r200so6305560iod.11 for <mmusic@ietf.org>; Fri, 01 Feb 2019 09:39:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=X48I0BkcRT1I8Qu0jeHdHaGeGuNVVnUqpIZNQMcgDJs=; b=niM0nxrFZgHht9Icb/D9QJ34KwXqOrIaRBI5yBGirinFupgbSDOp7F1UVLquxia3hk 6+mu1VTVTRrmAYCM/Kd4MDOykh18sV6EOd+BRR89sWLy3y6hqzt8qus/n80uuAOdv4Q+ 3n6KPR6ApzKdSQZu6LYwqPwB5Omi28zBP2y363fGpA0yrGxM8rxUbEk91faU+pL9pIru PcQxKebdWabZ++KAaZumxKxFMO2ryV/wz2+7MWO2J7bg/P+M4IDN10k5TeP1QBgOJYNL ok/xcG3+f2/a16b3jYURPdPIZbC2P/gi2+A/D60LzZT0fdf1JztW0zjOYgUnx7UH5t8W XliA==
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=X48I0BkcRT1I8Qu0jeHdHaGeGuNVVnUqpIZNQMcgDJs=; b=GdR9wGVBjiZTwVhr9gV8bMS/+Y03y4kKROP/Z6wkCirm1NO9L5TJyYpL3w8DqBWt7I rEY/yE0yV4QfqNXKTgjHpBw2Fj7eoZSdsmsEYCzclrTgT7gSjTAxgPSpm6yBqygrLsBK ejLKcDw25Rtr43Ew6oLyFypaJJuxZ/xMK6Y6IuShuqqIvmaweJYo4YBmkfSCV8GrnE+q vcsIggRPm6AM7cG3AUtJmeyoILZhC9ZvM0+rxhVfTEa7NK74mvSzwFmJJVDv5glFFk6U ozxp1V2jp/U0kk6BwP1UDmxjGjtA/vHQh2MyzZ3nPJBNcPCLDvDBNPPCuIH8mDvcUOF9 aaFg==
X-Gm-Message-State: AHQUAuZimI6IyYwu0wBWCweM29W5kMAEOlyq82xiM09L4fqrnVsf/sPM RAWq8n5Zdx4oYH1ZrKy3buUBLnE+Ij6bGpyrYmqwsQ==
X-Google-Smtp-Source: ALg8bN6ZYpnX3AnKrPSBU+TuyWS4pf14JlHO7n5ZSVZKKvbUWxD9JUp6NIW5+5YSMjc5dSkZWCEudkukhtY9nseuKac=
X-Received: by 2002:a5d:898b:: with SMTP id m11mr22104275iol.181.1549042763859;  Fri, 01 Feb 2019 09:39:23 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com>
In-Reply-To: <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Fri, 1 Feb 2019 09:39:12 -0800
Message-ID: <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>, Simon Perreault <sperreault@jive.com>
Content-Type: multipart/alternative; boundary="000000000000af0cc80580d89f22"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wHB1WcQ7hO48l7XWdc3_S4KFfjU>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 01 Feb 2019 17:39:36 -0000

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

I understand there were questions about the general case (e.g. regular DNS
names), but how do we plan to reconcile this removal with the need for mDNS
hostnames?

On Fri, Feb 1, 2019 at 9:09 AM Roman Shpount <roman@telurix.com> wrote:

> Hi Justin,
>
> I agree regarding #1 in theory, even though in practice a lot of (most)
> devices will not accept FQDN in either c= or ICE candidate.
>
> Regarding #2, mmusic-ice-sip-sdp was updated (
> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-24#section-4.1):
>
>    <connection-address>:  is taken from RFC 4566 <https://tools.ietf.org/html/rfc4566> [RFC4566 <https://tools.ietf.org/html/rfc4566>].  It is the
>       IP address of the candidate.  When parsing this field, an agent
>       can differentiate an IPv4 address and an IPv6 address by presence
>       of a colon in its value -- the presence of a colon indicates IPv6.
>       An agent MUST ignore candidate lines that include candidates with
>       IP address versions that are not supported or recognized.
>
>
> Specifically, support for FQDN names there was removed due to RFC 8445
> implementation issues. I believe Simon Perreault suggested this change.
>
> Regards,
> _____________
> Roman Shpount
>
>
> On Fri, Feb 1, 2019 at 12:02 AM Justin Uberti <juberti@google.com> wrote:
>
>> My recommendation here would be that we do c=IN IP6
>> 3557773f-5f01-46a4-aa14-54ab35b3d778.local, with either IP4 or IP6
>> depending on which type of address is being wrapped.
>>
>> Re #1: RFC 4566 seems to indicate you can use either IP4 or IP6 for FQDN
>> in the c= line.
>>
>>      unicast-address =     IP4-address / IP6-address / FQDN / extn-addr
>>
>>
>> Re #2: Quoth 5245 <https://tools.ietf.org/html/rfc5245#section-15.1>:
>>
>>    <connection-address>:  is taken from RFC 4566 <https://tools.ietf.org/html/rfc4566> [RFC4566 <https://tools.ietf.org/html/rfc4566>].  It is the
>>       IP address of the candidate, allowing for IPv4 addresses, IPv6
>>       addresses, and *fully qualified domain names (FQDNs).*  When parsing
>>       this field, an agent can differentiate an IPv4 address and an IPv6
>>
>>       address by presence of a colon in its value - the presence of a
>>       colon indicates IPv6.  An agent MUST ignore candidate lines that
>>       include candidates with IP address versions that are not supported
>>       or recognized.  An IP address SHOULD be used, but an FQDN MAY be
>>       used in place of an IP address.  In that case, when receiving an
>>       offer or answer containing an FQDN in an a=candidate attribute,
>>       the FQDN is looked up in the DNS first using an AAAA record
>>       (assuming the agent supports IPv6), and if no result is found or
>>       the agent only supports IPv4, using an A.  If the DNS query
>>       returns more than one IP address, one is chosen, and then used for
>>       the remainder of ICE processing.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Jan 31, 2019 at 8:43 PM Roman Shpount <roman@telurix.com> wrote:
>>
>>> On Thu, Jan 31, 2019 at 10:58 PM Justin Uberti <juberti@google.com>
>>> wrote:
>>>
>>>> We can however all agree that "c=IN IP6" is busted:
>>>> https://bugs.chromium.org/p/chromium/issues/detail?id=927309
>>>>
>>>>>
>>>>>>
>>> I guess one way to interpret this that each address should have a MDNS
>>> alias. So, if you are dealing with dual stack host, it should provide two
>>> MDNS candidates, one of which is IPv4 and another IPv6. The c= line should
>>> specify FQDN for one of those candidates and specify the type (IP4 or IP6).
>>>
>>> There are two problems:
>>>
>>> 1. There is no way to know which address type is in the
>>> candidate-address when FQDN is used there. Guidance in ice-sip-sdp is
>>> talking about the presence of column in IP6 address, but this definitely
>>> does not apply to FQDN. It would've been better to specify something like
>>> local4 and local6 as FQDN suffix in MDNS alias to specify the
>>> candidate-address type so that correct DNS request can be issued.
>>>
>>> 2. A lot (if not most) SDP/ICE implementations do no support parsing
>>> FQDN in candidate-address or c= line. This might create interop problems
>>> since RFC 5245 specified that candidate-address is an IP Address.
>>>
>>> Regards,
>>> _____________
>>> Roman Shpount
>>>
>>>
>>

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

<div dir=3D"ltr">I understand there were questions about the general case (=
e.g. regular DNS names), but how do we plan to reconcile this removal with =
the need for mDNS hostnames?</div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Fri, Feb 1, 2019 at 9:09 AM Roman Shpount =
&lt;<a href=3D"mailto:roman@telurix.com">roman@telurix.com</a>&gt; wrote:<b=
r></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 dir=3D"ltr">=
<div dir=3D"ltr"><div dir=3D"ltr">Hi Justin,<div><br></div><div>I agree reg=
arding #1 in theory, even though in practice a lot of (most) devices will n=
ot accept FQDN in either c=3D or ICE candidate.</div><div><br></div><div>Re=
garding #2, mmusic-ice-sip-sdp was updated (<a href=3D"https://tools.ietf.o=
rg/html/draft-ietf-mmusic-ice-sip-sdp-24#section-4.1" target=3D"_blank">htt=
ps://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-24#section-4.1</a>):=
</div><div><br></div><div><pre class=3D"gmail-m_-4390259510233163330gmail-n=
ewpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break=
-before:page;color:rgb(0,0,0)">   &lt;connection-address&gt;:  is taken fro=
m <a href=3D"https://tools.ietf.org/html/rfc4566" target=3D"_blank">RFC 456=
6</a> [<a href=3D"https://tools.ietf.org/html/rfc4566" title=3D"&quot;SDP: =
Session Description Protocol&quot;" target=3D"_blank">RFC4566</a>].  It is =
the
      IP address of the candidate.  When parsing this field, an agent
      can differentiate an IPv4 address and an IPv6 address by presence
      of a colon in its value -- the presence of a colon indicates IPv6.
      An agent MUST ignore candidate lines that include candidates with
      IP address versions that are not supported or recognized.</pre><pre c=
lass=3D"gmail-m_-4390259510233163330gmail-newpage" style=3D"font-size:13.33=
33px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><=
br></pre>Specifically, support for FQDN names there was removed due to=C2=
=A0<span style=3D"color:rgb(0,0,0)">RFC 8445 implementation issues. I belie=
ve=C2=A0</span><font color=3D"#000000">Simon Perreault suggested this chang=
e.</font></div><div><font color=3D"#000000"><br></font></div><div><font col=
or=3D"#000000">Regards,<br></font><div><div dir=3D"ltr" class=3D"gmail-m_-4=
390259510233163330gmail_signature">_____________<br>Roman Shpount</div></di=
v><br></div></div></div></div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Fri, Feb 1, 2019 at 12:02 AM Justin Uberti &lt;<=
a href=3D"mailto:juberti@google.com" target=3D"_blank">juberti@google.com</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr"><div dir=3D"ltr"><div>My recommendation here would be that w=
e do c=3DIN IP6 3557773f-5f01-46a4-aa14-54ab35b3d778.local, with either IP4=
 or IP6 depending on which type of address is being wrapped.</div><div><br>=
</div><div>Re #1:=C2=A0RFC 4566 seems to indicate you can use either IP4 or=
 IP6 for FQDN in the c=3D line.</div><div><br></div><div><pre class=3D"gmai=
l-m_-4390259510233163330gmail-m_7058075087377128197gmail-newpage" style=3D"=
font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;colo=
r:rgb(0,0,0)">     unicast-address =3D     IP4-address / IP6-address / FQDN=
 / extn-addr
</pre></div><div><br></div>Re #2: Quoth <a href=3D"https://tools.ietf.org/h=
tml/rfc5245#section-15.1" target=3D"_blank">5245</a>:<div><br></div><div><p=
re class=3D"gmail-m_-4390259510233163330gmail-m_7058075087377128197gmail-ne=
wpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-=
before:page;color:rgb(0,0,0)">   &lt;connection-address&gt;:  is taken from=
 <a href=3D"https://tools.ietf.org/html/rfc4566" target=3D"_blank">RFC 4566=
</a> [<a href=3D"https://tools.ietf.org/html/rfc4566" title=3D"&quot;SDP: S=
ession Description Protocol&quot;" target=3D"_blank">RFC4566</a>].  It is t=
he
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and <b>fully qualified domain names (FQDNs).</b>  When par=
sing
      this field, an agent can differentiate an IPv4 address and an IPv6
</pre><pre class=3D"gmail-m_-4390259510233163330gmail-m_7058075087377128197=
gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0p=
x;break-before:page;color:rgb(0,0,0)">      address by presence of a colon =
in its value - the presence of a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=3Dcandidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.
</pre><pre class=3D"gmail-m_-4390259510233163330gmail-m_7058075087377128197=
gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0p=
x;break-before:page;color:rgb(0,0,0)"><br></pre><pre class=3D"gmail-m_-4390=
259510233163330gmail-m_7058075087377128197gmail-newpage" style=3D"font-size=
:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0=
,0)"><br></pre><pre class=3D"gmail-m_-4390259510233163330gmail-m_7058075087=
377128197gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-=
bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><pre class=3D"gmai=
l-m_-4390259510233163330gmail-m_7058075087377128197gmail-newpage" style=3D"=
font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;colo=
r:rgb(0,0,0)"><br></pre><pre class=3D"gmail-m_-4390259510233163330gmail-m_7=
058075087377128197gmail-newpage" style=3D"font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><pre clas=
s=3D"gmail-m_-4390259510233163330gmail-m_7058075087377128197gmail-newpage" =
style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:=
page;color:rgb(0,0,0)"><br></pre><br class=3D"gmail-m_-4390259510233163330g=
mail-m_7058075087377128197gmail-Apple-interchange-newline"></div></div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On T=
hu, Jan 31, 2019 at 8:43 PM Roman Shpount &lt;<a href=3D"mailto:roman@telur=
ix.com" target=3D"_blank">roman@telurix.com</a>&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr=
"><div dir=3D"ltr"><div><div dir=3D"ltr" class=3D"gmail-m_-4390259510233163=
330gmail-m_7058075087377128197gmail-m_4773857553044000712gmail-m_8367249769=
720427912gmail_signature">On Thu, Jan 31, 2019 at 10:58 PM Justin Uberti &l=
t;<a href=3D"mailto:juberti@google.com" target=3D"_blank">juberti@google.co=
m</a>&gt; wrote:<br></div></div></div><div class=3D"gmail_quote"><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><=
div dir=3D"ltr">We can however all agree that &quot;c=3DIN IP6&quot; is bus=
ted:=C2=A0<a href=3D"https://bugs.chromium.org/p/chromium/issues/detail?id=
=3D927309" target=3D"_blank">https://bugs.chromium.org/p/chromium/issues/de=
tail?id=3D927309</a></div></div></div><div class=3D"gmail_quote"><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><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"><br></blockquote></div></blockquo=
te></div></blockquote><div><br></div><div>I guess one way to interpret this=
 that each address should have a MDNS alias. So, if you are dealing with du=
al stack host, it should provide two MDNS candidates, one of which is IPv4 =
and another IPv6. The c=3D line should specify FQDN for one of those candid=
ates and specify the type (IP4 or IP6).</div><div><br></div><div>There are =
two problems:</div><div><br></div><div>1. There is no way to know which add=
ress type is in the candidate-address when FQDN is used there. Guidance in =
ice-sip-sdp is talking about the presence of column in IP6 address, but thi=
s definitely does not apply to FQDN. It would&#39;ve been better to specify=
 something like local4 and local6 as FQDN suffix in MDNS alias to specify t=
he candidate-address type so that correct DNS request can be issued.</div><=
div><br></div><div>2. A lot (if not most) SDP/ICE implementations do no sup=
port parsing FQDN in candidate-address or c=3D line. This might create inte=
rop problems since RFC 5245 specified that candidate-address is an IP Addre=
ss.</div><div><br></div><div>Regards,</div>_____________<br>Roman Shpount<b=
r class=3D"gmail-m_-4390259510233163330gmail-m_7058075087377128197gmail-m_4=
773857553044000712gmail-m_8367249769720427912gmail-Apple-interchange-newlin=
e"><div>=C2=A0</div></div></div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>

--000000000000af0cc80580d89f22--


From nobody Fri Feb  1 11:18:18 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 B02C613129A for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 11:18:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.03
X-Spam-Level: 
X-Spam-Status: No, score=-2.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 9aCQMhiFSwlZ for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 11:18:13 -0800 (PST)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (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 E27B8131295 for <mmusic@ietf.org>; Fri,  1 Feb 2019 11:18:12 -0800 (PST)
Received: by mail-pg1-x52c.google.com with SMTP id z11so3386011pgu.0 for <mmusic@ietf.org>; Fri, 01 Feb 2019 11:18:12 -0800 (PST)
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=ksCmdtoHl28Hj3jY7BQmUL1XIbv8XQSylwigR5lyfRM=; b=ay9s+HVbcLON6dyEUg81WA2c/r+GX+qsIGVJUKxNGKRA9LQdxgVwAv/gc8TPpRK6xT uO3GvlCn9mShMaQQnmM8ACR6Nxa9jGp+h/eBl46fVBt3ey9QfHwDjg8Tgur2RUnCTHFE wuevjgnSKvvHhUMb5VKRRF8ayJIXGGBN/LTVmy+GHOhFtBGSLGKAOQL4oeT69005FlQK +c5YLvfNBsM4s2heJ0KMvbi+I9L2gXxd3ACZEb2/WGQZg5fJAnuCHzsEV86bvPBo9F25 nfaG9TC12vTG2h/q9lOWxOe1aVjUuml/BTvCdGhGr0WdeP7apg+CfK4Agn9Wa39X+vzO YFNA==
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=ksCmdtoHl28Hj3jY7BQmUL1XIbv8XQSylwigR5lyfRM=; b=j6nTPtEzbzd44SR5/3B9I9iOZAcXwjcDg+1R7dmih1OrTA2zREMC1ElxgEhBwZ+TDI 39sQe8EmpMPBzW0n/r9lLz+vz6e2mQY4Md9ALODogYIaJedwZnEnFD+tMmbgXcovqYAo U0AQkknlY3BhuO592cxxiBlmxS3Tr66G8DGRTmrxQHGBEVYGoub84o5FihDbUGVJ0D/k pENPsVMeDEIF3eN98RIUEaYWryP3kSnF9bSXIFIBhCWIRoi6QEtdfAPBsl8ijyvEAHEA 91XXMN/l61WiFO6YNRYlag3HQaJ/vv764E85xC3BEl9oEiHGSEqCVoPdQJlbvu503QoR Ka3A==
X-Gm-Message-State: AHQUAub0QvduXJaGghouqlmdnigcbUH6mkOr+mkoMkxjI61iSA/xV11S NgFcDXIlpzSqkca2YfCKOFR11A==
X-Google-Smtp-Source: AHgI3IZ1WeFfXUicROyXm+ZU3p+DJqPSM9LBVUVjNJUHumlnmpZ/VCYJni5GOmWhjzrbbiMgEhuNXA==
X-Received: by 2002:a62:3a8b:: with SMTP id v11mr9399110pfj.81.1549048692269;  Fri, 01 Feb 2019 11:18:12 -0800 (PST)
Received: from mail-pf1-f180.google.com (mail-pf1-f180.google.com. [209.85.210.180]) by smtp.gmail.com with ESMTPSA id g190sm10014309pgc.28.2019.02.01.11.18.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Feb 2019 11:18:11 -0800 (PST)
Received: by mail-pf1-f180.google.com with SMTP id w73so3671778pfk.10; Fri, 01 Feb 2019 11:18:11 -0800 (PST)
X-Received: by 2002:a62:160d:: with SMTP id 13mr40326587pfw.203.1549048690972;  Fri, 01 Feb 2019 11:18:10 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com>
In-Reply-To: <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 1 Feb 2019 14:18:01 -0500
X-Gmail-Original-Message-ID: <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com>
Message-ID: <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>, Simon Perreault <sperreault@jive.com>
Content-Type: multipart/alternative; boundary="000000000000f71ef00580da00c6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/UwaJA6L2qcnwqxCbphsVhABQk80>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 01 Feb 2019 19:18:16 -0000

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

Most likely mDNS draft will need to update RFC 8445 to specify how ICE
nomination procedures are modified, when mDNS is used as candidate-address.

As far as mmusic-ice-sip-sdp is concerned, one option would be to allow
FQDN as candidate-address. The guidance for handling FQDN in
candidate-address should be updated from RFC 5245 and should specify that
FQDN names should be ignored. mDNS ICE draft then will update ice-sip-sdp
and specify that mDNS FQDN should be handled according the procedures of
this draft.

Another option, which I think word work better with existing specifications
is to add a new candidate type -- mdns. This way, instead of magic DNS
suffix, candidate type will be used to determine that this candidate should
be handled differently. I do not think MDNS candidates can be used for
anything except host candidates, so making then a special candidate type
might be the least painful option. It might even make sense to make
separate types for IPv4 and IPv6 MDNS candidates which would save a DNS
query for each candidate.

Regards,
_____________
Roman Shpount


On Fri, Feb 1, 2019 at 12:39 PM Justin Uberti <juberti@google.com> wrote:

> I understand there were questions about the general case (e.g. regular DNS
> names), but how do we plan to reconcile this removal with the need for mDNS
> hostnames?
>
> On Fri, Feb 1, 2019 at 9:09 AM Roman Shpount <roman@telurix.com> wrote:
>
>> Hi Justin,
>>
>> I agree regarding #1 in theory, even though in practice a lot of (most)
>> devices will not accept FQDN in either c= or ICE candidate.
>>
>> Regarding #2, mmusic-ice-sip-sdp was updated (
>> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-24#section-4.1
>> ):
>>
>>    <connection-address>:  is taken from RFC 4566 <https://tools.ietf.org/html/rfc4566> [RFC4566 <https://tools.ietf.org/html/rfc4566>].  It is the
>>       IP address of the candidate.  When parsing this field, an agent
>>       can differentiate an IPv4 address and an IPv6 address by presence
>>       of a colon in its value -- the presence of a colon indicates IPv6.
>>       An agent MUST ignore candidate lines that include candidates with
>>       IP address versions that are not supported or recognized.
>>
>>
>> Specifically, support for FQDN names there was removed due to RFC 8445
>> implementation issues. I believe Simon Perreault suggested this change.
>>
>> Regards,
>> _____________
>> Roman Shpount
>>
>>
>> On Fri, Feb 1, 2019 at 12:02 AM Justin Uberti <juberti@google.com> wrote:
>>
>>> My recommendation here would be that we do c=IN IP6
>>> 3557773f-5f01-46a4-aa14-54ab35b3d778.local, with either IP4 or IP6
>>> depending on which type of address is being wrapped.
>>>
>>> Re #1: RFC 4566 seems to indicate you can use either IP4 or IP6 for FQDN
>>> in the c= line.
>>>
>>>      unicast-address =     IP4-address / IP6-address / FQDN / extn-addr
>>>
>>>
>>> Re #2: Quoth 5245 <https://tools.ietf.org/html/rfc5245#section-15.1>:
>>>
>>>    <connection-address>:  is taken from RFC 4566 <https://tools.ietf.org/html/rfc4566> [RFC4566 <https://tools.ietf.org/html/rfc4566>].  It is the
>>>       IP address of the candidate, allowing for IPv4 addresses, IPv6
>>>       addresses, and *fully qualified domain names (FQDNs).*  When parsing
>>>       this field, an agent can differentiate an IPv4 address and an IPv6
>>>
>>>       address by presence of a colon in its value - the presence of a
>>>       colon indicates IPv6.  An agent MUST ignore candidate lines that
>>>       include candidates with IP address versions that are not supported
>>>       or recognized.  An IP address SHOULD be used, but an FQDN MAY be
>>>       used in place of an IP address.  In that case, when receiving an
>>>       offer or answer containing an FQDN in an a=candidate attribute,
>>>       the FQDN is looked up in the DNS first using an AAAA record
>>>       (assuming the agent supports IPv6), and if no result is found or
>>>       the agent only supports IPv4, using an A.  If the DNS query
>>>       returns more than one IP address, one is chosen, and then used for
>>>       the remainder of ICE processing.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Thu, Jan 31, 2019 at 8:43 PM Roman Shpount <roman@telurix.com> wrote:
>>>
>>>> On Thu, Jan 31, 2019 at 10:58 PM Justin Uberti <juberti@google.com>
>>>> wrote:
>>>>
>>>>> We can however all agree that "c=IN IP6" is busted:
>>>>> https://bugs.chromium.org/p/chromium/issues/detail?id=927309
>>>>>
>>>>>>
>>>>>>>
>>>> I guess one way to interpret this that each address should have a MDNS
>>>> alias. So, if you are dealing with dual stack host, it should provide two
>>>> MDNS candidates, one of which is IPv4 and another IPv6. The c= line should
>>>> specify FQDN for one of those candidates and specify the type (IP4 or IP6).
>>>>
>>>> There are two problems:
>>>>
>>>> 1. There is no way to know which address type is in the
>>>> candidate-address when FQDN is used there. Guidance in ice-sip-sdp is
>>>> talking about the presence of column in IP6 address, but this definitely
>>>> does not apply to FQDN. It would've been better to specify something like
>>>> local4 and local6 as FQDN suffix in MDNS alias to specify the
>>>> candidate-address type so that correct DNS request can be issued.
>>>>
>>>> 2. A lot (if not most) SDP/ICE implementations do no support parsing
>>>> FQDN in candidate-address or c= line. This might create interop problems
>>>> since RFC 5245 specified that candidate-address is an IP Address.
>>>>
>>>> Regards,
>>>> _____________
>>>> Roman Shpount
>>>>
>>>>
>>>

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

<div dir=3D"ltr"><div dir=3D"ltr">Most likely mDNS draft will need to updat=
e <span style=3D"color:rgb(0,0,0)">RFC 8445</span>=C2=A0to specify how ICE =
nomination procedures are modified, when mDNS is used as candidate-address.=
=C2=A0</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">As far as mmusic-ic=
e-sip-sdp is concerned, one option would be to allow FQDN as candidate-addr=
ess. The guidance for handling FQDN in candidate-address should be updated =
from RFC 5245 and should specify that FQDN names should be ignored. mDNS IC=
E draft then will update ice-sip-sdp and specify that mDNS FQDN should be h=
andled according the procedures of this draft.</div><div dir=3D"ltr"><br></=
div><div dir=3D"ltr">Another option, which I think word work better with ex=
isting specifications is to add a new candidate type -- mdns. This way, ins=
tead of magic DNS suffix, candidate type will be used to determine that thi=
s candidate should be handled differently. I do not think MDNS candidates c=
an be used for anything except host candidates, so making then a special ca=
ndidate type might be the least painful option. It might even make sense to=
 make separate types for IPv4 and IPv6 MDNS candidates which would save a D=
NS query for each candidate.</div><div dir=3D"ltr"><br></div><div dir=3D"lt=
r">Regards,<br clear=3D"all"><div><div dir=3D"ltr" class=3D"gmail_signature=
" data-smartmail=3D"gmail_signature">_____________<br>Roman Shpount</div></=
div><br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmai=
l_attr">On Fri, Feb 1, 2019 at 12:39 PM Justin Uberti &lt;<a href=3D"mailto=
:juberti@google.com">juberti@google.com</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">I understand there =
were questions about the general case (e.g. regular DNS names), but how do =
we plan to reconcile this removal with the need for mDNS hostnames?</div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, =
Feb 1, 2019 at 9:09 AM Roman Shpount &lt;<a href=3D"mailto:roman@telurix.co=
m" target=3D"_blank">roman@telurix.com</a>&gt; wrote:<br></div><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 dir=3D"ltr"><di=
v dir=3D"ltr">Hi Justin,<div><br></div><div>I agree regarding #1 in theory,=
 even though in practice a lot of (most) devices will not accept FQDN in ei=
ther c=3D or ICE candidate.</div><div><br></div><div>Regarding #2, mmusic-i=
ce-sip-sdp was updated (<a href=3D"https://tools.ietf.org/html/draft-ietf-m=
music-ice-sip-sdp-24#section-4.1" target=3D"_blank">https://tools.ietf.org/=
html/draft-ietf-mmusic-ice-sip-sdp-24#section-4.1</a>):</div><div><br></div=
><div><pre class=3D"gmail-m_-2298128030139745895gmail-m_-439025951023316333=
0gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0=
px;break-before:page;color:rgb(0,0,0)">   &lt;connection-address&gt;:  is t=
aken from <a href=3D"https://tools.ietf.org/html/rfc4566" target=3D"_blank"=
>RFC 4566</a> [<a href=3D"https://tools.ietf.org/html/rfc4566" title=3D"&qu=
ot;SDP: Session Description Protocol&quot;" target=3D"_blank">RFC4566</a>].=
  It is the
      IP address of the candidate.  When parsing this field, an agent
      can differentiate an IPv4 address and an IPv6 address by presence
      of a colon in its value -- the presence of a colon indicates IPv6.
      An agent MUST ignore candidate lines that include candidates with
      IP address versions that are not supported or recognized.</pre><pre c=
lass=3D"gmail-m_-2298128030139745895gmail-m_-4390259510233163330gmail-newpa=
ge" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-bef=
ore:page;color:rgb(0,0,0)"><br></pre>Specifically, support for FQDN names t=
here was removed due to=C2=A0<span style=3D"color:rgb(0,0,0)">RFC 8445 impl=
ementation issues. I believe=C2=A0</span><font color=3D"#000000">Simon Perr=
eault suggested this change.</font></div><div><font color=3D"#000000"><br><=
/font></div><div><font color=3D"#000000">Regards,<br></font><div><div dir=
=3D"ltr" class=3D"gmail-m_-2298128030139745895gmail-m_-4390259510233163330g=
mail_signature">_____________<br>Roman Shpount</div></div><br></div></div><=
/div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Fri, Feb 1, 2019 at 12:02 AM Justin Uberti &lt;<a href=3D"mailto:ju=
berti@google.com" target=3D"_blank">juberti@google.com</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div=
 dir=3D"ltr"><div>My recommendation here would be that we do c=3DIN IP6 355=
7773f-5f01-46a4-aa14-54ab35b3d778.local, with either IP4 or IP6 depending o=
n which type of address is being wrapped.</div><div><br></div><div>Re #1:=
=C2=A0RFC 4566 seems to indicate you can use either IP4 or IP6 for FQDN in =
the c=3D line.</div><div><br></div><div><pre class=3D"gmail-m_-229812803013=
9745895gmail-m_-4390259510233163330gmail-m_7058075087377128197gmail-newpage=
" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-befor=
e:page;color:rgb(0,0,0)">     unicast-address =3D     IP4-address / IP6-add=
ress / FQDN / extn-addr
</pre></div><div><br></div>Re #2: Quoth <a href=3D"https://tools.ietf.org/h=
tml/rfc5245#section-15.1" target=3D"_blank">5245</a>:<div><br></div><div><p=
re class=3D"gmail-m_-2298128030139745895gmail-m_-4390259510233163330gmail-m=
_7058075087377128197gmail-newpage" style=3D"font-size:13.3333px;margin-top:=
0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">   &lt;connection=
-address&gt;:  is taken from <a href=3D"https://tools.ietf.org/html/rfc4566=
" target=3D"_blank">RFC 4566</a> [<a href=3D"https://tools.ietf.org/html/rf=
c4566" title=3D"&quot;SDP: Session Description Protocol&quot;" target=3D"_b=
lank">RFC4566</a>].  It is the
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and <b>fully qualified domain names (FQDNs).</b>  When par=
sing
      this field, an agent can differentiate an IPv4 address and an IPv6
</pre><pre class=3D"gmail-m_-2298128030139745895gmail-m_-439025951023316333=
0gmail-m_7058075087377128197gmail-newpage" style=3D"font-size:13.3333px;mar=
gin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">      add=
ress by presence of a colon in its value - the presence of a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=3Dcandidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.
</pre><pre class=3D"gmail-m_-2298128030139745895gmail-m_-439025951023316333=
0gmail-m_7058075087377128197gmail-newpage" style=3D"font-size:13.3333px;mar=
gin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre=
><pre class=3D"gmail-m_-2298128030139745895gmail-m_-4390259510233163330gmai=
l-m_7058075087377128197gmail-newpage" style=3D"font-size:13.3333px;margin-t=
op:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><pre=
 class=3D"gmail-m_-2298128030139745895gmail-m_-4390259510233163330gmail-m_7=
058075087377128197gmail-newpage" style=3D"font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><pre clas=
s=3D"gmail-m_-2298128030139745895gmail-m_-4390259510233163330gmail-m_705807=
5087377128197gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;mar=
gin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><pre class=3D"=
gmail-m_-2298128030139745895gmail-m_-4390259510233163330gmail-m_70580750873=
77128197gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-b=
ottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><pre class=3D"gmail=
-m_-2298128030139745895gmail-m_-4390259510233163330gmail-m_7058075087377128=
197gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom=
:0px;break-before:page;color:rgb(0,0,0)"><br></pre><br class=3D"gmail-m_-22=
98128030139745895gmail-m_-4390259510233163330gmail-m_7058075087377128197gma=
il-Apple-interchange-newline"></div></div></div><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jan 31, 2019 at 8:43 PM R=
oman Shpount &lt;<a href=3D"mailto:roman@telurix.com" target=3D"_blank">rom=
an@telurix.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div><div =
dir=3D"ltr" class=3D"gmail-m_-2298128030139745895gmail-m_-43902595102331633=
30gmail-m_7058075087377128197gmail-m_4773857553044000712gmail-m_83672497697=
20427912gmail_signature">On Thu, Jan 31, 2019 at 10:58 PM Justin Uberti &lt=
;<a href=3D"mailto:juberti@google.com" target=3D"_blank">juberti@google.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 so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><d=
iv dir=3D"ltr">We can however all agree that &quot;c=3DIN IP6&quot; is bust=
ed:=C2=A0<a href=3D"https://bugs.chromium.org/p/chromium/issues/detail?id=
=3D927309" target=3D"_blank">https://bugs.chromium.org/p/chromium/issues/de=
tail?id=3D927309</a></div></div></div><div class=3D"gmail_quote"><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><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"><br></blockquote></div></blockquo=
te></div></blockquote><div><br></div><div>I guess one way to interpret this=
 that each address should have a MDNS alias. So, if you are dealing with du=
al stack host, it should provide two MDNS candidates, one of which is IPv4 =
and another IPv6. The c=3D line should specify FQDN for one of those candid=
ates and specify the type (IP4 or IP6).</div><div><br></div><div>There are =
two problems:</div><div><br></div><div>1. There is no way to know which add=
ress type is in the candidate-address when FQDN is used there. Guidance in =
ice-sip-sdp is talking about the presence of column in IP6 address, but thi=
s definitely does not apply to FQDN. It would&#39;ve been better to specify=
 something like local4 and local6 as FQDN suffix in MDNS alias to specify t=
he candidate-address type so that correct DNS request can be issued.</div><=
div><br></div><div>2. A lot (if not most) SDP/ICE implementations do no sup=
port parsing FQDN in candidate-address or c=3D line. This might create inte=
rop problems since RFC 5245 specified that candidate-address is an IP Addre=
ss.</div><div><br></div><div>Regards,</div>_____________<br>Roman Shpount<b=
r class=3D"gmail-m_-2298128030139745895gmail-m_-4390259510233163330gmail-m_=
7058075087377128197gmail-m_4773857553044000712gmail-m_8367249769720427912gm=
ail-Apple-interchange-newline"><div>=C2=A0</div></div></div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div></div>

--000000000000f71ef00580da00c6--


From nobody Fri Feb  1 11:39:25 2019
Return-Path: <juberti@google.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 7613F1312BC for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 11:39:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.641
X-Spam-Level: 
X-Spam-Status: No, score=-17.641 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 3CtM2n_6HRh2 for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 11:39:13 -0800 (PST)
Received: from mail-it1-x12f.google.com (mail-it1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 4BCB91312C1 for <mmusic@ietf.org>; Fri,  1 Feb 2019 11:39:13 -0800 (PST)
Received: by mail-it1-x12f.google.com with SMTP id a6so11504236itl.4 for <mmusic@ietf.org>; Fri, 01 Feb 2019 11:39:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xcHBuDlh3EaXWoDoQmxZGhJzH/B1FkmLsOZnDiinlzA=; b=JWD8w/vnlAl1mq5fm18raSjveDSjArWqukzE9aNjfmaExr9wQnI30liSDWLQukzyXu p+js2c8FapOMdsE7mf5TeRrlbaS/tg7MAIxVI68mruQDhgPZcrKwHmdztoOj6iolG/RN gnhcp6C/iZEPLD2MT4SGBR6HaRITdmAgZAF1QMo9jD+UNBsDkAvkH6/MLpxVzAIWP+pz NoQdEJE4OEWiT7OjTyqIjTmfQWu3RHDNTlXpRvtyo8s2jtqWeHpnqvrXygD/vOLRjfdF qBpnTHsuxmR31Sn+2hc05xJe5uuqo52scH2AJ+s0QU4LCvfhuE1YFqf7F4l8a29U7IQf uliw==
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=xcHBuDlh3EaXWoDoQmxZGhJzH/B1FkmLsOZnDiinlzA=; b=f1ocAhUNVAbSahGW3hm1bWl8InwgThFyF6o7GSzF0wwicMYmDLkc03+bWI+B4e6mfj uUjhq0wUjk7tWcJzDKKZQJls8ak3mRZovsuOcnzGf0y+MVB4yv9ykNEuUX1OinH5he4n bAmENibqzqvowc0a43ktIMJW4ZGVS0Pc/pqFD0pMgG63jkUBYgx77ENIHIggvez+WUaF h/VrHtvhgHYNzeANS4FGTfkpbJvzAQlx8V2Qhzv8qYpzkCrtdqlceU6+LycbQVpt5ZSh Dg+MkhBsvvkjKHvD+/4nC4oeTOyLbE7etpwgFO1J1Ws2tBwIWEGyjmvLk8fz1J9gqjiM 2BbQ==
X-Gm-Message-State: AJcUukd2dx1vx9Sb5+2LcF9Uopf4AiIuO7xr5q6CVp3nQSiFD9FRlWIb YAUezO110XUhPCcTBitomULWQcRvmOx+mrOfDlyNfg==
X-Google-Smtp-Source: ALg8bN4SUTNQTegwlDqtK/xlWF9ST6S2irLSHYUmeWoDH/TSNHpfJ8Dwb2RJj9JY7R0GaJiRUYxYu0kalmAZlxONFmw=
X-Received: by 2002:a02:94eb:: with SMTP id x98mr25051601jah.88.1549049952060;  Fri, 01 Feb 2019 11:39:12 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com>
In-Reply-To: <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Fri, 1 Feb 2019 11:39:00 -0800
Message-ID: <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>, Simon Perreault <sperreault@jive.com>
Content-Type: multipart/alternative; boundary="000000000000224ef80580da4c45"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xcRDZCV4uYef2Li_MNGFSk6KMCc>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 01 Feb 2019 19:39:18 -0000

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

This has all been discussed at length in rtcweb and I don't think any
significant changes are needed, although I tend to think that we should
restore the removed FQDN text from mmusic-ice-sip-sdp, which is the only
thing not in alignment at this point in time.



On Fri, Feb 1, 2019 at 11:18 AM Roman Shpount <roman@telurix.com> wrote:

> Most likely mDNS draft will need to update RFC 8445 to specify how ICE
> nomination procedures are modified, when mDNS is used as candidate-address.
>
> As far as mmusic-ice-sip-sdp is concerned, one option would be to allow
> FQDN as candidate-address. The guidance for handling FQDN in
> candidate-address should be updated from RFC 5245 and should specify that
> FQDN names should be ignored. mDNS ICE draft then will update ice-sip-sdp
> and specify that mDNS FQDN should be handled according the procedures of
> this draft.
>
> Another option, which I think word work better with existing
> specifications is to add a new candidate type -- mdns. This way, instead of
> magic DNS suffix, candidate type will be used to determine that this
> candidate should be handled differently. I do not think MDNS candidates can
> be used for anything except host candidates, so making then a special
> candidate type might be the least painful option. It might even make sense
> to make separate types for IPv4 and IPv6 MDNS candidates which would save a
> DNS query for each candidate.
>
> Regards,
> _____________
> Roman Shpount
>
>
> On Fri, Feb 1, 2019 at 12:39 PM Justin Uberti <juberti@google.com> wrote:
>
>> I understand there were questions about the general case (e.g. regular
>> DNS names), but how do we plan to reconcile this removal with the need for
>> mDNS hostnames?
>>
>> On Fri, Feb 1, 2019 at 9:09 AM Roman Shpount <roman@telurix.com> wrote:
>>
>>> Hi Justin,
>>>
>>> I agree regarding #1 in theory, even though in practice a lot of (most)
>>> devices will not accept FQDN in either c= or ICE candidate.
>>>
>>> Regarding #2, mmusic-ice-sip-sdp was updated (
>>> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-24#section-4.1
>>> ):
>>>
>>>    <connection-address>:  is taken from RFC 4566 <https://tools.ietf.org/html/rfc4566> [RFC4566 <https://tools.ietf.org/html/rfc4566>].  It is the
>>>       IP address of the candidate.  When parsing this field, an agent
>>>       can differentiate an IPv4 address and an IPv6 address by presence
>>>       of a colon in its value -- the presence of a colon indicates IPv6.
>>>       An agent MUST ignore candidate lines that include candidates with
>>>       IP address versions that are not supported or recognized.
>>>
>>>
>>> Specifically, support for FQDN names there was removed due to RFC 8445
>>> implementation issues. I believe Simon Perreault suggested this change.
>>>
>>> Regards,
>>> _____________
>>> Roman Shpount
>>>
>>>
>>> On Fri, Feb 1, 2019 at 12:02 AM Justin Uberti <juberti@google.com>
>>> wrote:
>>>
>>>> My recommendation here would be that we do c=IN IP6
>>>> 3557773f-5f01-46a4-aa14-54ab35b3d778.local, with either IP4 or IP6
>>>> depending on which type of address is being wrapped.
>>>>
>>>> Re #1: RFC 4566 seems to indicate you can use either IP4 or IP6 for
>>>> FQDN in the c= line.
>>>>
>>>>      unicast-address =     IP4-address / IP6-address / FQDN / extn-addr
>>>>
>>>>
>>>> Re #2: Quoth 5245 <https://tools.ietf.org/html/rfc5245#section-15.1>:
>>>>
>>>>    <connection-address>:  is taken from RFC 4566 <https://tools.ietf.org/html/rfc4566> [RFC4566 <https://tools.ietf.org/html/rfc4566>].  It is the
>>>>       IP address of the candidate, allowing for IPv4 addresses, IPv6
>>>>       addresses, and *fully qualified domain names (FQDNs).*  When parsing
>>>>       this field, an agent can differentiate an IPv4 address and an IPv6
>>>>
>>>>       address by presence of a colon in its value - the presence of a
>>>>       colon indicates IPv6.  An agent MUST ignore candidate lines that
>>>>       include candidates with IP address versions that are not supported
>>>>       or recognized.  An IP address SHOULD be used, but an FQDN MAY be
>>>>       used in place of an IP address.  In that case, when receiving an
>>>>       offer or answer containing an FQDN in an a=candidate attribute,
>>>>       the FQDN is looked up in the DNS first using an AAAA record
>>>>       (assuming the agent supports IPv6), and if no result is found or
>>>>       the agent only supports IPv4, using an A.  If the DNS query
>>>>       returns more than one IP address, one is chosen, and then used for
>>>>       the remainder of ICE processing.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Jan 31, 2019 at 8:43 PM Roman Shpount <roman@telurix.com>
>>>> wrote:
>>>>
>>>>> On Thu, Jan 31, 2019 at 10:58 PM Justin Uberti <juberti@google.com>
>>>>> wrote:
>>>>>
>>>>>> We can however all agree that "c=IN IP6" is busted:
>>>>>> https://bugs.chromium.org/p/chromium/issues/detail?id=927309
>>>>>>
>>>>>>>
>>>>>>>>
>>>>> I guess one way to interpret this that each address should have a MDNS
>>>>> alias. So, if you are dealing with dual stack host, it should provide two
>>>>> MDNS candidates, one of which is IPv4 and another IPv6. The c= line should
>>>>> specify FQDN for one of those candidates and specify the type (IP4 or IP6).
>>>>>
>>>>> There are two problems:
>>>>>
>>>>> 1. There is no way to know which address type is in the
>>>>> candidate-address when FQDN is used there. Guidance in ice-sip-sdp is
>>>>> talking about the presence of column in IP6 address, but this definitely
>>>>> does not apply to FQDN. It would've been better to specify something like
>>>>> local4 and local6 as FQDN suffix in MDNS alias to specify the
>>>>> candidate-address type so that correct DNS request can be issued.
>>>>>
>>>>> 2. A lot (if not most) SDP/ICE implementations do no support parsing
>>>>> FQDN in candidate-address or c= line. This might create interop problems
>>>>> since RFC 5245 specified that candidate-address is an IP Address.
>>>>>
>>>>> Regards,
>>>>> _____________
>>>>> Roman Shpount
>>>>>
>>>>>
>>>>

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

<div dir=3D"ltr">This has all been discussed at length in rtcweb and I don&=
#39;t think any significant changes are needed, although I tend to think th=
at we should restore the removed FQDN text from mmusic-ice-sip-sdp, which i=
s the only thing not in alignment at this point in time.<div><br></div><div=
><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Fri, Feb 1, 2019 at 11:18 AM Roman Shpount &lt;<a href=3D"mai=
lto:roman@telurix.com">roman@telurix.com</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">M=
ost likely mDNS draft will need to update <span style=3D"color:rgb(0,0,0)">=
RFC 8445</span>=C2=A0to specify how ICE nomination procedures are modified,=
 when mDNS is used as candidate-address.=C2=A0</div><div dir=3D"ltr"><br></=
div><div dir=3D"ltr">As far as mmusic-ice-sip-sdp is concerned, one option =
would be to allow FQDN as candidate-address. The guidance for handling FQDN=
 in candidate-address should be updated from RFC 5245 and should specify th=
at FQDN names should be ignored. mDNS ICE draft then will update ice-sip-sd=
p and specify that mDNS FQDN should be handled according the procedures of =
this draft.</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Another option=
, which I think word work better with existing specifications is to add a n=
ew candidate type -- mdns. This way, instead of magic DNS suffix, candidate=
 type will be used to determine that this candidate should be handled diffe=
rently. I do not think MDNS candidates can be used for anything except host=
 candidates, so making then a special candidate type might be the least pai=
nful option. It might even make sense to make separate types for IPv4 and I=
Pv6 MDNS candidates which would save a DNS query for each candidate.</div><=
div dir=3D"ltr"><br></div><div dir=3D"ltr">Regards,<br clear=3D"all"><div><=
div dir=3D"ltr" class=3D"gmail-m_8846655286234283596gmail_signature">______=
_______<br>Roman Shpount</div></div><br></div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 1, 2019 at 12:39 PM Jus=
tin Uberti &lt;<a href=3D"mailto:juberti@google.com" target=3D"_blank">jube=
rti@google.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div dir=3D"ltr">I understand there were questions about the =
general case (e.g. regular DNS names), but how do we plan to reconcile this=
 removal with the need for mDNS hostnames?</div><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 1, 2019 at 9:09 AM Ro=
man Shpount &lt;<a href=3D"mailto:roman@telurix.com" target=3D"_blank">roma=
n@telurix.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Hi Justin,<=
div><br></div><div>I agree regarding #1 in theory, even though in practice =
a lot of (most) devices will not accept FQDN in either c=3D or ICE candidat=
e.</div><div><br></div><div>Regarding #2, mmusic-ice-sip-sdp was updated (<=
a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-24#sect=
ion-4.1" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-mmusic-ic=
e-sip-sdp-24#section-4.1</a>):</div><div><br></div><div><pre class=3D"gmail=
-m_8846655286234283596gmail-m_-2298128030139745895gmail-m_-4390259510233163=
330gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom=
:0px;break-before:page;color:rgb(0,0,0)">   &lt;connection-address&gt;:  is=
 taken from <a href=3D"https://tools.ietf.org/html/rfc4566" target=3D"_blan=
k">RFC 4566</a> [<a href=3D"https://tools.ietf.org/html/rfc4566" title=3D"&=
quot;SDP: Session Description Protocol&quot;" target=3D"_blank">RFC4566</a>=
].  It is the
      IP address of the candidate.  When parsing this field, an agent
      can differentiate an IPv4 address and an IPv6 address by presence
      of a colon in its value -- the presence of a colon indicates IPv6.
      An agent MUST ignore candidate lines that include candidates with
      IP address versions that are not supported or recognized.</pre><pre c=
lass=3D"gmail-m_8846655286234283596gmail-m_-2298128030139745895gmail-m_-439=
0259510233163330gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;=
margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre>Specificall=
y, support for FQDN names there was removed due to=C2=A0<span style=3D"colo=
r:rgb(0,0,0)">RFC 8445 implementation issues. I believe=C2=A0</span><font c=
olor=3D"#000000">Simon Perreault suggested this change.</font></div><div><f=
ont color=3D"#000000"><br></font></div><div><font color=3D"#000000">Regards=
,<br></font><div><div dir=3D"ltr" class=3D"gmail-m_8846655286234283596gmail=
-m_-2298128030139745895gmail-m_-4390259510233163330gmail_signature">_______=
______<br>Roman Shpount</div></div><br></div></div></div></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 1, 201=
9 at 12:02 AM Justin Uberti &lt;<a href=3D"mailto:juberti@google.com" targe=
t=3D"_blank">juberti@google.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div>My =
recommendation here would be that we do c=3DIN IP6 3557773f-5f01-46a4-aa14-=
54ab35b3d778.local, with either IP4 or IP6 depending on which type of addre=
ss is being wrapped.</div><div><br></div><div>Re #1:=C2=A0RFC 4566 seems to=
 indicate you can use either IP4 or IP6 for FQDN in the c=3D line.</div><di=
v><br></div><div><pre class=3D"gmail-m_8846655286234283596gmail-m_-22981280=
30139745895gmail-m_-4390259510233163330gmail-m_7058075087377128197gmail-new=
page" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-b=
efore:page;color:rgb(0,0,0)">     unicast-address =3D     IP4-address / IP6=
-address / FQDN / extn-addr
</pre></div><div><br></div>Re #2: Quoth <a href=3D"https://tools.ietf.org/h=
tml/rfc5245#section-15.1" target=3D"_blank">5245</a>:<div><br></div><div><p=
re class=3D"gmail-m_8846655286234283596gmail-m_-2298128030139745895gmail-m_=
-4390259510233163330gmail-m_7058075087377128197gmail-newpage" style=3D"font=
-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rg=
b(0,0,0)">   &lt;connection-address&gt;:  is taken from <a href=3D"https://=
tools.ietf.org/html/rfc4566" target=3D"_blank">RFC 4566</a> [<a href=3D"htt=
ps://tools.ietf.org/html/rfc4566" title=3D"&quot;SDP: Session Description P=
rotocol&quot;" target=3D"_blank">RFC4566</a>].  It is the
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and <b>fully qualified domain names (FQDNs).</b>  When par=
sing
      this field, an agent can differentiate an IPv4 address and an IPv6
</pre><pre class=3D"gmail-m_8846655286234283596gmail-m_-2298128030139745895=
gmail-m_-4390259510233163330gmail-m_7058075087377128197gmail-newpage" style=
=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;=
color:rgb(0,0,0)">      address by presence of a colon in its value - the p=
resence of a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=3Dcandidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.
</pre><pre class=3D"gmail-m_8846655286234283596gmail-m_-2298128030139745895=
gmail-m_-4390259510233163330gmail-m_7058075087377128197gmail-newpage" style=
=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;=
color:rgb(0,0,0)"><br></pre><pre class=3D"gmail-m_8846655286234283596gmail-=
m_-2298128030139745895gmail-m_-4390259510233163330gmail-m_70580750873771281=
97gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:=
0px;break-before:page;color:rgb(0,0,0)"><br></pre><pre class=3D"gmail-m_884=
6655286234283596gmail-m_-2298128030139745895gmail-m_-4390259510233163330gma=
il-m_7058075087377128197gmail-newpage" style=3D"font-size:13.3333px;margin-=
top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><pr=
e class=3D"gmail-m_8846655286234283596gmail-m_-2298128030139745895gmail-m_-=
4390259510233163330gmail-m_7058075087377128197gmail-newpage" style=3D"font-=
size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb=
(0,0,0)"><br></pre><pre class=3D"gmail-m_8846655286234283596gmail-m_-229812=
8030139745895gmail-m_-4390259510233163330gmail-m_7058075087377128197gmail-n=
ewpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break=
-before:page;color:rgb(0,0,0)"><br></pre><pre class=3D"gmail-m_884665528623=
4283596gmail-m_-2298128030139745895gmail-m_-4390259510233163330gmail-m_7058=
075087377128197gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;m=
argin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><br class=3D=
"gmail-m_8846655286234283596gmail-m_-2298128030139745895gmail-m_-4390259510=
233163330gmail-m_7058075087377128197gmail-Apple-interchange-newline"></div>=
</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Thu, Jan 31, 2019 at 8:43 PM Roman Shpount &lt;<a href=3D"mailto:r=
oman@telurix.com" target=3D"_blank">roman@telurix.com</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div =
dir=3D"ltr"><div dir=3D"ltr"><div><div dir=3D"ltr" class=3D"gmail-m_8846655=
286234283596gmail-m_-2298128030139745895gmail-m_-4390259510233163330gmail-m=
_7058075087377128197gmail-m_4773857553044000712gmail-m_8367249769720427912g=
mail_signature">On Thu, Jan 31, 2019 at 10:58 PM Justin Uberti &lt;<a href=
=3D"mailto:juberti@google.com" target=3D"_blank">juberti@google.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 rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=
=3D"ltr">We can however all agree that &quot;c=3DIN IP6&quot; is busted:=C2=
=A0<a href=3D"https://bugs.chromium.org/p/chromium/issues/detail?id=3D92730=
9" target=3D"_blank">https://bugs.chromium.org/p/chromium/issues/detail?id=
=3D927309</a></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 rg=
b(204,204,204);padding-left:1ex"><div class=3D"gmail_quote"><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"><br></blockquote></div></blockquote></di=
v></blockquote><div><br></div><div>I guess one way to interpret this that e=
ach address should have a MDNS alias. So, if you are dealing with dual stac=
k host, it should provide two MDNS candidates, one of which is IPv4 and ano=
ther IPv6. The c=3D line should specify FQDN for one of those candidates an=
d specify the type (IP4 or IP6).</div><div><br></div><div>There are two pro=
blems:</div><div><br></div><div>1. There is no way to know which address ty=
pe is in the candidate-address when FQDN is used there. Guidance in ice-sip=
-sdp is talking about the presence of column in IP6 address, but this defin=
itely does not apply to FQDN. It would&#39;ve been better to specify someth=
ing like local4 and local6 as FQDN suffix in MDNS alias to specify the cand=
idate-address type so that correct DNS request can be issued.</div><div><br=
></div><div>2. A lot (if not most) SDP/ICE implementations do no support pa=
rsing FQDN in candidate-address or c=3D line. This might create interop pro=
blems since RFC 5245 specified that candidate-address is an IP Address.</di=
v><div><br></div><div>Regards,</div>_____________<br>Roman Shpount<br class=
=3D"gmail-m_8846655286234283596gmail-m_-2298128030139745895gmail-m_-4390259=
510233163330gmail-m_7058075087377128197gmail-m_4773857553044000712gmail-m_8=
367249769720427912gmail-Apple-interchange-newline"><div>=C2=A0</div></div><=
/div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div></div>
</blockquote></div>

--000000000000224ef80580da4c45--


From nobody Fri Feb  1 11:58:43 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 2DF8F130E89 for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 11:58:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.853
X-Spam-Level: 
X-Spam-Status: No, score=-8.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=OOlQ1A1X; dkim=pass (1024-bit key) header.d=ericsson.com header.b=PlgKUAmF
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 FzXMxLejUgRF for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 11:58:39 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 7BBD9130E84 for <mmusic@ietf.org>; Fri,  1 Feb 2019 11:58:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/relaxed;  q=dns/txt; i=@ericsson.com; t=1549051117; x=1551643117; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=J3o/pbjF5l516ONCZLveyTI7s85W/Wo1GCrOx6Um6Jw=; b=OOlQ1A1XjaZAs7R5C1sjZ0OyojvR1EpCJ9JWHQqLenLpsGx3GXDSaBwWmXrMemmS owwCGV1lTC19veE80id7mz0l8zz/m8Pw0tl3s7HJqJxNPda7ai3JSCTNeuJYXANi ouCv5/JwmrjxzZHMIajdycE8AOwXBSpYoTce83pg3yc=;
X-AuditID: c1b4fb3a-5c9c29e00000672c-29-5c54a4ed7c99
Received: from ESESBMB502.ericsson.se (Unknown_Domain [153.88.183.115]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id A4.14.26412.DE4A45C5; Fri,  1 Feb 2019 20:58:37 +0100 (CET)
Received: from ESESBMB501.ericsson.se (153.88.183.168) by ESESBMB502.ericsson.se (153.88.183.169) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 1 Feb 2019 20:58:37 +0100
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESBMB501.ericsson.se (153.88.183.168) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Fri, 1 Feb 2019 20:58:37 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=J3o/pbjF5l516ONCZLveyTI7s85W/Wo1GCrOx6Um6Jw=; b=PlgKUAmFDSStjmne8Z9h8QV5Ght34ahUkQYnHv8tRDup1GFdmhtcrMywmzZHAfEQ4Vdvt8fUMnqIjekJymgz+VsPd10C1Y8wA55IRiOvUZhGudvG9BKmaKXbgoTGluSp6gyROYdYe47lA/MnUiGMtbv07q9e+rExqun/Q2s4WWg=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB4233.eurprd07.prod.outlook.com (20.176.166.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1580.14; Fri, 1 Feb 2019 19:58:35 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0%4]) with mapi id 15.20.1601.013; Fri, 1 Feb 2019 19:58:35 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>, Justin Uberti <juberti@google.com>
CC: Simon Perreault <sperreault@jive.com>, "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Thread-Topic: [rtcweb] [MMUSIC] What goes into c= line address when FQDN is used for the default candidate?
Thread-Index: AQHUulU2uFx8SsiiZk68wi8iILBKkKXLUQeAgAAK5Co=
Date: Fri, 1 Feb 2019 19:58:35 +0000
Message-ID: <HE1PR07MB3161471773206C16258150E493920@HE1PR07MB3161.eurprd07.prod.outlook.com>
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com>, <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com>
In-Reply-To: <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [37.136.56.89]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR07MB4233; 6:kukI0wDWCyB7D0HRwoC1oPBDsrzWf4iEXcdc5D+o6QpWn2YCF0RyJeq9F0yoxiUW9wGWdO1TVHd0O8t869YsX1NsRSqBq2Uk4V7twEdNgCm+3rSea8iF9yQSDW5YVgt+c+suNoRf0r+dn3pPQ29eDTLcm/oUQX+bJMskOA+oO7CRuAFZbgTn7a4DIasQe1ZeSzKmljzToNj0IMP7YQGpcqTBtWaeKn6MH2s/ToMaSTnTfsebvMU1qCZ6ufRUiYhIV1z9I7+9EUTzaR+7rNaJMRTggCSmCICug1gswF+g+XvfpH3KXQ7i3U31D6pHIGz4xEhs8iI/nbEdZ9N8ZZDKvMo1cEJx99r07aw0k7nGlD1cYqhtSGfAi5m97ZJH4ouhz0nLEPIGBTnc0Dk7Q5VWXdLAeFMC6uH7CMYDgeByZH8fPwNJhTTyonKi0oPZvT/8iZ4TMW99zOV64hmhWUr4Zg==; 5:dvuO94EIdYcZk8BDz5wXWVr544noQZlafkIe7JIDfPd7ULTbODTtJrmppnnNiexDojVUYB0UUiuhNobugPj/QfsYFmapKByhiU3co0ipGgWQSZh27DBXQC5bHe5YXczxG0lLt9qf9p24B6C4uTaCnwwbiCFYaSeRfojcfQUrDCtVv7LnWC97ojBdj2WDhbVg8X72YtuaJzGMpcyPIcUQaQ==; 7:uupugpHlMbMnb1ZMnc58LySI5Sdq7VPJjANwmDV/VLIO8JfgRzFcWhHkkcdLDrHsr6ckoRfUhxHz1WvHwXNawzOa2I2s1pweDi1+WgzRQm9cd9Yrwr0kw8xQsQ05kdKyXxE1E8lTd1GiISFBxXcoAQ==
x-ms-office365-filtering-correlation-id: 4a6ecbc3-7be1-4c50-ca3b-08d6887fa6b0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(2017052603328)(7153060)(7193020); SRVR:HE1PR07MB4233; 
x-ms-traffictypediagnostic: HE1PR07MB4233:
x-microsoft-antispam-prvs: <HE1PR07MB4233B05EF10AA2B3F6BBF75893920@HE1PR07MB4233.eurprd07.prod.outlook.com>
x-forefront-prvs: 09352FD734
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(396003)(366004)(136003)(39860400002)(189003)(199004)(476003)(558084003)(6246003)(7736002)(26005)(74316002)(2906002)(53936002)(99286004)(486006)(186003)(102836004)(68736007)(86362001)(6606003)(316002)(71190400001)(110136005)(8936002)(8676002)(81156014)(7696005)(446003)(81166006)(11346002)(19627405001)(44832011)(71200400001)(54906003)(66066001)(6506007)(76176011)(256004)(97736004)(54896002)(105586002)(14444005)(106356001)(33656002)(9686003)(55016002)(4326008)(14454004)(25786009)(6436002)(3846002)(6116002)(478600001)(93886005)(229853002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB4233; 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: cJ5E2jgRFvbf2mONq2n31HGFgQY2DReQ4mwvcp93bSWS+bCPVK9XAWNg0NiGnFDtF6cY8FQRFyjLLrlSbAsx9xGfqnHMZ1qO9deOMVeJjVB5Pz/x7cQPokb7f+f058SjnwfjrxSLF9GAzoi+UzjVtJx5Pp2Uw8b7QgpGDg2LlGl930y9beUEnh94uj5Wn0SwiK4ep1rNNNHopuS+0dM9s5ExOWqkuJ149NL73UOfAlYpEbcKeUiF2oMEz6yFENBb2IlUkWl96Do1iroKbKKB5KemeJdj7IeE+SnNkqUcz183JhnaCFjM2TmynJWfWgMuEju9LY1Y56kaEc2eUIrnXppU3Ow9PXN7knt+WTWWADrFI6NmhoBggAiiKSRdOax9N9vk7f1XraDvw/FqF35DAeoRuVmwkHmH0WoqF3XzhZo=
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB3161471773206C16258150E493920HE1PR07MB3161eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4a6ecbc3-7be1-4c50-ca3b-08d6887fa6b0
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2019 19:58:35.6650 (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-Transport-CrossTenantHeadersStamped: HE1PR07MB4233
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Se0hTYRjG+845247S4tu8vXjpMiLIW2oJy0LKImaQJmhFDGrkSc3b2FHJ /pLKigk1UVPX0kRTFLUUQ8H7jFymqKFpoqJ5y6ykVPKSx9zOAv/7Pc/zvt/7vvDRpPSDwJmO SUhiNAmqOJnQlsq/Us96/SgJV/pUTnjK3+RI5TllU5Q8ry+HlFdxD0XyoYEI+bwp5ZRQkdW6 Qipe1CYrSkrWCAVnmCEVI9nqi4KrticjmbiYFEZzJPC6bXRzm55QZzrcNm0NkWmoW6pFNjTg Y2Do6BRqkS0txW8RPDYZrGIFQefWKsmLYgKGTWkWQWEdCZNT1dayLALaNloIXkwi4PSzSIto WojlkMF5mIfY42D4vlZs6SaxDkFXfQsyB3Y4DtZn9SRfFA81Tz5ZOQC6ezcsTOGDUF6gFZpZ jJUwkPvVOvmVACrXtIQ5sMFhsPBIZ2lA2BH+dFVafBI7wch0IcGfiqGkqZfk2QHmpzgBX6+C 1ooJq78fOsenEc9u8LEwA5mHAb4rgtnFaSEfXIAxrpfgg88IXg8bKD5wB11Tg/WlWCi+12ht cIWG1TER3zAngH79imUlKWagrCod6ZCnfse2PCdCUfUE0lvOlsD7/GmK971hOCdbyLMHlBYt kDx7QR5npHb6L5CoAjmwDMvGR/n5eTOamBssm5jgncAk1aLtL9ZetxHQgNrnThsRppFst/h4 VrhSKlClsKnxRgQ0KbMXB93atsSRqtQ7jCbxmiY5jmGNyIWmZE7iv1KJUoqjVElMLMOoGc3/ lKBtnNOQa83PhpfP60LnlHYd+0K4hVx/iYjzkeytcJlp/L30bCikx3+5LEI8ITyq3rN5Ymr0 zPkCf8lg4HLGgXeGkaXSgc30B/mbN4M6ahzvfxsL9j0XVt7mf7b7cFNov6HwV0TmF/e0S83G XbmXF0fHI3pzW7bGetZj+rRINUg/PeSmTjbJKDZa5etOaljVPyJ1qoJeAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/g3i5F5qisA_MUIzUxtFR2oCHaI8>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 01 Feb 2019 19:58:41 -0000

--_000_HE1PR07MB3161471773206C16258150E493920HE1PR07MB3161eurp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,



> Most likely mDNS draft will need to update RFC
> 8445 to specify how ICE nomination procedures are
> modified, when mDNS is used as candidate-
> address.

What part of 8445 would need to be updated?

Regards,

Christer

--_000_HE1PR07MB3161471773206C16258150E493920HE1PR07MB3161eurp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p style=3D"margin-top:0;margin-bottom:0">Hi,</p>
<p style=3D"margin-top:0;margin-bottom:0">&nbsp;</p>
<div style=3D"color: rgb(0, 0, 0);">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"></div>
<div>
<div dir=3D"ltr">
<div dir=3D"ltr">&gt; Most likely mDNS draft will need to update <span styl=
e=3D"color:rgb(0,0,0)">
RFC&nbsp;</span></div>
<div dir=3D"ltr"><span style=3D"color:rgb(0,0,0)">&gt; 8445</span>&nbsp;to =
specify how ICE nomination procedures are</div>
<div dir=3D"ltr">&gt; modified, when mDNS is used as candidate-</div>
<div dir=3D"ltr">&gt; address.&nbsp;</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">What part of 8445 would need to be updated?</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">Regards,</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">Christer<br>
</div>
<div class=3D"x_gmail_quote">
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div class=3D"x_gmail_quote">
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div class=3D"x_gmail_quote">
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div class=3D"x_gmail_quote">
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div dir=3D"ltr">
<div dir=3D"ltr">
<div class=3D"x_gmail_quote"></div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_HE1PR07MB3161471773206C16258150E493920HE1PR07MB3161eurp_--


From nobody Fri Feb  1 12:09:20 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 EA93B130E89 for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 12:09:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.03
X-Spam-Level: 
X-Spam-Status: No, score=-2.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 Dbpbek8_WDVQ for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 12:09:16 -0800 (PST)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 B9DE1128B01 for <mmusic@ietf.org>; Fri,  1 Feb 2019 12:09:16 -0800 (PST)
Received: by mail-pl1-x62a.google.com with SMTP id 101so3747901pld.6 for <mmusic@ietf.org>; Fri, 01 Feb 2019 12:09:16 -0800 (PST)
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=NjeNGy85lYMwb0k0Fdoc9bqfM9ku9gfQVC041YICdr8=; b=yPklsQXH3feVNejAS3Pzy+Zgn6UNx74ce6DayhFRZDw+SbZxCace34Da4jy/+XI2GG mw/97FwCgfTjmlfUqOGGVa06S9KF7vWzfM/cQApBLEQobqpsMBcc3UFjsC8kG2dGx3f7 18Fk3ZpUfTsVv171IMMgr0phwzdouan5Ba5JYUTrJPXtznsKl6xLEzot9gnAhKP2L949 Lr7JuoDHUtU7d+UdXSVBqiSsqMw4QzmT++CSP77TIXDLe8lKqgnWv6qAAGlE7Zp5BfNG YZQJmrGC7t1O9/wx/Y/uNOyv6ftFLyO6MmpZu2Bp3dqoSvJfAAn51Sh98hyZNb/wHkkt 38cg==
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=NjeNGy85lYMwb0k0Fdoc9bqfM9ku9gfQVC041YICdr8=; b=uNJ7GkXqtSus0RDAZFmEtupQa3cByjbVeZzcfnuMdEJC+W51/YtH0VnVU2SA5te3Tb 2DFS0Qsr47zyYCp8UOFeZ6BwtYgHFCAseD7dVzoRSmNYU/thvrwWAhnoUDiT2I6ZHZxR 5bNFZRzzDHUV/TdZIY12hdGuBtb1FEd4wJohGxKH6H6uGqDPFFk1zeapKqwjRBI4mWLN /eFd+KxJizMmuBCuuDLf1uXL8sRnx5+p1EBamFSmGHjmSM2tj4nZPgrNRrTkUT5ITtbp 7KhXeTUS8q+ONx7LOa5S4uECNDlnNhXJ5viPCW3Tvm1XBZRgZAwQbxwcvJcs7Ok/VRgd s4pg==
X-Gm-Message-State: AJcUukdKlmBMvf8pvzfohhOZOI2Rqrf7A8XYBHPPy2y3lD3BnKwboR6w 3PkbfECsMXTSnxheQjDucYryU7H73SU=
X-Google-Smtp-Source: ALg8bN7jP+UF/+sEYfZLQ7kPxDKg7ORNB0l9e+I/DriHDRYSFiavIkTB3wZ5uAk9Zyo1DA2E480RYw==
X-Received: by 2002:a17:902:3283:: with SMTP id z3mr41613044plb.76.1549051756275;  Fri, 01 Feb 2019 12:09:16 -0800 (PST)
Received: from mail-pg1-f177.google.com (mail-pg1-f177.google.com. [209.85.215.177]) by smtp.gmail.com with ESMTPSA id g26sm10281362pfh.61.2019.02.01.12.09.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Feb 2019 12:09:15 -0800 (PST)
Received: by mail-pg1-f177.google.com with SMTP id t13so3414572pgr.11; Fri, 01 Feb 2019 12:09:15 -0800 (PST)
X-Received: by 2002:a63:b4c:: with SMTP id a12mr3634101pgl.131.1549051755149;  Fri, 01 Feb 2019 12:09:15 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <HE1PR07MB3161471773206C16258150E493920@HE1PR07MB3161.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB3161471773206C16258150E493920@HE1PR07MB3161.eurprd07.prod.outlook.com>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 1 Feb 2019 15:09:05 -0500
X-Gmail-Original-Message-ID: <CAD5OKxuMOhVAh=Q=BGChP8vU5oQ8AwaoXn5qqctdv+ky6g0Xpw@mail.gmail.com>
Message-ID: <CAD5OKxuMOhVAh=Q=BGChP8vU5oQ8AwaoXn5qqctdv+ky6g0Xpw@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Justin Uberti <juberti@google.com>, Simon Perreault <sperreault@jive.com>,  "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009ac2140580dab76f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/aqI4AxGA_iPxzvs8U9r94rU1fa4>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 01 Feb 2019 20:09:19 -0000

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

On Fri, Feb 1, 2019 at 2:58 PM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> > Most likely mDNS draft will need to update RFC
> > 8445 to specify how ICE nomination procedures are
> > modified, when mDNS is used as candidate-
> > address.
>
> What part of 8445 would need to be updated?
>
>
Currently RFC 8445 specifies that candidates are only IP addresses and not an
FQDN:

   2.1.  Gathering Candidates

   In order to execute ICE, an ICE agent identifies and gathers one or
   more address candidates.  A candidate has a transport address -- a
   combination of IP address and port for a particular transport
   protocol (with only UDP specified here).  There are different types
   of candidates; some are derived from physical or logical network
   interfaces, and others are discoverable via STUN and TURN.

In case of mDNS, candidate is a FQDN name. So when gathering candidates,
DNS query will need to be performed and its result added to the candidate
list. Also, I am not 100% sure, but I think mDNS can resolve to either
IPv4/IPv6 or both addresses. So, single mDNS candidate can result in two
actual ICE candidates. All of this looks like RFC 8445 update.

Regards,
_____________
Roman Shpount

--0000000000009ac2140580dab76f
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 Fri, Feb 1, 2019 at 2:58 PM Ch=
rister Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">chris=
ter.holmberg@ericsson.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 dir=3D"ltr">
<div id=3D"gmail-m_274926659898176368divtagdefaultwrapper" style=3D"font-si=
ze:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif" dir=3D"l=
tr">
<p style=3D"margin-top:0px;margin-bottom:0px"><span style=3D"font-size:12pt=
">&gt; Most likely mDNS draft will need to update </span><span style=3D"fon=
t-size:12pt">
RFC=C2=A0</span><br></p><div style=3D"color:rgb(0,0,0)"><div><div dir=3D"lt=
r">
<div dir=3D"ltr"><span style=3D"color:rgb(0,0,0)">&gt; 8445</span>=C2=A0to =
specify how ICE nomination procedures are</div>
<div dir=3D"ltr">&gt; modified, when mDNS is used as candidate-</div>
<div dir=3D"ltr">&gt; address.=C2=A0</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">What part of 8445 would need to be updated?</div>
<div dir=3D"ltr"><br></div></div></div></div></div></div></blockquote><div>=
<br></div><div>Currently RFC 8445 specifies that candidates are only IP add=
resses and not=C2=A0<span style=3D"color:rgb(0,0,0)">an FQDN:</span></div><=
div><br style=3D"color:rgb(0,0,0)"><span style=3D"color:rgb(0,0,0)">=C2=A0 =
=C2=A02.1.=C2=A0 Gathering Candidates</span><br style=3D"color:rgb(0,0,0)">=
<br style=3D"color:rgb(0,0,0)"><span style=3D"color:rgb(0,0,0)">=C2=A0 =C2=
=A0In order to execute ICE, an ICE agent identifies and gathers one or</spa=
n><br style=3D"color:rgb(0,0,0)"><span style=3D"color:rgb(0,0,0)">=C2=A0 =
=C2=A0more address candidates.=C2=A0 A candidate has a transport address --=
 a</span><br style=3D"color:rgb(0,0,0)"><span style=3D"color:rgb(0,0,0)">=
=C2=A0 =C2=A0combination of IP address and port for a particular transport<=
/span><br style=3D"color:rgb(0,0,0)"><span style=3D"color:rgb(0,0,0)">=C2=
=A0 =C2=A0protocol (with only UDP specified here).=C2=A0 There are differen=
t types</span><br style=3D"color:rgb(0,0,0)"><span style=3D"color:rgb(0,0,0=
)">=C2=A0 =C2=A0of candidates; some are derived from physical or logical ne=
twork</span><br style=3D"color:rgb(0,0,0)"><span style=3D"color:rgb(0,0,0)"=
>=C2=A0 =C2=A0interfaces, and others are discoverable via STUN and TURN.</s=
pan>=C2=A0=C2=A0<br></div><div class=3D"gmail_quote"><br></div><div class=
=3D"gmail_quote">In case of mDNS, candidate is a FQDN name. So when gatheri=
ng candidates, DNS query will need to be performed and its result added to =
the candidate list. Also, I am not 100% sure, but I think mDNS can resolve =
to either IPv4/IPv6 or both addresses. So, single mDNS candidate can result=
 in two actual ICE candidates. All of this looks like RFC 8445 update.</div=
><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">Regards,</=
div>_____________<br>Roman Shpount<br class=3D"gmail-Apple-interchange-newl=
ine"><div>=C2=A0</div></div></div>

--0000000000009ac2140580dab76f--


From nobody Fri Feb  1 12:22:38 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 D25A7130E6A for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 12:22:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.03
X-Spam-Level: 
X-Spam-Status: No, score=-2.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 dEgHr42nHdsX for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 12:22:27 -0800 (PST)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 C8A48128B01 for <mmusic@ietf.org>; Fri,  1 Feb 2019 12:22:27 -0800 (PST)
Received: by mail-pg1-x52d.google.com with SMTP id z11so3458637pgu.0 for <mmusic@ietf.org>; Fri, 01 Feb 2019 12:22:27 -0800 (PST)
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=ZxiszQvP8ZFDDvqn+Bf1lIlGwm+vjhJUim4CvEgEaHQ=; b=P6UXgvFmxnhUSbYRiOimooOaR7ScKbVThYvHTEQ8rvCzm2DbLVxg7Wkjda9Mtxnoqp oTjCBJcnBEBqCQNl3IdzICTyJk3Dvk3Cqrg42O4BRrgxD00dQb9iFS7xZmgT7ZwqCDRr 2Ron1C0Smmx0aoeUWRH1sVsPh4xrRlSf2VlnbMyzHGSXmyr5J8ah6EqyyiVmhDoB39CT v4v6y5+CGogOOHG69VD4qwwRGkC6Uy7vQSw4u+k3/i/dn3dcXWpNwWFPfPDQuLjQM9QX xP+B6sgC6DQbYNQtq+S/PJVOSUZLXWamRqTqkEGcROf4QvgUptDceiQgH7xrcCTxolxI NTJQ==
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=ZxiszQvP8ZFDDvqn+Bf1lIlGwm+vjhJUim4CvEgEaHQ=; b=aXaox2lTJvHzXgmxGp/UBI3r6fIZANv0hDJvlYTgUEr+SfHszT7zUTFpwo0UAewuVR LFilsKmlQwzTfjfiA1WhN4Hz/hVaToOOXuOL+fHLGF4RFdEwQ7dEHcw+NVXK/ep2mBJb 7HZ9h23/7ldLcE2AVku5gdF4jE44WU1kjMJi58zzRqtCZXph00b3Gv/tXmH/n1NKkseY VQMaNwC863Ra1PPaD5UZnHz8+Rj9cIerOGj1qc+qrg38/YFq2YgVEsTwgZ2mlrF/eY7u /I/YKPgszoqob2EtSOZ7m3EznKMujzQF+s/IjYXgY+7DBtRYmJpOnp8BathGk9YvME8k T/Ew==
X-Gm-Message-State: AJcUukfqQViBwmxxeQSAIKGmVFgi9h5oRdn2r8qT+rL58aWTedAqF64H L4/raDa9gKF+ZoL8pV49jEiuCg==
X-Google-Smtp-Source: ALg8bN5hpoGCwNe0h9Fsle3nr2V7nrqY64s6o6KVRM23P0HC7lRWDSPpQjfvf+bZ2kMIaetHnK6hsQ==
X-Received: by 2002:a63:1f1c:: with SMTP id f28mr37082470pgf.193.1549052547104;  Fri, 01 Feb 2019 12:22:27 -0800 (PST)
Received: from mail-pg1-f172.google.com (mail-pg1-f172.google.com. [209.85.215.172]) by smtp.gmail.com with ESMTPSA id c13sm10673219pfo.121.2019.02.01.12.22.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Feb 2019 12:22:26 -0800 (PST)
Received: by mail-pg1-f172.google.com with SMTP id z11so3458617pgu.0; Fri, 01 Feb 2019 12:22:26 -0800 (PST)
X-Received: by 2002:a63:b4c:: with SMTP id a12mr3678195pgl.131.1549052545848;  Fri, 01 Feb 2019 12:22:25 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com>
In-Reply-To: <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 1 Feb 2019 15:22:15 -0500
X-Gmail-Original-Message-ID: <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com>
Message-ID: <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>, Simon Perreault <sperreault@jive.com>
Content-Type: multipart/alternative; boundary="000000000000bbdaa90580dae688"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/4_rhQXpbve9aibxOq1OdltBkgH8>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 01 Feb 2019 20:22:31 -0000

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

On Fri, Feb 1, 2019 at 2:39 PM Justin Uberti <juberti@google.com> wrote:

> This has all been discussed at length in rtcweb and I don't think any
> significant changes are needed, although I tend to think that we should
> restore the removed FQDN text from mmusic-ice-sip-sdp, which is the only
> thing not in alignment at this point in time.
>

I agree that FQDN should be put back into connection-address definition,
but  the portion which talks about handling it is completely broken.

Quoting 5245 <https://tools.ietf.org/html/rfc5245#section-15.1>:

   <connection-address>:  is taken from RFC 4566
<https://tools.ietf.org/html/rfc4566> [RFC4566
<https://tools.ietf.org/html/rfc4566>].  It is the
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and *fully qualified domain names (FQDNs).*  When parsing
      this field, an agent can differentiate an IPv4 address and an IPv6

      address by presence of a colon in its value - the presence of a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=candidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.


I think it was discussed in quite a detail why using a random DNS
resolution result is not going to work here.

The only options we have here are:

a. Fix FQDN connection address handling. Probably the most logical way of
dealing with this would be to specify that candidate with FQDN should be
converted as a result of DNS resolution into multiple candidates, with each
candidate corresponding to A or AAAA record in DNS query result. We will
also need to specify how FQDN candidate gets applied to c= line address.
Something that says IN IP4 FQDN, if any A records exist for this DNS name
and IN IP6 FQDN if only AAAA records exist. Once candidate is nominated,
address family in c= line should match address family used for
communications. This will definitely require a lot more work and discussion.

b. Specify that FQDN connection addresses should be ignored until their
handling is defined in a future specification. This seems easy and only
requires a sentence or two to fix.

Regards,
_____________
Roman Shpount

>

--000000000000bbdaa90580dae688
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 Fri, Feb 1, 2019 at 2:39 PM Ju=
stin Uberti &lt;<a href=3D"mailto:juberti@google.com">juberti@google.com</a=
>&gt; wrote:<br></div></div></div><div class=3D"gmail_quote"><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">This has all been disc=
ussed at length in rtcweb and I don&#39;t think any significant changes are=
 needed, although I tend to think that we should restore the removed FQDN t=
ext from mmusic-ice-sip-sdp, which is the only thing not in alignment at th=
is point in time.</div></blockquote><div><br></div><div>I agree that FQDN s=
hould be put back into connection-address definition, but=C2=A0 the portion=
 which talks about handling it is completely broken.</div><div><br></div><d=
iv>Quoting=C2=A0<a href=3D"https://tools.ietf.org/html/rfc5245#section-15.1=
" target=3D"_blank">5245</a><span style=3D"color:rgb(0,0,0)">:</span></div>=
<div style=3D""><pre class=3D"gmail-m_7058075087377128197gmail-newpage" sty=
le=3D"color:rgb(0,0,0);white-space:pre-wrap;font-size:13.3333px;margin-top:=
0px;margin-bottom:0px;break-before:page">   &lt;connection-address&gt;:  is=
 taken from <a href=3D"https://tools.ietf.org/html/rfc4566" target=3D"_blan=
k">RFC 4566</a> [<a href=3D"https://tools.ietf.org/html/rfc4566" title=3D"&=
quot;SDP: Session Description Protocol&quot;" target=3D"_blank">RFC4566</a>=
].  It is the
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and <b>fully qualified domain names (FQDNs).</b>  When par=
sing
      this field, an agent can differentiate an IPv4 address and an IPv6
</pre><pre class=3D"gmail-m_7058075087377128197gmail-newpage" style=3D"colo=
r:rgb(0,0,0);white-space:pre-wrap;font-size:13.3333px;margin-top:0px;margin=
-bottom:0px;break-before:page">      address by presence of a colon in its =
value - the presence of a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=3Dcandidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.
</pre><pre class=3D"gmail-m_7058075087377128197gmail-newpage" style=3D"colo=
r:rgb(0,0,0);white-space:pre-wrap;font-size:13.3333px;margin-top:0px;margin=
-bottom:0px;break-before:page"><br></pre>I think it was discussed in quite =
a detail why using a random DNS resolution result is not going to work here=
.</div><div style=3D""><br></div><div style=3D"">The only options we have h=
ere are:</div><div style=3D""><br></div><div style=3D"">a. Fix FQDN connect=
ion address handling. Probably the most logical way of dealing with this wo=
uld be to specify that candidate with FQDN should be converted as a result =
of DNS resolution into multiple candidates, with each candidate correspondi=
ng to A or AAAA record in DNS query result. We will also need to specify ho=
w FQDN candidate gets applied to c=3D line address. Something that says IN =
IP4 FQDN, if any A records exist for this DNS name and IN IP6 FQDN if only =
AAAA records exist. Once candidate is nominated, address family in c=3D lin=
e should match address family used for communications. This will definitely=
 require a lot more work and discussion.</div><div style=3D""><br></div><di=
v style=3D"">b. Specify that FQDN connection addresses should be ignored un=
til their handling is defined in a future specification. This seems easy an=
d only requires a sentence or two to fix.</div><div style=3D""><br></div><d=
iv style=3D"">Regards,</div><div>_____________<br>Roman Shpount</div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div class=3D"gmail_quote"><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"><div dir=3D"ltr"><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 cla=
ss=3D"gmail_quote"><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 c=
lass=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=
 class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div></div>
</blockquote></div>
</blockquote></div></div>

--000000000000bbdaa90580dae688--


From nobody Fri Feb  1 12:27:37 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 B49C5130E89 for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 12:27:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.853
X-Spam-Level: 
X-Spam-Status: No, score=-8.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=K+oG7krw; dkim=pass (1024-bit key) header.d=ericsson.com header.b=VQsqxFjE
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 KBqNesCp7HRo for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 12:27:33 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 EB1DF130E6A for <mmusic@ietf.org>; Fri,  1 Feb 2019 12:27:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/relaxed;  q=dns/txt; i=@ericsson.com; t=1549052851; x=1551644851; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=X7YMOSKglwjZWwdZjCIG9hOm/umU/mz5TU3WUTNV7Ug=; b=K+oG7krwG+kEiIjDICFkM/nPTUrriyL6NL2umubWM6arYkbrfm9zcPmw0BcATK20 mH/pHg2CVxaG5YyHc+eKHNykz0VMYdnivKllJABr5N/ACKZBia2AhOJqp7VZ2fCI EN9s+u47517TJ/zHrI9+PVSpgSeE51Hc0BVzT/VIxgQ=;
X-AuditID: c1b4fb2d-d9dff7000000062f-8f-5c54abb3e28e
Received: from ESESBMB502.ericsson.se (Unknown_Domain [153.88.183.115]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 6C.D6.01583.3BBA45C5; Fri,  1 Feb 2019 21:27:31 +0100 (CET)
Received: from ESESBMR501.ericsson.se (153.88.183.129) by ESESBMB502.ericsson.se (153.88.183.185) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 1 Feb 2019 21:27:30 +0100
Received: from ESESBMB503.ericsson.se (153.88.183.170) by ESESBMR501.ericsson.se (153.88.183.129) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 1 Feb 2019 21:27:30 +0100
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (153.88.183.157) by ESESBMB503.ericsson.se (153.88.183.170) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Fri, 1 Feb 2019 21:27:30 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=X7YMOSKglwjZWwdZjCIG9hOm/umU/mz5TU3WUTNV7Ug=; b=VQsqxFjEfDI7atawNeRDCWLFjimt7zlIirb6MutKKbaMRh2s/pXzy82bG4sZEYw3iECWbn+knDPA8AUwYopYPj8R6VSVKOEk1mKJCqD9jTsHFqBiPMJcRi9FI497QntxyT1mlKZ9+1xdAamucERsiFcmjxx5jtI+JDre5wcCh+s=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3308.eurprd07.prod.outlook.com (10.170.246.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1580.11; Fri, 1 Feb 2019 20:27:28 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0%4]) with mapi id 15.20.1601.013; Fri, 1 Feb 2019 20:27:28 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
CC: Justin Uberti <juberti@google.com>, Simon Perreault <sperreault@jive.com>,  "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, "mmusic WG" <mmusic@ietf.org>
Thread-Topic: [rtcweb] [MMUSIC] What goes into c= line address when FQDN is used for the default candidate?
Thread-Index: AQHUulU2uFx8SsiiZk68wi8iILBKkKXLUQeAgAAK5CqAAANhgIAAA0UT
Date: Fri, 1 Feb 2019 20:27:28 +0000
Message-ID: <HE1PR07MB3161C0316B63EEE9C6B926DB93920@HE1PR07MB3161.eurprd07.prod.outlook.com>
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <HE1PR07MB3161471773206C16258150E493920@HE1PR07MB3161.eurprd07.prod.outlook.com>, <CAD5OKxuMOhVAh=Q=BGChP8vU5oQ8AwaoXn5qqctdv+ky6g0Xpw@mail.gmail.com>
In-Reply-To: <CAD5OKxuMOhVAh=Q=BGChP8vU5oQ8AwaoXn5qqctdv+ky6g0Xpw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [37.136.56.89]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR07MB3308; 6:TAIGx55XOKzdmSw/iZ1toN81X841wHCHWt49T+z0wjZu+EtBMvE5tZLlRmvo+Cy1dKN9iSoolmaRzgtrsF5svfE+Jmue4ZFtn2o9f2EaEW7RBwhy2/uQRVnXIMKMJzDANCsftPIjK6V8VKkQrLwcvDiY5PwTW1gEbybdRGOt6sz+MeeKrl/8U6ZbSAc9IrgwqizZJ1mR2lQJcfxgLm2D2Si/muyZZVVqZP6yyNJMpxtPFGAMxXOM9cmVhcb6Fmb2YCmT+/RHNZLMNP08mJ6K5+4mHP3S2mEj/uhXq9UMCFzoYwnhImDXjUwQSi9X9c3EhBSTLpOqZoV0Z9yi361Fj5bxpYbkN50YBhvUOFSYdp/tTxQyI0kOqs5RGXHDWmwvjnKzp2zuZhq1g/2UgjEqNmlbHVz+Tao869UP7IejsLma1n0SKMQ+KhHt0blKmDtSY1OxLXMMk8YOc/fJA6tpUQ==; 5:N5XZIjmIIRV6rOZEKpoxx+VROPkOpNeIGDBzKwYvg62lnlJ2uo5wMRg+8ukeNkemYx1qHbaZNVT1MmEKrTSMEmDcnFaVZUgmL+gCC5Xer86v8naq77xVgIjbqLhfSORYyk/Xp+M0EhiD7WLmGEAnoR+NSBOn+1Vdz0gEFB3pWWiMX3K4poFYryRLbTT3VlSU8uQfxP0wzeS0ncmGPcirLA==; 7:29CYj/YABg/iJIIclWZF/txJLhVSRvVNg3iMXxKX0ErkF8Es+UgXqqCmNdz1p/R1m0d0xm15IJVKR98SAF84xxhhtkJ5G2E3mk2inm7zOqn4LqkeRr3x1750EACh8CCLIyCusuWnJ1yJtJ6yvA7Qhg==
x-ms-office365-filtering-correlation-id: 3d8a8843-bac4-45c5-1439-08d68883af42
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(2017052603328)(7153060)(7193020); SRVR:HE1PR07MB3308; 
x-ms-traffictypediagnostic: HE1PR07MB3308:
x-microsoft-antispam-prvs: <HE1PR07MB33082440167574956E229C5293920@HE1PR07MB3308.eurprd07.prod.outlook.com>
x-forefront-prvs: 09352FD734
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39860400002)(366004)(346002)(376002)(136003)(199004)(189003)(106356001)(26005)(93886005)(86362001)(105586002)(6916009)(186003)(6606003)(19627405001)(256004)(14444005)(54906003)(99286004)(2906002)(102836004)(316002)(7696005)(68736007)(6506007)(76176011)(9686003)(54896002)(55016002)(8676002)(6116002)(53936002)(3846002)(486006)(8936002)(478600001)(81156014)(7736002)(81166006)(6246003)(25786009)(4326008)(74316002)(6436002)(14454004)(66066001)(229853002)(476003)(71190400001)(33656002)(71200400001)(44832011)(11346002)(446003)(97736004); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3308; 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: 6rcPEo6t+ZWL3AkzVQoRpvBgN8rEK/JSRewhevhz+eaU+OuIEPKKm0oHEr/4iMNM0kKm86jhtgDs4dO+kWs45CoKAO6Z7dT7RKSX8GcEA2tHE3550LKfXL7UnnvemYRkyC0bCQPBWXrKhS4RgBtvsdV0lnQyxrAoBEh12R+tPKQ7cE0/smV+ahUzgWjw9fha8G+zzaGH1Bvn+rOT5x1S0s4zXTS+pLj2I7Fu3hCqLq9y5WF1+jeKd00NYjf3LLH/IVxxgZBU8pOWph1MmWVOQ4Iaxr+1JJaaMLNapP9xhdmlktAgH+sG0WlDJFMRW5xQ7AY1onuxdvXJ8qgSFmBqHbWs/lFWutXIL/1CxsVO3BH9q38aalyYiux16vp2+to8G2Gh/3jV0J789nKW1Yg25WY8oJupc3pVFGjNvNOdXjk=
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB3161C0316B63EEE9C6B926DB93920HE1PR07MB3161eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3d8a8843-bac4-45c5-1439-08d68883af42
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2019 20:27:28.0739 (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-Transport-CrossTenantHeadersStamped: HE1PR07MB3308
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA01SfSyUcRzf757nnnvuuO3nkO9US7cwDJHpljJla7dWWzVK0XTjmbfD7R4s rZZYqqPYjkIZSrUdWo68bGTdWiJSKmISOcrIUvOScnL3qPnv8/28fF9++9GEpIPvSMclpTDq JIVSSonI4rBG1rOuKiRie4ZBJHtcKJEVPhgjZUWvCwlZjemyQNb/LlQ2+SItiJJr2+YIebk+ VV5Z+YsnN90eJ+SDBarD/JOi3dGMMi6NUXsHnhbFZi9r+aop3zO137S8DPTeQ4OENGA/qHmr RxokoiX4GYLs79f5XDGHoLm0mvpfjA9dQuaIBN/lwa16V7NA4nwCntxsFnAuLQ+GNV18zjWK oHzaRYNomsIyyDFZ5tlhZ1he0PLMfgI3IDD2ZPLMgi1WwtJECcGZEqE2r48wZ+3wftBPhJpp Em+DyY5hS3sxjoCW6rq1uR0UDI8OWbJCfAS6jC2UGSO8ARY6qy39CewAg8YyHnc0hsqWHoLD 9jA5ZuJzfgW06UbWeCdoHzYiDm+G3rIcyyMBzhTAQGsxxQmHoG5xkeKEAQSaotq1tDsMZY6t pRPgZ56O5PAmaFr8KOACg3zo/NpK5iPPknUbcjgZGnPekCWWU22go9hIcrwXfCgsoDjsAfcr pggOe0KRyUCu58uRQIfsWYZlE2N8d3gx6rgolk1O8kpiUvRo9YM9rf/t2YSqpvYaEKaR1FrM 6kIiJHxFGpueaEBAE1I78b74VUocrUg/y6iTI9WpSoY1oI00KXUQ/5HYREhwjCKFSWAYFaP+ p/JooWMGOuAfds6tX+Mnt4prCL+wZyn4VUWAW2/3sb4Rq1ln1bxbwaOVIcVMovWVLsGdhJCX ZTaDX8JdPo0GXivvFkayF5X3nn/uvnE8SxecO581TfzIPTHb3uVu2xe05WCkKnvnwxV//fl4 g3Zm6y7rmIJSGx9X+6uTpqMOUadueds5BQQIo6QkG6vwcSfUrOIvFouILVwDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/V7PtL3S-Cs3wizuo52bTM_6xXhA>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 01 Feb 2019 20:27:36 -0000

--_000_HE1PR07MB3161C0316B63EEE9C6B926DB93920HE1PR07MB3161eurp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,


>>> Most likely mDNS draft will need to update RFC
>>> 8445 to specify how ICE nomination procedures >>> are modified, when mD=
NS is used as candidate-
>>> address.
>>
>> What part of 8445 would need to be updated?
>
> Currently RFC 8445 specifies that candidates are
> only IP addresses and not an FQDN:
>
>   2.1.  Gathering Candidates
>
>   In order to execute ICE, an ICE agent identifies and
>   gathers one or more address candidates.  A
>   candidate has a transport address -- a combination
>   of IP address and port for a particular transport
>   protocol (with only UDP specified here).  There are
>   different types of candidates; some are derived
>   from physical or logical network interfaces, and
>   others are discoverable via STUN and TURN.
>
> In case of mDNS, candidate is a FQDN name. So
> when gathering candidates, DNS query will need to
> be performed and its result added to the candidate
> list.

The 8445 text does not talk about encoding of candidates on the wire. A can=
didate always has an IP address and port - and that is true no matter what =
you signal in the SDP on the wire.

> Also, I am not 100% sure, but I think mDNS can
> resolve to either IPv4/IPv6 or both addresses. So,
> single mDNS candidate can result in two actual ICE
> candidates. All of this looks like RFC 8445 update.

I raised this issue before, and I think the agreement was that, with ICE, m=
DNS would only result in ONE address (either IPv4 OR IPv6).

Regards,

Christer


--_000_HE1PR07MB3161C0316B63EEE9C6B926DB93920HE1PR07MB3161eurp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p style=3D"margin-top:0;margin-bottom:0">Hi,</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<div style=3D"color: rgb(0, 0, 0);">
<div>
<div dir=3D"ltr">
<div dir=3D"ltr">
<div>
<div class=3D"x_gmail_signature" dir=3D"ltr"><span style=3D"font-size:12pt"=
>&gt;&gt;&gt; Most likely mDNS draft will need to update
</span><span style=3D"font-size:12pt">RFC&nbsp;</span></div>
<div class=3D"x_gmail_signature" dir=3D"ltr"><span style=3D"font-size:12pt"=
></span><span style=3D"color:rgb(0,0,0)">&gt;&gt;&gt; 8445</span>&nbsp;to s=
pecify how ICE nomination procedures &gt;&gt;&gt; are modified, when mDNS i=
s used as candidate-</div>
<div class=3D"x_gmail_signature" dir=3D"ltr">&gt;&gt;&gt; address.&nbsp;</d=
iv>
<div class=3D"x_gmail_signature" dir=3D"ltr">&gt;&gt;</div>
<div class=3D"x_gmail_signature" dir=3D"ltr">&gt;&gt; What part of 8445 wou=
ld need to be updated?</div>
<div class=3D"x_gmail_signature" dir=3D"ltr"><font face=3D"Calibri,Helvetic=
a,sans-serif">&gt;</font><br>
</div>
</div>
</div>
<div class=3D"x_gmail_quote">
<div></div>
<div>&gt; Currently RFC 8445 specifies that candidates are&nbsp;</div>
<div>&gt; only IP addresses and not&nbsp;<span style=3D"color:rgb(0,0,0)">a=
n FQDN:</span><br>
</div>
<div>&gt;<br style=3D"color:rgb(0,0,0)">
<span style=3D"color:rgb(0,0,0)">&gt; &nbsp; 2.1.&nbsp; Gathering Candidate=
s</span><br style=3D"color:rgb(0,0,0)">
&gt;<br style=3D"color:rgb(0,0,0)">
<span style=3D"color:rgb(0,0,0)">&gt; &nbsp; In order to execute ICE, an IC=
E agent identifies and&nbsp;</span></div>
<div><span style=3D"color:rgb(0,0,0)">&gt; &nbsp; gathers one or </span><sp=
an style=3D"color:rgb(0,0,0)">more address candidates.&nbsp; A&nbsp;</span>=
</div>
<div><span style=3D"color:rgb(0,0,0)">&gt; &nbsp; candidate has a transport=
 address -- a </span>
<span style=3D"color:rgb(0,0,0)">combination</span></div>
<div><span style=3D"color:rgb(0,0,0)">&gt; &nbsp; of IP address and port fo=
r a particular transport</span><br style=3D"color:rgb(0,0,0)">
<span style=3D"color:rgb(0,0,0)">&gt; &nbsp; protocol (with only UDP specif=
ied here).&nbsp; There are&nbsp;</span></div>
<div><span style=3D"color:rgb(0,0,0)">&gt; &nbsp; different types </span><s=
pan style=3D"color:rgb(0,0,0)">of candidates; some are derived&nbsp;</span>=
</div>
<div><span style=3D"color:rgb(0,0,0)">&gt; &nbsp; from physical or logical =
network</span><span style=3D"color:rgb(0,0,0)"> interfaces, and</span></div=
>
<div><span style=3D"color:rgb(0,0,0)">&gt; &nbsp; others are discoverable v=
ia STUN and TURN.</span>&nbsp;&nbsp;<br>
</div>
<div class=3D"x_gmail_quote">&gt;</div>
<div class=3D"x_gmail_quote">&gt; In case of mDNS, candidate is a FQDN name=
. So&nbsp;</div>
<div class=3D"x_gmail_quote">&gt; when gathering candidates, DNS query will=
 need to&nbsp;</div>
<div class=3D"x_gmail_quote">&gt; be performed and its result added to the =
candidate&nbsp;</div>
<div class=3D"x_gmail_quote">&gt; list.&nbsp;</div>
<div class=3D"x_gmail_quote"><br>
</div>
<div class=3D"x_gmail_quote">The 8445 text does not talk about encoding of =
candidates on the wire. A candidate always has an IP address and port - and=
 that is true no matter what you signal in the SDP on the wire.</div>
<div class=3D"x_gmail_quote"><br>
</div>
<div class=3D"x_gmail_quote">&gt; Also, I am not 100% sure, but I think mDN=
S can&nbsp;</div>
<div class=3D"x_gmail_quote">&gt; resolve to either IPv4/IPv6 or both addre=
sses. So,&nbsp;</div>
<div class=3D"x_gmail_quote">&gt; single mDNS candidate can result in two a=
ctual ICE&nbsp;</div>
<div class=3D"x_gmail_quote">&gt; candidates. All of this looks like RFC 84=
45 update.</div>
<div class=3D"x_gmail_quote"><br>
</div>
<div class=3D"x_gmail_quote">I raised this issue before, and I think the ag=
reement was that, with ICE, mDNS would only result in ONE address (either I=
Pv4 OR IPv6).</div>
<div class=3D"x_gmail_quote"><br>
</div>
<div class=3D"x_gmail_quote">Regards,</div>
<div class=3D"x_gmail_quote"><br>
</div>
<div class=3D"x_gmail_quote">Christer</div>
<div class=3D"x_gmail_quote">&nbsp;</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_HE1PR07MB3161C0316B63EEE9C6B926DB93920HE1PR07MB3161eurp_--


From nobody Fri Feb  1 13:02:23 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 B611E130EAB for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 13:02:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.852
X-Spam-Level: 
X-Spam-Status: No, score=-8.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=WA173W+i; dkim=pass (1024-bit key) header.d=ericsson.com header.b=ZOo5YLOp
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 U5tHFuYjZd9Q for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 13:02:18 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 32D94130E8F for <mmusic@ietf.org>; Fri,  1 Feb 2019 13:02:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/relaxed;  q=dns/txt; i=@ericsson.com; t=1549054935; x=1551646935; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Cvsp8+sM9hs4gTAJszW/mMnQbERQz0yXX3UJ0ZzdzDc=; b=WA173W+iYHi3Fkf8vM2PQTDNpkttg9u7Bm9spQ5HfhWbT7DkmJ/pPexyESZhM3Mu +/GUSY0+XyArBquDubEm5Gx6SnZc5Kult394HHzciJKGAtCTQMs2Y9h04dTHjMsK g28t26weniBKQZfuL2E/yr8tpaxIWFX9/42YubIDu68=;
X-AuditID: c1b4fb3a-167ff7000000672c-14-5c54b3d77ffc
Received: from ESESSMB501.ericsson.se (Unknown_Domain [153.88.183.119]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id C5.FA.26412.7D3B45C5; Fri,  1 Feb 2019 22:02:15 +0100 (CET)
Received: from ESESBMB505.ericsson.se (153.88.183.172) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 1 Feb 2019 22:02:15 +0100
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESBMB505.ericsson.se (153.88.183.172) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Fri, 1 Feb 2019 22:02:15 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Cvsp8+sM9hs4gTAJszW/mMnQbERQz0yXX3UJ0ZzdzDc=; b=ZOo5YLOpOXHPv43LYM48uro4gmCHCes9r8jXJGS8UDCNzhbSziW3TEHss1DSa03jUpFY7AImEeQ7FHDDsI45PlSdpHXWcv+5PxFAT7hyJIvnoJRWFFzcfn4cOyaC2KhT00pMoCCSPxuE6KuNpm7cSjM27nzwvZ86FaXEaAVKPWg=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3082.eurprd07.prod.outlook.com (10.170.244.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1580.14; Fri, 1 Feb 2019 21:02:14 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0%4]) with mapi id 15.20.1601.013; Fri, 1 Feb 2019 21:02:14 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>, Justin Uberti <juberti@google.com>
CC: Simon Perreault <sperreault@jive.com>, "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Thread-Topic: [rtcweb] [MMUSIC] What goes into c= line address when FQDN is used for the default candidate?
Thread-Index: AQHUulU2uFx8SsiiZk68wi8iILBKkKXLUQeAgAAF3QCAAAwVgIAACK4A
Date: Fri, 1 Feb 2019 21:02:14 +0000
Message-ID: <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com>
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com>, <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com>
In-Reply-To: <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [37.136.56.89]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR07MB3082; 6:gvHPX9xSCDlQm2cBGKliaxwp3FfqLiRIjsjOZILo/DlzIVNRdRmHFQ43qlMszyAFkQK6XX7cyIvnhzYMchh9ch/Tuif6fwEFoI35XJ/dfrs4BHmmFpibN+GUAX1BBSn428TWlZdZCJcyXz/tlF/N/a6eH3afqUjAxpffDeGFsSx5MuUMSEIMAlAJtFDQho4f0z9OFRngnSfOHNQvlwWdxageAAWM4ca1fJ1XZPbq9iXSGZ3N//Hy5Ee6ps4zMkf57wyxPbkipEQx/omhEFkHaYTGwwSLcnyLCnLXCP0DD4FZnvamCoCQCtbhlJGgATA0a0QmhMgi/Z11142qJfOPWRApyna3WQV8IQ6C3dz+rDjpD2NL2KIp8BtxBLhch2jmKc2hHjszLxF2us+ZUQT2wAcTwW5ISPoYr4d+wSbYlwBZw56lm7o63+5ksncUJqVD/5eZAbiC+92KpXm/4goaxw==; 5:OECNRopP2ffBFga51TKE/XpMp9N91FQD5m8D4yLQycWw4THBkD8nzliTfn/MIz3KAqszb9L/lDzYFBbfZ6ce/iss7VffOQmMet2uoabcFGfrxvcdam4x1nZ8oyvyzuwCoCdGZT5jnAxrnZTPHmqqagv0H04vMPaLKpMpwWNxmrUqsENIrLHUBs8vXS/DY5WJwBkP0I/xrpsBWPDvLY9gOg==; 7:nFs9j0LsCsGH6+w4CACp/JiBdVZym51YLP11R24ZsCj1saJo1au8bBfWVFMONiPM3yYWb5mXXcFbIJnQj5RusmANWwrOXynFmvd98cvHkv517LUbY3VPlVe/eOHlUjrYZByiEsFnVlN5SkS/wVpvAg==
x-ms-office365-filtering-correlation-id: 5bed3c24-ae36-4975-7c13-08d688888aa4
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(2017052603328)(7153060)(7193020); SRVR:HE1PR07MB3082; 
x-ms-traffictypediagnostic: HE1PR07MB3082:
x-microsoft-antispam-prvs: <HE1PR07MB3082760319C66AE782991D3893920@HE1PR07MB3082.eurprd07.prod.outlook.com>
x-forefront-prvs: 09352FD734
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(366004)(136003)(346002)(376002)(396003)(199004)(189003)(8936002)(53936002)(93886005)(86362001)(99286004)(71190400001)(106356001)(71200400001)(1015004)(53546011)(14454004)(6506007)(236005)(6606003)(7736002)(74316002)(33656002)(229853002)(25786009)(68736007)(606006)(256004)(14444005)(76176011)(476003)(2906002)(446003)(6436002)(486006)(19627405001)(110136005)(26005)(54906003)(105586002)(102836004)(4326008)(44832011)(478600001)(11346002)(81156014)(7696005)(9686003)(55016002)(97736004)(8676002)(5070765005)(186003)(6246003)(81166006)(6306002)(66066001)(54896002)(316002)(6116002)(3846002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3082; 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: dDQDtotYETEvYpjXnGUmogB2wnZ/abcAGzhoOIOfp1CX3m843KfvmFtL+EzQ6EflAvSCD6qhQJaRCI9py913rIVFgeQiXwTzeHAy7SGSFPKoO2UhKKN4YLB46MflN91n/AbxcKK7dSsVb2yzRcOtUFUH0OYaBN7pCeFt4+p0rO+G1/qg8Z0W2vWTV8qXTLcWBtzGHBwecfaMqw8/0BXPbW70uTLnvV2qUtacrPCulab3UE4rWeLPS2p42vbo7RRMF3t/vrs7E9zP0RW+8wcLVZAoGmnzDikCFvu8YNIRweC6ySv9og3ju6jz43lN1zzwrLECeUP5yQ81IsgpZR88WUlGA+znHMqLu6P90CAZk7NgN7Qv/pzgicuY+XEr/ENhH8mXYpyJ+QqL9/BTswcKxn/3fms1Jvq4mSQJZXSlg6A=
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB31617DB79BE41B64AECF082693920HE1PR07MB3161eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5bed3c24-ae36-4975-7c13-08d688888aa4
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2019 21:02:14.1378 (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-Transport-CrossTenantHeadersStamped: HE1PR07MB3082
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Se0iTURjGOfu+ffscDo7L5ZsV1pAwb5UVTI2woFh/SBcMpCY68kNtF2Wf WgmVWVIY4kAHNRINV+btjzSZeckc5mVdvZB5zdI07WbU8JLM2o6B//3e53k4530Oh6WknUJf NkWfzhn0aq2cEdO3Y63nQgbqYlQ7f3WGK+pNUoWpfIJW3HpjohQ1zusixUD/ScVMV2YUoyxs dVDK0toMpcWyKFA673yilENFaceEp8T7EjltSiZn2LE/QZxcNvUDpT1WnW9YyRZlI1t0HvJg Ae+Brt56lIfErBS3I6ju6UEuQ4odCOamZcQoE0DPeJvANdDYSMFycS5NnEIBOPpaGDJ8QFBR WEXlIZZlsAJuOoNcR3njI/B1sYxyZShsRGC3PnHfsQ5rYWnKTJGQDh4WvF3lw2BumnVnaOwP bV/fi1wswSpo/lhOk/1aGKj77WYPfBwsL1658wivh3l7tcDFFPaBockSASmKwdL8miIsg5kJ p5Dk1dBaOb6qb4HOsUlEeDP0ltx0PwzgHBE8bexniBENCwP5QmIMIrjR/1Poagw4EO69iyOo AWP36r2boGFhVETiRQyU5DgYUoCD8ppcZETB5jW7Ek6Fvu8rtNnd2Qu6b0/SRA+Fd6YihnAQ 3L/7hSIcArecNnqtXopElUjGczyvSwoLC+UMKWd4PlUfqufSa9G/79X26E9EA2qbPmBDmEVy T0ldZYxKKlRn8hd0NgQsJfeWHDz7T5Ikqi9kcYbUeEOGluNtaCNLy30ky1IvlRQnqdM5Dcel cYb/roD18M1Gh2qEfpcC5VZNol9+1LglsiA50pT+0n8hdinAnvFgWHbieePg9Y7gvqzwN+bL jK5lODdipOmabC6h62JuUrt169G6DPP2z/PbNl+Nl8l3jxTINoyNt4c905yugA6zPd5H/K13 i2DwbJVIv3f20MJzWeHhhLiOgDtM8ajV4lmad0VO88nqXYGUgVf/BTXWc65aAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/zLReDPcHBc1SCtxVxFJoLViyDKk>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 01 Feb 2019 21:02:22 -0000

--_000_HE1PR07MB31617DB79BE41B64AECF082693920HE1PR07MB3161eurp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,


I have no problem with allowing FQDNs - as long as they result in a SINGLE =
address:port.


If we want to define ICE usage of FDNSs resulting in MULTIPLE addresses:por=
ts, I really think that should be a separate document - it should NOT be ad=
ded as a last minute thing to draft-ice-sip-sdp.


...and, yes, perhaps such work would also affect 8445.


Regards,


Christer





________________________________
From: rtcweb <rtcweb-bounces@ietf.org> on behalf of Roman Shpount <roman@te=
lurix.com>
Sent: Friday, February 1, 2019 10:22 PM
To: Justin Uberti
Cc: Simon Perreault; Dale R. Worley; RTCWeb IETF; mmusic WG
Subject: Re: [rtcweb] [MMUSIC] What goes into c=3D line address when FQDN i=
s used for the default candidate?

On Fri, Feb 1, 2019 at 2:39 PM Justin Uberti <juberti@google.com<mailto:jub=
erti@google.com>> wrote:
This has all been discussed at length in rtcweb and I don't think any signi=
ficant changes are needed, although I tend to think that we should restore =
the removed FQDN text from mmusic-ice-sip-sdp, which is the only thing not =
in alignment at this point in time.

I agree that FQDN should be put back into connection-address definition, bu=
t  the portion which talks about handling it is completely broken.

Quoting 5245<https://tools.ietf.org/html/rfc5245#section-15.1>:

   <connection-address>:  is taken from RFC 4566<https://tools.ietf.org/htm=
l/rfc4566> [RFC4566<https://tools.ietf.org/html/rfc4566>].  It is the
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and fully qualified domain names (FQDNs).  When parsing
      this field, an agent can differentiate an IPv4 address and an IPv6


      address by presence of a colon in its value - the presence of a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=3Dcandidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.



I think it was discussed in quite a detail why using a random DNS resolutio=
n result is not going to work here..

The only options we have here are:

a. Fix FQDN connection address handling. Probably the most logical way of d=
ealing with this would be to specify that candidate with FQDN should be con=
verted as a result of DNS resolution into multiple candidates, with each ca=
ndidate corresponding to A or AAAA record in DNS query result. We will also=
 need to specify how FQDN candidate gets applied to c=3D line address. Some=
thing that says IN IP4 FQDN, if any A records exist for this DNS name and I=
N IP6 FQDN if only AAAA records exist. Once candidate is nominated, address=
 family in c=3D line should match address family used for communications. T=
his will definitely require a lot more work and discussion.

b. Specify that FQDN connection addresses should be ignored until their han=
dling is defined in a future specification. This seems easy and only requir=
es a sentence or two to fix.

Regards,
_____________
Roman Shpount

--_000_HE1PR07MB31617DB79BE41B64AECF082693920HE1PR07MB3161eurp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p style=3D"margin-top:0;margin-bottom:0">Hi,</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">I have no problem with allowing F=
QDNs - as long as they result in a SINGLE address:port.</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">If we want to define ICE usage of=
 FDNSs resulting in MULTIPLE addresses:ports, I really think that should be=
 a separate document - it should NOT be added as a last minute thing to dra=
ft-ice-sip-sdp.</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">...and, yes, perhaps such work wo=
uld also affect 8445.</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">Regards,</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">Christer</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<br>
<br>
<div style=3D"color: rgb(0, 0, 0);">
<hr tabindex=3D"-1" style=3D"display:inline-block;width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font color=3D"#000000" face=3D"Calib=
ri, sans-serif" style=3D"font-size:11pt"><b>From:</b> rtcweb &lt;rtcweb-bou=
nces@ietf.org&gt; on behalf of Roman Shpount &lt;roman@telurix.com&gt;<br>
<b>Sent:</b> Friday, February 1, 2019 10:22 PM<br>
<b>To:</b> Justin Uberti<br>
<b>Cc:</b> Simon Perreault; Dale R. Worley; RTCWeb IETF; mmusic WG<br>
<b>Subject:</b> Re: [rtcweb] [MMUSIC] What goes into c=3D line address when=
 FQDN is used for the default candidate?</font>
<div>&nbsp;</div>
</div>
<div>
<div dir=3D"ltr">
<div dir=3D"ltr">
<div>
<div class=3D"x_gmail_signature" dir=3D"ltr">On Fri, Feb 1, 2019 at 2:39 PM=
 Justin Uberti &lt;<a class=3D"OWAAutoLink" id=3D"LPlnk701075" href=3D"mail=
to:juberti@google.com" previewremoved=3D"true">juberti@google.com</a>&gt; w=
rote:<br>
</div>
</div>
</div>
<div class=3D"x_gmail_quote">
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div dir=3D"ltr">This has all been discussed at length in rtcweb and I don'=
t think any significant changes are needed, although I tend to think that w=
e should restore the removed FQDN text from mmusic-ice-sip-sdp, which is th=
e only thing not in alignment at this
 point in time.</div>
</blockquote>
<div><br>
</div>
<div>I agree that FQDN should be put back into connection-address definitio=
n, but&nbsp; the portion which talks about handling it is completely broken=
.</div>
<div><br>
</div>
<div>Quoting&nbsp;<a class=3D"OWAAutoLink" id=3D"LPlnk401396" href=3D"https=
://tools.ietf.org/html/rfc5245#section-15.1" target=3D"_blank" previewremov=
ed=3D"true">5245</a><span style=3D"color:rgb(0,0,0)">:</span></div>
<div style=3D"">
<pre class=3D"x_gmail-m_7058075087377128197gmail-newpage" style=3D"color:rg=
b(0,0,0); white-space:pre-wrap; font-size:13.3333px; margin-top:0px; margin=
-bottom:0px; break-before:page">   &lt;connection-address&gt;:  is taken fr=
om <a class=3D"OWAAutoLink" id=3D"LPlnk554019" href=3D"https://tools.ietf.o=
rg/html/rfc4566" target=3D"_blank" previewremoved=3D"true">RFC 4566</a> [<a=
 title=3D"&quot;SDP: Session Description Protocol&quot;" class=3D"OWAAutoLi=
nk" id=3D"LPlnk297636" href=3D"https://tools.ietf.org/html/rfc4566" target=
=3D"_blank" previewremoved=3D"true">RFC4566</a>].  It is the=0A=
      IP address of the candidate, allowing for IPv4 addresses, IPv6=0A=
      addresses, and <b>fully qualified domain names (FQDNs).</b>  When par=
sing=0A=
      this field, an agent can differentiate an IPv4 address and an IPv6=0A=
</pre>
<pre class=3D"x_gmail-m_7058075087377128197gmail-newpage" style=3D"color:rg=
b(0,0,0); white-space:pre-wrap; font-size:13.3333px; margin-top:0px; margin=
-bottom:0px; break-before:page">      address by presence of a colon in its=
 value - the presence of a=0A=
      colon indicates IPv6.  An agent MUST ignore candidate lines that=0A=
      include candidates with IP address versions that are not supported=0A=
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be=0A=
      used in place of an IP address.  In that case, when receiving an=0A=
      offer or answer containing an FQDN in an a=3Dcandidate attribute,=0A=
      the FQDN is looked up in the DNS first using an AAAA record=0A=
      (assuming the agent supports IPv6), and if no result is found or=0A=
      the agent only supports IPv4, using an A.  If the DNS query=0A=
      returns more than one IP address, one is chosen, and then used for=0A=
      the remainder of ICE processing.=0A=
</pre>
<pre class=3D"x_gmail-m_7058075087377128197gmail-newpage" style=3D"color:rg=
b(0,0,0); white-space:pre-wrap; font-size:13.3333px; margin-top:0px; margin=
-bottom:0px; break-before:page"><br></pre>
I think it was discussed in quite a detail why using a random DNS resolutio=
n result is not going to work here..</div>
<div style=3D""><br>
</div>
<div style=3D"">The only options we have here are:</div>
<div style=3D""><br>
</div>
<div style=3D"">a. Fix FQDN connection address handling. Probably the most =
logical way of dealing with this would be to specify that candidate with FQ=
DN should be converted as a result of DNS resolution into multiple candidat=
es, with each candidate corresponding
 to A or AAAA record in DNS query result. We will also need to specify how =
FQDN candidate gets applied to c=3D line address. Something that says IN IP=
4 FQDN, if any A records exist for this DNS name and IN IP6 FQDN if only AA=
AA records exist. Once candidate is
 nominated, address family in c=3D line should match address family used fo=
r communications. This will definitely require a lot more work and discussi=
on.</div>
<div style=3D""><br>
</div>
<div style=3D"">b. Specify that FQDN connection addresses should be ignored=
 until their handling is defined in a future specification. This seems easy=
 and only requires a sentence or two to fix.</div>
<div style=3D""><br>
</div>
<div style=3D"">Regards,</div>
<div>_____________<br>
Roman Shpount</div>
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div class=3D"x_gmail_quote">
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div dir=3D"ltr">
<div class=3D"x_gmail_quote">
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div class=3D"x_gmail_quote">
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div class=3D"x_gmail_quote">
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div class=3D"x_gmail_quote">
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_HE1PR07MB31617DB79BE41B64AECF082693920HE1PR07MB3161eurp_--


From nobody Fri Feb  1 13:06:34 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 1448C130EB0 for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 13:06:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.03
X-Spam-Level: 
X-Spam-Status: No, score=-2.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 LDIr3YGfAjuh for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 13:06:30 -0800 (PST)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (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 81EDE130EAB for <mmusic@ietf.org>; Fri,  1 Feb 2019 13:06:30 -0800 (PST)
Received: by mail-pg1-x535.google.com with SMTP id n2so3498508pgm.3 for <mmusic@ietf.org>; Fri, 01 Feb 2019 13:06:30 -0800 (PST)
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=iff0lhNlCF7xnZCR8/in3v6Cm0JzBcSy7qWsRAEn5xQ=; b=ZBiT+H/KeUmADUCSeNXUlryUQgRc6jlbi/oQw7251D/PclCLhZw1vFzArTCEVIAd+0 taVGOnp3oUnooA2/MurSgrsgFlLlF1V4rAFk4EYo3rLbD9FEwpyv6ydf6u4yTRX8bAZI OYzcpZpI3zODgX+ew5b3QjxDzjIzFjxPNe807faDLECfqiP1qjHOpbpIQW+4rmJV3L7c l6Sy94wBvOxXLXJ5ydvEAwKXyBhMOP96ZukIEQxdRduDPfG4E1GCGxiVVsZ+CXWJhEtf DCxJSHMSnjHkYm2FqmVZBBX2McO05FXswgjIYax66Lx316ZebGYdyG1bosdiD++zdUWS yIpw==
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=iff0lhNlCF7xnZCR8/in3v6Cm0JzBcSy7qWsRAEn5xQ=; b=aDrNJd/ZabXsRR5IiabwR1kJQcUJ436QS54wKTFPrG3FdEYWpl4+LpTkJdclfdXbBT VoAHVpyv4Tx0YwoI/W/n8945/lnAx7m04FOBOMH3uTKK49ytx4610gB1+wfD7K4nq3kV gGiyVhyB9TSjp8FBBa2zVu+1BkcV9ewowKDvebvDOjdJloA6TggVqBjFF4mWCVv3fwAL /DrWw2mIC14LyvB9nCOgBU7ezgTyf42nIu7OZaBr6d3LfPuPK+NZkdB0jI3EnolWZ0WU jN8EBYpJQNFA20Z06N0XN1c/OzjH3sOZJ1KjWtnJUl3kSMcHjYJVZ3hkpj9iUJ8x0p3s flfQ==
X-Gm-Message-State: AHQUAuac4kfysX74JCCk9m371DBeQQwXz6x93WG9+LFVaBDx7c6VwtMN Gyhdq2xBQ4lfrfY6DDJfVlVXTw==
X-Google-Smtp-Source: AHgI3Ibastm4ax3ZdmStPFs0pN31bCDPf/GfUnI/Y2STxSjxwm1sgSF2+tXLKnVWCB2krfUIiGEtCA==
X-Received: by 2002:a63:d157:: with SMTP id c23mr2158612pgj.170.1549055189986;  Fri, 01 Feb 2019 13:06:29 -0800 (PST)
Received: from mail-pl1-f171.google.com (mail-pl1-f171.google.com. [209.85.214.171]) by smtp.gmail.com with ESMTPSA id h129sm27548879pfb.110.2019.02.01.13.06.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Feb 2019 13:06:29 -0800 (PST)
Received: by mail-pl1-f171.google.com with SMTP id p8so3829127plo.2; Fri, 01 Feb 2019 13:06:29 -0800 (PST)
X-Received: by 2002:a17:902:720c:: with SMTP id ba12mr41396137plb.79.1549055188791;  Fri, 01 Feb 2019 13:06:28 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com> <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com> <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 1 Feb 2019 16:06:18 -0500
X-Gmail-Original-Message-ID: <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com>
Message-ID: <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Justin Uberti <juberti@google.com>, Simon Perreault <sperreault@jive.com>,  "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004403690580db84ee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Bb4u9wizU528OzLi_FM9VzcbySM>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 01 Feb 2019 21:06:33 -0000

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

In this case section 4.1 of ice-sip-sdp should be updated to allow FQDN in
connection-address and, perhaps specify that FWDN which return multiple
results should be ignored.

Would this work for everyone?

Regards,
_____________
Roman Shpount


On Fri, Feb 1, 2019 at 4:02 PM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> I have no problem with allowing FQDNs - as long as they result in a SINGLE
> address:port.
>
>
> If we want to define ICE usage of FDNSs resulting in MULTIPLE
> addresses:ports, I really think that should be a separate document - it
> should NOT be added as a last minute thing to draft-ice-sip-sdp.
>
>
> ...and, yes, perhaps such work would also affect 8445.
>
>
> Regards,
>
>
> Christer
>
>
>
>
>
>
> ------------------------------
> *From:* rtcweb <rtcweb-bounces@ietf.org> on behalf of Roman Shpount <
> roman@telurix.com>
> *Sent:* Friday, February 1, 2019 10:22 PM
> *To:* Justin Uberti
> *Cc:* Simon Perreault; Dale R. Worley; RTCWeb IETF; mmusic WG
> *Subject:* Re: [rtcweb] [MMUSIC] What goes into c= line address when FQDN
> is used for the default candidate?
>
> On Fri, Feb 1, 2019 at 2:39 PM Justin Uberti <juberti@google.com> wrote:
>
> This has all been discussed at length in rtcweb and I don't think any
> significant changes are needed, although I tend to think that we should
> restore the removed FQDN text from mmusic-ice-sip-sdp, which is the only
> thing not in alignment at this point in time.
>
>
> I agree that FQDN should be put back into connection-address definition,
> but  the portion which talks about handling it is completely broken.
>
> Quoting 5245 <https://tools.ietf.org/html/rfc5245#section-15.1>:
>
>    <connection-address>:  is taken from RFC 4566 <https://tools.ietf.org/html/rfc4566> [RFC4566 <https://tools.ietf.org/html/rfc4566>].  It is the
>       IP address of the candidate, allowing for IPv4 addresses, IPv6
>       addresses, and *fully qualified domain names (FQDNs).*  When parsing
>       this field, an agent can differentiate an IPv4 address and an IPv6
>
>       address by presence of a colon in its value - the presence of a
>       colon indicates IPv6.  An agent MUST ignore candidate lines that
>       include candidates with IP address versions that are not supported
>       or recognized.  An IP address SHOULD be used, but an FQDN MAY be
>       used in place of an IP address.  In that case, when receiving an
>       offer or answer containing an FQDN in an a=candidate attribute,
>       the FQDN is looked up in the DNS first using an AAAA record
>       (assuming the agent supports IPv6), and if no result is found or
>       the agent only supports IPv4, using an A.  If the DNS query
>       returns more than one IP address, one is chosen, and then used for
>       the remainder of ICE processing.
>
>
> I think it was discussed in quite a detail why using a random DNS
> resolution result is not going to work here..
>
> The only options we have here are:
>
> a. Fix FQDN connection address handling. Probably the most logical way of
> dealing with this would be to specify that candidate with FQDN should be
> converted as a result of DNS resolution into multiple candidates, with each
> candidate corresponding to A or AAAA record in DNS query result. We will
> also need to specify how FQDN candidate gets applied to c= line address.
> Something that says IN IP4 FQDN, if any A records exist for this DNS name
> and IN IP6 FQDN if only AAAA records exist. Once candidate is nominated,
> address family in c= line should match address family used for
> communications. This will definitely require a lot more work and discussion.
>
> b. Specify that FQDN connection addresses should be ignored until their
> handling is defined in a future specification. This seems easy and only
> requires a sentence or two to fix.
>
> Regards,
> _____________
> Roman Shpount
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr">In this case section 4.1 of ice-sip-sdp s=
hould be updated to allow FQDN in connection-address and, perhaps specify t=
hat FWDN which return multiple results should be ignored.</div><div dir=3D"=
ltr"><br></div><div dir=3D"ltr">Would this work for everyone?</div><div dir=
=3D"ltr"><br></div><div dir=3D"ltr">Regards,<br clear=3D"all"><div><div dir=
=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature">_____=
________<br>Roman Shpount</div></div><br></div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 1, 2019 at 4:02 PM Chr=
ister Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">christ=
er.holmberg@ericsson.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">




<div dir=3D"ltr">
<div id=3D"gmail-m_-7925862921453132447divtagdefaultwrapper" style=3D"font-=
size:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif" dir=3D=
"ltr">
<p style=3D"margin-top:0px;margin-bottom:0px"><span style=3D"font-size:12pt=
">I have no problem with allowing FQDNs - as long as they result in a SINGL=
E address:port.</span><br></p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px">If we want to define ICE usag=
e of FDNSs resulting in MULTIPLE addresses:ports, I really think that shoul=
d be a separate document - it should NOT be added as a last minute thing to=
 draft-ice-sip-sdp.</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px">...and, yes, perhaps such wor=
k would also affect 8445.</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px">Regards,</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px">Christer</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<br>
<br>
<div style=3D"color:rgb(0,0,0)">
<hr style=3D"display:inline-block;width:98%">
<div id=3D"gmail-m_-7925862921453132447divRplyFwdMsg" dir=3D"ltr"><font col=
or=3D"#000000" face=3D"Calibri, sans-serif" style=3D"font-size:11pt"><b>Fro=
m:</b> rtcweb &lt;<a href=3D"mailto:rtcweb-bounces@ietf.org" target=3D"_bla=
nk">rtcweb-bounces@ietf.org</a>&gt; on behalf of Roman Shpount &lt;<a href=
=3D"mailto:roman@telurix.com" target=3D"_blank">roman@telurix.com</a>&gt;<b=
r>
<b>Sent:</b> Friday, February 1, 2019 10:22 PM<br>
<b>To:</b> Justin Uberti<br>
<b>Cc:</b> Simon Perreault; Dale R. Worley; RTCWeb IETF; mmusic WG<br>
<b>Subject:</b> Re: [rtcweb] [MMUSIC] What goes into c=3D line address when=
 FQDN is used for the default candidate?</font>
<div>=C2=A0</div>
</div>
<div>
<div dir=3D"ltr">
<div dir=3D"ltr">
<div>
<div class=3D"gmail-m_-7925862921453132447x_gmail_signature" dir=3D"ltr">On=
 Fri, Feb 1, 2019 at 2:39 PM Justin Uberti &lt;<a class=3D"gmail-m_-7925862=
921453132447OWAAutoLink" id=3D"gmail-m_-7925862921453132447LPlnk701075" hre=
f=3D"mailto:juberti@google.com" target=3D"_blank">juberti@google.com</a>&gt=
; wrote:<br>
</div>
</div>
</div>
<div class=3D"gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
<div dir=3D"ltr">This has all been discussed at length in rtcweb and I don&=
#39;t think any significant changes are needed, although I tend to think th=
at we should restore the removed FQDN text from mmusic-ice-sip-sdp, which i=
s the only thing not in alignment at this
 point in time.</div>
</blockquote>
<div><br>
</div>
<div>I agree that FQDN should be put back into connection-address definitio=
n, but=C2=A0 the portion which talks about handling it is completely broken=
.</div>
<div><br>
</div>
<div>Quoting=C2=A0<a class=3D"gmail-m_-7925862921453132447OWAAutoLink" id=
=3D"gmail-m_-7925862921453132447LPlnk401396" href=3D"https://tools.ietf.org=
/html/rfc5245#section-15.1" target=3D"_blank">5245</a><span style=3D"color:=
rgb(0,0,0)">:</span></div>
<div>
<pre class=3D"gmail-m_-7925862921453132447x_gmail-m_7058075087377128197gmai=
l-newpage" style=3D"color:rgb(0,0,0);white-space:pre-wrap;font-size:13.3333=
px;margin-top:0px;margin-bottom:0px;break-before:page">   &lt;connection-ad=
dress&gt;:  is taken from <a class=3D"gmail-m_-7925862921453132447OWAAutoLi=
nk" id=3D"gmail-m_-7925862921453132447LPlnk554019" href=3D"https://tools.ie=
tf.org/html/rfc4566" target=3D"_blank">RFC 4566</a> [<a title=3D"&quot;SDP:=
 Session Description Protocol&quot;" class=3D"gmail-m_-7925862921453132447O=
WAAutoLink" id=3D"gmail-m_-7925862921453132447LPlnk297636" href=3D"https://=
tools.ietf.org/html/rfc4566" target=3D"_blank">RFC4566</a>].  It is the
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and <b>fully qualified domain names (FQDNs).</b>  When par=
sing
      this field, an agent can differentiate an IPv4 address and an IPv6
</pre>
<pre class=3D"gmail-m_-7925862921453132447x_gmail-m_7058075087377128197gmai=
l-newpage" style=3D"color:rgb(0,0,0);white-space:pre-wrap;font-size:13.3333=
px;margin-top:0px;margin-bottom:0px;break-before:page">      address by pre=
sence of a colon in its value - the presence of a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=3Dcandidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.
</pre>
<pre class=3D"gmail-m_-7925862921453132447x_gmail-m_7058075087377128197gmai=
l-newpage" style=3D"color:rgb(0,0,0);white-space:pre-wrap;font-size:13.3333=
px;margin-top:0px;margin-bottom:0px;break-before:page"><br></pre>
I think it was discussed in quite a detail why using a random DNS resolutio=
n result is not going to work here..</div>
<div><br>
</div>
<div>The only options we have here are:</div>
<div><br>
</div>
<div>a. Fix FQDN connection address handling. Probably the most logical way=
 of dealing with this would be to specify that candidate with FQDN should b=
e converted as a result of DNS resolution into multiple candidates, with ea=
ch candidate corresponding
 to A or AAAA record in DNS query result. We will also need to specify how =
FQDN candidate gets applied to c=3D line address. Something that says IN IP=
4 FQDN, if any A records exist for this DNS name and IN IP6 FQDN if only AA=
AA records exist. Once candidate is
 nominated, address family in c=3D line should match address family used fo=
r communications. This will definitely require a lot more work and discussi=
on.</div>
<div><br>
</div>
<div>b. Specify that FQDN connection addresses should be ignored until thei=
r handling is defined in a future specification. This seems easy and only r=
equires a sentence or two to fix.</div>
<div><br>
</div>
<div>Regards,</div>
<div>_____________<br>
Roman Shpount</div>
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
<div class=3D"gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
<div dir=3D"ltr">
<div class=3D"gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
<div class=3D"gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
<div class=3D"gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
<div class=3D"gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>

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

--0000000000004403690580db84ee--


From nobody Fri Feb  1 13:17:35 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 2D627130ED1 for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 13:17:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.852
X-Spam-Level: 
X-Spam-Status: No, score=-8.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=hbaJl/oE; dkim=pass (1024-bit key) header.d=ericsson.com header.b=VfCFbBkx
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 SZSoHEEjoLuk for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 13:17:30 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 563EF1312CA for <mmusic@ietf.org>; Fri,  1 Feb 2019 13:17:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/relaxed;  q=dns/txt; i=@ericsson.com; t=1549055847; x=1551647847; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=J0InleAtJk46yikHo6O6Zf6T8deC0Yjl5TJz5YBZsgQ=; b=hbaJl/oE4Xy+CpLHvseb/9tqUVnQE92sU8dS0z/5EiTWwH0oR7S8x3sN211YjYHV YH+805mcNWfnek53WL3rEeBc+tjxwmuShEOun8lKZXJIx5rDkQkFg96Yr5IwnJVY zidjVIlCFDx6ELO8+6X2IDS9pCtwxo9ubuLNubbg2S8=;
X-AuditID: c1b4fb25-209009e000005ff7-c1-5c54b7678952
Received: from ESESSMB505.ericsson.se (Unknown_Domain [153.88.183.123]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 86.B5.24567.767B45C5; Fri,  1 Feb 2019 22:17:27 +0100 (CET)
Received: from ESESSMR503.ericsson.se (153.88.183.112) by ESESSMB505.ericsson.se (153.88.183.123) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 1 Feb 2019 22:17:03 +0100
Received: from ESESSMB503.ericsson.se (153.88.183.164) by ESESSMR503.ericsson.se (153.88.183.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 1 Feb 2019 22:17:03 +0100
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB503.ericsson.se (153.88.183.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Fri, 1 Feb 2019 22:17:02 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=J0InleAtJk46yikHo6O6Zf6T8deC0Yjl5TJz5YBZsgQ=; b=VfCFbBkxm8ONFovLGvzK7dwoDUzyCehgikf+eFU0zsMdYK46lhm/kXDbLEDx7I4sY5BLXKdgs+OMFrulaMufI85EjxOeBx3WULxjqOx5r4w6tXtBCP800jnRliZNlctVo3+LuGx1iyhWUaOipFTAKxwE83NVju/dXfRd/BkuzR4=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3212.eurprd07.prod.outlook.com (10.170.246.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1580.13; Fri, 1 Feb 2019 21:16:55 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0%4]) with mapi id 15.20.1601.013; Fri, 1 Feb 2019 21:16:55 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
CC: Justin Uberti <juberti@google.com>, Simon Perreault <sperreault@jive.com>,  "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, "mmusic WG" <mmusic@ietf.org>
Thread-Topic: [rtcweb] [MMUSIC] What goes into c= line address when FQDN is used for the default candidate?
Thread-Index: AQHUulU2uFx8SsiiZk68wi8iILBKkKXLUQeAgAAF3QCAAAwVgIAACK4AgAADoQCAAAJpqQ==
Date: Fri, 1 Feb 2019 21:16:55 +0000
Message-ID: <HE1PR07MB3161679C1754C88B01279A3493920@HE1PR07MB3161.eurprd07.prod.outlook.com>
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com> <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com> <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com>, <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com>
In-Reply-To: <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [37.136.56.89]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR07MB3212; 6:BP2y/87cuLmx+0Hw55gic25xvOFFs561kVwVwa7KBKbEh5P4oEizU3R6Qxqv+xoSz1BW+PkBq+/ogreMW4wBEYb+Bk0fT6tZru9w6gYgw5yQLyy3xy/qu0htruv+vk5qQMKCAgNhffAELrcN3vJoAc7E10eaV9MeKTPnjmPkpRLD8yLjYgDz1+RHATQBsPHrizNLPqWQygqV1k9a9beA5tMKqPoSa9Ktqdff9kUcSDxO7gQGsheoKagIxWmf/erD28FLBFHMDRnHd5B3UbGtBRDKHXOxpFvnRfHKSnP8lknCOeZK/lzG/lKMus7vwoM8XI2wcGc01zIbkPA1h5RGZvpn5q1vLAmbCi8KgWsFO3qAp2W+J2UH9OVfuwshl591p1SMt+pDJ0KwHENs2XAKfk0ykxD9/7bMIX65sOKWQL81Dh03N/G0iS75YZToOR340xUAHGmU/TKA4S9IGOXJbQ==; 5:ef906xqG4BYU1c66olg97fQlSXZvXY169NEV71LuCcFyT7MoYc/pQMMuao4lsDjz9f7jmcPvVpvisF1+uQg58fWs9qGKab1cvGZPqLt/wMr7I/cgXHRrLcGKGNG4NDRL56WI5xmbl5d8UVr06w4Z7XzBhuWOq1kAU1TEY8UaMI5GUU0N0UjwvJN5Rr6X/ANEwF2QB0kjrejSVsbqbyRI/Q==; 7:3wzarknytigYpCLqwtfmvFVJHcJhS/PfdF9r2QDKYdwlKPG+Ep5vtsFnJUDtzP1bNG6T7pxmWq/7jViTj98wJWS9tfksQsMn+q+BuSwy6GDTQtMzBL6tW6b95a+o9lDBKeZql5TH+5qKfRVnX6pYHg==
x-ms-office365-filtering-correlation-id: d08360ff-f4e0-4ff0-1148-08d6888a982c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(2017052603328)(7153060)(7193020); SRVR:HE1PR07MB3212; 
x-ms-traffictypediagnostic: HE1PR07MB3212:
x-microsoft-antispam-prvs: <HE1PR07MB32123DC67C42011105E4879493920@HE1PR07MB3212.eurprd07.prod.outlook.com>
x-forefront-prvs: 09352FD734
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(396003)(346002)(376002)(136003)(366004)(199004)(189003)(6246003)(8676002)(229853002)(6916009)(256004)(6606003)(8936002)(54906003)(81156014)(6436002)(2906002)(53546011)(316002)(6506007)(14454004)(102836004)(5070765005)(106356001)(66066001)(81166006)(53936002)(68736007)(606006)(14444005)(19627405001)(74316002)(71190400001)(478600001)(71200400001)(86362001)(76176011)(105586002)(6116002)(3846002)(1015004)(7696005)(93886005)(7736002)(99286004)(54896002)(6306002)(9686003)(186003)(26005)(55016002)(486006)(236005)(476003)(97736004)(11346002)(44832011)(446003)(33656002)(4326008)(25786009); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3212; 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: nUZof7AElP1kHWrx8JW/Cc/e4pcQG4fRhVzYcMqFGa7L8JRFyd8G+PPCOI6hEsNmoWVtYVM/xxrvfMwrSZHs9teXMd6xbuJDFN0ASNLpSXY8Q14S8GJU6BvOi2yyI4Smy3sFWIpG46J9VYSQ9DZONlTCNmxlP2AAHKhzBJ4gCvcTkSKBfiTzLQACVUr3mpAOLhjwRKf+tZzo1qreeNxwvK/eu2GcVlQb+zp13AZi9up4+gtv/lbVHf0xaaN28AuyMY27sbJU/w6ICd+UWxMulP+p/qc6FADVkxrVMdpM4Qvia4lvimmikhenfzxRaAGYBT8L0palNNTu2pgYZEli/IaBor9CuHbf+jaS6umJIHMdNujoyRWqi2BoG/q91TJsOWYWBeQI9aFharqyDgJRpvxtV8cTDhSOKTdBsr6Uvus=
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB3161679C1754C88B01279A3493920HE1PR07MB3161eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d08360ff-f4e0-4ff0-1148-08d6888a982c
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2019 21:16:55.7581 (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-Transport-CrossTenantHeadersStamped: HE1PR07MB3212
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SbUhTURjHObv37l6Xo+t8e3zLGlrgeyZ4P4TYp4YQJGiK+LbypuJ0tunQ onAGSUoozoHKQkWpMI00TYnQmmKWoZmSNUsUV6JpWLSsrGvbjkXffv///znPc57DYQjZBOXL 5BeV8JoipUoulpBNqQMXwnMHktKj2u/6cP1GGWe8uUxyjS+MBNctVNHc3GwytzquixcrDMM2 QtHaW6ro6PghUgim94TC0lB8kkqTHM3hVfk6XhMZly3Jmx+rQcUmXdl14VIFas+pRi4MsDHQ N7FNVCMJI2NHEWxZKkVY2BD0zNxC/4TpzpfdpF0Etv4rlEOQbB0Bwy2NFE7qRbC28FyMxZL9 TOeavQHDiFkOaoRQx0QPNhh+bxmcrQj2PgLrlGOiC+POquDnh2YCFxVCT+2rXT4FI9O3xQ4m 2SDQm7coB0vZdLBZqkg8bI6G7qEx2hG4sInQ/7bR2RSxXrD1rMvJBOsNFmuLCO/NQsfDKQKz J6wuCxSuV8Jw5+Kuvx+eLFgR5gB42VLjfA1gK2lom6/YDU7AozkDhYM3CITaDQoHIbC2uENj LoCuzR4Ssz8Mfn9H4wP1Yli+XCWuQ+HN/90Qsxo2bF/pZueqbvC0yUpiPwJeGxvEmEPhRttH AnM4NApm8n+/FdGdyFPLa08X5kYfieA1+We0WnVRRBFf0ovsX+xx33bwIJpZP2ZGLIPkrlJ9 Z1K6jFLqtOWFZgQMIfeQWvrtljRHWX6e16izNKUqXmtGfgwp95b+krmly9hcZQlfwPPFvOZv KmJcfCtQ2IPFyaxM03GP5KFA14srosjswJRvCZOzXhlnr7lmRna5raS656znHlBXJ+yLWvoc 364/lJY2uiZZyO7jZqQGhTVlSD0aMa736hLo1cqST+5CnSlmbyBd1XYudI9tc9tgu3dVVZ9Y 5neQyxsJl0SXhgXs+PhPT8TGlvdkBMV5yUltnvJwCKHRKv8A3gL9QF4DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wny3LlbgTpInH6BbIjRxjknBofE>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 01 Feb 2019 21:17:33 -0000

--_000_HE1PR07MB3161679C1754C88B01279A3493920HE1PR07MB3161eurp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hi,

> In this case section 4.1 of ice-sip-sdp should be updated to allow FQDN i=
n
> connection-address and, perhaps specify that FWDN which return multiple
> results should be ignored.

I suggest MUST be ignored, perhaps with a note saying that a future specifi=
cation will have to define how to use FQDNs that return multiple results.

> Would this work for everyone?

It would work for me.

Regards,

Christer



On Fri, Feb 1, 2019 at 4:02 PM Christer Holmberg <christer.holmberg@ericsso=
n.com<mailto:christer.holmberg@ericsson.com>> wrote:

I have no problem with allowing FQDNs - as long as they result in a SINGLE =
address:port.


If we want to define ICE usage of FDNSs resulting in MULTIPLE addresses:por=
ts, I really think that should be a separate document - it should NOT be ad=
ded as a last minute thing to draft-ice-sip-sdp.


...and, yes, perhaps such work would also affect 8445.


Regards,


Christer





________________________________
From: rtcweb <rtcweb-bounces@ietf.org<mailto:rtcweb-bounces@ietf.org>> on b=
ehalf of Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>>
Sent: Friday, February 1, 2019 10:22 PM
To: Justin Uberti
Cc: Simon Perreault; Dale R. Worley; RTCWeb IETF; mmusic WG
Subject: Re: [rtcweb] [MMUSIC] What goes into c=3D line address when FQDN i=
s used for the default candidate?

On Fri, Feb 1, 2019 at 2:39 PM Justin Uberti <juberti@google.com<mailto:jub=
erti@google.com>> wrote:
This has all been discussed at length in rtcweb and I don't think any signi=
ficant changes are needed, although I tend to think that we should restore =
the removed FQDN text from mmusic-ice-sip-sdp, which is the only thing not =
in alignment at this point in time.

I agree that FQDN should be put back into connection-address definition, bu=
t  the portion which talks about handling it is completely broken.

Quoting 5245<https://tools.ietf.org/html/rfc5245#section-15.1>:

   <connection-address>:  is taken from RFC 4566<https://tools.ietf.org/htm=
l/rfc4566> [RFC4566<https://tools.ietf.org/html/rfc4566>].  It is the
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and fully qualified domain names (FQDNs).  When parsing
      this field, an agent can differentiate an IPv4 address and an IPv6


      address by presence of a colon in its value - the presence of a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=3Dcandidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.



I think it was discussed in quite a detail why using a random DNS resolutio=
n result is not going to work here..

The only options we have here are:

a. Fix FQDN connection address handling. Probably the most logical way of d=
ealing with this would be to specify that candidate with FQDN should be con=
verted as a result of DNS resolution into multiple candidates, with each ca=
ndidate corresponding to A or AAAA record in DNS query result. We will also=
 need to specify how FQDN candidate gets applied to c=3D line address. Some=
thing that says IN IP4 FQDN, if any A records exist for this DNS name and I=
N IP6 FQDN if only AAAA records exist. Once candidate is nominated, address=
 family in c=3D line should match address family used for communications. T=
his will definitely require a lot more work and discussion.

b. Specify that FQDN connection addresses should be ignored until their han=
dling is defined in a future specification. This seems easy and only requir=
es a sentence or two to fix.

Regards,
_____________
Roman Shpount

--_000_HE1PR07MB3161679C1754C88B01279A3493920HE1PR07MB3161eurp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<div>Hi,</div>
<div>&nbsp;</div>
<div style=3D"color: rgb(0, 0, 0);">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"></div>
<div>
<div dir=3D"ltr">
<div dir=3D"ltr">&gt; In this case section 4.1 of ice-sip-sdp should be upd=
ated to allow FQDN in&nbsp;</div>
<div dir=3D"ltr">&gt; connection-address and, perhaps specify that FWDN whi=
ch return multiple&nbsp;</div>
<div dir=3D"ltr">&gt; results should be ignored.</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">I suggest MUST be ignored, perhaps with a note saying that=
 a future specification will have to define how to use FQDNs that return mu=
ltiple results.</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">&gt; Would this work for everyone?</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">It would work for me.</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">Regards,</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">Christer</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr"></div>
<br>
<div class=3D"x_gmail_quote">
<div class=3D"x_gmail_attr" dir=3D"ltr">On Fri, Feb 1, 2019 at 4:02 PM Chri=
ster Holmberg &lt;<a class=3D"OWAAutoLink" id=3D"LPlnk584367" href=3D"mailt=
o:christer.holmberg@ericsson.com" previewremoved=3D"true">christer.holmberg=
@ericsson.com</a>&gt; wrote:<br>
</div>
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div dir=3D"ltr">
<div id=3D"x_gmail-m_-7925862921453132447divtagdefaultwrapper" style=3D"fon=
t-size:12pt; color:rgb(0,0,0); font-family:Calibri,Helvetica,sans-serif" di=
r=3D"ltr">
<p style=3D"margin-top:0px; margin-bottom:0px"><span style=3D"font-size:12p=
t">I have no problem with allowing FQDNs - as long as they result in a SING=
LE address:port.</span><br>
</p>
<p style=3D"margin-top:0px; margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px; margin-bottom:0px">If we want to define ICE usa=
ge of FDNSs resulting in MULTIPLE addresses:ports, I really think that shou=
ld be a separate document - it should NOT be added as a last minute thing t=
o draft-ice-sip-sdp.</p>
<p style=3D"margin-top:0px; margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px; margin-bottom:0px">...and, yes, perhaps such wo=
rk would also affect 8445.</p>
<p style=3D"margin-top:0px; margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px; margin-bottom:0px">Regards,</p>
<p style=3D"margin-top:0px; margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px; margin-bottom:0px">Christer</p>
<p style=3D"margin-top:0px; margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px; margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px; margin-bottom:0px"><br>
</p>
<br>
<br>
<div style=3D"color:rgb(0,0,0)">
<hr style=3D"display:inline-block; width:98%">
<div id=3D"x_gmail-m_-7925862921453132447divRplyFwdMsg" dir=3D"ltr"><font c=
olor=3D"#000000" face=3D"Calibri, sans-serif" style=3D"font-size:11pt"><b>F=
rom:</b> rtcweb &lt;<a class=3D"OWAAutoLink" id=3D"LPlnk781442" href=3D"mai=
lto:rtcweb-bounces@ietf.org" target=3D"_blank" previewremoved=3D"true">rtcw=
eb-bounces@ietf.org</a>&gt;
 on behalf of Roman Shpount &lt;<a class=3D"OWAAutoLink" id=3D"LPlnk582413"=
 href=3D"mailto:roman@telurix.com" target=3D"_blank" previewremoved=3D"true=
">roman@telurix.com</a>&gt;<br>
<b>Sent:</b> Friday, February 1, 2019 10:22 PM<br>
<b>To:</b> Justin Uberti<br>
<b>Cc:</b> Simon Perreault; Dale R. Worley; RTCWeb IETF; mmusic WG<br>
<b>Subject:</b> Re: [rtcweb] [MMUSIC] What goes into c=3D line address when=
 FQDN is used for the default candidate?</font>
<div>&nbsp;</div>
</div>
<div>
<div dir=3D"ltr">
<div dir=3D"ltr">
<div>
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_signature" dir=3D"ltr">=
On Fri, Feb 1, 2019 at 2:39 PM Justin Uberti &lt;<a class=3D"x_gmail-m_-792=
5862921453132447OWAAutoLink OWAAutoLink" id=3D"LPlnk66353" href=3D"mailto:j=
uberti@google.com" target=3D"_blank" previewremoved=3D"true">juberti@google=
.com</a>&gt;
 wrote:<br>
</div>
</div>
</div>
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
<div dir=3D"ltr">This has all been discussed at length in rtcweb and I don'=
t think any significant changes are needed, although I tend to think that w=
e should restore the removed FQDN text from mmusic-ice-sip-sdp, which is th=
e only thing not in alignment at this
 point in time.</div>
</blockquote>
<div><br>
</div>
<div>I agree that FQDN should be put back into connection-address definitio=
n, but&nbsp; the portion which talks about handling it is completely broken=
.</div>
<div><br>
</div>
<div>Quoting&nbsp;<a class=3D"x_gmail-m_-7925862921453132447OWAAutoLink OWA=
AutoLink" id=3D"LPlnk302905" href=3D"https://tools.ietf.org/html/rfc5245#se=
ction-15.1" target=3D"_blank" previewremoved=3D"true">5245</a><span style=
=3D"color:rgb(0,0,0)">:</span></div>
<div>
<pre class=3D"x_gmail-m_-7925862921453132447x_gmail-m_7058075087377128197gm=
ail-newpage" style=3D"color:rgb(0,0,0); white-space:pre-wrap; font-size:13.=
3333px; margin-top:0px; margin-bottom:0px; break-before:page">   &lt;connec=
tion-address&gt;:  is taken from <a class=3D"x_gmail-m_-7925862921453132447=
OWAAutoLink OWAAutoLink" id=3D"LPlnk127203" href=3D"https://tools.ietf.org/=
html/rfc4566" target=3D"_blank" previewremoved=3D"true">RFC 4566</a> [<a ti=
tle=3D"&quot;SDP: Session Description Protocol&quot;" class=3D"x_gmail-m_-7=
925862921453132447OWAAutoLink OWAAutoLink" id=3D"LPlnk550807" href=3D"https=
://tools.ietf.org/html/rfc4566" target=3D"_blank" previewremoved=3D"true">R=
FC4566</a>].  It is the=0A=
      IP address of the candidate, allowing for IPv4 addresses, IPv6=0A=
      addresses, and <b>fully qualified domain names (FQDNs).</b>  When par=
sing=0A=
      this field, an agent can differentiate an IPv4 address and an IPv6=0A=
</pre>
<pre class=3D"x_gmail-m_-7925862921453132447x_gmail-m_7058075087377128197gm=
ail-newpage" style=3D"color:rgb(0,0,0); white-space:pre-wrap; font-size:13.=
3333px; margin-top:0px; margin-bottom:0px; break-before:page">      address=
 by presence of a colon in its value - the presence of a=0A=
      colon indicates IPv6.  An agent MUST ignore candidate lines that=0A=
      include candidates with IP address versions that are not supported=0A=
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be=0A=
      used in place of an IP address.  In that case, when receiving an=0A=
      offer or answer containing an FQDN in an a=3Dcandidate attribute,=0A=
      the FQDN is looked up in the DNS first using an AAAA record=0A=
      (assuming the agent supports IPv6), and if no result is found or=0A=
      the agent only supports IPv4, using an A.  If the DNS query=0A=
      returns more than one IP address, one is chosen, and then used for=0A=
      the remainder of ICE processing.=0A=
</pre>
<pre class=3D"x_gmail-m_-7925862921453132447x_gmail-m_7058075087377128197gm=
ail-newpage" style=3D"color:rgb(0,0,0); white-space:pre-wrap; font-size:13.=
3333px; margin-top:0px; margin-bottom:0px; break-before:page"><br></pre>
I think it was discussed in quite a detail why using a random DNS resolutio=
n result is not going to work here..</div>
<div><br>
</div>
<div>The only options we have here are:</div>
<div><br>
</div>
<div>a. Fix FQDN connection address handling. Probably the most logical way=
 of dealing with this would be to specify that candidate with FQDN should b=
e converted as a result of DNS resolution into multiple candidates, with ea=
ch candidate corresponding to A
 or AAAA record in DNS query result. We will also need to specify how FQDN =
candidate gets applied to c=3D line address. Something that says IN IP4 FQD=
N, if any A records exist for this DNS name and IN IP6 FQDN if only AAAA re=
cords exist. Once candidate is nominated,
 address family in c=3D line should match address family used for communica=
tions. This will definitely require a lot more work and discussion.</div>
<div><br>
</div>
<div>b. Specify that FQDN connection addresses should be ignored until thei=
r handling is defined in a future specification. This seems easy and only r=
equires a sentence or two to fix.</div>
<div><br>
</div>
<div>Regards,</div>
<div>_____________<br>
Roman Shpount</div>
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
<div dir=3D"ltr">
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_HE1PR07MB3161679C1754C88B01279A3493920HE1PR07MB3161eurp_--


From nobody Fri Feb  1 14:53:29 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 9C3FC130ECE for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 14:53:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -19.052
X-Spam-Level: 
X-Spam-Status: No, score=-19.052 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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, 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 cveilWfIT29I for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 14:53:26 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D959D130EBE for <mmusic@ietf.org>; Fri,  1 Feb 2019 14:53:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2234; q=dns/txt; s=iport; t=1549061605; x=1550271205; h=from:subject:to:message-id:date:mime-version; bh=JFmWtUJJu6m6qOHnh7hO9Axxmnym8WEiRJ14OtkrBhI=; b=mJ6KCBUvcPpCK+ZNsPtQTjRRoECMSXritgqWkMQG3tTAZcnlNva8QSKx ksUu2QI8EE77lpR5qsrU0tNXivei8vZ3eY1lgkUb4JeqjjyACkdsLCj3f 7eytClXy5hZUGPUNCcZqZL0Pz5tG08cKzdwJwnO7idfkNxgaPVHzO5KPE Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A/AADMzFRc/5xdJa1kHAEBAQQBAQc?= =?us-ascii?q?EAQGBUgYBAQsBggNngQOEKpQOgWCJYYhrhW+Bew0fh2AiNQgNAQMBAQIBAQJ?= =?us-ascii?q?tHAyFdHUBPQJfDQgBAYMeAYF0DQ+aBI52gS8fhA8BgRSESh0FjEAXgUA/gTi?= =?us-ascii?q?GCQIDhGeCVwKRK5E8CYcwiwAGGYFrhUCDF4d+j0+MLIFIAjSBVk0jFYMoix2?= =?us-ascii?q?FXSEDjVoBAQ?=
X-IronPort-AV: E=Sophos;i="5.56,549,1539648000";  d="scan'208,217";a="234897486"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2019 22:53:24 +0000
Received: from [10.118.10.18] (rtp-fandreas-2-881-ap.cisco.com [10.118.10.18]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTP id x11MrO3p025293 for <mmusic@ietf.org>; Fri, 1 Feb 2019 22:53:24 GMT
From: Flemming Andreasen <fandreas@cisco.com>
To: mmusic <mmusic@ietf.org>
Message-ID: <e013d7c6-db6a-c937-b29c-1b24398b5901@cisco.com>
Date: Fri, 1 Feb 2019 17:53:24 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------05752F836DEE36B2DBA1F18C"
Content-Language: en-US
X-Outbound-SMTP-Client: 10.118.10.18, rtp-fandreas-2-881-ap.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9IQvx_SoayT6MYL_dljSnDeRUs4>
Subject: [MMUSIC] Potential IPR on 4566bis
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, 01 Feb 2019 22:53:27 -0000

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

Greetings MMUSIC

We currently do not have any submitted IPR declarations against 
draft-ietf-mmusic-rfc4566bis, however during the AD review of the draft, 
it was noted that IPR declarations were submitted against the original 
RFC 2327, and that those declarations may also apply to RFC 4566 and 
4566bis:

     https://datatracker.ietf.org/ipr/1389/
     https://datatracker.ietf.org/ipr/1372/

If anybody has any concerns with these, please let us know.

In the mean time, the chairs will try to contact the original IPR 
submitter and see if we can get an updated IPR statement (if applicable) 
to 4566bis.

Thanks

-- Flemming (as MMUSIC co-chair)







--------------05752F836DEE36B2DBA1F18C
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">
    Greetings MMUSIC<br>
    <br>
    We currently do not have any submitted IPR declarations against
    draft-ietf-mmusic-rfc4566bis, however during the AD review of the
    draft, it was noted that IPR declarations were submitted against the
    original RFC 2327, and that those declarations may also apply to RFC
    4566 and 4566bis:<br>
    <br>
        <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/ipr/1389/">https://datatracker.ietf.org/ipr/1389/</a><br>
        <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/ipr/1372/">https://datatracker.ietf.org/ipr/1372/</a><br>
    <br>
    If anybody has any concerns with these, please let us know. <br>
    <br>
    In the mean time, the chairs will try to contact the original IPR
    submitter and see if we can get an updated IPR statement (if
    applicable) to 4566bis. <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming (as MMUSIC co-chair)<br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
  </body>
</html>

--------------05752F836DEE36B2DBA1F18C--


From nobody Fri Feb  1 15:28:16 2019
Return-Path: <juberti@google.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 D41CE130F74 for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 15:28:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.641
X-Spam-Level: 
X-Spam-Status: No, score=-17.641 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 vgFVmNs7vHs1 for <mmusic@ietfa.amsl.com>; Fri,  1 Feb 2019 15:28:12 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 5CBCA130F6D for <mmusic@ietf.org>; Fri,  1 Feb 2019 15:28:12 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id b16so7193499ior.1 for <mmusic@ietf.org>; Fri, 01 Feb 2019 15:28:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1ot9NtzC2DaxpHhVI//RiX2SQDQ2wZDVa1JI2nBQD2Q=; b=SRFRMx/bEi5BZWQKo3OW+1XPD1XiPPv16Mzlt1+WR+iFsOCMwgKVxvt8kdli4eHEkB lVlUEs/S9RUgxOS7rXDtDxSjqM5OJ+6VuIw8PXdAXI8erDNlTwlBLQRDgM+kUDdLMT+k OsjYNeIFaAdkjsW7SiQhpIMKBVWGNjvewCwN02f2gNWRY6wyjEQ0+YaLGkzY47g+ypGt HbSxUttex+n2DFFLxf/gnsp7z9mE1hfd9HLcMw5wMF/LJukjmGMOkCkbZaQFRZyCMxTP MbIJKx+YZyPMpqfNJiWZ0YT8cbF2TR1Y/Vu9ym7rE75ZZblTtlG8QNgyLh+KMcl4DxWn tWlQ==
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=1ot9NtzC2DaxpHhVI//RiX2SQDQ2wZDVa1JI2nBQD2Q=; b=ns2Q4+ljDbX5uqbffpSIMYPKQ/M21jqDv1cYrP3OYfx0+3ANT6/36BOyTYY7xdvmXu mRyT2ggyIL99klchXtgOh7nxUf9WB4EMgFBEZ5FHdXiMlJ2bvzyHoeXcjrgF6KC0Pamg O43ocqVavFgnikm6x/ZFJy60r9VjclV4Fq3KuOB0N9CTCxS09oUjQ6rBGGoWHkFZ2D3f mTw6RtrFQy0S9v6XYPGZnAoaGUpxxkivSEdFdwju1L6W5gWD1Er8yEV5DCW6cYZ54HSJ Gxm5EpjuZWk5vINgI2LpaK5WMwXIAnVn1s6/p3+ZLveALYApZK1aDSy+5rnIoxkyBluV TNRw==
X-Gm-Message-State: AHQUAubb1YP8IqdNBWtE44afgUttHuWGYd7WvDB6/hBH2HIpgg5C+GBZ ypD63onoSVMXBwxbQvXmYKQZ+qeFKXgfmSpRXijNbQ==
X-Google-Smtp-Source: AHgI3IYdJUF4HlMD0PRr2IV8iHBKMUWmU/jMa5eKJ6z6FtgTZgD9YEslUDyyw535bAcHFF8/cFccg3FXp7cbiXkm8BE=
X-Received: by 2002:a5e:920d:: with SMTP id y13mr22265000iop.95.1549063691156;  Fri, 01 Feb 2019 15:28:11 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com> <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com> <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com> <HE1PR07MB3161679C1754C88B01279A3493920@HE1PR07MB3161.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB3161679C1754C88B01279A3493920@HE1PR07MB3161.eurprd07.prod.outlook.com>
From: Justin Uberti <juberti@google.com>
Date: Fri, 1 Feb 2019 15:27:56 -0800
Message-ID: <CAOJ7v-2GHOQBxO3nO02pfKRkXq1SUDiZO2GMLvH-vLHv73mRCA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Roman Shpount <roman@telurix.com>, Simon Perreault <sperreault@jive.com>,  "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000c703c0580dd7ff3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/m3gIlpug9VJa7bGKuyJrnmEN5zY>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 01 Feb 2019 23:28:15 -0000

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

That works for me as well - it then becomes a clarification of 5245, rather
than a removal of functionality.

On Fri, Feb 1, 2019 at 1:17 PM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>
> Hi,
>
> > In this case section 4.1 of ice-sip-sdp should be updated to allow FQDN
> in
> > connection-address and, perhaps specify that FWDN which return multiple
> > results should be ignored.
>
> I suggest MUST be ignored, perhaps with a note saying that a future
> specification will have to define how to use FQDNs that return multiple
> results.
>
> > Would this work for everyone?
>
> It would work for me.
>
> Regards,
>
> Christer
>
>
>
> On Fri, Feb 1, 2019 at 4:02 PM Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
> I have no problem with allowing FQDNs - as long as they result in a SINGLE
> address:port.
>
>
> If we want to define ICE usage of FDNSs resulting in MULTIPLE
> addresses:ports, I really think that should be a separate document - it
> should NOT be added as a last minute thing to draft-ice-sip-sdp.
>
>
> ...and, yes, perhaps such work would also affect 8445.
>
>
> Regards,
>
>
> Christer
>
>
>
>
>
>
> ------------------------------
> *From:* rtcweb <rtcweb-bounces@ietf.org> on behalf of Roman Shpount <
> roman@telurix.com>
> *Sent:* Friday, February 1, 2019 10:22 PM
> *To:* Justin Uberti
> *Cc:* Simon Perreault; Dale R. Worley; RTCWeb IETF; mmusic WG
> *Subject:* Re: [rtcweb] [MMUSIC] What goes into c= line address when FQDN
> is used for the default candidate?
>
> On Fri, Feb 1, 2019 at 2:39 PM Justin Uberti <juberti@google.com> wrote:
>
> This has all been discussed at length in rtcweb and I don't think any
> significant changes are needed, although I tend to think that we should
> restore the removed FQDN text from mmusic-ice-sip-sdp, which is the only
> thing not in alignment at this point in time.
>
>
> I agree that FQDN should be put back into connection-address definition,
> but  the portion which talks about handling it is completely broken.
>
> Quoting 5245 <https://tools.ietf.org/html/rfc5245#section-15.1>:
>
>    <connection-address>:  is taken from RFC 4566 <https://tools.ietf.org/html/rfc4566> [RFC4566 <https://tools.ietf.org/html/rfc4566>].  It is the
>       IP address of the candidate, allowing for IPv4 addresses, IPv6
>       addresses, and *fully qualified domain names (FQDNs).*  When parsing
>       this field, an agent can differentiate an IPv4 address and an IPv6
>
>       address by presence of a colon in its value - the presence of a
>       colon indicates IPv6.  An agent MUST ignore candidate lines that
>       include candidates with IP address versions that are not supported
>       or recognized.  An IP address SHOULD be used, but an FQDN MAY be
>       used in place of an IP address.  In that case, when receiving an
>       offer or answer containing an FQDN in an a=candidate attribute,
>       the FQDN is looked up in the DNS first using an AAAA record
>       (assuming the agent supports IPv6), and if no result is found or
>       the agent only supports IPv4, using an A.  If the DNS query
>       returns more than one IP address, one is chosen, and then used for
>       the remainder of ICE processing.
>
>
> I think it was discussed in quite a detail why using a random DNS
> resolution result is not going to work here..
>
> The only options we have here are:
>
> a. Fix FQDN connection address handling. Probably the most logical way of
> dealing with this would be to specify that candidate with FQDN should be
> converted as a result of DNS resolution into multiple candidates, with each
> candidate corresponding to A or AAAA record in DNS query result. We will
> also need to specify how FQDN candidate gets applied to c= line address.
> Something that says IN IP4 FQDN, if any A records exist for this DNS name
> and IN IP6 FQDN if only AAAA records exist. Once candidate is nominated,
> address family in c= line should match address family used for
> communications. This will definitely require a lot more work and discussion.
>
> b. Specify that FQDN connection addresses should be ignored until their
> handling is defined in a future specification. This seems easy and only
> requires a sentence or two to fix.
>
> Regards,
> _____________
> Roman Shpount
>
>

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

<div dir=3D"ltr"><div>That works for me as well - it then becomes a clarifi=
cation of 5245, rather than a removal of functionality.</div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 1, 2019 =
at 1:17 PM Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericss=
on.com">christer.holmberg@ericsson.com</a>&gt; wrote:<br></div><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 id=3D"gmail-m_4281477119354329881divtagdefaultwrapper" style=3D"font-s=
ize:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif" dir=3D"=
ltr">
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<div>Hi,</div>
<div>=C2=A0</div>
<div style=3D"color:rgb(0,0,0)">
<div id=3D"gmail-m_4281477119354329881divRplyFwdMsg" dir=3D"ltr"></div>
<div>
<div dir=3D"ltr">
<div dir=3D"ltr">&gt; In this case section 4.1 of ice-sip-sdp should be upd=
ated to allow FQDN in=C2=A0</div>
<div dir=3D"ltr">&gt; connection-address and, perhaps specify that FWDN whi=
ch return multiple=C2=A0</div>
<div dir=3D"ltr">&gt; results should be ignored.</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">I suggest MUST be ignored, perhaps with a note saying that=
 a future specification will have to define how to use FQDNs that return mu=
ltiple results.</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">&gt; Would this work for everyone?</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">It would work for me.</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">Regards,</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">Christer</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr"></div>
<br>
<div class=3D"gmail-m_4281477119354329881x_gmail_quote">
<div class=3D"gmail-m_4281477119354329881x_gmail_attr" dir=3D"ltr">On Fri, =
Feb 1, 2019 at 4:02 PM Christer Holmberg &lt;<a class=3D"gmail-m_4281477119=
354329881OWAAutoLink" id=3D"gmail-m_4281477119354329881LPlnk584367" href=3D=
"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christer.holmberg=
@ericsson.com</a>&gt; wrote:<br>
</div>
<blockquote class=3D"gmail-m_4281477119354329881x_gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">
<div dir=3D"ltr">
<div id=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447divtagd=
efaultwrapper" style=3D"font-size:12pt;color:rgb(0,0,0);font-family:Calibri=
,Helvetica,sans-serif" dir=3D"ltr">
<p style=3D"margin-top:0px;margin-bottom:0px"><span style=3D"font-size:12pt=
">I have no problem with allowing FQDNs - as long as they result in a SINGL=
E address:port.</span><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px">If we want to define ICE usag=
e of FDNSs resulting in MULTIPLE addresses:ports, I really think that shoul=
d be a separate document - it should NOT be added as a last minute thing to=
 draft-ice-sip-sdp.</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px">...and, yes, perhaps such wor=
k would also affect 8445.</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px">Regards,</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px">Christer</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<br>
<br>
<div style=3D"color:rgb(0,0,0)">
<hr style=3D"display:inline-block;width:98%">
<div id=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447divRply=
FwdMsg" dir=3D"ltr"><font color=3D"#000000" face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt"><b>From:</b> rtcweb &lt;<a class=3D"gmail-m_42814771=
19354329881OWAAutoLink" id=3D"gmail-m_4281477119354329881LPlnk781442" href=
=3D"mailto:rtcweb-bounces@ietf.org" target=3D"_blank">rtcweb-bounces@ietf.o=
rg</a>&gt;
 on behalf of Roman Shpount &lt;<a class=3D"gmail-m_4281477119354329881OWAA=
utoLink" id=3D"gmail-m_4281477119354329881LPlnk582413" href=3D"mailto:roman=
@telurix.com" target=3D"_blank">roman@telurix.com</a>&gt;<br>
<b>Sent:</b> Friday, February 1, 2019 10:22 PM<br>
<b>To:</b> Justin Uberti<br>
<b>Cc:</b> Simon Perreault; Dale R. Worley; RTCWeb IETF; mmusic WG<br>
<b>Subject:</b> Re: [rtcweb] [MMUSIC] What goes into c=3D line address when=
 FQDN is used for the default candidate?</font>
<div>=C2=A0</div>
</div>
<div>
<div dir=3D"ltr">
<div dir=3D"ltr">
<div>
<div class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447x_gm=
ail_signature" dir=3D"ltr">On Fri, Feb 1, 2019 at 2:39 PM Justin Uberti &lt=
;<a class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447OWAAu=
toLink gmail-m_4281477119354329881OWAAutoLink" id=3D"gmail-m_42814771193543=
29881LPlnk66353" href=3D"mailto:juberti@google.com" target=3D"_blank">juber=
ti@google.com</a>&gt;
 wrote:<br>
</div>
</div>
</div>
<div class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447x_gm=
ail_quote">
<blockquote class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132=
447x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
<div dir=3D"ltr">This has all been discussed at length in rtcweb and I don&=
#39;t think any significant changes are needed, although I tend to think th=
at we should restore the removed FQDN text from mmusic-ice-sip-sdp, which i=
s the only thing not in alignment at this
 point in time.</div>
</blockquote>
<div><br>
</div>
<div>I agree that FQDN should be put back into connection-address definitio=
n, but=C2=A0 the portion which talks about handling it is completely broken=
.</div>
<div><br>
</div>
<div>Quoting=C2=A0<a class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862=
921453132447OWAAutoLink gmail-m_4281477119354329881OWAAutoLink" id=3D"gmail=
-m_4281477119354329881LPlnk302905" href=3D"https://tools.ietf.org/html/rfc5=
245#section-15.1" target=3D"_blank">5245</a><span style=3D"color:rgb(0,0,0)=
">:</span></div>
<div>
<pre class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447x_gm=
ail-m_7058075087377128197gmail-newpage" style=3D"color:rgb(0,0,0);white-spa=
ce:pre-wrap;font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-befo=
re:page">   &lt;connection-address&gt;:  is taken from <a class=3D"gmail-m_=
4281477119354329881x_gmail-m_-7925862921453132447OWAAutoLink gmail-m_428147=
7119354329881OWAAutoLink" id=3D"gmail-m_4281477119354329881LPlnk127203" hre=
f=3D"https://tools.ietf.org/html/rfc4566" target=3D"_blank">RFC 4566</a> [<=
a title=3D"&quot;SDP: Session Description Protocol&quot;" class=3D"gmail-m_=
4281477119354329881x_gmail-m_-7925862921453132447OWAAutoLink gmail-m_428147=
7119354329881OWAAutoLink" id=3D"gmail-m_4281477119354329881LPlnk550807" hre=
f=3D"https://tools.ietf.org/html/rfc4566" target=3D"_blank">RFC4566</a>].  =
It is the
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and <b>fully qualified domain names (FQDNs).</b>  When par=
sing
      this field, an agent can differentiate an IPv4 address and an IPv6
</pre>
<pre class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447x_gm=
ail-m_7058075087377128197gmail-newpage" style=3D"color:rgb(0,0,0);white-spa=
ce:pre-wrap;font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-befo=
re:page">      address by presence of a colon in its value - the presence o=
f a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=3Dcandidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.
</pre>
<pre class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447x_gm=
ail-m_7058075087377128197gmail-newpage" style=3D"color:rgb(0,0,0);white-spa=
ce:pre-wrap;font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-befo=
re:page"><br></pre>
I think it was discussed in quite a detail why using a random DNS resolutio=
n result is not going to work here..</div>
<div><br>
</div>
<div>The only options we have here are:</div>
<div><br>
</div>
<div>a. Fix FQDN connection address handling. Probably the most logical way=
 of dealing with this would be to specify that candidate with FQDN should b=
e converted as a result of DNS resolution into multiple candidates, with ea=
ch candidate corresponding to A
 or AAAA record in DNS query result. We will also need to specify how FQDN =
candidate gets applied to c=3D line address. Something that says IN IP4 FQD=
N, if any A records exist for this DNS name and IN IP6 FQDN if only AAAA re=
cords exist. Once candidate is nominated,
 address family in c=3D line should match address family used for communica=
tions. This will definitely require a lot more work and discussion.</div>
<div><br>
</div>
<div>b. Specify that FQDN connection addresses should be ignored until thei=
r handling is defined in a future specification. This seems easy and only r=
equires a sentence or two to fix.</div>
<div><br>
</div>
<div>Regards,</div>
<div>_____________<br>
Roman Shpount</div>
<blockquote class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132=
447x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
<div class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447x_gm=
ail_quote">
<blockquote class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132=
447x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
<div dir=3D"ltr">
<div class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447x_gm=
ail_quote">
<blockquote class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132=
447x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
<div class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447x_gm=
ail_quote">
<blockquote class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132=
447x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
<div class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447x_gm=
ail_quote">
<blockquote class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132=
447x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
<div class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132447x_gm=
ail_quote">
<blockquote class=3D"gmail-m_4281477119354329881x_gmail-m_-7925862921453132=
447x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>

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

--0000000000000c703c0580dd7ff3--


From nobody Tue Feb  5 07:04:02 2019
Return-Path: <alan.ford@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 681FE12D4EF; Tue,  5 Feb 2019 07:03:53 -0800 (PST)
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_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 8-mKvWZFfNRI; Tue,  5 Feb 2019 07:03:50 -0800 (PST)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 D2C5B128CF3; Tue,  5 Feb 2019 07:03:49 -0800 (PST)
Received: by mail-lf1-x130.google.com with SMTP id z26so2882119lfj.6; Tue, 05 Feb 2019 07:03:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=owExOrfkKjs/wCjN5kHmH+mHynDVt0DON6xDWz+TcX4=; b=NU0CrmYinnNr9NHoiZiltcBGCDdDvbfIMQ65nYAO3vbkG6OOiEKdIwYhML2xKd00jB pO5b4csuQ0CaD1A0kGzHW5RtGYd8LwBewWM61bPrygAXOV6LWcVVyy+0J/6UB8E94H9i 4uAiAd+YklyX6oGQFRedodTWMQTxyMdlJTLNcbLIV/WBITf/YFdk42VICI93j1A7RC2U opvhATMyLkwyLb4zD7xNPJ5HXLieoHD2SltiZ0FgkcN6Drpw4UbpCoW2hcUAbiVToahw tKWQamyphicThCOCY+f4gnXcj/KLEWdVgAuIlSqLdcgAPKyP+wuobDj/573rJEXjWzUq rsDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=owExOrfkKjs/wCjN5kHmH+mHynDVt0DON6xDWz+TcX4=; b=TLw16q+Yz4t0HP8/YmnTukVQjM8YDWDA5HSaz/XlTuZPoRHo2XH+GVx07PFpwTmxU+ zU6jTpDnbyIJinZ0LyfxQFXZha4RD1q6LpAvnYGyk5PX0XTMG/xXRjIRLpOCPR70r3Cp jHbOktZQFygc97bBvVFoP0+yNkxm0MhFrWw9xEJ+C+jTyufSqrx7PTAwoc9f/MgbHXfY HNXYO0STbrXQ7/A75hcIIAY1FymWamLfwBUhURP9FyYhpeg/k2Bvjuzyha++uI3qZgGE T/lCfz6RCSQUd1AVcdtrEfF6jxpJVUdkOAD1CXvLrAMccTLTRlEyC0BrM6VmkTb5YgIN RBAg==
X-Gm-Message-State: AHQUAua0Ujj3VsusSDARwxg8yW1OFUTVYrXQyJVf2VlgAAoxGCEKNArW fibgl5ZDSCC0WufSl6f5S5s=
X-Google-Smtp-Source: AHgI3Ibi4gH6z0SIjn2NjhT129hNKcBq49ekleyaPpz9sL6MAsQ5RdA73wUJwJ6wmSVKJVvl4TXghw==
X-Received: by 2002:a19:d1d2:: with SMTP id i201mr3365742lfg.136.1549379027942;  Tue, 05 Feb 2019 07:03:47 -0800 (PST)
Received: from [192.168.1.66] ([31.185.193.196]) by smtp.gmail.com with ESMTPSA id y24-v6sm3271987ljd.20.2019.02.05.07.03.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Feb 2019 07:03:45 -0800 (PST)
From: Alan Ford <alan.ford@gmail.com>
Message-Id: <24551658-0943-431C-B319-D74B5DC169B9@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D52ECA0E-FEE4-4068-9E22-7E0B9B278114"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 5 Feb 2019 15:03:41 +0000
In-Reply-To: <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, Simon Perreault <sperreault@jive.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
To: Roman Shpount <roman@telurix.com>
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com> <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com> <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/W7IwT_wN7QH9_Hh4OxyVay_80cQ>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 05 Feb 2019 15:03:53 -0000

--Apple-Mail=_D52ECA0E-FEE4-4068-9E22-7E0B9B278114
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

If that update was to be made, this goes against the text in =
draft-ietf-rtcweb-mdns-ice-candidates-02 which says:

   An ICE agent that supports mDNS candidates MUST support the situation
   where the hostname resolution results in more than one IP address.
   In this case, the ICE agent MUST take exactly one of the resolved IP
   addresses and ignore the others.  The ICE agent SHOULD, if available,
   use the first IPv6 address resolved, otherwise the first IPv4
   address.

But there=E2=80=99s a bigger problem here, which is how to cope with an =
FQDN is not resolvable. So the intention, as I understand it, is that =
when these host candidates leave the mDNS domain and are thus not =
resolvable, they will be treated as peer reflexive candidates.

But at that point there is no address family information available, so =
how does an ICE agent know to do pairing with these candidates, which =
requires the address family to be known?

Regards,
Alan

> On 1 Feb 2019, at 21:06, Roman Shpount <roman@telurix.com> wrote:
>=20
> In this case section 4.1 of ice-sip-sdp should be updated to allow =
FQDN in connection-address and, perhaps specify that FWDN which return =
multiple results should be ignored.
>=20
> Would this work for everyone?
>=20
> Regards,
> _____________
> Roman Shpount
>=20
>=20
> On Fri, Feb 1, 2019 at 4:02 PM Christer Holmberg =
<christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>> =
wrote:
> I have no problem with allowing FQDNs - as long as they result in a =
SINGLE address:port.
>=20
> If we want to define ICE usage of FDNSs resulting in MULTIPLE =
addresses:ports, I really think that should be a separate document - it =
should NOT be added as a last minute thing to draft-ice-sip-sdp.
>=20
> ...and, yes, perhaps such work would also affect 8445.
>=20
> Regards,
>=20
> Christer
>=20
>=20
>=20
>=20
>=20
> From: rtcweb <rtcweb-bounces@ietf.org =
<mailto:rtcweb-bounces@ietf.org>> on behalf of Roman Shpount =
<roman@telurix.com <mailto:roman@telurix.com>>
> Sent: Friday, February 1, 2019 10:22 PM
> To: Justin Uberti
> Cc: Simon Perreault; Dale R. Worley; RTCWeb IETF; mmusic WG
> Subject: Re: [rtcweb] [MMUSIC] What goes into c=3D line address when =
FQDN is used for the default candidate?
> =20
> On Fri, Feb 1, 2019 at 2:39 PM Justin Uberti <juberti@google.com =
<mailto:juberti@google.com>> wrote:
> This has all been discussed at length in rtcweb and I don't think any =
significant changes are needed, although I tend to think that we should =
restore the removed FQDN text from mmusic-ice-sip-sdp, which is the only =
thing not in alignment at this point in time.
>=20
> I agree that FQDN should be put back into connection-address =
definition, but  the portion which talks about handling it is completely =
broken..
>=20
> Quoting 5245 <https://tools.ietf.org/html/rfc5245#section-15.1>:
>    <connection-address>:  is taken from RFC 4566 =
<https://tools.ietf.org/html/rfc4566> [RFC4566 =
<https://tools.ietf.org/html/rfc4566>].  It is the
>       IP address of the candidate, allowing for IPv4 addresses, IPv6
>       addresses, and fully qualified domain names (FQDNs).  When =
parsing
>       this field, an agent can differentiate an IPv4 address and an =
IPv6
>       address by presence of a colon in its value - the presence of a
>       colon indicates IPv6.  An agent MUST ignore candidate lines that
>       include candidates with IP address versions that are not =
supported
>       or recognized.  An IP address SHOULD be used, but an FQDN MAY be
>       used in place of an IP address.  In that case, when receiving an
>       offer or answer containing an FQDN in an a=3Dcandidate =
attribute,
>       the FQDN is looked up in the DNS first using an AAAA record
>       (assuming the agent supports IPv6), and if no result is found or
>       the agent only supports IPv4, using an A.  If the DNS query
>       returns more than one IP address, one is chosen, and then used =
for
>       the remainder of ICE processing.
>=20
> I think it was discussed in quite a detail why using a random DNS =
resolution result is not going to work here..
>=20
> The only options we have here are:
>=20
> a. Fix FQDN connection address handling. Probably the most logical way =
of dealing with this would be to specify that candidate with FQDN should =
be converted as a result of DNS resolution into multiple candidates, =
with each candidate corresponding to A or AAAA record in DNS query =
result. We will also need to specify how FQDN candidate gets applied to =
c=3D line address. Something that says IN IP4 FQDN, if any A records =
exist for this DNS name and IN IP6 FQDN if only AAAA records exist. Once =
candidate is nominated, address family in c=3D line should match address =
family used for communications. This will definitely require a lot more =
work and discussion.
>=20
> b. Specify that FQDN connection addresses should be ignored until =
their handling is defined in a future specification. This seems easy and =
only requires a sentence or two to fix.
>=20
> Regards,
> _____________
> Roman Shpount
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


--Apple-Mail=_D52ECA0E-FEE4-4068-9E22-7E0B9B278114
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"">If =
that update was to be made, this goes against the text =
in&nbsp;draft-ietf-rtcweb-mdns-ice-candidates-02 which says:<div =
class=3D""><br class=3D""></div><div class=3D""><span style=3D"font-size: =
11px;" class=3D""><font face=3D"Menlo" class=3D"">&nbsp; &nbsp;An ICE =
agent that supports mDNS candidates MUST support the situation<br =
class=3D"">&nbsp; &nbsp;where the hostname resolution results in more =
than one IP address.<br class=3D"">&nbsp; &nbsp;In this case, the ICE =
agent MUST take exactly one of the resolved IP<br class=3D"">&nbsp; =
&nbsp;addresses and ignore the others. &nbsp;The ICE agent SHOULD, if =
available,<br class=3D"">&nbsp; &nbsp;use the first IPv6 address =
resolved, otherwise the first IPv4<br class=3D"">&nbsp; =
&nbsp;address.</font></span><br class=3D""><div><br =
class=3D""></div><div>But there=E2=80=99s a bigger problem here, which =
is how to cope with an FQDN is not resolvable. So the intention, as I =
understand it, is that when these host candidates leave the mDNS domain =
and are thus not resolvable, they will be treated as peer reflexive =
candidates.</div><div><br class=3D""></div><div>But at that point there =
is no address family information available, so how does an ICE agent =
know to do pairing with these candidates, which requires the address =
family to be known?</div><div><br =
class=3D""></div><div>Regards,</div><div>Alan</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On 1 Feb =
2019, at 21:06, Roman Shpount &lt;<a href=3D"mailto:roman@telurix.com" =
class=3D"">roman@telurix.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D""><div dir=3D"ltr" class=3D"">In this case section 4.1 of =
ice-sip-sdp should be updated to allow FQDN in connection-address and, =
perhaps specify that FWDN which return multiple results should be =
ignored.</div><div dir=3D"ltr" class=3D""><br class=3D""></div><div =
dir=3D"ltr" class=3D"">Would this work for everyone?</div><div dir=3D"ltr"=
 class=3D""><br class=3D""></div><div dir=3D"ltr" class=3D"">Regards,<br =
clear=3D"all" class=3D""><div class=3D""><div dir=3D"ltr" =
class=3D"gmail_signature" =
data-smartmail=3D"gmail_signature">_____________<br class=3D"">Roman =
Shpount</div></div><br class=3D""></div><br class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb =
1, 2019 at 4:02 PM Christer Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com" =
class=3D"">christer.holmberg@ericsson.com</a>&gt; wrote:<br =
class=3D""></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 dir=3D"ltr" class=3D"">
<div id=3D"gmail-m_-7925862921453132447divtagdefaultwrapper" =
style=3D"font-size: 12pt; font-family: Calibri, Helvetica, sans-serif;" =
dir=3D"ltr" class=3D""><div style=3D"margin-top: 0px; margin-bottom: =
0px;" class=3D""><span style=3D"font-size:12pt" class=3D"">I have no =
problem with allowing FQDNs - as long as they result in a SINGLE =
address:port.</span><br class=3D""></div><div style=3D"margin-top: 0px; =
margin-bottom: 0px;" class=3D""><br class=3D"">
</div><div style=3D"margin-top: 0px; margin-bottom: 0px;" class=3D"">If =
we want to define ICE usage of FDNSs resulting in MULTIPLE =
addresses:ports, I really think that should be a separate document - it =
should NOT be added as a last minute thing to =
draft-ice-sip-sdp.</div><div style=3D"margin-top: 0px; margin-bottom: =
0px;" class=3D""><br class=3D"">
</div><div style=3D"margin-top: 0px; margin-bottom: 0px;" =
class=3D"">...and, yes, perhaps such work would also affect =
8445.</div><div style=3D"margin-top: 0px; margin-bottom: 0px;" =
class=3D""><br class=3D"">
</div><div style=3D"margin-top: 0px; margin-bottom: 0px;" =
class=3D"">Regards,</div><div style=3D"margin-top: 0px; margin-bottom: =
0px;" class=3D""><br class=3D"">
</div><div style=3D"margin-top: 0px; margin-bottom: 0px;" =
class=3D"">Christer</div><div style=3D"margin-top: 0px; margin-bottom: =
0px;" class=3D""><br class=3D"">
</div><div style=3D"margin-top: 0px; margin-bottom: 0px;" class=3D""><br =
class=3D"">
</div><div style=3D"margin-top: 0px; margin-bottom: 0px;" class=3D""><br =
class=3D"">
</div>
<br class=3D"">
<br class=3D"">
<div style=3D"" class=3D"">
<hr style=3D"display:inline-block;width:98%" class=3D"">
<div id=3D"gmail-m_-7925862921453132447divRplyFwdMsg" dir=3D"ltr" =
class=3D""><font face=3D"Calibri, sans-serif" style=3D"font-size:11pt" =
class=3D""><b class=3D"">From:</b> rtcweb &lt;<a =
href=3D"mailto:rtcweb-bounces@ietf.org" target=3D"_blank" =
class=3D"">rtcweb-bounces@ietf.org</a>&gt; on behalf of Roman Shpount =
&lt;<a href=3D"mailto:roman@telurix.com" target=3D"_blank" =
class=3D"">roman@telurix.com</a>&gt;<br class=3D"">
<b class=3D"">Sent:</b> Friday, February 1, 2019 10:22 PM<br class=3D"">
<b class=3D"">To:</b> Justin Uberti<br class=3D"">
<b class=3D"">Cc:</b> Simon Perreault; Dale R. Worley; RTCWeb IETF; =
mmusic WG<br class=3D"">
<b class=3D"">Subject:</b> Re: [rtcweb] [MMUSIC] What goes into c=3D =
line address when FQDN is used for the default candidate?</font>
<div class=3D"">&nbsp;</div>
</div>
<div class=3D"">
<div dir=3D"ltr" class=3D"">
<div dir=3D"ltr" class=3D"">
<div class=3D"">
<div class=3D"gmail-m_-7925862921453132447x_gmail_signature" =
dir=3D"ltr">On Fri, Feb 1, 2019 at 2:39 PM Justin Uberti &lt;<a =
class=3D"gmail-m_-7925862921453132447OWAAutoLink" =
id=3D"gmail-m_-7925862921453132447LPlnk701075" =
href=3D"mailto:juberti@google.com" =
target=3D"_blank">juberti@google.com</a>&gt; wrote:<br class=3D"">
</div>
</div>
</div>
<div class=3D"gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
<div dir=3D"ltr" class=3D"">This has all been discussed at length in =
rtcweb and I don't think any significant changes are needed, although I =
tend to think that we should restore the removed FQDN text from =
mmusic-ice-sip-sdp, which is the only thing not in alignment at this
 point in time.</div>
</blockquote>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I agree that FQDN should be put back into =
connection-address definition, but&nbsp; the portion which talks about =
handling it is completely broken..</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Quoting&nbsp;<a =
class=3D"gmail-m_-7925862921453132447OWAAutoLink" =
id=3D"gmail-m_-7925862921453132447LPlnk401396" =
href=3D"https://tools.ietf.org/html/rfc5245#section-15.1" =
target=3D"_blank">5245</a><span style=3D"" class=3D"">:</span></div>
<div class=3D"">
<pre =
class=3D"gmail-m_-7925862921453132447x_gmail-m_7058075087377128197gmail-ne=
wpage" style=3D"white-space: pre-wrap; font-size: 13.3333px; margin-top: =
0px; margin-bottom: 0px; break-before: page;">   =
&lt;connection-address&gt;:  is taken from <a =
class=3D"gmail-m_-7925862921453132447OWAAutoLink" =
id=3D"gmail-m_-7925862921453132447LPlnk554019" =
href=3D"https://tools.ietf.org/html/rfc4566" target=3D"_blank">RFC =
4566</a> [<a title=3D"&quot;SDP: Session Description Protocol&quot;" =
class=3D"gmail-m_-7925862921453132447OWAAutoLink" =
id=3D"gmail-m_-7925862921453132447LPlnk297636" =
href=3D"https://tools.ietf.org/html/rfc4566" =
target=3D"_blank">RFC4566</a>].  It is the
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and <b class=3D"">fully qualified domain names =
(FQDNs).</b>  When parsing
      this field, an agent can differentiate an IPv4 address and an IPv6
</pre>
<pre =
class=3D"gmail-m_-7925862921453132447x_gmail-m_7058075087377128197gmail-ne=
wpage" style=3D"white-space: pre-wrap; font-size: 13.3333px; margin-top: =
0px; margin-bottom: 0px; break-before: page;">      address by presence =
of a colon in its value - the presence of a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=3Dcandidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.
</pre>
<pre =
class=3D"gmail-m_-7925862921453132447x_gmail-m_7058075087377128197gmail-ne=
wpage" style=3D"white-space: pre-wrap; font-size: 13.3333px; margin-top: =
0px; margin-bottom: 0px; break-before: page;"><br class=3D""></pre>
I think it was discussed in quite a detail why using a random DNS =
resolution result is not going to work here..</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">The only options we have here are:</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">a. Fix FQDN connection address handling. Probably the =
most logical way of dealing with this would be to specify that candidate =
with FQDN should be converted as a result of DNS resolution into =
multiple candidates, with each candidate corresponding
 to A or AAAA record in DNS query result. We will also need to specify =
how FQDN candidate gets applied to c=3D line address. Something that =
says IN IP4 FQDN, if any A records exist for this DNS name and IN IP6 =
FQDN if only AAAA records exist. Once candidate is
 nominated, address family in c=3D line should match address family used =
for communications. This will definitely require a lot more work and =
discussion.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">b. Specify that FQDN connection addresses should be =
ignored until their handling is defined in a future specification. This =
seems easy and only requires a sentence or two to fix.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Regards,</div>
<div class=3D"">_____________<br class=3D"">
Roman Shpount</div>
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
<div class=3D"gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
<div dir=3D"ltr" class=3D"">
<div class=3D"gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
<div class=3D"gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
<div class=3D"gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
<div class=3D"gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"gmail-m_-7925862921453132447x_gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>

</blockquote></div></div>
_______________________________________________<br class=3D"">mmusic =
mailing list<br class=3D""><a href=3D"mailto:mmusic@ietf.org" =
class=3D"">mmusic@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/mmusic<br =
class=3D""></div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_D52ECA0E-FEE4-4068-9E22-7E0B9B278114--


From nobody Tue Feb  5 10:19:27 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 85C121311B5 for <mmusic@ietfa.amsl.com>; Tue,  5 Feb 2019 10:19:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.031
X-Spam-Level: 
X-Spam-Status: No, score=-2.031 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 iCUP-HFUr4rh for <mmusic@ietfa.amsl.com>; Tue,  5 Feb 2019 10:19:19 -0800 (PST)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (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 4C39C1311D7 for <mmusic@ietf.org>; Tue,  5 Feb 2019 10:19:19 -0800 (PST)
Received: by mail-pg1-x531.google.com with SMTP id d72so1720937pga.9 for <mmusic@ietf.org>; Tue, 05 Feb 2019 10:19:19 -0800 (PST)
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=5C7Wzh1W2jkgNal52qiy3718jGsLLm53TwMcxaUG1jI=; b=q2kGLaBq55xRiugKR0/C+IeJgryuM8x9QjCIwd9nUEJjLXqemV630s+BNKPp5vXvDK mDwNS0BNbb4vJdUGgM1pW/cjMqpFWjJhu7j2MxOXDTm2dVkMw+bJ/lPfxQQz3xxDt01H dFuQBnIcsLx3wc0z0Kh+vV+15skhOAB4QxLCChKd5iy1Wq/wWdyzUs2UrMYaFMR2U8zb mR2ENhScWrQ4pjggIMM7JmZxGGHL8eRnTP3WdvH5xTP4AcHXih6IXWuEFqbJZTcRBtQK 8rYAwYIQBLaud1BAuCShKLT6LfznqPU8sdzUfyDhjDVeYwAQ/4bn8mxLM3DpyCI2ObZa kTDA==
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=5C7Wzh1W2jkgNal52qiy3718jGsLLm53TwMcxaUG1jI=; b=leDS9pYowOqn661t+rwrsFGBYbotLnTpbEmdBTZMvnnfEn1O8f52OnxK3B4qpMydyd liGEkxIgkSnUX2RQ1bS5jgdUnvKOWx8QvY3FbK1RMVrIw8lhLLbPSsjiQHLwTD9o980i Z05Non7i0An97WTv/sFg9IxYF47GMH4CNtP9rScL7RwMluJjSBVQ8zngYYQGKO7hj0SM XAbOP1q5wyYN8F+3sO6nRQUEfPx45FymSa8klnME9POBzgm0GeHf2c/uaHqNgiVsIQM/ ABYoTJhZZK343LO32mWdaZm/30LKlDMVjHX6Ow7whTCJrNpfJwZCc8H2nO0jVwmF1rpD JESA==
X-Gm-Message-State: AHQUAuaxgj/ZGgLEfhdih/ZkAa2l0a+QD8WPmzK68XCTTaMU0KRcvczG Esth5u2Jhtu6mqAd4WHHQcQ9bQ==
X-Google-Smtp-Source: AHgI3Ia0+ZXEFkbGFM/uf/Lxu7wWrB2j+kAuFQYpYX9UUl0NC/xluV4LBjLr8c0pqaGpVif6u1nqLg==
X-Received: by 2002:a65:6553:: with SMTP id a19mr1321543pgw.267.1549390758510;  Tue, 05 Feb 2019 10:19:18 -0800 (PST)
Received: from mail-pl1-f181.google.com (mail-pl1-f181.google.com. [209.85.214.181]) by smtp.gmail.com with ESMTPSA id x186sm5095034pfb.59.2019.02.05.10.19.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Feb 2019 10:19:17 -0800 (PST)
Received: by mail-pl1-f181.google.com with SMTP id u18so1846577plq.7; Tue, 05 Feb 2019 10:19:17 -0800 (PST)
X-Received: by 2002:a17:902:8b88:: with SMTP id ay8mr6476391plb.55.1549390757224;  Tue, 05 Feb 2019 10:19:17 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com> <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com> <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com> <24551658-0943-431C-B319-D74B5DC169B9@gmail.com>
In-Reply-To: <24551658-0943-431C-B319-D74B5DC169B9@gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 5 Feb 2019 13:19:06 -0500
X-Gmail-Original-Message-ID: <CAD5OKxtn4TCZCgV_4r17AqUgbFxgk1NjMBNCR0Gcn-67zRJCwQ@mail.gmail.com>
Message-ID: <CAD5OKxtn4TCZCgV_4r17AqUgbFxgk1NjMBNCR0Gcn-67zRJCwQ@mail.gmail.com>
To: Alan Ford <alan.ford@gmail.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, Simon Perreault <sperreault@jive.com>,  RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b3e5af058129a5d8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/hF0WLd2R3JVG03Sec8THXfEM5J8>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 05 Feb 2019 18:19:27 -0000

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

On Tue, Feb 5, 2019 at 10:03 AM Alan Ford <alan.ford@gmail.com> wrote:

> If that update was to be made, this goes against the text
> in draft-ietf-rtcweb-mdns-ice-candidates-02 which says:
>
>    An ICE agent that supports mDNS candidates MUST support the situation
>    where the hostname resolution results in more than one IP address.
>    In this case, the ICE agent MUST take exactly one of the resolved IP
>    addresses and ignore the others.  The ICE agent SHOULD, if available,
>    use the first IPv6 address resolved, otherwise the first IPv4
>    address.
>

This is obviously not going to work. At the very minimum ICE client should
be listening for connectivity checks on all addresses to which FQDN
candidate resolves, including IPv4 and IPv6. It also should do connectivity
checks to all addresses. Otherwise, if you have two clients, one dual stack
and another single stack, they are not going to see each other, since one
will be listening and sending connectivity checks via IPv6 and another via
IPv4. This is why language about FQDN was removed from mmusic-ice-sip-sdp
-- it was broken.

For ICE to work, you want to include all possible addresses for FQDN in the
candidate list and then proceed with nomination as if they were independent
candidates.

But there=E2=80=99s a bigger problem here, which is how to cope with an FQD=
N is not
> resolvable. So the intention, as I understand it, is that when these host
> candidates leave the mDNS domain and are thus not resolvable, they will b=
e
> treated as peer reflexive candidates.
>
> But at that point there is no address family information available, so ho=
w
> does an ICE agent know to do pairing with these candidates, which require=
s
> the address family to be known?
>

I do not think this is a problem. For peer reflexive candidates, ICE agent
knows address family/local address/port where connectivity check was
received and the address family/remote address/port from which the
connectivity check was received. Everything, including the address family
is known in this case and agent can proceed with nomination as with any
other peer reflexive candidate.

Regards,
_____________
Roman Shpount

--000000000000b3e5af058129a5d8
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 Tue, Feb 5, 2019 at 10:03 AM A=
lan Ford &lt;<a href=3D"mailto:alan.ford@gmail.com">alan.ford@gmail.com</a>=
&gt; wrote:<br></div></div></div><div class=3D"gmail_quote"><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 style=3D"overflow-wrap: break-word;=
">If that update was to be made, this goes against the text in=C2=A0draft-i=
etf-rtcweb-mdns-ice-candidates-02 which says:<div><br></div><div><span styl=
e=3D"font-size:11px"><font face=3D"Menlo">=C2=A0 =C2=A0An ICE agent that su=
pports mDNS candidates MUST support the situation<br>=C2=A0 =C2=A0where the=
 hostname resolution results in more than one IP address.<br>=C2=A0 =C2=A0I=
n this case, the ICE agent MUST take exactly one of the resolved IP<br>=C2=
=A0 =C2=A0addresses and ignore the others.=C2=A0 The ICE agent SHOULD, if a=
vailable,<br>=C2=A0 =C2=A0use the first IPv6 address resolved, otherwise th=
e first IPv4<br>=C2=A0 =C2=A0address.</font></span></div></div></blockquote=
><div>=C2=A0</div><div>This is obviously not going to work. At the very min=
imum ICE client should be listening for connectivity checks on all addresse=
s to which FQDN candidate resolves, including IPv4 and IPv6. It also should=
 do connectivity checks to all addresses. Otherwise, if you have two client=
s, one dual stack and another single stack, they are not going to see each =
other, since one will be listening and sending connectivity checks via IPv6=
 and another via IPv4. This is why language about FQDN was removed from mmu=
sic-ice-sip-sdp -- it was broken.</div><div><br></div><div>For ICE to work,=
 you want to include all possible addresses for FQDN in the candidate list =
and then proceed with nomination as if they were independent candidates.</d=
iv><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"><div st=
yle=3D"overflow-wrap: break-word;"><div><div></div><div>But there=E2=80=99s=
 a bigger problem here, which is how to cope with an FQDN is not resolvable=
. So the intention, as I understand it, is that when these host candidates =
leave the mDNS domain and are thus not resolvable, they will be treated as =
peer reflexive candidates.</div><div><br></div><div>But at that point there=
 is no address family information available, so how does an ICE agent know =
to do pairing with these candidates, which requires the address family to b=
e known?</div></div></div></blockquote><div><br></div><div>I do not think t=
his is a problem. For peer reflexive candidates, ICE agent knows address fa=
mily/local address/port where connectivity check was received and the addre=
ss family/remote address/port from which the connectivity check was receive=
d. Everything, including the address family is known in this case and agent=
 can proceed with nomination as with any other peer reflexive candidate.</d=
iv><div><br></div><div>Regards,</div>_____________<br>Roman Shpount<br clas=
s=3D"gmail-Apple-interchange-newline"><div>=C2=A0</div></div></div>

--000000000000b3e5af058129a5d8--


From nobody Tue Feb  5 11:52:58 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 857CB13121F for <mmusic@ietfa.amsl.com>; Tue,  5 Feb 2019 11:52:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.852
X-Spam-Level: 
X-Spam-Status: No, score=-8.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=eZKvO9v5; dkim=pass (1024-bit key) header.d=ericsson.com header.b=l7/zh4OK
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 2vCzuhO-hV9x for <mmusic@ietfa.amsl.com>; Tue,  5 Feb 2019 11:52:54 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 778EF13121D for <mmusic@ietf.org>; Tue,  5 Feb 2019 11:52:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/relaxed;  q=dns/txt; i=@ericsson.com; t=1549396371; x=1551988371; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=83GZQUo+GG+MWYiQbd7fU6xg635/scO/IaMIJnlZh80=; b=eZKvO9v5fHlc7Pxqa54BGHh4y8NVRYDZOQJ9TN+5ljQiq6KQBdw149UN6OnUjcuM Hd59Q2fsPmv+7jadLQ4uJ9UcN1Ji9+gQLWfs+z6QQEOxZWVaN3mRUVkSwOKuPkn5 O73bppbyB1keB2AjJrxFjuejLgTpsy6YMpWN/lXQlZA=;
X-AuditID: c1b4fb30-f93ff7000000355c-e3-5c59e993a91f
Received: from ESESBMB502.ericsson.se (Unknown_Domain [153.88.183.115]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 0B.6B.13660.399E95C5; Tue,  5 Feb 2019 20:52:51 +0100 (CET)
Received: from ESESSMB501.ericsson.se (153.88.183.162) by ESESBMB502.ericsson.se (153.88.183.169) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 5 Feb 2019 20:52:50 +0100
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Tue, 5 Feb 2019 20:52:51 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=83GZQUo+GG+MWYiQbd7fU6xg635/scO/IaMIJnlZh80=; b=l7/zh4OKHlqUMquWoxlcgdM4wSmH5vPnVLoNv+Kj2e4IYBS0dCi+gBlQTpFQ1V/9kXkolmeE3hc1dO8vx+AA3fidpK6iRUMvauP5vodxlhc4As1eTQBV11Ul6t4C24yQHpCXIWrH5xLSYChMDdwApnJmYhqlqMmLaB6Bu0QPhSg=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3098.eurprd07.prod.outlook.com (10.170.244.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1601.14; Tue, 5 Feb 2019 19:52:49 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0%4]) with mapi id 15.20.1601.016; Tue, 5 Feb 2019 19:52:49 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Alan Ford <alan.ford@gmail.com>, Roman Shpount <roman@telurix.com>
CC: Simon Perreault <sperreault@jive.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Thread-Topic: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
Thread-Index: AQHUvWQJ5AXujZ/OCkayq1rv1scozqXRnTFt
Date: Tue, 5 Feb 2019 19:52:48 +0000
Message-ID: <HE1PR07MB3161A360F1C281127CCFDCF5936E0@HE1PR07MB3161.eurprd07.prod.outlook.com>
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com> <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com> <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com>, <24551658-0943-431C-B319-D74B5DC169B9@gmail.com>
In-Reply-To: <24551658-0943-431C-B319-D74B5DC169B9@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [87.93.22.227]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR07MB3098; 6:7yH1A2AwzUDzFMxlPqDbixEaPBvS4dbXiwoxb6L4UAJBHAl1o+SaSvhP1fo5EWgFqf7H3Qsb8XfUxp20aAOQ7HvDRm3zyT5lYDDvqTW/2pidXxxUYLdopiizx9sOoHTlu73C/MuqfOmU98i0oxh4IHuroiHkZLkwO74NTsjjW+HHvHQw+0w9vewqKstzBWFYrMRGEMIgpW31/2YM32H7/mA9IjYCrlmupbEetNKZ4bbgdPVR+oesCyL+G+rZTvGLPVQAkZIVD+G9ct5oGaWmgS9FYityKWrMLgVqgBXCu2vBYmUSMtyWTschnTAgZOGH59wmsohIkpucLVMAiCST180IZRFx1x3Pgm+7QWuVUXpNPq7R8JsW3/uslmgTUzLDg8IchONEqh638hHmvnBC+HkW8MhyjoNop1XF2zmNTxRF6Gcjp7BcNxbdJcXAzzVYuyo5J3iA5iIFFam2pswxHQ==; 5:jYSbY3kbci3ap5zF5XKlYTbEVYpTe1r8hNMfI9FYzOsmTFCv1iOp/wi1BPYELSWktWrxKMR1nPFos1D+qaX7GG+3gendjlZ235vG08bnlRCs3hQKBOGmFr37Em3/JiILBPDkswHXnuNufJiAHZiIXIYftBhqyazWOwqJFNwM5VuS70cx0OJlznJvL4sCKYPclB8N4RuKraxazQGtBrWTzQ==; 7:eZ6+eeLOhpb4mqIbEMoOp3LoJY9YVMIiuqqhp7lPyFoMsp70DLtC0220I23nJLT7xtKVpgXdHHJYjI8veLr3GkU8cbztNk0d5PlXFdXUBnK6UZxwQb68BwTNovS8Krt6aN08LyQ+D6X3/7HbQZKlng==
x-ms-office365-filtering-correlation-id: e8e6c23b-7d62-4011-3628-08d68ba381a8
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(2017052603328)(7153060)(7193020); SRVR:HE1PR07MB3098; 
x-ms-traffictypediagnostic: HE1PR07MB3098:
x-microsoft-antispam-prvs: <HE1PR07MB3098BEF1FE47988B8C937ED4936E0@HE1PR07MB3098.eurprd07.prod.outlook.com>
x-forefront-prvs: 0939529DE2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(396003)(136003)(366004)(39860400002)(346002)(189003)(199004)(54896002)(6306002)(66066001)(3846002)(9686003)(4326008)(7736002)(14454004)(97736004)(478600001)(6116002)(93886005)(236005)(606006)(19627405001)(966005)(8936002)(6506007)(53546011)(102836004)(71200400001)(71190400001)(81166006)(186003)(26005)(99286004)(7696005)(76176011)(446003)(110136005)(54906003)(11346002)(476003)(105586002)(2906002)(106356001)(1015004)(316002)(55016002)(6436002)(33656002)(81156014)(8676002)(68736007)(6606003)(25786009)(486006)(229853002)(14444005)(53936002)(6246003)(44832011)(74316002)(256004)(5070765005)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3098; 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: if4/YqnPkSxO6JnmfTqTu7wIiSUPd/BisBhjPQ4qFLsHT8LipF+5fgSN+0qyqZS9ysumat0dhZJAi92f6EWpqVFYUxKzqHsouQAO6OKGLYJxklM1W5Xz2jN8yPXFRfSYJOdzgFGWHKnuyIGIO+gJlOSXXsGaDbZ9MtuCuOW1ov4l6sLI5EbD4Mynby+VzPz1fDuuy+Wive+0jTEcwrYu4JudEZ4i4uZJK+/ZqSd+YR3ecJGdzQMdVUj8jSdCaihhOulsrlQVFoTvjy4wZJUYmjQmXefkY/A8Kv0kBnY/v2PRWcgh3HD2g0YdQj8KTVdZ4Asv7RGr4Y+c8V2g3c/t4zqYwhJKgKYY0wZKV7bRhCxOnGpbUpdLBC/iKqhxJT5LsriXAi6ND70q9JbaiH6/PGN611UiFZoYggw+xZ8ng44=
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB3161A360F1C281127CCFDCF5936E0HE1PR07MB3161eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e8e6c23b-7d62-4011-3628-08d68ba381a8
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Feb 2019 19:52:48.9307 (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-Transport-CrossTenantHeadersStamped: HE1PR07MB3098
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0iTURzGO3vf7X23Gh2Xlz9aGkMMpk6TyH3QSAixRChLyBjoytcL6pS9 yzIJLFrJVqapeMlbuTLNC4qikk4dRuqHrBCvdBGnsso+VBaWjJzHwG+///95Hp5zDoelZFah J5um1XM6rSZDLpLQled7+MASe7w6+M9DH1XT62eUqqxxkVZVvCmjVK2OO4xqejLuuDCqr+o9 E2U2rwuiHNVLVNRcafZp+oIkLInLSMvhdEHHEiWptnYTlV14G13tthiYfFStMyIxC/gIFHbc p41IwsrwCILJXpOIDGsI7IaebaVBAK+GChjnQOMiCl6slCBnXoZLNpWlcOJaQDBjKdvMs6wI q8Dk8Hd6XHEklCwXipxM4RRw1C1TTt6HM2BlsI0mnkyo6cpHhEOg7Vu9wMk09oWG1o2trBSr wVhajUiXkYXRKQvl7BLjcDD/iHF6EHaH3+MtAtLlAXO2OgG5JwZz/wRF2A3siw4h8WtgsPnT 9v4gdAwZt/kAvKszbXUBvsnA1MQSQ4QYKF+1MUSYRWCZeykkggJsH0YQ4XSoqm3eDuyH3r5h AQlUi8B07zNNno6DxlYDKkIBVTtOSzgL2isMWyzFLjBWaaPJXgkzZaUiwv7w9NEXinAgVDis 9M59PWKakRvP8RczU0JClJwu7RLPZ2mVWk7fiTZ/1nDX3+BeZF+JsCLMIvkeafJCvFom1OTw uZlWBCwld5UGdG+upEma3GucLitBdzmD463Ii6XlHtINmYtahlM0ei6d47I53X9VwIo985H7 oY95EcrkaPVaXXfigH9I1620rKkAa//uk8Vva/amd5oTUq94N6zHjo+f8CoIHms7lSebFuZm 3/UK/uqj0M+Ieov9EgZWj7cZXH3jQr2bciXu2G/Ucr1/17nHz+fFQd9r51vOzoau/kJnmOjy By1hlQk3fi5KAmqeKMyRsYr4o3KaT9UcVlA6XvMPL+LiP1UDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/HSeUqE_vIbXNGbaHvDc_oePcixA>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 05 Feb 2019 19:52:56 -0000

--_000_HE1PR07MB3161A360F1C281127CCFDCF5936E0HE1PR07MB3161eurp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,



>If that update was to be made, this goes against the text in draft-ietf-rt=
cweb-mdns-ice-
>candidates-02 which says:
>
>  An ICE agent that supports mDNS candidates MUST support the situation
>   where the hostname resolution results in more than one IP address.
>  In this case, the ICE agent MUST take exactly one of the resolved IP
>  addresses and ignore the others.  The ICE agent SHOULD, if available,
>use the first IPv6 address resolved, otherwise the first IPv4 address.

This is what I have previously commented. The text needs to be modified.

Regards,

Christer



On 1 Feb 2019, at 21:06, Roman Shpount <roman@telurix.com<mailto:roman@telu=
rix.com>> wrote:

In this case section 4.1 of ice-sip-sdp should be updated to allow FQDN in =
connection-address and, perhaps specify that FWDN which return multiple res=
ults should be ignored.

Would this work for everyone?

Regards,
_____________
Roman Shpount


On Fri, Feb 1, 2019 at 4:02 PM Christer Holmberg <christer.holmberg@ericsso=
n.com<mailto:christer.holmberg@ericsson.com>> wrote:
I have no problem with allowing FQDNs - as long as they result in a SINGLE =
address:port.

If we want to define ICE usage of FDNSs resulting in MULTIPLE addresses:por=
ts, I really think that should be a separate document - it should NOT be ad=
ded as a last minute thing to draft-ice-sip-sdp.

...and, yes, perhaps such work would also affect 8445.

Regards,

Christer





________________________________
From: rtcweb <rtcweb-bounces@ietf.org<mailto:rtcweb-bounces@ietf.org>> on b=
ehalf of Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>>
Sent: Friday, February 1, 2019 10:22 PM
To: Justin Uberti
Cc: Simon Perreault; Dale R. Worley; RTCWeb IETF; mmusic WG
Subject: Re: [rtcweb] [MMUSIC] What goes into c=3D line address when FQDN i=
s used for the default candidate?

On Fri, Feb 1, 2019 at 2:39 PM Justin Uberti <juberti@google.com<mailto:jub=
erti@google.com>> wrote:
This has all been discussed at length in rtcweb and I don't think any signi=
ficant changes are needed, although I tend to think that we should restore =
the removed FQDN text from mmusic-ice-sip-sdp, which is the only thing not =
in alignment at this point in time.

I agree that FQDN should be put back into connection-address definition, bu=
t  the portion which talks about handling it is completely broken..

Quoting 5245<https://tools.ietf.org/html/rfc5245#section-15.1>:

   <connection-address>:  is taken from RFC 4566<https://tools.ietf.org/htm=
l/rfc4566> [RFC4566<https://tools.ietf.org/html/rfc4566>].  It is the
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and fully qualified domain names (FQDNs).  When parsing
      this field, an agent can differentiate an IPv4 address and an IPv6


      address by presence of a colon in its value - the presence of a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=3Dcandidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.



I think it was discussed in quite a detail why using a random DNS resolutio=
n result is not going to work here..

The only options we have here are:

a. Fix FQDN connection address handling. Probably the most logical way of d=
ealing with this would be to specify that candidate with FQDN should be con=
verted as a result of DNS resolution into multiple candidates, with each ca=
ndidate corresponding to A or AAAA record in DNS query result. We will also=
 need to specify how FQDN candidate gets applied to c=3D line address. Some=
thing that says IN IP4 FQDN, if any A records exist for this DNS name and I=
N IP6 FQDN if only AAAA records exist. Once candidate is nominated, address=
 family in c=3D line should match address family used for communications. T=
his will definitely require a lot more work and discussion.

b. Specify that FQDN connection addresses should be ignored until their han=
dling is defined in a future specification. This seems easy and only requir=
es a sentence or two to fix.

Regards,
_____________
Roman Shpount
_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


--_000_HE1PR07MB3161A360F1C281127CCFDCF5936E0HE1PR07MB3161eurp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p style=3D"margin-top:0;margin-bottom:0">Hi,</p>
<p style=3D"margin-top:0;margin-bottom:0">&nbsp;</p>
<div style=3D"color: rgb(0, 0, 0);">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"></div>
<div style=3D"word-wrap:break-word; line-break:after-white-space">&gt;If th=
at update was to be made, this goes against the text in&nbsp;draft-ietf-rtc=
web-mdns-ice-</div>
<div style=3D"word-wrap:break-word; line-break:after-white-space">&gt;candi=
dates-02 which says:
<div>&gt;</div>
<div><span style=3D"font-size:11px"><font face=3D"Menlo">&gt;&nbsp; An ICE =
agent that supports mDNS candidates MUST support the situation<br>
<div>&gt; &nbsp; where the hostname resolution results in more than one IP =
address.<br>
</div>
<div>&gt;&nbsp; In this case, the ICE agent MUST take exactly one of the re=
solved IP</div>
<div>&gt;&nbsp; addresses and ignore the others. &nbsp;The ICE agent SHOULD=
, if available,&nbsp;</div>
</font></span>
<div><span style=3D"font-size:11px"><font face=3D"Menlo">&gt;use the first =
IPv6 address resolved, otherwise the first IPv4
</font></span><span style=3D"font-size:11px"><font face=3D"Menlo">address.<=
/font></span><br>
</div>
<div><br>
</div>
<div>This is what I have previously commented. The text needs to be modifie=
d.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<blockquote type=3D"cite">
<div>On 1 Feb 2019, at 21:06, Roman Shpount &lt;<a class=3D"OWAAutoLink" id=
=3D"LPlnk217078" href=3D"mailto:roman@telurix.com" previewremoved=3D"true">=
roman@telurix.com</a>&gt; wrote:</div>
<br class=3D"x_Apple-interchange-newline">
<div>
<div dir=3D"ltr">
<div dir=3D"ltr">In this case section 4.1 of ice-sip-sdp should be updated =
to allow FQDN in connection-address and, perhaps specify that FWDN which re=
turn multiple results should be ignored.</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">Would this work for everyone?</div>
<div dir=3D"ltr"><br>
</div>
<div dir=3D"ltr">Regards,<br clear=3D"all">
<div>
<div class=3D"x_gmail_signature" dir=3D"ltr">_____________<br>
Roman Shpount</div>
</div>
<br>
</div>
<br>
<div class=3D"x_gmail_quote">
<div class=3D"x_gmail_attr" dir=3D"ltr">On Fri, Feb 1, 2019 at 4:02 PM Chri=
ster Holmberg &lt;<a class=3D"OWAAutoLink" id=3D"LPlnk533600" href=3D"mailt=
o:christer.holmberg@ericsson.com" previewremoved=3D"true">christer.holmberg=
@ericsson.com</a>&gt; wrote:<br>
</div>
<blockquote class=3D"x_gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; bord=
er-left:1px solid rgb(204,204,204); padding-left:1ex">
<div dir=3D"ltr">
<div id=3D"x_gmail-m_-7925862921453132447divtagdefaultwrapper" style=3D"fon=
t-size:12pt; font-family:Calibri,Helvetica,sans-serif" dir=3D"ltr">
<div style=3D"margin-top:0px; margin-bottom:0px"><span style=3D"font-size:1=
2pt">I have no problem with allowing FQDNs - as long as they result in a SI=
NGLE address:port.</span><br>
</div>
<div style=3D"margin-top:0px; margin-bottom:0px"><br>
</div>
<div style=3D"margin-top:0px; margin-bottom:0px">If we want to define ICE u=
sage of FDNSs resulting in MULTIPLE addresses:ports, I really think that sh=
ould be a separate document - it should NOT be added as a last minute thing=
 to draft-ice-sip-sdp.</div>
<div style=3D"margin-top:0px; margin-bottom:0px"><br>
</div>
<div style=3D"margin-top:0px; margin-bottom:0px">...and, yes, perhaps such =
work would also affect 8445.</div>
<div style=3D"margin-top:0px; margin-bottom:0px"><br>
</div>
<div style=3D"margin-top:0px; margin-bottom:0px">Regards,</div>
<div style=3D"margin-top:0px; margin-bottom:0px"><br>
</div>
<div style=3D"margin-top:0px; margin-bottom:0px">Christer</div>
<div style=3D"margin-top:0px; margin-bottom:0px"><br>
</div>
<div style=3D"margin-top:0px; margin-bottom:0px"><br>
</div>
<div style=3D"margin-top:0px; margin-bottom:0px"><br>
</div>
<br>
<br>
<div style=3D"">
<hr style=3D"display:inline-block; width:98%">
<div id=3D"x_gmail-m_-7925862921453132447divRplyFwdMsg" dir=3D"ltr"><font f=
ace=3D"Calibri, sans-serif" style=3D"font-size:11pt"><b>From:</b> rtcweb &l=
t;<a class=3D"OWAAutoLink" id=3D"LPlnk646358" href=3D"mailto:rtcweb-bounces=
@ietf.org" target=3D"_blank" previewremoved=3D"true">rtcweb-bounces@ietf.or=
g</a>&gt;
 on behalf of Roman Shpount &lt;<a class=3D"OWAAutoLink" id=3D"LPlnk39762" =
href=3D"mailto:roman@telurix.com" target=3D"_blank" previewremoved=3D"true"=
>roman@telurix.com</a>&gt;<br>
<b>Sent:</b> Friday, February 1, 2019 10:22 PM<br>
<b>To:</b> Justin Uberti<br>
<b>Cc:</b> Simon Perreault; Dale R. Worley; RTCWeb IETF; mmusic WG<br>
<b>Subject:</b> Re: [rtcweb] [MMUSIC] What goes into c=3D line address when=
 FQDN is used for the default candidate?</font>
<div>&nbsp;</div>
</div>
<div>
<div dir=3D"ltr">
<div dir=3D"ltr">
<div>
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_signature" dir=3D"ltr">=
On Fri, Feb 1, 2019 at 2:39 PM Justin Uberti &lt;<a class=3D"x_gmail-m_-792=
5862921453132447OWAAutoLink OWAAutoLink" id=3D"LPlnk671390" href=3D"mailto:=
juberti@google.com" target=3D"_blank" previewremoved=3D"true">juberti@googl=
e.com</a>&gt;
 wrote:<br>
</div>
</div>
</div>
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
<div dir=3D"ltr">This has all been discussed at length in rtcweb and I don'=
t think any significant changes are needed, although I tend to think that w=
e should restore the removed FQDN text from mmusic-ice-sip-sdp, which is th=
e only thing not in alignment at this
 point in time.</div>
</blockquote>
<div><br>
</div>
<div>I agree that FQDN should be put back into connection-address definitio=
n, but&nbsp; the portion which talks about handling it is completely broken=
..</div>
<div><br>
</div>
<div>Quoting&nbsp;<a class=3D"x_gmail-m_-7925862921453132447OWAAutoLink OWA=
AutoLink" id=3D"LPlnk655058" href=3D"https://tools.ietf.org/html/rfc5245#se=
ction-15.1" target=3D"_blank" previewremoved=3D"true">5245</a><span style=
=3D"">:</span></div>
<div>
<pre class=3D"x_gmail-m_-7925862921453132447x_gmail-m_7058075087377128197gm=
ail-newpage" style=3D"white-space:pre-wrap; font-size:13.3333px; margin-top=
:0px; margin-bottom:0px; break-before:page">   &lt;connection-address&gt;: =
 is taken from <a class=3D"x_gmail-m_-7925862921453132447OWAAutoLink OWAAut=
oLink" id=3D"LPlnk444988" href=3D"https://tools.ietf.org/html/rfc4566" targ=
et=3D"_blank" previewremoved=3D"true">RFC 4566</a> [<a title=3D"&quot;SDP: =
Session Description Protocol&quot;" class=3D"x_gmail-m_-7925862921453132447=
OWAAutoLink OWAAutoLink" id=3D"LPlnk544548" href=3D"https://tools.ietf.org/=
html/rfc4566" target=3D"_blank" previewremoved=3D"true">RFC4566</a>].  It i=
s the=0A=
      IP address of the candidate, allowing for IPv4 addresses, IPv6=0A=
      addresses, and <b>fully qualified domain names (FQDNs).</b>  When par=
sing=0A=
      this field, an agent can differentiate an IPv4 address and an IPv6=0A=
</pre>
<pre class=3D"x_gmail-m_-7925862921453132447x_gmail-m_7058075087377128197gm=
ail-newpage" style=3D"white-space:pre-wrap; font-size:13.3333px; margin-top=
:0px; margin-bottom:0px; break-before:page">      address by presence of a =
colon in its value - the presence of a=0A=
      colon indicates IPv6.  An agent MUST ignore candidate lines that=0A=
      include candidates with IP address versions that are not supported=0A=
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be=0A=
      used in place of an IP address.  In that case, when receiving an=0A=
      offer or answer containing an FQDN in an a=3Dcandidate attribute,=0A=
      the FQDN is looked up in the DNS first using an AAAA record=0A=
      (assuming the agent supports IPv6), and if no result is found or=0A=
      the agent only supports IPv4, using an A.  If the DNS query=0A=
      returns more than one IP address, one is chosen, and then used for=0A=
      the remainder of ICE processing.=0A=
</pre>
<pre class=3D"x_gmail-m_-7925862921453132447x_gmail-m_7058075087377128197gm=
ail-newpage" style=3D"white-space:pre-wrap; font-size:13.3333px; margin-top=
:0px; margin-bottom:0px; break-before:page"><br></pre>
I think it was discussed in quite a detail why using a random DNS resolutio=
n result is not going to work here..</div>
<div><br>
</div>
<div>The only options we have here are:</div>
<div><br>
</div>
<div>a. Fix FQDN connection address handling. Probably the most logical way=
 of dealing with this would be to specify that candidate with FQDN should b=
e converted as a result of DNS resolution into multiple candidates, with ea=
ch candidate corresponding to A
 or AAAA record in DNS query result. We will also need to specify how FQDN =
candidate gets applied to c=3D line address. Something that says IN IP4 FQD=
N, if any A records exist for this DNS name and IN IP6 FQDN if only AAAA re=
cords exist. Once candidate is nominated,
 address family in c=3D line should match address family used for communica=
tions. This will definitely require a lot more work and discussion.</div>
<div><br>
</div>
<div>b. Specify that FQDN connection addresses should be ignored until thei=
r handling is defined in a future specification. This seems easy and only r=
equires a sentence or two to fix.</div>
<div><br>
</div>
<div>Regards,</div>
<div>_____________<br>
Roman Shpount</div>
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
<div dir=3D"ltr">
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
<div class=3D"x_gmail-m_-7925862921453132447x_gmail_quote">
<blockquote class=3D"x_gmail-m_-7925862921453132447x_gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-l=
eft:1ex">
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
_______________________________________________<br>
mmusic mailing list<br>
<a class=3D"OWAAutoLink" id=3D"LPlnk258614" href=3D"mailto:mmusic@ietf.org"=
 previewremoved=3D"true">mmusic@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/mmusic<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_HE1PR07MB3161A360F1C281127CCFDCF5936E0HE1PR07MB3161eurp_--


From nobody Tue Feb  5 14:02:48 2019
Return-Path: <alissa@cooperw.in>
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 6FEEB131317; Tue,  5 Feb 2019 14:02:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
Cc: mmusic-chairs@ietf.org, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.91.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154940416338.32237.8653012939519141336.idtracker@ietfa.amsl.com>
Date: Tue, 05 Feb 2019 14:02:43 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/a317Ce5IhKDRST1ROFOFj4w17TA>
Subject: [MMUSIC] Alissa Cooper's No Objection on charter-ietf-mmusic-04-00: (with COMMENT)
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, 05 Feb 2019 22:02:45 -0000

Alissa Cooper has entered the following ballot position for
charter-ietf-mmusic-04-00: No Objection

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



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



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

I don't think this needs external review.

"Maintain the specifications of the Interactive Connectivity Establishment
(ICE) and specify extensions to it with demonstrated interest and value."  -->
Maybe "where there is demonstrated interest and value"? The way it is written
now sounds a bit weird.

Isn't CLUE closing soon? I wonder if it still needs to be listed.



From nobody Tue Feb  5 16:57:45 2019
Return-Path: <juberti@google.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 5D169128CE4 for <mmusic@ietfa.amsl.com>; Tue,  5 Feb 2019 16:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.642
X-Spam-Level: 
X-Spam-Status: No, score=-17.642 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 c_zle3vVdyso for <mmusic@ietfa.amsl.com>; Tue,  5 Feb 2019 16:57:34 -0800 (PST)
Received: from mail-it1-x136.google.com (mail-it1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 691F1128B01 for <mmusic@ietf.org>; Tue,  5 Feb 2019 16:57:34 -0800 (PST)
Received: by mail-it1-x136.google.com with SMTP id a6so2463560itl.4 for <mmusic@ietf.org>; Tue, 05 Feb 2019 16:57:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lNMNPz7PRH05KqR1BtjFReUSJ13QsK6ioyH3/IOKo8I=; b=PD3odNS/vMaV7fw0lM1XAXLDXgDXcKJ9UKN9Nb27broQDfANTcBuJWgJC5vSsp9Qn5 IQCbmjs2Pt8tvQ5cK1pgIAYr+Y+nXdiI/3ejPMSf4EP8hduvbmEQFkCGNfpf1H+OLZOX /DT4wbPrbX43bE5dRNI6Q84JIm1H4UG1x9zNE4M28iy/FAjOKWfYWaB8mDaVRng6KWfl 0Fw89HN3LmUHEVHBDSxE2KP8BoWp6z2CA8kL//CfB062ZFTQYGzbAAsGZq1WazRccpZH Q4CCW+qwz4RnmCsMzIEX0IyEVmKV+rDZV0EBKthh4QTJnTJ6Sft0pnycEwEW58QQ+2W+ qkKw==
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=lNMNPz7PRH05KqR1BtjFReUSJ13QsK6ioyH3/IOKo8I=; b=kmESYiZQjojIE35kXDvhbRTDTLgA/Ew7sz41wHqy//Yt3pdV1f2XSxblObiT2dNAc3 z/0vYxLJMfdgUUq8+dFXaTL6FWA599yGbo6P8I9IUhcaHhTlSWpxhbk7jHuLqV6Q0cec DUuP+USRZos8Bo58lJB8NP1F688cHq6hfJt0E7koXsDIf3v0g1J1Gd5RHF3QBvtYb9zJ QkgZBGt3rgQDBJCc2eAYlsFubSh7zYiB9jRL3/ioUWI/xJoqi+1myMACBOXuZ99lavn0 DSr13p11IPizx1uEeWSGr03YIMqg5hBB777LDOeNHK+rlAOHmO0yJpuWXN0iUEzNpyRI KwIg==
X-Gm-Message-State: AHQUAuYsv0UJxrW/7iijallZicqOtGC/ZlNueBKD2RF6QKRn1xcSYIPQ ly3N34regg6hCJN+odgyWakahMk4COnjRqSSvjg6Xg==
X-Google-Smtp-Source: AHgI3IaWIHlB7CyCoa2uXbZJ7nldnvnd9Y/GvURh7kRmvfxzK/dS2JICWODU5lMpHrFBWQkfgIjFj1zdd1IUhZ+1nE8=
X-Received: by 2002:a24:738f:: with SMTP id y137mr897186itb.136.1549414653359;  Tue, 05 Feb 2019 16:57:33 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com> <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com> <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com> <24551658-0943-431C-B319-D74B5DC169B9@gmail.com> <CAD5OKxtn4TCZCgV_4r17AqUgbFxgk1NjMBNCR0Gcn-67zRJCwQ@mail.gmail.com>
In-Reply-To: <CAD5OKxtn4TCZCgV_4r17AqUgbFxgk1NjMBNCR0Gcn-67zRJCwQ@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Tue, 5 Feb 2019 16:57:21 -0800
Message-ID: <CAOJ7v-1z4P-=RQfUb1o2JGduuVNs3G-HmXNXxuvrM-4XhRH_9w@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Alan Ford <alan.ford@gmail.com>, Simon Perreault <sperreault@jive.com>,  RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>,  Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="0000000000000667ea05812f360e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/sS_wfsiIzWuy3i9qBSJvcSY9fKU>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 06 Feb 2019 00:57:38 -0000

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

On Tue, Feb 5, 2019 at 10:19 AM Roman Shpount <roman@telurix.com> wrote:

> On Tue, Feb 5, 2019 at 10:03 AM Alan Ford <alan.ford@gmail.com> wrote:
>
>> If that update was to be made, this goes against the text
>> in draft-ietf-rtcweb-mdns-ice-candidates-02 which says:
>>
>>    An ICE agent that supports mDNS candidates MUST support the situation
>>    where the hostname resolution results in more than one IP address.
>>    In this case, the ICE agent MUST take exactly one of the resolved IP
>>    addresses and ignore the others.  The ICE agent SHOULD, if available,
>>    use the first IPv6 address resolved, otherwise the first IPv4
>>    address.
>>
>
> This is obviously not going to work. At the very minimum ICE client shoul=
d
> be listening for connectivity checks on all addresses to which FQDN
> candidate resolves, including IPv4 and IPv6. It also should do connectivi=
ty
> checks to all addresses. Otherwise, if you have two clients, one dual sta=
ck
> and another single stack, they are not going to see each other, since one
> will be listening and sending connectivity checks via IPv6 and another vi=
a
> IPv4. This is why language about FQDN was removed from mmusic-ice-sip-sdp
> -- it was broken.
>

> For ICE to work, you want to include all possible addresses for FQDN in
> the candidate list and then proceed with nomination as if they were
> independent candidates.
>

I don't think this is correct behavior, but it's really beside the point
since we can ignore it if we have the one-FQDN-per-address concept we
discussed.

>
> But there=E2=80=99s a bigger problem here, which is how to cope with an F=
QDN is
>> not resolvable.. So the intention, as I understand it, is that when thes=
e
>> host candidates leave the mDNS domain and are thus not resolvable, they
>> will be treated as peer reflexive candidates.
>>
>> But at that point there is no address family information available, so
>> how does an ICE agent know to do pairing with these candidates, which
>> requires the address family to be known?
>>
>
> I do not think this is a problem. For peer reflexive candidates, ICE agen=
t
> knows address family/local address/port where connectivity check was
> received and the address family/remote address/port from which the
> connectivity check was received. Everything, including the address family
> is known in this case and agent can proceed with nomination as with any
> other peer reflexive candidate.
>

Right - this is implemented today in Chrome and appears to be working well
so far (with a few minor bugs discovered along the way).

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

<div dir=3D"ltr"><div dir=3D"ltr"></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Tue, Feb 5, 2019 at 10:19 AM 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:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"=
ltr"><div dir=3D"ltr"><div><div dir=3D"ltr" class=3D"gmail-m_31837006220677=
96669gmail_signature">On Tue, Feb 5, 2019 at 10:03 AM Alan Ford &lt;<a href=
=3D"mailto:alan.ford@gmail.com" target=3D"_blank">alan.ford@gmail.com</a>&g=
t; 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 rg=
b(204,204,204);padding-left:1ex"><div>If that update was to be made, this g=
oes against the text in=C2=A0draft-ietf-rtcweb-mdns-ice-candidates-02 which=
 says:<div><br></div><div><span style=3D"font-size:11px"><font face=3D"Menl=
o">=C2=A0 =C2=A0An ICE agent that supports mDNS candidates MUST support the=
 situation<br>=C2=A0 =C2=A0where the hostname resolution results in more th=
an one IP address.<br>=C2=A0 =C2=A0In this case, the ICE agent MUST take ex=
actly one of the resolved IP<br>=C2=A0 =C2=A0addresses and ignore the other=
s.=C2=A0 The ICE agent SHOULD, if available,<br>=C2=A0 =C2=A0use the first =
IPv6 address resolved, otherwise the first IPv4<br>=C2=A0 =C2=A0address.</f=
ont></span></div></div></blockquote><div>=C2=A0</div><div>This is obviously=
 not going to work. At the very minimum ICE client should be listening for =
connectivity checks on all addresses to which FQDN candidate resolves, incl=
uding IPv4 and IPv6. It also should do connectivity checks to all addresses=
. Otherwise, if you have two clients, one dual stack and another single sta=
ck, they are not going to see each other, since one will be listening and s=
ending connectivity checks via IPv6 and another via IPv4. This is why langu=
age about FQDN was removed from mmusic-ice-sip-sdp -- it was broken.=C2=A0<=
/div></div></div></blockquote><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div><br></div><div>For IC=
E to work, you want to include all possible addresses for FQDN in the candi=
date list and then proceed with nomination as if they were independent cand=
idates.</div></div></div></blockquote><div><br></div><div>I don&#39;t think=
 this is correct behavior, but it&#39;s really beside the point since we ca=
n ignore it if we have the one-FQDN-per-address concept we discussed.=C2=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><d=
iv class=3D"gmail_quote"><div><br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><div><div><div></div><div>But there=E2=80=99s a bigger probl=
em here, which is how to cope with an FQDN is not resolvable.. So the inten=
tion, as I understand it, is that when these host candidates leave the mDNS=
 domain and are thus not resolvable, they will be treated as peer reflexive=
 candidates.</div><div><br></div><div>But at that point there is no address=
 family information available, so how does an ICE agent know to do pairing =
with these candidates, which requires the address family to be known?</div>=
</div></div></blockquote><div><br></div><div>I do not think this is a probl=
em. For peer reflexive candidates, ICE agent knows address family/local add=
ress/port where connectivity check was received and the address family/remo=
te address/port from which the connectivity check was received. Everything,=
 including the address family is known in this case and agent can proceed w=
ith nomination as with any other peer reflexive candidate.</div></div></div=
></blockquote><div><br></div><div>Right - this is implemented today in Chro=
me and appears to be working well so far (with a few minor bugs discovered =
along the way).=C2=A0</div></div></div>

--0000000000000667ea05812f360e--


From nobody Tue Feb  5 17:03:55 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 556B3128B01 for <mmusic@ietfa.amsl.com>; Tue,  5 Feb 2019 17:03:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.031
X-Spam-Level: 
X-Spam-Status: No, score=-2.031 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 SEtxzpcKQ2uK for <mmusic@ietfa.amsl.com>; Tue,  5 Feb 2019 17:03:51 -0800 (PST)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (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 209A2128BCC for <mmusic@ietf.org>; Tue,  5 Feb 2019 17:03:51 -0800 (PST)
Received: by mail-pg1-x536.google.com with SMTP id z10so2183134pgp.7 for <mmusic@ietf.org>; Tue, 05 Feb 2019 17:03:51 -0800 (PST)
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=8Em3bFbsX//W0Sbg5kR97WtfmM4E8TdthFeA1COv7/M=; b=OjgybrdQ4n2tBv7vlzIUvP4YxB+jPWVV+uMxYIObn+J2eFiog/X+Fl6nNNJcpzvN0t pc3uEw8Xv2RbNfOb7dExvnasmgi+KKSfIOGLMD7N27IEr6x6NIfbVGfDNz1U3SNhv5iS SwmJ/IpYrqpnR/wy/zY5eza+F3GogwpSffyrT3K2rNC+hXtnpLJ7+ZMns67MDu8pRKCK dbExuNkm42iLQjwuiTSwRo8imto089CmuNZxLYkDDyO7G9w15SqiHMr8ruhbQiLDUkZW 9KCAgsrroW6Jz3GlVjsF03PnyuxuuyCa5ejwJNIjbNLLwQ/ljXb/ee5NeIQ+CB+SADnH 2xeQ==
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=8Em3bFbsX//W0Sbg5kR97WtfmM4E8TdthFeA1COv7/M=; b=G1G6TYUzYT+Opt9ftPk8vTu2lbmbg4LmbWxrhb39NZNC94bNteEySfFle7kgTC0sN6 cpdKBDquCj5kXbbGa6+Sf++ClxlX+x6nx+Lu7ozNkwzTkcfTygWAxNrdQ05OLUT4/G7Q 2ijhXJL53Op6ugpZyJ1U91d4GTmfok3EOdEErX53PvufMRL17ZuZFnLNhHY8JAYyBk5Q VxOvowQUErmNpfaoq1uxnhA8vdXAUbGtwuF5liMHcWoOXP91t/Vce6DNBgl0PX/BxL+C nr7Sv/+fIKcI1SwpTOgtdVjuppr/QDjiPtHuIZlgpul+TPm4uh77ES8n38G878SBT3m5 eL0w==
X-Gm-Message-State: AHQUAualjpyI09YKQ6tJ3ApxQz77nLjqZkLs1HrGX/tYsn2KiOkoc9rp BJo3u91S6RNI+LIDPOYfpDvhrAvFGE4=
X-Google-Smtp-Source: AHgI3IZX9oQlDlfObI3BxDjPQw7/0B0G3HJoItKmLUVWvezPtZ29gt1aWv1Zylq0UebxJTrLcmGKIw==
X-Received: by 2002:a62:1f9d:: with SMTP id l29mr7862664pfj.14.1549415030617;  Tue, 05 Feb 2019 17:03:50 -0800 (PST)
Received: from mail-pf1-f173.google.com (mail-pf1-f173.google.com. [209.85.210.173]) by smtp.gmail.com with ESMTPSA id m67sm6878069pfb.25.2019.02.05.17.03.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Feb 2019 17:03:49 -0800 (PST)
Received: by mail-pf1-f173.google.com with SMTP id 64so2322239pfr.9; Tue, 05 Feb 2019 17:03:49 -0800 (PST)
X-Received: by 2002:a63:5861:: with SMTP id i33mr7215522pgm.60.1549415028850;  Tue, 05 Feb 2019 17:03:48 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com> <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com> <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com> <24551658-0943-431C-B319-D74B5DC169B9@gmail.com> <CAD5OKxtn4TCZCgV_4r17AqUgbFxgk1NjMBNCR0Gcn-67zRJCwQ@mail.gmail.com> <CAOJ7v-1z4P-=RQfUb1o2JGduuVNs3G-HmXNXxuvrM-4XhRH_9w@mail.gmail.com>
In-Reply-To: <CAOJ7v-1z4P-=RQfUb1o2JGduuVNs3G-HmXNXxuvrM-4XhRH_9w@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 5 Feb 2019 20:03:38 -0500
X-Gmail-Original-Message-ID: <CAD5OKxv72sfohGx1pYwsfb8hki8NPRvJ=2bbv+MrX88gk7xg1g@mail.gmail.com>
Message-ID: <CAD5OKxv72sfohGx1pYwsfb8hki8NPRvJ=2bbv+MrX88gk7xg1g@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: Alan Ford <alan.ford@gmail.com>, Simon Perreault <sperreault@jive.com>,  RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>,  Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="00000000000067873705812f4c36"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/T3dnzNK_CvCc1uU6C0sq0Q0lFPY>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 06 Feb 2019 01:03:54 -0000

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

On Tue, Feb 5, 2019 at 7:57 PM Justin Uberti <juberti@google.com> wrote:

>
> On Tue, Feb 5, 2019 at 10:19 AM Roman Shpount <roman@telurix.com> wrote:
>
>> On Tue, Feb 5, 2019 at 10:03 AM Alan Ford <alan.ford@gmail.com> wrote:
>>
>>> If that update was to be made, this goes against the text
>>> in draft-ietf-rtcweb-mdns-ice-candidates-02 which says:
>>>
>>>    An ICE agent that supports mDNS candidates MUST support the situation
>>>    where the hostname resolution results in more than one IP address.
>>>    In this case, the ICE agent MUST take exactly one of the resolved IP
>>>    addresses and ignore the others.  The ICE agent SHOULD, if available,
>>>    use the first IPv6 address resolved, otherwise the first IPv4
>>>    address.
>>>
>>
>> This is obviously not going to work. At the very minimum ICE client
>> should be listening for connectivity checks on all addresses to which FQDN
>> candidate resolves, including IPv4 and IPv6. It also should do connectivity
>> checks to all addresses. Otherwise, if you have two clients, one dual stack
>> and another single stack, they are not going to see each other, since one
>> will be listening and sending connectivity checks via IPv6 and another via
>> IPv4. This is why language about FQDN was removed from mmusic-ice-sip-sdp
>> -- it was broken.
>>
>
>> For ICE to work, you want to include all possible addresses for FQDN in
>> the candidate list and then proceed with nomination as if they were
>> independent candidates.
>>
>
> I don't think this is correct behavior, but it's really beside the point
> since we can ignore it if we have the one-FQDN-per-address concept we
> discussed.
>

I am not sure why this is wrong, but I agree this is besides the point if
we agree on one-FQDN-per-address. If we agree on one-FQDN-per-address,
rtcweb-mdns-ice-candidates needs to be modified to match. Behavior
currently described there (each sides picks an address in random) is
definitely wrong.

Regards,
_____________
Roman Shpount

--00000000000067873705812f4c36
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 Tue, Feb 5, 2019 at 7:57 PM Ju=
stin Uberti &lt;<a href=3D"mailto:juberti@google.com">juberti@google.com</a=
>&gt; wrote:<br></div></div></div><div class=3D"gmail_quote"><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"></div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tu=
e, Feb 5, 2019 at 10:19 AM Roman Shpount &lt;<a href=3D"mailto:roman@teluri=
x.com" target=3D"_blank">roman@telurix.com</a>&gt; wrote:<br></div><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"><div dir=3D"ltr"><div dir=3D"ltr"=
><div><div dir=3D"ltr" class=3D"gmail-m_3233790790765464439gmail-m_31837006=
22067796669gmail_signature">On Tue, Feb 5, 2019 at 10:03 AM Alan Ford &lt;<=
a href=3D"mailto:alan.ford@gmail.com" target=3D"_blank">alan.ford@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 so=
lid rgb(204,204,204);padding-left:1ex"><div>If that update was to be made, =
this goes against the text in=C2=A0draft-ietf-rtcweb-mdns-ice-candidates-02=
 which says:<div><br></div><div><span style=3D"font-size:11px"><font face=
=3D"Menlo">=C2=A0 =C2=A0An ICE agent that supports mDNS candidates MUST sup=
port the situation<br>=C2=A0 =C2=A0where the hostname resolution results in=
 more than one IP address.<br>=C2=A0 =C2=A0In this case, the ICE agent MUST=
 take exactly one of the resolved IP<br>=C2=A0 =C2=A0addresses and ignore t=
he others.=C2=A0 The ICE agent SHOULD, if available,<br>=C2=A0 =C2=A0use th=
e first IPv6 address resolved, otherwise the first IPv4<br>=C2=A0 =C2=A0add=
ress.</font></span></div></div></blockquote><div>=C2=A0</div><div>This is o=
bviously not going to work. At the very minimum ICE client should be listen=
ing for connectivity checks on all addresses to which FQDN candidate resolv=
es, including IPv4 and IPv6. It also should do connectivity checks to all a=
ddresses. Otherwise, if you have two clients, one dual stack and another si=
ngle stack, they are not going to see each other, since one will be listeni=
ng and sending connectivity checks via IPv6 and another via IPv4. This is w=
hy language about FQDN was removed from mmusic-ice-sip-sdp -- it was broken=
.=C2=A0</div></div></div></blockquote><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div><br></div><di=
v>For ICE to work, you want to include all possible addresses for FQDN in t=
he candidate list and then proceed with nomination as if they were independ=
ent candidates.</div></div></div></blockquote><div><br></div><div>I don&#39=
;t think this is correct behavior, but it&#39;s really beside the point sin=
ce we can ignore it if we have the one-FQDN-per-address concept we discusse=
d.=C2=A0<br></div></div></div></blockquote><div><br></div><div>I am not sur=
e why this is wrong, but I agree this is besides the point if we agree on o=
ne-FQDN-per-address. If we agree on one-FQDN-per-address, rtcweb-mdns-ice-c=
andidates needs to be modified to match. Behavior currently described there=
 (each sides picks an address in random) is definitely wrong.</div><div><br=
></div><div>Regards,</div>_____________<br>Roman Shpount<br class=3D"gmail-=
Apple-interchange-newline"><div>=C2=A0</div></div></div>

--00000000000067873705812f4c36--


From nobody Wed Feb  6 03:59:37 2019
Return-Path: <ietf@kuehlewind.net>
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 8C2E0124D68; Wed,  6 Feb 2019 03:59:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
Cc: mmusic-chairs@ietf.org, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.91.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154945436949.31050.7163847983446120931.idtracker@ietfa.amsl.com>
Date: Wed, 06 Feb 2019 03:59:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/svlJvBd5T5baLvFSm2dpXg_aZkQ>
Subject: [MMUSIC] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_char?= =?utf-8?q?ter-ietf-mmusic-04-00=3A_=28with_COMMENT=29?=
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, 06 Feb 2019 11:59:30 -0000

Mirja Kühlewind has entered the following ballot position for
charter-ietf-mmusic-04-00: No Objection

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



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



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

Just wondering if we should approve this now or when ICE is actually closed (to
avoid confusion). Or when is ICE to be expected to be closed?



From nobody Wed Feb  6 23:07:14 2019
Return-Path: <ben@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 ECC07126F72; Wed,  6 Feb 2019 23:07:06 -0800 (PST)
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 Mo4PBHsnoIwV; Wed,  6 Feb 2019 23:07:05 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9F371228B7; Wed,  6 Feb 2019 23:07:05 -0800 (PST)
Received: from [10.0.1.29] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x177732D064593 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 7 Feb 2019 01:07:04 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1549523225; bh=1Enb9Dq22SvtwqmsyLGV2hxergUQ8fusXJ7I6fC64yA=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=RERmqtXCuJdnlWZ8jVV0LQxMIH+6QhwLYEv+O3Tzw3ilacbzZqRwQJxezGXG/XGxK ow3xkUenMENqrG5s4eRBq+5Vwivh7jdrzaR35W3hK5W6i78hHZJcBNle23JzMNw/js QESA+jOUAGq65THaSrt1rOiyeFXaQpYLoIYyRux0=
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.29]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <F6FF007F-0D68-43FB-9841-14DECB4C7563@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_F9176729-A46C-4F13-9C68-BDEDE0F550BC"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Thu, 7 Feb 2019 01:07:01 -0600
In-Reply-To: <154945436949.31050.7163847983446120931.idtracker@ietfa.amsl.com>
Cc: The IESG <iesg@ietf.org>, mmusic-chairs@ietf.org, mmusic@ietf.org
To: =?utf-8?Q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
References: <154945436949.31050.7163847983446120931.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jyoxiv19jLweykxKjJGsG-SEybg>
Subject: Re: [MMUSIC]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_char?= =?utf-8?q?ter-ietf-mmusic-04-00=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: Thu, 07 Feb 2019 07:07:07 -0000

--Apple-Mail=_F9176729-A46C-4F13-9C68-BDEDE0F550BC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Feb 6, 2019, at 5:59 AM, Mirja K=C3=BChlewind <ietf@kuehlewind.net> =
wrote:
>=20
> Mirja K=C3=BChlewind has entered the following ballot position for
> charter-ietf-mmusic-04-00: No Objection
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut =
this
> introductory paragraph, however.)
>=20
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-mmusic/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> Just wondering if we should approve this now or when ICE is actually =
closed (to
> avoid confusion). Or when is ICE to be expected to be closed?

ICE only has one unpublished milestone, and that one is in the RFC =
Editor queue. It will close as soon as that one is processed. They =
won=E2=80=99t be taking on new work.

Thanks!

Ben.


--Apple-Mail=_F9176729-A46C-4F13-9C68-BDEDE0F550BC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlxb2RUACgkQgFZKbJXz
1A3lVg//flv9esHZIgu1QS9pZy4KTTPFaOIlK/p2PyrExCJ+PxOVE+26ng56Fa54
BeBdJg45102ZTPzdCeUuD8Trfkb+F6II0taAL4kQzfm2NvkJ+uLoDVqvmH2oRn9C
/7HsodR3xJVdD4ifdKkzB9XQWl03eQQOQsigR7vE9kH7F8DpPwTmAnfh/vKJglnI
J3hZxxRBB2CI/8+1LsboDZ69tpTdNAnCRtJ09keiK4lrAlwO413A8XUgKempRkUp
RNpKyvGacgRDWGw08gHXPdBqSgM00xb4Wj7A4NoTECM3iaVSsAUT1ACMiwUk5+kB
4MRVC7CVidBPXYKnCM04kj8Ueja4EO8tQTcZI1k3udeux5aqtnE6b3sD37FmWXWP
C5yWYMJuH18HMuL5gOREBO8J6ufypesDN2VeXpJvr6Q1deUdSrsPGi55nK77oCtC
pJn61LMR9wSmN3o57nMApOA8uinBFA4mBYCeLbXsbpP8jxD3lRoZ5S96guGCU2aW
SFB86SIfMb0HJziSV0XdLk/lMxm1dzu9h344kd9md8KjZuZuWt7hxehLk0ho/u4G
21Crm7U5v7tKAOy3gUg6GEQAgmtjpsigGgVfyQi//veKEix4xkaBZRfScr9mWxdF
rNvxj4vzd89J51WCsoacBVY7eQ+7xmimGRAEiUfdXUPQRXwKHc0=
=Fp9f
-----END PGP SIGNATURE-----

--Apple-Mail=_F9176729-A46C-4F13-9C68-BDEDE0F550BC--


From nobody Wed Feb  6 23:08:42 2019
Return-Path: <ben@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 33057130EEB; Wed,  6 Feb 2019 23:08:23 -0800 (PST)
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 NT6mc5HO5EIG; Wed,  6 Feb 2019 23:08:21 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 115DE1228B7; Wed,  6 Feb 2019 23:08:21 -0800 (PST)
Received: from [10.0.1.29] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x1778D5q064798 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 7 Feb 2019 01:08:16 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1549523297; bh=mMr26+Ycwo+kTpxcCyxOwMtLAFe7YJZbDCaOrRllrQY=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=rPTUxbNbkvWqV+vot5x6HbKU0JMD7+yN5keRClIVhR1kHfrSe00bNnvGkRLx77jea 7DfxTFsslKObEIjBQUkfnn+P6xw/6oxGrYQpwJfe2f77fiaVNdGFQER/GuQnCcLWW/ eoTbsISh5g67cqtiiN+i8m50IREWGfll37SwgXlA=
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.29]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <C4394C67-54E8-4148-A48F-492B2256988F@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_3C7E357D-8879-4BAE-AA73-1A9A51DD92BB"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Thu, 7 Feb 2019 01:08:12 -0600
In-Reply-To: <154940416338.32237.8653012939519141336.idtracker@ietfa.amsl.com>
Cc: The IESG <iesg@ietf.org>, mmusic-chairs@ietf.org, mmusic@ietf.org
To: Alissa Cooper <alissa@cooperw.in>
References: <154940416338.32237.8653012939519141336.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ciIic3AR6DtiPNBQQXW8EYA2I8I>
Subject: Re: [MMUSIC] Alissa Cooper's No Objection on charter-ietf-mmusic-04-00: (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, 07 Feb 2019 07:08:24 -0000

--Apple-Mail=_3C7E357D-8879-4BAE-AA73-1A9A51DD92BB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Feb 5, 2019, at 4:02 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>=20
> Alissa Cooper has entered the following ballot position for
> charter-ietf-mmusic-04-00: No Objection
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut =
this
> introductory paragraph, however.)
>=20
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-mmusic/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> I don't think this needs external review.
>=20
> "Maintain the specifications of the Interactive Connectivity =
Establishment
> (ICE) and specify extensions to it with demonstrated interest and =
value."  -->
> Maybe "where there is demonstrated interest and value"? The way it is =
written
> now sounds a bit weird.

I used your suggested text.

>=20
> Isn't CLUE closing soon? I wonder if it still needs to be listed.

I removed CLUE from the =E2=80=9Ccoordinate closely with=E2=80=9D list.

Thanks!

Ben.


--Apple-Mail=_3C7E357D-8879-4BAE-AA73-1A9A51DD92BB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlxb2VwACgkQgFZKbJXz
1A1poA//RKBnQtPOE4w5///BHjbQWXLUlvXe2wYV0/uE5RVQiSL7FvZ0qjAEyw51
5JzUL5U4ejQKY+lXmNCeKYI/Tl2JG0lKR4fUQDYus8R2lPcNiZGRUkrUHVSzmy9s
66DcOw3J7jAzaK9xl9DuiHEj68w62CNrUkGqi0lsD2F84UxLB414HjRHaRXBnDzG
r6h/rCAz7L1PXmbvLN5b8tHesaQFokeM3FpleLdgxqErSlXTm+lkIV66jkid2tkn
EEs2c24G+y6dHs7zkv9dmWuB+saCAxtBZECCk5XWxJFBAbzGpAdzUv2nBFULxg43
VbireHOO8txvz0Xjo+/ChA+nu8zvRKiAZOVpjqKONVEKuYBQyh2BEgprdQEUgUlj
G8z+OrEfeutwngt/IOQOIyQb8tuIa7a0dUChMSe7o/e9Oeu401/QqIGgLuuK7ImA
2WYgPnunpBJw0R3yDqxKfohyvMW1qf41S10zmR0x0UmDCBtAU46lpuovgOOa8xSb
eL68igQ8dbKZToUBY7FMSd3UK45majLtoTqsWzCfHSfqDFymInAcJb37XewsI6cW
N4rGn932VYm8xRyW0dxs6LGBE2Xy0EsC6OGSUXLOFmMxxG0Rv6cxw+YA2Mqkki+c
QwaoewUPCz+/+tIha2FIpMi04grmwSwo0WjJsrBvrOxweEDFqL8=
=HNyf
-----END PGP SIGNATURE-----

--Apple-Mail=_3C7E357D-8879-4BAE-AA73-1A9A51DD92BB--


From nobody Thu Feb  7 04:39:41 2019
Return-Path: <ekr@rtfm.com>
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 E555B12D4F2; Thu,  7 Feb 2019 04:39:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Eric Rescorla <ekr@rtfm.com>
To: "The IESG" <iesg@ietf.org>
Cc: mmusic-chairs@ietf.org, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.91.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154954315683.23487.4570943041962843728.idtracker@ietfa.amsl.com>
Date: Thu, 07 Feb 2019 04:39:16 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2CCSxC2CrA7YKD7PrgD9DYKqS-M>
Subject: [MMUSIC] Eric Rescorla's Abstain on charter-ietf-mmusic-04-01: (with COMMENT)
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, 07 Feb 2019 12:39:17 -0000

Eric Rescorla has entered the following ballot position for
charter-ietf-mmusic-04-01: Abstain

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



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



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

I'm actually not enthusiastic about moving ICE back into MMUSIC. That really
never made sense in terms of the WG members or technology stack. However, I
recognize that I'm in the rough.



From nobody Thu Feb  7 08:01:39 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 13AE6130E9B for <mmusic@ietfa.amsl.com>; Thu,  7 Feb 2019 08:01:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.01
X-Spam-Level: 
X-Spam-Status: No, score=0.01 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 aAPszT6Y1tAy for <mmusic@ietfa.amsl.com>; Thu,  7 Feb 2019 08:01:26 -0800 (PST)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 B829012D826 for <mmusic@ietf.org>; Thu,  7 Feb 2019 08:01:26 -0800 (PST)
Received: by mail-pg1-x530.google.com with SMTP id w7so96602pgp.13 for <mmusic@ietf.org>; Thu, 07 Feb 2019 08:01:26 -0800 (PST)
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=o1g5rkWcKWGEx7n0CudN65EaAdkhaD37UcLCl4jPQ0g=; b=oXsceddh5IRL3aEQRNjvO0NuJTsJzpCpmVHyUupnbgDgYAT6/y1a2fvdMOjb4sQMeD HRNxub2+DVcsVNWfmLEwt2kzxR7tFHNSVcNH7gJCjvn/SVDdolVBj+Wp7LdPuuTlcheI AZqJR+BT9hi/ey3hgTWp3kh0oDhAQ+Kom1v0Elx7O7Lvz4TyHtnkcadOXDir8u1ECt2Z Fxf17cb5mweNo4isJAsWBY70fPYM+lGqiPf6UjOoJ0U0Q6exvhBOP1PI8uMrqttQ0E9A BvnGGDX/g5atp3hQFPOgvZ2ZmWkn4cQxZQpYqQv0sJx6k0t/kmCZNdKywSz9esVN4B26 8Wsw==
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=o1g5rkWcKWGEx7n0CudN65EaAdkhaD37UcLCl4jPQ0g=; b=FD6UQqREw1F2Ag4a+JuiV7P56pxL7+bhaFfbRCf4rXcp6usEmgHp3qDMDQwXdpZRgv b/cn+OECxe7EgZdy07aqczabLOc1yQ3FBMBMQnsSrvH5ElZvUbw0UyMP97V/EaSJNZkq Qq0yUN1F6QKAZIGit8WXoybAF2W0TJ3hacjTADfd78yYpo9oyIOcFF96djQgcBgN+oMC 7HWKQ6A+MeuggJm0ADpHMI1diHNSZs20bsciM0V+G3puzZD/90aqjXL8B1z044PyU+Cu fyIgOMCYrUhqQi561QmWGgcVyrLYKz0wN6tSzN1si4wghZ/zcxu/9r0SQkDsbCulSK8E QF1w==
X-Gm-Message-State: AHQUAuZ5B87eW+SsFUEeVazxMdbJD0DDZ6kNxZ0KV/TsYJtCg3xbXAeq 5kItS2C5UibhLE3Un39DnFjjFVPDPrA=
X-Google-Smtp-Source: AHgI3IZsgyonxKiPefey69xfKWvVsQoDJPP25RuR+KSI6Sre+YF+hxltWAXJ7iJGQitGuOHCPOikPA==
X-Received: by 2002:a63:2a89:: with SMTP id q131mr11895077pgq.216.1549555286260;  Thu, 07 Feb 2019 08:01:26 -0800 (PST)
Received: from mail-pg1-f172.google.com (mail-pg1-f172.google.com. [209.85.215.172]) by smtp.gmail.com with ESMTPSA id v15sm11710316pfn.94.2019.02.07.08.01.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Feb 2019 08:01:25 -0800 (PST)
Received: by mail-pg1-f172.google.com with SMTP id d72so107137pga.9; Thu, 07 Feb 2019 08:01:25 -0800 (PST)
X-Received: by 2002:a63:db04:: with SMTP id e4mr907773pgg.40.1549555284882; Thu, 07 Feb 2019 08:01:24 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com> <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com> <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com> <24551658-0943-431C-B319-D74B5DC169B9@gmail.com> <CAD5OKxtn4TCZCgV_4r17AqUgbFxgk1NjMBNCR0Gcn-67zRJCwQ@mail.gmail.com> <CAOJ7v-1z4P-=RQfUb1o2JGduuVNs3G-HmXNXxuvrM-4XhRH_9w@mail.gmail.com> <CAD5OKxv72sfohGx1pYwsfb8hki8NPRvJ=2bbv+MrX88gk7xg1g@mail.gmail.com>
In-Reply-To: <CAD5OKxv72sfohGx1pYwsfb8hki8NPRvJ=2bbv+MrX88gk7xg1g@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Thu, 7 Feb 2019 11:01:11 -0500
X-Gmail-Original-Message-ID: <CAD5OKxui3MtNmjG+S1jNdo-D6QiLg_Y2=fSXV+XO6U8HXT5fEA@mail.gmail.com>
Message-ID: <CAD5OKxui3MtNmjG+S1jNdo-D6QiLg_Y2=fSXV+XO6U8HXT5fEA@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: Alan Ford <alan.ford@gmail.com>, Simon Perreault <sperreault@jive.com>,  RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>,  Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="00000000000050c2ff05814ff431"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/6kRIpuSedJ5DxEM0snXaBe27F0s>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 07 Feb 2019 16:01:34 -0000

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

Hi All,

>From what I can see there is a new problem identified during mDNS
discussion with using FQDN: If all the candidates are FQDN and these names
do not resolve or resolve to more then one address, so all the candidates
will end up being ignored. ICE agent might end up with no remote candidates
and no candidate pairs to form. I think  RFC 8445 does not handle this
situation, but I might be missing something.

P.S. I am not arguing against FQDN, I am just trying to figure out what
needs to be done to get this documented and operational.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi All,</div><div dir=3D"ltr"><br></div><=
div dir=3D"ltr">From what I can see there is a new problem identified durin=
g mDNS discussion with using FQDN: If all the candidates are FQDN and these=
 names do not resolve or resolve to more then one address, so all the candi=
dates will end up being ignored. ICE agent might end up with no remote cand=
idates and no candidate pairs to form. I think=C2=A0

<span style=3D"color:rgb(0,0,0)">RFC 8445=C2=A0does not handle this situati=
on, but I might be missing something.</span></div><div dir=3D"ltr"><br></di=
v><div dir=3D"ltr"><span style=3D"color:rgb(0,0,0)"></span>P.S. I am not ar=
guing against FQDN, I am just trying to figure out what needs to be done to=
 get this documented and operational.=C2=A0<br clear=3D"all"><div><div dir=
=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature">_____=
________<br>Roman Shpount</div></div></div></div>

--00000000000050c2ff05814ff431--


From nobody Thu Feb  7 08:44:43 2019
Return-Path: <youennf@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 21ADE124BF6; Thu,  7 Feb 2019 08:44:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level: 
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 MLjvombKQcmh; Thu,  7 Feb 2019 08:44:38 -0800 (PST)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 19FA51292F1; Thu,  7 Feb 2019 08:44:38 -0800 (PST)
Received: by mail-lf1-x130.google.com with SMTP id z13so349157lfe.11; Thu, 07 Feb 2019 08:44:38 -0800 (PST)
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:content-transfer-encoding; bh=TiK8Nzc06AQ1Yx6Hpz1jW+UZ+keiCasr59vYPP087zs=; b=lW6ElDmmQL+BRcK3WhRYbhNT1+/Z6029aDIlnwcSMip/PzgMJZCkH5oikPlGrcDlCS 4Eh40ChHbGPqeFsuUaMdz1oyICi1fpI4KcJN7jy4ioGQDGLeyD0P71TsRhRBFCd5Lf5o rWnac8zF2pcLC66FrfMjNtMN2nUB//hkjqKZSEM9DRl0YtJk2cYr4YCkcps18DNWooXA 6R+uSfWTrJJ9z8RkvkqIMAAEWk+kftshgS6qi2ZZ3eTcUbquz/IZYFTl4dm18CvYyqhf V+jCxn8GDFhEUqTiLC5i6XhwFsZf45tAhv76bDt9GfF6mQl2IUAhS0lqgZixc+JA/4sl XsdA==
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=TiK8Nzc06AQ1Yx6Hpz1jW+UZ+keiCasr59vYPP087zs=; b=afvueVC4MpN8Mrln43AiGVSIXbeeSryFvAMtuLFCYiXe5WhSUlSvuhiJYuB6EdH1kc s1EZ436hhOfIpqrBFMgpTInRyHyFVFp4dNCB4hxpbpeW/g5odS/WTdIdiEgDPUN0Rs8h XppULSlnM3y5R5WIzBwGpQg0+SfIq5tZyNoSjGPjjfZYX3WZqpb4jU/PEcF9OSCX8bzF 0DM5zdQCVfDQUDFET7p/wN/ii3aHXZua6b9ksGowzm8J1L8wsiXM5u4/i2XFqhnkt84S knOR7NN9e04sRypSkQGjvKx1XcW3sEbMYfLy81Pk3neiJHiQwjLdf6W/3WVZhU0p+I8+ tMvg==
X-Gm-Message-State: AHQUAuYdhft76FDiHk2WgCqkf+i7VZ5rM2XmPuxNk/eS7GlQAO5Q/Bne TcYbakJai1BnxIjd8XpWOlVY/oUEl6UEPRSNoRk=
X-Google-Smtp-Source: AHgI3IZmKr1AvHe6ihDHz+cxdfBmJBgLDPKQvtdj+6T2qzpfQuUi3KKXscP0Hx7zrXkll0k0syDzntchU1+n7b/y5zE=
X-Received: by 2002:ac2:50c8:: with SMTP id h8mr2678339lfm.35.1549557876140; Thu, 07 Feb 2019 08:44:36 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com> <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com> <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com> <24551658-0943-431C-B319-D74B5DC169B9@gmail.com> <CAD5OKxtn4TCZCgV_4r17AqUgbFxgk1NjMBNCR0Gcn-67zRJCwQ@mail.gmail.com> <CAOJ7v-1z4P-=RQfUb1o2JGduuVNs3G-HmXNXxuvrM-4XhRH_9w@mail.gmail.com> <CAD5OKxv72sfohGx1pYwsfb8hki8NPRvJ=2bbv+MrX88gk7xg1g@mail.gmail.com> <CAD5OKxui3MtNmjG+S1jNdo-D6QiLg_Y2=fSXV+XO6U8HXT5fEA@mail.gmail.com>
In-Reply-To: <CAD5OKxui3MtNmjG+S1jNdo-D6QiLg_Y2=fSXV+XO6U8HXT5fEA@mail.gmail.com>
From: youenn fablet <youennf@gmail.com>
Date: Thu, 7 Feb 2019 08:44:24 -0800
Message-ID: <CANN+akb49vRMMMkaz_TijgQW3MPS_-fHDd_EtoaPCYk7C4EK_w@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Justin Uberti <juberti@google.com>, Simon Perreault <sperreault@jive.com>,  RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Ch9s3E3OqBPgL0ptPzp_9C1pJjE>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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, 07 Feb 2019 16:44:40 -0000

FWIW, Safari Tech Preview introduced last year an mDNS experiment
which is close to Chrome experiment.
This experiment is now on by default in Safari Tech Preview.

As of the case of no ICE candidate at all, this already happens in
Safari 12: by default, mode 3 is used.
As mentioned by Harald, peer reflexive candidates are already used in
some products to enable Safari connection with SFUs or Chrome
instances.

In some cases, implementations had to be updated to better cope with
this, in particular the case of a successful connection triggered by
peer reflexive candidates, leading to not expose server reflexive
candidates to the web site.
Providing guidance to implementors in that area might indeed be good.

Le jeu. 7 f=C3=A9vr. 2019 =C3=A0 08:01, Roman Shpount <roman@telurix.com> a=
 =C3=A9crit :
>
> Hi All,
>
> From what I can see there is a new problem identified during mDNS discuss=
ion with using FQDN: If all the candidates are FQDN and these names do not =
resolve or resolve to more then one address, so all the candidates will end=
 up being ignored. ICE agent might end up with no remote candidates and no =
candidate pairs to form. I think  RFC 8445 does not handle this situation, =
but I might be missing something.
>
> P.S. I am not arguing against FQDN, I am just trying to figure out what n=
eeds to be done to get this documented and operational.
> _____________
> Roman Shpount
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb


From nobody Fri Feb  8 06:29:55 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 979D712008F; Fri,  8 Feb 2019 06:29:53 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, mmusic@ietf.org, ben@nostrum.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.91.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154963619356.31218.2313089296931062909.idtracker@ietfa.amsl.com>
Date: Fri, 08 Feb 2019 06:29:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ufKyN4rKFyR-RswcOx6M28_xdOc>
Subject: [MMUSIC] mmusic - New Meeting Session Request for IETF 104
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, 08 Feb 2019 14:29:54 -0000

A new meeting session request has just been submitted by Flemming Andreasen, a Chair of the mmusic working group.


---------------------------------------------------------
Working Group Name: Multiparty Multimedia Session Control
Area Name: Applications and Real-Time Area
Session Requester: Flemming Andreasen

Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 20
Conflicts to Avoid: 
 First Priority: quic perc tsvarea tsvwg tram tls ice httpbis rtcweb tcpm avtcore sipcore dispatch payload core dots sipbrandy
 Second Priority: clue xrblock rmcat stir regext netvc



People who must be present:
  Ben Campbell
  Flemming Andreasen
  Bo Burman

Resources Requested:

Special Requests:
  
---------------------------------------------------------


From nobody Mon Feb 11 11:03:53 2019
Return-Path: <ietf-secretariat-reply@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 4D9EA131169 for <mmusic@ietf.org>; Mon, 11 Feb 2019 11:03:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <mmusic@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.91.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154991180631.29532.17059429957361428689.idtracker@ietfa.amsl.com>
Date: Mon, 11 Feb 2019 11:03:26 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jnfFsR1CSq3BfwWr4Jk_fh86izQ>
Subject: [MMUSIC] Milestones changed for mmusic WG
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, 11 Feb 2019 19:03:34 -0000

Changed milestone "Submit revised SDP specification to IETF as Proposed
Standard", resolved as "Done".

Changed milestone "Submit SDP Negotiation of DataChannel sub-protocols as
Proposed Standard", resolved as "Done".

Changed milestone "Submit Interactive Connectivity Establishment (ICE) with
SDP offer/answer and SIP as Proposed Standard", set due date to March 2019
from November 2018.

URL: https://datatracker.ietf.org/wg/mmusic/about/


From nobody Mon Feb 11 19:45:38 2019
Return-Path: <ben@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 B008212D4EF; Mon, 11 Feb 2019 19:45:37 -0800 (PST)
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 BOG0BPN0HLcy; Mon, 11 Feb 2019 19:45:35 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E5F012D4E9; Mon, 11 Feb 2019 19:45:34 -0800 (PST)
Received: from [10.0.1.29] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x1C3jVGT010362 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 11 Feb 2019 21:45:33 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1549943134; bh=4tBhuZ4skrxTuvjNrD26EOKnJ+YLMYmi8EmEyUvpM0g=; h=From:Subject:Date:Cc:To; b=OES6wPRZJye3Isqukp+yolZ5SrLXPd9aCKZUgSfWMuqZ9Vsi/mDYAPU6SCsAmiaG+ bUsORnMJFKeKouyoyIWFBWMCz0dsIwJ5fgRo4nPe5K/zXT0tDNM86/vaZ3y4uC0m3q L4+GzNBiNenqww0m4IXPPvJDZmNa5S+S0J1t5+AU=
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.29]
From: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_872EDD49-79E8-405C-8393-67AA4D69D5E4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Message-Id: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com>
Date: Mon, 11 Feb 2019 21:45:30 -0600
Cc: mmusic WG <mmusic@ietf.org>
To: draft-ietf-mmusic-rfc4566bis.all@ietf.org
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/lPP5aZ5nPfTIqdS80X3G71RrE_w>
Subject: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32
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, 12 Feb 2019 03:45:38 -0000

--Apple-Mail=_872EDD49-79E8-405C-8393-67AA4D69D5E4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

This is my AD evaluation of draft-ietf-mmusic-rfc4566bis-32. I have =
several minor substantive comments, and a number of editorial comments =
and nits. I=E2=80=99d like to resolve at least the substantive comments =
prior to IETF last call.

Thanks!

Ben.
----------------------


*** Substantive Comments ***

=C2=A71, last paragraph: The statement that this update is limited to =
essential corrections is demonstrably untrue. For example, this version =
changes a lot of spellings from British English to US English. While =
that might be best for the sake of consistency, it would be hard to =
argue that it is _essential_.

Along the same lines, =C2=A710 does not seem to capture all material =
changes.

=C2=A72, =E2=80=9CMedia Description=E2=80=9D: While true, the text here =
is not a definition of anything but syntax. Please add a sentence or two =
to say what the media description semantically represents.

- Deleted text formerly in =C2=A74.3: The removal of the =E2=80=9Cprivate =
sessions=E2=80=9D section in its entirety deserves some explanatory =
text.

=C2=A75.2: "Unless an SDP extension for NAT traversal is used
(e.g., ICE [RFC8445], ICE TCP [RFC6544]), a local IP address MUST
NOT be used in any context where the SDP description might leave
the scope in which the address is meaningful=E2=80=9D

That doesn=E2=80=99t apply to just any NAT traversal extension does it? =
It seems to require extensions that have scope-resolution properties =
similar to those of ICE.

=C2=A75.8: "Use of the "X-" prefix is NOT RECOMMENDED: instead new (non =
"X-"
prefix) <bwtype> names SHOULD be defined, and then MUST be registered
with IANA in the standard namespace.=E2=80=9D

=E2=80=9CSHOULD be defined=E2=80=9D seems to be in tension with =E2=80=9CM=
UST be registered=E2=80=9D.

=C2=A75.13: "The "k=3D" line (key-field) is obsolete and MUST NOT be =
used.=E2=80=9D
Should it be removed from the field order definition in =C2=A75?

=C2=A76.1: Please state what behavior is meant by =E2=80=9CThis =
attribute is obsoleted=E2=80=9D. For example, MUST not send but SHOULD =
accept? Something different? (This pattern occurs for multiple =
attributes.)

=C2=A76.7.4: "Note that an RTP-based system MUST still send RTCP (if =
RTCP
is used), even if started inactive.=E2=80=9D
Other similar attributes use SHOULD instead of MUST. Is the =
inconsistency intentional?

=C2=A77, last paragraph:
What is the impact of this on RFC 4568 (security descriptions)? That RFC =
seems to allow the use of =E2=80=9Ck=3D=E2=80=9C lines at a MAY level. =
Does this draft need to update that? But more importantly, is it worth =
distinguishing the case of E@E protection of keying material vs the HBH =
protection offered by security descriptions?

=C2=A78 and subsectionsl:

I think there needs to be more clarity about what this draft defines vs =
what was defined in previous versions, and what has changed. For =
example, language to the effect of "XXX was originally defined in RFC =
4566. This document requests IANA to change the reference to =
=E2=80=9CRFC-this=E2=80=9D.=E2=80=9D

=C2=A78.2: "The contact address for all parameters registered below is:
IETF MMUSIC working group <mmusic@ietf.org>=E2=80=9D
Please consider =E2=80=9CThe IETF MMUSIC working group <mmusic@ietf.org> =
or its successor as designated by the IESG.=E2=80=9D

=C2=A78.2.1: "Until that is done, applications SHOULD NOT use these
types and SHOULD NOT declare support for them in SIP capabilities
declarations (even though they exist in the registry created by
[RFC3840]).=E2=80=9D

Should this spec update 3840?

=C2=A78.2.4.2: This section needs some guidance about the maturity of =
specs needed to update attributes defined in previous specs. While the =
registration policy is =E2=80=9Cspec required=E2=80=9D, what happens if =
someone defines FOO in a standards-track RFC, and someone else wants to =
update it with some lower-maturity instrument?

Along the same line, is there any restriction from party B updating an =
attribute defined by party A without consent? That is clear for IETF =
stream RFCs where the IETF retains change control, but might not be =
clear for other specification forms.

=C2=A78.2.8: Are telephone numbers still necessary? Under GDPR rules, we =
should be careful about requiring data unless there is a clear need for =
it.

*** Editorial Comments and Nits ***

=C2=A73.3, 2nd paragraph: "Note that descriptions of multicast sessions =
made only via email or=E2=80=A6=E2=80=9D

The sentence no longer makes sense with the change from =
=E2=80=9Cannouncement=E2=80=9D to =E2=80=9Cdescription=E2=80=9D. If you =
want to avoid the term =E2=80=9Cannouncements=E2=80=9D, consider =
something like =E2=80=9C=E2=80=A6 descriptions of multicast sessions =
sent only via email=E2=80=A6=E2=80=9D

=C2=A74.1: "This address and port is the destination address and =
destination port=E2=80=9D: Plural disagreement. (It was correct in =
4566.)

=C2=A75:
- =E2=80=9C=E2=80=A6 the end of the whole session description - =
whichever=E2=80=A6=E2=80=9D: A dash usually separates two independent =
clauses, much like a semicolon. That is not the cast here; a comma would =
be more appropriate.

- "Some lines in each description are REQUIRED and some are OPTIONAL,=E2=80=
=9D : While I recognize these are unchanged from 4566, the REQUIRED and =
OPTIONAL terms seem like statements of fact rather than normative =
statements.

- "media-, or session-specific basis=E2=80=9D : Incorrect comma usage.

- "An SDP description may contain URIs=E2=80=9D
 I'm not sure this change makes sense. Should it say ''session =
description=E2=80=9D?

- "Text containing fields such as the session-name-field and
information-field=E2=80=9D:
This is ambiguous. Are we talking about text that contains fields, or =
text-containing fields? =46rom context, I assume the latter.

=C2=A75.5: "The "u=3D" line (uri-field) provides URI (Uniform Resource =
Identifier)
as used by WWW clients=E2=80=9D
Missing article before URI

=C2=A75.7:
- "The "c=3D" line (connection-field) contains connection data.=E2=80=9D
The section heading was changed from =E2=80=9Cconnection data=E2=80=9D =
to =E2=80=9Cconnection information=E2=80=9D. Should that change apply =
here, too?

- There are a number of places in this section (and maybe elsewhere) =
where IPv6 was changed to IP6. While I realize 4566 was inconsistent on =
this, wouldn=E2=80=99t it make more sense to change to consistently use =
the more conventional =E2=80=9CIPv6=E2=80=9D?  (Probably also true for =
IP4/IPv4).

- "Multiple addresses or "c=3D" lines MAY be specified on a per media
description basis=E2=80=9D
4566 correctly hyphenated =E2=80=9Cper-media-description basis=E2=80=9D. =
Why were the hyphens removed here?

=C2=A75.8: "A prefix "X-" is defined for <bwtype> names. This is =
intended for
experimental purposes only.=E2=80=9D

Please consider active voice for =E2=80=9Cis defined=E2=80=9D, since in =
this case it obscures the fact that this was defined by an earlier =
version of the spec. Would it make sense to say that previous versions =
defined it, but it is now deprecated?

=C2=A75.9: "A "t=3D" line (time-field) initiates a time description that =
specifies
the start and stop times for a session.=E2=80=9D

I don't understand what it means to "intitiate" a time description. The =
text from 4566 seemed more clear.

=C2=A75.13: "(Attribute scopes in addition to media- and
session- specific may also be defined=E2=80=9D
Should =E2=80=9Cspecific=E2=80=9D be =E2=80=9Clevel=E2=80=9D?

=C2=A75.14:

- "If noncontiguous
ports are required, they must be signaled using a
separate attribute. (There is currently no attribute defined that
can accomplish this. The "a=3Drtcp:" defined in [RFC3605] does not
handle hierarchical encoding.)=E2=80=9D

 This is oddly stated. Is the point that, if non-contiguous ports are =
needed, someone will have to specify a new attribute?

- "This implies that, unlike
limited past practice, there is no implicit grouping defined by
such means and an explicit grouping framework=E2=80=9D

This does considerably more than =E2=80=9Cimply=E2=80=9D it. It states =
it explicitly. Perhaps =E2=80=9CThis means that, unlike=E2=80=A6=E2=80=9D?=


=C2=A76.7: "At most one of recvonly/sendrecv/sendonly/inactive MAY =
appear at
session level=E2=80=9D
Consider something like "occurrence of recvonly, sendrecv, sendonly, or =
inactive=E2=80=9D. (Please don=E2=80=99t use slashes to substitute for =
conjunctions.)

=C2=A76.7.1: "(e.g., an RTP-based system in
recvonly mode SHOULD still send RTCP packets=E2=80=9D
Please don=E2=80=99t use normative keywords in examples. Examples should =
never be normative.

=C2=A711: It seems a shame to completely drop the acknowledgements from =
4566, since the fact that this will obsolete it means people should no =
longer need to read it. I recognize that those acknowledgements do not =
apply to _this_ draft, but one could always include a paragraph of the =
form of =E2=80=9CRFC 4566 also acknowledged=E2=80=A6"




--Apple-Mail=_872EDD49-79E8-405C-8393-67AA4D69D5E4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlxiQVoACgkQgFZKbJXz
1A2MkhAAlieGEpgpx/pAnAa2trUptf8c9gjHbboyKYSog/T25HDIQ3Hkb5XyuZrl
Y/xe13/kUff0WtgmZoyA+tYiadgdoszY4k8zIT2uWiBjrqF30V4WRzeHdn681HX5
4bDladesHrL6iREDgS6rG7uXcj24i5tsNsvHTJMmU5qw1xV3QVJrFXHlTyrQKBAZ
evU/Cp5w89h0J/9z3VpF4zZzOcSlMLckxL4gxTdXDzJq3yFQkgALfZcWCjVgJPn6
LJlt8LYNmFZrtPcnNl5X+BjaZ7cC1WGm38PshVvSWYBTn2N2TWcCKtXZYmTtHKHs
hOq8bitZpzOftoOAvQ1WvwuZgN6HmPPO2ZGuibLzOan5sTA8DWH5On88t+t9myco
DpPEHITSYS1war8ZURtI40Tvl8hjmnZ9HfQrUu3TAu5una2weQAXCDA0KQXXKW6J
PI17+G23NWo37HjiFSukB+HG1pORhsNKDWIC49a3qcIv6SC1QMUrf5X1SMLAgbAK
8CrUZwoB5IY5WgrFQhEQM3g94Xqj3KS8/KY642FXQewxzRk+yTsh2IVcLNN7fBPq
uDa9O36eN+kLOnuRCkrsEcP5rUwtPsyfoii9PFfo01aWQWBUP3Z4aCiAIA8zD8Pg
nisqmdK0l7wGxKkKwhUCYoeUeFivcSEJ8Va862Vj8xL6N/ZZGD8=
=+rf8
-----END PGP SIGNATURE-----

--Apple-Mail=_872EDD49-79E8-405C-8393-67AA4D69D5E4--


From nobody Tue Feb 12 07:41: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 70FCC124C04; Tue, 12 Feb 2019 07:41:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 l7cVOgwPTWxa; Tue, 12 Feb 2019 07:41:38 -0800 (PST)
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 EE5051200B3; Tue, 12 Feb 2019 07:41:37 -0800 (PST)
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 x1CFfXhY018046 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 12 Feb 2019 10:41:35 -0500
To: Ben Campbell <ben@nostrum.com>, draft-ietf-mmusic-rfc4566bis.all@ietf.org
Cc: mmusic WG <mmusic@ietf.org>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <b970d1c5-f9ca-9411-f2a6-9820ed70a7d3@alum.mit.edu>
Date: Tue, 12 Feb 2019 10:41:33 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@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/xNd5gjYBOVYWn1LK5aawi1YcgmE>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32
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, 12 Feb 2019 15:41:40 -0000

On 2/11/19 10:45 PM, Ben Campbell wrote:
> Hi,
> 
> This is my AD evaluation of draft-ietf-mmusic-rfc4566bis-32. I have several minor substantive comments, and a number of editorial comments and nits. I’d like to resolve at least the substantive comments prior to IETF last call.

Thanks Ben. I will start working on these. I may have some questions as 
I work through them. It will take some digging to figure out where some 
of these things came from and why.

	Thanks,
	Paul

> Thanks!
> 
> Ben.
> ----------------------
> 
> 
> *** Substantive Comments ***
> 
> §1, last paragraph: The statement that this update is limited to essential corrections is demonstrably untrue. For example, this version changes a lot of spellings from British English to US English. While that might be best for the sake of consistency, it would be hard to argue that it is _essential_.
> 
> Along the same lines, §10 does not seem to capture all material changes.
> 
> §2, “Media Description”: While true, the text here is not a definition of anything but syntax. Please add a sentence or two to say what the media description semantically represents.
> 
> - Deleted text formerly in §4.3: The removal of the “private sessions” section in its entirety deserves some explanatory text.
> 
> §5.2: "Unless an SDP extension for NAT traversal is used
> (e.g., ICE [RFC8445], ICE TCP [RFC6544]), a local IP address MUST
> NOT be used in any context where the SDP description might leave
> the scope in which the address is meaningful”
> 
> That doesn’t apply to just any NAT traversal extension does it? It seems to require extensions that have scope-resolution properties similar to those of ICE.
> 
> §5.8: "Use of the "X-" prefix is NOT RECOMMENDED: instead new (non "X-"
> prefix) <bwtype> names SHOULD be defined, and then MUST be registered
> with IANA in the standard namespace.”
> 
> “SHOULD be defined” seems to be in tension with “MUST be registered”.
> 
> §5.13: "The "k=" line (key-field) is obsolete and MUST NOT be used.”
> Should it be removed from the field order definition in §5?
> 
> §6.1: Please state what behavior is meant by “This attribute is obsoleted”. For example, MUST not send but SHOULD accept? Something different? (This pattern occurs for multiple attributes.)
> 
> §6.7.4: "Note that an RTP-based system MUST still send RTCP (if RTCP
> is used), even if started inactive.”
> Other similar attributes use SHOULD instead of MUST. Is the inconsistency intentional?
> 
> §7, last paragraph:
> What is the impact of this on RFC 4568 (security descriptions)? That RFC seems to allow the use of “k=“ lines at a MAY level. Does this draft need to update that? But more importantly, is it worth distinguishing the case of E@E protection of keying material vs the HBH protection offered by security descriptions?
> 
> §8 and subsectionsl:
> 
> I think there needs to be more clarity about what this draft defines vs what was defined in previous versions, and what has changed. For example, language to the effect of "XXX was originally defined in RFC 4566. This document requests IANA to change the reference to “RFC-this”.”
> 
> §8.2: "The contact address for all parameters registered below is:
> IETF MMUSIC working group <mmusic@ietf.org>”
> Please consider “The IETF MMUSIC working group <mmusic@ietf.org> or its successor as designated by the IESG.”
> 
> §8.2.1: "Until that is done, applications SHOULD NOT use these
> types and SHOULD NOT declare support for them in SIP capabilities
> declarations (even though they exist in the registry created by
> [RFC3840]).”
> 
> Should this spec update 3840?
> 
> §8.2.4.2: This section needs some guidance about the maturity of specs needed to update attributes defined in previous specs. While the registration policy is “spec required”, what happens if someone defines FOO in a standards-track RFC, and someone else wants to update it with some lower-maturity instrument?
> 
> Along the same line, is there any restriction from party B updating an attribute defined by party A without consent? That is clear for IETF stream RFCs where the IETF retains change control, but might not be clear for other specification forms.
> 
> §8.2.8: Are telephone numbers still necessary? Under GDPR rules, we should be careful about requiring data unless there is a clear need for it.
> 
> *** Editorial Comments and Nits ***
> 
> §3.3, 2nd paragraph: "Note that descriptions of multicast sessions made only via email or…”
> 
> The sentence no longer makes sense with the change from “announcement” to “description”. If you want to avoid the term “announcements”, consider something like “… descriptions of multicast sessions sent only via email…”
> 
> §4.1: "This address and port is the destination address and destination port”: Plural disagreement. (It was correct in 4566.)
> 
> §5:
> - “… the end of the whole session description - whichever…”: A dash usually separates two independent clauses, much like a semicolon. That is not the cast here; a comma would be more appropriate.
> 
> - "Some lines in each description are REQUIRED and some are OPTIONAL,” : While I recognize these are unchanged from 4566, the REQUIRED and OPTIONAL terms seem like statements of fact rather than normative statements.
> 
> - "media-, or session-specific basis” : Incorrect comma usage.
> 
> - "An SDP description may contain URIs”
>   I'm not sure this change makes sense. Should it say ''session description”?
> 
> - "Text containing fields such as the session-name-field and
> information-field”:
> This is ambiguous. Are we talking about text that contains fields, or text-containing fields? From context, I assume the latter.
> 
> §5.5: "The "u=" line (uri-field) provides URI (Uniform Resource Identifier)
> as used by WWW clients”
> Missing article before URI
> 
> §5.7:
> - "The "c=" line (connection-field) contains connection data.”
> The section heading was changed from “connection data” to “connection information”. Should that change apply here, too?
> 
> - There are a number of places in this section (and maybe elsewhere) where IPv6 was changed to IP6. While I realize 4566 was inconsistent on this, wouldn’t it make more sense to change to consistently use the more conventional “IPv6”?  (Probably also true for IP4/IPv4).
> 
> - "Multiple addresses or "c=" lines MAY be specified on a per media
> description basis”
> 4566 correctly hyphenated “per-media-description basis”. Why were the hyphens removed here?
> 
> §5.8: "A prefix "X-" is defined for <bwtype> names. This is intended for
> experimental purposes only.”
> 
> Please consider active voice for “is defined”, since in this case it obscures the fact that this was defined by an earlier version of the spec. Would it make sense to say that previous versions defined it, but it is now deprecated?
> 
> §5.9: "A "t=" line (time-field) initiates a time description that specifies
> the start and stop times for a session.”
> 
> I don't understand what it means to "intitiate" a time description. The text from 4566 seemed more clear.
> 
> §5.13: "(Attribute scopes in addition to media- and
> session- specific may also be defined”
> Should “specific” be “level”?
> 
> §5.14:
> 
> - "If noncontiguous
> ports are required, they must be signaled using a
> separate attribute. (There is currently no attribute defined that
> can accomplish this. The "a=rtcp:" defined in [RFC3605] does not
> handle hierarchical encoding.)”
> 
>   This is oddly stated. Is the point that, if non-contiguous ports are needed, someone will have to specify a new attribute?
> 
> - "This implies that, unlike
> limited past practice, there is no implicit grouping defined by
> such means and an explicit grouping framework”
> 
> This does considerably more than “imply” it. It states it explicitly. Perhaps “This means that, unlike…”?
> 
> §6.7: "At most one of recvonly/sendrecv/sendonly/inactive MAY appear at
> session level”
> Consider something like "occurrence of recvonly, sendrecv, sendonly, or inactive”. (Please don’t use slashes to substitute for conjunctions.)
> 
> §6.7.1: "(e.g., an RTP-based system in
> recvonly mode SHOULD still send RTCP packets”
> Please don’t use normative keywords in examples. Examples should never be normative.
> 
> §11: It seems a shame to completely drop the acknowledgements from 4566, since the fact that this will obsolete it means people should no longer need to read it. I recognize that those acknowledgements do not apply to _this_ draft, but one could always include a paragraph of the form of “RFC 4566 also acknowledged…"
> 
> 
> 


From nobody Tue Feb 12 08:18:32 2019
Return-Path: <ben@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 CDA381288BD; Tue, 12 Feb 2019 08:18:29 -0800 (PST)
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 VHhe5A8yLelh; Tue, 12 Feb 2019 08:18:28 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78864127287; Tue, 12 Feb 2019 08:18:28 -0800 (PST)
Received: from [10.0.1.29] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x1CGINMe036882 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 12 Feb 2019 10:18:24 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1549988305; bh=xgy/RQYJU9AfBYGdoEw/55g4RE+mPKWqE89m5kBLWK8=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=fvA5fKdErnQZOnLJqW9U1vp8QiuSQje8TU0VmXvHzCb+cL5RevZzulD/s5sAQiwOT VtAgnu6fWW2QL7xFe8rYvX0fcsHNu/ZkOqdcCJYaHt6dfY2T+pkHZIheiNU3ib17fH aUIpTbqSH0YTZaPT4fRaZjHMFPHZbKoms+8kttlw=
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.29]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <4F4B6137-618D-4403-8123-E31A3420018F@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_57543CDD-5FF0-4A0A-90B4-21BA211CE135"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Tue, 12 Feb 2019 10:18:21 -0600
In-Reply-To: <b970d1c5-f9ca-9411-f2a6-9820ed70a7d3@alum.mit.edu>
Cc: draft-ietf-mmusic-rfc4566bis.all@ietf.org, mmusic WG <mmusic@ietf.org>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <b970d1c5-f9ca-9411-f2a6-9820ed70a7d3@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/qBVNpgO81OfNwVt1g36TMTO-rC4>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32
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, 12 Feb 2019 16:18:30 -0000

--Apple-Mail=_57543CDD-5FF0-4A0A-90B4-21BA211CE135
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Feb 12, 2019, at 9:41 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>=20
> On 2/11/19 10:45 PM, Ben Campbell wrote:
>> Hi,
>> This is my AD evaluation of draft-ietf-mmusic-rfc4566bis-32. I have =
several minor substantive comments, and a number of editorial comments =
and nits. I=E2=80=99d like to resolve at least the substantive comments =
prior to IETF last call.
>=20
> Thanks Ben. I will start working on these. I may have some questions =
as I work through them. It will take some digging to figure out where =
some of these things came from and why.
>=20

Thanks!

Ben.


--Apple-Mail=_57543CDD-5FF0-4A0A-90B4-21BA211CE135
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlxi8c0ACgkQgFZKbJXz
1A0eog/+JqzqDJHR7qwqbYpOWLM23EgVcL0+8uvRwfU6kg5sjoobLZ6yimLbxSVm
dFF5AMf8LKPLxPnS8LgR3ORfiIQFcCz5xzfHx1ED5K38n1xwkVn84/O7ycphvkQ0
rTqyl/zeJgy1hN1ZKafkqM/rsnp9JI+R1j4S2UpWVtroz9pUrP5QlXn8j7oI0HSA
rL6bVCrlNduDt876AU472SDHzn+lBAAcepNG/yWQnS/OndN9d0jbywyxGpOEMSeM
WSsAAYCz5nETE6r623uP825sBYzG9JMCnA7rPEWS7vygqoTpJsXWUnHM5iKRS6y+
n+YzdXtxTrfx69YUwvPF5LQDNUoFIj8zsQ/JN4J7maGj/j9vrfgONxREKDg6XsT5
ysPu5QwjIsegxrJJYm+srsQAiFvPAt+IucA/Nxd6xxG97NgDBScbZnzjSYoNcowB
JBtgRQ8Tpam+41Q7hX78+HW7gaYCTkVJlAQgZOAaAvrRGIWqe7Wm//0zOHEcEdMW
kOkJ6EWRGUJqUJY65SYv4pecjzun+J+JReTR/2d3DSa1sRFYTl7yPVHmmjNWEGSc
crzsJOVMOGt8bE95LLzsb4WKzNkkKjZZqqm7kzBrgIeYNwNjKcLxvras6W7qpbsF
LCVbTdpJ7ezfqiqFWBK7msoyaeXvyuvsMnHKZLv/1DJBVQam0Bc=
=Fm8G
-----END PGP SIGNATURE-----

--Apple-Mail=_57543CDD-5FF0-4A0A-90B4-21BA211CE135--


From nobody Wed Feb 13 12:16: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 788EC130E5A for <mmusic@ietfa.amsl.com>; Wed, 13 Feb 2019 12:16:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.924
X-Spam-Level: 
X-Spam-Status: No, score=-1.924 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DLVzz7R9UeVg for <mmusic@ietfa.amsl.com>; Wed, 13 Feb 2019 12:16:36 -0800 (PST)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (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 7DEF21310C4 for <mmusic@ietf.org>; Wed, 13 Feb 2019 12:16:36 -0800 (PST)
Received: from resomta-ch2-01v.sys.comcast.net ([69.252.207.97]) by resqmta-ch2-05v.sys.comcast.net with ESMTP id u0Rdgbsv6kzMNu0xOgdZVY; Wed, 13 Feb 2019 20:16:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1550088994; bh=kYLLWoKEGMaZBw+npZSrezr1B2KJ3gDVaI9vBp+y9NI=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=fOxRkZlqRnyeU4XGad2uvcCzpBSjJ6vcYvneBsCizm8DI/U5iM++WcZ3GLeVuOVRS wcdmK4uh17c2YDthFstvmHJEcuGuQPUZ18Tt2uWwRGi0SPiflCSfyah4hokcd2sbdK AY6c4GLO9kZteE25ZmmBHKnPKsGsfC4LrxG3GIBzKFcl8HI8ciN7yh7qsGHIrJfOJ9 Y2zVnzrzSGxNaTBfWfDzNsQqXHFHk2ZdnQwIb4v+dnKELbdLxD5p3DCJ7KQHBQilIf zb9aS+7em55KYpVTjV8Qw6vbwWDC9mJNvjnjS6ND4d8reBc18QRFzXIKWNCKjZJInJ 4F/dpLv5KABnw==
Received: from PaulKyzivatsMBP.localdomain ([24.62.227.142]) by resomta-ch2-01v.sys.comcast.net with ESMTPA id u0xNgJdxIXnyHu0xNgz0h9; Wed, 13 Feb 2019 20:16:34 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedtledruddtfedgudefiecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefrrghulhcumfihiihivhgrthcuoehpkhihiihivhgrthesrghluhhmrdhmihhtrdgvughuqeenucfkphepvdegrdeivddrvddvjedrudegvdenucfrrghrrghmpehhvghloheprfgruhhlmfihiihivhgrthhsofeurfdrlhhotggrlhguohhmrghinhdpihhnvghtpedvgedriedvrddvvdejrddugedvpdhmrghilhhfrhhomhepphhkhiiiihhvrghtsegrlhhumhdrmhhithdrvgguuhdprhgtphhtthhopehmmhhushhitgesihgvthhfrdhorhhgpdhrtghpthhtohepughrrghfthdqihgvthhfqdhmmhhushhitgdqrhhftgegheeiiegsihhsrdgrlhhlsehivghtfhdrohhrghdprhgtphhtthhopegsvghnsehnohhsthhruhhmrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-Xfinity-VMeta: sc=-100;st=legit
To: Ben Campbell <ben@nostrum.com>, draft-ietf-mmusic-rfc4566bis.all@ietf.org
Cc: mmusic WG <mmusic@ietf.org>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu>
Date: Wed, 13 Feb 2019 15:16:33 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@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/1wANIFtmcAWxeGx1rjk7wq97A-Q>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32
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, 13 Feb 2019 20:16:49 -0000

Ben,

Some clarifying questions inline...

On 2/11/19 10:45 PM, Ben Campbell wrote:
> Hi,
> 
> This is my AD evaluation of draft-ietf-mmusic-rfc4566bis-32. I have several minor substantive comments, and a number of editorial comments and nits. I’d like to resolve at least the substantive comments prior to IETF last call.
> 
> Thanks!
> 
> Ben.
> ----------------------
> 
> 
> *** Substantive Comments ***
> 
> §1, last paragraph: The statement that this update is limited to essential corrections is demonstrably untrue. For example, this version changes a lot of spellings from British English to US English. While that might be best for the sake of consistency, it would be hard to argue that it is _essential_.

Agreed. Is it sufficient for me to remove the claim that they are 
essential? (Or do you want me to remove changes that aren't essential.) 
A good number of the changes were made to improve clarity for things 
have been found confusing over the years.

> Along the same lines, §10 does not seem to capture all material changes.

I don't think it would be helpful to enumerate *every* change. But I'll 
do a fresh diff against 4566 and try to identify the *material* changes. 
Possibly bucket some of them into categories and just list those.

> §2, “Media Description”: While true, the text here is not a definition of anything but syntax. Please add a sentence or two to say what the media description semantically represents.

I'm pretty sure this definition has been with us forever. But I'll put 
something in about the semantics.

> - Deleted text formerly in §4.3: The removal of the “private sessions” section in its entirety deserves some explanatory text.

I don't recall why that was removed. I'll try to find the discussion on it.

> §5.2: "Unless an SDP extension for NAT traversal is used
> (e.g., ICE [RFC8445], ICE TCP [RFC6544]), a local IP address MUST
> NOT be used in any context where the SDP description might leave
> the scope in which the address is meaningful”
> 
> That doesn’t apply to just any NAT traversal extension does it? It seems to require extensions that have scope-resolution properties similar to those of ICE.

Hmm. That condition is what was added to the prior language. But the way 
it was was often violated with an assumption that something on the path 
would replace the address. And of course using ICE in this context also 
results in using a different (global) IP when leaving the scope. IIRC 
there was a desire to have a reference to ICE here, but I'll try to come 
up with some more general words for other hypothetical escapes from this 
rule.

> §5.8: "Use of the "X-" prefix is NOT RECOMMENDED: instead new (non "X-"
> prefix) <bwtype> names SHOULD be defined, and then MUST be registered
> with IANA in the standard namespace.”
> 
> “SHOULD be defined” seems to be in tension with “MUST be registered”.

Hmm. Note that we are not *forbidding* the use of the X- prefix. (For 
backward compatibility reasons I think.) Instead, we are saying the the 
X- prefix *SHOULD* NOT be used. So you aren't required to define a 
non-X-prefix (hence the SHOULD), but if you do define one then you MUST 
register it.

I remember there was quite a bit of wordsmithing of this. But I can try 
again. Perhaps we should be stronger, and say that X- prefixes may only 
be used for backward compatibility with existing work, and non-X- 
prefixes MUST be defined and registered for new work.

> §5.13: "The "k=" line (key-field) is obsolete and MUST NOT be used.”
> Should it be removed from the field order definition in §5?

It continues to be mentioned because implementations may need to support 
it for backward compatibility with 4566. In that case they need to know 
where it goes.

> §6.1: Please state what behavior is meant by “This attribute is obsoleted”. For example, MUST not send but SHOULD accept? Something different? (This pattern occurs for multiple attributes.)

I don't recall that we ever discussed the behavior. I think MUST NOT be 
sent is ok. How about MUST accept but MAY ignore?

> §6.7.4: "Note that an RTP-based system MUST still send RTCP (if RTCP
> is used), even if started inactive.”
> Other similar attributes use SHOULD instead of MUST. Is the inconsistency intentional?

IIRC it indeed was intentional, because of past interoperability 
problems. But I would like to pass the buck on this to an RTCP expert.

> §7, last paragraph:
> What is the impact of this on RFC 4568 (security descriptions)? That RFC seems to allow the use of “k=“ lines at a MAY level. Does this draft need to update that? But more importantly, is it worth distinguishing the case of E@E protection of keying material vs the HBH protection offered by security descriptions?

I didn't write this part. Again I want to pass the buck to an expert. 
I'll see if I can find who wrote this text.

> §8 and subsectionsl:
> 
> I think there needs to be more clarity about what this draft defines vs what was defined in previous versions, and what has changed. For example, language to the effect of "XXX was originally defined in RFC 4566. This document requests IANA to change the reference to “RFC-this”.”

OK. Good idea!

> §8.2: "The contact address for all parameters registered below is:
> IETF MMUSIC working group <mmusic@ietf.org>”
> Please consider “The IETF MMUSIC working group <mmusic@ietf.org> or its successor as designated by the IESG.”

Will do.

> §8.2.1: "Until that is done, applications SHOULD NOT use these
> types and SHOULD NOT declare support for them in SIP capabilities
> declarations (even though they exist in the registry created by
> [RFC3840]).”
> 
> Should this spec update 3840?

Leaving 3840 as-is doesn't hurt anything. As long as these aren't used 
in m-lines then usage in 3840/3841 will be moot.

> §8.2.4.2: This section needs some guidance about the maturity of specs needed to update attributes defined in previous specs. While the registration policy is “spec required”, what happens if someone defines FOO in a standards-track RFC, and someone else wants to update it with some lower-maturity instrument?

Good point. But I think it will be tricky to come up with a suitable 
rule. I think I will need help.

> Along the same line, is there any restriction from party B updating an attribute defined by party A without consent? That is clear for IETF stream RFCs where the IETF retains change control, but might not be clear for other specification forms.

Can that be separated from you above point? Obviously we often have 
different authors for an update or bis, but it is ok because both are 
operating within the rules for the same document stream. I assume 
something similar applies for other SDOs. But I can't find the 
definition of "Specification Required" right now. Can there be a 
document that satisfies "Specification Required" that doesn't have such 
rules?

I need help here.

> §8.2.8: Are telephone numbers still necessary? Under GDPR rules, we should be careful about requiring data unless there is a clear need for it.

IMO they aren't. We struggle with contact info for IANA all the time. 
Most the time for new things we end up identifying a WG or IESG, or some 
other organization. When contact info for individuals is used the 
contact info other than name is likely be be obsolete before it is used. 
But doesn't an email address also run afoul of the GDPR rules? Clearly 
we need *some* means of contact. Maybe we should require email OR phone# 
OR postal address. (OR Facebook id, ...?)

Perhaps we should say that this SHOULD identify an organization rather 
than an individual. Organizations don't fall under GDPR do that?

> *** Editorial Comments and Nits ***
> 
> §3.3, 2nd paragraph: "Note that descriptions of multicast sessions made only via email or…”
> 
> The sentence no longer makes sense with the change from “announcement” to “description”. If you want to avoid the term “announcements”, consider something like “… descriptions of multicast sessions sent only via email…”

OK

> §4.1: "This address and port is the destination address and destination port”: Plural disagreement. (It was correct in 4566.)

Obviously an intentional change. Don't know why. Will fix.

> §5:
> - “… the end of the whole session description - whichever…”: A dash usually separates two independent clauses, much like a semicolon. That is not the cast here; a comma would be more appropriate.

OK

> - "Some lines in each description are REQUIRED and some are OPTIONAL,” : While I recognize these are unchanged from 4566, the REQUIRED and OPTIONAL terms seem like statements of fact rather than normative statements.

OK

> - "media-, or session-specific basis” : Incorrect comma usage.

IIUC this is an "Oxford comma", and the use of it is controversial. Does 
IETF have a policy on its use?

(Or we can leave it for the editor to decide.)

> - "An SDP description may contain URIs”
>   I'm not sure this change makes sense. Should it say ''session description”?

I don't know where that came from. I agree. Will fix.

> - "Text containing fields such as the session-name-field and
> information-field”:
> This is ambiguous. Are we talking about text that contains fields, or text-containing fields? From context, I assume the latter.

Yes. Will fix.

> §5.5: "The "u=" line (uri-field) provides URI (Uniform Resource Identifier)
> as used by WWW clients”
> Missing article before URI

OK

> §5.7:
> - "The "c=" line (connection-field) contains connection data.”
> The section heading was changed from “connection data” to “connection information”. Should that change apply here, too?

That seems pretty circular. How about:

"The "c=" line (connection-field) contains information necessary to 
establish a connection.”?

> - There are a number of places in this section (and maybe elsewhere) where IPv6 was changed to IP6. While I realize 4566 was inconsistent on this, wouldn’t it make more sense to change to consistently use the more conventional “IPv6”?  (Probably also true for IP4/IPv4).

Agree. Will fix.

> - "Multiple addresses or "c=" lines MAY be specified on a per media
> description basis”
> 4566 correctly hyphenated “per-media-description basis”. Why were the hyphens removed here?

I see the same text in both for this. OTOH we are using "per-media" in 
the same section. I will change it.

> §5.8: "A prefix "X-" is defined for <bwtype> names. This is intended for
> experimental purposes only.”
> 
> Please consider active voice for “is defined”, since in this case it obscures the fact that this was defined by an earlier version of the spec. Would it make sense to say that previous versions defined it, but it is now deprecated?

Yes, I can reword to say that this was defined in 4566. The next 
sentence already talks about intended usage now, and we already 
discussed changes to that above.

> §5.9: "A "t=" line (time-field) initiates a time description that specifies
> the start and stop times for a session.”
> 
> I don't understand what it means to "intitiate" a time description. The text from 4566 seemed more clear.

I reworked this considerably to resolve ambiguities that came up, 
particularly around z=. The ABNF was hard to follow and wrong after we 
concluded that z= only modifies the preceding r=. This led me to define 
time-description in the ABNF. (Because the syntax used to permit z= 
without r=, which is nonsense.) The time-description is a multi-line 
sequence that begins with t= that has optional r= and z= following, 
according to the syntax. Here we are trying to talk about it in English.

"initiate" seems fine to me (since I wrote it), but I can change it to 
something like "starts" or "marks the beginning of".

> §5.13: "(Attribute scopes in addition to media- and
> session- specific may also be defined”
> Should “specific” be “level”?

Yes, that seems better.

> §5.14:
> 
> - "If noncontiguous
> ports are required, they must be signaled using a
> separate attribute. (There is currently no attribute defined that
> can accomplish this. The "a=rtcp:" defined in [RFC3605] does not
> handle hierarchical encoding.)”
> 
>   This is oddly stated. Is the point that, if non-contiguous ports are needed, someone will have to specify a new attribute?

Yes. I will try to clarify.

> - "This implies that, unlike
> limited past practice, there is no implicit grouping defined by
> such means and an explicit grouping framework”
> 
> This does considerably more than “imply” it. It states it explicitly. Perhaps “This means that, unlike…”?

I'll work on it. I agree that "imply" is wrong here. I think it is 
trying to say that there was some limited past practice of using the 
same transport address to indicate grouping. This is saying that such 
practice was wrong, and that grouping requires an explicit mechanism. 
But interestingly it doesn't say that in normative language. Do you 
think we need something normative here?

> §6.7: "At most one of recvonly/sendrecv/sendonly/inactive MAY appear at
> session level”
> Consider something like "occurrence of recvonly, sendrecv, sendonly, or inactive”. (Please don’t use slashes to substitute for conjunctions.)

OK.

> §6.7.1: "(e.g., an RTP-based system in
> recvonly mode SHOULD still send RTCP packets”
> Please don’t use normative keywords in examples. Examples should never be normative.

OK

> §11: It seems a shame to completely drop the acknowledgements from 4566, since the fact that this will obsolete it means people should no longer need to read it. I recognize that those acknowledgements do not apply to _this_ draft, but one could always include a paragraph of the form of “RFC 4566 also acknowledged…"

I agree. Will do.

	Thanks,
	Paul


From nobody Wed Feb 13 15:33:07 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 E33E9130E9C; Wed, 13 Feb 2019 15:33:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.19
X-Spam-Level: 
X-Spam-Status: No, score=-4.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wTtx4-r_5uFd; Wed, 13 Feb 2019 15:33:04 -0800 (PST)
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 C71E3128B01; Wed, 13 Feb 2019 15:33:03 -0800 (PST)
Received: from [81.187.2.149] (port=35235 helo=[192.168.0.78]) 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 1gu41P-0001q0-8K; Wed, 13 Feb 2019 23:32:59 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu>
Date: Wed, 13 Feb 2019 23:32:51 +0000
Cc: Ben Campbell <ben@nostrum.com>, draft-ietf-mmusic-rfc4566bis.all@ietf.org,  mmusic WG <mmusic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E6D4F528-3738-4568-80E8-A2578D0B7C7D@csperkins.org>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/P24F_cgoo8pAQ1tx9VCbmyM3rBY>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32
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, 13 Feb 2019 23:33:07 -0000

Hi,

Some comments inline.

> On 13 Feb 2019, at 20:16, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
> Ben,
>=20
> Some clarifying questions inline...
>=20
> On 2/11/19 10:45 PM, Ben Campbell wrote:
>> Hi,
>> This is my AD evaluation of draft-ietf-mmusic-rfc4566bis-32. I have =
several minor substantive comments, and a number of editorial comments =
and nits. I=E2=80=99d like to resolve at least the substantive comments =
prior to IETF last call.
>> Thanks!
>> Ben.
>> ----------------------
>> *** Substantive Comments ***
>> =C2=A71, last paragraph: The statement that this update is limited to =
essential corrections is demonstrably untrue. For example, this version =
changes a lot of spellings from British English to US English. While =
that might be best for the sake of consistency, it would be hard to =
argue that it is _essential_.
>=20
> Agreed. Is it sufficient for me to remove the claim that they are =
essential? (Or do you want me to remove changes that aren't essential.) =
A good number of the changes were made to improve clarity for things =
have been found confusing over the years.
>=20
>> Along the same lines, =C2=A710 does not seem to capture all material =
changes.
>=20
> I don't think it would be helpful to enumerate *every* change. But =
I'll do a fresh diff against 4566 and try to identify the *material* =
changes. Possibly bucket some of them into categories and just list =
those.
>=20
>> =C2=A72, =E2=80=9CMedia Description=E2=80=9D: While true, the text =
here is not a definition of anything but syntax. Please add a sentence =
or two to say what the media description semantically represents.
>=20
> I'm pretty sure this definition has been with us forever. But I'll put =
something in about the semantics.
>=20
>> - Deleted text formerly in =C2=A74.3: The removal of the =E2=80=9Cpriva=
te sessions=E2=80=9D section in its entirety deserves some explanatory =
text.
>=20
> I don't recall why that was removed. I=E2=80=99ll try to find the =
discussion on it.

http://mailarchive.ietf.org/arch/msg/mmusic/W82Ba0vOboPUqbfWiZ0yJZqZMTQ=20=


>> =C2=A75.2: "Unless an SDP extension for NAT traversal is used
>> (e.g., ICE [RFC8445], ICE TCP [RFC6544]), a local IP address MUST
>> NOT be used in any context where the SDP description might leave
>> the scope in which the address is meaningful=E2=80=9D
>> That doesn=E2=80=99t apply to just any NAT traversal extension does =
it? It seems to require extensions that have scope-resolution properties =
similar to those of ICE.
>=20
> Hmm. That condition is what was added to the prior language. But the =
way it was was often violated with an assumption that something on the =
path would replace the address. And of course using ICE in this context =
also results in using a different (global) IP when leaving the scope. =
IIRC there was a desire to have a reference to ICE here, but I'll try to =
come up with some more general words for other hypothetical escapes from =
this rule.
>=20
>> =C2=A75.8: "Use of the "X-" prefix is NOT RECOMMENDED: instead new =
(non "X-"
>> prefix) <bwtype> names SHOULD be defined, and then MUST be registered
>> with IANA in the standard namespace.=E2=80=9D
>> =E2=80=9CSHOULD be defined=E2=80=9D seems to be in tension with =
=E2=80=9CMUST be registered=E2=80=9D.
>=20
> Hmm. Note that we are not *forbidding* the use of the X- prefix. (For =
backward compatibility reasons I think.) Instead, we are saying the the =
X- prefix *SHOULD* NOT be used. So you aren't required to define a =
non-X-prefix (hence the SHOULD), but if you do define one then you MUST =
register it.
>=20
> I remember there was quite a bit of wordsmithing of this. But I can =
try again. Perhaps we should be stronger, and say that X- prefixes may =
only be used for backward compatibility with existing work, and non-X- =
prefixes MUST be defined and registered for new work.
>=20
>> =C2=A75.13: "The "k=3D" line (key-field) is obsolete and MUST NOT be =
used.=E2=80=9D
>> Should it be removed from the field order definition in =C2=A75?
>=20
> It continues to be mentioned because implementations may need to =
support it for backward compatibility with 4566. In that case they need =
to know where it goes.
>=20
>> =C2=A76.1: Please state what behavior is meant by =E2=80=9CThis =
attribute is obsoleted=E2=80=9D. For example, MUST not send but SHOULD =
accept? Something different? (This pattern occurs for multiple =
attributes.)

=E2=80=9Cobsoleted" -> "obsolete=E2=80=9D maybe?

> I don't recall that we ever discussed the behavior. I think MUST NOT =
be sent is ok. How about MUST accept but MAY ignore?

In general, this might be different for declarative and offer/answer =
uses of SDP? A lot of the obsolete attributes are things that were only =
ever really used in declarative applications of SDP.

>> =C2=A76.7.4: "Note that an RTP-based system MUST still send RTCP (if =
RTCP
>> is used), even if started inactive.=E2=80=9D
>> Other similar attributes use SHOULD instead of MUST. Is the =
inconsistency intentional?
>=20
> IIRC it indeed was intentional, because of past interoperability =
problems. But I would like to pass the buck on this to an RTCP expert.

I agree that MUST send RTCP even if started inactive is correct.

>> =C2=A77, last paragraph:
>> What is the impact of this on RFC 4568 (security descriptions)? That =
RFC seems to allow the use of =E2=80=9Ck=3D=E2=80=9C lines at a MAY =
level. Does this draft need to update that? But more importantly, is it =
worth distinguishing the case of E@E protection of keying material vs =
the HBH protection offered by security descriptions?
>=20
> I didn't write this part. Again I want to pass the buck to an expert. =
I'll see if I can find who wrote this text.
>=20
>> =C2=A78 and subsectionsl:
>> I think there needs to be more clarity about what this draft defines =
vs what was defined in previous versions, and what has changed. For =
example, language to the effect of "XXX was originally defined in RFC =
4566. This document requests IANA to change the reference to =
=E2=80=9CRFC-this=E2=80=9D.=E2=80=9D
>=20
> OK. Good idea!
>=20
>> =C2=A78.2: "The contact address for all parameters registered below =
is:
>> IETF MMUSIC working group <mmusic@ietf.org>=E2=80=9D
>> Please consider =E2=80=9CThe IETF MMUSIC working group =
<mmusic@ietf.org> or its successor as designated by the IESG.=E2=80=9D
>=20
> Will do.
>=20
>> =C2=A78.2.1: "Until that is done, applications SHOULD NOT use these
>> types and SHOULD NOT declare support for them in SIP capabilities
>> declarations (even though they exist in the registry created by
>> [RFC3840]).=E2=80=9D
>> Should this spec update 3840?
>=20
> Leaving 3840 as-is doesn't hurt anything. As long as these aren't used =
in m-lines then usage in 3840/3841 will be moot.
>=20
>> =C2=A78.2.4.2: This section needs some guidance about the maturity of =
specs needed to update attributes defined in previous specs. While the =
registration policy is =E2=80=9Cspec required=E2=80=9D, what happens if =
someone defines FOO in a standards-track RFC, and someone else wants to =
update it with some lower-maturity instrument?
>=20
> Good point. But I think it will be tricky to come up with a suitable =
rule. I think I will need help.
>=20
>> Along the same line, is there any restriction from party B updating =
an attribute defined by party A without consent? That is clear for IETF =
stream RFCs where the IETF retains change control, but might not be =
clear for other specification forms.
>=20
> Can that be separated from you above point? Obviously we often have =
different authors for an update or bis, but it is ok because both are =
operating within the rules for the same document stream. I assume =
something similar applies for other SDOs. But I can't find the =
definition of "Specification Required" right now. Can there be a =
document that satisfies "Specification Required" that doesn't have such =
rules?
>=20
> I need help here.

Specification Required is RFC 8126, section 4.6. Essentially it punts to =
the designated expert for the registry, but says nothing about priority =
between SDOs.

>> =C2=A78.2.8: Are telephone numbers still necessary? Under GDPR rules, =
we should be careful about requiring data unless there is a clear need =
for it.
>=20
> IMO they aren't. We struggle with contact info for IANA all the time. =
Most the time for new things we end up identifying a WG or IESG, or some =
other organization. When contact info for individuals is used the =
contact info other than name is likely be be obsolete before it is used. =
But doesn't an email address also run afoul of the GDPR rules? Clearly =
we need *some* means of contact. Maybe we should require email OR phone# =
OR postal address. (OR Facebook id, ...?)
>=20
> Perhaps we should say that this SHOULD identify an organization rather =
than an individual. Organizations don=E2=80=99t fall under GDPR do that?

Does IANA not have a policy for this?

>> *** Editorial Comments and Nits ***
>> =C2=A73.3, 2nd paragraph: "Note that descriptions of multicast =
sessions made only via email or=E2=80=A6=E2=80=9D
>> The sentence no longer makes sense with the change from =
=E2=80=9Cannouncement=E2=80=9D to =E2=80=9Cdescription=E2=80=9D. If you =
want to avoid the term =E2=80=9Cannouncements=E2=80=9D, consider =
something like =E2=80=9C=E2=80=A6 descriptions of multicast sessions =
sent only via email=E2=80=A6=E2=80=9D
>=20
> OK
>=20
>> =C2=A74.1: "This address and port is the destination address and =
destination port=E2=80=9D: Plural disagreement. (It was correct in =
4566.)
>=20
> Obviously an intentional change. Don't know why. Will fix.
>=20
>> =C2=A75:
>> - =E2=80=9C=E2=80=A6 the end of the whole session description - =
whichever=E2=80=A6=E2=80=9D: A dash usually separates two independent =
clauses, much like a semicolon. That is not the cast here; a comma would =
be more appropriate.
>=20
> OK
>=20
>> - "Some lines in each description are REQUIRED and some are =
OPTIONAL,=E2=80=9D : While I recognize these are unchanged from 4566, =
the REQUIRED and OPTIONAL terms seem like statements of fact rather than =
normative statements.
>=20
> OK
>=20
>> - "media-, or session-specific basis=E2=80=9D : Incorrect comma =
usage.
>=20
> IIUC this is an "Oxford comma", and the use of it is controversial. =
Does IETF have a policy on its use?
>=20
> (Or we can leave it for the editor to decide.)
>=20
>> - "An SDP description may contain URIs=E2=80=9D
>>  I'm not sure this change makes sense. Should it say ''session =
description=E2=80=9D?
>=20
> I don't know where that came from. I agree. Will fix.
>=20
>> - "Text containing fields such as the session-name-field and
>> information-field=E2=80=9D:
>> This is ambiguous. Are we talking about text that contains fields, or =
text-containing fields? =46rom context, I assume the latter.
>=20
> Yes. Will fix.
>=20
>> =C2=A75.5: "The "u=3D" line (uri-field) provides URI (Uniform =
Resource Identifier)
>> as used by WWW clients=E2=80=9D
>> Missing article before URI
>=20
> OK
>=20
>> =C2=A75.7:
>> - "The "c=3D" line (connection-field) contains connection data.=E2=80=9D=

>> The section heading was changed from =E2=80=9Cconnection data=E2=80=9D =
to =E2=80=9Cconnection information=E2=80=9D. Should that change apply =
here, too?
>=20
> That seems pretty circular. How about:
>=20
> "The "c=3D" line (connection-field) contains information necessary to =
establish a connection.=E2=80=9D?
>=20
>> - There are a number of places in this section (and maybe elsewhere) =
where IPv6 was changed to IP6. While I realize 4566 was inconsistent on =
this, wouldn=E2=80=99t it make more sense to change to consistently use =
the more conventional =E2=80=9CIPv6=E2=80=9D?  (Probably also true for =
IP4/IPv4).
>=20
> Agree. Will fix.
>=20
>> - "Multiple addresses or "c=3D" lines MAY be specified on a per media
>> description basis=E2=80=9D
>> 4566 correctly hyphenated =E2=80=9Cper-media-description basis=E2=80=9D=
. Why were the hyphens removed here?
>=20
> I see the same text in both for this. OTOH we are using "per-media" in =
the same section. I will change it.
>=20
>> =C2=A75.8: "A prefix "X-" is defined for <bwtype> names. This is =
intended for
>> experimental purposes only.=E2=80=9D
>> Please consider active voice for =E2=80=9Cis defined=E2=80=9D, since =
in this case it obscures the fact that this was defined by an earlier =
version of the spec. Would it make sense to say that previous versions =
defined it, but it is now deprecated?
>=20
> Yes, I can reword to say that this was defined in 4566. The next =
sentence already talks about intended usage now, and we already =
discussed changes to that above.
>=20
>> =C2=A75.9: "A "t=3D" line (time-field) initiates a time description =
that specifies
>> the start and stop times for a session.=E2=80=9D
>> I don't understand what it means to "intitiate" a time description. =
The text from 4566 seemed more clear.
>=20
> I reworked this considerably to resolve ambiguities that came up, =
particularly around z=3D. The ABNF was hard to follow and wrong after we =
concluded that z=3D only modifies the preceding r=3D. This led me to =
define time-description in the ABNF. (Because the syntax used to permit =
z=3D without r=3D, which is nonsense.) The time-description is a =
multi-line sequence that begins with t=3D that has optional r=3D and z=3D =
following, according to the syntax. Here we are trying to talk about it =
in English.
>=20
> "initiate" seems fine to me (since I wrote it), but I can change it to =
something like "starts" or "marks the beginning of".
>=20
>> =C2=A75.13: "(Attribute scopes in addition to media- and
>> session- specific may also be defined=E2=80=9D
>> Should =E2=80=9Cspecific=E2=80=9D be =E2=80=9Clevel=E2=80=9D?
>=20
> Yes, that seems better.
>=20
>> =C2=A75.14:
>> - "If noncontiguous
>> ports are required, they must be signaled using a
>> separate attribute. (There is currently no attribute defined that
>> can accomplish this. The "a=3Drtcp:" defined in [RFC3605] does not
>> handle hierarchical encoding.)=E2=80=9D
>>  This is oddly stated. Is the point that, if non-contiguous ports are =
needed, someone will have to specify a new attribute?
>=20
> Yes. I will try to clarify.
>=20
>> - "This implies that, unlike
>> limited past practice, there is no implicit grouping defined by
>> such means and an explicit grouping framework=E2=80=9D
>> This does considerably more than =E2=80=9Cimply=E2=80=9D it. It =
states it explicitly. Perhaps =E2=80=9CThis means that, unlike=E2=80=A6=E2=
=80=9D?
>=20
> I'll work on it. I agree that "imply" is wrong here. I think it is =
trying to say that there was some limited past practice of using the =
same transport address to indicate grouping. This is saying that such =
practice was wrong, and that grouping requires an explicit mechanism. =
But interestingly it doesn't say that in normative language. Do you =
think we need something normative here?
>=20
>> =C2=A76.7: "At most one of recvonly/sendrecv/sendonly/inactive MAY =
appear at
>> session level=E2=80=9D
>> Consider something like "occurrence of recvonly, sendrecv, sendonly, =
or inactive=E2=80=9D. (Please don=E2=80=99t use slashes to substitute =
for conjunctions.)
>=20
> OK.
>=20
>> =C2=A76.7.1: "(e.g., an RTP-based system in
>> recvonly mode SHOULD still send RTCP packets=E2=80=9D
>> Please don=E2=80=99t use normative keywords in examples. Examples =
should never be normative.
>=20
> OK
>=20
>> =C2=A711: It seems a shame to completely drop the acknowledgements =
from 4566, since the fact that this will obsolete it means people should =
no longer need to read it. I recognize that those acknowledgements do =
not apply to _this_ draft, but one could always include a paragraph of =
the form of =E2=80=9CRFC 4566 also acknowledged=E2=80=A6"
>=20
> I agree. Will do.
>=20
> 	Thanks,
> 	Paul
>=20



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





From nobody Mon Feb 18 12:24:10 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 006DF130F00; Mon, 18 Feb 2019 12:24:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 LsyynQY_B323; Mon, 18 Feb 2019 12:24:07 -0800 (PST)
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 26044130E8A; Mon, 18 Feb 2019 12:24:06 -0800 (PST)
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 x1IKNtjE004513 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 18 Feb 2019 15:23:56 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: Ben Campbell <ben@nostrum.com>, draft-ietf-mmusic-rfc4566bis.all@ietf.org
Cc: mmusic WG <mmusic@ietf.org>, "'Colin Perkins'" <csp@csperkins.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu>
Message-ID: <355f8125-87f8-6372-8289-126fa126ccb9@alum.mit.edu>
Date: Mon, 18 Feb 2019 15:23:55 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@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/8vxLtV6iSK2WW5oUvEGiyEW4nqY>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
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, 18 Feb 2019 20:24:09 -0000

> On 2/11/19 10:45 PM, Ben Campbell wrote:

>> §2, “Media Description”: While true, the text here is not a definition 
>> of anything but syntax. Please add a sentence or two to say what the 
>> media description semantically represents.
I'm having trouble finding a suitable semantic definition of Media 
Description.

My first thought is that it provides the information necessary to 
establish a media session. But while *Multimedia Session* is described, 
media Session isn't defined in the document.

I looked at RFC7656 (Taxonomy) for a definition, but it doesn't have one 
either. It defines RTP Session, and Multimedia Session as one or more 
RTP Sessions. That is close, but in SDP media sessions need not be RTP.

Is there any suitable existing definition???

If not, then how about:

"A Media Description contains the information needed for one party to 
establish an application layer network protocol connection to another 
party." ???

OR

"A Media Description contains the information needed for one party to 
establish a Media Session with another party."

"A Media Session is an application layer network protocol connection 
between two parties."

It seems important to get this right! It is essentially a broadening of 
RFC7656 beyond RTP.

	Thanks,
	Paul



From nobody Mon Feb 18 12:49: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 8DEB1130FE8; Mon, 18 Feb 2019 12:49:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 jAIHCuhNSu73; Mon, 18 Feb 2019 12:49:38 -0800 (PST)
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 9291D128BCC; Mon, 18 Feb 2019 12:49:38 -0800 (PST)
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 x1IKnTb1006188 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 18 Feb 2019 15:49:30 -0500
To: Colin Perkins <csp@csperkins.org>
Cc: Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>, draft-ietf-mmusic-rfc4566bis.all@ietf.org
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu> <E6D4F528-3738-4568-80E8-A2578D0B7C7D@csperkins.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <30850d4c-9fe2-8d45-4b7c-8ccb36f79ade@alum.mit.edu>
Date: Mon, 18 Feb 2019 15:49:29 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <E6D4F528-3738-4568-80E8-A2578D0B7C7D@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/8wF22L0ssV_M6UWgcXI7DBTY_Is>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Private Sessions
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, 18 Feb 2019 20:49:40 -0000

On 2/13/19 6:32 PM, Colin Perkins wrote:
>> On 2/11/19 10:45 PM, Ben Campbell wrote:
>>> - Deleted text formerly in §4.3: The removal of the “private sessions” section in its entirety deserves some explanatory text.
>>
>> I don't recall why that was removed. I’ll try to find the discussion on it.
> 
> http://mailarchive.ietf.org/arch/msg/mmusic/W82Ba0vOboPUqbfWiZ0yJZqZMTQ

That is a reply from Christer. The relevant part says:

> My suggestion would be to remove the whole section. I can't remember any discussion where one would have used private vs public sessions. The Security Considerations should then cover encryption etc of SDP information.

We managed to do the part that deletes the Private Sessions section, but 
not the update to Security Considerations. When looked at from this 
perspective, Security Considerations does seem lacking.

Ben, will you be happy if this is addressed in Security Considerations? 
If so I'll open another discussion about that.

	Thanks,
	Paul


From nobody Mon Feb 18 13:11:18 2019
Return-Path: <ben@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 B9A15130F7C; Mon, 18 Feb 2019 13:11:16 -0800 (PST)
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 B_6EM9_pQnhN; Mon, 18 Feb 2019 13:11:14 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39A9C128BCC; Mon, 18 Feb 2019 13:11:14 -0800 (PST)
Received: from [10.0.1.29] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x1ILB0fa029307 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 18 Feb 2019 15:11:01 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1550524262; bh=WZoMqdlSrSWCcROl8iWqEC/I2oJR7itboBMxpjAqpGo=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=Syepe4PXxXgDe57dfM16IafOKgkyAD/eiCHuSrDkEnvB6EEPkxJq9TvHUfrADMygW cx3ZJ+SY7Q4j34TtWUylYXJhbA4iZskgolGruuN9IUEeOlb/hrEWmmgcQpTyX2bjyg 2CZck1dfXA2fYlQIKhfeqvGxoky4cjB6fPEMwR1Q=
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.29]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <4DD323E5-0634-49FC-8A6F-F1D2056F3A57@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_B34DC6B0-79F5-46C0-85C8-AD0AA4CBDF10"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Mon, 18 Feb 2019 15:10:57 -0600
In-Reply-To: <30850d4c-9fe2-8d45-4b7c-8ccb36f79ade@alum.mit.edu>
Cc: Colin Perkins <csp@csperkins.org>, mmusic WG <mmusic@ietf.org>, draft-ietf-mmusic-rfc4566bis.all@ietf.org
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu> <E6D4F528-3738-4568-80E8-A2578D0B7C7D@csperkins.org> <30850d4c-9fe2-8d45-4b7c-8ccb36f79ade@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/GHNqHbX0x_HUUu64B5P29EvMEzw>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Private Sessions
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, 18 Feb 2019 21:11:17 -0000

--Apple-Mail=_B34DC6B0-79F5-46C0-85C8-AD0AA4CBDF10
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Feb 18, 2019, at 2:49 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>=20
> On 2/13/19 6:32 PM, Colin Perkins wrote:
>>> On 2/11/19 10:45 PM, Ben Campbell wrote:
>>>> - Deleted text formerly in =C2=A74.3: The removal of the =E2=80=9Cpri=
vate sessions=E2=80=9D section in its entirety deserves some explanatory =
text.
>>>=20
>>> I don't recall why that was removed. I=E2=80=99ll try to find the =
discussion on it.
>> =
http://mailarchive.ietf.org/arch/msg/mmusic/W82Ba0vOboPUqbfWiZ0yJZqZMTQ
>=20
> That is a reply from Christer. The relevant part says:
>=20
>> My suggestion would be to remove the whole section. I can't remember =
any discussion where one would have used private vs public sessions. The =
Security Considerations should then cover encryption etc of SDP =
information.
>=20
> We managed to do the part that deletes the Private Sessions section, =
but not the update to Security Considerations. When looked at from this =
perspective, Security Considerations does seem lacking.
>=20
> Ben, will you be happy if this is addressed in Security =
Considerations? If so I'll open another discussion about that.

To be clear, I was asking for language along the lines of =E2=80=9C4566 =
had this thing; we=E2=80=99re taking it out. Here=E2=80=99s why=E2=80=9D. =
I=E2=80=99m fine if that is covered in the security considerations =
section. The =E2=80=9CSummary of Changes=E2=80=9D section could also =
work. This might be orthogonal to the security considerations language =
that Christer had in mind (which we should also add.)

>=20
> 	Thanks,
> 	Paul


--Apple-Mail=_B34DC6B0-79F5-46C0-85C8-AD0AA4CBDF10
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlxrH2EACgkQgFZKbJXz
1A0/Bg//cz//00JXkP1WRMgaHl0oYdnfWz47mS+PVHz9eEUFl3P76RDlp31SN6vS
ISdijRfZSqH3X+wI8ECJolt9+LD126l51sGZM8BYkr+lShdV0z/6EfxsANsrp8Ex
bzmPtbQJ8osRkmB3IT2E7Jbf2wcLV1cUIPY/x5hGIKi9ZFHdfAsGzCUQ48mZPpSr
Oz4nhuUxdbO29UYGDxLBlykpH1vtApjClIeAwEUY+WpOTOMp+7esuu3TEOB+F1C+
gPOpbI23LtHXhDA868pjVFfQfCMCLA4d5kRbQqhNnfY6o9mt/7+M4lcjqfA+QCUw
C+5WHXykjMx0qpbQtYME1wX96caXBvtPOk2LTq65H/qJOeFSo64OjNYkzOz/jONH
tuM5oFBrB3TsM051MFlBwEmG3dfJhYuJtq06gfX9CPUiD7lR2Gs8RnxP/Xkcff/8
WDjgW+z0XXkNn0EXDuWvmujjo17eAjVLw22iCGrggvhR+lzEQilwC6dY7SkoPNRS
7ORi6oe+5Hd78jGdK3S+WrDMQQ8jFXGxP85OB9cABlCKj2Hv7I79kY1+9E+ZJPjZ
3Ah5JMZQgqLF3dI5k8RTKsNxinKvSaEFmZ97V/H3dvmWFIDh3IJ6Rvq6/SVUGBEX
1rfxkRI1ZahqHNjRpNeYmUHQ2waAZDGBgDHWT164Ci9l48rsfvY=
=2v1f
-----END PGP SIGNATURE-----

--Apple-Mail=_B34DC6B0-79F5-46C0-85C8-AD0AA4CBDF10--


From nobody Mon Feb 18 13:13:52 2019
Return-Path: <ben@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 2959B130F4D; Mon, 18 Feb 2019 13:13:51 -0800 (PST)
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 wOHnQ5j4grnq; Mon, 18 Feb 2019 13:13:49 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9518130E8B; Mon, 18 Feb 2019 13:13:49 -0800 (PST)
Received: from [10.0.1.29] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x1ILDYBJ029839 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 18 Feb 2019 15:13:35 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1550524417; bh=8cLyi7JtiAqmZdlPL/IEe4pfyweztEb6yesFQpMJxp8=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=BeS+QIqSkuGKYGnqC+Qqoca/yc6hMwjo4LXwk0czXg8uxmnsAjW7JNnqc1hXtQ68H t5ftBOv45ob01oqy+fEEjlEQC97ab1mA9XLPxLRe19zuVYhHKkU9ssmvTqrjKVzFg5 losE/1qTYMeBSczQhHwjD3AFQuTBtTE88CClK+P8=
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.29]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <5BD16000-A00D-4B6C-9BDA-D2CEF4C53EA6@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_B73E7FDC-61D5-444F-A9AD-6AED33B103BE"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Mon, 18 Feb 2019 15:13:32 -0600
In-Reply-To: <355f8125-87f8-6372-8289-126fa126ccb9@alum.mit.edu>
Cc: draft-ietf-mmusic-rfc4566bis.all@ietf.org, mmusic WG <mmusic@ietf.org>, Colin Perkins <csp@csperkins.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu> <355f8125-87f8-6372-8289-126fa126ccb9@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/-0RNXYAe9BByk9DFmVDh-KcuGew>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
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, 18 Feb 2019 21:13:51 -0000

--Apple-Mail=_B73E7FDC-61D5-444F-A9AD-6AED33B103BE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Feb 18, 2019, at 2:23 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>=20
>=20
>=20
>> On 2/11/19 10:45 PM, Ben Campbell wrote:
>=20
>>> =C2=A72, =E2=80=9CMedia Description=E2=80=9D: While true, the text =
here is not a definition of anything but syntax. Please add a sentence =
or two to say what the media description semantically represents.
> I'm having trouble finding a suitable semantic definition of Media =
Description.
>=20
> My first thought is that it provides the information necessary to =
establish a media session. But while *Multimedia Session* is described, =
media Session isn't defined in the document.
>=20
> I looked at RFC7656 (Taxonomy) for a definition, but it doesn't have =
one either. It defines RTP Session, and Multimedia Session as one or =
more RTP Sessions. That is close, but in SDP media sessions need not be =
RTP.
>=20
> Is there any suitable existing definition???
>=20
> If not, then how about:
>=20
> "A Media Description contains the information needed for one party to =
establish an application layer network protocol connection to another =
party." ???
>=20
> OR
>=20
> "A Media Description contains the information needed for one party to =
establish a Media Session with another party."
>=20
> "A Media Session is an application layer network protocol connection =
between two parties."
>=20
> It seems important to get this right! It is essentially a broadening =
of RFC7656 beyond RTP.

I am okay with either of those. :-)

Ben.

--Apple-Mail=_B73E7FDC-61D5-444F-A9AD-6AED33B103BE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlxrH/wACgkQgFZKbJXz
1A0ShA/+PQPM9pzSUZHfFVS+1gPt7mzrkl87hcXNZXWAmEf1viHgIVM89mloIkk+
Zv9KV1pwKcVh+sBpSCV8mfmX6WlfTo2peMu+dNqiKTaVTH+vVGpfV0F+zjiicwu0
xNnch6Hk5mgz0py85LyZgJfyk/CywMEcTsoPpaTmvAyeAAih0GgYzpn+bQ9FP5Rg
Xncwm9/h5lEjRyCnQyi+7v4RPnXZE9zN9LO5ych8pNDFWYLeZoxUGcFj83752DVU
fwtZQ84CdaF7rVJXRWK7nCfYxVLOPAvclXRX9FLE2R2IP/B+Cb6fSl523X2x574A
Ok7FV3+vDEMz+4lazBa+gOSQrEsEnCSIQiWGlZEy/ilfztWYjU/qzHKVZ9NFr08O
UqTF7Hj26O5BkNTm2nq9PZWTT3F8InfkQlZ5827m4k8yTlI0nWKIHAaFPruVL6vC
+cTGx0MJ5ZtygMvBLMicD0fLNkARseEYe8L2bAhi8ecm41RA3sPr3Erzs4biZiuc
FIm/3AWFfAmBplSdgMZcG6RmL2stQquNpGxnp0dqYW4Llp3lUPh0urCxtGecqHJa
q6F8qid/eoMPAlJ0+oOsIO+tQs2yXWUxfFPVz9lP9jAJCdi4zaG5bc6vgSztMyL5
fdqbqlXcHUFDn6vIVo0L8KNYswSIHm5fLspuCK1fBV0Q1/VLfcs=
=csFt
-----END PGP SIGNATURE-----

--Apple-Mail=_B73E7FDC-61D5-444F-A9AD-6AED33B103BE--


From nobody Mon Feb 18 13:33: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 4CE8B13104B for <mmusic@ietfa.amsl.com>; Mon, 18 Feb 2019 13:33:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=CmRpFGcM; dkim=pass (1024-bit key) header.d=ericsson.com header.b=KVr/uR5h
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 sm_kUxGA5SxO for <mmusic@ietfa.amsl.com>; Mon, 18 Feb 2019 13:33:47 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 231261295D8 for <mmusic@ietf.org>; Mon, 18 Feb 2019 13:33:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/relaxed;  q=dns/txt; i=@ericsson.com; t=1550525625; x=1553117625; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4MUClJnjySMmelkJ2YhclgmcuLDthB28ITeI+kRXZwA=; b=CmRpFGcMA4d80L6LGqhPSgMVtfowqPtRbiQ4chaIQycOX2ChsYXPjz5eppV1pCsQ L4KEHm1FHei7wEw8yeOyG7JUpDpoNLWw9NlPdP+HHJqxCCpToCUjD1SCuQQBqlOV Ko5APhQuXsDoHLz6ZDfTCBeE2r4xyxxK97IDEOgP3V4=;
X-AuditID: c1b4fb25-d89ff70000005ff7-d3-5c6b24b936ee
Received: from ESESSMB504.ericsson.se (Unknown_Domain [153.88.183.122]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id D2.AF.24567.9B42B6C5; Mon, 18 Feb 2019 22:33:45 +0100 (CET)
Received: from ESESBMR504.ericsson.se (153.88.183.139) by ESESSMB504.ericsson.se (153.88.183.165) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Mon, 18 Feb 2019 22:33:45 +0100
Received: from ESESSMB503.ericsson.se (153.88.183.164) by ESESBMR504.ericsson.se (153.88.183.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Mon, 18 Feb 2019 22:33:44 +0100
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB503.ericsson.se (153.88.183.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Mon, 18 Feb 2019 22:33:44 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4MUClJnjySMmelkJ2YhclgmcuLDthB28ITeI+kRXZwA=; b=KVr/uR5h1PyOQ1LJjD45VjHEgFhiw1fKGJvwC+xlQoDoSy/NW/JyruWkg/er7giMBbeTjX013TfNaG8gxUaP+Wj1hh+JaUcBk/KCCO9bHZEJ2/hK9yJknRP1/LbcaDacdZcrrUwZYN2Py3iLkaItplYfBmN+Rf19u+0bwYPXuX4=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3228.eurprd07.prod.outlook.com (10.170.246.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.11; Mon, 18 Feb 2019 21:33:43 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0%4]) with mapi id 15.20.1622.016; Mon, 18 Feb 2019 21:33:43 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
CC: Magnus Westerlund <magnus.westerlund@ericsson.com>, mmusic WG <mmusic@ietf.org>, "draft-ietf-mmusic-rfc4566bis.all@ietf.org" <draft-ietf-mmusic-rfc4566bis.all@ietf.org>, Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
Thread-Index: AQHUx8f672wDf1L5zkyahFHOY88nA6XmDgoAgAAnKQA=
Date: Mon, 18 Feb 2019 21:33:43 +0000
Message-ID: <BC0693C8-0FA5-4B06-89C4-C1A912C00469@ericsson.com>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu> <355f8125-87f8-6372-8289-126fa126ccb9@alum.mit.edu> <5BD16000-A00D-4B6C-9BDA-D2CEF4C53EA6@nostrum.com>
In-Reply-To: <5BD16000-A00D-4B6C-9BDA-D2CEF4C53EA6@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.15.0.190117
x-originating-ip: [89.166.49.243]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9aa792a6-c199-4acd-962a-08d695e8c1bb
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600110)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:HE1PR07MB3228; 
x-ms-traffictypediagnostic: HE1PR07MB3228:
x-microsoft-exchange-diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIzMjI4OzIzOlk1bFJTcmhjYTN4bFczcTdMcmFIbkRWbEta?= =?utf-8?B?VUFPZTdnd3BCdGZnQkdzWm1qUGE0TTNVOHVSR0ZKYjROTHE0UjBnYlhObE9N?= =?utf-8?B?ZWxMWjlqelF3UmhVMmZaME53Z1NPRk9abjViVTQrR014LzdneXBXL0VQbFJz?= =?utf-8?B?bnIzUXZGTWZwOFhMR3NsZ0w2cVhsNmw0R0RqUTduUU9MN08rOEExYXVHdHhu?= =?utf-8?B?eUNObUtGTXl4TG5tK3Z3WnZxNlUwdG1Fbmg3ejF3Sm1Vbm9WZFhYVUJ5MnhT?= =?utf-8?B?bUdMNWRoZThTUU42WlZHeVNOWHdZdEorMlNOelVDUkFBcmNTMm4yL04vTnFH?= =?utf-8?B?bEV2TWdQb0p5TWdHR0pXYSs4Uk4xUzNlTGo3R1lVQksyWFFrczRWcEY5ZHlM?= =?utf-8?B?MmZHUTY0aTdySXMvbmJXVC9ra0V2eWg3NjFHazFLb3U3T0JTdlNPZURMVVBD?= =?utf-8?B?cW0xdlFEWjc4cnduZ3R1bW56eHZhSmdIUWt6clgwazJIZ3NxUWVjVzQ2SzZa?= =?utf-8?B?SkNBVU1DNkhsWlgrd0liQndUTUYyUm0wVEFFaW9pQXB6eVdDMGZiMktNU1hH?= =?utf-8?B?UW5JVXlQczJtVEdwR3JaVlZ4TjdqY3JBQmJ4WjkwQ2J5Rk50c0xDaDVRZjlq?= =?utf-8?B?c3B2STdER2hyb3pUY1IxYWwwUWpyTmwrd3M0QVdMSUQwTHdmWTloekNxWnkv?= =?utf-8?B?UmRYSitIRkJjb2FneE9vb1lCamtNNGZKRmhHbEl4aU10V29GaWhTblkxajJY?= =?utf-8?B?L0FjVG13WkF1dUF0Rmh1S081MmJZbDllVTZzKzU3bEFpVzd5TTZlM3Q5UkZC?= =?utf-8?B?ekZpcFFTMExLL2c0YnFZVTZRYU1QMFI2c3hkS2pibXBqQnZLMFFZVW5JRm5X?= =?utf-8?B?bWN1NmpwdWl1a3k3dFJDa0hHTnkxWGNaKzZGcHpGeElMd0VWKzJWSWdodzN5?= =?utf-8?B?RzFyLzhNVTJhd2VoV0NTWTJjOXYwRGV1UXlFUlRGUjA0T1RBL2xKMjhqWjlQ?= =?utf-8?B?bitNTmdhSkNydlp3UXBXZXlOWnR2WTJCbHl0Q2lUemlidWdjYWdRS1c4NjVK?= =?utf-8?B?OHEvckNEOEdZVFNlM1NoRnArS1l1SEUrM2NjeHhNdTdJK3ZxS2l4R00vZHFy?= =?utf-8?B?Z0ZabFpPWElORkIvVEtiRmNJTjBCazk5VXBiUWNIeEJPOEhYRGk5WjJYQlhj?= =?utf-8?B?U0JlellkZ1lyNWoxcm11UUdpdDRxVGZWU1doQ0JoSURHVTQ0ZlpaNlM1TVBq?= =?utf-8?B?b1UybmxvcVN6Zm8zS0Z6em9vNVZxVGM0b284V0VNMGVEVFhpR2RUcFVDMFdv?= =?utf-8?B?bGVRdFB6eFVjck9rWk5WL0NoQUYvd2xxdllmZitLak1IOWFqOHZUaCt2aThW?= =?utf-8?B?YmlSaTl3MVR5K2ZpVGluallpc3JKaU8xZCsrN3BPMERudkVSTitQVXVUYVNz?= =?utf-8?B?Z2NCWXlXaCs3WGxkTk55TXZKV2RTeDhJSHNBeHR5RVJFTUlvS1pDUXdxTjBK?= =?utf-8?B?YXNkdUlBWWxxcllXcnBwUjJPOG0xS1EyTzlUbnlzR0VYQ3NZYXY5cnV4MUc1?= =?utf-8?B?Zk5pNllzNFlrQVdzZUxWVjhjRkE5S054ZFd0MlQxVk5aME1obE44STNEMnVR?= =?utf-8?B?NTd0VjBrRXN4VitmdWd6UFk5MEdBbUJYVTBRUld0ME1aQSsvTnAwNHI4NkRX?= =?utf-8?B?bnpENUthd1dJaGlzblNlWGJFeFBVQkFKL2NiNURrQlhQQ3B1bklFWnY4N01V?= =?utf-8?B?NVJ4cmZPNUZmMDNBL0FFTXp0OEJMSVZ2WDBodS9OR1NIbHp5czd2cEkxM2FS?= =?utf-8?B?RFpWVVYvYkszM1VxMWRDaXBTcmhzai9PRVdWVTJ0dHZPNHA3V1dkenlGUjg4?= =?utf-8?Q?RLZa/3SOPsI=3D?=
x-microsoft-antispam-prvs: <HE1PR07MB3228B393025CE638D78CE94C93630@HE1PR07MB3228.eurprd07.prod.outlook.com>
x-forefront-prvs: 09525C61DB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(136003)(396003)(366004)(39860400002)(376002)(199004)(189003)(5660300002)(76176011)(83716004)(71200400001)(4326008)(2906002)(33656002)(25786009)(14444005)(478600001)(2171002)(6346003)(6506007)(53546011)(6246003)(71190400001)(93886005)(14454004)(66066001)(229853002)(102836004)(256004)(68736007)(6436002)(26005)(6486002)(86362001)(53936002)(6116002)(105586002)(6512007)(36756003)(8676002)(3846002)(305945005)(82746002)(58126008)(7736002)(54906003)(446003)(486006)(11346002)(99286004)(81156014)(81166006)(8936002)(316002)(110136005)(186003)(2616005)(44832011)(106356001)(97736004)(476003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3228; 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)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: l4rjHPkIbWk75y1lxi/450rt4MSgLBDktcmo+vxUsWgWwMYw8v90xPjkjgZmLQRCh16+/Tjhs8MdvXhIWz35DaJl9Liof3wz2Y2GX1m+mtXOPnqF6ODcydsS3WpDbXtMYj1NFWNKm1b+ZXtohUYD83ZTTy2BuivtQbWKQcu/XTbdfyMZorCjLMXXzc+qP6P0PPxgrvBLrlvsFpfh/o8YpN/EN1GHAdLnc8KuKQnrwLTGmumG5rBXkvXnY1q3j8dYzXK9BILbNq+i/S8DdfyVjtVgETmKQH/3jqt1QFC5my6ud1XJh5XMYRn1bQeLWhRVNYy+nWckM0571VwS8Lx0h1Az1zlq/UZBlYf7MQ00BiM2MxF89gujlTj+q0c/3A3MVIb1PAbUjAocu1lejta9Ld8Fo2NGIfvIgmYPR2e6nTE=
Content-Type: text/plain; charset="utf-8"
Content-ID: <163BAC3C277DBD4483DFB4FA6252E9E6@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9aa792a6-c199-4acd-962a-08d695e8c1bb
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Feb 2019 21:33:43.3050 (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-Transport-CrossTenantHeadersStamped: HE1PR07MB3228
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Se0iTYRTGe7/L9ikNX5eXg6bh0CTFWxdbdjGtbBGBEEHYQNf88jJvbMtU QsQg8BIKWemoljjzkqnUUCf+ofNSppWmQiVtrAmhloZWNryQ22fUf89znt/hvA+8DCl8Qnsx aVlqVpklyxDxnKmai50FIQZ/hTR8osJdrC0Z4YsbZl8icfFYNSG+02ClxI3tvfRxWrK++J2Q 3DWbeRKdzkZINIYZKp5KcD6SzGak5bLKsGNJzqlLPXp+TuWuvMaF5CLU6FuKnBjA++HHXB1V ipwZIR5AMK6xEZz5haB3zvDP9Ov/Gh0Bw+1rfLuhcCUJA+vNPC65TcBij3EL+4zgaXf/ZsIw PCyGso1g+0U3LAGN5Q1tZ0g8hWB04wZlD3bgS/BirJzmICnUdX7jczoKWufaHXMKB8DkYhGy awGOhvmaYT53zIygpKPDseC0GVRb+x0LCHvAyqsWwq5J7AkfZ7QE1xuDructyWl3mLVuOHh3 HAarDSMUN/eD1wuWLd4H3mnLEKfPwYPfJsdhwB8QmKxTW0EQGJue01wwLoQ2s81RH7AC7k3s 5uRO6Fo6yCHlPFhpMZGVKFzz3/s0mxiJ90Bbdxg3lsDIzEOa035QVWbhaxz9XWG4ZoZ6hOhm 5K5iVZczU/buC2WVaXKVKjsrNItVP0ObX6hPvxrQhSa+xhgRZpBouyDEWyEV0rJcVX6mEQFD itwEQ+/TpUJBsiy/gFVmJyqvZrAqI/JmKJGnYE3oKhXiFJmaVbBsDqv8mxKMk1cROt0aUZh3 dvjTtEnucmjxwqSu/or5cFNs8YHIZbksKK7RqX4+blB/q8ES2Py4IkobY/OcdRkMKLxpir0+ pG5vrbPS8vKuo31joycNtRY3lDTkURXscz8vKVuBUot9mwJPrNquRcoTvNP9dcvnTwX8LAg6 E//FrBb1Rif61E5vixBRqlRZRBCpVMn+AC48L5U+AwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/7EUlxLqT-Umyy1O_IiTwOsW6ILo>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
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, 18 Feb 2019 21:33:49 -0000

SGksDQoNClRoZSBmaXJzdCB0aGluZyB3ZSBuZWVkIHRvIG1ha2UgY2xlYXIsIGJlY2F1c2UgaXQg
aGFzIGNhdXNlZCBzb21lIGNvbmZ1c2lvbiBpbiB0aGUgcGFzdCwgaXMgd2hldGhlciBhICJtZWRp
YSBkZXNjcmlwdGlvbiIgb25seSBjb3ZlcnMgdGhlIG0tIGxpbmUsIE9SIHdoZXRoZXIgaXQgY292
ZXJzIHRoZSBtLSBsaW5lIEFORCBlYWNoIFNEUCBhdHRyaWJ1dGUgKGEtIGxpbmUpIGFzc29jaWF0
ZWQgd2l0aCBpdC4NCg0KQlVORExFIHNheXMgdGhlIGZvbGxvd2luZzoNCg0KICAgICAibT0iIHNl
Y3Rpb246IFNEUCBib2RpZXMgY29udGFpbiBvbmUgb3IgbW9yZSBtZWRpYSBkZXNjcmlwdGlvbnMs
DQogICAgIHJlZmVycmVkIHRvIGFzICJtPSIgc2VjdGlvbnMuICBFYWNoICJtPSIgc2VjdGlvbiBp
cyByZXByZXNlbnRlZCBieQ0KICAgICBhbiBTRFAgIm09IiBsaW5lLCBhbmQgemVybyBvciBtb3Jl
IFNEUCBhdHRyaWJ1dGVzIGFzc29jaWF0ZWQgd2l0aA0KICAgICB0aGUgIm09IiBsaW5lLiAgQSBs
b2NhbCBhZGRyZXNzOnBvcnQgY29tYmluYXRpb24gaXMgYXNzaWduZWQgdG8NCiAgICAgZWFjaCAi
bT0iIHNlY3Rpb24uDQoNCi4uLndoaWNoIGRvZXNuJ3QgcHJvdmlkZSBhbnkgc2VtYW50aWNzLCBi
dXQgZG9lcyBpbmRpY2F0ZSB0aGF0IHRoZSBhdHRyaWJ1dGVzIGFyZSBwYXJ0IG9mIHRoZSBtZWRp
YSBkZXNjcmlwdGlvbi4NCg0KQWZ0ZXIgYSBxdWljayBzY2FuIHRocm91Z2ggQlVORExFLCBJIGNv
dWxkbid0IGZpbmQgYW55IHNlbWFudGljcywgb3RoZXIgdGhhbiBhIG1lZGlhIGRlc2NyaXB0aW9u
IGlzIHVzZWQgdG8gImRlc2NyaWJlIG1lZGlhIi4NCg0KQnV0LCBCVU5ETEUgYWxzbyBzYXlzIHRo
YXQgQlVORExFIGlzIHVzZWQgZm9yICJ1c2luZyBhIHNpbmdsZSB0cmFuc3BvcnQgZm9yIHNlbmRp
bmcgYW5kIHJlY2VpdmluZyBtZWRpYSBhc3NvY2lhdGVkIHdpdGggU0RQIG11bHRpcGxlIG1lZGlh
IGRlc2NyaXB0aW9ucyIuDQoNClNvLCB3aGlsZSBJIGRvbid0IGhhdmUgZXhhY3Qgd29yZGluZyBh
dCB0aGUgbW9tZW50LCBteSBzdWdnZXN0aW9uIHdvdWxkIGJlIHRvIHNheSB0aGF0IGFuIFNEUCBt
ZWRpYSBkZXNjcmlwdGlvbiBkZXNjcmliZXMgYSBUUkFOU1BPUlQgZm9yIGEgbWVkaWEgZmxvdywg
b3Igc29tZXRoaW5nIGxpa2UgdGhhdC4uLiANCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQoN
Cu+7v09uIDE4LzAyLzIwMTksIDIzLjE0LCAibW11c2ljIG9uIGJlaGFsZiBvZiBCZW4gQ2FtcGJl
bGwiIDxtbXVzaWMtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgYmVuQG5vc3RydW0uY29t
PiB3cm90ZToNCg0KICAgIA0KICAgIA0KICAgID4gT24gRmViIDE4LCAyMDE5LCBhdCAyOjIzIFBN
LCBQYXVsIEt5eml2YXQgPHBreXppdmF0QGFsdW0ubWl0LmVkdT4gd3JvdGU6DQogICAgPiANCiAg
ICA+IA0KICAgID4gDQogICAgPj4gT24gMi8xMS8xOSAxMDo0NSBQTSwgQmVuIENhbXBiZWxsIHdy
b3RlOg0KICAgID4gDQogICAgPj4+IMKnMiwg4oCcTWVkaWEgRGVzY3JpcHRpb27igJ06IFdoaWxl
IHRydWUsIHRoZSB0ZXh0IGhlcmUgaXMgbm90IGEgZGVmaW5pdGlvbiBvZiBhbnl0aGluZyBidXQg
c3ludGF4LiBQbGVhc2UgYWRkIGEgc2VudGVuY2Ugb3IgdHdvIHRvIHNheSB3aGF0IHRoZSBtZWRp
YSBkZXNjcmlwdGlvbiBzZW1hbnRpY2FsbHkgcmVwcmVzZW50cy4NCiAgICA+IEknbSBoYXZpbmcg
dHJvdWJsZSBmaW5kaW5nIGEgc3VpdGFibGUgc2VtYW50aWMgZGVmaW5pdGlvbiBvZiBNZWRpYSBE
ZXNjcmlwdGlvbi4NCiAgICA+IA0KICAgID4gTXkgZmlyc3QgdGhvdWdodCBpcyB0aGF0IGl0IHBy
b3ZpZGVzIHRoZSBpbmZvcm1hdGlvbiBuZWNlc3NhcnkgdG8gZXN0YWJsaXNoIGEgbWVkaWEgc2Vz
c2lvbi4gQnV0IHdoaWxlICpNdWx0aW1lZGlhIFNlc3Npb24qIGlzIGRlc2NyaWJlZCwgbWVkaWEg
U2Vzc2lvbiBpc24ndCBkZWZpbmVkIGluIHRoZSBkb2N1bWVudC4NCiAgICA+IA0KICAgID4gSSBs
b29rZWQgYXQgUkZDNzY1NiAoVGF4b25vbXkpIGZvciBhIGRlZmluaXRpb24sIGJ1dCBpdCBkb2Vz
bid0IGhhdmUgb25lIGVpdGhlci4gSXQgZGVmaW5lcyBSVFAgU2Vzc2lvbiwgYW5kIE11bHRpbWVk
aWEgU2Vzc2lvbiBhcyBvbmUgb3IgbW9yZSBSVFAgU2Vzc2lvbnMuIFRoYXQgaXMgY2xvc2UsIGJ1
dCBpbiBTRFAgbWVkaWEgc2Vzc2lvbnMgbmVlZCBub3QgYmUgUlRQLg0KICAgID4gDQogICAgPiBJ
cyB0aGVyZSBhbnkgc3VpdGFibGUgZXhpc3RpbmcgZGVmaW5pdGlvbj8/Pw0KICAgID4gDQogICAg
PiBJZiBub3QsIHRoZW4gaG93IGFib3V0Og0KICAgID4gDQogICAgPiAiQSBNZWRpYSBEZXNjcmlw
dGlvbiBjb250YWlucyB0aGUgaW5mb3JtYXRpb24gbmVlZGVkIGZvciBvbmUgcGFydHkgdG8gZXN0
YWJsaXNoIGFuIGFwcGxpY2F0aW9uIGxheWVyIG5ldHdvcmsgcHJvdG9jb2wgY29ubmVjdGlvbiB0
byBhbm90aGVyIHBhcnR5LiIgPz8/DQogICAgPiANCiAgICA+IE9SDQogICAgPiANCiAgICA+ICJB
IE1lZGlhIERlc2NyaXB0aW9uIGNvbnRhaW5zIHRoZSBpbmZvcm1hdGlvbiBuZWVkZWQgZm9yIG9u
ZSBwYXJ0eSB0byBlc3RhYmxpc2ggYSBNZWRpYSBTZXNzaW9uIHdpdGggYW5vdGhlciBwYXJ0eS4i
DQogICAgPiANCiAgICA+ICJBIE1lZGlhIFNlc3Npb24gaXMgYW4gYXBwbGljYXRpb24gbGF5ZXIg
bmV0d29yayBwcm90b2NvbCBjb25uZWN0aW9uIGJldHdlZW4gdHdvIHBhcnRpZXMuIg0KICAgID4g
DQogICAgPiBJdCBzZWVtcyBpbXBvcnRhbnQgdG8gZ2V0IHRoaXMgcmlnaHQhIEl0IGlzIGVzc2Vu
dGlhbGx5IGEgYnJvYWRlbmluZyBvZiBSRkM3NjU2IGJleW9uZCBSVFAuDQogICAgDQogICAgSSBh
bSBva2F5IHdpdGggZWl0aGVyIG9mIHRob3NlLiA6LSkNCiAgICANCiAgICBCZW4uDQogICAgDQoN
Cg==


From nobody Mon Feb 18 13:58:35 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 BB46F131051 for <mmusic@ietfa.amsl.com>; Mon, 18 Feb 2019 13:58:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=G2cH1v22; dkim=pass (1024-bit key) header.d=ericsson.com header.b=miWI2G1z
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 NbISTy5-dPYW for <mmusic@ietfa.amsl.com>; Mon, 18 Feb 2019 13:58:31 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 C3B04126C7E for <mmusic@ietf.org>; Mon, 18 Feb 2019 13:58:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/relaxed;  q=dns/txt; i=@ericsson.com; t=1550527108; x=1553119108; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Kjp0OZvUDYrlBYIaA7w79eCucvAQK6UpFWap7jOz6us=; b=G2cH1v22ITeLdaRsX8j5hkSURNwQSTnnv7vIkm9uE2+QOXuCgJAF8BuYl5wmsFeO rRng+swVAIiDoVlJFFOZTxObtONVMnScJLjLjXtFwqjIMOx8o2HsFUPY1YOJZ/3h 7z3f9V2zR03NIoQgrdP0CdK89p+7gJJz1HzTiQE4K2U=;
X-AuditID: c1b4fb3a-167ff7000000672c-f3-5c6b2a843abb
Received: from ESESBMB503.ericsson.se (Unknown_Domain [153.88.183.116]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id B9.4C.26412.48A2B6C5; Mon, 18 Feb 2019 22:58:28 +0100 (CET)
Received: from ESESBMR501.ericsson.se (153.88.183.129) by ESESBMB503.ericsson.se (153.88.183.170) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Mon, 18 Feb 2019 22:58:28 +0100
Received: from ESESSMB505.ericsson.se (153.88.183.166) by ESESBMR501.ericsson.se (153.88.183.129) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Mon, 18 Feb 2019 22:58:28 +0100
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB505.ericsson.se (153.88.183.166) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Mon, 18 Feb 2019 22:58:28 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Kjp0OZvUDYrlBYIaA7w79eCucvAQK6UpFWap7jOz6us=; b=miWI2G1zPtqpk7pfuRElUzeOkA44vf8Z78Q4zz/I/FMn8i7UxFkO6CtfpkfR9U/zOq/1RAuWGEWigSDLb46l0gPIxWlqOfOiV61PAnBkpPfVmEnP5BWlpTaZ5bfQKNiTJH8VnMAIn3p32AxWyo1N4DYMBnK/SwJKNzCfpjx0mrI=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3418.eurprd07.prod.outlook.com (10.170.247.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1622.13; Mon, 18 Feb 2019 21:58:26 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0%4]) with mapi id 15.20.1622.016; Mon, 18 Feb 2019 21:58:26 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
CC: Magnus Westerlund <magnus.westerlund@ericsson.com>, mmusic WG <mmusic@ietf.org>, "draft-ietf-mmusic-rfc4566bis.all@ietf.org" <draft-ietf-mmusic-rfc4566bis.all@ietf.org>, Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
Thread-Index: AQHUx8f672wDf1L5zkyahFHOY88nA6XmDgoAgAAnKQCAAAbogA==
Date: Mon, 18 Feb 2019 21:58:26 +0000
Message-ID: <BEF2B13D-2F23-49BF-B566-006046B1C229@ericsson.com>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu> <355f8125-87f8-6372-8289-126fa126ccb9@alum.mit.edu> <5BD16000-A00D-4B6C-9BDA-D2CEF4C53EA6@nostrum.com> <BC0693C8-0FA5-4B06-89C4-C1A912C00469@ericsson.com>
In-Reply-To: <BC0693C8-0FA5-4B06-89C4-C1A912C00469@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.15.0.190117
x-originating-ip: [89.166.49.243]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 995fd4d5-16e7-4e34-7fda-08d695ec35de
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:HE1PR07MB3418; 
x-ms-traffictypediagnostic: HE1PR07MB3418:
x-ms-exchange-purlcount: 1
x-microsoft-exchange-diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIzNDE4OzIzOnlXS0xvZEJrN2g4bUxwckxlbDdubEJqZGVO?= =?utf-8?B?ajJqRDNVNTcxbUZqcDUwb0RjaFZGRGZuSVQxckZwSTIvVzJKb09mMHRMYVVu?= =?utf-8?B?S3cvcCsrNGVKb012b1Bhd1ZpaGl4N3I5NnpwejhpdnZYTUsxbFYrKzFNbXRt?= =?utf-8?B?OFlkMUp6R3F3VEo3SWJqU1JsaktmQVMzOExPVDZDeUtBa2N0eWg1OThaV2o2?= =?utf-8?B?bGptazhGZ2FIMXNEekVLbW05U2J1MDhBd0hqSkcrSzZBajVkUEpLcmVaQ3Vm?= =?utf-8?B?UGtEUUI1K0lZZ3Y5R0daMGZPQlNOZGcwUzFMd2lJTTVRTjJ6MzUxQnI5TitE?= =?utf-8?B?TWJHemNhYUQyRDk5b2U0YTY1UUZtQnVTWkJROTR4TkRPTE5PY2QveHQ0UXpk?= =?utf-8?B?ZURUek8zRnNWVHA3bXpYZzJ0U29WNXpIOWF0WlhlVW9DTlR3V3p2aWNIY3ZM?= =?utf-8?B?K0dMTmxCcE4rK0lnS2Q5SkpZUkx3WEhya2hNUWZ5ZVZ5YUhBcFRjTll0RnBo?= =?utf-8?B?bUxpWnB3RCtMQzZjYU9CUzhMVlFlaWlTdlhwdWovVm9XcmxrYlJ2WnppWDhJ?= =?utf-8?B?d1VVamh2eHF1S1hIZ0xodjdPQ1Q5OFRld0lRT2p5Wk5PZDdyYkpudm5TMHd5?= =?utf-8?B?K3dYd2JlWFFhZ2EzTUZSOURIUE1NMytqSGlLRkZYMGNHbDNySGlVcE9lZFN0?= =?utf-8?B?eDlPT2FYbzNFL2pkMkV6SGw1dG1uSEZmNG5BdTI5RWdRb2NrNC9CQnFKVEly?= =?utf-8?B?YjZkUHdLRnJ4MVdwaWROYW1SSEIvYWxiZmFJN0t0a1plMVZlZ3F6VVdybHg2?= =?utf-8?B?dkxmYnAwNlR5Yk9RcHFFREJsMlpZbjBpSXNiSS9tY0dpOGZxZmpwSkNxTDVF?= =?utf-8?B?VUk4MFJHbjY5WG9hdE92cWFjMFVVcitIb24ycXg1d1dDKzg2STlHY0VMdGlU?= =?utf-8?B?elZ2c3p6dG1YN3FsRmVISWVwNnhtaS9sTmk2Y3M0MFhiK3FrVkprMzhrbnZi?= =?utf-8?B?anhrWlFHRitxSXdvazJVczFEakVtSkN4TEEvakptTTZ0Sytld3diOE90M1pt?= =?utf-8?B?NFFiVXVjZU00YmhkOWV2N3QxZkFOeHNCV0RIeTh6M3ZqWi9yL3N5S3k2TjVz?= =?utf-8?B?dUFIY1RIYlRJYnFEUEF5alUyckxaek1ZemdsM0xEaVEyT1RnQ3hocU9raktv?= =?utf-8?B?SDlZTXY5Tk9LVTVKcmxBMTIzVmpuNy9vQ3A4eS9NOWhDSWRUUXBhQkxzbzZU?= =?utf-8?B?eWpUR2NPclV6ZzBFcVZmcldiV2JYcHJKRit5dExmY0h5aWU0RkQxaFR5YXJ3?= =?utf-8?B?cHUwZVVKZmt4Q3BMb1M2d2ljNUxqRnN2ekhSVkJQV0d2NVgxOWtGekg3Qkh0?= =?utf-8?B?U1Zxbm1RVWhWRlNCRENzYTlFbFk3eFJpbTdhaVZWZDZxdm8wUitlMTFzWG54?= =?utf-8?B?eE95NUFVRkdWZjJGUWZGUk5BdTdTcml2S3o0dmV2UElYNHR2RDByVUk5ejUx?= =?utf-8?B?aXdIeVJwOUp1K01Mb2hFRGlocGVDR0RrRXQvSFhDcTQvT3diRm16SUpnQmNv?= =?utf-8?B?dFBUUng2K1VNeDNscENQdytqbUEyMEl3bW4xdkNSMklJUTlKdW5JbENNZkZq?= =?utf-8?B?WFlMMFI5NzNWL1Eza1RMRVNiaytwNGtielpiRTc3TGp0cEp0c2tNYWtIeFZF?= =?utf-8?B?ZVJzaTdvZmVYQXczL2lCQUh4TkJPc3ZsNDB1bFlOT1NYYUxLZDcwN1ZZVGM4?= =?utf-8?B?cmRZQk04Wm5ORGk1aFk3NFMwcnNZalJTQjB1L3diL04zRm9xRVBHYlJUb0dG?= =?utf-8?B?bjZ0TnIyVDkyZkFYazVyRmh5UTJRNDJkS05OOHZkUVFaOEVoMENVWE5hUVY4?= =?utf-8?B?RUNSN2FZWXpmb1BpTENld1lnemp5VjkzRkdiM0xoWXgyYlYzVXBYSEJNVzJS?= =?utf-8?B?SnRsaVNnT1ZRPT0=?=
x-microsoft-antispam-prvs: <HE1PR07MB3418045129238C983784962293630@HE1PR07MB3418.eurprd07.prod.outlook.com>
x-forefront-prvs: 09525C61DB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(376002)(366004)(136003)(39860400002)(346002)(189003)(199004)(33656002)(5660300002)(97736004)(3846002)(81166006)(25786009)(7736002)(66066001)(305945005)(4326008)(229853002)(83716004)(53936002)(2171002)(81156014)(6116002)(106356001)(82746002)(14454004)(71200400001)(105586002)(486006)(2906002)(8936002)(6306002)(44832011)(6512007)(6246003)(93886005)(71190400001)(14444005)(2616005)(99286004)(316002)(446003)(6436002)(8676002)(76176011)(6506007)(478600001)(476003)(110136005)(6486002)(11346002)(966005)(54906003)(86362001)(6346003)(256004)(36756003)(102836004)(58126008)(186003)(26005)(68736007)(53546011); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3418; 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)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: PeTWDP6ihk0ytqbYHtpcOAGyOvJyQm5BruUx7Tq8Gy1TmSlhKtjZ830P5+dukFNyKjAn/dqeytKekQCV+OXg7l7Vvo1Zya4Opty6Qq5DG8FADmWLnOrEChqROjpaGW0YuAgQGo7SmbaP7f5MY+MtvCnY3KYS2xWES09urgczeWN6V2WOSglJIunF+j0M785FdFXcybOWivIqP1Z5WzciAPHIXvNRS9XlJLWzF0pPw44ZG4apLr389V6dHjjxfhH3eb8u5K7M4kSowJLZbPA5QYQkm7PMEXfWUgQMH3ME752MeZTGQdA/r13ZIZ8n+2xfZY9iao/AwWq1xF+jhP3MTuU+QUgIDA/46A8cFoAzzuhnOR7w0qSjmMOamJ70fCLKim3517UH7l5oqliNio6+VYXWGJ0RBv8X8go6mTyuCwo=
Content-Type: text/plain; charset="utf-8"
Content-ID: <FCC6983512074B42BE2C16F6DE24E1F8@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 995fd4d5-16e7-4e34-7fda-08d695ec35de
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Feb 2019 21:58:26.6517 (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-Transport-CrossTenantHeadersStamped: HE1PR07MB3418
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SfyxVYRjH954f12Hd7XX9enarP9xNRSGyddYM+aOdtZoyW8pt3HKGLvfa OVjaWqJNXJOKyrVhc/MjtmKGLm0Rkt/aWBjCLamFmpiR5d6j1n+f5/l+3+d5v+9ehlRU00om QZfCCzpNokrmQBVHNqd43/HSqo/+yD7GluX02bFViz2IzRx+QrBFVfMUW/3iNR1Cc7+XVwju 0cyMjDOZNgjO+NJCnaMuOQTG8okJabzgGxTjEN/ya5VKbjtwfbquEGWgNo9cZM8ADoCW/EKZ lRW4E8GnEmUuctjhNQRTa/12/wrLUL1MKkwEVKxaKGtB4QISevIMtKQ8JKB/sJqQhs0hmNvk chHDyDALhu3D1rYz5sA4O2jzk3gUQf92FmUVnHAUvB3OoyWTGiqav9tJHArmgW82prAHWAby bfPlOBimxgYJaXERATWdY6RVsMchsNW4bBuKsCus99bZDpDYDSYsZYSUGoOpbYiU2AUW57dt i12wL2xW9VFS3x0GlmZ3/fvhfZkBSXwWFh+U2x4G8DiCrIw80poSsBfMvqIljxJ6Rrp2udQJ Htc4SqyF1q4RWrLvg5afxwuQn/G/2xl3FBJ7wnOzr9TmYHKyCEnsDoWGWTujLb0jvCu2UOWI foZcRF4Uk+L8/X14IeGqKOp1Pjo+pQHt/J/2xs0TLah94WQHwgxS7ZFPg1atoDVpYnpSBwKG VDnLuz9cUyvksZr0G7ygjxZSE3mxA+1lKJWbfEvhqFbgOE0Kr+X5ZF74qxKMvTIDnQ+O7PMM PMJyTV/1h1IrL1YtD97Tj785rSw7aHKJYwtWLpd0eWtzEm8nxX/0fRq+ENYQoI4QMntda83e bLb7enxPR3RxqHrjc+2VqJiGiJAzlat88mi4mcOluNusvz9WLq8sD/Jhi8cN6QEXwk7dujlR vzSkQ7LW1Ka+u8IXFSXGa/y8SEHU/AHsxqSQOwMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/d_DQb19hr31UZapbof5tpv0MW78>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
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, 18 Feb 2019 21:58:34 -0000

Li4uLm9yLCAidHJhbnNwb3J0IGFuZCBwcm9wZXJ0aWVzIChjb2RlY3MgZXRjKSBvZiBhIG1lZGlh
IGZsb3ciLCBiZWNhdXNlIGl0IGlzIG1vcmUgdGhhbiB0aGUgSVAgYWRkcmVzcyBhbmQgcG9ydC4N
Cg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0K77u/T24gMTgvMDIvMjAxOSwgMjMuMzQsICJtbXVz
aWMgb24gYmVoYWxmIG9mIENocmlzdGVyIEhvbG1iZXJnIiA8bW11c2ljLWJvdW5jZXNAaWV0Zi5v
cmcgb24gYmVoYWxmIG9mIGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4gd3JvdGU6DQoN
CiAgICBIaSwNCiAgICANCiAgICBUaGUgZmlyc3QgdGhpbmcgd2UgbmVlZCB0byBtYWtlIGNsZWFy
LCBiZWNhdXNlIGl0IGhhcyBjYXVzZWQgc29tZSBjb25mdXNpb24gaW4gdGhlIHBhc3QsIGlzIHdo
ZXRoZXIgYSAibWVkaWEgZGVzY3JpcHRpb24iIG9ubHkgY292ZXJzIHRoZSBtLSBsaW5lLCBPUiB3
aGV0aGVyIGl0IGNvdmVycyB0aGUgbS0gbGluZSBBTkQgZWFjaCBTRFAgYXR0cmlidXRlIChhLSBs
aW5lKSBhc3NvY2lhdGVkIHdpdGggaXQuDQogICAgDQogICAgQlVORExFIHNheXMgdGhlIGZvbGxv
d2luZzoNCiAgICANCiAgICAgICAgICJtPSIgc2VjdGlvbjogU0RQIGJvZGllcyBjb250YWluIG9u
ZSBvciBtb3JlIG1lZGlhIGRlc2NyaXB0aW9ucywNCiAgICAgICAgIHJlZmVycmVkIHRvIGFzICJt
PSIgc2VjdGlvbnMuICBFYWNoICJtPSIgc2VjdGlvbiBpcyByZXByZXNlbnRlZCBieQ0KICAgICAg
ICAgYW4gU0RQICJtPSIgbGluZSwgYW5kIHplcm8gb3IgbW9yZSBTRFAgYXR0cmlidXRlcyBhc3Nv
Y2lhdGVkIHdpdGgNCiAgICAgICAgIHRoZSAibT0iIGxpbmUuICBBIGxvY2FsIGFkZHJlc3M6cG9y
dCBjb21iaW5hdGlvbiBpcyBhc3NpZ25lZCB0bw0KICAgICAgICAgZWFjaCAibT0iIHNlY3Rpb24u
DQogICAgDQogICAgLi4ud2hpY2ggZG9lc24ndCBwcm92aWRlIGFueSBzZW1hbnRpY3MsIGJ1dCBk
b2VzIGluZGljYXRlIHRoYXQgdGhlIGF0dHJpYnV0ZXMgYXJlIHBhcnQgb2YgdGhlIG1lZGlhIGRl
c2NyaXB0aW9uLg0KICAgIA0KICAgIEFmdGVyIGEgcXVpY2sgc2NhbiB0aHJvdWdoIEJVTkRMRSwg
SSBjb3VsZG4ndCBmaW5kIGFueSBzZW1hbnRpY3MsIG90aGVyIHRoYW4gYSBtZWRpYSBkZXNjcmlw
dGlvbiBpcyB1c2VkIHRvICJkZXNjcmliZSBtZWRpYSIuDQogICAgDQogICAgQnV0LCBCVU5ETEUg
YWxzbyBzYXlzIHRoYXQgQlVORExFIGlzIHVzZWQgZm9yICJ1c2luZyBhIHNpbmdsZSB0cmFuc3Bv
cnQgZm9yIHNlbmRpbmcgYW5kIHJlY2VpdmluZyBtZWRpYSBhc3NvY2lhdGVkIHdpdGggU0RQIG11
bHRpcGxlIG1lZGlhIGRlc2NyaXB0aW9ucyIuDQogICAgDQogICAgU28sIHdoaWxlIEkgZG9uJ3Qg
aGF2ZSBleGFjdCB3b3JkaW5nIGF0IHRoZSBtb21lbnQsIG15IHN1Z2dlc3Rpb24gd291bGQgYmUg
dG8gc2F5IHRoYXQgYW4gU0RQIG1lZGlhIGRlc2NyaXB0aW9uIGRlc2NyaWJlcyBhIFRSQU5TUE9S
VCBmb3IgYSBtZWRpYSBmbG93LCBvciBzb21ldGhpbmcgbGlrZSB0aGF0Li4uIA0KICAgIA0KICAg
IFJlZ2FyZHMsDQogICAgDQogICAgQ2hyaXN0ZXINCiAgICANCiAgICANCiAgICANCiAgICBPbiAx
OC8wMi8yMDE5LCAyMy4xNCwgIm1tdXNpYyBvbiBiZWhhbGYgb2YgQmVuIENhbXBiZWxsIiA8bW11
c2ljLWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIGJlbkBub3N0cnVtLmNvbT4gd3JvdGU6
DQogICAgDQogICAgICAgIA0KICAgICAgICANCiAgICAgICAgPiBPbiBGZWIgMTgsIDIwMTksIGF0
IDI6MjMgUE0sIFBhdWwgS3l6aXZhdCA8cGt5eml2YXRAYWx1bS5taXQuZWR1PiB3cm90ZToNCiAg
ICAgICAgPiANCiAgICAgICAgPiANCiAgICAgICAgPiANCiAgICAgICAgPj4gT24gMi8xMS8xOSAx
MDo0NSBQTSwgQmVuIENhbXBiZWxsIHdyb3RlOg0KICAgICAgICA+IA0KICAgICAgICA+Pj4gwqcy
LCDigJxNZWRpYSBEZXNjcmlwdGlvbuKAnTogV2hpbGUgdHJ1ZSwgdGhlIHRleHQgaGVyZSBpcyBu
b3QgYSBkZWZpbml0aW9uIG9mIGFueXRoaW5nIGJ1dCBzeW50YXguIFBsZWFzZSBhZGQgYSBzZW50
ZW5jZSBvciB0d28gdG8gc2F5IHdoYXQgdGhlIG1lZGlhIGRlc2NyaXB0aW9uIHNlbWFudGljYWxs
eSByZXByZXNlbnRzLg0KICAgICAgICA+IEknbSBoYXZpbmcgdHJvdWJsZSBmaW5kaW5nIGEgc3Vp
dGFibGUgc2VtYW50aWMgZGVmaW5pdGlvbiBvZiBNZWRpYSBEZXNjcmlwdGlvbi4NCiAgICAgICAg
PiANCiAgICAgICAgPiBNeSBmaXJzdCB0aG91Z2h0IGlzIHRoYXQgaXQgcHJvdmlkZXMgdGhlIGlu
Zm9ybWF0aW9uIG5lY2Vzc2FyeSB0byBlc3RhYmxpc2ggYSBtZWRpYSBzZXNzaW9uLiBCdXQgd2hp
bGUgKk11bHRpbWVkaWEgU2Vzc2lvbiogaXMgZGVzY3JpYmVkLCBtZWRpYSBTZXNzaW9uIGlzbid0
IGRlZmluZWQgaW4gdGhlIGRvY3VtZW50Lg0KICAgICAgICA+IA0KICAgICAgICA+IEkgbG9va2Vk
IGF0IFJGQzc2NTYgKFRheG9ub215KSBmb3IgYSBkZWZpbml0aW9uLCBidXQgaXQgZG9lc24ndCBo
YXZlIG9uZSBlaXRoZXIuIEl0IGRlZmluZXMgUlRQIFNlc3Npb24sIGFuZCBNdWx0aW1lZGlhIFNl
c3Npb24gYXMgb25lIG9yIG1vcmUgUlRQIFNlc3Npb25zLiBUaGF0IGlzIGNsb3NlLCBidXQgaW4g
U0RQIG1lZGlhIHNlc3Npb25zIG5lZWQgbm90IGJlIFJUUC4NCiAgICAgICAgPiANCiAgICAgICAg
PiBJcyB0aGVyZSBhbnkgc3VpdGFibGUgZXhpc3RpbmcgZGVmaW5pdGlvbj8/Pw0KICAgICAgICA+
IA0KICAgICAgICA+IElmIG5vdCwgdGhlbiBob3cgYWJvdXQ6DQogICAgICAgID4gDQogICAgICAg
ID4gIkEgTWVkaWEgRGVzY3JpcHRpb24gY29udGFpbnMgdGhlIGluZm9ybWF0aW9uIG5lZWRlZCBm
b3Igb25lIHBhcnR5IHRvIGVzdGFibGlzaCBhbiBhcHBsaWNhdGlvbiBsYXllciBuZXR3b3JrIHBy
b3RvY29sIGNvbm5lY3Rpb24gdG8gYW5vdGhlciBwYXJ0eS4iID8/Pw0KICAgICAgICA+IA0KICAg
ICAgICA+IE9SDQogICAgICAgID4gDQogICAgICAgID4gIkEgTWVkaWEgRGVzY3JpcHRpb24gY29u
dGFpbnMgdGhlIGluZm9ybWF0aW9uIG5lZWRlZCBmb3Igb25lIHBhcnR5IHRvIGVzdGFibGlzaCBh
IE1lZGlhIFNlc3Npb24gd2l0aCBhbm90aGVyIHBhcnR5LiINCiAgICAgICAgPiANCiAgICAgICAg
PiAiQSBNZWRpYSBTZXNzaW9uIGlzIGFuIGFwcGxpY2F0aW9uIGxheWVyIG5ldHdvcmsgcHJvdG9j
b2wgY29ubmVjdGlvbiBiZXR3ZWVuIHR3byBwYXJ0aWVzLiINCiAgICAgICAgPiANCiAgICAgICAg
PiBJdCBzZWVtcyBpbXBvcnRhbnQgdG8gZ2V0IHRoaXMgcmlnaHQhIEl0IGlzIGVzc2VudGlhbGx5
IGEgYnJvYWRlbmluZyBvZiBSRkM3NjU2IGJleW9uZCBSVFAuDQogICAgICAgIA0KICAgICAgICBJ
IGFtIG9rYXkgd2l0aCBlaXRoZXIgb2YgdGhvc2UuIDotKQ0KICAgICAgICANCiAgICAgICAgQmVu
Lg0KICAgICAgICANCiAgICANCiAgICBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KICAgIG1tdXNpYyBtYWlsaW5nIGxpc3QNCiAgICBtbXVzaWNAaWV0Zi5v
cmcNCiAgICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYw0KICAg
IA0KDQo=


From nobody Mon Feb 18 22:52:24 2019
Return-Path: <roni.even@huawei.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 95B66130E82; Mon, 18 Feb 2019 22:52:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1s0jFAZ78hhd; Mon, 18 Feb 2019 22:52:20 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7591130E7E; Mon, 18 Feb 2019 22:52:20 -0800 (PST)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 4B6D3C3C212A47C1E186; Tue, 19 Feb 2019 06:52:18 +0000 (GMT)
Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 19 Feb 2019 06:52:17 +0000
Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Tue, 19 Feb 2019 06:52:17 +0000
Received: from DGGEMM423-HUB.china.huawei.com (10.1.198.40) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Tue, 19 Feb 2019 06:52:17 +0000
Received: from DGGEMM526-MBX.china.huawei.com ([169.254.8.222]) by dggemm423-hub.china.huawei.com ([10.1.198.40]) with mapi id 14.03.0415.000; Tue, 19 Feb 2019 14:52:11 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Ben Campbell <ben@nostrum.com>, "draft-ietf-mmusic-rfc4566bis.all@ietf.org" <draft-ietf-mmusic-rfc4566bis.all@ietf.org>
CC: Magnus Westerlund <magnus.westerlund@ericsson.com>, mmusic WG <mmusic@ietf.org>, 'Colin Perkins' <csp@csperkins.org>
Thread-Topic: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
Thread-Index: AQHUx8fxbs918E2F1karkE7QXY8wS6XmrKuQ
Date: Tue, 19 Feb 2019 06:52:10 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD18CB5561@dggemm526-mbx.china.huawei.com>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu> <355f8125-87f8-6372-8289-126fa126ccb9@alum.mit.edu>
In-Reply-To: <355f8125-87f8-6372-8289-126fa126ccb9@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.80]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/339woA1OBvXe3hn6SLCFZ_HZTdY>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
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, 19 Feb 2019 06:52:23 -0000

SGkgUGF1bCwNCkkgYW0gbm90IHN1cmUgd2h5IHdlIG5lZWQgdG8gIGNoYW5nZSB0aGUgZGVmaW5p
dGlvbi4NCg0KQSBtZWRpYSBkZXNjcmlwdGlvbiBkZXNjcmliZXMgdGhlIG1lZGlhIGFuZCBpdCBz
dGFydCB3aXRoIGEgbT0gbGluZSAgLi4uIChhbmQgc28gb24pDQoNCklmIHdhbnQgdG8gZXhwYW5k
IG1heWJlIHNheSB0aGF0IGl0IG11c3Qgc3RhcnQgd2l0aCBhbiBtPSBsaW5lIGFuZCB3aWxsIGlu
Y2x1ZGUgdGhlIHNkcCB0eXBlcyBhcyBsaXN0ZWQgaW4gc2VjdGlvbiA1DQoNCg0KTWVkaWEgZGVz
Y3JpcHRpb24sIGlmIHByZXNlbnQNCiAgICAgICAgIG09ICAobWVkaWEgbmFtZSBhbmQgdHJhbnNw
b3J0IGFkZHJlc3MpDQogICAgICAgICBpPSogKG1lZGlhIHRpdGxlKQ0KICAgICAgICAgYz0qIChj
b25uZWN0aW9uIGluZm9ybWF0aW9uIC0tIG9wdGlvbmFsIGlmIGluY2x1ZGVkIGF0DQogICAgICAg
ICAgICAgIHNlc3Npb24gbGV2ZWwpDQogICAgICAgICBiPSogKHplcm8gb3IgbW9yZSBiYW5kd2lk
dGggaW5mb3JtYXRpb24gbGluZXMpDQogICAgICAgICBrPSogKGVuY3J5cHRpb24ga2V5KQ0KICAg
ICAgICAgYT0qICh6ZXJvIG9yIG1vcmUgbWVkaWEgYXR0cmlidXRlIGxpbmVzKQ0KDQoNCk1lZGlh
IGRlc2NyaXB0aW9uIGlzIG5vdCBhYm91dCBSVFAgc2luY2UgdGhlIHByb3RvIGF0dHJpYnV0ZSBp
biB0aGUgbS1saW5lIGNhbiBkZWZpbmUgb3RoZXJzIHNlZSBodHRwczovL3d3dy5pYW5hLm9yZy9h
c3NpZ25tZW50cy9zZHAtcGFyYW1ldGVycy9zZHAtcGFyYW1ldGVycy54aHRtbCNzZHAtcGFyYW1l
dGVycy0yICANCg0KZm9yIGV4YW1wbGUgaW4gZHJhZnQgZGF0YS1jaGFubmVsLXNkcG5lZyB3ZSBo
YXZlOiAgbT1hcHBsaWNhdGlvbiAxMDAwMSBVRFAvRFRMUy9TQ1RQIHdlYnJ0Yy1kYXRhY2hhbm5l
bCB3aGljaCBpcyBub3QgUlRQLg0KDQoNClJvbmkgRXZlbg0KDQotLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KRnJvbTogbW11c2ljIFttYWlsdG86bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZiBPZiBQYXVsIEt5eml2YXQNClNlbnQ6IE1vbmRheSwgRmVicnVhcnkgMTgsIDIwMTkg
MTA6MjQgUE0NClRvOiBCZW4gQ2FtcGJlbGw7IGRyYWZ0LWlldGYtbW11c2ljLXJmYzQ1NjZiaXMu
YWxsQGlldGYub3JnDQpDYzogTWFnbnVzIFdlc3Rlcmx1bmQ7IG1tdXNpYyBXRzsgJ0NvbGluIFBl
cmtpbnMnDQpTdWJqZWN0OiBSZTogW01NVVNJQ10gQUQgRXZhbHVhdGlvbiBvZiBkcmFmdC1pZXRm
LW1tdXNpYy1yZmM0NTY2YmlzLTMyOiBNZWRpYSBEZXNjcmlwdGlvbg0KDQoNCg0KPiBPbiAyLzEx
LzE5IDEwOjQ1IFBNLCBCZW4gQ2FtcGJlbGwgd3JvdGU6DQoNCj4+IMKnMiwg4oCcTWVkaWEgRGVz
Y3JpcHRpb27igJ06IFdoaWxlIHRydWUsIHRoZSB0ZXh0IGhlcmUgaXMgbm90IGEgDQo+PiBkZWZp
bml0aW9uIG9mIGFueXRoaW5nIGJ1dCBzeW50YXguIFBsZWFzZSBhZGQgYSBzZW50ZW5jZSBvciB0
d28gdG8gDQo+PiBzYXkgd2hhdCB0aGUgbWVkaWEgZGVzY3JpcHRpb24gc2VtYW50aWNhbGx5IHJl
cHJlc2VudHMuDQpJJ20gaGF2aW5nIHRyb3VibGUgZmluZGluZyBhIHN1aXRhYmxlIHNlbWFudGlj
IGRlZmluaXRpb24gb2YgTWVkaWEgRGVzY3JpcHRpb24uDQoNCk15IGZpcnN0IHRob3VnaHQgaXMg
dGhhdCBpdCBwcm92aWRlcyB0aGUgaW5mb3JtYXRpb24gbmVjZXNzYXJ5IHRvIGVzdGFibGlzaCBh
IG1lZGlhIHNlc3Npb24uIEJ1dCB3aGlsZSAqTXVsdGltZWRpYSBTZXNzaW9uKiBpcyBkZXNjcmli
ZWQsIG1lZGlhIFNlc3Npb24gaXNuJ3QgZGVmaW5lZCBpbiB0aGUgZG9jdW1lbnQuDQoNCkkgbG9v
a2VkIGF0IFJGQzc2NTYgKFRheG9ub215KSBmb3IgYSBkZWZpbml0aW9uLCBidXQgaXQgZG9lc24n
dCBoYXZlIG9uZSBlaXRoZXIuIEl0IGRlZmluZXMgUlRQIFNlc3Npb24sIGFuZCBNdWx0aW1lZGlh
IFNlc3Npb24gYXMgb25lIG9yIG1vcmUgUlRQIFNlc3Npb25zLiBUaGF0IGlzIGNsb3NlLCBidXQg
aW4gU0RQIG1lZGlhIHNlc3Npb25zIG5lZWQgbm90IGJlIFJUUC4NCg0KSXMgdGhlcmUgYW55IHN1
aXRhYmxlIGV4aXN0aW5nIGRlZmluaXRpb24/Pz8NCg0KSWYgbm90LCB0aGVuIGhvdyBhYm91dDoN
Cg0KIkEgTWVkaWEgRGVzY3JpcHRpb24gY29udGFpbnMgdGhlIGluZm9ybWF0aW9uIG5lZWRlZCBm
b3Igb25lIHBhcnR5IHRvIGVzdGFibGlzaCBhbiBhcHBsaWNhdGlvbiBsYXllciBuZXR3b3JrIHBy
b3RvY29sIGNvbm5lY3Rpb24gdG8gYW5vdGhlciBwYXJ0eS4iID8/Pw0KDQpPUg0KDQoiQSBNZWRp
YSBEZXNjcmlwdGlvbiBjb250YWlucyB0aGUgaW5mb3JtYXRpb24gbmVlZGVkIGZvciBvbmUgcGFy
dHkgdG8gZXN0YWJsaXNoIGEgTWVkaWEgU2Vzc2lvbiB3aXRoIGFub3RoZXIgcGFydHkuIg0KDQoi
QSBNZWRpYSBTZXNzaW9uIGlzIGFuIGFwcGxpY2F0aW9uIGxheWVyIG5ldHdvcmsgcHJvdG9jb2wg
Y29ubmVjdGlvbiBiZXR3ZWVuIHR3byBwYXJ0aWVzLiINCg0KSXQgc2VlbXMgaW1wb3J0YW50IHRv
IGdldCB0aGlzIHJpZ2h0ISBJdCBpcyBlc3NlbnRpYWxseSBhIGJyb2FkZW5pbmcgb2YNClJGQzc2
NTYgYmV5b25kIFJUUC4NCg0KCVRoYW5rcywNCglQYXVsDQoNCg0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1tdXNpYyBtYWlsaW5nIGxpc3QNCm1tdXNp
Y0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMN
Cg==


From nobody Tue Feb 19 07:48:11 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 3DC24130F09; Tue, 19 Feb 2019 07:48:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 JxInFxaVjO5x; Tue, 19 Feb 2019 07:48:08 -0800 (PST)
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 7BC1E130F07; Tue, 19 Feb 2019 07:48:08 -0800 (PST)
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 x1JFloRL005262 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 19 Feb 2019 10:47:51 -0500
To: "Roni Even (A)" <roni.even@huawei.com>, Ben Campbell <ben@nostrum.com>, "draft-ietf-mmusic-rfc4566bis.all@ietf.org" <draft-ietf-mmusic-rfc4566bis.all@ietf.org>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, mmusic WG <mmusic@ietf.org>, "'Colin Perkins'" <csp@csperkins.org>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu> <355f8125-87f8-6372-8289-126fa126ccb9@alum.mit.edu> <6E58094ECC8D8344914996DAD28F1CCD18CB5561@dggemm526-mbx.china.huawei.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <16e3f203-f914-34e6-8383-788231c78914@alum.mit.edu>
Date: Tue, 19 Feb 2019 10:47:50 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD18CB5561@dggemm526-mbx.china.huawei.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/hAgpmm9AKenCV-BjQzvSzfupNcQ>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
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, 19 Feb 2019 15:48:10 -0000

On 2/19/19 1:52 AM, Roni Even (A) wrote:
> Hi Paul,
> I am not sure why we need to  change the definition.
> 
> A media description describes the media and it start with a m= line  ... (and so on)
> 
> If want to expand maybe say that it must start with an m= line and will include the sdp types as listed in section 5

This came up because Ben felt that the current definition was inadequate 
because it is only syntactic. He asked for a semantic definition to be 
added.

IMO the fact that it seems hard to come up with a suitable semantic 
definition makes it more important to do so.

	Thanks,
	Paul


From nobody Tue Feb 19 08:06:42 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 BF00F130F0F for <mmusic@ietfa.amsl.com>; Tue, 19 Feb 2019 08:06:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=KXynRalU; dkim=pass (1024-bit key) header.d=ericsson.com header.b=mNTUuSxY
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 CkyXJ2N993Xm for <mmusic@ietfa.amsl.com>; Tue, 19 Feb 2019 08:06:38 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 E6087130F08 for <mmusic@ietf.org>; Tue, 19 Feb 2019 08:06:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/relaxed;  q=dns/txt; i=@ericsson.com; t=1550592395; x=1553184395; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=7GTwt/LYd/67dVvqBMo9xnGj2UgAuwEYITnsYJ+2uFQ=; b=KXynRalUDF9R4IhHHZsbxUgwcANpGeim3IdPRl8/Y9u+hYPjBFawx7Y8QI3HVwTy CLmpgU/79Zhn2SKtvUM1soKx4Whdj9RxKkH5BWQleSMTuMwWqiaJbnndCX7lEq2p zaewPROL38HG+1SeYJmOL2c9kf0vipU7gvgqRFoe4cc=;
X-AuditID: c1b4fb3a-167ff7000000672c-21-5c6c298b01a3
Received: from ESESBMB503.ericsson.se (Unknown_Domain [153.88.183.116]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 49.17.26412.B892C6C5; Tue, 19 Feb 2019 17:06:35 +0100 (CET)
Received: from ESESBMR501.ericsson.se (153.88.183.129) by ESESBMB503.ericsson.se (153.88.183.116) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 19 Feb 2019 17:06:34 +0100
Received: from ESESSMB504.ericsson.se (153.88.183.165) by ESESBMR501.ericsson.se (153.88.183.129) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 19 Feb 2019 17:06:34 +0100
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB504.ericsson.se (153.88.183.165) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Tue, 19 Feb 2019 17:06:34 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7GTwt/LYd/67dVvqBMo9xnGj2UgAuwEYITnsYJ+2uFQ=; b=mNTUuSxYT9S+4zoByG83ADwqHZOJwXJmlfGiaXLeYWLdGNz3QByvQbpkHRxwk7J+MUObFtDvqfj7CxW8zXYGNCipgXKrsq2uE9UtatYpb4Kab+pCIT9mgNDEv7mgSydMtxCAH0WX6En1JiWQjIgFc8U/RmYneeuTwt7ADgBuORY=
Received: from VI1PR07MB3167.eurprd07.prod.outlook.com (10.175.243.17) by VI1PR07MB4464.eurprd07.prod.outlook.com (20.177.57.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.7; Tue, 19 Feb 2019 16:06:33 +0000
Received: from VI1PR07MB3167.eurprd07.prod.outlook.com ([fe80::654f:5349:f2b4:176f]) by VI1PR07MB3167.eurprd07.prod.outlook.com ([fe80::654f:5349:f2b4:176f%4]) with mapi id 15.20.1622.020; Tue, 19 Feb 2019 16:06:33 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "Roni Even (A)" <roni.even@huawei.com>, Ben Campbell <ben@nostrum.com>, "draft-ietf-mmusic-rfc4566bis.all@ietf.org" <draft-ietf-mmusic-rfc4566bis.all@ietf.org>
CC: Magnus Westerlund <magnus.westerlund@ericsson.com>, mmusic WG <mmusic@ietf.org>, 'Colin Perkins' <csp@csperkins.org>
Thread-Topic: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
Thread-Index: AQHUx8f672wDf1L5zkyahFHOY88nA6Xmr7UAgACVqgCAACa/gA==
Date: Tue, 19 Feb 2019 16:06:32 +0000
Message-ID: <D50DD9EA-3E5B-47AE-9588-714C54C752D9@ericsson.com>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu> <355f8125-87f8-6372-8289-126fa126ccb9@alum.mit.edu> <6E58094ECC8D8344914996DAD28F1CCD18CB5561@dggemm526-mbx.china.huawei.com> <16e3f203-f914-34e6-8383-788231c78914@alum.mit.edu>
In-Reply-To: <16e3f203-f914-34e6-8383-788231c78914@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.15.0.190117
x-originating-ip: [192.176.1.86]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0fc992c8-b88e-4bf5-6c10-08d6968437c7
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600110)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB4464; 
x-ms-traffictypediagnostic: VI1PR07MB4464:
x-ms-exchange-purlcount: 1
x-microsoft-exchange-diagnostics: =?utf-8?B?MTtWSTFQUjA3TUI0NDY0OzIzOk1wWUhxcENHaHJPTDJnSlNxcGJ3NVhtZ1pq?= =?utf-8?B?YnZEcmpTL2g2Y2wvTGRFVUN1OWRncWkrVmZRRjYyNkkwbGdsSmNCZ1VSa1BW?= =?utf-8?B?QnNua0M5WmtTaDRzVWJ1bitRY2F5MGxPb2VRZGxoZUFNZk5WRGZaMk5heEkz?= =?utf-8?B?YS9jWS8wSGc3UXZUV1JDS1hZcktDNjZJdUNzd3ZkcEpCRkpqTG0yYzlQY1Zj?= =?utf-8?B?K1ZmeVJ5ektIOXNSYnBqaEpVTFpQOVR4Vnk4eVNYVzh5OHd2TkNENUhLU0hM?= =?utf-8?B?M3RxME5nQmdoZmRUY2ZvUzFsY1dtRFI2VTBOYS9adGxNeFE3cE9DaHR2eEQy?= =?utf-8?B?dlpPNkpldmdsUFZYZ0ttbXZGcFcyOVhGQTNyQVp6c1o0bG85djREL0hRQmxZ?= =?utf-8?B?U1IrNi85cGF4b0x4V0R4M3NRczZTZEVNR2tjNzhGalJhZndSYlIxTTF2elZv?= =?utf-8?B?M0YwRjFvY0xxRU16MTRlMWh1S3JGR1hJWmxZMlRpcWhOUEt5TDN0V0hpbDFr?= =?utf-8?B?ZWVXbVQwSU0yUldBSmNnTlVBVzhGL1Yvd1lKT2o3a0pjTzhZVWF2aEMza04v?= =?utf-8?B?azVvVnA5N0cyY2Z3ekhKdUNnWThvWndhMWxYTEJUUkxPWkFKb20zc3R5VFdW?= =?utf-8?B?TUdsaitjS2JtZnMvSHh4ekRzUCtTaEFjWUpXM0dvQWlIUTBnOEpaYXFaWmdl?= =?utf-8?B?ajNVUndMcWJDbnZDZ09CemxkSzZBYUFnSWdsY0VLbjB0U1duUmY5MzBGVWw3?= =?utf-8?B?UUd3UHZSWlVQemsrVGZVdnd1czZuT3QwelF6cjRNN09tUmpqYlNJQTF3cDJa?= =?utf-8?B?VmhWRGZWZlJld29sVjJYeGNVNm9oNlFIMTRZKytSVkg0bHYzcm51Y3hPNUsv?= =?utf-8?B?U1ByZ3p3SGUxWmZMSEQ5U25aRnRyWkEyemoxbHFxR3ZiaVhLaU8xNE41Y251?= =?utf-8?B?OENZNTUxZDFXRUtMa2Y3bncvZTJDNW1EbWNtcVBTenRMS1JrQ2FUS1JGTmxH?= =?utf-8?B?VlBpZHRlb0Y1b1RhZzdjZWVVbDhMY0xMR3RWcGRoSzYvakt4Ym9iTi9XRWZH?= =?utf-8?B?Tk51TVpEZ3RrYkNrc3J0QVMrL1FFTzNlUW5yYW9IN1FycExPbG5kY2dCekpI?= =?utf-8?B?VEZOOGJNWHgwcHJGUVR4a1BNenpRdEV0WDd1ajRBQUkxeEF2cHhtVlNaSWRv?= =?utf-8?B?eEVSRDhIeFNZOGQ5QkF1REZFakNWc2RFK1pSYm5ndU9uYUJHa25vY3IvbktI?= =?utf-8?B?c0ZPaTNsekREL29rUmdDQWRuWktmRXBsOUtRNWRsZys5T2JWMCtFRFpNY3Fs?= =?utf-8?B?T2ZPK2hWd0Q0RmhPWGtBSlpLV1pyL3VuNFNYaWNJeUQ3bUh0eHc1TlY5dmJG?= =?utf-8?B?YXBUd0RUbVllSHBaSUpnUmpieWxqWElFODFsUzUvWmNNL2V6cWdtNnVHQVdO?= =?utf-8?B?MHNPTEp5cXJ1eER2Qk5Sb2lZUlIxSk1PK3orcDRJcjJiY1BrWk5QRk5JRVlm?= =?utf-8?B?Qm5vNlB5RXVlVDhvbTdhdWdUaFZlRnFZaktOeDRKS2w3cVdwR3JVbkh6MnBp?= =?utf-8?B?MGVKZ3AyMHdCZUVVSUNTSXVVZ1ZnU2ZNdE5ySTZucWFVdHFCT2dpQmJNVC9B?= =?utf-8?B?bVlZeEtMYklKTnM0Rm1xWU1XR3BQVWN0eEJyKzRVNHdOcW9GSHl3Y1ZJQ3dR?= =?utf-8?B?eURZOVpJYlpjaGtSckRxTVZqUFFjaEJFYlEwUkMrWk5lNHo1dlBMeU5XVktS?= =?utf-8?B?Zy82QWRoWTZrYXlzZ0F1TFMzbHRheHpWRm9qd3dIVk9NVE1idUgxSUkvVFVI?= =?utf-8?B?eHZUcjdMc1lGMGtJTXBsOHpJOUFLbnhuU2Y4dnhkeXJCdFlYRXZwenFzUWxz?= =?utf-8?B?U2twNEZxMVRNU0tadlpmekluRDl4aVhDdkJENmNmbnp4V01ZZVJIT0lyUkpO?= =?utf-8?B?TUdzUHJBR1V3PT0=?=
x-microsoft-antispam-prvs: <VI1PR07MB4464B3B16381FEF426578BA8937C0@VI1PR07MB4464.eurprd07.prod.outlook.com>
x-forefront-prvs: 09538D3531
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(376002)(366004)(346002)(396003)(136003)(199004)(189003)(6486002)(305945005)(83716004)(2171002)(25786009)(186003)(44832011)(316002)(58126008)(110136005)(82746002)(68736007)(26005)(6246003)(6306002)(6512007)(2906002)(71190400001)(8676002)(71200400001)(53936002)(256004)(4326008)(8936002)(6436002)(53546011)(14444005)(93886005)(7736002)(102836004)(81166006)(81156014)(3846002)(5660300002)(6116002)(229853002)(6506007)(86362001)(66066001)(14454004)(6346003)(446003)(478600001)(76176011)(486006)(966005)(2501003)(97736004)(33656002)(105586002)(106356001)(11346002)(2616005)(54906003)(36756003)(99286004)(476003); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB4464; H:VI1PR07MB3167.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)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 79H68kVXo9CWzicBTrv6MuV9wTFJzqPIT3tKYwwrSISanrmZvA6cdBkYFTHT3adgadgfqJQ95aA5I0i0G9hlRaCVYcbQKaYYnJUQWNgHtVaRzCiFtKcInqlqVqEX51BzPE5ORamX8Q1vTxOwygrPR2F71UYEq8jF/cqnHGctSID9hlb+Wf8LPVN2Ma/SHhN2pbbVAmrNfo9/DAZuYpOCmldjpAMMvto9j7h9I8ahbkU3Aq0bshcBz6fyg+/PvVwHqH04Gh1PByA16cglgNpOmyHkO//1tu/V5u8qPkazTDWirqTuob/Iiv8lGsyWdRnoAnlYFywR034mSZV0QRfTN+PRUOazWuEx9RYpU9O2ghhqssgj64paAmo0fPB0xe03ylhPok0V3NL5BS5+zDU4HhEhf6ma/4cEO5rytqmDK6I=
Content-Type: text/plain; charset="utf-8"
Content-ID: <5BA2E872BB99334590B592C2E7712B4C@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0fc992c8-b88e-4bf5-6c10-08d6968437c7
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Feb 2019 16:06:32.5002 (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-Transport-CrossTenantHeadersStamped: VI1PR07MB4464
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA01Se0hTURzu3Hu3XVez45z6Q7NsVKCSLwqGhFokjFAyCBE1bLSLinParvmK YEVBuhKjTB2RYquF+UpKeyj5yjf5QCEzGuXEfFGoaVMbbbsL+u873+N8v/Pj0KT4Jc+bTlfn MBq1QiXlC6nKhNacwzp/VXLIUIerrKpoSCAzzvcj2bXRCkJWZpyhZE+bOniyld4RKoov//Pj JyG/bzLx5dd7lnlyg8FCyPWvzVQcL1F4TMmo0nMZTXDEeWHaYP+yILtkd/5z3QZfiz67FiMX GvARWOsdRcVISItxD4K6iRZkF8R4HUFjm5ITbHjK1EhyBwMBLTOVPLuLwqUkVDbu5YQ7BAxb Jwnu8A3Bh8kRm4um+VgGOmugnZfgEQTlN8ykPU3iQrj5bNuB3XES9I3ectwqwcnwqHVZwOET 0FLeyefaDoK1oZmwYxGOhLLqRefgdbaRhlcdgguOgqKOtw6MsCdsDNYRXJkXfDJXEdyrMRja RkgOe8D8jNVR7IGDYcs4RHG8H5g27zo9vjBepUMcjoWxwUXKXgx4CsG0dtwZCICrffXOAm/o H3vP40wP3aHGuOZMZ0BH2awzsAemh8rJUhSq/29AvW1jJPaHxjfBHC2H+vVexOH9cE/3VaB3 LMANBirNVDXi1SIPlmHZzNSwsCBGk36BZbPUQWompxnZPlPni63wV6hz7ngXwjSS7hLFSFTJ Yp4ily3I7EJAk1KJKFRoo0RKRUEho8lK0VxSMWwX8qEpqZdoW+yWLMapihwmg2GyGc0/laBd vLUocKL5iyR2vStmQnvxaNbsAepc3oKy5KOlvdto8Mt3XXxw9pBlOZZe6W7aadq3av2tjajv m3l8qv1RtcfS1lxe/qaSPHnFV347qHal6EzI9+yB6gbrr/ikqui1lIr4dz7RtXG6qYjLnjvq I6P61bKFFJfEJ1m0JSF8xf20IM1csySl2DRFaACpYRV/AdckOJVIAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/zv0yyLcUYHsJqyJQh2LbW9wNMXA>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
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, 19 Feb 2019 16:06:41 -0000

SGksDQoNClRoZSBtZWRpYSBkZXNjcmlwdGlvbiBkZXNjcmliZXMgdGhlIHByb3BlcnRpZXMsIGFz
c29jaWF0ZWQgd2l0aCBhIGRhdGEgZmxvdywgdGhhdCBhbiBlbmRwb2ludCBwcm92aWRlcyBpbiBv
cmRlciB0byBwcm9wZXJseSBiZSBhYmxlIHRvIHByb2Nlc3MgZGF0YSBhc3NvY2lhdGVkIHdpdGgg
dGhlIGRhdGEgZmxvdy4gSXQgaW5jbHVkZXMgSVAgYWRkcmVzcyBhbmQgcG9ydCwgYW5kIHByb3Bl
cnRpZXMgc3BlY2lmaWMgdG8gdGhlIHRyYW5zcG9ydCBwcm90b2NvbCBhbmQgbWVkaWEgdHlwZSBh
c3NvY2lhdGVkIHdpdGggdGhlIGRhdGEgZmxvdy4NCg0KLi4ub3Igc29tZXRoaW5nIGxpa2UgdGhh
dC4NCg0KSSBkb24ndCB0aGluayB3ZSBuZWVkIHRvIG1ha2UgaXQgbW9yZSBjb21wbGljYXRlZC4N
Cg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQrvu79PbiAxOS8wMi8yMDE5LCAxNy40OCwgIm1t
dXNpYyBvbiBiZWhhbGYgb2YgUGF1bCBLeXppdmF0IiA8bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmcg
b24gYmVoYWxmIG9mIHBreXppdmF0QGFsdW0ubWl0LmVkdT4gd3JvdGU6DQoNCiAgICBPbiAyLzE5
LzE5IDE6NTIgQU0sIFJvbmkgRXZlbiAoQSkgd3JvdGU6DQogICAgPiBIaSBQYXVsLA0KICAgID4g
SSBhbSBub3Qgc3VyZSB3aHkgd2UgbmVlZCB0byAgY2hhbmdlIHRoZSBkZWZpbml0aW9uLg0KICAg
ID4gDQogICAgPiBBIG1lZGlhIGRlc2NyaXB0aW9uIGRlc2NyaWJlcyB0aGUgbWVkaWEgYW5kIGl0
IHN0YXJ0IHdpdGggYSBtPSBsaW5lICAuLi4gKGFuZCBzbyBvbikNCiAgICA+IA0KICAgID4gSWYg
d2FudCB0byBleHBhbmQgbWF5YmUgc2F5IHRoYXQgaXQgbXVzdCBzdGFydCB3aXRoIGFuIG09IGxp
bmUgYW5kIHdpbGwgaW5jbHVkZSB0aGUgc2RwIHR5cGVzIGFzIGxpc3RlZCBpbiBzZWN0aW9uIDUN
CiAgICANCiAgICBUaGlzIGNhbWUgdXAgYmVjYXVzZSBCZW4gZmVsdCB0aGF0IHRoZSBjdXJyZW50
IGRlZmluaXRpb24gd2FzIGluYWRlcXVhdGUgDQogICAgYmVjYXVzZSBpdCBpcyBvbmx5IHN5bnRh
Y3RpYy4gSGUgYXNrZWQgZm9yIGEgc2VtYW50aWMgZGVmaW5pdGlvbiB0byBiZSANCiAgICBhZGRl
ZC4NCiAgICANCiAgICBJTU8gdGhlIGZhY3QgdGhhdCBpdCBzZWVtcyBoYXJkIHRvIGNvbWUgdXAg
d2l0aCBhIHN1aXRhYmxlIHNlbWFudGljIA0KICAgIGRlZmluaXRpb24gbWFrZXMgaXQgbW9yZSBp
bXBvcnRhbnQgdG8gZG8gc28uDQogICAgDQogICAgCVRoYW5rcywNCiAgICAJUGF1bA0KICAgIA0K
ICAgIF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICAg
bW11c2ljIG1haWxpbmcgbGlzdA0KICAgIG1tdXNpY0BpZXRmLm9yZw0KICAgIGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljDQogICAgDQoNCg==


From nobody Tue Feb 19 08:22:19 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 C2B1E130F20 for <mmusic@ietfa.amsl.com>; Tue, 19 Feb 2019 08:22:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 PlIZsPjmEL1e for <mmusic@ietfa.amsl.com>; Tue, 19 Feb 2019 08:22:15 -0800 (PST)
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 77A0D130F1E for <mmusic@ietf.org>; Tue, 19 Feb 2019 08:22:15 -0800 (PST)
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 x1JGMDuu007911 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Tue, 19 Feb 2019 11:22:13 -0500
To: mmusic@ietf.org
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu> <355f8125-87f8-6372-8289-126fa126ccb9@alum.mit.edu> <6E58094ECC8D8344914996DAD28F1CCD18CB5561@dggemm526-mbx.china.huawei.com> <16e3f203-f914-34e6-8383-788231c78914@alum.mit.edu> <D50DD9EA-3E5B-47AE-9588-714C54C752D9@ericsson.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <0d686068-f24f-a764-6297-38e2a1c08016@alum.mit.edu>
Date: Tue, 19 Feb 2019 11:22:12 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <D50DD9EA-3E5B-47AE-9588-714C54C752D9@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/0M-jnFNJU3-0PJj0PMbV_eg6-kI>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
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, 19 Feb 2019 16:22:18 -0000

On 2/19/19 11:06 AM, Christer Holmberg wrote:
> Hi,
> 
> The media description describes the properties, associated with a data flow, that an endpoint provides in order to properly be able to process data associated with the data flow. It includes IP address and port, and properties specific to the transport protocol and media type associated with the data flow.

I would rather not define it in terms of other undefined things. So I 
have a problem with "data flow".

It clearly has to do with a network connection, but only defines half of 
one.

When used with O/A, it defines only the receiving end of a connection, 
while with declarative SDP it defines both a sending and receiving end.

And while the c= line and the port from the m= line typically specify 
part of a *transport* protocol, the intent in the proto and fmt is to 
identify an application level protocol.

	Thanks,
	Paul

> ...or something like that.
> 
> I don't think we need to make it more complicated.
> 
> Regards,
> 
> Christer
> 
> 
> ﻿On 19/02/2019, 17.48, "mmusic on behalf of Paul Kyzivat" <mmusic-bounces@ietf.org on behalf of pkyzivat@alum.mit.edu> wrote:
> 
>      On 2/19/19 1:52 AM, Roni Even (A) wrote:
>      > Hi Paul,
>      > I am not sure why we need to  change the definition.
>      >
>      > A media description describes the media and it start with a m= line  ... (and so on)
>      >
>      > If want to expand maybe say that it must start with an m= line and will include the sdp types as listed in section 5
>      
>      This came up because Ben felt that the current definition was inadequate
>      because it is only syntactic. He asked for a semantic definition to be
>      added.
>      
>      IMO the fact that it seems hard to come up with a suitable semantic
>      definition makes it more important to do so.
>      
>      	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 Wed Feb 20 11:10:31 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 B1922130E7B; Wed, 20 Feb 2019 11:10:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 4q2zPaTYr3-H; Wed, 20 Feb 2019 11:10:29 -0800 (PST)
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 0F650130E7A; Wed, 20 Feb 2019 11:10:28 -0800 (PST)
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 x1KJAQE3009722 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 20 Feb 2019 14:10:26 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: Ben Campbell <ben@nostrum.com>, draft-ietf-mmusic-rfc4566bis.all@ietf.org
Cc: mmusic WG <mmusic@ietf.org>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com>
Message-ID: <8402099d-8d98-34b6-7de4-ae5a162888ae@alum.mit.edu>
Date: Wed, 20 Feb 2019 14:10:26 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@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/LnO6q2B4q7Z2A5u91UeGitYA-0w>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Local addresses
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, 20 Feb 2019 19:10:31 -0000

Ben,

On 2/11/19 10:45 PM, Ben Campbell wrote:
...
> §5.2: "Unless an SDP extension for NAT traversal is used
> (e.g., ICE [RFC8445], ICE TCP [RFC6544]), a local IP address MUST
> NOT be used in any context where the SDP description might leave
> the scope in which the address is meaningful”
> 
> That doesn’t apply to just any NAT traversal extension does it? It seems to require extensions that have scope-resolution properties similar to those of ICE.

When I came back to this I realized it is talking about an address in an 
o= line, not c=. Hence there is no intent that anybody connect to this, 
and ICE doesn't apply here. The address is primarily here to add to the 
uniqueness of the o= line. And note that the <sess-id> is required to 
make up any lack of uniqueness in the combination of the other fields. 
And privacy is leading to people not wanting to put real addresses or 
names in here.

I suggest we trim this back to:

    <unicast-address>  is an address of the machine from which the
       session was created.  For an address type of IP4, this is either a
       fully qualified domain name of the machine or the dotted-decimal
       representation of an IP version 4 address of the machine.  For an
       address type of IP6, this is either a fully qualified domain name
       of the machine or the compressed textual representation of an IP
       version 6 address of the machine.  For both IP4 and IP6, the fully
       qualified domain name is the form that SHOULD be given unless this
       is unavailable, in which case a globally unique address MAY be
       substituted.

And perhaps we should recommend that something bogus may be used to 
preserve some privacy.

I would like some feedback here!

	Thanks,
	Paul


From nobody Wed Feb 20 11:13:15 2019
Return-Path: <ben@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 17EFB130E7B; Wed, 20 Feb 2019 11:13:14 -0800 (PST)
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 9ABGbv-FM6Y8; Wed, 20 Feb 2019 11:13:12 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A48CA130E7A; Wed, 20 Feb 2019 11:13:12 -0800 (PST)
Received: from [10.0.1.29] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x1KJD7qC095919 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 20 Feb 2019 13:13:09 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1550689990; bh=Ep2r+b9MobPHYKVRhViu9gi91gJc5aSn2/i8ecYhiFU=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=A153xxxmYfi2+IVaTdX4o5enPo7joTkzBSDuMGbr9JkZ2cYiMtTVkbcDBwf6Nh5DK hD0lQj4Q4qa3/rfPPI0fZDju0HooPdK/jYHlHgyPdLO2Xd5TWJ2arNt7EOu+WfkpdO v3pSTahrDMvTe3wUl3CnGJH34FYzBSA0eSMxtZNg=
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.29]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <80E70150-AD8D-4279-BD2C-DFE554E3ED71@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_3C2A772F-50DC-448E-8637-039D18F69335"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Wed, 20 Feb 2019 13:13:06 -0600
In-Reply-To: <8402099d-8d98-34b6-7de4-ae5a162888ae@alum.mit.edu>
Cc: draft-ietf-mmusic-rfc4566bis.all@ietf.org, mmusic WG <mmusic@ietf.org>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <8402099d-8d98-34b6-7de4-ae5a162888ae@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/0fTcRdiAwedTb7_BBCCjwDGG2MU>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Local addresses
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, 20 Feb 2019 19:13:14 -0000

--Apple-Mail=_3C2A772F-50DC-448E-8637-039D18F69335
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Feb 20, 2019, at 1:10 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>=20
> Ben,
>=20
> On 2/11/19 10:45 PM, Ben Campbell wrote:
> ...
>> =C2=A75.2: "Unless an SDP extension for NAT traversal is used
>> (e.g., ICE [RFC8445], ICE TCP [RFC6544]), a local IP address MUST
>> NOT be used in any context where the SDP description might leave
>> the scope in which the address is meaningful=E2=80=9D
>> That doesn=E2=80=99t apply to just any NAT traversal extension does =
it? It seems to require extensions that have scope-resolution properties =
similar to those of ICE.
>=20
> When I came back to this I realized it is talking about an address in =
an o=3D line, not c=3D. Hence there is no intent that anybody connect to =
this, and ICE doesn't apply here. The address is primarily here to add =
to the uniqueness of the o=3D line. And note that the <sess-id> is =
required to make up any lack of uniqueness in the combination of the =
other fields. And privacy is leading to people not wanting to put real =
addresses or names in here.
>=20
> I suggest we trim this back to:
>=20
>   <unicast-address>  is an address of the machine from which the
>      session was created.  For an address type of IP4, this is either =
a
>      fully qualified domain name of the machine or the dotted-decimal
>      representation of an IP version 4 address of the machine.  For an
>      address type of IP6, this is either a fully qualified domain name
>      of the machine or the compressed textual representation of an IP
>      version 6 address of the machine.  For both IP4 and IP6, the =
fully
>      qualified domain name is the form that SHOULD be given unless =
this
>      is unavailable, in which case a globally unique address MAY be
>      substituted.
>=20
> And perhaps we should recommend that something bogus may be used to =
preserve some privacy.
>=20
> I would like some feedback here!

Works for me.

Thanks!

Ben.

--Apple-Mail=_3C2A772F-50DC-448E-8637-039D18F69335
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlxtpsIACgkQgFZKbJXz
1A2t/Q/+KppNU1UPQG21AqEWeLx9tEKO0KbOSp6AV00r8iS7R0HEmZ5a3uVqKGEC
5ZXLnwAFTsVBL+lYWOLPaC42bNrIK+yoTSKvwhU282c/eyx2OxC2W9Zicjfomtjy
0YyClPrKXpMt+DYPUbXVvHLXyrxfmsdBEDVi8NY724VStFWBDdJyFRwkSf6C/1W2
1bIRiDFlSYfwOHaMG6yvht3Y3GPLpqgc5aSCvRBnZE6xjii355jxIoVOlgiW8N85
eaANI+6CJ1R4bnBZot32hDM2ZWcvkIY5m1TTUhsCQcHG2AjqAFogMt4cqrI7LuY9
pXAg7e1CD7Fuhqu7G6k3OyxbqoZUKy6QfWiedZZK1BZo3vLjhhoXlMGUj08bvwN0
5f431aga6IeiJ5qeyQCC0BzrSW8yZswcVoSf3uNyMNL/uGaYqIWi3YVrQLMojxuR
h0zLpmC+AjuVwPGb1QyLBY/nz+VPTGQfUn64dYDI8J2MxZeHq5SHZI7uzlTMiji0
AoRcYteOX14eIMQMTI++x1oqbd4+6/x9emLmm0te8UDdAYBoDrCLZdzPUd3r1DQY
yq6IlDMe2vnnDk3dtSLv+y1AQ1Skf/C64+7EmaWocN33ERCXRux56sCPu9wmptWT
O/ohveRj2ykoFAGOctDr78HSK0DKwsaJGzJko6Tfl+kjpJuNQls=
=nRvS
-----END PGP SIGNATURE-----

--Apple-Mail=_3C2A772F-50DC-448E-8637-039D18F69335--


From nobody Wed Feb 20 12:39:21 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 98584129B88 for <mmusic@ietfa.amsl.com>; Wed, 20 Feb 2019 12:39:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 3PvaKqxlRDv9 for <mmusic@ietfa.amsl.com>; Wed, 20 Feb 2019 12:39:17 -0800 (PST)
Received: from mail-yb1-xb42.google.com (mail-yb1-xb42.google.com [IPv6:2607:f8b0:4864:20::b42]) (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 56E3812950A for <mmusic@ietf.org>; Wed, 20 Feb 2019 12:39:17 -0800 (PST)
Received: by mail-yb1-xb42.google.com with SMTP id j189so10140347ybj.9 for <mmusic@ietf.org>; Wed, 20 Feb 2019 12:39:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked-media.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VGyaU1AJm3cqHvyo0P43wnJLXPaggkRfJt5obycUn1E=; b=vCvUYDNTICopv7fJsJil9O9eOjadd3lAqL9eTOrfR+H537rfn3lphnGiy/BjP/sUx/ ikv3/OMfV9EkhQLDEd03IPvVC1GjOPUfohZvYTN1g5lZYJrmao3UiqeijKKaCCi9+ojq KvCjuYwE/TE3VBeUAFEhdYAUrLTfLKklr5ML2Rtbv/YawrvCcadZGyoB26nSl6t4cy/M 56B86mMbrFtc/I9WO/zLfdqvGmoXrFtbK70YKWiavWejlH3chynzmaV0cY8rHqo4ryrR WkAw6ERVhkhGB/Efkbj68scJndCIOZ6T1HPDyZRoRTayryct8Mhen/++70cKN99XQ7AD treQ==
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=VGyaU1AJm3cqHvyo0P43wnJLXPaggkRfJt5obycUn1E=; b=n+YJst/BQTnxBlQU+wXxWD8lJmFJKbHiFExOAdnZxyWSJax526rWBiBSQPvUq5ZlK5 mLZcDSLPtNJfvvX2lnTP6ic8ELkJXa9oHHkYkRwoGxOUh6+s+IOY3Cj0FwCj9xtaUidM he8lethIQ5zasPq1VgF3fyy+lfsoCggmyyS2nO6Er7xhnxMOnvZVWsB6IB0PN1ISTD8U rjS3+m8wgFL5z3dhefgjhR7ZZFPG41j1bAOAzr3MupI2GbruA0SblDrgzUIxQTQFtXNj cy/+rmjNEjbja3xMy2GyNBaWfmXbSd35WFdSmrziUEraCZOUq7ZSIw3r46wuLO5MNf4J Nrsw==
X-Gm-Message-State: AHQUAuZwIcXqKIRtrBuPoc95GJvVZ7ci6oRVRMdqgwStb9nULI7z3kOB Mxc5LwIkEfshjpVrjLA1RZCeGbPgaFQr6bw1OWcDRA==
X-Google-Smtp-Source: AHgI3Ib/uHAGmLKmYUbkxEm7VoUfZOyYxo+v8qKW/nxJ3yi8KEjQmrpAGjlcrJtYxNCEiwOxm/5gpFp+60RWtWkiXNU=
X-Received: by 2002:a25:bd4b:: with SMTP id p11mr30579358ybm.251.1550695156278;  Wed, 20 Feb 2019 12:39:16 -0800 (PST)
MIME-Version: 1.0
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <8402099d-8d98-34b6-7de4-ae5a162888ae@alum.mit.edu>
In-Reply-To: <8402099d-8d98-34b6-7de4-ae5a162888ae@alum.mit.edu>
From: "Ali C. Begen" <ali.begen@networked.media>
Date: Wed, 20 Feb 2019 23:39:05 +0300
Message-ID: <CAA4McztV9b_VET6bycyspXiNPXr2J6VE3g+o9t3nKvwf2DmbrQ@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: Ben Campbell <ben@nostrum.com>, draft-ietf-mmusic-rfc4566bis.all@ietf.org,  mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f200d70582595919"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/bjYMVz3oNtS6AO-MeePz6EzeeKw>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Local addresses
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, 20 Feb 2019 20:39:20 -0000

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

On Wed, Feb 20, 2019 at 10:10 PM Paul Kyzivat <pkyzivat@alum.mit.edu> wrote=
:

> Ben,
>
> On 2/11/19 10:45 PM, Ben Campbell wrote:
> ...
> > =C2=A75.2: "Unless an SDP extension for NAT traversal is used
> > (e.g., ICE [RFC8445], ICE TCP [RFC6544]), a local IP address MUST
> > NOT be used in any context where the SDP description might leave
> > the scope in which the address is meaningful=E2=80=9D
> >
> > That doesn=E2=80=99t apply to just any NAT traversal extension does it?=
 It seems
> to require extensions that have scope-resolution properties similar to
> those of ICE.
>
> When I came back to this I realized it is talking about an address in an
> o=3D line, not c=3D. Hence there is no intent that anybody connect to thi=
s,
> and ICE doesn't apply here. The address is primarily here to add to the
> uniqueness of the o=3D line. And note that the <sess-id> is required to
> make up any lack of uniqueness in the combination of the other fields.
> And privacy is leading to people not wanting to put real addresses or
> names in here.
>
> I suggest we trim this back to:
>
>     <unicast-address>  is an address of the machine from which the
>        session was created.  For an address type of IP4, this is either a
>        fully qualified domain name of the machine or the dotted-decimal
>        representation of an IP version 4 address of the machine.  For an
>        address type of IP6, this is either a fully qualified domain name
>        of the machine or the compressed textual representation of an IP
>        version 6 address of the machine.  For both IP4 and IP6, the fully
>        qualified domain name is the form that SHOULD be given unless this
>        is unavailable, in which case a globally unique address MAY be
>        substituted.
>
> And perhaps we should recommend that something bogus may be used to
> preserve some privacy.
>

Maybe use RFC 7022 for the privacy goal?


>
> I would like some feedback here!
>
>         Thanks,
>         Paul
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Feb 20, 2019 at 10:10 PM Paul=
 Kyzivat &lt;<a href=3D"mailto:pkyzivat@alum.mit.edu">pkyzivat@alum.mit.edu=
</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">=
Ben,<br>
<br>
On 2/11/19 10:45 PM, Ben Campbell wrote:<br>
...<br>
&gt; =C2=A75.2: &quot;Unless an SDP extension for NAT traversal is used<br>
&gt; (e.g., ICE [RFC8445], ICE TCP [RFC6544]), a local IP address MUST<br>
&gt; NOT be used in any context where the SDP description might leave<br>
&gt; the scope in which the address is meaningful=E2=80=9D<br>
&gt; <br>
&gt; That doesn=E2=80=99t apply to just any NAT traversal extension does it=
? It seems to require extensions that have scope-resolution properties simi=
lar to those of ICE.<br>
<br>
When I came back to this I realized it is talking about an address in an <b=
r>
o=3D line, not c=3D. Hence there is no intent that anybody connect to this,=
 <br>
and ICE doesn&#39;t apply here. The address is primarily here to add to the=
 <br>
uniqueness of the o=3D line. And note that the &lt;sess-id&gt; is required =
to <br>
make up any lack of uniqueness in the combination of the other fields. <br>
And privacy is leading to people not wanting to put real addresses or <br>
names in here.<br>
<br>
I suggest we trim this back to:<br>
<br>
=C2=A0 =C2=A0 &lt;unicast-address&gt;=C2=A0 is an address of the machine fr=
om which the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0session was created.=C2=A0 For an address type o=
f IP4, this is either a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0fully qualified domain name of the machine or th=
e dotted-decimal<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0representation of an IP version 4 address of the=
 machine.=C2=A0 For an<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0address type of IP6, this is either a fully qual=
ified domain name<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0of the machine or the compressed textual represe=
ntation of an IP<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0version 6 address of the machine.=C2=A0 For both=
 IP4 and IP6, the fully<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0qualified domain name is the form that SHOULD be=
 given unless this<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0is unavailable, in which case a globally unique =
address MAY be<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0substituted.<br>
<br>
And perhaps we should recommend that something bogus may be used to <br>
preserve some privacy.<br></blockquote><div><br></div><div>Maybe use RFC 70=
22 for the privacy goal?</div><div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">
<br>
I would like some feedback here!<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Thanks,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Paul<br>
<br>
</blockquote></div></div>

--000000000000f200d70582595919--


From nobody Wed Feb 20 16:08:07 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 51FB21274D0 for <mmusic@ietfa.amsl.com>; Wed, 20 Feb 2019 16:08:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 srreh-DdHrGZ for <mmusic@ietfa.amsl.com>; Wed, 20 Feb 2019 16:08:03 -0800 (PST)
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 82A28124BAA for <mmusic@ietf.org>; Wed, 20 Feb 2019 16:08:03 -0800 (PST)
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 x1L07mL3027655 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 20 Feb 2019 19:07:48 -0500
To: IETF MMUSIC WG <mmusic@ietf.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: Mark Handley <M.Handley@cs.ucl.ac.uk>, "'Colin Perkins'" <csp@csperkins.org>
Message-ID: <7fc571de-eadd-6929-d227-1453500c97bc@alum.mit.edu>
Date: Wed, 20 Feb 2019 19:07:47 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.5.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/gDaUeWQwWQ8qWhJqTxs3Z7YkV9U>
Subject: [MMUSIC] RFC4566bis: what is the origin of change to IP6-address ???
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, 21 Feb 2019 00:08:05 -0000

In trying to clean up 4566bis I'm making a list of changes.
A big one is the syntax of IP6-address. This is an entirely new 
definition. The old one had a reference to where it came from. The new 
one doesn't. I'm looking for the source of this, and why the change was 
made.

The change appeared in -00 of 4566bis from 6-dec-2007. I haven't been 
able to figure out who submitted it. I found the announcement of this 
version in my own archives, but I found no other emails discussing it.

Does anybody know:
- the source for the IP6-address def?
- who submitted the -00 version that made the change?

	Thanks,
	Paul


From nobody Wed Feb 20 16:31:40 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 67B37130ED7 for <mmusic@ietfa.amsl.com>; Wed, 20 Feb 2019 16:31:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tMYdRbzzIbBu for <mmusic@ietfa.amsl.com>; Wed, 20 Feb 2019 16:31:37 -0800 (PST)
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 A6502130ED0 for <mmusic@ietf.org>; Wed, 20 Feb 2019 16:31:37 -0800 (PST)
Received: from [81.187.2.149] (port=36766 helo=[192.168.0.78]) 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 1gwcGy-0000aR-6H; Thu, 21 Feb 2019 00:31:36 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <7fc571de-eadd-6929-d227-1453500c97bc@alum.mit.edu>
Date: Thu, 21 Feb 2019 00:31:24 +0000
Cc: IETF MMUSIC WG <mmusic@ietf.org>, Mark Handley <M.Handley@cs.ucl.ac.uk>
Content-Transfer-Encoding: quoted-printable
Message-Id: <95E24FC8-5E9D-4414-B7C8-64762C16DCAF@csperkins.org>
References: <7fc571de-eadd-6929-d227-1453500c97bc@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 14
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jNIKEUAwv0sYfsDzbmje27lstOg>
Subject: Re: [MMUSIC] RFC4566bis: what is the origin of change to IP6-address ???
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, 21 Feb 2019 00:31:39 -0000

> On 21 Feb 2019, at 00:07, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
> In trying to clean up 4566bis I'm making a list of changes.
> A big one is the syntax of IP6-address. This is an entirely new =
definition. The old one had a reference to where it came from. The new =
one doesn't. I'm looking for the source of this, and why the change was =
made.
>=20
> The change appeared in -00 of 4566bis from 6-dec-2007. I haven't been =
able to figure out who submitted it. I found the announcement of this =
version in my own archives, but I found no other emails discussing it.
>=20
> Does anybody know:
> - the source for the IP6-address def?

As far as I can tell, the change came from =
draft-gurbani-sip-ipv6-abnf-fix-00, via the SIP and MMUSIC mailing lists =
on 19/20 Nov 2007: =
https://mailarchive.ietf.org/arch/msg/sip/C5BD-wexP0fp_fcIuKOJxvGJ_iA

> - who submitted the -00 version that made the change?


I did.

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





From nobody Thu Feb 21 00:03:49 2019
Return-Path: <roni.even@huawei.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 4BB971277CC; Thu, 21 Feb 2019 00:03:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7HIf-gA2pmpO; Thu, 21 Feb 2019 00:03:45 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69315127287; Thu, 21 Feb 2019 00:03:45 -0800 (PST)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 8F0B9ED5FB2C7A87062E; Thu, 21 Feb 2019 08:03:43 +0000 (GMT)
Received: from lhreml708-chm.china.huawei.com (10.201.108.57) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 21 Feb 2019 08:03:42 +0000
Received: from lhreml708-chm.china.huawei.com (10.201.108.57) by lhreml708-chm.china.huawei.com (10.201.108.57) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Thu, 21 Feb 2019 08:03:43 +0000
Received: from DGGEMM401-HUB.china.huawei.com (10.3.20.209) by lhreml708-chm.china.huawei.com (10.201.108.57) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Thu, 21 Feb 2019 08:03:42 +0000
Received: from DGGEMM526-MBX.china.huawei.com ([169.254.8.222]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0415.000; Thu, 21 Feb 2019 16:03:15 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Ben Campbell <ben@nostrum.com>, "draft-ietf-mmusic-rfc4566bis.all@ietf.org" <draft-ietf-mmusic-rfc4566bis.all@ietf.org>
CC: Magnus Westerlund <magnus.westerlund@ericsson.com>, mmusic WG <mmusic@ietf.org>, 'Colin Perkins' <csp@csperkins.org>
Thread-Topic: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
Thread-Index: AQHUx8fxbs918E2F1karkE7QXY8wS6XmrKuQgAASmACAAygfYA==
Date: Thu, 21 Feb 2019 08:03:15 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD18CB6D4B@dggemm526-mbx.china.huawei.com>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <e7e0042a-8079-8c0e-0ddd-1ea330f08e7c@alum.mit.edu> <355f8125-87f8-6372-8289-126fa126ccb9@alum.mit.edu> <6E58094ECC8D8344914996DAD28F1CCD18CB5561@dggemm526-mbx.china.huawei.com> <16e3f203-f914-34e6-8383-788231c78914@alum.mit.edu>
In-Reply-To: <16e3f203-f914-34e6-8383-788231c78914@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.80]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2UL1d8kAhdv5_XdTwUDPGBobHEk>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32: Media Description
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, 21 Feb 2019 08:03:47 -0000

SGkgUGF1bCwNCkkgdGhpbmsgdGhlIHNlbWFudGljcyBpcyB0aGF0IGl0IGluY2x1ZGVzIGFsbCBh
dHRyaWJ1dGVzIHRoYXQgZGVzY3JpYmUgYSBzcGVjaWZpYyBtZWRpYSBvbiB0b3Agb2YgdGhlIHNl
c3Npb24gZGVzY3JpcHRpb24gYW5kIGNhbiBvdmVycmlkZSBzZXNzaW9uIGF0dHJpYnV0ZXMgZm9y
IHRoaXMgc3BlY2lmaWMgbWVkaWENClJvbmkNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
CkZyb206IFBhdWwgS3l6aXZhdCBbbWFpbHRvOnBreXppdmF0QGFsdW0ubWl0LmVkdV0gDQpTZW50
OiBUdWVzZGF5LCBGZWJydWFyeSAxOSwgMjAxOSA1OjQ4IFBNDQpUbzogUm9uaSBFdmVuIChBKTsg
QmVuIENhbXBiZWxsOyBkcmFmdC1pZXRmLW1tdXNpYy1yZmM0NTY2YmlzLmFsbEBpZXRmLm9yZw0K
Q2M6IE1hZ251cyBXZXN0ZXJsdW5kOyBtbXVzaWMgV0c7ICdDb2xpbiBQZXJraW5zJw0KU3ViamVj
dDogUmU6IFtNTVVTSUNdIEFEIEV2YWx1YXRpb24gb2YgZHJhZnQtaWV0Zi1tbXVzaWMtcmZjNDU2
NmJpcy0zMjogTWVkaWEgRGVzY3JpcHRpb24NCg0KT24gMi8xOS8xOSAxOjUyIEFNLCBSb25pIEV2
ZW4gKEEpIHdyb3RlOg0KPiBIaSBQYXVsLA0KPiBJIGFtIG5vdCBzdXJlIHdoeSB3ZSBuZWVkIHRv
ICBjaGFuZ2UgdGhlIGRlZmluaXRpb24uDQo+IA0KPiBBIG1lZGlhIGRlc2NyaXB0aW9uIGRlc2Ny
aWJlcyB0aGUgbWVkaWEgYW5kIGl0IHN0YXJ0IHdpdGggYSBtPSBsaW5lICANCj4gLi4uIChhbmQg
c28gb24pDQo+IA0KPiBJZiB3YW50IHRvIGV4cGFuZCBtYXliZSBzYXkgdGhhdCBpdCBtdXN0IHN0
YXJ0IHdpdGggYW4gbT0gbGluZSBhbmQgDQo+IHdpbGwgaW5jbHVkZSB0aGUgc2RwIHR5cGVzIGFz
IGxpc3RlZCBpbiBzZWN0aW9uIDUNCg0KVGhpcyBjYW1lIHVwIGJlY2F1c2UgQmVuIGZlbHQgdGhh
dCB0aGUgY3VycmVudCBkZWZpbml0aW9uIHdhcyBpbmFkZXF1YXRlIGJlY2F1c2UgaXQgaXMgb25s
eSBzeW50YWN0aWMuIEhlIGFza2VkIGZvciBhIHNlbWFudGljIGRlZmluaXRpb24gdG8gYmUgYWRk
ZWQuDQoNCklNTyB0aGUgZmFjdCB0aGF0IGl0IHNlZW1zIGhhcmQgdG8gY29tZSB1cCB3aXRoIGEg
c3VpdGFibGUgc2VtYW50aWMgZGVmaW5pdGlvbiBtYWtlcyBpdCBtb3JlIGltcG9ydGFudCB0byBk
byBzby4NCg0KCVRoYW5rcywNCglQYXVsDQo=


From nobody Thu Feb 21 07:05:51 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 25BD4130DDA for <mmusic@ietfa.amsl.com>; Thu, 21 Feb 2019 07:05:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 kJzv8OwxzZQa for <mmusic@ietfa.amsl.com>; Thu, 21 Feb 2019 07:05:47 -0800 (PST)
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 53C0D12F1A2 for <mmusic@ietf.org>; Thu, 21 Feb 2019 07:05:46 -0800 (PST)
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 x1LF5i9G012358 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Thu, 21 Feb 2019 10:05:45 -0500
To: mmusic@ietf.org
References: <7fc571de-eadd-6929-d227-1453500c97bc@alum.mit.edu> <95E24FC8-5E9D-4414-B7C8-64762C16DCAF@csperkins.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <8c9d8b6a-5b72-3f07-c2a2-193faae87a37@alum.mit.edu>
Date: Thu, 21 Feb 2019 10:05:44 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <95E24FC8-5E9D-4414-B7C8-64762C16DCAF@csperkins.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/_Ub6akuV0cVFJIrazFb0hBR4U2U>
Subject: Re: [MMUSIC] RFC4566bis: what is the origin of change to IP6-address ???
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, 21 Feb 2019 15:05:49 -0000

On 2/20/19 7:31 PM, Colin Perkins wrote:
> 
>> On 21 Feb 2019, at 00:07, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>
>> In trying to clean up 4566bis I'm making a list of changes.
>> A big one is the syntax of IP6-address. This is an entirely new definition. The old one had a reference to where it came from. The new one doesn't. I'm looking for the source of this, and why the change was made.
>>
>> The change appeared in -00 of 4566bis from 6-dec-2007. I haven't been able to figure out who submitted it. I found the announcement of this version in my own archives, but I found no other emails discussing it.
>>
>> Does anybody know:
>> - the source for the IP6-address def?
> 
> As far as I can tell, the change came from draft-gurbani-sip-ipv6-abnf-fix-00, via the SIP and MMUSIC mailing lists on 19/20 Nov 2007: https://mailarchive.ietf.org/arch/msg/sip/C5BD-wexP0fp_fcIuKOJxvGJ_iA

Ah! That explains it. The same fix was made to 3261 by RFC5964.

>> - who submitted the -00 version that made the change?

So *you* started this in 2007! We are working expeditiously to get it 
published. :-)

	Thanks,
	Paul


From nobody Fri Feb 22 12:49:09 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 53AAC130F6D; Fri, 22 Feb 2019 12:49:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.91.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mmusic@ietf.org
Message-ID: <155086854131.5484.908607386332296353@ietfa.amsl.com>
Date: Fri, 22 Feb 2019 12:49:01 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ZXJ5dequcgcdtX1M63135YAkbJg>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-rfc4566bis-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: Fri, 22 Feb 2019 20:49: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           : SDP: Session Description Protocol
        Authors         : Ali Begen
                          Paul Kyzivat
                          Colin Perkins
                          Mark Handley
	Filename        : draft-ietf-mmusic-rfc4566bis-33.txt
	Pages           : 61
	Date            : 2019-02-22

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-33
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-rfc4566bis-33

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-rfc4566bis-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 Fri Feb 22 12:58: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 049E4130E5E; Fri, 22 Feb 2019 12:58:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ImIOFuE5mRQ4; Fri, 22 Feb 2019 12:58:21 -0800 (PST)
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 798AD130E5F; Fri, 22 Feb 2019 12:58:21 -0800 (PST)
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 x1MKwHNd019045 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 22 Feb 2019 15:58:18 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: Ben Campbell <ben@nostrum.com>, draft-ietf-mmusic-rfc4566bis.all@ietf.org
Cc: mmusic WG <mmusic@ietf.org>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com>
Message-ID: <2f297a3c-39d4-cb99-65f4-f0bcd072306a@alum.mit.edu>
Date: Fri, 22 Feb 2019 15:58:17 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@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/o_067yHrNY1ZEK5iuYBkuzFP6OU>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32
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, 22 Feb 2019 20:58:25 -0000

Ben,

I just submitted -33. It attempts to address most, but not all, of your 
comments. See my detailed replies below. I need help for some of the 
remainder, specifically security considerations.

There will need to be another revision to address the remaining items.

	Thanks,
	Paul

On 2/11/19 10:45 PM, Ben Campbell wrote:
> Hi,
> 
> This is my AD evaluation of draft-ietf-mmusic-rfc4566bis-32. I have several minor substantive comments, and a number of editorial comments and nits. I’d like to resolve at least the substantive comments prior to IETF last call.
> 
> Thanks!
> 
> Ben.
> ----------------------
> 
> 
> *** Substantive Comments ***
> 
> §1, last paragraph: The statement that this update is limited to essential corrections is demonstrably untrue. For example, this version changes a lot of spellings from British English to US English. While that might be best for the sake of consistency, it would be hard to argue that it is _essential_.

I removed this claim.

> Along the same lines, §10 does not seem to capture all material changes.

I've tried to summarize all the important changes.

> §2, “Media Description”: While true, the text here is not a definition of anything but syntax. Please add a sentence or two to say what the media description semantically represents.

I've added my attempt at describing the semantics. (I posted a query 
about this but didn't get a response that seemed to work.

Please comment if you want a further change.

> - Deleted text formerly in §4.3: The removal of the “private sessions” section in its entirety deserves some explanatory text.

I posted a query about this. The consensus was that the removal here is 
right, but that more discussion is needed in the Security Considerations 
section. But I don't know what to write. I need some help on that.

> §5.2: "Unless an SDP extension for NAT traversal is used
> (e.g., ICE [RFC8445], ICE TCP [RFC6544]), a local IP address MUST
> NOT be used in any context where the SDP description might leave
> the scope in which the address is meaningful”
> 
> That doesn’t apply to just any NAT traversal extension does it? It seems to require extensions that have scope-resolution properties similar to those of ICE.

After reading 5.2 again I realized it is talking about an address in an 
o= line, not c=. Hence there is no intent that anybody connect to this, 
and ICE doesn't apply here. The address is primarily here to add to the 
uniqueness of the o= line. And note that the <sess-id> is required to 
make up any lack of uniqueness in the combination of the other fields. 
And privacy is leading to people not wanting to put real addresses or 
names in here.

So I removed all the discussion of ICE.

Please comment if you think this isn't sufficient or appropriate.

> §5.8: "Use of the "X-" prefix is NOT RECOMMENDED: instead new (non "X-"
> prefix) <bwtype> names SHOULD be defined, and then MUST be registered
> with IANA in the standard namespace.”
> 
> “SHOULD be defined” seems to be in tension with “MUST be registered”.

I twiddled with this. Does it work for you now?

> §5.13: "The "k=" line (key-field) is obsolete and MUST NOT be used.”
> Should it be removed from the field order definition in §5?

It continues to be mentioned because implementations may need to support 
it for backward compatibility with 4566. In that case they need to know 
where it goes.

I left this unchanged.

> §6.1: Please state what behavior is meant by “This attribute is obsoleted”. For example, MUST not send but SHOULD accept? Something different? (This pattern occurs for multiple attributes.)

I beefed up the language for this.

> §6.7.4: "Note that an RTP-based system MUST still send RTCP (if RTCP
> is used), even if started inactive.”
> Other similar attributes use SHOULD instead of MUST. Is the inconsistency intentional?

I brought this to the list. The feedback I got was that is change is 
correct.

> §7, last paragraph:
> What is the impact of this on RFC 4568 (security descriptions)? That RFC seems to allow the use of “k=“ lines at a MAY level. Does this draft need to update that? But more importantly, is it worth distinguishing the case of E@E protection of keying material vs the HBH protection offered by security descriptions?

This text is unchanged since 4566.

I need help with this from a security person.

> §8 and subsectionsl:
> 
> I think there needs to be more clarity about what this draft defines vs what was defined in previous versions, and what has changed. For example, language to the effect of "XXX was originally defined in RFC 4566. This document requests IANA to change the reference to “RFC-this”.”

Done.

> §8.2: "The contact address for all parameters registered below is:
> IETF MMUSIC working group <mmusic@ietf.org>”
> Please consider “The IETF MMUSIC working group <mmusic@ietf.org> or its successor as designated by the IESG.”

Done.

> §8.2.1: "Until that is done, applications SHOULD NOT use these
> types and SHOULD NOT declare support for them in SIP capabilities
> declarations (even though they exist in the registry created by
> [RFC3840]).”
> 
> Should this spec update 3840?

Leaving 3840 as-is doesn't hurt anything. As long as these aren't used 
in m-lines then usage in 3840/3841 will be moot.

I left this as-is.

> §8.2.4.2: This section needs some guidance about the maturity of specs needed to update attributes defined in previous specs. While the registration policy is “spec required”, what happens if someone defines FOO in a standards-track RFC, and someone else wants to update it with some lower-maturity instrument?

> Along the same line, is there any restriction from party B updating an attribute defined by party A without consent? That is clear for IETF stream RFCs where the IETF retains change control, but might not be clear for other specification forms.

Specification Required calls for a designated expert to review the 
registration. I revised the language to ask the expert to consider these 
issues.

> §8.2.8: Are telephone numbers still necessary? Under GDPR rules, we should be careful about requiring data unless there is a clear need for it.

I removed the requirement for a phone number. (This makes it consistent 
with the template for attribute registrations that already didn't ask 
for a phone number.)

> *** Editorial Comments and Nits ***
> 
> §3.3, 2nd paragraph: "Note that descriptions of multicast sessions made only via email or…”
> 
> The sentence no longer makes sense with the change from “announcement” to “description”. If you want to avoid the term “announcements”, consider something like “… descriptions of multicast sessions sent only via email…”

Done.

> §4.1: "This address and port is the destination address and destination port”: Plural disagreement. (It was correct in 4566.)

Fixed.

> §5:
> - “… the end of the whole session description - whichever…”: A dash usually separates two independent clauses, much like a semicolon. That is not the cast here; a comma would be more appropriate.

Done

> - "Some lines in each description are REQUIRED and some are OPTIONAL,” : While I recognize these are unchanged from 4566, the REQUIRED and OPTIONAL terms seem like statements of fact rather than normative statements.

I cleaned this up and made it explicit that the ABNF is normative and 
this section is only a summary of the ABNF.

> - "media-, or session-specific basis” : Incorrect comma usage.

IIUC this is an "Oxford comma", and the use of it is controversial. Does 
IETF have a policy on its use?

(Or we can leave it for the editor to decide.)

I've left this unchanged for now.

> - "An SDP description may contain URIs”
>   I'm not sure this change makes sense. Should it say ''session description”?

After investigating further, I realized that “session description” and 
“SDP description” are used synonymously through the document. So this 
change isn’t *wrong*. IIRC I did it to be consistent with the other 
usage of "SDP description" in the vicinity of this.

I suspect that “session description” might have been considered an 
abstract concept, with an "SDP description" being a specific realization 
of that. But the document doesn’t really make this distinction. And “SDP 
description” is redundant (Session Description Protocol description).

So perhaps every occurrence of “SDP description” should be changed to 
“Session Description”. Alternately, we could change every occurrence of 
"Session Description" to "SDP description".

For now I have left things as-is.

> - "Text containing fields such as the session-name-field and
> information-field”:
> This is ambiguous. Are we talking about text that contains fields, or text-containing fields? From context, I assume the latter.

Done.

> §5.5: "The "u=" line (uri-field) provides URI (Uniform Resource Identifier)
> as used by WWW clients”
> Missing article before URI

Done.

> §5.7:
> - "The "c=" line (connection-field) contains connection data.”
> The section heading was changed from “connection data” to “connection information”. Should that change apply here, too?

That seems pretty circular. Instead I changed it to:

"The "c=" line (connection-field) contains information necessary to 
establish a connection.”

> - There are a number of places in this section (and maybe elsewhere) where IPv6 was changed to IP6. While I realize 4566 was inconsistent on this, wouldn’t it make more sense to change to consistently use the more conventional “IPv6”?  (Probably also true for IP4/IPv4).

This turns out to be tricky: "IP4" and "IP6" are the encodings used in 
the m-line. They are also used in the names of ABNF rules such as 
"IP4-address" and "IP4-multicast".

Most of the text usage seems to be talking about these encodings or 
rules. Just a few seem to be talking about the abstract protocols. I’ve 
changed those few.

Please see if that works for you.

> - "Multiple addresses or "c=" lines MAY be specified on a per media
> description basis”
> 4566 correctly hyphenated “per-media-description basis”. Why were the hyphens removed here?

I see the same text in both for this. OTOH we are using "per-media" in 
the same section. This led me to investigate the use of "media-level" 
vs. "media level" and "session-level" vs. "session-level". It turned out 
to be a mess. So I have attempted to regularize the usage throughout. I 
now use "session level" and "media level" when referring to levels, and 
using "media-level" and "session-level" when the usage is as an adjective.

Let me know what you think.

> §5.8: "A prefix "X-" is defined for <bwtype> names. This is intended for
> experimental purposes only.”
> 
> Please consider active voice for “is defined”, since in this case it obscures the fact that this was defined by an earlier version of the spec. Would it make sense to say that previous versions defined it, but it is now deprecated?

I revised to indicate this came from 4566.

The text already says NOT RECOMMENDED which is pretty much the same as 
deprecated and is normative. I considered saying both in that sentence 
but it seemed peculiar.

> §5.9: "A "t=" line (time-field) initiates a time description that specifies
> the start and stop times for a session.”
> 
> I don't understand what it means to "intitiate" a time description. The text from 4566 seemed more clear.

I changed "initiate" to "begins".

There has been a lot of confusion and questions raised bout how t=/r=/z= 
work together. I revised the ABNF to clarify that, and then reworked 
this text to be consistent with and coordinate with the ABNF.

> §5.13: "(Attribute scopes in addition to media- and
> session- specific may also be defined”
> Should “specific” be “level”?

Yes. Done.

> §5.14:
> 
> - "If noncontiguous
> ports are required, they must be signaled using a
> separate attribute. (There is currently no attribute defined that
> can accomplish this. The "a=rtcp:" defined in [RFC3605] does not
> handle hierarchical encoding.)”
> 
>   This is oddly stated. Is the point that, if non-contiguous ports are needed, someone will have to specify a new attribute?

I rewrote this to make it clearer.

> - "This implies that, unlike
> limited past practice, there is no implicit grouping defined by
> such means and an explicit grouping framework”
> 
> This does considerably more than “imply” it. It states it explicitly. Perhaps “This means that, unlike…”?

I rewrote the paragraph. Hopefully it is better.

> §6.7: "At most one of recvonly/sendrecv/sendonly/inactive MAY appear at
> session level”
> Consider something like "occurrence of recvonly, sendrecv, sendonly, or inactive”. (Please don’t use slashes to substitute for conjunctions.)

Done.

> §6.7.1: "(e.g., an RTP-based system in
> recvonly mode SHOULD still send RTCP packets”
> Please don’t use normative keywords in examples. Examples should never be normative.

Done.

> §11: It seems a shame to completely drop the acknowledgements from 4566, since the fact that this will obsolete it means people should no longer need to read it. I recognize that those acknowledgements do not apply to _this_ draft, but one could always include a paragraph of the form of “RFC 4566 also acknowledged…"

I went back and gathered and acknowledged all the people who authored or 
were acknowledged in any of the documents obsoleted by this one or 4566.

Can you think of anyone else who should be acknowledged?

	Thanks,
	Paul



From nobody Mon Feb 25 05:23:13 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 5C9FB130EED for <mmusic@ietfa.amsl.com>; Mon, 25 Feb 2019 05:23:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=XYmbg9UU; dkim=pass (1024-bit key) header.d=ericsson.com header.b=Rnyi7tVE
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 jwi9lgR3xtJB for <mmusic@ietfa.amsl.com>; Mon, 25 Feb 2019 05:23:10 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 75A23128CB7 for <mmusic@ietf.org>; Mon, 25 Feb 2019 05:23:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/relaxed;  q=dns/txt; i=@ericsson.com; t=1551100987; x=1553692987; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=yE5htWkzQaCY5I/15ZbCnCVDxr1xQEtM3Ls46UcrBRw=; b=XYmbg9UUQXr2PPghfJyXG2FFnvGhP6hc5N7aCFG9kLHb1Wp3SbnoE5+7qKD25lHk XovCTT5W1qTQrYYHcUTXzRfsRAP99l/gvaDbaHS82YTTxFZedBuYyy/5Zz7g7OdP KBsyWxKVXq6jkdWjLy7dlbTV+/2lz7o17B2kMqYpTZY=;
X-AuditID: c1b4fb2d-2198b9e00000062f-66-5c73ec3bcc15
Received: from ESESSMB501.ericsson.se (Unknown_Domain [153.88.183.119]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id FD.47.01583.B3CE37C5; Mon, 25 Feb 2019 14:23:07 +0100 (CET)
Received: from ESESBMB504.ericsson.se (153.88.183.171) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Mon, 25 Feb 2019 14:23:05 +0100
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (153.88.183.157) by ESESBMB504.ericsson.se (153.88.183.171) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Mon, 25 Feb 2019 14:23:05 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yE5htWkzQaCY5I/15ZbCnCVDxr1xQEtM3Ls46UcrBRw=; b=Rnyi7tVEZGP/arjh33su0ITCHNRbmkVYo6vkPc1r203ILfVSoS1jGEXOfOU80mcPurosx7m8XOCuKZ7YboMUhkHKfdiwTLqrAql88xlV70uX9P/xtJAt6k0Q83XcLuBTGwqP6RIHhqnvOCe78Ojltn7Xkg1/SjKoIwHCdnbUNa4=
Received: from HE1PR07MB3259.eurprd07.prod.outlook.com (10.170.246.26) by HE1PR07MB4220.eurprd07.prod.outlook.com (20.176.166.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.5; Mon, 25 Feb 2019 13:23:04 +0000
Received: from HE1PR07MB3259.eurprd07.prod.outlook.com ([fe80::31df:749d:121a:93f3]) by HE1PR07MB3259.eurprd07.prod.outlook.com ([fe80::31df:749d:121a:93f3%4]) with mapi id 15.20.1665.012; Mon, 25 Feb 2019 13:23:04 +0000
From: Bo Burman <bo.burman@ericsson.com>
To: Martin Thomson <mt@lowentropy.net>, mmusic <mmusic@ietf.org>
CC: "draft-ietf-mmusic-sdp-uks@ietf.org" <draft-ietf-mmusic-sdp-uks@ietf.org>
Thread-Topic: [MMUSIC] WGLC on draft-ietf-mmusic-sdp-uks-03
Thread-Index: AQHUppKYzbL9IIoclE+lDKCXhZBCwqW6bOuAgDZNm5A=
Date: Mon, 25 Feb 2019 13:23:04 +0000
Message-ID: <HE1PR07MB3259FFC36B8E84EA647982728D7A0@HE1PR07MB3259.eurprd07.prod.outlook.com>
References: <ec74675d-c576-f728-0481-c9488fb13beb@cisco.com> <DB7PR07MB4988216B696D0E69ED14D5F095820@DB7PR07MB4988.eurprd07.prod.outlook.com> <1547691891.367836.1636707376.1C1427EE@webmail.messagingengine.com> <AM0PR07MB5793531D0F31BCDBEF95CE8695830@AM0PR07MB5793.eurprd07.prod.outlook.com> <1548111599.1648805.1640352152.40952394@webmail.messagingengine.com>
In-Reply-To: <1548111599.1648805.1640352152.40952394@webmail.messagingengine.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=bo.burman@ericsson.com; 
x-originating-ip: [79.138.87.202]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 53b4f21f-b99f-4ebd-4622-08d69b245f8b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600110)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:HE1PR07MB4220; 
x-ms-traffictypediagnostic: HE1PR07MB4220:
x-ms-exchange-purlcount: 3
x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; HE1PR07MB4220; 23:ZdQ3Letq7RH3DWBFZZxMfCgnKcC00WxVckXTS+Ndu?= =?us-ascii?Q?CCD4WtSc5znOs9WPUv1uRXXo7kp78jZifIW+wTsEyLUxE1htQVckZOwJDzCq?= =?us-ascii?Q?mqUZJOBaRsU05j2dgcjY6JZkiHScMMcqlBLOU+Hc2PmQ3M4bOemQXaNRfQXQ?= =?us-ascii?Q?D9g9b2hRZ/Lm6mHSBrHImaRqjknZr8XneDISOoB9mux4UcTAejsd4xnTB84T?= =?us-ascii?Q?GQZfdloFb3qgwO0+9w8+p5B0Pu594sbrPrvIumJqazURP9ooEgNkUNF0PKzu?= =?us-ascii?Q?Cn5CD3/h8kzVj1S1ByA+5DwkzP06Gv0ER/G5+8LO8PmGgs0pwlZ4EKvsEwvF?= =?us-ascii?Q?mKSQKo9qRoGljlsxiWbxYZt8npeUW9lqAqiawAE4Od5ZdXhpuDeDLWuObQ8s?= =?us-ascii?Q?PDoGd9dTgJyJN+XaCUwrPyfw4DxiL0iHwwLrIpfN643YolFkcCqCOqcbEiPz?= =?us-ascii?Q?hF5amUBrHJXpnnmqvWiOOdrKrNa6QXM1U9XNQQmU0l7+Of1RUXHEJ01GDv5s?= =?us-ascii?Q?3camRC6PcygMRFtPEXEyooKYLeUs8Wgv/UbKqGhkXLle8JH5H4/ZTq7LOECo?= =?us-ascii?Q?GETlj9629lqoP2sMwTYAe/KXt+4w6bCAqLs7S4m8cSm2vTYswAPr6zaC40/E?= =?us-ascii?Q?rP03ucw7cruCiiH/Nbg37geKAd1njdbOlUJuHz4uiosjNFMb0gwNKdD87nJF?= =?us-ascii?Q?UUBZnMu5l+XrPJtM6Rx9TEzPAgfb3KFtxquPEJHcuU5pwTysq/SeEU4zYYiB?= =?us-ascii?Q?kT+qMp939ILhHF3x766WxOLSIeAm5reyOLDImO8oRfu+FXO5AMoPUrtPEQ0V?= =?us-ascii?Q?u9giBN+jL+Zgi9By7ghw3dJ1bDal5qvV8jl2bWEbXldvpvnfqh8dAcgoNW8X?= =?us-ascii?Q?yWp5x5SN7TVX1IsZ9e0AIMDYwiGzygGdjT3aOmKK4lebbGSSRfo0fWLofumk?= =?us-ascii?Q?ohnY8egvKJ6+8E56ffEoVhfdoKiaFgxm/TQjrSipyEr7P3vrM6d24Y+GjCqY?= =?us-ascii?Q?Gl4GkjrsezUGi7bIa0ehLVZxavlf2buatUi0VGFtlcyLJm5zNl3HIz/+Z/Fu?= =?us-ascii?Q?tVrobJtObRntilKD9wO9wBMzZUZKQxLKbogtNPJGOhr28yf39g5sLTSpPVzf?= =?us-ascii?Q?QYrkuf3E3hcUFLO7rTdQeHIWFpECFggIH/Ycpi50XszaPJCS42ditpfL0g23?= =?us-ascii?Q?41VNk7vOV4YFmfxUzKATsoEU+BQ7qhkOGPjXgj2cpyCkLqY7ydw6IKNgzXyp?= =?us-ascii?Q?hMb64iBOqzYwlQQHoY2MztV6XH7yGhrreNe/I3kWzh/XSVyZoWALmluPPixr?= =?us-ascii?Q?iqqyRrra9pQS4QgoNerYAzkrtLJ+P4/JNOIlmqr+wbTetcbEeuBOlfKczmFd?= =?us-ascii?Q?7pfjw=3D=3D?=
x-microsoft-antispam-prvs: <HE1PR07MB4220F912BED1FBB914B981CB8D7A0@HE1PR07MB4220.eurprd07.prod.outlook.com>
x-forefront-prvs: 095972DF2F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(136003)(376002)(396003)(366004)(39860400002)(51914003)(189003)(199004)(13464003)(8676002)(186003)(81156014)(81166006)(8936002)(486006)(305945005)(7736002)(7696005)(966005)(66066001)(93886005)(102836004)(74316002)(53936002)(33656002)(76176011)(478600001)(44832011)(26005)(11346002)(476003)(446003)(6506007)(106356001)(105586002)(97736004)(14454004)(68736007)(53546011)(25786009)(14444005)(6246003)(86362001)(6306002)(9686003)(99286004)(2906002)(5660300002)(4326008)(229853002)(316002)(256004)(6436002)(71190400001)(71200400001)(3846002)(52536013)(110136005)(6116002)(55016002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB4220; 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: CyiA4mFD4gzg/kWGDTP4Dbu87FlOS6MX2eNeMULkjQpwKvU4ibEjC1lEtA83ER0H216wJhHrvpw3v3aqS5iBwKnxJ6a9JH0aoGAw63k3J3wo0UpR+t8BBang7wRxsjNX5zr4pQy9vZVjOayzBMl4PsrF+HKPf9tdZNUOQ5epMDhu7+9B7lMfRiOireASywgD4eK2o7bHCchFUog9mOSiVNgQGSqOfWaNdkhZJrs2ZVa6q9POwsEdQI5EcrxEmehFAlPk4JVWkxrYd4ETFrQMSeovRbSmLMarwQfzBz1U9RS1EkDNWqhUTfNxIacuUY4SmutGPHxdF4ZizfsG2e94VXm/Tz4UnA31ln3oy+0yJDpwFp+ugNAD1tyP934Z24CDtWn+C8g2YlqGEWcTx9zWR6Kex23ar/pqe3EFg1i6d38=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 53b4f21f-b99f-4ebd-4622-08d69b245f8b
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Feb 2019 13:23:04.1873 (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-Transport-CrossTenantHeadersStamped: HE1PR07MB4220
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjleLIzCtJLcpLzFFi42KZGbG9XNf6TXGMweIpehbvPnSwW0xd/pjF YufZ2UwOzB5Llvxk8lj3ch17AFMUl01Kak5mWWqRvl0CV8ahjfdZC14rV6xvusvYwDhRtouR k0NCwETi2tSHLF2MXBxCAkcYJS5NfsoE4XxjlFjZ+J4dwlnCJDGncz5YhkVgArPEybf7mCEy k5kkln6eADXgEaPEwm+N7CCT2QQ0JObvuMsIYosIOEhcP76dDcRmFvCV6Hs3BaxGWMBK4uyW iawQNdYSs9ZMhqq3knjV3sEMYrMIqEr0dn0Fq+cViJE4u28l1LL3TBLn/zwGS3AKBEq8PtzC AmIzCshK3P9+jwVimbjErScgd4O8KiCxZM95ZghbVOLl43+sEPWREpMnnmWHiCtKXNt4ixHC lpW4NL8byvaVeHXgKDgwJARuMkrc2H+VBSKhJXGivx3KlpJYeP4LVNE+PonjO/5BJbIlrvx+ CbVBRuLTxjVsEEVNbBKfr61imcCoNwvJtRC2jsSC3Z/YIGxtiWULXzPPAgeBoMTJmU9YFjCy rGIULU4tLs5NNzLWSy3KTC4uzs/Ty0st2cQITCUHt/zW3cG4+rXjIUYBDkYlHt6sC8UxQqyJ ZcWVuYcYJTiYlUR4TS4ChXhTEiurUovy44tKc1KLDzFKc7AoifP+ERKMERJITyxJzU5NLUgt gskycXBKNTBOq/tc2L7M8j13mvApiSnGov1bL5SoX4lZtrFFTUVbd59ok/PBtLqVh5qEP32t ecqkp9E83eqygf2at6a9tTM2qTKZKJnkpZd4ugRMUPwpfavqwtsjKrb3anlEWG/XFUm0xT+5 fP1FZbCySqRSh/XL/Obdi648F/xieMQ2t0v5jjrbBe01EUosxRmJhlrMRcWJAPC9r8UhAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/4SyZZ8D6G3dMIIQiF3xhRKzpHM8>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sdp-uks-03
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, 25 Feb 2019 13:23:12 -0000

Hi Martin,

I've now also reviewed this and have a set of comments and questions, after=
 taking Magnus' comments and your suggested edits in response to that into =
account:

Section 2.1:
* In bullet 2, "complete communications" is slightly unclear (more so if "c=
omplete" is used in other contexts further down in the text). Do you with "=
complete" mean "accept", or perhaps "accept setting up"?

* Don't understand what is meant with "...second condition..."; is it bulle=
t #2, or is it referring to "...joining two separate sessions"?

* Also don't really understand in what way that second condition is "not ne=
cessary"; to limit the attacker capabilities (related to bullet #2), for th=
e attacker to join two sessions, or something else like "for the attack to =
succeed"?

* Just to confirm, does "removing this constraint" refer to removing use of=
 an identity binding?

Section 3:
* Is the "victim" of the first paragraph the same or another victim compare=
d to the one mentioned in the next paragraph?

* Is "another entity of the attacker's choice" also to be considered a vict=
im?

* The last paragraph in section 3, just before section 3.1 "The same techni=
que..." seems a bit misplaced, after text talking about a solution. Should =
it perhaps be moved just before the paragraph "The problem..." in section 3=
? Or, is this "same technique" referring to what is described in section 4?

Section 4:
* First sentence, "similar attack"; similar to what?

Section 4.1:
* Believe it would be helpful for the reader to better understand why "Mall=
ory has no real interest in seeing that session complete"

* Same sentence, does "session complete" mean "session setup complete"? I f=
irst interpreted "complete" as "conclude" in the meaning "terminate".

* Same paragraph, should "call completion" be "call setup completion", and =
"session completes" be "session setup completes"?

* Same paragraph, "will likely be discarded by Patsy"; believe it would be =
helpful to say why.

Section 4.2:
* I believe the first paragraph ("An attack on... ...vulnerable to attack."=
) would also be helpful as first text of section 4. Move? Copy?

* "Validating that peers..." -> "Successful validation that peers..."?

Section 4.3:
* "When used with SDP, the value includes..." -> "When used with SDP, the v=
alue MUST consist of..."?

Section 5:
* "Use of the "external_session_id"
   does not guarantee that the identity of the peer at the TLS layer is
   the same as the identity of the signaling peer"; sounds a bit strange - =
isn't this what the draft is supposed to solve? Is "... when used with sess=
ion concatenation" meant?=20

* "Similarly, data from one TLS connection..."; I assume "data" means "secu=
rity-related information", not "user data" (TLS payload)?

Nits:

Section 2.2:
* geniune -> genuine

Section 4:
* "believe that is calling" -> "believe that it is calling"

Section 4.1:
* "also needs to the ability" -> "also needs the ability"
* "ostensibly between Mallory and Norma, is complete.  Mallory begins forwa=
rding DTLS" -> "ostensibly between Mallory and Norma, Mallory begins forwar=
ding DTLS"
* "These packets denoted" -> "These packets are denoted"

Section 5:
* concatention -> concatenation

Cheers,
Bo (as individual)

-----Original Message-----
From: mmusic <mmusic-bounces@ietf.org> On Behalf Of Martin Thomson
Sent: den 22 januari 2019 00:00
To: Magnus Westerlund <magnus.westerlund@ericsson.com>; Flemming Andreasen =
<fandreas@cisco.com>; mmusic <mmusic@ietf.org>
Cc: draft-ietf-mmusic-sdp-uks@ietf.org
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sdp-uks-03

On Thu, Jan 17, 2019, at 19:50, Magnus Westerlund wrote:
> Hi Martin,
>=20
> Thanks for the pull request. I have detailed inline comments, but I=20
> think the pull request do address my issues.

Thanks again Magnus.

I made a few tweaks regarding canonicalization (or lack thereof) and merged=
 the PR.  I'll await the end of the WGLC and the chairs' instruction before=
 publishing again, but there's a preview here:

https://martinthomson.github.io/sdp-uks/draft-ietf-mmusic-sdp-uks.html

> Although I didn't read all the sections in 7, I do agree that security=20
> arch appear to need some clarification so that what you write is clear.

FWIW, https://github.com/rtcweb-wg/security-arch/pull/84 attempts to fix th=
at.

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


From nobody Mon Feb 25 15:03:07 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 642131277D2; Mon, 25 Feb 2019 15:03:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xUHYxP5H7GSl; Mon, 25 Feb 2019 15:03:01 -0800 (PST)
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 58A9513115A; Mon, 25 Feb 2019 15:03:01 -0800 (PST)
Received: from [81.187.2.149] (port=34670 helo=[192.168.0.78]) 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 1gyPGv-0000FX-5x; Mon, 25 Feb 2019 23:02:57 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <2f297a3c-39d4-cb99-65f4-f0bcd072306a@alum.mit.edu>
Date: Mon, 25 Feb 2019 23:02:41 +0000
Cc: Ben Campbell <ben@nostrum.com>, draft-ietf-mmusic-rfc4566bis.all@ietf.org,  mmusic WG <mmusic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C054EF10-FE82-4E9D-9ABA-5C2E6090F0C9@csperkins.org>
References: <04CAFF8C-B6ED-4B7D-9FDD-ED37DCA2848B@nostrum.com> <2f297a3c-39d4-cb99-65f4-f0bcd072306a@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/RIxWM3uSPkeBPNNps2FQIfVBhPo>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rfc4566bis-32
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, 25 Feb 2019 23:03:05 -0000

Paul, Ben,

(inline)

> On 22 Feb 2019, at 20:58, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
> Ben,
>=20
> I just submitted -33. It attempts to address most, but not all, of =
your comments. See my detailed replies below. I need help for some of =
the remainder, specifically security considerations.
>=20
> There will need to be another revision to address the remaining items.
>=20
> 	Thanks,
> 	Paul
>=20
> On 2/11/19 10:45 PM, Ben Campbell wrote:
>> Hi,
>> This is my AD evaluation of draft-ietf-mmusic-rfc4566bis-32. I have =
several minor substantive comments, and a number of editorial comments =
and nits. I=E2=80=99d like to resolve at least the substantive comments =
prior to IETF last call.
>> Thanks!
>> Ben.
>> ----------------------
>> *** Substantive Comments ***
>> =C2=A71, last paragraph: The statement that this update is limited to =
essential corrections is demonstrably untrue. For example, this version =
changes a lot of spellings from British English to US English. While =
that might be best for the sake of consistency, it would be hard to =
argue that it is _essential_.
>=20
> I removed this claim.
>=20
>> Along the same lines, =C2=A710 does not seem to capture all material =
changes.
>=20
> I've tried to summarize all the important changes.
>=20
>> =C2=A72, =E2=80=9CMedia Description=E2=80=9D: While true, the text =
here is not a definition of anything but syntax. Please add a sentence =
or two to say what the media description semantically represents.
>=20
> I've added my attempt at describing the semantics. (I posted a query =
about this but didn't get a response that seemed to work.
>=20
> Please comment if you want a further change.
>=20
>> - Deleted text formerly in =C2=A74.3: The removal of the =E2=80=9Cpriva=
te sessions=E2=80=9D section in its entirety deserves some explanatory =
text.
>=20
> I posted a query about this. The consensus was that the removal here =
is right, but that more discussion is needed in the Security =
Considerations section. But I don't know what to write. I need some help =
on that.

The former =C2=A74.3 just said two things. The first was that if you =
want to keep the SDP session description private, then you need =
encryption to protect for distribution. That seems obvious, but I guess =
a statement to that effect could be added to the security considerations =
(=E2=80=9CIf it=E2=80=99s desired to keep a session description =
confidential, then confidentiality protection SHOULD be used=E2=80=9D). =
It also said that a private session description can be used to convey =
encryption keys. I=E2=80=99m not sure that=E2=80=99s something we want =
to encourage.



=C2=A75 has several changes to normative language. Most are okay, but I =
think the change from =E2=80=9Call MUST appear in exactly the order =
given here=E2=80=9D to =E2=80=9Call must appear=E2=80=9D weakens it too =
much, and I=E2=80=99d prefer that to remain a MUST.

>> =C2=A75.2: "Unless an SDP extension for NAT traversal is used
>> (e.g., ICE [RFC8445], ICE TCP [RFC6544]), a local IP address MUST
>> NOT be used in any context where the SDP description might leave
>> the scope in which the address is meaningful=E2=80=9D
>> That doesn=E2=80=99t apply to just any NAT traversal extension does =
it? It seems to require extensions that have scope-resolution properties =
similar to those of ICE.
>=20
> After reading 5.2 again I realized it is talking about an address in =
an o=3D line, not c=3D. Hence there is no intent that anybody connect to =
this, and ICE doesn't apply here. The address is primarily here to add =
to the uniqueness of the o=3D line. And note that the <sess-id> is =
required to make up any lack of uniqueness in the combination of the =
other fields. And privacy is leading to people not wanting to put real =
addresses or names in here.
>=20
> So I removed all the discussion of ICE.
>=20
> Please comment if you think this isn't sufficient or appropriate.
>=20
>> =C2=A75.8: "Use of the "X-" prefix is NOT RECOMMENDED: instead new =
(non "X-"
>> prefix) <bwtype> names SHOULD be defined, and then MUST be registered
>> with IANA in the standard namespace.=E2=80=9D
>> =E2=80=9CSHOULD be defined=E2=80=9D seems to be in tension with =
=E2=80=9CMUST be registered=E2=80=9D.
>=20
> I twiddled with this. Does it work for you now?
>=20
>> =C2=A75.13: "The "k=3D" line (key-field) is obsolete and MUST NOT be =
used.=E2=80=9D
>> Should it be removed from the field order definition in =C2=A75?
>=20
> It continues to be mentioned because implementations may need to =
support it for backward compatibility with 4566. In that case they need =
to know where it goes.
>=20
> I left this unchanged.
>=20
>> =C2=A76.1: Please state what behavior is meant by =E2=80=9CThis =
attribute is obsoleted=E2=80=9D. For example, MUST not send but SHOULD =
accept? Something different? (This pattern occurs for multiple =
attributes.)
>=20
> I beefed up the language for this.
>=20
>> =C2=A76.7.4: "Note that an RTP-based system MUST still send RTCP (if =
RTCP
>> is used), even if started inactive.=E2=80=9D
>> Other similar attributes use SHOULD instead of MUST. Is the =
inconsistency intentional?
>=20
> I brought this to the list. The feedback I got was that is change is =
correct.

Agree.

>> =C2=A77, last paragraph:
>> What is the impact of this on RFC 4568 (security descriptions)? That =
RFC seems to allow the use of =E2=80=9Ck=3D=E2=80=9C lines at a MAY =
level. Does this draft need to update that? But more importantly, is it =
worth distinguishing the case of E@E protection of keying material vs =
the HBH protection offered by security descriptions?
>=20
> This text is unchanged since 4566.
>=20
> I need help with this from a security person.

SDP security descriptions has problems, but I=E2=80=99d argue that those =
should be addressed in an RFC updating RFC 4568, or moving it to =
historic, rather than in the base SDP specification. Is this not =
something SIPBRANDY will be producing?

>> =C2=A78 and subsectionsl:
>> I think there needs to be more clarity about what this draft defines =
vs what was defined in previous versions, and what has changed. For =
example, language to the effect of "XXX was originally defined in RFC =
4566. This document requests IANA to change the reference to =
=E2=80=9CRFC-this=E2=80=9D.=E2=80=9D
>=20
> Done.
>=20
>> =C2=A78.2: "The contact address for all parameters registered below =
is:
>> IETF MMUSIC working group <mmusic@ietf.org>=E2=80=9D
>> Please consider =E2=80=9CThe IETF MMUSIC working group =
<mmusic@ietf.org> or its successor as designated by the IESG.=E2=80=9D
>=20
> Done.
>=20
>> =C2=A78.2.1: "Until that is done, applications SHOULD NOT use these
>> types and SHOULD NOT declare support for them in SIP capabilities
>> declarations (even though they exist in the registry created by
>> [RFC3840]).=E2=80=9D
>> Should this spec update 3840?
>=20
> Leaving 3840 as-is doesn't hurt anything. As long as these aren't used =
in m-lines then usage in 3840/3841 will be moot.
>=20
> I left this as-is.
>=20
>> =C2=A78.2.4.2: This section needs some guidance about the maturity of =
specs needed to update attributes defined in previous specs. While the =
registration policy is =E2=80=9Cspec required=E2=80=9D, what happens if =
someone defines FOO in a standards-track RFC, and someone else wants to =
update it with some lower-maturity instrument?
>=20
>> Along the same line, is there any restriction from party B updating =
an attribute defined by party A without consent? That is clear for IETF =
stream RFCs where the IETF retains change control, but might not be =
clear for other specification forms.
>=20
> Specification Required calls for a designated expert to review the =
registration. I revised the language to ask the expert to consider these =
issues.
>=20
>> =C2=A78.2.8: Are telephone numbers still necessary? Under GDPR rules, =
we should be careful about requiring data unless there is a clear need =
for it.
>=20
> I removed the requirement for a phone number. (This makes it =
consistent with the template for attribute registrations that already =
didn't ask for a phone number.)
>=20
>> *** Editorial Comments and Nits ***
>> =C2=A73.3, 2nd paragraph: "Note that descriptions of multicast =
sessions made only via email or=E2=80=A6=E2=80=9D
>> The sentence no longer makes sense with the change from =
=E2=80=9Cannouncement=E2=80=9D to =E2=80=9Cdescription=E2=80=9D. If you =
want to avoid the term =E2=80=9Cannouncements=E2=80=9D, consider =
something like =E2=80=9C=E2=80=A6 descriptions of multicast sessions =
sent only via email=E2=80=A6=E2=80=9D
>=20
> Done.
>=20
>> =C2=A74.1: "This address and port is the destination address and =
destination port=E2=80=9D: Plural disagreement. (It was correct in =
4566.)
>=20
> Fixed.
>=20
>> =C2=A75:
>> - =E2=80=9C=E2=80=A6 the end of the whole session description - =
whichever=E2=80=A6=E2=80=9D: A dash usually separates two independent =
clauses, much like a semicolon. That is not the cast here; a comma would =
be more appropriate.
>=20
> Done
>=20
>> - "Some lines in each description are REQUIRED and some are =
OPTIONAL,=E2=80=9D : While I recognize these are unchanged from 4566, =
the REQUIRED and OPTIONAL terms seem like statements of fact rather than =
normative statements.
>=20
> I cleaned this up and made it explicit that the ABNF is normative and =
this section is only a summary of the ABNF.
>=20
>> - "media-, or session-specific basis=E2=80=9D : Incorrect comma =
usage.
>=20
> IIUC this is an "Oxford comma", and the use of it is controversial. =
Does IETF have a policy on its use?
>=20
> (Or we can leave it for the editor to decide.)
>=20
> I've left this unchanged for now.
>=20
>> - "An SDP description may contain URIs=E2=80=9D
>>  I'm not sure this change makes sense. Should it say ''session =
description=E2=80=9D?
>=20
> After investigating further, I realized that =E2=80=9Csession =
description=E2=80=9D and =E2=80=9CSDP description=E2=80=9D are used =
synonymously through the document. So this change isn=E2=80=99t *wrong*. =
IIRC I did it to be consistent with the other usage of "SDP description" =
in the vicinity of this.
>=20
> I suspect that =E2=80=9Csession description=E2=80=9D might have been =
considered an abstract concept, with an "SDP description" being a =
specific realization of that. But the document doesn=E2=80=99t really =
make this distinction. And =E2=80=9CSDP description=E2=80=9D is =
redundant (Session Description Protocol description).
>=20
> So perhaps every occurrence of =E2=80=9CSDP description=E2=80=9D =
should be changed to =E2=80=9CSession Description=E2=80=9D. Alternately, =
we could change every occurrence of "Session Description" to "SDP =
description".
>=20
> For now I have left things as-is.
>=20
>> - "Text containing fields such as the session-name-field and
>> information-field=E2=80=9D:
>> This is ambiguous. Are we talking about text that contains fields, or =
text-containing fields? =46rom context, I assume the latter.
>=20
> Done.
>=20
>> =C2=A75.5: "The "u=3D" line (uri-field) provides URI (Uniform =
Resource Identifier)
>> as used by WWW clients=E2=80=9D
>> Missing article before URI
>=20
> Done.
>=20
>> =C2=A75.7:
>> - "The "c=3D" line (connection-field) contains connection data.=E2=80=9D=

>> The section heading was changed from =E2=80=9Cconnection data=E2=80=9D =
to =E2=80=9Cconnection information=E2=80=9D. Should that change apply =
here, too?
>=20
> That seems pretty circular. Instead I changed it to:
>=20
> "The "c=3D" line (connection-field) contains information necessary to =
establish a connection.=E2=80=9D
>=20
>> - There are a number of places in this section (and maybe elsewhere) =
where IPv6 was changed to IP6. While I realize 4566 was inconsistent on =
this, wouldn=E2=80=99t it make more sense to change to consistently use =
the more conventional =E2=80=9CIPv6=E2=80=9D?  (Probably also true for =
IP4/IPv4).
>=20
> This turns out to be tricky: "IP4" and "IP6" are the encodings used in =
the m-line. They are also used in the names of ABNF rules such as =
"IP4-address" and "IP4-multicast".
>=20
> Most of the text usage seems to be talking about these encodings or =
rules. Just a few seem to be talking about the abstract protocols. =
I=E2=80=99ve changed those few.
>=20
> Please see if that works for you.
>=20
>> - "Multiple addresses or "c=3D" lines MAY be specified on a per media
>> description basis=E2=80=9D
>> 4566 correctly hyphenated =E2=80=9Cper-media-description basis=E2=80=9D=
. Why were the hyphens removed here?
>=20
> I see the same text in both for this. OTOH we are using "per-media" in =
the same section. This led me to investigate the use of "media-level" =
vs. "media level" and "session-level" vs. "session-level". It turned out =
to be a mess. So I have attempted to regularize the usage throughout. I =
now use "session level" and "media level" when referring to levels, and =
using "media-level" and "session-level" when the usage is as an =
adjective.
>=20
> Let me know what you think.
>=20
>> =C2=A75.8: "A prefix "X-" is defined for <bwtype> names. This is =
intended for
>> experimental purposes only.=E2=80=9D
>> Please consider active voice for =E2=80=9Cis defined=E2=80=9D, since =
in this case it obscures the fact that this was defined by an earlier =
version of the spec. Would it make sense to say that previous versions =
defined it, but it is now deprecated?
>=20
> I revised to indicate this came from 4566.
>=20
> The text already says NOT RECOMMENDED which is pretty much the same as =
deprecated and is normative. I considered saying both in that sentence =
but it seemed peculiar.
>=20
>> =C2=A75.9: "A "t=3D" line (time-field) initiates a time description =
that specifies
>> the start and stop times for a session.=E2=80=9D
>> I don't understand what it means to "intitiate" a time description. =
The text from 4566 seemed more clear.
>=20
> I changed "initiate" to "begins".
>=20
> There has been a lot of confusion and questions raised bout how =
t=3D/r=3D/z=3D work together. I revised the ABNF to clarify that, and =
then reworked this text to be consistent with and coordinate with the =
ABNF.
>=20
>> =C2=A75.13: "(Attribute scopes in addition to media- and
>> session- specific may also be defined=E2=80=9D
>> Should =E2=80=9Cspecific=E2=80=9D be =E2=80=9Clevel=E2=80=9D?
>=20
> Yes. Done.
>=20
>> =C2=A75.14:
>> - "If noncontiguous
>> ports are required, they must be signaled using a
>> separate attribute. (There is currently no attribute defined that
>> can accomplish this. The "a=3Drtcp:" defined in [RFC3605] does not
>> handle hierarchical encoding.)=E2=80=9D
>>  This is oddly stated. Is the point that, if non-contiguous ports are =
needed, someone will have to specify a new attribute?
>=20
> I rewrote this to make it clearer.
>=20
>> - "This implies that, unlike
>> limited past practice, there is no implicit grouping defined by
>> such means and an explicit grouping framework=E2=80=9D
>> This does considerably more than =E2=80=9Cimply=E2=80=9D it. It =
states it explicitly. Perhaps =E2=80=9CThis means that, unlike=E2=80=A6=E2=
=80=9D?
>=20
> I rewrote the paragraph. Hopefully it is better.
>=20
>> =C2=A76.7: "At most one of recvonly/sendrecv/sendonly/inactive MAY =
appear at
>> session level=E2=80=9D
>> Consider something like "occurrence of recvonly, sendrecv, sendonly, =
or inactive=E2=80=9D. (Please don=E2=80=99t use slashes to substitute =
for conjunctions.)
>=20
> Done.
>=20
>> =C2=A76.7.1: "(e.g., an RTP-based system in
>> recvonly mode SHOULD still send RTCP packets=E2=80=9D
>> Please don=E2=80=99t use normative keywords in examples. Examples =
should never be normative.
>=20
> Done.

This is a normative requirement of RTP, however. If we want to avoid =
normative examples, which I=E2=80=99d agree makes sense, then this needs =
to be rewritten as just =E2=80=9CAn RTP-based system in recvonly mode =
SHOULD=E2=80=A6=E2=80=9D.


>> =C2=A711: It seems a shame to completely drop the acknowledgements =
from 4566, since the fact that this will obsolete it means people should =
no longer need to read it. I recognize that those acknowledgements do =
not apply to _this_ draft, but one could always include a paragraph of =
the form of =E2=80=9CRFC 4566 also acknowledged=E2=80=A6"
>=20
> I went back and gathered and acknowledged all the people who authored =
or were acknowledged in any of the documents obsoleted by this one or =
4566.
>=20
> Can you think of anyone else who should be acknowledged?
>=20
> 	Thanks,
> 	Paul
>=20
>=20



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





From nobody Mon Feb 25 20:45:39 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 E260F130E6B; Mon, 25 Feb 2019 20:45:37 -0800 (PST)
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, DKIMWL_WL_MED=-0.001, 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, 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 YXoKwG-L8-3P; Mon, 25 Feb 2019 20:45:36 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7FE0130E6A; Mon, 25 Feb 2019 20:45:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6288; q=dns/txt; s=iport; t=1551156335; x=1552365935; h=subject:from:to:cc:references:message-id:date: mime-version:in-reply-to; bh=mGYNknV0TUEAWr5esR4WmuNZa6bM04xBzjQGF86be5s=; b=RpCnikIMjVUqe3zPKWvAXsD2JKbKK1DYOoWUJ+unLVjijPnPGv/qnXSj x9MdnHQ2Rem+QpQ23ky7UGLDXsNgwN854Gs9ziWNe11wByautm3kEg0MU 305wQ9jF0mfhXWJvXMJu1vKrECPe+PV8S2WYu6oOQpaK3xr0SEYVHBDiL I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAABOw3Rc/5hdJa1bCRkBAQEBAQE?= =?us-ascii?q?BAQEBAQEHAQEBAQEBgVEEAQEBAQELAYIDZ4EDJ4QIiBqNOy2JO4hyhXGBew0?= =?us-ascii?q?YAQqEA0YChAwiNAkNAQMBAQIBAQJtHAyFSwEBAQMBASFLCxALGCoCAicwBgE?= =?us-ascii?q?MBgIBAYMcAYFlDQ+rXIEvH4UlhFYdBYoAgkgXgUA/gREngmuDHgEBgTeDNIJ?= =?us-ascii?q?XApFakgYJkmAGGYFxhVuDHYZwgTqKU5I6gUc4gVZNIxU7gmyLHoVdIQMwAZA?= =?us-ascii?q?8AQE?=
X-IronPort-AV: E=Sophos;i="5.58,414,1544486400";  d="scan'208,217";a="306244856"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Feb 2019 04:45:34 +0000
Received: from [10.118.10.18] (rtp-fandreas-2-881-ap.cisco.com [10.118.10.18]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTP id x1Q4jYHO012740; Tue, 26 Feb 2019 04:45:34 GMT
From: Flemming Andreasen <fandreas@cisco.com>
To: mmusic <mmusic@ietf.org>, Martin Thomson <mt@lowentropy.net>
Cc: draft-ietf-mmusic-sdp-uks@ietf.org
References: <ec74675d-c576-f728-0481-c9488fb13beb@cisco.com>
Message-ID: <ea61540a-20c7-0c3d-1f7d-4d702d9a5332@cisco.com>
Date: Mon, 25 Feb 2019 23:45:34 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <ec74675d-c576-f728-0481-c9488fb13beb@cisco.com>
Content-Type: multipart/alternative; boundary="------------9E99C94BD763AB57A37471CE"
Content-Language: en-US
X-Outbound-SMTP-Client: 10.118.10.18, rtp-fandreas-2-881-ap.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/W361DlK5jnbQsXSOQywKnimc_v0>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sdp-uks-03
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, 26 Feb 2019 04:45:38 -0000

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

Hi Martin

I also took a closer look at the document and have a few additional 
comments (as individual):

Non-Editorial
=========
Section 2.3, second paragraph:     The description on how 3PCC can work 
with the proposed mechanism is a bit vague. It would be helpful to 
expand it and provide an example.

Section 3, last paragraph:    The text seems out of place here. The text 
implicitly refers to the previous paragraph, which doesn't seem to make 
sense.

Section 3.1, second paragraph: "In the first session, Patsy is presented 
with the option to communicate with Norma"
How is that possible when the signaling originates from Mallory (I 
thought we had signaling integrity and authenticated identity) ?



Editorial
======
Section 2.2, first paragraph: A reference after "key continuity" might 
be helpful.

Section 3.1, first paragraph after Figure 1:
- Old: The attack requires that Mallory obtain an identity binding for 
their own identity
- New: The attack requires that Mallory obtains an identity binding for 
her own identity

Section 3.1, 3rd paragraph after figure 1:
- Old: Patsy correctly believes that they are communicating with Norma. 
However Norma incorrectly believes they are talking to Mallory
- New: Patsy correctly believes that she is communicating with Norma. 
However Norma incorrectly believes she is talking to Mallory

Section 3.2, 4th last paragraph
- Old: in which the extension
- New: in which case the extension

Section 4.1, last paragraph
s/succeed/succeeds

Section 4.3
- Old: a ExternalSessionId
- New: an ExternalSessionId


On 1/7/19 9:08 AM, Flemming Andreasen wrote:
> Greetings MMUSIC
>
> This is to announce a 2 week WGLC on the draft:
>
> https://www.ietf.org/id/draft-ietf-mmusic-sdp-uks-03.txt
>
> as Proposed Standard. Please review and provide any comments you may 
> have on the document by Monday, January 21, 2019. Comments should be 
> sent to the document authors and the MMUSIC WG list. If you review the 
> document but do not have any comments, please send a note to that 
> effect as well.
>
> Thanks
>
> -- Flemming (MMUSIC co-chair)
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


--------------9E99C94BD763AB57A37471CE
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">
    Hi Martin <br>
    <br>
    I also took a closer look at the document and have a few additional
    comments (as individual):<br>
    <br>
    Non-Editorial<br>
    =========<br>
    Section 2.3, second paragraph:     The description on how 3PCC can
    work with the proposed mechanism is a bit vague. It would be helpful
    to expand it and provide an example. <br>
    <br>
    Section 3, last paragraph:    The text seems out of place here. The
    text implicitly refers to the previous paragraph, which doesn't seem
    to make sense. <br>
    <br>
    Section 3.1, second paragraph: "In the first session, Patsy is
    presented with the option to communicate with Norma"<br>
    How is that possible when the signaling originates from Mallory (I
    thought we had signaling integrity and authenticated identity) ? <br>
    <br>
    <br>
    <br>
    Editorial <br>
    ======<br>
    Section 2.2, first paragraph: A reference after "key continuity"
    might be helpful. <br>
    <br>
    Section 3.1, first paragraph after Figure 1:<br>
    - Old: The attack requires that Mallory obtain an identity binding
    for their own identity<br>
    - New: The attack requires that Mallory obtains an identity binding
    for her own identity<br>
    <br>
    Section 3.1, 3rd paragraph after figure 1:<br>
    - Old: Patsy correctly believes that they are communicating with
    Norma. However Norma incorrectly believes they are talking to
    Mallory<br>
    - New: Patsy correctly believes that she is communicating with
    Norma. However Norma incorrectly believes she is talking to Mallory<br>
    <br>
    Section 3.2, 4th last paragraph<br>
    - Old: in which the extension<br>
    - New: in which case the extension<br>
    <br>
    Section 4.1, last paragraph<br>
    s/succeed/succeeds<br>
    <br>
    Section 4.3<br>
    - Old: a ExternalSessionId<br>
    - New: an ExternalSessionId <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 1/7/19 9:08 AM, Flemming Andreasen
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:ec74675d-c576-f728-0481-c9488fb13beb@cisco.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      Greetings MMUSIC <br>
      <br>
      This is to announce a 2 week WGLC on the draft: <br>
      <br>
          <a class="moz-txt-link-freetext"
        href="https://www.ietf.org/id/draft-ietf-mmusic-sdp-uks-03.txt"
        moz-do-not-send="true">https://www.ietf.org/id/draft-ietf-mmusic-sdp-uks-03.txt</a>
      <br>
      <br>
      as Proposed Standard. Please review and provide any comments you
      may have on the document by Monday, January 21, 2019. Comments
      should be sent to the document authors and the MMUSIC WG list. If
      you review the document but do not have any comments, please send
      a note to that effect as well. <br>
      <br>
      Thanks <br>
      <br>
      -- Flemming (MMUSIC co-chair) <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
mmusic mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.org/mailman/listinfo/mmusic</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------9E99C94BD763AB57A37471CE--


From nobody Tue Feb 26 06:29:11 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 28643131170 for <mmusic@ietfa.amsl.com>; Tue, 26 Feb 2019 06:29:06 -0800 (PST)
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, DKIMWL_WL_HIGH=-0.001, 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, 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 CbO9sIeag5vR for <mmusic@ietfa.amsl.com>; Tue, 26 Feb 2019 06:29:03 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 569EC1311C6 for <mmusic@ietf.org>; Tue, 26 Feb 2019 06:29:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2015; q=dns/txt; s=iport; t=1551191342; x=1552400942; h=to:from:subject:message-id:date:mime-version; bh=nM3kiX8QRcq+ZM0zpRUrSRnoExkftyeKr10U8E5yTrI=; b=LB+m4zoszVVd89moUj+Fm3LWIk1jFl70Bozr1b2BbtZ4oe5J6aC7T7Pz EQsRPaciM3+aFJlvslUoFXLElK+4v7T5x9Q6JImpn4ypsHOHa+x8XAoQu 9kuCRME8eYaOHkkb7QpasQ35cO7Jz+aZBfHlKZ7PgiVw1Sj6yeVYtPInt 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DVAQDGTHVc/4MNJK0ZAUodAQEFAQc?= =?us-ascii?q?FAYFUBQELAQGCAoE3ATKEL5N1gWiJYIhyh2wNiHAiNwYNAQMBAQIBAQJtKIV?= =?us-ascii?q?BM3QBPgJfDQgBAYMcgWYNjSGeI4EvH4UlhFAijEgXgUA/gTgMgjGIOYJXApF?= =?us-ascii?q?dkggJkmIGAheKcIgqnRWBXSKBVk0jFYMokHohA5BzAQE?=
X-IronPort-AV: E=Sophos;i="5.58,415,1544486400";  d="scan'208,217";a="514269879"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Feb 2019 14:29:01 +0000
Received: from [10.118.10.18] (rtp-fandreas-2-881-ap.cisco.com [10.118.10.18]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTP id x1QET0Jl012437 for <mmusic@ietf.org>; Tue, 26 Feb 2019 14:29:01 GMT
To: mmusic <mmusic@ietf.org>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <42742461-99ae-50b6-50e7-365fbc2f0edf@cisco.com>
Date: Tue, 26 Feb 2019 09:29:00 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------5DDE1ACC3E716CAE742D1AB9"
Content-Language: en-US
X-Outbound-SMTP-Client: 10.118.10.18, rtp-fandreas-2-881-ap.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/l7A2qtbn-BNZRpF9RQoHN35dVC4>
Subject: [MMUSIC] Cancel MMUSIC Meeting in Prague ?
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, 26 Feb 2019 14:29:10 -0000

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

Greetings MMUSIC

We are currently scheduled to meet for 1 hour in Prague, however we do 
not have any agenda requests at this point. The only two documents that 
are currently undergoing active WG work are
1) ice-sip-sdp, which we expect to be updated shortly following the 
recent consensus call in RTCWeb, and after which we will move to 
Publication Request
2) sdp-uks, which has undergone review in the WG and is also expected to 
be updated shortly, after which we will move to Publication Request.

If we do not hear of any agenda requests by Friday, March 8, then we 
will go ahead and cancel the meeting.

Thanks

     Bo & Flemming (MMUSIC chairs)




--------------5DDE1ACC3E716CAE742D1AB9
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">
    Greetings MMUSIC <br>
    <br>
    We are currently scheduled to meet for 1 hour in Prague, however we
    do not have any agenda requests at this point. The only two
    documents that are currently undergoing active WG work are<br>
    1) ice-sip-sdp, which we expect to be updated shortly following the
    recent consensus call in RTCWeb, and after which we will move to
    Publication Request<br>
    2) sdp-uks, which has undergone review in the WG and is also
    expected to be updated shortly, after which we will move to
    Publication Request. <br>
    <br>
    If we do not hear of any agenda requests by Friday, March 8, then we
    will go ahead and cancel the meeting. <br>
    <br>
    Thanks <br>
    <br>
        Bo &amp; Flemming (MMUSIC chairs)<br>
    <br>
    <br>
    <br>
  </body>
</html>

--------------5DDE1ACC3E716CAE742D1AB9--


From nobody Thu Feb 28 22:03:49 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 397FE1295D8; Thu, 28 Feb 2019 22:03:48 -0800 (PST)
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=VwBUPYQx; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=bf+h2T9y
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 Msvi0ZpPWer1; Thu, 28 Feb 2019 22:03:45 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AFC41311F1; Thu, 28 Feb 2019 22:03:45 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 40CCE3582; Fri,  1 Mar 2019 01:03:44 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Fri, 01 Mar 2019 01:03:44 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=message-id:in-reply-to:references:date:from:to:cc:subject :content-type; s=fm1; bh=U4KT3KXYTXNjUva2Gl/O7K3NfQ+4UxPENa2xa6T eyl4=; b=VwBUPYQxLjjJ5eno9YVW0fo9v6KJr6ZctsBPOoFFrEjGmNd0Up03fAU x8QremN0ChAh+gj75b6XS41uHgEK0IS6FA5X+5OHomJz+e6aCPHcGBwjAqnWNpnk QUBoenhkXluOfmwFh3QzmBNjsu8MiXV2xBOz+poKO3LwI3P9bKNI/rsgeyAVQiYm DAz3H/N947NfQgTzG1y7gMqlLs98rLgcR3zCkypp1rMiV9RDCzGr/lg3ovUda/Er 5qH1ouAPbSW58Zd+jeh82V7fv1cHpDMRgze/NWzGIAqGmstzQ0Q/NmhbLjHcx4Nv aAZDotIlaD0u6QQPiwUoNG00QhcYykQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:references:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=U4KT3KXYTXNjUva2G l/O7K3NfQ+4UxPENa2xa6Teyl4=; b=bf+h2T9y0K6gEZVAmpwdwueHgqiiZVJ7h NpUnUx61AAa+OVdxtKS1x0DA1zr68A5lNGk0IzL1m0vRK6Uq+SL2hIrPm+ZO/aeT WUQ3An1UZiUNGajfM8lqxKL6+JIkuhndCyGx4TJ/odebjs/c5CXRuMs7EJipifRp 6IEwFGXrKl7u0IaD7ERCyqO5bWzKiNVmJMcL/eRIQbtLbLLQ5XHtMKkHLc9NXqlx ihAJCFmK4zqcLskSiWkgN65t4brXHSbltmZzpjPNCA1USnitCm+/NOF5D05xrSkw EM16I/Jo1UgjoAhiS+gUZF+5r9rzuaD1Ia02XU9J7KzvLz8/4KOlA==
X-ME-Sender: <xms:P8t4XMIh1MhOKjLciQy6qRPRkfFxMPgOZOztqSX3cCy6_vS5KarnWg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrvdeggdelgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdforghrthhi nhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecuffhomh grihhnpehgihhthhhusgdrtghomhenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehl ohifvghnthhrohhphidrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:P8t4XAahoxTcycmthbFPpbLIxTDF7SYLv_I1ELCsArjXt6V0bFEzzA> <xmx:P8t4XHvgiTMfHb_Mq6OR6fUzAUsLcSYdphFJFHI2bfb6q_zPAiS6Yw> <xmx:P8t4XNsfxnuq4FPBGsUiTZa0Fcf9RVCBzh5vnn8u-0RD7uLokgAl_g> <xmx:P8t4XHO8XMO38QxwLd3rCh8sS2ShIqX779sY7kgk0FvThNr7M0Ag2g>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 442F77C4CE; Fri,  1 Mar 2019 01:03:43 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.5-925-g644bf8c-fmstable-20190228v5
X-Me-Personality: 92534000
Message-Id: <bd9f46be-abee-438c-b3f8-52eafd7b1b2e@www.fastmail.com>
In-Reply-To: <HE1PR07MB3259FFC36B8E84EA647982728D7A0@HE1PR07MB3259.eurprd07.prod.outlook.com>
References: <ec74675d-c576-f728-0481-c9488fb13beb@cisco.com> <DB7PR07MB4988216B696D0E69ED14D5F095820@DB7PR07MB4988.eurprd07.prod.outlook.com> <1547691891.367836.1636707376.1C1427EE@webmail.messagingengine.com> <AM0PR07MB5793531D0F31BCDBEF95CE8695830@AM0PR07MB5793.eurprd07.prod.outlook.com> <1548111599.1648805.1640352152.40952394@webmail.messagingengine.com> <HE1PR07MB3259FFC36B8E84EA647982728D7A0@HE1PR07MB3259.eurprd07.prod.outlook.com>
Date: Fri, 01 Mar 2019 01:03:43 -0500
From: "Martin Thomson" <mt@lowentropy.net>
To: "Bo Burman" <bo.burman@ericsson.com>, mmusic <mmusic@ietf.org>
Cc: "draft-ietf-mmusic-sdp-uks@ietf.org" <draft-ietf-mmusic-sdp-uks@ietf.org>
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/EVaaXXjlKRXQ3BDQ1zWgc5NjAzw>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sdp-uks-03
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, 01 Mar 2019 06:03:48 -0000

Thanks for reviewing Bo,

I've got the changes I've made up at https://github.com/martinthomson/sdp-uks/pull/7

The changes look like a lot, but that is mostly because of some reordering of text.  I've reworded a few things to improve clarity.  I appreciate having a new set of eyes on this.  I find I tend to miss places where the text assumes too much prior knowledge.

I'll put a second PR up for Flemming's review shortly.  That will stack on top of this one.

On Tue, Feb 26, 2019, at 00:23, Bo Burman wrote:
> Hi Martin,
> 
> I've now also reviewed this and have a set of comments and questions, 
> after taking Magnus' comments and your suggested edits in response to 
> that into account:
> 
> Section 2.1:
> * In bullet 2, "complete communications" is slightly unclear (more so 
> if "complete" is used in other contexts further down in the text). Do 
> you with "complete" mean "accept", or perhaps "accept setting up"?

Yes, I can see how this could be confusing. Reworded to:

"2. No entity will successfully establish a session with a peer unless they are
   willing to participate in a session with that peer."

> * Don't understand what is meant with "...second condition..."; is it 
> bullet #2, or is it referring to "...joining two separate sessions"?

Bullet 2, but see below.

> * Also don't really understand in what way that second condition is 
> "not necessary"; to limit the attacker capabilities (related to bullet 
> #2), for the attacker to join two sessions, or something else like "for 
> the attack to succeed"?
>
> * Just to confirm, does "removing this constraint" refer to removing 
> use of an identity binding?

Does this make more sense?

"Systems that rely on strong identity bindings, such as those defined in
{{WEBRTC}} or {{!SIP-ID}}, have a different threat model, which admits the
possibility of attack by an entity with access to the signaling channel.
Attacks under these conditions are more feasible as an attacker is assumed to be
able to both observe and modify signaling messages."

> Section 3:
> * Is the "victim" of the first paragraph the same or another victim 
> compared to the one mentioned in the next paragraph?
> 
> * Is "another entity of the attacker's choice" also to be considered a victim?

Yes, there are really two victims here, so I've reworded to use first victim and second victim.

"An attacker causes an
identity binding to be created that binds an identity they control to the
fingerprint of a first victim.

"An attacker can thereby cause a second victim to believe that they are
communicating with an attacker-controlled identity, when they are really talking
to the first victim.  The attacker only needs to create an identity assertion
that covers a certificate fingerprint of the first victim."

> * The last paragraph in section 3, just before section 3.1 "The same 
> technique..." seems a bit misplaced, after text talking about a 
> solution. Should it perhaps be moved just before the paragraph "The 
> problem..." in section 3? Or, is this "same technique" referring to 
> what is described in section 4?

Yes, this was a little light.  I've moved it up with the attack synopsis.

"A variation on the same technique can be used to cause both victims to both
believe they are talking to the attacker when they are talking to each other.
In this case, the attacker performs the identity misbinding once for each
victim."
 
> Section 4:
> * First sentence, "similar attack"; similar to what?

Yeah, that lost context.  How about:

"Even where the integrity of session signaling can be relied upon, an attacker
might still be able to create a session where there is confusion about the
communicating endpoints by substituting the fingerprint of a communicating
endpoint."

> Section 4.1:
> * Believe it would be helpful for the reader to better understand why 
> "Mallory has no real interest in seeing that session complete"

The next sentence is intended to explain this point: Mallory needs Patsy to maintain her end of the communications, lest Norma believe that the session is broken.
 
> * Same sentence, does "session complete" mean "session setup complete"? 
> I first interpreted "complete" as "conclude" in the meaning "terminate".
> 
> * Same paragraph, should "call completion" be "call setup completion", 
> and "session completes" be "session setup completes"?
> 
> * Same paragraph, "will likely be discarded by Patsy"; believe it would 
> be helpful to say why.

Here's what I ended up with:

"Though Patsy needs to believe that the second signaling session has been
successfully established, Mallory has no real interest in seeing that session
also be established.  Mallory only needs to ensure that Patsy maintains the
active session and does not abandon the session prematurely.  For this reason,
it might be necessary to permit the signaling from Patsy to reach Norma to allow
Patsy to receive a call setup completion signal, such as a SIP ACK.  Once the
second session completes, Mallory might cause DTLS packets sent by Norma to
Patsy to be dropped.  It is likely that these DTLS packets will be discarded by
Patsy as Patsy will already have a successful DTLS connection established."

> Section 4.2:
> * I believe the first paragraph ("An attack on... ...vulnerable to 
> attack.") would also be helpful as first text of section 4. Move? Copy?

Good suggestion.  I moved it up.

> * "Validating that peers..." -> "Successful validation that peers..."?

Yep.  Expanded to

"Successful validation that the identifier matches the expected value means that
the connection corresponds to the signaled session and is therefore established
between the correct two endpoints."

> Section 4.3:
> * "When used with SDP, the value includes..." -> "When used with SDP, 
> the value MUST consist of..."?

Thanks.

> Section 5:
> * "Use of the "external_session_id"
>    does not guarantee that the identity of the peer at the TLS layer is
>    the same as the identity of the signaling peer"; sounds a bit 
> strange - isn't this what the draft is supposed to solve? Is "... when 
> used with session concatenation" meant? 

This is a fundamental restriction of the design and with DTLS-SRTP in the absence of some sort of identity bindings.  As described here, an attacker can establish two sessions, call them A and B, with two different parties, call them Alice and Bob if you like.  It can send Bob's connection parameters (ICE, fingerprints,etc...) to Alice, and forward Alice's details to Bob in the same way.  This creates two signaling sessions (or 3pcc if you like), one between Alice and Attacker, and one between Attacker and Bob.  But there is only one media session between Alice and Bob.

I've done some rearranging here in an attempt to improve the flow of the section.  There are a few more words.  Let me know if it makes sense.

> * "Similarly, data from one TLS connection..."; I assume "data" means 
> "security-related information", not "user data" (TLS payload)?

Yep, thanks.


From nobody Thu Feb 28 22:47:23 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 406DD12D4ED; Thu, 28 Feb 2019 22:47:21 -0800 (PST)
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=hFTvbDKG; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=pgw/HnTv
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 UB2mVQsRUs-s; Thu, 28 Feb 2019 22:47:19 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D25731274D0; Thu, 28 Feb 2019 22:47:19 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id BEFA935C9; Fri,  1 Mar 2019 01:47:18 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Fri, 01 Mar 2019 01:47:19 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=message-id:in-reply-to:references:date:from:to:cc:subject :content-type; s=fm1; bh=dKto89BCk4enrp+D4LX3Ao1Je2VOfw9dGsvwejM 8tQM=; b=hFTvbDKGDLewl4H1RrlQL+OTQsr2lmsZ/LeaArtLJVwvD+ScaA+c2nt w9WwHPUyuhgSvA6CPubQvD6o9XUIQX+gho3iY2y5ZmSEt9GP4XFQ5MdIM+T5MMzx E30FvNG8S6ljMjLg38venvxvU/xZYc064nHa1d8wyw/zOMTXncLf2t9O6hfUm+zp 4bDVML3l86FbkXkKUFgLirV+81QPJwdHCQrlxNE8zTEM0qhvZI3TVUotF7gjd5vy hgZhMcKfoqNuC7nzgPgtm/mTNj7NJvAk6vw5pRT1ECZGAAjBd8pfzRDuNZ5uqQeF 3vGc4LxXU3X8m6TRxjewnsx3EBf8s8A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:references:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=dKto89BCk4enrp+D4 LX3Ao1Je2VOfw9dGsvwejM8tQM=; b=pgw/HnTvTl52UoU4+vQMUkbIu9nwXAbvr yED/KbmElh2JPj6y8KJeyZw2j1qmM9P6wZuUiOaV5MnMS93HQRy2ikrKQOmhY6Gr pl4qVb3HGe4hj2QTq9HxAAOLoISZGFlO8s3l3Hba3V+wDT58YZhbhCjex5IxW09I 744DhaNz3HVrYJPs59DWDh10cn+TXZBS9a1rXRbyiZSaqMJoBUBywpiERbfRH7dD RsZ53Kp5THnsV1UJF8X3xY7SaUbY2Cda9TUHDAmqTvfYl8Xcl5lJ5Hl/hIgU8ETX tO2VkANzSQ0xIGGyYQBiTK7NsdgIScjA77YgCzFyd4gGF6s9zfvqw==
X-ME-Sender: <xms:ddV4XNVvzlyeoj7lWfaxv13wxeKrjzxIQadHb9eTmJlVhXu5ATfF_w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrvdeggddutdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedfofgrrhht ihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigvnhhtrhhophihrdhnvghtqeenucffoh hmrghinhepghhithhhuhgsrdgtohhmnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmthes lhhofigvnhhtrhhophihrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:ddV4XDmbTqOx-IHrREZ8Q1xBqVp1sLxcZfi_4BX7AAu6RWQFZavDGg> <xmx:ddV4XHBDwuJBg0uP436h-yhLLN_s_ucfJmXPmlaf1ECVZX1XtNQ_pw> <xmx:ddV4XLefZ4gQq4Nnq-MXy5cdrIJ1r2UM3QmrgvPMus35_QdLkqEYGQ> <xmx:dtV4XAhwsiw8vLD8V3NIIWXYR7BSnmj1QC6JfU_nEB2IGsyR2JPbzg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 962C47C1EB; Fri,  1 Mar 2019 01:47:17 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.5-925-g644bf8c-fmstable-20190228v5
X-Me-Personality: 92534000
Message-Id: <e17042ae-af33-4b86-8a99-086290a1e8c0@www.fastmail.com>
In-Reply-To: <ea61540a-20c7-0c3d-1f7d-4d702d9a5332@cisco.com>
References: <ec74675d-c576-f728-0481-c9488fb13beb@cisco.com> <ea61540a-20c7-0c3d-1f7d-4d702d9a5332@cisco.com>
Date: Fri, 01 Mar 2019 01:47:17 -0500
From: "Martin Thomson" <mt@lowentropy.net>
To: "Flemming Andreasen" <fandreas@cisco.com>, mmusic <mmusic@ietf.org>
Cc: draft-ietf-mmusic-sdp-uks@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2YpqLxe0eiZEUKXAHxVOlVNdmpg>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sdp-uks-03
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, 01 Mar 2019 06:47:21 -0000

Thanks for the review Flemming,

I've made changes as suggested below, which you can review here: https://github.com/martinthomson/sdp-uks/pull/8

All the changes I have made are on https://github.com/martinthomson/sdp-uks/pull/9 if you want to see the entire batch of changes.

On Tue, Feb 26, 2019, at 15:45, Flemming Andreasen wrote:
> Hi Martin 
> 
>  I also took a closer look at the document and have a few additional 
> comments (as individual):
> 
>  Non-Editorial
>  =========
>  Section 2.3, second paragraph: The description on how 3PCC can work 
> with the proposed mechanism is a bit vague. It would be helpful to 
> expand it and provide an example.

Can do.

"For 3PCC to work with the proposed mechanisms, TLS peers need to be aware of the
signaling so that they can correctly generate (and check) the extension.  Peers
need access to any identity assertions present in signaling in order to perform
the checks in {{external_id_hash}}.  To perform the checks in
{{external_session_id}}, a 3PCC system needs to ensure that guarantee that peers
use the same SDP `tls-id` attribute value."

>  Section 3, last paragraph: The text seems out of place here. The text 
> implicitly refers to the previous paragraph, which doesn't seem to make 
> sense. 

Bo made the same comment.  I moved it up and expanded it a little.

>  Section 3.1, second paragraph: "In the first session, Patsy is 
> presented with the option to communicate with Norma"
>  How is that possible when the signaling originates from Mallory (I 
> thought we had signaling integrity and authenticated identity) ? 

The previous paragraph says "it is assumed that the attacker also controls the signaling channel."  As I mentioned in my other mail, when there is an identity binding, we assume that the signaling service is an attacker.  I've made some edits to the corresponding introductory text in response to Bo's review.  Let me know if you think that clears things up, or could be improved.
 

