
From nobody Sun Oct  2 17:31:04 2016
Return-Path: <ekr@rtfm.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 F2717127077 for <mmusic@ietfa.amsl.com>; Sun,  2 Oct 2016 17:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13-beqMpv-dB for <mmusic@ietfa.amsl.com>; Sun,  2 Oct 2016 17:30:59 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (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 9BB92127076 for <mmusic@ietf.org>; Sun,  2 Oct 2016 17:30:59 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id i129so99507768ywb.0 for <mmusic@ietf.org>; Sun, 02 Oct 2016 17:30:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=sS0zDNAPSkUMcgqIop34pvNYxK/KLWHEmUsH1KcT+eY=; b=BCYO0jU+ba4wsDZnLUmLGJSRtqtLzdkJkx7by3D8qU+H4F1OLQecYMJIqBgosubL29 CGcb2zutKKxtMguIHNnoLvRhYHSuYcUYmI9i9ONvomL8Z2AiZf2zD9m1xk/cUxKiShZu 70nSXtIHw+0ONitTH1gs7LyPTDeghPQ0D+jg83rMh3p7YvxNXGZz6aHRX5V9YM6cvhuo rYXcde6jpHbNsE3lIpmaqA/9+3I5B8JLZ9Ic1/1fq/3+RkJKBLp0JjQgyDWRzLO3v6s6 sf0Wz/H0NttXWCT6iQ32lytW5oiuyIOGazCQV4fFGKHGSJvHgEAbAuIVpHVLQah1l7WR ZjFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=sS0zDNAPSkUMcgqIop34pvNYxK/KLWHEmUsH1KcT+eY=; b=WWCGP2VwinH6NQ12zsPslU2zZf12+Qw28gH6mwjqBXajogFmuMWidjkd6SRFC6JUmn 4oGa5z9CtjpHgcQ9XHZxMl6AjhHPZlaCPu1LBihe9I1Q2EJYvqRBi71Z6EKfxYtg66yA 5hi5HnA9WnjGvB2TaUvSZMxr1HZk7fKP8Jw4v7ip9dwAatcHADPR6B9nUEJIQvnP1ZRO IinKcawjImA0Bcn8lC2JgHfmUZj141FH2Ga/nfRJmQMG3jeCQF43AKuBpIsX5jIE6xW4 adEDE+ju0wdpbkWPAT0hE8H9ah8ZE+UCATTSk3iXeIO4b3uQoxDnMqNYhESOhTYSHUHA M78Q==
X-Gm-Message-State: AA6/9Rm1CtMRzpHdhuft9B+OegSBe8oJVGx8roMvxoU+0zS0eUKusMCYazrj4aUXe/QYOu20VNhJkSzwQFiaFA==
X-Received: by 10.129.53.206 with SMTP id c197mr4574164ywa.205.1475454658801;  Sun, 02 Oct 2016 17:30:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.160.10 with HTTP; Sun, 2 Oct 2016 17:30:18 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BC722B7@ESESSMB209.ericsson.se>
References: <CABcZeBPpdyxiFbiHsqj=XwxFvOs4=z+R0zK0zoxbpixa25k3zQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BC722B7@ESESSMB209.ericsson.se>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 2 Oct 2016 17:30:18 -0700
Message-ID: <CABcZeBP_Rcd3_pmEcAoQVOeKV_mtStM+31Gz+6eqR4hDvHNemA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a11421a26d2498f053deb0e54
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FCsEnLY2_1OBOz6kkdEpzuSfSxo>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2016 00:31:03 -0000

--001a11421a26d2498f053deb0e54
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 29, 2016 at 12:54 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi Ekr,
>
>
>
> Thanks for the comments! Please see inline.
>
>
>
> OVERALL
>
>
>
> >The overall framing of this document as being about attaching multiple
>
> >m=3D sections to a single "shared address" is extremely problematic,
>
> >for two reasons:
>
> >
>
> >- With ICE there isn't actually any notion of a shared address except
>
> >  in some vague sense. I suppose you could argue that because with
>
> >  ICE you are required to specify a port on the m=3D line then you
>
> >  still have a concept of an address, but that's not true in
>
> >  trickle ICE, where the port is 9, so all m=3D lines share the same
>
> >  address/port. So, actually when you use trickle a whole bunch of
>
> >  the statements in this document are wrong.
>
> >
>
> >- A lot more is being overloaded here than addresses. In fact, a whole
>
> >  pile of semantics are being overloaded, so the way to think about
>
> >  this is actually as gluing a whole bunch of m=3D lines together at
>
> >  the transport level.
>
> >
>
> > I think the right concept here is not "shared address" but "bundle grou=
p"
>
> > and the document should be written in that way, namely that there are
>
> > a  bunch of m=3D lines in a bundle group and the one with the bundle ta=
g
>
> > is the one that sets all the shared parameters.
>
>
>
> It is true that the actual port value in the m- line, and the IP address
> in the c- line address, represent the address that is actually being used=
.
>
>
>
> But, even with ICE there is a shared address, isn=E2=80=99t there? Yes, t=
hat
> shared address may change, but at any given time there will be one addres=
s
> that is shared among the media streams within the BUNDLE group. Or?
>

Not if you trickle, no. Then all the m=3D lines have the same address wheth=
er
they are bundled or not.


MAJOR TECHNICAL
>
>
>
> > Maybe I missed this, but I don't see any requirement that m=3D lines
>
> > appear in the a=3Dgroup:BUNDLE line in the order they appear in the
>
> > SDP. That would make life a lot easier.
>
>
>
> There is no such requirement.
>
>
>
> AFAIR, it was discussed at some point, but it was agreed to not mandate m=
-
> lines to be listed in the order of preference (as far as selecting the
> BUNDLE address is concerned).
>
>
>
> Also, if you mid-session adds a new m- line, and wants that to represent
> the new BUNDLE address you have to place the new m- line after the existi=
ng
> m- lines, but you have to place it first in the a=3Dgroup:BUNDLE attribut=
e
> list.
>

OK. Well, that would be useful to state clearly upfront.


DETAILED COMMENTS (MIXED EDITORIAL/TECHNICAL)
>
>
>
> >S 1.
>
> >This really needs some explanation of why you would want this feature.
>
>
>
> You represent the community that wants the feature, so feel free to
> suggest some text explaining why you want it :)
>

"Each 5-tuple for which communications are set up consumes additional
resources (especially when ICE is in use). For this reason, it is
attractive to have as many different flows as possible multiplexed over the
same 5-tuple."


>S 5.
>
> >The first three grafs of this section seem to duplicate the intro
>
> >and the abstract.
>
> >
>
> >Also, this claim about sharing a 5-tuple is not quite right with ICE
>
> >because ICE can switch 5-tuples during aggressive nomination.
>
>
>
> Yes. But, at any given time there will only be one 5-tuple, won=E2=80=99t=
 it?
>

Not really no, no, because it's asymmetrical.

Say that we have two candidate pairs A and B with B higher priority than A.
The controlling endpoint sends checks on A and B but the initial check for
A is dropped
whereas the one for B is not. This establishes a flow on B at which point
both controlling
and controlled endpoints are sending on B. Then the controlling endpoint
retransmits the
check for A. At the point when the controlled endpoint receives that check
it starts transmitting
on A, but the controlling endpoint is still sending on B. So, the
controlled endpoint has to
simultaneously transmit on A but send on B.


>
>
> >S 8.1.
>
> >This seems like a key concept: there are a number of different categorie=
s
>
> >of attributes and some are shared with all members of a bundle group
>
> >and some are not. To what extent is this draft just duplicative of those
>
> >listed in the mux-attributes draft?
>
>
>
> Not sure I understand the question.
>

My point is that the concept you need to know for *this draft* is:

- Some attributes are shared and some are not.

The detailed rules are defined in the mux attributes draft, right?




> >S 8.2 and following
>
> >Really would be useful to have some examples here to make it less
>
> >abstract.
>
>
>
> You don=E2=80=99t think the examples in section 17 are enough? You want e=
xamples
> in the normative sections describing how to create offers, answers etc?
>

Yes. Partial examples would be fine.


>S 8.5.
>
> >How does this interact with ICE Restart?
>
>
>
> From a pure ICE Restart perspective, I don=E2=80=99t see any conflict. IC=
E Restart
> is triggered by changing the user name and password, and the text does no=
t
> forbid that.
>
>
>
> If you also want to change the BUNDLE address, you follow the rules in
> section 8.5.1.
>

My concern is this text "   These rules imply that setting the IP address
in the c line to

   0.0.0.0 will cause an ICE restart.  Consequently, ICE implementations
   MUST NOT utilize this mechanism for call hold, and instead MUST use

   a=3Dinactive and a=3Dsendonly as described in [RFC3264
<https://tools.ietf.org/html/rfc3264>]."




> >S 8.5.2
>
> >When you say "extend" do you mean "add to the end"?
>
>
>
> Yes. I can fix that.
>
>
>
>
>
> >S 10.1
>
> >In this first bullet is "if" "iff"?
>
>
>
> =E2=80=9Ciff=E2=80=9D?
>

"if and only if"



> >S 10.3.1.1.
>
> >   When an offerer generates an initial offer, the offerer MUST
>
> >   associate either an SDP 'rtcp-mux' attribute [RFC5761] or an SDP
>
> >   'rtcp-mux-only' attribute [I-D.ietf-mmusic-mux-exclusive] with each
>
> >   bundled RTP-based "m=3D" line in the offer.  The offerer MUST associa=
te
>
> >   an SDP 'rtcp-mux-only' attribute with each bundle-only "m=3D" line.  =
If
>
> >   the offerer associates a 'rtcp-mux-only' attribute with an "m=3D" lin=
e,
>
> >   the offerer may also associate a 'rtcp-mux' attribute with the same
>
> >   "m=3D" line, as described in [I-D.ietf-mmusic-mux-exclusive].
>
> >
>
> > This is a particularly egregious case of associate disease that could
>
> > be easily solved by using "add" when referring to the attributes
>
> > you put in the m=3D section.
>
>
>
> People have previously said that you don=E2=80=99t =E2=80=9Cadd=E2=80=9D =
attributes to m- lines:
> you add port values etc, but not attributes.
>
>
>
> This is an example of where I=E2=80=99ve had to re-write big parts of the
> documents a number of times already, because every time someone else read=
s
> the document he/she is not happy with the terminology. I just don=E2=80=
=99t want to
> do it again.
>

The terminology that JSEP uses is that "m=3D sections" include attribute
lines.

I think this is a lot clearer.



> >S 11.1
>
> >   When an offerer associates a unique address with a bundled "m=3D" lin=
e
>
> >   (excluding any bundle-only "m=3D" line), the offerer MUST associate S=
DP
>
> >   'candidate' attributes (and other applicable ICE-related media-level
>
> >   SDP attributes), containing unique ICE properties (candidates etc),
>
> >   with the "m=3D" line, according to the procedures in
>
> >   [I-D.ietf-mmusic-ice-sip-sdp].
>
> >
>
> > Here is an example of where the "address" framing doesn't work, if you
>
> > are using trickle.
>
>
>
> See top of e-mail.
>

Yeah, I continue to believe that this is wrong for the reasons above.

-Ekr


>
>
>
>
> Regards,
>
>
>
> Christer
>
>
>

--001a11421a26d2498f053deb0e54
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Aug 29, 2016 at 12:54 PM, Christer Holmberg <span dir=3D"ltr">&=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">





<div lang=3D"EN-GB">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Hi Ekr,<u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Thanks for the comments! Please see inline.<u></u><=
u></u></span></p>
</div><span class=3D"gmail-">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">OVERALL<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;The overall framing of this document as being a=
bout attaching multiple<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;m=3D sections to a single &quot;shared address&=
quot; is extremely problematic,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;for two reasons:<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;- With ICE there isn&#39;t actually any notion =
of a shared address except<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0in some vague sense. I suppose you could=
 argue that because with<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0ICE you are required to specify a port o=
n the m=3D line then you<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0still have a concept of an address, but =
that&#39;s not true in<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0trickle ICE, where the port is 9, so all=
 m=3D lines share the same<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0address/port. So, actually when you use =
trickle a whole bunch of<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0the statements in this document are wron=
g.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;- A lot more is being overloaded here than addr=
esses. In fact, a whole<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0pile of semantics are being overloaded, =
so the way to think about<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0this is actually as gluing a whole bunch=
 of m=3D lines together at<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0the transport level.<u></u><u></u></span=
></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; I think the right concept here is not &quot;sh=
ared address&quot; but &quot;bundle group&quot;<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; and the document should be written in that way=
, namely that there are<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; a =C2=A0bunch of m=3D lines in a bundle group =
and the one with the bundle tag<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; is the one that sets all the shared parameters=
.<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">It is true that the actual port value in the m- lin=
e, and the IP address in the c- line address, represent the address that is=
 actually being used.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">But, even with ICE there is a shared address, isn=
=E2=80=99t there? Yes, that shared address may change, but at any given tim=
e there will be one address that is shared among
 the media streams within the BUNDLE group. Or?</span></p></div></div></div=
></blockquote><div><br></div><div>Not if you trickle, no. Then all the m=3D=
 lines have the same address whether they are bundled or not.</div><div><br=
></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><di=
v lang=3D"EN-GB"><div><span class=3D"gmail-"><div><div><div><div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">MAJOR TECHNICAL<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; Maybe I missed this, but I don&#39;t see any r=
equirement that m=3D lines<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; appear in the a=3Dgroup:BUNDLE line in the ord=
er they appear in the<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; SDP. That would make life a lot easier.<u></u>=
<u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">There is no such requirement.<u></u><u></u></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">AFAIR, it was discussed at some point, but it was a=
greed to not mandate m- lines to be listed in the order of preference (as f=
ar as selecting the BUNDLE address
 is concerned).<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Also, if you mid-session adds a new m- line, and wa=
nts that to represent the new BUNDLE address you have to place the new m- l=
ine after the existing m- lines, but
 you have to place it first in the a=3Dgroup:BUNDLE attribute list.</span><=
/p></div></div></div></blockquote><div><br></div><div>OK. Well, that would =
be useful to state clearly upfront.</div><div><br></div><div><br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-GB"><span cla=
ss=3D"gmail-"><div><div><div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">DETAILED COMMENTS (MIXED EDITORIAL/TECHNICAL)<u></u=
><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 1.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;This really needs some explanation of why you w=
ould want this feature.<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">You represent the community that wants the feature,=
 so feel free to suggest some text explaining why you want it :)</span></p>=
</div></div></blockquote><div><br></div><div>&quot;Each 5-tuple for which c=
ommunications are set up consumes additional resources (especially when ICE=
 is in use). For this reason, it is attractive to have as many different fl=
ows as possible multiplexed over the same 5-tuple.&quot;</div><div>=C2=A0</=
div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div l=
ang=3D"EN-GB"><span class=3D"gmail-"><div><div><div><div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 5.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;The first three grafs of this section seem to d=
uplicate the intro<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;and the abstract.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;Also, this claim about sharing a 5-tuple is not=
 quite right with ICE<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;because ICE can switch 5-tuples during aggressi=
ve nomination.<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Yes. But, at any given time there will only be one =
5-tuple, won=E2=80=99t it?</span></p></div></div></blockquote><div><br></di=
v><div>Not really no, no, because it&#39;s asymmetrical.</div><div><br></di=
v><div>Say that we have two candidate pairs A and B with B higher priority =
than A.</div><div>The controlling endpoint sends checks on A and B but the =
initial check for A is dropped</div><div>whereas the one for B is not. This=
 establishes a flow on B at which point both controlling<br></div><div>and =
controlled endpoints are sending on B. Then the controlling endpoint retran=
smits the</div><div>check for A. At the point when the controlled endpoint =
receives that check it starts transmitting</div><div>on A, but the controll=
ing endpoint is still sending on B. So, the controlled endpoint has to</div=
><div>simultaneously transmit on A but send on B.</div><div>=C2=A0</div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-GB"><div><sp=
an class=3D"gmail-"><div><div><div><div><p class=3D"MsoNormal"><span style=
=3D"font-size:10.5pt;font-family:calibri,sans-serif;color:black">=C2=A0<u><=
/u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 8.1.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;This seems like a key concept: there are a numb=
er of different categories<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;of attributes and some are shared with all memb=
ers of a bundle group<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;and some are not. To what extent is this draft =
just duplicative of those<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;listed in the mux-attributes draft?<u></u><u></=
u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Not sure I understand the question.</span></p></div=
></div></div></blockquote><div><br></div><div>My point is that the concept =
you need to know for *this draft* is:</div><div><br></div><div>- Some attri=
butes are shared and some are not.</div><div><br></div><div>The detailed ru=
les are defined in the mux attributes draft, right?</div><div><br></div><di=
v><br></div><div><span style=3D"color:black;font-family:calibri,sans-serif;=
font-size:10.5pt">=C2=A0</span></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div lang=3D"EN-GB"><span class=3D"gmail-"><div><div><div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 8.2 and following<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;Really would be useful to have some examples he=
re to make it less<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;abstract.<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">You don=E2=80=99t think the examples in section 17 =
are enough? You want examples in the normative sections describing how to c=
reate offers, answers etc?</span></p></div></div></blockquote><div><br></di=
v><div>Yes. Partial examples would be fine.</div><div><br></div><div><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 lang=3D"EN-GB"><=
div><div><div><div><span class=3D"gmail-"><div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 8.5.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;How does this interact with ICE Restart?<u></u>=
<u></u></span></p>
</div>
</span></div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">From a pure ICE Restart perspective, I don=E2=80=99=
t see any conflict. ICE Restart is triggered by changing the user name and =
password, and the text does not forbid that.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">If you also want to change the BUNDLE address, you =
follow the rules in section 8.5.1.</span></p></div></div></div></blockquote=
><div><br></div><div>My concern is this text &quot; =C2=A0 These rules impl=
y that setting the IP address in the c line to</div><pre class=3D"gmail-new=
page">   0.0.0.0 will cause an ICE restart.  Consequently, ICE implementati=
ons
   MUST NOT utilize this mechanism for call hold, and instead MUST use=C2=
=A0</pre><div>=C2=A0 =C2=A0a=3Dinactive and a=3Dsendonly as described in [<=
a href=3D"https://tools.ietf.org/html/rfc3264" title=3D"&quot;An Offer/Answ=
er Model with Session Description Protocol (SDP)&quot;">RFC3264</a>].&quot;=
</div><div><br></div><div><span style=3D"color:black;font-family:calibri,sa=
ns-serif;font-size:10.5pt"><br></span></div><div><span style=3D"color:black=
;font-family:calibri,sans-serif;font-size:10.5pt">=C2=A0</span></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 lang=3D"EN-GB"><div><span =
class=3D"gmail-"><div><div><div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 8.5.2<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;When you say &quot;extend&quot; do you mean &qu=
ot;add to the end&quot;?<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Yes. I can fix that.<u></u><u></u></span></p>
</div><span class=3D"gmail-">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 10.1<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;In this first bullet is &quot;if&quot; &quot;if=
f&quot;?<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">=E2=80=9Ciff=E2=80=9D?</span></p></div></div></div>=
</blockquote><div><br></div><div>&quot;if and only if&quot;</div><div>=C2=
=A0</div><div><span style=3D"color:black;font-family:calibri,sans-serif;fon=
t-size:10.5pt">=C2=A0</span></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 lang=3D"EN-GB"><div><span class=3D"gmail-"><div><div><div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 10.3.1.1.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 When an offerer generates an initial of=
fer, the offerer MUST<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 associate either an SDP &#39;rtcp-mux&#=
39; attribute [RFC5761] or an SDP<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 &#39;rtcp-mux-only&#39; attribute [I-D.=
ietf-mmusic-mux-<wbr>exclusive] with each<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 bundled RTP-based &quot;m=3D&quot; line=
 in the offer.=C2=A0 The offerer MUST associate<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 an SDP &#39;rtcp-mux-only&#39; attribut=
e with each bundle-only &quot;m=3D&quot; line.=C2=A0 If<u></u><u></u></span=
></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 the offerer associates a &#39;rtcp-mux-=
only&#39; attribute with an &quot;m=3D&quot; line,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 the offerer may also associate a &#39;r=
tcp-mux&#39; attribute with the same<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 &quot;m=3D&quot; line, as described in =
[I-D.ietf-mmusic-mux-<wbr>exclusive].<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; This is a particularly egregious case of assoc=
iate disease that could<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; be easily solved by using &quot;add&quot; when=
 referring to the attributes<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; you put in the m=3D section.<u></u><u></u></sp=
an></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">People have previously said that you don=E2=80=99t =
=E2=80=9Cadd=E2=80=9D attributes to m- lines: you add port values etc, but =
not attributes.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">This is an example of where I=E2=80=99ve had to re-=
write big parts of the documents a number of times already, because every t=
ime someone else reads the document he/she
 is not happy with the terminology. I just don=E2=80=99t want to do it agai=
n.</span></p></div></div></div></blockquote><div><br></div><div>The termino=
logy that JSEP uses is that &quot;m=3D sections&quot; include attribute lin=
es.</div><div><span style=3D"color:black;font-family:calibri,sans-serif;fon=
t-size:10.5pt"><br></span></div><div><span style=3D"color:black;font-family=
:calibri,sans-serif;font-size:10.5pt">I think this is a lot clearer.</span>=
</div><div><span style=3D"color:black;font-family:calibri,sans-serif;font-s=
ize:10.5pt"><br></span></div><div><span style=3D"color:black;font-family:ca=
libri,sans-serif;font-size:10.5pt">=C2=A0</span></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div lang=3D"EN-GB"><div><span class=3D"gmail-=
"><div><div><div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 11.1<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 When an offerer associates a unique add=
ress with a bundled &quot;m=3D&quot; line<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 (excluding any bundle-only &quot;m=3D&q=
uot; line), the offerer MUST associate SDP<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 &#39;candidate&#39; attributes (and oth=
er applicable ICE-related media-level<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 SDP attributes), containing unique ICE =
properties (candidates etc),<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 with the &quot;m=3D&quot; line, accordi=
ng to the procedures in<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 [I-D.ietf-mmusic-ice-sip-sdp].<u></u><u=
></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; Here is an example of where the &quot;address&=
quot; framing doesn&#39;t work, if you<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; are using trickle.<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">See top of e-mail.</span></p></div></div></div></bl=
ockquote><div><br></div><div>Yeah, I continue to believe that this is wrong=
 for the reasons above.</div><div><br></div><div>-Ekr</div><div>=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-GB"><div=
><div><p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:ca=
libri,sans-serif;color:black"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Regards,<span class=3D"gmail-HOEnZb"><font color=3D=
"#888888"><u></u><u></u></font></span></span></p><span class=3D"gmail-HOEnZ=
b"><font color=3D"#888888">
</font></span></div><span class=3D"gmail-HOEnZb"><font color=3D"#888888">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Christer<u></u><u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</div>
</div>
</div>
</font></span></div>
</div>

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

--001a11421a26d2498f053deb0e54--


From nobody Mon Oct  3 04:01:34 2016
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 455D512B078 for <mmusic@ietfa.amsl.com>; Mon,  3 Oct 2016 04:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 nbOpXA93m6R9 for <mmusic@ietfa.amsl.com>; Mon,  3 Oct 2016 04:01:26 -0700 (PDT)
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 5932112B04E for <mmusic@ietf.org>; Mon,  3 Oct 2016 04:01:24 -0700 (PDT)
X-AuditID: c1b4fb25-14bff7000000793b-9a-57f23a82290a
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by  (Symantec Mail Security) with SMTP id E4.47.31035.28A32F75; Mon,  3 Oct 2016 13:01:23 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0319.002; Mon, 3 Oct 2016 13:01:22 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I)
Thread-Index: AQHSAjFbVSmCBcGmbka3UICv6Cl9oaCV9LgAgADkVIA=
Date: Mon, 3 Oct 2016 11:01:21 +0000
Message-ID: <D41804D7.10437%christer.holmberg@ericsson.com>
References: <CABcZeBPpdyxiFbiHsqj=XwxFvOs4=z+R0zK0zoxbpixa25k3zQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BC722B7@ESESSMB209.ericsson.se> <CABcZeBP_Rcd3_pmEcAoQVOeKV_mtStM+31Gz+6eqR4hDvHNemA@mail.gmail.com>
In-Reply-To: <CABcZeBP_Rcd3_pmEcAoQVOeKV_mtStM+31Gz+6eqR4hDvHNemA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_D41804D710437christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFIsWRmVeSWpSXmKPExsUyM2K7pW6z1adwgyMnOSxWvD7HbjF1+WMW ByaPJUt+MnlMftzGHMAUxWWTkpqTWZZapG+XwJWx7ad/wa1bTBX7dk1jamBcspqpi5GTQ0LA ROLtkc3MXYxcHEIC6xklLv3vgXIWMUpc+7yMrYuRg4NNwEKi+582SIOIgILErz8nWEBsZgF5 iQtL1oANEhYIk5i44SQTRE24xOGn/6FsK4n/s86BjWERUJFYctYDJMwrYC1xteU6O8Sq20Cr unrZQRKcAoESz88vZASxGQXEJL6fgpjPLCAucevJfKijBSSW7DnPDGGLSrx8/I8VxBYV0JP4 /nU2M8guCQFFieX9ciAms0CCxKojJhBrBSVOznzCMoFRdBaSobMQqmYhqYIoMZB4f24+M4St LbFs4WsoW19i45ezjBC2tcSnVSvZkNUsYORYxShanFqclJtuZKyXWpSZXFycn6eXl1qyiREY gwe3/FbdwXj5jeMhRgEORiUe3gdCH8OFWBPLiitzDzFKcDArifButPgULsSbklhZlVqUH19U mpNafIhRmoNFSZzXbOX9cCGB9MSS1OzU1ILUIpgsEwenVAPjlPh+y7zFh/7vDb6bOecF11zp w7NzcyZuiWh+vjA4aMuc2sVz5jOaXvj3dAlvQ7hx240typEr70ocbGCIsuRROyR9f0n49dg9 ezSzrxju+HZt5s/fq/mFjAPET846eeRsNkee0MmdH40SxY/cs5q+ZdKcqy3Nr3LfrSrZeG6u X136zJkzLX9OEFNiKc5INNRiLipOBAB8uJKSvQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MmxXoTm5EvW1WrGfp3vuG5YQgvM>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2016 11:01:33 -0000

--_000_D41804D710437christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

OVERALL

>The overall framing of this document as being about attaching multiple
>m=3D sections to a single "shared address" is extremely problematic,
>for two reasons:
>
>- With ICE there isn't actually any notion of a shared address except
>  in some vague sense. I suppose you could argue that because with
>  ICE you are required to specify a port on the m=3D line then you
>  still have a concept of an address, but that's not true in
>  trickle ICE, where the port is 9, so all m=3D lines share the same
>  address/port. So, actually when you use trickle a whole bunch of
>  the statements in this document are wrong.
>
>- A lot more is being overloaded here than addresses. In fact, a whole
>  pile of semantics are being overloaded, so the way to think about
>  this is actually as gluing a whole bunch of m=3D lines together at
>  the transport level.
>
> I think the right concept here is not "shared address" but "bundle group"
> and the document should be written in that way, namely that there are
> a  bunch of m=3D lines in a bundle group and the one with the bundle tag
> is the one that sets all the shared parameters.

It is true that the actual port value in the m- line, and the IP address in=
 the c- line address, represent the address that is actually being used.

But, even with ICE there is a shared address, isn=92t there? Yes, that shar=
ed address may change, but at any given time there will be one address that=
 is shared among the media streams within the BUNDLE group. Or?

Not if you trickle, no. Then all the m=3D lines have the same address wheth=
er they are bundled or not.


Ok, I hear you. You are basically saying that it doesn=92t matter whether b=
undled m- lines share addresses or not =96 the ONLY thing that matters is t=
hat the m- line associated with the bundle tag contains the address to be u=
sed.

The reason we mandated shared addresses, once the usage of BUNDLE had been =
negotiated, was because of intermediaries that don=92t support BUNDLE (to m=
ake sure they send media towards the correct address). But, maybe we don=92=
t need to worry about anymore =96 BUNDLE probably won=92t work reliably wit=
h such intermediaries anyway=85

Also, there is at least once case where the address matters: when you add a=
 new m- line to a bundle group. If you use a unique address, and the answer=
er does not accept the m- line in the BUNDLE group, it can be used un-bundl=
ed. If you use a shared address, the answerer will have to reject the m- li=
ne.


MAJOR TECHNICAL

> Maybe I missed this, but I don't see any requirement that m=3D lines
> appear in the a=3Dgroup:BUNDLE line in the order they appear in the
> SDP. That would make life a lot easier.

There is no such requirement.

AFAIR, it was discussed at some point, but it was agreed to not mandate m- =
lines to be listed in the order of preference (as far as selecting the BUND=
LE address is concerned).

Also, if you mid-session adds a new m- line, and wants that to represent th=
e new BUNDLE address you have to place the new m- line after the existing m=
- lines, but you have to place it first in the a=3Dgroup:BUNDLE attribute l=
ist.

OK. Well, that would be useful to state clearly upfront.

I=92ll think of some wording.


DETAILED COMMENTS (MIXED EDITORIAL/TECHNICAL)

>S 1.
>This really needs some explanation of why you would want this feature.

You represent the community that wants the feature, so feel free to suggest=
 some text explaining why you want it :)

"Each 5-tuple for which communications are set up consumes additional resou=
rces (especially when ICE is in use). For this reason, it is attractive to =
have as many different flows as possible multiplexed over the same 5-tuple.=
"

l=92ll add that.


>S 5.
>The first three grafs of this section seem to duplicate the intro
>and the abstract.
>
>Also, this claim about sharing a 5-tuple is not quite right with ICE
>because ICE can switch 5-tuples during aggressive nomination.

Yes. But, at any given time there will only be one 5-tuple, won=92t it?

Not really no, no, because it's asymmetrical.

Say that we have two candidate pairs A and B with B higher priority than A.
The controlling endpoint sends checks on A and B but the initial check for =
A is dropped
whereas the one for B is not. This establishes a flow on B at which point b=
oth controlling
and controlled endpoints are sending on B. Then the controlling endpoint re=
transmits the
check for A. At the point when the controlled endpoint receives that check =
it starts transmitting
on A, but the controlling endpoint is still sending on B. So, the controlle=
d endpoint has to
simultaneously transmit on A but send on B.

Sure, different 5-tuples may be used in each direction, as indicated in the=
 two first paragraphs.

I guess we could remove =935-tuple=94 text in the 3rd paragraph, and only s=
ay that all media associated with a BUNDLE group is sent using the same tra=
nsport layer protocol.


>S 8.1.
>This seems like a key concept: there are a number of different categories
>of attributes and some are shared with all members of a bundle group
>and some are not. To what extent is this draft just duplicative of those
>listed in the mux-attributes draft?

Not sure I understand the question.

My point is that the concept you need to know for *this draft* is:

- Some attributes are shared and some are not.

The detailed rules are defined in the mux attributes draft, right?


Yes. So, perhaps we should not use RFC2119 terminology in draft-bundle, but=
 simple refer to draft-mux-attributes for the rules.



>S 8.2 and following
>Really would be useful to have some examples here to make it less
>abstract.

You don=92t think the examples in section 17 are enough? You want examples =
in the normative sections describing how to create offers, answers etc?

Yes. Partial examples would be fine.

I=92ll look into that.

>S 8.5.
>How does this interact with ICE Restart?

>From a pure ICE Restart perspective, I don=92t see any conflict. ICE Restar=
t is triggered by changing the user name and password, and the text does no=
t forbid that.

If you also want to change the BUNDLE address, you follow the rules in sect=
ion 8.5.1.

My concern is this text "   These rules imply that setting the IP address i=
n the c line to

   0.0.0.0 will cause an ICE restart.  Consequently, ICE implementations
   MUST NOT utilize this mechanism for call hold, and instead MUST use

   a=3Dinactive and a=3Dsendonly as described in [RFC3264<https://tools.iet=
f.org/html/rfc3264>]."

Correct. So, if you use BUNDLE and want to trigger an ICE restart, you do a=
s described above. BUNDLE does not define usage of 0.0.0.0 in the c line, s=
o there should be no conflict.

Or, do I still misunderstand you issue?

>S 8.5.2
>When you say "extend" do you mean "add to the end"?

Yes. I can fix that.


>S 10.1
>In this first bullet is "if" "iff"?

=93iff=94?

"if and only if"

 It=92s =93iff=94.

>S 10.3.1.1.
>   When an offerer generates an initial offer, the offerer MUST
>   associate either an SDP 'rtcp-mux' attribute [RFC5761] or an SDP
>   'rtcp-mux-only' attribute [I-D.ietf-mmusic-mux-exclusive] with each
>   bundled RTP-based "m=3D" line in the offer.  The offerer MUST associate
>   an SDP 'rtcp-mux-only' attribute with each bundle-only "m=3D" line.  If
>   the offerer associates a 'rtcp-mux-only' attribute with an "m=3D" line,
>   the offerer may also associate a 'rtcp-mux' attribute with the same
>   "m=3D" line, as described in [I-D.ietf-mmusic-mux-exclusive].
>
> This is a particularly egregious case of associate disease that could
> be easily solved by using "add" when referring to the attributes
> you put in the m=3D section.

People have previously said that you don=92t =93add=94 attributes to m- lin=
es: you add port values etc, but not attributes.

This is an example of where I=92ve had to re-write big parts of the documen=
ts a number of times already, because every time someone else reads the doc=
ument he/she is not happy with the terminology. I just don=92t want to do i=
t again.

The terminology that JSEP uses is that "m=3D sections" include attribute li=
nes.

I think this is a lot clearer.

 I don=92t personally disagree, but there are people that have had other op=
inions.

 In general I think it would be really useful to have common terminology in=
 BUNDLE and JSEP, but I don=92t want to re-write the document once again, a=
nd then later be told to do it again=85

Regards,

Christer



--_000_D41804D710437christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <8E9F2E143B001F4C9E5149C73682F278@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
Hi,</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px; color: rgb(0, 0, 0);">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<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 lang=3D"EN-GB">
<div><span class=3D"gmail-">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">OVERALL<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;The overall framing of this document as being a=
bout attaching multiple<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;m=3D sections to a single &quot;shared address&=
quot; is extremely problematic,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;for two reasons:<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;- With ICE there isn't actually any notion of a=
 shared address except<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp;in some vague sense. I suppose you could=
 argue that because with<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp;ICE you are required to specify a port o=
n the m=3D line then you<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp;still have a concept of an address, but =
that's not true in<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp;trickle ICE, where the port is 9, so all=
 m=3D lines share the same<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp;address/port. So, actually when you use =
trickle a whole bunch of<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp;the statements in this document are wron=
g.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;- A lot more is being overloaded here than addr=
esses. In fact, a whole<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp;pile of semantics are being overloaded, =
so the way to think about<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp;this is actually as gluing a whole bunch=
 of m=3D lines together at<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp;the transport level.<u></u><u></u></span=
></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; I think the right concept here is not &quot;sh=
ared address&quot; but &quot;bundle group&quot;<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; and the document should be written in that way=
, namely that there are<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; a &nbsp;bunch of m=3D lines in a bundle group =
and the one with the bundle tag<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; is the one that sets all the shared parameters=
.<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">It is true that the actual port value in the m- lin=
e, and the IP address in the c- line address, represent the address that is=
 actually being used.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">But, even with ICE there is a shared address, isn=
=92t there? Yes, that shared address may change, but at any given time ther=
e will be one address that is shared among
 the media streams within the BUNDLE group. Or?</span></p>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Not if you trickle, no. Then all the m=3D lines have the same address =
whether they are bundled or not.</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">Ok, I hear you. Y=
ou are basically saying that it doesn=92t matter whether bundled m- lines s=
hare addresses or not&nbsp;=96&nbsp;the ONLY thing that matters is that the=
 m- line associated with the bundle tag contains the
 address to be used.</font></font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><font face=3D"Calibri,sans-serif"><br>
</font></font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">The reason we man=
dated shared addresses, once the usage of BUNDLE had been negotiated, was b=
ecause of intermediaries that don=92t support BUNDLE (to make sure they sen=
d media towards the correct address).
 But, maybe we don=92t need to worry about anymore&nbsp;=96&nbsp;BUNDLE&nbs=
p;probably won=92t work reliably with such&nbsp;intermediaries anyway</font=
></font><font color=3D"#ff0000" face=3D"Calibri,sans-serif">=85</font></div=
>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000" face=3D"Calibri,sans-serif"><br>
</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000" face=3D"Calibri,sans-serif">Also, there is at least=
 once case where the address matters: when you add a new m- line to a bundl=
e group. If you use a unique address, and the answerer does not accept the =
m- line in the BUNDLE group, it can
 be used un-bundled. If you use a shared address, the answerer will have to=
 reject the m- line.</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000" face=3D"Calibri,sans-serif"><br>
</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px; color: rgb(0, 0, 0);">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<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 lang=3D"EN-GB">
<div><span class=3D"gmail-">
<div>
<div>
<div>
<div></div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">MAJOR TECHNICAL<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; Maybe I missed this, but I don't see any requi=
rement that m=3D lines<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; appear in the a=3Dgroup:BUNDLE line in the ord=
er they appear in the<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; SDP. That would make life a lot easier.<u></u>=
<u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">There is no such requirement.<u></u><u></u></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">AFAIR, it was discussed at some point, but it was a=
greed to not mandate m- lines to be listed in the order of preference (as f=
ar as selecting the BUNDLE address is
 concerned).<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Also, if you mid-session adds a new m- line, and wa=
nts that to represent the new BUNDLE address you have to place the new m- l=
ine after the existing m- lines, but
 you have to place it first in the a=3Dgroup:BUNDLE attribute list.</span><=
/p>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>OK. Well, that would be useful to state clearly upfront.</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">I=92ll think of some wording.</font></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px; color: rgb(0, 0, 0);">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><br>
</div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang=3D"EN-GB"><span class=3D"gmail-">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">DETAILED COMMENTS (MIXED EDITORIAL/TECHNICAL)<u></u=
><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 1.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;This really needs some explanation of why you w=
ould want this feature.<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">You represent the community that wants the feature,=
 so feel free to suggest some text explaining why you want it :)</span></p>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>&quot;Each 5-tuple for which communications are set up consumes additi=
onal resources (especially when ICE is in use). For this reason, it is attr=
active to have as many different flows as possible multiplexed over the sam=
e 5-tuple.&quot;</div>
<div>&nbsp;</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">l=92ll add that.</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px; color: rgb(0, 0, 0);">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<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 lang=3D"EN-GB"><span class=3D"gmail-">
<div>
<div>
<div>
<div></div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 5.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;The first three grafs of this section seem to d=
uplicate the intro<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;and the abstract.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;Also, this claim about sharing a 5-tuple is not=
 quite right with ICE<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;because ICE can switch 5-tuples during aggressi=
ve nomination.<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Yes. But, at any given time there will only be one =
5-tuple, won=92t it?</span></p>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Not really no, no, because it's asymmetrical.</div>
<div><br>
</div>
<div>Say that we have two candidate pairs A and B with B higher priority th=
an A.</div>
<div>The controlling endpoint sends checks on A and B but the initial check=
 for A is dropped</div>
<div>whereas the one for B is not. This establishes a flow on B at which po=
int both controlling<br>
</div>
<div>and controlled endpoints are sending on B. Then the controlling endpoi=
nt retransmits the</div>
<div>check for A. At the point when the controlled endpoint receives that c=
heck it starts transmitting</div>
<div>on A, but the controlling endpoint is still sending on B. So, the cont=
rolled endpoint has to</div>
<div>simultaneously transmit on A but send on B.</div>
<div>&nbsp;</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><font col=
or=3D"#ff0000">Sure, different 5-tuples may be used in each direction, as i=
ndicated in the two first paragraphs.</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><font col=
or=3D"#ff0000"><br>
</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><font col=
or=3D"#ff0000">I guess we could remove =935-tuple=94 text in the 3rd paragr=
aph, and only say that all media associated with a BUNDLE group is sent usi=
ng the same transport layer protocol.</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><font col=
or=3D"#ff0000"><br>
</font></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px;">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; borde=
r-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 20=
4, 204); padding-left: 1ex;">
<div lang=3D"EN-GB"><span class=3D"gmail-">
<div>
<div>
<p class=3D"MsoNormal"><br>
</p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 8.1.<u></u><u></u></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;This seems like a key concept: there are a numb=
er of different categories<u></u><u></u></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;of attributes and some are shared with all memb=
ers of a bundle group<u></u><u></u></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;and some are not. To what extent is this draft =
just duplicative of those<u></u><u></u></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;listed in the mux-attributes draft?<u></u><u></=
u></span></p>
</div>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Not sure I understand the question.</span></p>
</div>
</div>
</blockquote>
<div style=3D"color: rgb(0, 0, 0);"><br>
</div>
<div style=3D"color: rgb(0, 0, 0);">My point is that the concept you need t=
o know for *this draft* is:</div>
<div style=3D"color: rgb(0, 0, 0);"><br>
</div>
<div style=3D"color: rgb(0, 0, 0);">- Some attributes are shared and some a=
re not.</div>
<div style=3D"color: rgb(0, 0, 0);"><br>
</div>
<div style=3D"color: rgb(0, 0, 0);">The detailed rules are defined in the m=
ux attributes draft, right?</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><br>
</div>
<div><font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">Yes. So, per=
haps we should not use RFC2119 terminology in draft-bundle, but simple refe=
r to&nbsp;draft-mux-attributes for the rules.&nbsp;</font></font></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px;">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div style=3D"color: rgb(0, 0, 0);"><br>
</div>
<div style=3D"color: rgb(0, 0, 0);"><br>
</div>
<div style=3D"color: rgb(0, 0, 0);"><span style=3D"color:black;font-family:=
calibri,sans-serif;font-size:10.5pt">&nbsp;</span></div>
<blockquote class=3D"gmail_quote" style=3D"color: rgb(0, 0, 0); margin: 0px=
 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-le=
ft-color: rgb(204, 204, 204); padding-left: 1ex;">
<div lang=3D"EN-GB"><span class=3D"gmail-">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 8.2 and following<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;Really would be useful to have some examples he=
re to make it less<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;abstract.<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">You don=92t think the examples in section 17 are en=
ough? You want examples in the normative sections describing how to create =
offers, answers etc?</span></p>
</div>
</div>
</blockquote>
<div style=3D"color: rgb(0, 0, 0);"><br>
</div>
<div style=3D"color: rgb(0, 0, 0);">Yes. Partial examples would be fine.</d=
iv>
</div>
</div>
</div>
</span>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><font color=3D"#ff0000" face=3D"Calibri,sans-serif">I=92ll look into t=
hat.</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<blockquote class=3D"gmail_quote" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px; color: rgb(0, 0, 0); margin: 0px 0px 0px 0.8ex; border-l=
eft-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, =
204); padding-left: 1ex;">
<div lang=3D"EN-GB">
<div>
<div>
<div>
<div><span class=3D"gmail-">
<div></div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 8.5.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;How does this interact with ICE Restart?<u></u>=
<u></u></span></p>
</div>
</span></div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">From a pure ICE Restart perspective, I don=92t see =
any conflict. ICE Restart is triggered by changing the user name and passwo=
rd, and the text does not forbid that.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">If you also want to change the BUNDLE address, you =
follow the rules in section 8.5.1.</span></p>
</div>
</div>
</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
My concern is this text &quot; &nbsp; These rules imply that setting the IP=
 address in the c line to</div>
<pre class=3D"gmail-newpage" style=3D"font-family: Calibri, sans-serif; fon=
t-size: 14px; color: rgb(0, 0, 0);">   0.0.0.0 will cause an ICE restart.  =
Consequently, ICE implementations
   MUST NOT utilize this mechanism for call hold, and instead MUST use&nbsp=
;</pre>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
&nbsp; &nbsp;a=3Dinactive and a=3Dsendonly as described in [<a href=3D"http=
s://tools.ietf.org/html/rfc3264" title=3D"&quot;An Offer/Answer Model with =
Session Description Protocol (SDP)&quot;">RFC3264</a>].&quot;</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<span style=3D"color: rgb(255, 0, 0); font-size: medium;">Correct. So, if y=
ou use BUNDLE and want to trigger an ICE restart, you do as described above=
. BUNDLE does not define usage of 0.0.0.0 in the c line, so there should be=
 no conflict.</span></div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div><font color=3D"#ff0000">Or, do I still misunderstand you issue?</font>=
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<span style=3D"color:black;font-family:calibri,sans-serif;font-size:10.5pt"=
>&nbsp;</span></div>
<blockquote class=3D"gmail_quote" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px; color: rgb(0, 0, 0); margin: 0px 0px 0px 0.8ex; border-l=
eft-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, =
204); padding-left: 1ex;">
<div lang=3D"EN-GB">
<div><span class=3D"gmail-">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 8.5.2<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;When you say &quot;extend&quot; do you mean &qu=
ot;add to the end&quot;?<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Yes. I can fix that.<u></u><u></u></span></p>
</div>
<span class=3D"gmail-">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 10.1<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;In this first bullet is &quot;if&quot; &quot;if=
f&quot;?<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">=93iff=94?</span></p>
</div>
</div>
</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
&quot;if and only if&quot;</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
&nbsp;</div>
</div>
</div>
</div>
</span>
<div><font color=3D"#ff0000">&nbsp;It=92s&nbsp;=93iff=94.</font></div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<span style=3D"color:black;font-family:calibri,sans-serif;font-size:10.5pt"=
>&nbsp;</span></div>
<blockquote class=3D"gmail_quote" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px; color: rgb(0, 0, 0); margin: 0px 0px 0px 0.8ex; border-l=
eft-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, =
204); padding-left: 1ex;">
<div lang=3D"EN-GB">
<div><span class=3D"gmail-">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 10.3.1.1.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp; When an offerer generates an initial of=
fer, the offerer MUST<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp; associate either an SDP 'rtcp-mux' attr=
ibute [RFC5761] or an SDP<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp; 'rtcp-mux-only' attribute [I-D.ietf-mmu=
sic-mux-<wbr>exclusive] with each<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp; bundled RTP-based &quot;m=3D&quot; line=
 in the offer.&nbsp; The offerer MUST associate<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp; an SDP 'rtcp-mux-only' attribute with e=
ach bundle-only &quot;m=3D&quot; line.&nbsp; If<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp; the offerer associates a 'rtcp-mux-only=
' attribute with an &quot;m=3D&quot; line,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp; the offerer may also associate a 'rtcp-=
mux' attribute with the same<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; &nbsp; &quot;m=3D&quot; line, as described in =
[I-D.ietf-mmusic-mux-<wbr>exclusive].<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; This is a particularly egregious case of assoc=
iate disease that could<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; be easily solved by using &quot;add&quot; when=
 referring to the attributes<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; you put in the m=3D section.<u></u><u></u></sp=
an></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">People have previously said that you don=92t =93add=
=94 attributes to m- lines: you add port values etc, but not attributes.<u>=
</u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">This is an example of where I=92ve had to re-write =
big parts of the documents a number of times already, because every time so=
meone else reads the document he/she is
 not happy with the terminology. I just don=92t want to do it again.</span>=
</p>
</div>
</div>
</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
The terminology that JSEP uses is that &quot;m=3D sections&quot; include at=
tribute lines.</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<span style=3D"color:black;font-family:calibri,sans-serif;font-size:10.5pt"=
><br>
</span></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<span style=3D"color:black;font-family:calibri,sans-serif;font-size:10.5pt"=
>I think this is a lot clearer.</span></div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div>
<div><font color=3D"#ff0000">&nbsp;I don=92t personally disagree, but there=
 are people that have had other opinions.</font></div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote"></div>
</div>
</div>
</span></div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><font color=3D"#ff0000">&nbsp;In general I think it would be&nbsp;real=
ly useful to have common&nbsp;terminology in BUNDLE and JSEP, but I don=92t=
 want to re-write the document once again, and then later be told to do it =
again=85</font></div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div><font color=3D"#ff0000">Regards,</font></div>
<div><font color=3D"#ff0000"><br>
</font></div>
<div><font color=3D"#ff0000">Christer</font></div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>

--_000_D41804D710437christerholmbergericssoncom_--


From nobody Mon Oct  3 07:00:58 2016
Return-Path: <ekr@rtfm.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 E464212B096 for <mmusic@ietfa.amsl.com>; Mon,  3 Oct 2016 07:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3aXl3gGULYZD for <mmusic@ietfa.amsl.com>; Mon,  3 Oct 2016 07:00:51 -0700 (PDT)
Received: from mail-yb0-x22b.google.com (mail-yb0-x22b.google.com [IPv6:2607:f8b0:4002:c09::22b]) (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 5D9AD12B29A for <mmusic@ietf.org>; Mon,  3 Oct 2016 07:00:49 -0700 (PDT)
Received: by mail-yb0-x22b.google.com with SMTP id 191so10869281ybv.3 for <mmusic@ietf.org>; Mon, 03 Oct 2016 07:00:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lorfZcGqqwcvrfgjPN3L4FpYiXRnLRfq8PAWJbAsXjM=; b=oHeq862DuwUxRduPxh894AENQzcGuLyfaE67RTHGnjV2Bk2ZRiUjDjvOWLnupCuawx GJZKtBuOKeWDL6hiU2Ky/3kM7wq49mRbt7hvUT2ECKFoLiszc2Jd9fqCdgi8wD/CF6RJ 9EEX0xYmXlt4QvuxJAmRUcWTDummVXK2RAQzKXGTEvrIyUW9KStl9Rh+cfKsLpJQLXdK b7BMMjNIdRCvxgtR78YsrYs5+AHV3m1YHt2rf/IlnMFY7455xEbTqkDFvCRWbXt1TL0a DQ1JPLUx0XP6UJcon9e5THDkixMXF6BScbi73UxY8wp8hSFrUOPiCD4I9C+68gWTm8sN OeUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lorfZcGqqwcvrfgjPN3L4FpYiXRnLRfq8PAWJbAsXjM=; b=ir6wCm0gKbR9szBGIUoyd5ASw4P3v1oJG7/YZ20i0jsTtskcMbUZ2ED+Nv9J9GdTeB s1N8OgtJP3jol9sCiNJaO5vff6u19d6Z6g4pllboc1iMQJO3oRPKwfmh9HD3vkQCiTrD ppw+9G37PUtzUCPrT/+ensdNTWHCcYcOypgAtGW8YwvaUsdmSn+9/KKB8kJtUlr3Kg/m T12putjd+7uNkNvGNKRccs4YF+7CTUfVhPPbY7aQsyTtpAjysc2hhhYwd2HLvPzaPnfv ivjlSiXwPx22HtSMiQeY8d/uuwiuPnCPvE34IXUkuCGVYIAO5FFWOrxJsDglMlTM2mKt s1iA==
X-Gm-Message-State: AA6/9Rmmb8UReqduBSuaiWfpY2jIfeMzd/AKMM9JUyFpRqrLqfLa7URE3iAUlByD8B+i7wGvN0RyQMSiMqrqtg==
X-Received: by 10.37.3.132 with SMTP id 126mr4924333ybd.64.1475503248487; Mon, 03 Oct 2016 07:00:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.160.10 with HTTP; Mon, 3 Oct 2016 07:00:07 -0700 (PDT)
In-Reply-To: <D41804D7.10437%christer.holmberg@ericsson.com>
References: <CABcZeBPpdyxiFbiHsqj=XwxFvOs4=z+R0zK0zoxbpixa25k3zQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BC722B7@ESESSMB209.ericsson.se> <CABcZeBP_Rcd3_pmEcAoQVOeKV_mtStM+31Gz+6eqR4hDvHNemA@mail.gmail.com> <D41804D7.10437%christer.holmberg@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 3 Oct 2016 07:00:07 -0700
Message-ID: <CABcZeBOa-zegdj1ZvP3==bac1ZXTLkkKe7y6SPk43F2EpfKDwQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a11c06d52fe3113053df65e58
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/tkblgJG0_azdaQSh34OMdWM7jXg>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2016 14:00:56 -0000

--001a11c06d52fe3113053df65e58
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 3, 2016 at 4:01 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> OVERALL
>>
>>
>>
>> >The overall framing of this document as being about attaching multiple
>>
>> >m=3D sections to a single "shared address" is extremely problematic,
>>
>> >for two reasons:
>>
>> >
>>
>> >- With ICE there isn't actually any notion of a shared address except
>>
>> >  in some vague sense. I suppose you could argue that because with
>>
>> >  ICE you are required to specify a port on the m=3D line then you
>>
>> >  still have a concept of an address, but that's not true in
>>
>> >  trickle ICE, where the port is 9, so all m=3D lines share the same
>>
>> >  address/port. So, actually when you use trickle a whole bunch of
>>
>> >  the statements in this document are wrong.
>>
>> >
>>
>> >- A lot more is being overloaded here than addresses. In fact, a whole
>>
>> >  pile of semantics are being overloaded, so the way to think about
>>
>> >  this is actually as gluing a whole bunch of m=3D lines together at
>>
>> >  the transport level.
>>
>> >
>>
>> > I think the right concept here is not "shared address" but "bundle
>> group"
>>
>> > and the document should be written in that way, namely that there are
>>
>> > a  bunch of m=3D lines in a bundle group and the one with the bundle t=
ag
>>
>> > is the one that sets all the shared parameters.
>>
>>
>>
>> It is true that the actual port value in the m- line, and the IP address
>> in the c- line address, represent the address that is actually being use=
d.
>>
>>
>>
>> But, even with ICE there is a shared address, isn=E2=80=99t there? Yes, =
that
>> shared address may change, but at any given time there will be one addre=
ss
>> that is shared among the media streams within the BUNDLE group. Or?
>>
>
> Not if you trickle, no. Then all the m=3D lines have the same address
> whether they are bundled or not.
>
>
> Ok, I hear you. You are basically saying that it doesn=E2=80=99t matter w=
hether
> bundled m- lines share addresses or not =E2=80=93 the ONLY thing that mat=
ters is
> that the m- line associated with the bundle tag contains the address to b=
e
> used.
>
> The reason we mandated shared addresses, once the usage of BUNDLE had bee=
n
> negotiated, was because of intermediaries that don=E2=80=99t support BUND=
LE (to
> make sure they send media towards the correct address). But, maybe we don=
=E2=80=99t
> need to worry about anymore =E2=80=93 BUNDLE probably won=E2=80=99t work =
reliably with
> such intermediaries anyway=E2=80=A6
>
> Also, there is at least once case where the address matters: when you add
> a new m- line to a bundle group. If you use a unique address, and the
> answerer does not accept the m- line in the BUNDLE group, it can be used
> un-bundled. If you use a shared address, the answerer will have to reject
> the m- line.
>

I think this is all true, but what I am trying to say here is, I think,
conceptually different:

BUNDLED m=3D lines are grouped together and share a bunch of properties.
Amongst those properties is that they share IP addresses, but it's not the
only thing they share, nor is it it the indicator that they are shared
(that's the a=3Dgroup:BUNDLE list). So the top-line category isn't shared
vs/unique IP address but rather bundled vs. unbundled.


>S 5.
>>
>> >The first three grafs of this section seem to duplicate the intro
>>
>> >and the abstract.
>>
>> >
>>
>> >Also, this claim about sharing a 5-tuple is not quite right with ICE
>>
>> >because ICE can switch 5-tuples during aggressive nomination.
>>
>>
>>
>> Yes. But, at any given time there will only be one 5-tuple, won=E2=80=99=
t it?
>>
>
> Not really no, no, because it's asymmetrical.
>
> Say that we have two candidate pairs A and B with B higher priority than =
A.
> The controlling endpoint sends checks on A and B but the initial check fo=
r
> A is dropped
> whereas the one for B is not. This establishes a flow on B at which point
> both controlling
> and controlled endpoints are sending on B. Then the controlling endpoint
> retransmits the
> check for A. At the point when the controlled endpoint receives that chec=
k
> it starts transmitting
> on A, but the controlling endpoint is still sending on B. So, the
> controlled endpoint has to
> simultaneously transmit on A but send on B.
>
> Sure, different 5-tuples may be used in each direction, as indicated in
> the two first paragraphs.
>
> I guess we could remove =E2=80=9C5-tuple=E2=80=9D text in the 3rd paragra=
ph, and only say
> that all media associated with a BUNDLE group is sent using the same
> transport layer protocol.
>

I think that would be better.


>S 8.1.
>>
>> >This seems like a key concept: there are a number of different categori=
es
>>
>> >of attributes and some are shared with all members of a bundle group
>>
>> >and some are not. To what extent is this draft just duplicative of thos=
e
>>
>> >listed in the mux-attributes draft?
>>
>>
>>
>> Not sure I understand the question.
>>
>
> My point is that the concept you need to know for *this draft* is:
>
> - Some attributes are shared and some are not.
>
> The detailed rules are defined in the mux attributes draft, right?
>
>
> Yes. So, perhaps we should not use RFC2119 terminology in draft-bundle,
> but simple refer to draft-mux-attributes for the rules.
>

That would be my recommendation.



> >S 8.5.
>>
>> >How does this interact with ICE Restart?
>>
>>
>>
>> From a pure ICE Restart perspective, I don=E2=80=99t see any conflict. I=
CE
>> Restart is triggered by changing the user name and password, and the tex=
t
>> does not forbid that.
>>
>>
>>
>> If you also want to change the BUNDLE address, you follow the rules in
>> section 8.5.1.
>>
>
> My concern is this text "   These rules imply that setting the IP address
> in the c line to
>
>    0.0.0.0 will cause an ICE restart.  Consequently, ICE implementations
>    MUST NOT utilize this mechanism for call hold, and instead MUST use
>
>    a=3Dinactive and a=3Dsendonly as described in [RFC3264
> <https://tools.ietf.org/html/rfc3264>]."
>
> Correct. So, if you use BUNDLE and want to trigger an ICE restart, you do
> as described above. BUNDLE does not define usage of 0.0.0.0 in the c line=
,
> so there should be no conflict.
>
> Or, do I still misunderstand you issue?
>

OK. I'll think about it some more and let you know if I still think there's
an issue.



> >S 8.5.2
>>
>> >When you say "extend" do you mean "add to the end"?
>>
>>
>>
>> Yes. I can fix that.
>>
>>
>>
>>
>>
>> >S 10.1
>>
>> >In this first bullet is "if" "iff"?
>>
>>
>>
>> =E2=80=9Ciff=E2=80=9D?
>>
>
> "if and only if"
>
>  It=E2=80=99s =E2=80=9Ciff=E2=80=9D.
>

It should say so, then, I think.




> >S 10.3.1.1.
>>
>> >   When an offerer generates an initial offer, the offerer MUST
>>
>> >   associate either an SDP 'rtcp-mux' attribute [RFC5761] or an SDP
>>
>> >   'rtcp-mux-only' attribute [I-D.ietf-mmusic-mux-exclusive] with each
>>
>> >   bundled RTP-based "m=3D" line in the offer.  The offerer MUST associ=
ate
>>
>> >   an SDP 'rtcp-mux-only' attribute with each bundle-only "m=3D" line. =
 If
>>
>> >   the offerer associates a 'rtcp-mux-only' attribute with an "m=3D" li=
ne,
>>
>> >   the offerer may also associate a 'rtcp-mux' attribute with the same
>>
>> >   "m=3D" line, as described in [I-D.ietf-mmusic-mux-exclusive].
>>
>> >
>>
>> > This is a particularly egregious case of associate disease that could
>>
>> > be easily solved by using "add" when referring to the attributes
>>
>> > you put in the m=3D section.
>>
>>
>>
>> People have previously said that you don=E2=80=99t =E2=80=9Cadd=E2=80=9D=
 attributes to m- lines:
>> you add port values etc, but not attributes.
>>
>>
>>
>> This is an example of where I=E2=80=99ve had to re-write big parts of th=
e
>> documents a number of times already, because every time someone else rea=
ds
>> the document he/she is not happy with the terminology. I just don=E2=80=
=99t want to
>> do it again.
>>
>
> The terminology that JSEP uses is that "m=3D sections" include attribute
> lines.
>
> I think this is a lot clearer.
>
>  I don=E2=80=99t personally disagree, but there are people that have had =
other
> opinions.
>
>  In general I think it would be really useful to have common terminology
> in BUNDLE and JSEP, but I don=E2=80=99t want to re-write the document onc=
e again,
> and then later be told to do it again=E2=80=A6
>

Resolving the appropriate terminology seems like a chair issue.

-Ekr


> Regards,
>
> Christer
>
>
>

--001a11c06d52fe3113053df65e58
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Oct 3, 2016 at 4:01 AM, Christer Holmberg <span dir=3D"ltr">&lt=
;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christ=
er.holmberg@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">



<div style=3D"word-wrap:break-word">
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
Hi,</div><span class=3D"">
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<br>
</div>
<span style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,=
0)">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<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 lang=3D"EN-GB">
<div><span>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">OVERALL<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;The overall framing of this document as being a=
bout attaching multiple<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;m=3D sections to a single &quot;shared address&=
quot; is extremely problematic,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;for two reasons:<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;- With ICE there isn&#39;t actually any notion =
of a shared address except<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0in some vague sense. I suppose you could=
 argue that because with<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0ICE you are required to specify a port o=
n the m=3D line then you<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0still have a concept of an address, but =
that&#39;s not true in<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0trickle ICE, where the port is 9, so all=
 m=3D lines share the same<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0address/port. So, actually when you use =
trickle a whole bunch of<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0the statements in this document are wron=
g.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;- A lot more is being overloaded here than addr=
esses. In fact, a whole<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0pile of semantics are being overloaded, =
so the way to think about<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0this is actually as gluing a whole bunch=
 of m=3D lines together at<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0the transport level.<u></u><u></u></span=
></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; I think the right concept here is not &quot;sh=
ared address&quot; but &quot;bundle group&quot;<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; and the document should be written in that way=
, namely that there are<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; a =C2=A0bunch of m=3D lines in a bundle group =
and the one with the bundle tag<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; is the one that sets all the shared parameters=
.<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">It is true that the actual port value in the m- lin=
e, and the IP address in the c- line address, represent the address that is=
 actually being used.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">But, even with ICE there is a shared address, isn=
=E2=80=99t there? Yes, that shared address may change, but at any given tim=
e there will be one address that is shared among
 the media streams within the BUNDLE group. Or?</span></p>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Not if you trickle, no. Then all the m=3D lines have the same address =
whether they are bundled or not.</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<br>
</div>
</span><div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rg=
b(0,0,0)">
<font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">Ok, I hear you. Y=
ou are basically saying that it doesn=E2=80=99t matter whether bundled m- l=
ines share addresses or not=C2=A0=E2=80=93=C2=A0the ONLY thing that matters=
 is that the m- line associated with the bundle tag contains the
 address to be used.</font></font></div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<font color=3D"#ff0000"><font face=3D"Calibri,sans-serif"><br>
</font></font></div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">The reason we man=
dated shared addresses, once the usage of BUNDLE had been negotiated, was b=
ecause of intermediaries that don=E2=80=99t support BUNDLE (to make sure th=
ey send media towards the correct address).
 But, maybe we don=E2=80=99t need to worry about anymore=C2=A0=E2=80=93=C2=
=A0BUNDLE=C2=A0probably won=E2=80=99t work reliably with such=C2=A0intermed=
iaries anyway</font></font><font color=3D"#ff0000" face=3D"Calibri,sans-ser=
if">=E2=80=A6</font></div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<font color=3D"#ff0000" face=3D"Calibri,sans-serif"><br>
</font></div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<font color=3D"#ff0000" face=3D"Calibri,sans-serif">Also, there is at least=
 once case where the address matters: when you add a new m- line to a bundl=
e group. If you use a unique address, and the answerer does not accept the =
m- line in the BUNDLE group, it can
 be used un-bundled. If you use a shared address, the answerer will have to=
 reject the m- line.</font></div></div></blockquote><div><br></div><div>I t=
hink this is all true, but what I am trying to say here is, I think, concep=
tually different:</div><div><br></div><div>BUNDLED m=3D lines are grouped t=
ogether and share a bunch of properties. Amongst those properties is that t=
hey share IP addresses, but it&#39;s not the only thing they share, nor is =
it it the indicator that they are shared (that&#39;s the a=3Dgroup:BUNDLE l=
ist). So the top-line category isn&#39;t shared vs/unique IP address but ra=
ther bundled vs. unbundled.=C2=A0</div><div><br></div><div><br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><span class=3D=
""><span style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0=
,0,0)"><div><div><div dir=3D"ltr"><div class=3D"gmail_extra"><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 lang=3D"EN-GB"><span>
<div>
<div>
<div>
<div></div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 5.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;The first three grafs of this section seem to d=
uplicate the intro<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;and the abstract.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;Also, this claim about sharing a 5-tuple is not=
 quite right with ICE<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;because ICE can switch 5-tuples during aggressi=
ve nomination.<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Yes. But, at any given time there will only be one =
5-tuple, won=E2=80=99t it?</span></p>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Not really no, no, because it&#39;s asymmetrical.</div>
<div><br>
</div>
<div>Say that we have two candidate pairs A and B with B higher priority th=
an A.</div>
<div>The controlling endpoint sends checks on A and B but the initial check=
 for A is dropped</div>
<div>whereas the one for B is not. This establishes a flow on B at which po=
int both controlling<br>
</div>
<div>and controlled endpoints are sending on B. Then the controlling endpoi=
nt retransmits the</div>
<div>check for A. At the point when the controlled endpoint receives that c=
heck it starts transmitting</div>
<div>on A, but the controlling endpoint is still sending on B. So, the cont=
rolled endpoint has to</div>
<div>simultaneously transmit on A but send on B.</div>
<div>=C2=A0</div>
</div>
</div>
</div>
</div>
</div>
</span>
</span><div style=3D"font-family:Calibri,sans-serif;font-size:14px"><font c=
olor=3D"#ff0000">Sure, different 5-tuples may be used in each direction, as=
 indicated in the two first paragraphs.</font></div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px"><font color=3D=
"#ff0000"><br>
</font></div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px"><font color=3D=
"#ff0000">I guess we could remove =E2=80=9C5-tuple=E2=80=9D text in the 3rd=
 paragraph, and only say that all media associated with a BUNDLE group is s=
ent using the same transport layer protocol.</font></div></div></blockquote=
><div><br></div><div>I think that would be better.</div><div><br></div><div=
><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-wor=
d"><span class=3D""><span style=3D"font-family:Calibri,sans-serif;font-size=
:14px"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quot=
e"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204=
);padding-left:1ex"><div lang=3D"EN-GB"><span><div>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 8.1.<u></u><u></u></span></p>
</div>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;This seems like a key concept: there are a numb=
er of different categories<u></u><u></u></span></p>
</div>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;of attributes and some are shared with all memb=
ers of a bundle group<u></u><u></u></span></p>
</div>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;and some are not. To what extent is this draft =
just duplicative of those<u></u><u></u></span></p>
</div>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;listed in the mux-attributes draft?<u></u><u></=
u></span></p>
</div>
</div>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Not sure I understand the question.</span></p>
</div>
</div>
</blockquote>
<div style=3D"color:rgb(0,0,0)"><br>
</div>
<div style=3D"color:rgb(0,0,0)">My point is that the concept you need to kn=
ow for *this draft* is:</div>
<div style=3D"color:rgb(0,0,0)"><br>
</div>
<div style=3D"color:rgb(0,0,0)">- Some attributes are shared and some are n=
ot.</div>
<div style=3D"color:rgb(0,0,0)"><br>
</div>
<div style=3D"color:rgb(0,0,0)">The detailed rules are defined in the mux a=
ttributes draft, right?</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
</span><div><font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">Yes. =
So, perhaps we should not use RFC2119 terminology in draft-bundle, but simp=
le refer to=C2=A0draft-mux-attributes for the rules.=C2=A0</font></font></d=
iv></div></blockquote><div><br></div><div>That would be my recommendation.<=
/div><div><span style=3D"color:black;font-family:calibri,sans-serif;font-si=
ze:10.5pt"><br></span></div><div><span style=3D"color:black;font-family:cal=
ibri,sans-serif;font-size:10.5pt">=C2=A0</span></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"><div style=3D"word-wrap:break-word"><span><div dir=3D"ltr"><div cl=
ass=3D"gmail_extra"><div class=3D"gmail_quote"><span class=3D""><blockquote=
 class=3D"gmail_quote" style=3D"font-family:Calibri,sans-serif;font-size:14=
px;color:rgb(0,0,0);margin:0px 0px 0px 0.8ex;border-left-width:1px;border-l=
eft-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div lang=3D"EN-GB">
<div>
<div>
<div>
<div><span>
<div></div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 8.5.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;How does this interact with ICE Restart?<u></u>=
<u></u></span></p>
</div>
</span></div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">From a pure ICE Restart perspective, I don=E2=80=99=
t see any conflict. ICE Restart is triggered by changing the user name and =
password, and the text does not forbid that.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">If you also want to change the BUNDLE address, you =
follow the rules in section 8.5.1.</span></p>
</div>
</div>
</div>
</blockquote>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
My concern is this text &quot; =C2=A0 These rules imply that setting the IP=
 address in the c line to</div>
<pre style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">   0.0.0.0 will cause an ICE restart.  Consequently, ICE implementations
   MUST NOT utilize this mechanism for call hold, and instead MUST use=C2=
=A0</pre>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
=C2=A0 =C2=A0a=3Dinactive and a=3Dsendonly as described in [<a href=3D"http=
s://tools.ietf.org/html/rfc3264" title=3D"&quot;An Offer/Answer Model with =
Session Description Protocol (SDP)&quot;" target=3D"_blank">RFC3264</a>].&q=
uot;</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<br>
</div>
</span><div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rg=
b(0,0,0)">
<span style=3D"color:rgb(255,0,0);font-size:medium">Correct. So, if you use=
 BUNDLE and want to trigger an ICE restart, you do as described above. BUND=
LE does not define usage of 0.0.0.0 in the c line, so there should be no co=
nflict.</span></div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div><font color=3D"#ff0000">Or, do I still misunderstand you issue?</font>=
</div></div></blockquote><div>=C2=A0</div><div>OK. I&#39;ll think about it =
some more and let you know if I still think there&#39;s an issue.</div><div=
><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"wo=
rd-wrap:break-word"><span class=3D""><span><div dir=3D"ltr"><div class=3D"g=
mail_extra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"font-family:Calibri,sans-serif;f=
ont-size:14px;color:rgb(0,0,0);margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:=
1ex">
<div lang=3D"EN-GB">
<div><span>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 8.5.2<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;When you say &quot;extend&quot; do you mean &qu=
ot;add to the end&quot;?<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Yes. I can fix that.<u></u><u></u></span></p>
</div>
<span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 10.1<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;In this first bullet is &quot;if&quot; &quot;if=
f&quot;?<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">=E2=80=9Ciff=E2=80=9D?</span></p>
</div>
</div>
</div>
</blockquote>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
&quot;if and only if&quot;</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
=C2=A0</div>
</div>
</div>
</div>
</span>
</span><div><font color=3D"#ff0000">=C2=A0It=E2=80=99s=C2=A0=E2=80=9Ciff=E2=
=80=9D.</font></div></div></blockquote><div><br></div><div>It should say so=
, then, I think.</div><div><br></div><div><br></div><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><span class=3D=
""><span><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_qu=
ote"><div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(=
0,0,0)"></div>
<blockquote class=3D"gmail_quote" style=3D"font-family:Calibri,sans-serif;f=
ont-size:14px;color:rgb(0,0,0);margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:=
1ex">
<div lang=3D"EN-GB">
<div><span>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 10.3.1.1.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 When an offerer generates an initial of=
fer, the offerer MUST<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 associate either an SDP &#39;rtcp-mux&#=
39; attribute [RFC5761] or an SDP<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 &#39;rtcp-mux-only&#39; attribute [I-D.=
ietf-mmusic-mux-exclusive<wbr>] with each<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 bundled RTP-based &quot;m=3D&quot; line=
 in the offer.=C2=A0 The offerer MUST associate<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 an SDP &#39;rtcp-mux-only&#39; attribut=
e with each bundle-only &quot;m=3D&quot; line.=C2=A0 If<u></u><u></u></span=
></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 the offerer associates a &#39;rtcp-mux-=
only&#39; attribute with an &quot;m=3D&quot; line,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 the offerer may also associate a &#39;r=
tcp-mux&#39; attribute with the same<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; =C2=A0 &quot;m=3D&quot; line, as described in =
[I-D.ietf-mmusic-mux-exclusive<wbr>].<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; This is a particularly egregious case of assoc=
iate disease that could<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; be easily solved by using &quot;add&quot; when=
 referring to the attributes<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt; you put in the m=3D section.<u></u><u></u></sp=
an></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</span>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">People have previously said that you don=E2=80=99t =
=E2=80=9Cadd=E2=80=9D attributes to m- lines: you add port values etc, but =
not attributes.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">This is an example of where I=E2=80=99ve had to re-=
write big parts of the documents a number of times already, because every t=
ime someone else reads the document he/she is
 not happy with the terminology. I just don=E2=80=99t want to do it again.<=
/span></p>
</div>
</div>
</div>
</blockquote>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
The terminology that JSEP uses is that &quot;m=3D sections&quot; include at=
tribute lines.</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<span style=3D"color:black;font-family:calibri,sans-serif;font-size:10.5pt"=
><br>
</span></div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<span style=3D"color:black;font-family:calibri,sans-serif;font-size:10.5pt"=
>I think this is a lot clearer.</span></div>
</div>
</div>
</div>
</span>
<div><br>
</div>
</span><div>
<div><font color=3D"#ff0000">=C2=A0I don=E2=80=99t personally disagree, but=
 there are people that have had other opinions.</font></div>
<span>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote"></div>
</div>
</div>
</span></div>
<div><br>
</div>
<span>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><font color=3D"#ff0000">=C2=A0In general I think it would be=C2=A0real=
ly useful to have common=C2=A0terminology in BUNDLE and JSEP, but I don=E2=
=80=99t want to re-write the document once again, and then later be told to=
 do it again=E2=80=A6</font></div></div></div></div></span></div></blockquo=
te><div><br></div><div>Resolving the appropriate terminology seems like a c=
hair issue.</div><div><br></div><div>-Ekr</div><div><br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div style=3D"word-wrap:break-word"><span><div dir=3D"ltr=
"><div class=3D"gmail_extra"><div class=3D"gmail_quote">
</div>
</div>
</div>
</span>
<div><br>
</div>
<div><font color=3D"#ff0000">Regards,</font></div>
<div><font color=3D"#ff0000"><br>
</font></div>
<div><font color=3D"#ff0000">Christer</font></div>
<div><br>
</div>
<div><br>
</div>
</div>

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

--001a11c06d52fe3113053df65e58--


From nobody Mon Oct  3 13:07:08 2016
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 E4DF0129507 for <mmusic@ietfa.amsl.com>; Mon,  3 Oct 2016 13:07:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 xttu0p-PWmEh for <mmusic@ietfa.amsl.com>; Mon,  3 Oct 2016 13:07:04 -0700 (PDT)
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 1EEE4129510 for <mmusic@ietf.org>; Mon,  3 Oct 2016 13:07:03 -0700 (PDT)
X-AuditID: c1b4fb30-b87ff70000000cb2-fc-57f2ba6482b6
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by  (Symantec Mail Security) with SMTP id CC.8B.03250.46AB2F75; Mon,  3 Oct 2016 22:07:02 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0319.002; Mon, 3 Oct 2016 22:07:00 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I)
Thread-Index: AQHSAjFbVSmCBcGmbka3UICv6Cl9oaCV9LgAgADkVID///3vgIAAgk6A
Date: Mon, 3 Oct 2016 20:07:00 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD14B37@ESESSMB209.ericsson.se>
References: <CABcZeBPpdyxiFbiHsqj=XwxFvOs4=z+R0zK0zoxbpixa25k3zQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BC722B7@ESESSMB209.ericsson.se> <CABcZeBP_Rcd3_pmEcAoQVOeKV_mtStM+31Gz+6eqR4hDvHNemA@mail.gmail.com> <D41804D7.10437%christer.holmberg@ericsson.com> <CABcZeBOa-zegdj1ZvP3==bac1ZXTLkkKe7y6SPk43F2EpfKDwQ@mail.gmail.com>
In-Reply-To: <CABcZeBOa-zegdj1ZvP3==bac1ZXTLkkKe7y6SPk43F2EpfKDwQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BD14B37ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKIsWRmVeSWpSXmKPExsUyM2K7n27ark/hBjfOM1useH2O3WLq8scs DkweS5b8ZPKY/LiNOYApissmJTUnsyy1SN8ugSvj1N25TAU/zjFWPOw7ytLAuOckYxcjJ4eE gInE558LWUBsIYH1jBInj6V0MXIB2YsYJXafugaU4OBgE7CQ6P6nDVIjIqAg8evPCbB6ZgF5 iQtL1jCB2MICYRIv589hhqgJlzj89D8ThO0m8fnYBLB6FgEViU+n1rCB2LwCvhJ3Pz5lgth1 hUli9aEDrCAJToFAiUOH74INYhQQk/h+CmIBs4C4xK0n85kgjhaQWLLnPDOELSrx8vE/Vghb SWLR7c9Q9fkS29f+YYVYJihxcuYTlgmMIrOQjJqFpGwWkrJZQC8zC2hKrN+lD1GiKDGl+yE7 hK0h0TpnLjuy+AJG9lWMosWpxUm56UZGeqlFmcnFxfl5enmpJZsYgZF1cMtvgx2ML587HmIU 4GBU4uFNSPkULsSaWFZcmXuIUYKDWUmEV2o7UIg3JbGyKrUoP76oNCe1+BCjNAeLkjiv2cr7 4UIC6YklqdmpqQWpRTBZJg5OqQZGzaj9l5svM0/tkNrOdu56lJeh2GtHt5j9b0/Lyvy++ii5 9Mf1d0elxS/8bD+scOFpr7zp+eWVy/90fTKU8df3ap6pqjTLOeDHhe8X5fsO5y89fcTMd4tG QrfRm42TrmyN//dWnmnfXg02va2aAp8DJrb9dDh6fsNV91Ntf494PZkoYBo046vnLCWW4oxE Qy3mouJEAKK7J5eoAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/OMGra2ucsX8-0WLEhsyIb3X0lyY>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2016 20:07:07 -0000

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

SGksDQoNCk9WRVJBTEwNCg0KPlRoZSBvdmVyYWxsIGZyYW1pbmcgb2YgdGhpcyBkb2N1bWVudCBh
cyBiZWluZyBhYm91dCBhdHRhY2hpbmcgbXVsdGlwbGUNCj5tPSBzZWN0aW9ucyB0byBhIHNpbmds
ZSAic2hhcmVkIGFkZHJlc3MiIGlzIGV4dHJlbWVseSBwcm9ibGVtYXRpYywNCj5mb3IgdHdvIHJl
YXNvbnM6DQo+DQo+LSBXaXRoIElDRSB0aGVyZSBpc24ndCBhY3R1YWxseSBhbnkgbm90aW9uIG9m
IGEgc2hhcmVkIGFkZHJlc3MgZXhjZXB0DQo+ICBpbiBzb21lIHZhZ3VlIHNlbnNlLiBJIHN1cHBv
c2UgeW91IGNvdWxkIGFyZ3VlIHRoYXQgYmVjYXVzZSB3aXRoDQo+ICBJQ0UgeW91IGFyZSByZXF1
aXJlZCB0byBzcGVjaWZ5IGEgcG9ydCBvbiB0aGUgbT0gbGluZSB0aGVuIHlvdQ0KPiAgc3RpbGwg
aGF2ZSBhIGNvbmNlcHQgb2YgYW4gYWRkcmVzcywgYnV0IHRoYXQncyBub3QgdHJ1ZSBpbg0KPiAg
dHJpY2tsZSBJQ0UsIHdoZXJlIHRoZSBwb3J0IGlzIDksIHNvIGFsbCBtPSBsaW5lcyBzaGFyZSB0
aGUgc2FtZQ0KPiAgYWRkcmVzcy9wb3J0LiBTbywgYWN0dWFsbHkgd2hlbiB5b3UgdXNlIHRyaWNr
bGUgYSB3aG9sZSBidW5jaCBvZg0KPiAgdGhlIHN0YXRlbWVudHMgaW4gdGhpcyBkb2N1bWVudCBh
cmUgd3JvbmcuDQo+DQo+LSBBIGxvdCBtb3JlIGlzIGJlaW5nIG92ZXJsb2FkZWQgaGVyZSB0aGFu
IGFkZHJlc3Nlcy4gSW4gZmFjdCwgYSB3aG9sZQ0KPiAgcGlsZSBvZiBzZW1hbnRpY3MgYXJlIGJl
aW5nIG92ZXJsb2FkZWQsIHNvIHRoZSB3YXkgdG8gdGhpbmsgYWJvdXQNCj4gIHRoaXMgaXMgYWN0
dWFsbHkgYXMgZ2x1aW5nIGEgd2hvbGUgYnVuY2ggb2YgbT0gbGluZXMgdG9nZXRoZXIgYXQNCj4g
IHRoZSB0cmFuc3BvcnQgbGV2ZWwuDQo+DQo+IEkgdGhpbmsgdGhlIHJpZ2h0IGNvbmNlcHQgaGVy
ZSBpcyBub3QgInNoYXJlZCBhZGRyZXNzIiBidXQgImJ1bmRsZSBncm91cCINCj4gYW5kIHRoZSBk
b2N1bWVudCBzaG91bGQgYmUgd3JpdHRlbiBpbiB0aGF0IHdheSwgbmFtZWx5IHRoYXQgdGhlcmUg
YXJlDQo+IGEgIGJ1bmNoIG9mIG09IGxpbmVzIGluIGEgYnVuZGxlIGdyb3VwIGFuZCB0aGUgb25l
IHdpdGggdGhlIGJ1bmRsZSB0YWcNCj4gaXMgdGhlIG9uZSB0aGF0IHNldHMgYWxsIHRoZSBzaGFy
ZWQgcGFyYW1ldGVycy4NCg0KSXQgaXMgdHJ1ZSB0aGF0IHRoZSBhY3R1YWwgcG9ydCB2YWx1ZSBp
biB0aGUgbS0gbGluZSwgYW5kIHRoZSBJUCBhZGRyZXNzIGluIHRoZSBjLSBsaW5lIGFkZHJlc3Ms
IHJlcHJlc2VudCB0aGUgYWRkcmVzcyB0aGF0IGlzIGFjdHVhbGx5IGJlaW5nIHVzZWQuDQoNCkJ1
dCwgZXZlbiB3aXRoIElDRSB0aGVyZSBpcyBhIHNoYXJlZCBhZGRyZXNzLCBpc27igJl0IHRoZXJl
PyBZZXMsIHRoYXQgc2hhcmVkIGFkZHJlc3MgbWF5IGNoYW5nZSwgYnV0IGF0IGFueSBnaXZlbiB0
aW1lIHRoZXJlIHdpbGwgYmUgb25lIGFkZHJlc3MgdGhhdCBpcyBzaGFyZWQgYW1vbmcgdGhlIG1l
ZGlhIHN0cmVhbXMgd2l0aGluIHRoZSBCVU5ETEUgZ3JvdXAuIE9yPw0KDQpOb3QgaWYgeW91IHRy
aWNrbGUsIG5vLiBUaGVuIGFsbCB0aGUgbT0gbGluZXMgaGF2ZSB0aGUgc2FtZSBhZGRyZXNzIHdo
ZXRoZXIgdGhleSBhcmUgYnVuZGxlZCBvciBub3QuDQoNCg0KT2ssIEkgaGVhciB5b3UuIFlvdSBh
cmUgYmFzaWNhbGx5IHNheWluZyB0aGF0IGl0IGRvZXNu4oCZdCBtYXR0ZXIgd2hldGhlciBidW5k
bGVkIG0tIGxpbmVzIHNoYXJlIGFkZHJlc3NlcyBvciBub3Qg4oCTIHRoZSBPTkxZIHRoaW5nIHRo
YXQgbWF0dGVycyBpcyB0aGF0IHRoZSBtLSBsaW5lIGFzc29jaWF0ZWQgd2l0aCB0aGUgYnVuZGxl
IHRhZyBjb250YWlucyB0aGUgYWRkcmVzcyB0byBiZSB1c2VkLg0KDQpUaGUgcmVhc29uIHdlIG1h
bmRhdGVkIHNoYXJlZCBhZGRyZXNzZXMsIG9uY2UgdGhlIHVzYWdlIG9mIEJVTkRMRSBoYWQgYmVl
biBuZWdvdGlhdGVkLCB3YXMgYmVjYXVzZSBvZiBpbnRlcm1lZGlhcmllcyB0aGF0IGRvbuKAmXQg
c3VwcG9ydCBCVU5ETEUgKHRvIG1ha2Ugc3VyZSB0aGV5IHNlbmQgbWVkaWEgdG93YXJkcyB0aGUg
Y29ycmVjdCBhZGRyZXNzKS4gQnV0LCBtYXliZSB3ZSBkb27igJl0IG5lZWQgdG8gd29ycnkgYWJv
dXQgYW55bW9yZSDigJMgQlVORExFIHByb2JhYmx5IHdvbuKAmXQgd29yayByZWxpYWJseSB3aXRo
IHN1Y2ggaW50ZXJtZWRpYXJpZXMgYW55d2F54oCmDQoNCkFsc28sIHRoZXJlIGlzIGF0IGxlYXN0
IG9uY2UgY2FzZSB3aGVyZSB0aGUgYWRkcmVzcyBtYXR0ZXJzOiB3aGVuIHlvdSBhZGQgYSBuZXcg
bS0gbGluZSB0byBhIGJ1bmRsZSBncm91cC4gSWYgeW91IHVzZSBhIHVuaXF1ZSBhZGRyZXNzLCBh
bmQgdGhlIGFuc3dlcmVyIGRvZXMgbm90IGFjY2VwdCB0aGUgbS0gbGluZSBpbiB0aGUgQlVORExF
IGdyb3VwLCBpdCBjYW4gYmUgdXNlZCB1bi1idW5kbGVkLiBJZiB5b3UgdXNlIGEgc2hhcmVkIGFk
ZHJlc3MsIHRoZSBhbnN3ZXJlciB3aWxsIGhhdmUgdG8gcmVqZWN0IHRoZSBtLSBsaW5lLg0KDQpJ
IHRoaW5rIHRoaXMgaXMgYWxsIHRydWUsIGJ1dCB3aGF0IEkgYW0gdHJ5aW5nIHRvIHNheSBoZXJl
IGlzLCBJIHRoaW5rLCBjb25jZXB0dWFsbHkgZGlmZmVyZW50Og0KDQpCVU5ETEVEIG09IGxpbmVz
IGFyZSBncm91cGVkIHRvZ2V0aGVyIGFuZCBzaGFyZSBhIGJ1bmNoIG9mIHByb3BlcnRpZXMuIEFt
b25nc3QgdGhvc2UgcHJvcGVydGllcyBpcyB0aGF0IHRoZXkgc2hhcmUgSVAgYWRkcmVzc2VzLCBi
dXQgaXQncyBub3QgdGhlIG9ubHkgdGhpbmcgdGhleSBzaGFyZSwgbm9yIGlzIGl0IGl0IHRoZSBp
bmRpY2F0b3IgdGhhdCB0aGV5IGFyZSBzaGFyZWQgKHRoYXQncyB0aGUgYT1ncm91cDpCVU5ETEUg
bGlzdCkuIFNvIHRoZSB0b3AtbGluZSBjYXRlZ29yeSBpc24ndCBzaGFyZWQgdnMvdW5pcXVlIElQ
IGFkZHJlc3MgYnV0IHJhdGhlciBidW5kbGVkIHZzLiB1bmJ1bmRsZWQuDQoNCkNvcnJlY3QuDQoN
ClRoZSBiZXN0IHRoaW5nLCBhcyBmYXIgYXMgdGhlIGFkZHJlc3MgaW4gdGhlIG0tIGxpbmUgaXMg
Y29uY2VybmVkLCB3b3VsZCBiZSB0byBzaW1wbHkgdXNlIG5vcm1hbCBTRFAgcHJvY2VkdXJlcyAo
cmVhZDogdW5pcXVlIGFkZHJlc3NlcykgYWxzbyBmb3IgYnVuZGxlZCBtLSBsaW5lcy4gQW5kLCBp
ZiB0aGUgb2ZmZXJlciB3YW50cyB0byBtYWtlIHN1cmUgYSBtaWQtc2Vzc2lvbiBhZGRlZCBtLSBs
aW5lIGdldHMgYWNjZXB0ZWQgaW4gdGhlIGJ1bmRsZSBncm91cCAob3Igb3RoZXJ3aXNlIGlzIHJl
amVjdGVkKSBoZSB3b3VsZCB1c2UgYnVuZGxlLW9ubHkg4oCTIGluIHRoZSBzYW1lIHdheSBpdOKA
mXMgdXNlZCBpbiB0aGUgaW5pdGlhbCBvZmZlci4NCg0KVGhlbiBhIOKAnHNoYXJlZCBhZGRyZXNz
4oCdIHdvdWxkIG9ubHkgYmUgYSBwcm9wZXJ0eSBvZiB0aGUgQlVORExFIGdyb3VwIOKAkyBub3Qg
cmVsYXRlZCB0byB0aGUgYWRkcmVzcyBwdXQgaW4gdGhlIG0tIGxpbmUuDQoNClJlZ2FyZHMsDQoN
CkNocmlzdGVyDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnByZQ0K
CXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0
dGVkIENoYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt
c2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpzcGFuLkhUTUxQcmVm
b3JtYXR0ZWRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsN
Cgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0
dGVkIjsNCglmb250LWZhbWlseTpDb25zb2xhczsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1H
Qjt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250
LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1h
aWxTdHlsZTIwDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLWNvbXBvc2U7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVm
YXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsc2Fucy1zZXJpZjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3Jk
U2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQg
NzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30N
Ci0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6
ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBn
dGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2
OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0t
LT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLUdCIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxl
Ij4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+SGks
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNt
IDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2
Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAw
Y20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPk9WRVJBTEw8L3NwYW4+PHNwYW4gc3R5bGU9
ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZndDtU
aGUgb3ZlcmFsbCBmcmFtaW5nIG9mIHRoaXMgZG9jdW1lbnQgYXMgYmVpbmcgYWJvdXQgYXR0YWNo
aW5nIG11bHRpcGxlPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6YmxhY2siPiZndDttPSBzZWN0aW9ucyB0byBhIHNpbmdsZSAmcXVvdDtz
aGFyZWQgYWRkcmVzcyZxdW90OyBpcyBleHRyZW1lbHkgcHJvYmxlbWF0aWMsPC9zcGFuPjxzcGFu
IHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZn
dDtmb3IgdHdvIHJlYXNvbnM6PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZndDsmbmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9
ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jmd0Oy0gV2l0
aCBJQ0UgdGhlcmUgaXNuJ3QgYWN0dWFsbHkgYW55IG5vdGlvbiBvZiBhIHNoYXJlZCBhZGRyZXNz
IGV4Y2VwdDwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOmJsYWNrIj4mZ3Q7ICZuYnNwO2luIHNvbWUgdmFndWUgc2Vuc2UuIEkgc3VwcG9z
ZSB5b3UgY291bGQgYXJndWUgdGhhdCBiZWNhdXNlIHdpdGg8L3NwYW4+PHNwYW4gc3R5bGU9ImNv
bG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jmd0OyAmbmJzcDtJ
Q0UgeW91IGFyZSByZXF1aXJlZCB0byBzcGVjaWZ5IGEgcG9ydCBvbiB0aGUgbT0gbGluZSB0aGVu
IHlvdTwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOmJsYWNrIj4mZ3Q7ICZuYnNwO3N0aWxsIGhhdmUgYSBjb25jZXB0IG9mIGFuIGFkZHJl
c3MsIGJ1dCB0aGF0J3Mgbm90IHRydWUgaW48L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNr
Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jmd0OyAmbmJzcDt0cmlja2xlIElD
RSwgd2hlcmUgdGhlIHBvcnQgaXMgOSwgc28gYWxsIG09IGxpbmVzIHNoYXJlIHRoZSBzYW1lPC9z
cGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
YmxhY2siPiZndDsgJm5ic3A7YWRkcmVzcy9wb3J0LiBTbywgYWN0dWFsbHkgd2hlbiB5b3UgdXNl
IHRyaWNrbGUgYSB3aG9sZSBidW5jaCBvZjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2si
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mZ3Q7ICZuYnNwO3RoZSBzdGF0ZW1l
bnRzIGluIHRoaXMgZG9jdW1lbnQgYXJlIHdyb25nLjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6
YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mZ3Q7Jm5ic3A7PC9zcGFu
PjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Ymxh
Y2siPiZndDstIEEgbG90IG1vcmUgaXMgYmVpbmcgb3ZlcmxvYWRlZCBoZXJlIHRoYW4gYWRkcmVz
c2VzLiBJbiBmYWN0LCBhIHdob2xlPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZndDsgJm5ic3A7cGlsZSBvZiBzZW1hbnRp
Y3MgYXJlIGJlaW5nIG92ZXJsb2FkZWQsIHNvIHRoZSB3YXkgdG8gdGhpbmsgYWJvdXQ8L3NwYW4+
PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFj
ayI+Jmd0OyAmbmJzcDt0aGlzIGlzIGFjdHVhbGx5IGFzIGdsdWluZyBhIHdob2xlIGJ1bmNoIG9m
IG09IGxpbmVzIHRvZ2V0aGVyIGF0PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZndDsgJm5ic3A7dGhlIHRyYW5zcG9ydCBs
ZXZlbC48L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjpibGFjayI+Jmd0OyZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2si
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mZ3Q7IEkgdGhpbmsgdGhlIHJpZ2h0
IGNvbmNlcHQgaGVyZSBpcyBub3QgJnF1b3Q7c2hhcmVkIGFkZHJlc3MmcXVvdDsgYnV0ICZxdW90
O2J1bmRsZSBncm91cCZxdW90Ozwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mZ3Q7IGFuZCB0aGUgZG9jdW1lbnQgc2hvdWxk
IGJlIHdyaXR0ZW4gaW4gdGhhdCB3YXksIG5hbWVseSB0aGF0IHRoZXJlIGFyZTwvc3Bhbj48c3Bh
biBzdHlsZT0iY29sb3I6YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4m
Z3Q7IGEgJm5ic3A7YnVuY2ggb2YgbT0gbGluZXMgaW4gYSBidW5kbGUgZ3JvdXAgYW5kIHRoZSBv
bmUgd2l0aCB0aGUgYnVuZGxlIHRhZzwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mZ3Q7IGlzIHRoZSBvbmUgdGhhdCBzZXRz
IGFsbCB0aGUgc2hhcmVkIHBhcmFtZXRlcnMuPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFj
ayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Ymxh
Y2siPiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOmJsYWNrIj5JdCBpcyB0cnVlIHRoYXQgdGhlIGFjdHVhbCBwb3J0IHZhbHVl
IGluIHRoZSBtLSBsaW5lLCBhbmQgdGhlIElQIGFkZHJlc3MgaW4gdGhlIGMtIGxpbmUgYWRkcmVz
cywgcmVwcmVzZW50DQogdGhlIGFkZHJlc3MgdGhhdCBpcyBhY3R1YWxseSBiZWluZyB1c2VkLjwv
c3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mbmJzcDs8
L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+QnV0LCBl
dmVuIHdpdGggSUNFIHRoZXJlIGlzIGEgc2hhcmVkIGFkZHJlc3MsIGlzbuKAmXQgdGhlcmU/IFll
cywgdGhhdCBzaGFyZWQgYWRkcmVzcyBtYXkgY2hhbmdlLCBidXQgYXQNCiBhbnkgZ2l2ZW4gdGlt
ZSB0aGVyZSB3aWxsIGJlIG9uZSBhZGRyZXNzIHRoYXQgaXMgc2hhcmVkIGFtb25nIHRoZSBtZWRp
YSBzdHJlYW1zIHdpdGhpbiB0aGUgQlVORExFIGdyb3VwLiBPcj88L3NwYW4+PHNwYW4gc3R5bGU9
ImNvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2si
Pk5vdCBpZiB5b3UgdHJpY2tsZSwgbm8uIFRoZW4gYWxsIHRoZSBtPSBsaW5lcyBoYXZlIHRoZSBz
YW1lIGFkZHJlc3Mgd2hldGhlciB0aGV5IGFyZSBidW5kbGVkIG9yIG5vdC48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNr
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjpyZWQiPk9rLCBJIGhlYXIgeW91LiBZb3UgYXJlIGJhc2ljYWxseSBzYXlp
bmcgdGhhdCBpdCBkb2VzbuKAmXQgbWF0dGVyIHdoZXRoZXIgYnVuZGxlZCBtLSBsaW5lcyBzaGFy
ZSBhZGRyZXNzZXMgb3Igbm90Jm5ic3A74oCTJm5ic3A7dGhlIE9OTFkgdGhpbmcgdGhhdCBtYXR0
ZXJzIGlzIHRoYXQgdGhlIG0tIGxpbmUNCiBhc3NvY2lhdGVkIHdpdGggdGhlIGJ1bmRsZSB0YWcg
Y29udGFpbnMgdGhlIGFkZHJlc3MgdG8gYmUgdXNlZC48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjpyZWQiPlRoZSByZWFzb24gd2UgbWFuZGF0ZWQgc2hhcmVkIGFkZHJl
c3Nlcywgb25jZSB0aGUgdXNhZ2Ugb2YgQlVORExFIGhhZCBiZWVuIG5lZ290aWF0ZWQsIHdhcyBi
ZWNhdXNlIG9mIGludGVybWVkaWFyaWVzIHRoYXQgZG9u4oCZdCBzdXBwb3J0IEJVTkRMRSAodG8g
bWFrZSBzdXJlIHRoZXkNCiBzZW5kIG1lZGlhIHRvd2FyZHMgdGhlIGNvcnJlY3QgYWRkcmVzcyku
IEJ1dCwgbWF5YmUgd2UgZG9u4oCZdCBuZWVkIHRvIHdvcnJ5IGFib3V0IGFueW1vcmUmbmJzcDvi
gJMmbmJzcDtCVU5ETEUmbmJzcDtwcm9iYWJseSB3b27igJl0IHdvcmsgcmVsaWFibHkgd2l0aCBz
dWNoJm5ic3A7aW50ZXJtZWRpYXJpZXMgYW55d2F54oCmPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6cmVkIj5BbHNvLCB0aGVyZSBpcyBhdCBsZWFzdCBvbmNlIGNhc2Ug
d2hlcmUgdGhlIGFkZHJlc3MgbWF0dGVyczogd2hlbiB5b3UgYWRkIGEgbmV3IG0tIGxpbmUgdG8g
YSBidW5kbGUgZ3JvdXAuIElmIHlvdSB1c2UgYSB1bmlxdWUgYWRkcmVzcywgYW5kIHRoZSBhbnN3
ZXJlciBkb2VzIG5vdA0KIGFjY2VwdCB0aGUgbS0gbGluZSBpbiB0aGUgQlVORExFIGdyb3VwLCBp
dCBjYW4gYmUgdXNlZCB1bi1idW5kbGVkLiBJZiB5b3UgdXNlIGEgc2hhcmVkIGFkZHJlc3MsIHRo
ZSBhbnN3ZXJlciB3aWxsIGhhdmUgdG8gcmVqZWN0IHRoZSBtLSBsaW5lLjwvc3Bhbj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHRoaW5r
IHRoaXMgaXMgYWxsIHRydWUsIGJ1dCB3aGF0IEkgYW0gdHJ5aW5nIHRvIHNheSBoZXJlIGlzLCBJ
IHRoaW5rLCBjb25jZXB0dWFsbHkgZGlmZmVyZW50OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CVU5ETEVEIG09IGxpbmVzIGFyZSBncm91cGVk
IHRvZ2V0aGVyIGFuZCBzaGFyZSBhIGJ1bmNoIG9mIHByb3BlcnRpZXMuIEFtb25nc3QgdGhvc2Ug
cHJvcGVydGllcyBpcyB0aGF0IHRoZXkgc2hhcmUgSVAgYWRkcmVzc2VzLCBidXQgaXQncyBub3Qg
dGhlIG9ubHkgdGhpbmcgdGhleSBzaGFyZSwgbm9yIGlzIGl0IGl0IHRoZSBpbmRpY2F0b3IgdGhh
dCB0aGV5IGFyZSBzaGFyZWQgKHRoYXQncyB0aGUgYT1ncm91cDpCVU5ETEUNCiBsaXN0KS4gU28g
dGhlIHRvcC1saW5lIGNhdGVnb3J5IGlzbid0IHNoYXJlZCB2cy91bmlxdWUgSVAgYWRkcmVzcyBi
dXQgcmF0aGVyIGJ1bmRsZWQgdnMuIHVuYnVuZGxlZC4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOnJl
ZCI+Q29ycmVjdC4gPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImNvbG9yOnJlZCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOnJlZCI+VGhlIGJlc3QgdGhpbmcs
IGFzIGZhciBhcyB0aGUgYWRkcmVzcyBpbiB0aGUgbS0gbGluZSBpcyBjb25jZXJuZWQsIHdvdWxk
IGJlIHRvIHNpbXBseSB1c2Ugbm9ybWFsIFNEUCBwcm9jZWR1cmVzIChyZWFkOiB1bmlxdWUgYWRk
cmVzc2VzKSBhbHNvIGZvciBidW5kbGVkIG0tIGxpbmVzLiBBbmQsIGlmIHRoZSBvZmZlcmVyIHdh
bnRzIHRvIG1ha2Ugc3VyZSBhIG1pZC1zZXNzaW9uDQogYWRkZWQgbS0gbGluZSBnZXRzIGFjY2Vw
dGVkIGluIHRoZSBidW5kbGUgZ3JvdXAgKG9yIG90aGVyd2lzZSBpcyByZWplY3RlZCkgaGUgd291
bGQgdXNlIGJ1bmRsZS1vbmx5IOKAkyBpbiB0aGUgc2FtZSB3YXkgaXTigJlzIHVzZWQgaW4gdGhl
IGluaXRpYWwgb2ZmZXIuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImNvbG9yOnJlZCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOnJlZCI+VGhlbiBhIOKAnHNo
YXJlZCBhZGRyZXNz4oCdIHdvdWxkIG9ubHkgYmUgYSBwcm9wZXJ0eSBvZiB0aGUgQlVORExFIGdy
b3VwIOKAkyBub3QgcmVsYXRlZCB0byB0aGUgYWRkcmVzcyBwdXQgaW4gdGhlIG0tIGxpbmUuPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNv
bG9yOnJlZCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImNvbG9yOnJlZCI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6cmVkIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29s
b3I6cmVkIj5DaHJpc3RlcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_7594FB04B1934943A5C02806D1A2204B4BD14B37ESESSMB209erics_--


From nobody Mon Oct  3 16:08:58 2016
Return-Path: <ekr@rtfm.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 6AA42129579 for <mmusic@ietfa.amsl.com>; Mon,  3 Oct 2016 16:08:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gY0IOaJ8vju5 for <mmusic@ietfa.amsl.com>; Mon,  3 Oct 2016 16:08:54 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 AE2511294FE for <mmusic@ietf.org>; Mon,  3 Oct 2016 16:08:54 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id i129so117879577ywb.0 for <mmusic@ietf.org>; Mon, 03 Oct 2016 16:08:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/r49XREK8Q5sqZNUMzyP0X8i7mKAu/qUymMiULR46sY=; b=gZ1k+kGXQs1TIBLPBeR+y7BTNnn5WPbmuujHE1a9fmZu2s8BJib6n6aTej1sJGCQJ0 /ps9Coy26+8mMv7lhHPt/WPL1Ho4PorgXTMglvQRbTD7v+5RCQLDNOD2sn0ob7i4AT+z YU6TT4hkHPeQMhG7KU77t14B4vlKQJBm1GBedrhCkORZTPL6uqMI6/YQqmtUbEGqPxst EaAUzbLsERxK1OWh9FoPGzoVI38yNOdU+j9HJJBXNBwslvSXdMSDzt+LOHqMuMpwTuy5 AmQakvUDFeiN7kbxHs+nf6z3zye5gjD1JE/PWHxNU/1O07EQGmyVVDTCq/B3X3omUqR2 /XoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/r49XREK8Q5sqZNUMzyP0X8i7mKAu/qUymMiULR46sY=; b=MkOHQJzKHCKeSi+kmBmoWe5YAmnU0ljgetp3r3Dct8ZRLIp05CGMx2tPl/OlTtUUAe +6fABvL6zzK6j5l0tZrzi4lA9liSyT6Itma7iJh2lHquNeFoJz4qXgYCntcihKm7MgA3 i6tO+9CP9WQ3+vEbrDc2vZjGaylcSy9UPVPDC6rLIToLE0Y5UfRZjo85F09w2JvL1ipK aX6XytfHUtGD/YdaqDCV7P7djYdLpbAf0eQf4T4oAQGpfgTtL4hXFxAVEYk0ZvGR6H9D vnCg20z+n+6zeMk07kxwu7hpTFyWocOXPuVNeRZ4wJ9rcEIKIComnl0xQxHdoNVid3ip OU5g==
X-Gm-Message-State: AA6/9RlRMXWzEmTk9cEpal7jvHNdxsVoZ4uQjetnbltG7oKnSRq6c552bBbH/uvMNMW06gkB1fwo0nYZrQ5e6A==
X-Received: by 10.129.83.193 with SMTP id h184mr487806ywb.52.1475536133914; Mon, 03 Oct 2016 16:08:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.160.10 with HTTP; Mon, 3 Oct 2016 16:08:12 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD14B37@ESESSMB209.ericsson.se>
References: <CABcZeBPpdyxiFbiHsqj=XwxFvOs4=z+R0zK0zoxbpixa25k3zQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BC722B7@ESESSMB209.ericsson.se> <CABcZeBP_Rcd3_pmEcAoQVOeKV_mtStM+31Gz+6eqR4hDvHNemA@mail.gmail.com> <D41804D7.10437%christer.holmberg@ericsson.com> <CABcZeBOa-zegdj1ZvP3==bac1ZXTLkkKe7y6SPk43F2EpfKDwQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD14B37@ESESSMB209.ericsson.se>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 3 Oct 2016 16:08:12 -0700
Message-ID: <CABcZeBOtEJTv_jh=hpCWhoOLtZWgi04486agOG3OZs_O1ikbBQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a114d6f1c1ddfd3053dfe076f
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/eFbCIb60WMxUgfVzJz2nfMDrWlo>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2016 23:08:56 -0000

--001a114d6f1c1ddfd3053dfe076f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 3, 2016 at 1:07 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
>
>
> OVERALL
>
>
>
> >The overall framing of this document as being about attaching multiple
>
> >m=3D sections to a single "shared address" is extremely problematic,
>
> >for two reasons:
>
> >
>
> >- With ICE there isn't actually any notion of a shared address except
>
> >  in some vague sense. I suppose you could argue that because with
>
> >  ICE you are required to specify a port on the m=3D line then you
>
> >  still have a concept of an address, but that's not true in
>
> >  trickle ICE, where the port is 9, so all m=3D lines share the same
>
> >  address/port. So, actually when you use trickle a whole bunch of
>
> >  the statements in this document are wrong.
>
> >
>
> >- A lot more is being overloaded here than addresses. In fact, a whole
>
> >  pile of semantics are being overloaded, so the way to think about
>
> >  this is actually as gluing a whole bunch of m=3D lines together at
>
> >  the transport level.
>
> >
>
> > I think the right concept here is not "shared address" but "bundle grou=
p"
>
> > and the document should be written in that way, namely that there are
>
> > a  bunch of m=3D lines in a bundle group and the one with the bundle ta=
g
>
> > is the one that sets all the shared parameters.
>
>
>
> It is true that the actual port value in the m- line, and the IP address
> in the c- line address, represent the address that is actually being used=
.
>
>
>
> But, even with ICE there is a shared address, isn=E2=80=99t there? Yes, t=
hat
> shared address may change, but at any given time there will be one addres=
s
> that is shared among the media streams within the BUNDLE group. Or?
>
>
>
> Not if you trickle, no. Then all the m=3D lines have the same address
> whether they are bundled or not.
>
>
>
>
>
> Ok, I hear you. You are basically saying that it doesn=E2=80=99t matter w=
hether
> bundled m- lines share addresses or not =E2=80=93 the ONLY thing that mat=
ters is
> that the m- line associated with the bundle tag contains the address to b=
e
> used.
>
>
>
> The reason we mandated shared addresses, once the usage of BUNDLE had bee=
n
> negotiated, was because of intermediaries that don=E2=80=99t support BUND=
LE (to
> make sure they send media towards the correct address). But, maybe we don=
=E2=80=99t
> need to worry about anymore =E2=80=93 BUNDLE probably won=E2=80=99t work =
reliably with
> such intermediaries anyway=E2=80=A6
>
>
>
> Also, there is at least once case where the address matters: when you add
> a new m- line to a bundle group. If you use a unique address, and the
> answerer does not accept the m- line in the BUNDLE group, it can be used
> un-bundled. If you use a shared address, the answerer will have to reject
> the m- line.
>
>
>
> I think this is all true, but what I am trying to say here is, I think,
> conceptually different:
>
>
>
> BUNDLED m=3D lines are grouped together and share a bunch of properties.
> Amongst those properties is that they share IP addresses, but it's not th=
e
> only thing they share, nor is it it the indicator that they are shared
> (that's the a=3Dgroup:BUNDLE list). So the top-line category isn't shared
> vs/unique IP address but rather bundled vs. unbundled.
>
>
>
> Correct.
>
>
>
> The best thing, as far as the address in the m- line is concerned, would
> be to simply use normal SDP procedures (read: unique addresses) also for
> bundled m- lines. And, if the offerer wants to make sure a mid-session
> added m- line gets accepted in the bundle group (or otherwise is rejected=
)
> he would use bundle-only =E2=80=93 in the same way it=E2=80=99s used in t=
he initial offer.
>
>
>
> Then a =E2=80=9Cshared address=E2=80=9D would only be a property of the B=
UNDLE group =E2=80=93 not
> related to the address put in the m- line.
>

I worry that we're not communicating. I would have this document never
refer to "shared" or "unique" addresses and instead refer to bundled or
unbundled m=3D lines.

-Ekr



> Regards,
>
>
>
> Christer
>

--001a114d6f1c1ddfd3053dfe076f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Oct 3, 2016 at 1:07 PM, Christer Holmberg <span dir=3D"ltr">&lt=
;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christ=
er.holmberg@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Hi,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<div>
<div>
<div><div><div class=3D"h5">
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div>
<div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">OVERALL</span><span style=3D"color:blac=
k"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">=C2=A0</span><span style=3D"color:black=
"><u></u><u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt;The overall framing of this documen=
t as being about attaching multiple</span><span style=3D"color:black"><u></=
u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt;m=3D sections to a single &quot;sha=
red address&quot; is extremely problematic,</span><span style=3D"color:blac=
k"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt;for two reasons:</span><span style=
=3D"color:black"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt;=C2=A0</span><span style=3D"color:b=
lack"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt;- With ICE there isn&#39;t actually=
 any notion of a shared address except</span><span style=3D"color:black"><u=
></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; =C2=A0in some vague sense. I suppo=
se you could argue that because with</span><span style=3D"color:black"><u><=
/u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; =C2=A0ICE you are required to spec=
ify a port on the m=3D line then you</span><span style=3D"color:black"><u><=
/u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; =C2=A0still have a concept of an a=
ddress, but that&#39;s not true in</span><span style=3D"color:black"><u></u=
><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; =C2=A0trickle ICE, where the port =
is 9, so all m=3D lines share the same</span><span style=3D"color:black"><u=
></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; =C2=A0address/port. So, actually w=
hen you use trickle a whole bunch of</span><span style=3D"color:black"><u><=
/u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; =C2=A0the statements in this docum=
ent are wrong.</span><span style=3D"color:black"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt;=C2=A0</span><span style=3D"color:b=
lack"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt;- A lot more is being overloaded he=
re than addresses. In fact, a whole</span><span style=3D"color:black"><u></=
u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; =C2=A0pile of semantics are being =
overloaded, so the way to think about</span><span style=3D"color:black"><u>=
</u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; =C2=A0this is actually as gluing a=
 whole bunch of m=3D lines together at</span><span style=3D"color:black"><u=
></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; =C2=A0the transport level.</span><=
span style=3D"color:black"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt;=C2=A0</span><span style=3D"color:b=
lack"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; I think the right concept here is =
not &quot;shared address&quot; but &quot;bundle group&quot;</span><span sty=
le=3D"color:black"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; and the document should be written=
 in that way, namely that there are</span><span style=3D"color:black"><u></=
u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; a =C2=A0bunch of m=3D lines in a b=
undle group and the one with the bundle tag</span><span style=3D"color:blac=
k"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; is the one that sets all the share=
d parameters.</span><span style=3D"color:black"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">=C2=A0</span><span style=3D"color:black=
"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">It is true that the actual port value i=
n the m- line, and the IP address in the c- line address, represent
 the address that is actually being used.</span><span style=3D"color:black"=
><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">=C2=A0</span><span style=3D"color:black=
"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">But, even with ICE there is a shared ad=
dress, isn=E2=80=99t there? Yes, that shared address may change, but at
 any given time there will be one address that is shared among the media st=
reams within the BUNDLE group. Or?</span><span style=3D"color:black"><u></u=
><u></u></span></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Not if you trickle, no. Then all the m=
=3D lines have the same address whether they are bundled or not.<u></u><u><=
/u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Ok, I hear you. You are basically saying =
that it doesn=E2=80=99t matter whether bundled m- lines share addresses or =
not=C2=A0=E2=80=93=C2=A0the ONLY thing that matters is that the m- line
 associated with the bundle tag contains the address to be used.</span><spa=
n style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans-serif;colo=
r:black"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">The reason we mandated shared addresses, =
once the usage of BUNDLE had been negotiated, was because of intermediaries=
 that don=E2=80=99t support BUNDLE (to make sure they
 send media towards the correct address). But, maybe we don=E2=80=99t need =
to worry about anymore=C2=A0=E2=80=93=C2=A0BUNDLE=C2=A0probably won=E2=80=
=99t work reliably with such=C2=A0intermediaries anyway=E2=80=A6</span><spa=
n style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans-serif;colo=
r:black"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Also, there is at least once case where t=
he address matters: when you add a new m- line to a bundle group. If you us=
e a unique address, and the answerer does not
 accept the m- line in the BUNDLE group, it can be used un-bundled. If you =
use a shared address, the answerer will have to reject the m- line.</span><=
span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans-serif;c=
olor:black"><u></u><u></u></span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I think this is all true, but what I am trying to sa=
y here is, I think, conceptually different:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">BUNDLED m=3D lines are grouped together and share a =
bunch of properties. Amongst those properties is that they share IP address=
es, but it&#39;s not the only thing they share, nor is it it the indicator =
that they are shared (that&#39;s the a=3Dgroup:BUNDLE
 list). So the top-line category isn&#39;t shared vs/unique IP address but =
rather bundled vs. unbundled.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div></div><div>
<p class=3D"MsoNormal"><span style=3D"color:red">Correct. <u></u><u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:red"><u></u>=C2=A0<u></u></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:red">The best thing, as far as =
the address in the m- line is concerned, would be to simply use normal SDP =
procedures (read: unique addresses) also for bundled m- lines. And, if the =
offerer wants to make sure a mid-session
 added m- line gets accepted in the bundle group (or otherwise is rejected)=
 he would use bundle-only =E2=80=93 in the same way it=E2=80=99s used in th=
e initial offer.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:red"><u></u>=C2=A0<u></u></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:red">Then a =E2=80=9Cshared add=
ress=E2=80=9D would only be a property of the BUNDLE group =E2=80=93 not re=
lated to the address put in the m- line.</span></p></div></div></div></div>=
</div></div></blockquote><div><br></div><div>I worry that we&#39;re not com=
municating. I would have this document never refer to &quot;shared&quot; or=
 &quot;unique&quot; addresses and instead refer to bundled or unbundled m=
=3D lines.</div><div><br></div><div>-Ekr</div><div><br></div><div>=C2=A0</d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-GB" link=3D"blue" vlink=
=3D"purple"><div><div><div><div><div><p class=3D"MsoNormal"></p>
<p class=3D"MsoNormal"><span style=3D"color:red">Regards,<span class=3D"HOE=
nZb"><font color=3D"#888888"><u></u><u></u></font></span></span></p><span c=
lass=3D"HOEnZb"><font color=3D"#888888">
<p class=3D"MsoNormal"><span style=3D"color:red"><u></u>=C2=A0<u></u></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:red">Christer<u></u><u></u></sp=
an></p>
</font></span></div>
</div>
</div>
</div>
</div>
</div>

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

--001a114d6f1c1ddfd3053dfe076f--


From nobody Mon Oct  3 16:14:48 2016
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 7CAF3129579 for <mmusic@ietfa.amsl.com>; Mon,  3 Oct 2016 16:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 Z3Nqw6rlJ3OU for <mmusic@ietfa.amsl.com>; Mon,  3 Oct 2016 16:14:43 -0700 (PDT)
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 76828129457 for <mmusic@ietf.org>; Mon,  3 Oct 2016 16:14:43 -0700 (PDT)
X-AuditID: c1b4fb3a-ab7ff7000000099a-82-57f2e65fd364
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by  (Symantec Mail Security) with SMTP id 04.CE.02458.F56E2F75; Tue,  4 Oct 2016 01:14:41 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0319.002; Tue, 4 Oct 2016 01:14:39 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I)
Thread-Index: AQHSAjFbVSmCBcGmbka3UICv6Cl9oaCV9LgAgADkVID///3vgIAAgk6AgAAW1ACAACJbgA==
Date: Mon, 3 Oct 2016 23:14:38 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD15355@ESESSMB209.ericsson.se>
References: <CABcZeBPpdyxiFbiHsqj=XwxFvOs4=z+R0zK0zoxbpixa25k3zQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BC722B7@ESESSMB209.ericsson.se> <CABcZeBP_Rcd3_pmEcAoQVOeKV_mtStM+31Gz+6eqR4hDvHNemA@mail.gmail.com> <D41804D7.10437%christer.holmberg@ericsson.com> <CABcZeBOa-zegdj1ZvP3==bac1ZXTLkkKe7y6SPk43F2EpfKDwQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD14B37@ESESSMB209.ericsson.se> <CABcZeBOtEJTv_jh=hpCWhoOLtZWgi04486agOG3OZs_O1ikbBQ@mail.gmail.com>
In-Reply-To: <CABcZeBOtEJTv_jh=hpCWhoOLtZWgi04486agOG3OZs_O1ikbBQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BD15355ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprEIsWRmVeSWpSXmKPExsUyM2K7um7is0/hBm8fa1useH2O3WLq8scs DkweS5b8ZPKY/LiNOYApissmJTUnsyy1SN8ugSvj487/zAVznjFWbHw1ja2BccoDxi5GDg4J AROJ49/Zuhi5OIQE1jNKzHrYDeRwAjmLGCWmHkoHqWETsJDo/qcNEhYRUJD49ecEC4jNLCAv cWHJGiYQW1ggTOLl/DnMEDXhEoef/meCsMMkXv/cC2azCKhIzLk2jRHE5hXwlVhzZC47xN77 zBJfWs+wgiQ4BQIlnhyCaGYUEJP4fgpiAbOAuMStJ/PBbAkBAYkle84zQ9iiEi8f/2OFsJUk Ft3+zARyM7NAvsSeM/YQuwQlTs58wjKBUWQWkkmzEKpmIamCCGtKrN+lD1GtKDGl+yE7hK0h 0TpnLjuy+AJG9lWMosWpxcW56UZGeqlFmcnFxfl5enmpJZsYgTF1cMtvqx2MB587HmIU4GBU 4uFNSPkULsSaWFZcmXuIUYKDWUmE9/RjoBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXFes5X3w4UE 0hNLUrNTUwtSi2CyTBycUg2M8e/9pm5/krLzxXbNpW0M0V/mBl640fbPzvOw6P60ps0/VZZt PK99yKQtaoPr5arTqi7vSipyX3ztyxKdkJlY4uCbdktML/aTg861jKUHexYFRu3TMU4xOBJw 6rHA0YOLNiereDtU6tg7TL9kpNrnuJ7v+crlGq2qjhk5IpqvsxI/FquVc/IpsRRnJBpqMRcV JwIAPnd3tqUCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MoAS_mwW6Q-ju4odZIQCTO0BUs0>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2016 23:14:46 -0000

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

SGksDQoNCk9WRVJBTEwNCg0KPlRoZSBvdmVyYWxsIGZyYW1pbmcgb2YgdGhpcyBkb2N1bWVudCBh
cyBiZWluZyBhYm91dCBhdHRhY2hpbmcgbXVsdGlwbGUNCj5tPSBzZWN0aW9ucyB0byBhIHNpbmds
ZSAic2hhcmVkIGFkZHJlc3MiIGlzIGV4dHJlbWVseSBwcm9ibGVtYXRpYywNCj5mb3IgdHdvIHJl
YXNvbnM6DQo+DQo+LSBXaXRoIElDRSB0aGVyZSBpc24ndCBhY3R1YWxseSBhbnkgbm90aW9uIG9m
IGEgc2hhcmVkIGFkZHJlc3MgZXhjZXB0DQo+ICBpbiBzb21lIHZhZ3VlIHNlbnNlLiBJIHN1cHBv
c2UgeW91IGNvdWxkIGFyZ3VlIHRoYXQgYmVjYXVzZSB3aXRoDQo+ICBJQ0UgeW91IGFyZSByZXF1
aXJlZCB0byBzcGVjaWZ5IGEgcG9ydCBvbiB0aGUgbT0gbGluZSB0aGVuIHlvdQ0KPiAgc3RpbGwg
aGF2ZSBhIGNvbmNlcHQgb2YgYW4gYWRkcmVzcywgYnV0IHRoYXQncyBub3QgdHJ1ZSBpbg0KPiAg
dHJpY2tsZSBJQ0UsIHdoZXJlIHRoZSBwb3J0IGlzIDksIHNvIGFsbCBtPSBsaW5lcyBzaGFyZSB0
aGUgc2FtZQ0KPiAgYWRkcmVzcy9wb3J0LiBTbywgYWN0dWFsbHkgd2hlbiB5b3UgdXNlIHRyaWNr
bGUgYSB3aG9sZSBidW5jaCBvZg0KPiAgdGhlIHN0YXRlbWVudHMgaW4gdGhpcyBkb2N1bWVudCBh
cmUgd3JvbmcuDQo+DQo+LSBBIGxvdCBtb3JlIGlzIGJlaW5nIG92ZXJsb2FkZWQgaGVyZSB0aGFu
IGFkZHJlc3Nlcy4gSW4gZmFjdCwgYSB3aG9sZQ0KPiAgcGlsZSBvZiBzZW1hbnRpY3MgYXJlIGJl
aW5nIG92ZXJsb2FkZWQsIHNvIHRoZSB3YXkgdG8gdGhpbmsgYWJvdXQNCj4gIHRoaXMgaXMgYWN0
dWFsbHkgYXMgZ2x1aW5nIGEgd2hvbGUgYnVuY2ggb2YgbT0gbGluZXMgdG9nZXRoZXIgYXQNCj4g
IHRoZSB0cmFuc3BvcnQgbGV2ZWwuDQo+DQo+IEkgdGhpbmsgdGhlIHJpZ2h0IGNvbmNlcHQgaGVy
ZSBpcyBub3QgInNoYXJlZCBhZGRyZXNzIiBidXQgImJ1bmRsZSBncm91cCINCj4gYW5kIHRoZSBk
b2N1bWVudCBzaG91bGQgYmUgd3JpdHRlbiBpbiB0aGF0IHdheSwgbmFtZWx5IHRoYXQgdGhlcmUg
YXJlDQo+IGEgIGJ1bmNoIG9mIG09IGxpbmVzIGluIGEgYnVuZGxlIGdyb3VwIGFuZCB0aGUgb25l
IHdpdGggdGhlIGJ1bmRsZSB0YWcNCj4gaXMgdGhlIG9uZSB0aGF0IHNldHMgYWxsIHRoZSBzaGFy
ZWQgcGFyYW1ldGVycy4NCg0KSXQgaXMgdHJ1ZSB0aGF0IHRoZSBhY3R1YWwgcG9ydCB2YWx1ZSBp
biB0aGUgbS0gbGluZSwgYW5kIHRoZSBJUCBhZGRyZXNzIGluIHRoZSBjLSBsaW5lIGFkZHJlc3Ms
IHJlcHJlc2VudCB0aGUgYWRkcmVzcyB0aGF0IGlzIGFjdHVhbGx5IGJlaW5nIHVzZWQuDQoNCkJ1
dCwgZXZlbiB3aXRoIElDRSB0aGVyZSBpcyBhIHNoYXJlZCBhZGRyZXNzLCBpc27igJl0IHRoZXJl
PyBZZXMsIHRoYXQgc2hhcmVkIGFkZHJlc3MgbWF5IGNoYW5nZSwgYnV0IGF0IGFueSBnaXZlbiB0
aW1lIHRoZXJlIHdpbGwgYmUgb25lIGFkZHJlc3MgdGhhdCBpcyBzaGFyZWQgYW1vbmcgdGhlIG1l
ZGlhIHN0cmVhbXMgd2l0aGluIHRoZSBCVU5ETEUgZ3JvdXAuIE9yPw0KDQpOb3QgaWYgeW91IHRy
aWNrbGUsIG5vLiBUaGVuIGFsbCB0aGUgbT0gbGluZXMgaGF2ZSB0aGUgc2FtZSBhZGRyZXNzIHdo
ZXRoZXIgdGhleSBhcmUgYnVuZGxlZCBvciBub3QuDQoNCg0KT2ssIEkgaGVhciB5b3UuIFlvdSBh
cmUgYmFzaWNhbGx5IHNheWluZyB0aGF0IGl0IGRvZXNu4oCZdCBtYXR0ZXIgd2hldGhlciBidW5k
bGVkIG0tIGxpbmVzIHNoYXJlIGFkZHJlc3NlcyBvciBub3Qg4oCTIHRoZSBPTkxZIHRoaW5nIHRo
YXQgbWF0dGVycyBpcyB0aGF0IHRoZSBtLSBsaW5lIGFzc29jaWF0ZWQgd2l0aCB0aGUgYnVuZGxl
IHRhZyBjb250YWlucyB0aGUgYWRkcmVzcyB0byBiZSB1c2VkLg0KDQpUaGUgcmVhc29uIHdlIG1h
bmRhdGVkIHNoYXJlZCBhZGRyZXNzZXMsIG9uY2UgdGhlIHVzYWdlIG9mIEJVTkRMRSBoYWQgYmVl
biBuZWdvdGlhdGVkLCB3YXMgYmVjYXVzZSBvZiBpbnRlcm1lZGlhcmllcyB0aGF0IGRvbuKAmXQg
c3VwcG9ydCBCVU5ETEUgKHRvIG1ha2Ugc3VyZSB0aGV5IHNlbmQgbWVkaWEgdG93YXJkcyB0aGUg
Y29ycmVjdCBhZGRyZXNzKS4gQnV0LCBtYXliZSB3ZSBkb27igJl0IG5lZWQgdG8gd29ycnkgYWJv
dXQgYW55bW9yZSDigJMgQlVORExFIHByb2JhYmx5IHdvbuKAmXQgd29yayByZWxpYWJseSB3aXRo
IHN1Y2ggaW50ZXJtZWRpYXJpZXMgYW55d2F54oCmDQoNCkFsc28sIHRoZXJlIGlzIGF0IGxlYXN0
IG9uY2UgY2FzZSB3aGVyZSB0aGUgYWRkcmVzcyBtYXR0ZXJzOiB3aGVuIHlvdSBhZGQgYSBuZXcg
bS0gbGluZSB0byBhIGJ1bmRsZSBncm91cC4gSWYgeW91IHVzZSBhIHVuaXF1ZSBhZGRyZXNzLCBh
bmQgdGhlIGFuc3dlcmVyIGRvZXMgbm90IGFjY2VwdCB0aGUgbS0gbGluZSBpbiB0aGUgQlVORExF
IGdyb3VwLCBpdCBjYW4gYmUgdXNlZCB1bi1idW5kbGVkLiBJZiB5b3UgdXNlIGEgc2hhcmVkIGFk
ZHJlc3MsIHRoZSBhbnN3ZXJlciB3aWxsIGhhdmUgdG8gcmVqZWN0IHRoZSBtLSBsaW5lLg0KDQpJ
IHRoaW5rIHRoaXMgaXMgYWxsIHRydWUsIGJ1dCB3aGF0IEkgYW0gdHJ5aW5nIHRvIHNheSBoZXJl
IGlzLCBJIHRoaW5rLCBjb25jZXB0dWFsbHkgZGlmZmVyZW50Og0KDQpCVU5ETEVEIG09IGxpbmVz
IGFyZSBncm91cGVkIHRvZ2V0aGVyIGFuZCBzaGFyZSBhIGJ1bmNoIG9mIHByb3BlcnRpZXMuIEFt
b25nc3QgdGhvc2UgcHJvcGVydGllcyBpcyB0aGF0IHRoZXkgc2hhcmUgSVAgYWRkcmVzc2VzLCBi
dXQgaXQncyBub3QgdGhlIG9ubHkgdGhpbmcgdGhleSBzaGFyZSwgbm9yIGlzIGl0IGl0IHRoZSBp
bmRpY2F0b3IgdGhhdCB0aGV5IGFyZSBzaGFyZWQgKHRoYXQncyB0aGUgYT1ncm91cDpCVU5ETEUg
bGlzdCkuIFNvIHRoZSB0b3AtbGluZSBjYXRlZ29yeSBpc24ndCBzaGFyZWQgdnMvdW5pcXVlIElQ
IGFkZHJlc3MgYnV0IHJhdGhlciBidW5kbGVkIHZzLiB1bmJ1bmRsZWQuDQoNCkNvcnJlY3QuDQoN
ClRoZSBiZXN0IHRoaW5nLCBhcyBmYXIgYXMgdGhlIGFkZHJlc3MgaW4gdGhlIG0tIGxpbmUgaXMg
Y29uY2VybmVkLCB3b3VsZCBiZSB0byBzaW1wbHkgdXNlIG5vcm1hbCBTRFAgcHJvY2VkdXJlcyAo
cmVhZDogdW5pcXVlIGFkZHJlc3NlcykgYWxzbyBmb3IgYnVuZGxlZCBtLSBsaW5lcy4gQW5kLCBp
ZiB0aGUgb2ZmZXJlciB3YW50cyB0byBtYWtlIHN1cmUgYSBtaWQtc2Vzc2lvbiBhZGRlZCBtLSBs
aW5lIGdldHMgYWNjZXB0ZWQgaW4gdGhlIGJ1bmRsZSBncm91cCAob3Igb3RoZXJ3aXNlIGlzIHJl
amVjdGVkKSBoZSB3b3VsZCB1c2UgYnVuZGxlLW9ubHkg4oCTIGluIHRoZSBzYW1lIHdheSBpdOKA
mXMgdXNlZCBpbiB0aGUgaW5pdGlhbCBvZmZlci4NCg0KVGhlbiBhIOKAnHNoYXJlZCBhZGRyZXNz
4oCdIHdvdWxkIG9ubHkgYmUgYSBwcm9wZXJ0eSBvZiB0aGUgQlVORExFIGdyb3VwIOKAkyBub3Qg
cmVsYXRlZCB0byB0aGUgYWRkcmVzcyBwdXQgaW4gdGhlIG0tIGxpbmUuDQoNCkkgd29ycnkgdGhh
dCB3ZSdyZSBub3QgY29tbXVuaWNhdGluZy4gSSB3b3VsZCBoYXZlIHRoaXMgZG9jdW1lbnQgbmV2
ZXIgcmVmZXIgdG8gInNoYXJlZCIgb3IgInVuaXF1ZSIgYWRkcmVzc2VzIGFuZCBpbnN0ZWFkIHJl
ZmVyIHRvIGJ1bmRsZWQgb3IgdW5idW5kbGVkIG09IGxpbmVzLg0KDQpFYXJsaWVyIHlvdSBzYWlk
IHRoYXQg4oCcc2hhcmVkIGFkZHJlc3PigJ0gaXMgb25lIG9mIHRoZSBQUk9QRVJUSUVTIG9mIGEg
YnVuZGxlZCBtLSBsaW5lLCBhbmQgdGhhdCBpcyB3aGF0IEkgd2FzIHJlZmVycmluZyB0by4gT3Ro
ZXIgdGhhbiB0aGF0LCB3ZSB3b3VsZCBub3QgaGF2ZSB0byB0YWxrIGFib3V0IOKAnHNoYXJlZOKA
nSBvciDigJx1bmlxdWXigJ0gYWRkcmVzc2VzLCBhcyB5b3Ugc3VnZ2VzdC4NCg0K4oCcQlVORExF
RCBtPSBsaW5lcyBhcmUgZ3JvdXBlZCB0b2dldGhlciBhbmQgc2hhcmUgYSBidW5jaCBvZiBwcm9w
ZXJ0aWVzLiBBbW9uZ3N0IHRob3NlIHByb3BlcnRpZXMgaXMgdGhhdCB0aGV5IHNoYXJlIElQIGFk
ZHJlc3NlcyzigJ0NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLmhvZW56Yg0KCXttc28t
c3R5bGUtbmFtZTpob2VuemI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFG
NDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21w
b3NlOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3Rl
eHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9u
dC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4t
VVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdp
bjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdl
OldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86
c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2Vu
ZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVk
aXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+
PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1HQiIgbGluaz0iYmx1
ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOnJlZDttc28tZmFyZWFzdC1sYW5ndWFn
ZTpFTi1VUyI+SGksPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxibG9j
a3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0
O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0
OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0K
PGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0Mg
MS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4t
dG9wOjUuMHB0O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0K
PGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20g
MGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0
OjBjbTttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OmJsYWNrIj5PVkVSQUxMPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOmJsYWNrIj4mZ3Q7VGhlIG92ZXJhbGwgZnJhbWluZyBvZiB0aGlzIGRvY3Vt
ZW50IGFzIGJlaW5nIGFib3V0IGF0dGFjaGluZyBtdWx0aXBsZTwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOmJsYWNrIj4mZ3Q7bT0gc2VjdGlvbnMgdG8gYSBzaW5nbGUgJnF1b3Q7c2hhcmVkIGFk
ZHJlc3MmcXVvdDsgaXMgZXh0cmVtZWx5IHByb2JsZW1hdGljLDwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOmJsYWNrIj4mZ3Q7Zm9yIHR3byByZWFzb25zOjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOmJsYWNrIj4mZ3Q7Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZn
dDstIFdpdGggSUNFIHRoZXJlIGlzbid0IGFjdHVhbGx5IGFueSBub3Rpb24gb2YgYSBzaGFyZWQg
YWRkcmVzcyBleGNlcHQ8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jmd0OyAmbmJz
cDtpbiBzb21lIHZhZ3VlIHNlbnNlLiBJIHN1cHBvc2UgeW91IGNvdWxkIGFyZ3VlIHRoYXQgYmVj
YXVzZSB3aXRoPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZndDsgJm5ic3A7SUNF
IHlvdSBhcmUgcmVxdWlyZWQgdG8gc3BlY2lmeSBhIHBvcnQgb24gdGhlIG09IGxpbmUgdGhlbiB5
b3U8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jmd0OyAmbmJzcDtzdGlsbCBoYXZl
IGEgY29uY2VwdCBvZiBhbiBhZGRyZXNzLCBidXQgdGhhdCdzIG5vdCB0cnVlIGluPC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZndDsgJm5ic3A7dHJpY2tsZSBJQ0UsIHdoZXJlIHRo
ZSBwb3J0IGlzIDksIHNvIGFsbCBtPSBsaW5lcyBzaGFyZSB0aGUgc2FtZTwvc3Bhbj48bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOmJsYWNrIj4mZ3Q7ICZuYnNwO2FkZHJlc3MvcG9ydC4gU28sIGFjdHVhbGx5
IHdoZW4geW91IHVzZSB0cmlja2xlIGEgd2hvbGUgYnVuY2ggb2Y8L3NwYW4+PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjpibGFjayI+Jmd0OyAmbmJzcDt0aGUgc3RhdGVtZW50cyBpbiB0aGlzIGRvY3VtZW50
IGFyZSB3cm9uZy48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jmd0OyZuYnNwOzwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mZ3Q7LSBBIGxvdCBtb3JlIGlzIGJlaW5n
IG92ZXJsb2FkZWQgaGVyZSB0aGFuIGFkZHJlc3Nlcy4gSW4gZmFjdCwgYSB3aG9sZTwvc3Bhbj48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4mZ3Q7ICZuYnNwO3BpbGUgb2Ygc2VtYW50aWNzIGFy
ZSBiZWluZyBvdmVybG9hZGVkLCBzbyB0aGUgd2F5IHRvIHRoaW5rIGFib3V0PC9zcGFuPjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6YmxhY2siPiZndDsgJm5ic3A7dGhpcyBpcyBhY3R1YWxseSBhcyBnbHVp
bmcgYSB3aG9sZSBidW5jaCBvZiBtPSBsaW5lcyB0b2dldGhlciBhdDwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOmJsYWNrIj4mZ3Q7ICZuYnNwO3RoZSB0cmFuc3BvcnQgbGV2ZWwuPC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZndDsmbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjpibGFjayI+Jmd0OyBJIHRoaW5rIHRoZSByaWdodCBjb25jZXB0IGhlcmUgaXMgbm90ICZx
dW90O3NoYXJlZCBhZGRyZXNzJnF1b3Q7IGJ1dCAmcXVvdDtidW5kbGUgZ3JvdXAmcXVvdDs8L3Nw
YW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jmd0OyBhbmQgdGhlIGRvY3VtZW50IHNob3Vs
ZCBiZSB3cml0dGVuIGluIHRoYXQgd2F5LCBuYW1lbHkgdGhhdCB0aGVyZSBhcmU8L3NwYW4+PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jmd0OyBhICZuYnNwO2J1bmNoIG9mIG09IGxpbmVzIGlu
IGEgYnVuZGxlIGdyb3VwIGFuZCB0aGUgb25lIHdpdGggdGhlIGJ1bmRsZSB0YWc8L3NwYW4+PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jmd0OyBpcyB0aGUgb25lIHRoYXQgc2V0cyBhbGwgdGhl
IHNoYXJlZCBwYXJhbWV0ZXJzLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFj
ayI+SXQgaXMgdHJ1ZSB0aGF0IHRoZSBhY3R1YWwgcG9ydCB2YWx1ZSBpbiB0aGUgbS0gbGluZSwg
YW5kIHRoZSBJUCBhZGRyZXNzIGluIHRoZSBjLSBsaW5lIGFkZHJlc3MsIHJlcHJlc2VudA0KIHRo
ZSBhZGRyZXNzIHRoYXQgaXMgYWN0dWFsbHkgYmVpbmcgdXNlZC48L3NwYW4+PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+
Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkJ1dCwgZXZlbiB3aXRoIElDRSB0aGVyZSBpcyBhIHNo
YXJlZCBhZGRyZXNzLCBpc27igJl0IHRoZXJlPyBZZXMsIHRoYXQgc2hhcmVkIGFkZHJlc3MgbWF5
IGNoYW5nZSwgYnV0IGF0DQogYW55IGdpdmVuIHRpbWUgdGhlcmUgd2lsbCBiZSBvbmUgYWRkcmVz
cyB0aGF0IGlzIHNoYXJlZCBhbW9uZyB0aGUgbWVkaWEgc3RyZWFtcyB3aXRoaW4gdGhlIEJVTkRM
RSBncm91cC4gT3I/PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFj
ayI+Tm90IGlmIHlvdSB0cmlja2xlLCBuby4gVGhlbiBhbGwgdGhlIG09IGxpbmVzIGhhdmUgdGhl
IHNhbWUgYWRkcmVzcyB3aGV0aGVyIHRoZXkgYXJlIGJ1bmRsZWQgb3Igbm90Ljwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpi
bGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bh
bj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOnJlZCI+T2ssIEkgaGVhciB5b3UuIFlvdSBhcmUgYmFzaWNh
bGx5IHNheWluZyB0aGF0IGl0IGRvZXNu4oCZdCBtYXR0ZXIgd2hldGhlciBidW5kbGVkIG0tIGxp
bmVzIHNoYXJlIGFkZHJlc3Nlcw0KIG9yIG5vdCZuYnNwO+KAkyZuYnNwO3RoZSBPTkxZIHRoaW5n
IHRoYXQgbWF0dGVycyBpcyB0aGF0IHRoZSBtLSBsaW5lIGFzc29jaWF0ZWQgd2l0aCB0aGUgYnVu
ZGxlIHRhZyBjb250YWlucyB0aGUgYWRkcmVzcyB0byBiZSB1c2VkLjwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpyZWQiPlRo
ZSByZWFzb24gd2UgbWFuZGF0ZWQgc2hhcmVkIGFkZHJlc3Nlcywgb25jZSB0aGUgdXNhZ2Ugb2Yg
QlVORExFIGhhZCBiZWVuIG5lZ290aWF0ZWQsIHdhcyBiZWNhdXNlIG9mIGludGVybWVkaWFyaWVz
DQogdGhhdCBkb27igJl0IHN1cHBvcnQgQlVORExFICh0byBtYWtlIHN1cmUgdGhleSBzZW5kIG1l
ZGlhIHRvd2FyZHMgdGhlIGNvcnJlY3QgYWRkcmVzcykuIEJ1dCwgbWF5YmUgd2UgZG9u4oCZdCBu
ZWVkIHRvIHdvcnJ5IGFib3V0IGFueW1vcmUmbmJzcDvigJMmbmJzcDtCVU5ETEUmbmJzcDtwcm9i
YWJseSB3b27igJl0IHdvcmsgcmVsaWFibHkgd2l0aCBzdWNoJm5ic3A7aW50ZXJtZWRpYXJpZXMg
YW55d2F54oCmPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOnJlZCI+QWxzbywgdGhlcmUgaXMgYXQgbGVhc3Qgb25jZSBjYXNl
IHdoZXJlIHRoZSBhZGRyZXNzIG1hdHRlcnM6IHdoZW4geW91IGFkZCBhIG5ldyBtLSBsaW5lIHRv
IGEgYnVuZGxlIGdyb3VwLg0KIElmIHlvdSB1c2UgYSB1bmlxdWUgYWRkcmVzcywgYW5kIHRoZSBh
bnN3ZXJlciBkb2VzIG5vdCBhY2NlcHQgdGhlIG0tIGxpbmUgaW4gdGhlIEJVTkRMRSBncm91cCwg
aXQgY2FuIGJlIHVzZWQgdW4tYnVuZGxlZC4gSWYgeW91IHVzZSBhIHNoYXJlZCBhZGRyZXNzLCB0
aGUgYW5zd2VyZXIgd2lsbCBoYXZlIHRvIHJlamVjdCB0aGUgbS0gbGluZS48L3NwYW4+PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPkkgdGhpbmsgdGhpcyBpcyBhbGwgdHJ1ZSwgYnV0IHdoYXQgSSBh
bSB0cnlpbmcgdG8gc2F5IGhlcmUgaXMsIEkgdGhpbmssIGNvbmNlcHR1YWxseSBkaWZmZXJlbnQ6
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij5CVU5ETEVEIG09IGxpbmVzIGFyZSBncm91cGVkIHRvZ2V0aGVyIGFuZCBzaGFyZSBhIGJ1bmNo
IG9mIHByb3BlcnRpZXMuIEFtb25nc3QgdGhvc2UgcHJvcGVydGllcyBpcyB0aGF0IHRoZXkgc2hh
cmUgSVAgYWRkcmVzc2VzLCBidXQgaXQncyBub3QgdGhlIG9ubHkgdGhpbmcgdGhleSBzaGFyZSwg
bm9yIGlzIGl0DQogaXQgdGhlIGluZGljYXRvciB0aGF0IHRoZXkgYXJlIHNoYXJlZCAodGhhdCdz
IHRoZSBhPWdyb3VwOkJVTkRMRSBsaXN0KS4gU28gdGhlIHRvcC1saW5lIGNhdGVnb3J5IGlzbid0
IHNoYXJlZCB2cy91bmlxdWUgSVAgYWRkcmVzcyBidXQgcmF0aGVyIGJ1bmRsZWQgdnMuIHVuYnVu
ZGxlZC4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iY29sb3I6cmVkIj5Db3Jy
ZWN0Lg0KPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3Bh
biBzdHlsZT0iY29sb3I6cmVkIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJjb2xvcjpyZWQiPlRoZSBiZXN0IHRoaW5nLCBh
cyBmYXIgYXMgdGhlIGFkZHJlc3MgaW4gdGhlIG0tIGxpbmUgaXMgY29uY2VybmVkLCB3b3VsZCBi
ZSB0byBzaW1wbHkgdXNlIG5vcm1hbCBTRFAgcHJvY2VkdXJlcyAocmVhZDogdW5pcXVlIGFkZHJl
c3NlcykgYWxzbyBmb3IgYnVuZGxlZA0KIG0tIGxpbmVzLiBBbmQsIGlmIHRoZSBvZmZlcmVyIHdh
bnRzIHRvIG1ha2Ugc3VyZSBhIG1pZC1zZXNzaW9uIGFkZGVkIG0tIGxpbmUgZ2V0cyBhY2NlcHRl
ZCBpbiB0aGUgYnVuZGxlIGdyb3VwIChvciBvdGhlcndpc2UgaXMgcmVqZWN0ZWQpIGhlIHdvdWxk
IHVzZSBidW5kbGUtb25seSDigJMgaW4gdGhlIHNhbWUgd2F5IGl04oCZcyB1c2VkIGluIHRoZSBp
bml0aWFsIG9mZmVyLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+PHNwYW4gc3R5bGU9ImNvbG9yOnJlZCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iY29sb3I6cmVkIj5UaGVuIGEg4oCc
c2hhcmVkIGFkZHJlc3PigJ0gd291bGQgb25seSBiZSBhIHByb3BlcnR5IG9mIHRoZSBCVU5ETEUg
Z3JvdXAg4oCTIG5vdCByZWxhdGVkIHRvIHRoZSBhZGRyZXNzIHB1dCBpbiB0aGUgbS0gbGluZS48
L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5JIHdvcnJ5IHRoYXQgd2UncmUgbm90IGNvbW11bmljYXRpbmcuIEkgd291bGQgaGF2ZSB0aGlz
IGRvY3VtZW50IG5ldmVyIHJlZmVyIHRvICZxdW90O3NoYXJlZCZxdW90OyBvciAmcXVvdDt1bmlx
dWUmcXVvdDsgYWRkcmVzc2VzIGFuZCBpbnN0ZWFkIHJlZmVyIHRvIGJ1bmRsZWQgb3IgdW5idW5k
bGVkIG09IGxpbmVzLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6cmVkIj5FYXJsaWVyIHlvdSBzYWlkIHRoYXQg4oCcc2hhcmVkIGFk
ZHJlc3PigJ0gaXMgb25lIG9mIHRoZSBQUk9QRVJUSUVTIG9mIGEgYnVuZGxlZCBtLSBsaW5lLCBh
bmQgdGhhdCBpcyB3aGF0IEkgd2FzIHJlZmVycmluZyB0by4gT3RoZXIgdGhhbiB0aGF0LCB3ZSB3
b3VsZCBub3QgaGF2ZSB0byB0YWxrDQogYWJvdXQg4oCcc2hhcmVk4oCdIG9yIOKAnHVuaXF1ZeKA
nSBhZGRyZXNzZXMsIGFzIHlvdSBzdWdnZXN0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpyZWQiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxpPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjpyZWQiPuKAnDwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6cmVkIj5CVU5ETEVEIG09IGxp
bmVzIGFyZSBncm91cGVkIHRvZ2V0aGVyIGFuZCBzaGFyZSBhIGJ1bmNoIG9mIHByb3BlcnRpZXMu
IEFtb25nc3QgdGhvc2UgcHJvcGVydGllcyBpcyB0aGF0IHRoZXkgc2hhcmUgSVAgYWRkcmVzc2Vz
LOKAnTwvc3Bhbj48L2k+PGk+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOnJlZCI+PG86cD48L286cD48
L3NwYW4+PC9pPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjpyZWQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjpyZWQiPlJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOnJlZCI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOnJlZCI+Q2hyaXN0ZXI8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6cmVkIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_7594FB04B1934943A5C02806D1A2204B4BD15355ESESSMB209erics_--


From nobody Tue Oct  4 03:43:42 2016
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 755481297CC for <mmusic@ietfa.amsl.com>; Tue,  4 Oct 2016 03:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 fcCJQhKAufDW for <mmusic@ietfa.amsl.com>; Tue,  4 Oct 2016 03:43:39 -0700 (PDT)
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 A8FAA1297CB for <mmusic@ietf.org>; Tue,  4 Oct 2016 03:43:38 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-dd-57f387d8dcb4
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by  (Symantec Mail Security) with SMTP id A3.C2.02551.8D783F75; Tue,  4 Oct 2016 12:43:36 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0319.002; Tue, 4 Oct 2016 12:43:36 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
Thread-Index: AQHSHiwofDubrkbtCEu3VfmkQRPgmg==
Date: Tue, 4 Oct 2016 10:43:36 +0000
Message-ID: <D41963FD.1059F%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_D41963FD1059Fchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCIsWRmVeSWpSXmKPExsUyM2J7oO6N9s/hBgvem1tMXf6YxWLxgfus DkweU35vZPVYsuQnUwBTFJdNSmpOZllqkb5dAlfGn/ZPLAXPZCp2TF7J3MDYKNnFyMkhIWAi cWTmZpYuRi4OIYH1jBKzGnqYIJxFjBJPfs1i7WLk4GATsJDo/qcN0iAioC7xdW8PM4jNLKAr 8ezWUTBbWCBN4vGc1UwQNdkS29feYYaw9SSmH+xhBLFZBFQkjnR2g9XwClhLHD4+jx3EZhQQ k/h+ag0TxExxiVtP5jNBHCcgsWTPeWYIW1Ti5eN/rCC2KNDM719nQ8WVJH5suMQC0ZsgcXff VWaI+YISJ2c+YZnAKDwLydhZSMpmISmDiBtIvD83nxnC1pZYtvA1lK0vsfHLWUYI21qi++9+ dmQ1Cxg5VjGKFqcWF+emGxnrpRZlJhcX5+fp5aWWbGIExtXBLb91dzCufu14iFGAg1GJhzch 5VO4EGtiWXFl7iFGCQ5mJRFeR2BUCvGmJFZWpRblxxeV5qQWH2KU5mBREuc1W3k/XEggPbEk NTs1tSC1CCbLxMEp1cCY+pNt+qTL81elnFJQzm7e/sjRKYTryAnzj28mmWVeNypc7vmN6ZN4 6+7OmLMKtoGv9e9H9mfXLWh9GTpr3h4z+yLvG5WLm9pFlfdHrRPaOM9MiSnQpujXnN2XFi7g n1y6WLX1m3boqdmRF9LOHeSz+1OwqKE4Ylvmmr3unU+Cdp6fbxdS062ixFKckWioxVxUnAgA ec6InacCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/fOetJjQUW0e6xGAJ1MrUgVjaVXE>
Cc: "snandaku@cisco.com" <snandaku@cisco.com>
Subject: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Oct 2016 10:43:40 -0000

--_000_D41963FD1059Fchristerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

Based on Ekr=92s review of BUNDLE, it has been suggested that the text shou=
ld not focus so much on whether the bundled m- line addresses are =93shared=
=94 or =93unique=94. The important thing is that the BUNDLE m- line specifi=
es the address for the bundle group.

I wonder if the same thing applies also to SDP attributes (read: draft-ietf=
-mmusic-sdp-mux-attributes): E.g., what is important is whether an attribut=
e property is applied to all bundled m- lines or not (based on the mux cate=
gory) =96 not whether the SDP attribute values must be identical in differe=
nt m- lines.

Comments?

Regards,

Christer

--_000_D41963FD1059Fchristerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <DD18A87E7B95C342824DCAD59310CE9A@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Hi,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Based on Ekr=92s review of BUNDLE, it has been suggested that the text shou=
ld not focus so much on whether the bundled m- line addresses are =93shared=
=94 or =93unique=94. The important thing is that the BUNDLE m- line specifi=
es the address for the bundle group.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-serif">I w=
onder if the same thing applies also to SDP attributes (read:&nbsp;</font><=
span style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-serif"><sp=
an style=3D"white-space: pre-wrap;">draft-ietf-mmusic-sdp-mux-attributes):
 E.g., what is important is whether an attribute property is applied to all=
 bundled m- lines or not (based on the mux category) =96 not whether the SD=
P attribute values must be identical in different m- lines.</span></font></=
span></div>
<div style=3D"orphans: 2; widows: 2;"><span style=3D"orphans: 2; widows: 2;=
"><font face=3D"Calibri,sans-serif"><span style=3D"white-space: pre-wrap;">=
<br>
</span></font></span></div>
<div style=3D"orphans: 2; widows: 2;"><span style=3D"orphans: 2; widows: 2;=
"><font face=3D"Calibri,sans-serif"><span style=3D"white-space: pre-wrap;">=
Comments?</span></font></span></div>
<div style=3D"orphans: 2; widows: 2;"><span style=3D"orphans: 2; widows: 2;=
"><font face=3D"Calibri,sans-serif"><span style=3D"white-space: pre-wrap;">=
<br>
</span></font></span></div>
<div style=3D"orphans: 2; widows: 2;"><span style=3D"orphans: 2; widows: 2;=
"><font face=3D"Calibri,sans-serif"><span style=3D"white-space: pre-wrap;">=
Regards,</span></font></span></div>
<div style=3D"orphans: 2; widows: 2;"><span style=3D"orphans: 2; widows: 2;=
"><font face=3D"Calibri,sans-serif"><span style=3D"white-space: pre-wrap;">=
<br>
</span></font></span></div>
<div style=3D"orphans: 2; widows: 2;"><span style=3D"orphans: 2; widows: 2;=
"><font face=3D"Calibri,sans-serif"><span style=3D"white-space: pre-wrap;">=
Christer</span></font></span></div>
</body>
</html>

--_000_D41963FD1059Fchristerholmbergericssoncom_--


From nobody Wed Oct  5 03:38:21 2016
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 3D7B612965C for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 03:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 w6IdgN71bHRg for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 03:38:17 -0700 (PDT)
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 6952E129659 for <mmusic@ietf.org>; Wed,  5 Oct 2016 03:38:17 -0700 (PDT)
X-AuditID: c1b4fb25-14bff7000000793b-41-57f4d817e112
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.183.54]) by  (Symantec Mail Security) with SMTP id C1.35.31035.718D4F75; Wed,  5 Oct 2016 12:38:15 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0319.002; Wed, 5 Oct 2016 12:37:08 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I) - Ekr's comment on the Mux Category Considerations section
Thread-Index: AQHSHvRrXpIDaHugL0CM2BY9aPgx0Q==
Date: Wed, 5 Oct 2016 10:37:08 +0000
Message-ID: <D41AB2F9.10708%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_D41AB2F910708christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKIsWRmVeSWpSXmKPExsUyM2K7ma74jS/hBpvPqFmseH2O3WLq8scs DkweS5b8ZPKY/LiNOYApissmJTUnsyy1SN8ugSvjynSPgt8WFZsOtjA2MF4z7GLk5JAQMJG4 seIwexcjF4eQwHpGif2/T7JCOIsYJfo6HzN3MXJwsAlYSHT/0wZpEBFQkPj15wQLiM0sIC9x YckaJpB6YYGJjBILJq0DmyQiMIlRouPaEWaIDj2JG9t+soHYLAIqEttv94LZvALWEs97N4PZ jAJiEt9PgUwCmSoucevJfCaI8wQkluw5zwxhi0q8fPyPFcQWBZr5/etsqLiSxI8Nl6AuSpA4 tHc/E8R8QYmTM5+wTGAUnoVk7CwkZbOQlEHEDSTen5vPDGFrSyxb+BrK1pfY+OUsI4RtLfFu TgcLspoFjByrGEWLU4uTctONjPVSizKTi4vz8/TyUks2MQIj6+CW36o7GC+/cTzEKMDBqMTD +2Dr53Ah1sSy4srcQ4wSHMxKIrznr30JF+JNSaysSi3Kjy8qzUktPsQozcGiJM5rtvJ+uJBA emJJanZqakFqEUyWiYNTqoGR55PbLCFf0z2z9fzlnIRrHomazpPYrM5WcngX5/vlHQ+dCtfv 1XnxLSbheoBCwXS/Yz82coe8YeTf5bWxOTRSW5y5NXL+7xVrHR3Uv/OJ2Jdm+DEs0OxZUWw+ Z2bXqh8xe64djai9/nDakbCE6Zl5XzpXmz3tfNt4tOgZR1yKHlti+fHlGieUWIozEg21mIuK EwEG4/LyqAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/h6Cx48_-gWl8pbeSU-oJfb1Pe7c>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I) - Ekr's comment on the Mux Category Considerations section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 10:38:19 -0000

--_000_D41AB2F910708christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

=85

>S 8.1.
>This seems like a key concept: there are a number of different categories
>of attributes and some are shared with all members of a bundle group
>and some are not. To what extent is this draft just duplicative of those
>listed in the mux-attributes draft?

Not sure I understand the question.

My point is that the concept you need to know for *this draft* is:

- Some attributes are shared and some are not.

The detailed rules are defined in the mux attributes draft, right?


Yes. So, perhaps we should not use RFC2119 terminology in draft-bundle, but=
 simple refer to draft-mux-attributes for the rules.

That would be my recommendation.

I had a closer look at this, and the text is actually NOT covered by draft-=
mux-attributes.

While draft-mux-attributes defines the categories, the attribute value rest=
rictions based on category etc, the text in Section 8.1 says that IDENTICAL=
/TRANSPORT category attribute are only associated with the BUNDLE-tag m- li=
ne to begin with.

We can of course discuss whether THAT should also be described in draft-mux=
-attributres, but currently it=92s not.

Regards,

Christer

--_000_D41AB2F910708christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <C6198121DC57D14791D9CB833C6D6072@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><font col=
or=3D"#ff0000">Hi,</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
=85</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<blockquote class=3D"gmail_quote" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px; color: rgb(0, 0, 0); margin: 0px 0px 0px 0.8ex; border-l=
eft-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: s=
olid; padding-left: 1ex;">
<div style=3D"word-wrap:break-word"><span class=3D""><span style=3D"font-fa=
mily:Calibri,sans-serif;font-size:14px">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<div lang=3D"EN-GB"><span>
<div>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;S 8.1.<u></u><u></u></span></p>
</div>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;This seems like a key concept: there are a numb=
er of different categories<u></u><u></u></span></p>
</div>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;of attributes and some are shared with all memb=
ers of a bundle group<u></u><u></u></span></p>
</div>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;and some are not. To what extent is this draft =
just duplicative of those<u></u><u></u></span></p>
</div>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">&gt;listed in the mux-attributes draft?<u></u><u></=
u></span></p>
</div>
</div>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black"><u></u>&nbsp;<u></u></span></p>
</div>
</span>
<div style=3D"color:rgb(0,0,0)">
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:calibri,=
sans-serif;color:black">Not sure I understand the question.</span></p>
</div>
</div>
</blockquote>
<div style=3D"color:rgb(0,0,0)"><br>
</div>
<div style=3D"color:rgb(0,0,0)">My point is that the concept you need to kn=
ow for *this draft* is:</div>
<div style=3D"color:rgb(0,0,0)"><br>
</div>
<div style=3D"color:rgb(0,0,0)">- Some attributes are shared and some are n=
ot.</div>
<div style=3D"color:rgb(0,0,0)"><br>
</div>
<div style=3D"color:rgb(0,0,0)">The detailed rules are defined in the mux a=
ttributes draft, right?</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
</span>
<div><font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">Yes. So, per=
haps we should not use RFC2119 terminology in draft-bundle, but simple refe=
r to&nbsp;draft-mux-attributes for the rules.&nbsp;</font></font></div>
</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
That would be my recommendation.</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<span style=3D"color:black;font-family:calibri,sans-serif;font-size:10.5pt"=
><br>
</span></div>
<div><font color=3D"#ff0000"><font face=3D"calibri,sans-serif" size=3D"3">I=
 had a closer look at this, and the text is actually NOT covered by draft-m=
ux-attributes.
</font></font></div>
</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><font color=3D"#ff0000"><font face=3D"calibri,sans-serif" size=3D"3">W=
hile draft-mux-attributes defines the categories, the attribute value restr=
ictions based on category etc, the text in Section 8.1 says that IDENTICAL/=
TRANSPORT category attribute are only
 associated with the BUNDLE-tag m- line to begin with. </font></font></div>
</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><font color=3D"#ff0000"><font face=3D"calibri,sans-serif" size=3D"3">W=
e can of course discuss whether THAT should also be described in draft-mux-=
attributres, but currently it=92s not.</font></font></div>
</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div><font color=3D"#ff0000">Regards,</font></div>
<div><font color=3D"#ff0000"><br>
</font></div>
<div><font color=3D"#ff0000">Christer</font></div>
</body>
</html>

--_000_D41AB2F910708christerholmbergericssoncom_--


From nobody Wed Oct  5 04:38:20 2016
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 580081296A2 for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 04:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 7ZGDGNuuFRez for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 04:38:16 -0700 (PDT)
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 4F0AE12969C for <mmusic@ietf.org>; Wed,  5 Oct 2016 04:38:16 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-ae-57f4e626a6e9
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by  (Symantec Mail Security) with SMTP id 38.3A.02551.626E4F75; Wed,  5 Oct 2016 13:38:14 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0319.002; Wed, 5 Oct 2016 13:37:35 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I) - PULL REQUEST
Thread-Index: AQHSHvzegkIFEVH970mtiPG9kfSxjQ==
Date: Wed, 5 Oct 2016 11:37:35 +0000
Message-ID: <D41AC1B6.10717%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_D41AC1B610717christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCIsWRmVeSWpSXmKPExsUyM2K7q67asy/hBovOKFuseH2O3WLq8scs DkweS5b8ZPKY/LiNOYApissmJTUnsyy1SN8ugSvj7czLTAVnjjJWbPn7j6WBsXUdYxcjJ4eE gIlE+5F7LCC2kMB6RokJtxK7GLmA7EWMEtefnmPqYuTgYBOwkOj+pw1SIyKgIPHrzwmwemYB eYkLS9YwgdjCAqkSO6a+YIeoSZNoO3+IBcLWk5h4czcbiM0ioCKxuf8PO8hIXgFriblTo0DC jAJiEt9PQYxhFhCXuPVkPhPEaQISS/acZ4awRSVePv7HCmKLAo38/nU2VFxJ4seGS1DnJEjc eXIX7C1eAUGJkzOfsExgFJ6FZOwsJGWzkJRBxA0k3p+bzwxha0ssW/gaytaX2PjlLCOEbS3x u+MhO7KaBYwcqxhFi1OLi3PTjYz1Uosyk4uL8/P08lJLNjEC4+rglt+6OxhXv3Y8xCjAwajE w/tg6+dwIdbEsuLK3EOMEhzMSiK8KU+/hAvxpiRWVqUW5ccXleakFh9ilOZgURLnNVt5P1xI ID2xJDU7NbUgtQgmy8TBKdXAyMHz46N0GxvX21SunMZmu7+aLs9nbz3y69tlwQu31zauvOsl smXZZrZN0syy2UfOFl3lkY9V/2kZsveOxuVMk2ahOI+Uwg9ePConJY/xcVw4e/zUj5JdSXdk PwV8WBlV4aW6eM+Pia9v9mc3XivdvTtNU+SD8bWfqmc2e75KOGRTVO1/bX/RRiWW4oxEQy3m ouJEACmacSmnAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/5DtkbIa4Fq1i9eZC7byaP5ExUHI>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I) - PULL REQUEST
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 11:38:19 -0000

--_000_D41AC1B610717christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


Hi,

I=92ve created a PR based on Ekr=92s comments.

Note that the PR only contains the =93easy=94 fixes. The bigger ones I will=
 start working on when it=92s clear that they are to be done.

https://github.com/cdh4u/draft-sdp-bundle/pull/8

Regards,

Christer


From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on b=
ehalf of Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.=
holmberg@ericsson.com>>
Date: Tuesday 4 October 2016 at 02:14
To: Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtfm.com>>
Cc: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32=
 (Part I)

Hi,

OVERALL

>The overall framing of this document as being about attaching multiple
>m=3D sections to a single "shared address" is extremely problematic,
>for two reasons:
>
>- With ICE there isn't actually any notion of a shared address except
>  in some vague sense. I suppose you could argue that because with
>  ICE you are required to specify a port on the m=3D line then you
>  still have a concept of an address, but that's not true in
>  trickle ICE, where the port is 9, so all m=3D lines share the same
>  address/port. So, actually when you use trickle a whole bunch of
>  the statements in this document are wrong.
>
>- A lot more is being overloaded here than addresses. In fact, a whole
>  pile of semantics are being overloaded, so the way to think about
>  this is actually as gluing a whole bunch of m=3D lines together at
>  the transport level.
>
> I think the right concept here is not "shared address" but "bundle group"
> and the document should be written in that way, namely that there are
> a  bunch of m=3D lines in a bundle group and the one with the bundle tag
> is the one that sets all the shared parameters.

It is true that the actual port value in the m- line, and the IP address in=
 the c- line address, represent the address that is actually being used.

But, even with ICE there is a shared address, isn=92t there? Yes, that shar=
ed address may change, but at any given time there will be one address that=
 is shared among the media streams within the BUNDLE group. Or?

Not if you trickle, no. Then all the m=3D lines have the same address wheth=
er they are bundled or not.


Ok, I hear you. You are basically saying that it doesn=92t matter whether b=
undled m- lines share addresses or not =96 the ONLY thing that matters is t=
hat the m- line associated with the bundle tag contains the address to be u=
sed.

The reason we mandated shared addresses, once the usage of BUNDLE had been =
negotiated, was because of intermediaries that don=92t support BUNDLE (to m=
ake sure they send media towards the correct address). But, maybe we don=92=
t need to worry about anymore =96 BUNDLE probably won=92t work reliably wit=
h such intermediaries anyway=85

Also, there is at least once case where the address matters: when you add a=
 new m- line to a bundle group. If you use a unique address, and the answer=
er does not accept the m- line in the BUNDLE group, it can be used un-bundl=
ed. If you use a shared address, the answerer will have to reject the m- li=
ne.

I think this is all true, but what I am trying to say here is, I think, con=
ceptually different:

BUNDLED m=3D lines are grouped together and share a bunch of properties. Am=
ongst those properties is that they share IP addresses, but it's not the on=
ly thing they share, nor is it it the indicator that they are shared (that'=
s the a=3Dgroup:BUNDLE list). So the top-line category isn't shared vs/uniq=
ue IP address but rather bundled vs. unbundled.

Correct.

The best thing, as far as the address in the m- line is concerned, would be=
 to simply use normal SDP procedures (read: unique addresses) also for bund=
led m- lines. And, if the offerer wants to make sure a mid-session added m-=
 line gets accepted in the bundle group (or otherwise is rejected) he would=
 use bundle-only =96 in the same way it=92s used in the initial offer.

Then a =93shared address=94 would only be a property of the BUNDLE group =
=96 not related to the address put in the m- line.

I worry that we're not communicating. I would have this document never refe=
r to "shared" or "unique" addresses and instead refer to bundled or unbundl=
ed m=3D lines.

Earlier you said that =93shared address=94 is one of the PROPERTIES of a bu=
ndled m- line, and that is what I was referring to. Other than that, we wou=
ld not have to talk about =93shared=94 or =93unique=94 addresses, as you su=
ggest.

=93BUNDLED m=3D lines are grouped together and share a bunch of properties.=
 Amongst those properties is that they share IP addresses,=94

Regards,

Christer



--_000_D41AC1B610717christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <7AC814302533CA48A07A7A8104CB421C@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div><br>
</div>
<div>Hi,</div>
<div><br>
</div>
<div>I=92ve created a PR based on Ekr=92s comments.</div>
<div><br>
</div>
<div>Note that the PR only contains the =93easy=94 fixes. The bigger ones I=
 will start working on when it=92s clear that they are to be done.</div>
<div><br>
</div>
<div><a href=3D"https://github.com/cdh4u/draft-sdp-bundle/pull/8">https://g=
ithub.com/cdh4u/draft-sdp-bundle/pull/8</a></div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>mmusic &lt;<a href=3D"mailto:=
mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a>&gt; on behalf of Chris=
ter Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">christer=
.holmberg@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday 4 October 2016 at 02:=
14<br>
<span style=3D"font-weight:bold">To: </span>Eric Rescorla &lt;<a href=3D"ma=
ilto:ekr@rtfm.com">ekr@rtfm.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:mmusic@=
ietf.org">mmusic@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org">=
mmusic@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [MMUSIC] Review of dra=
ft-ietf-mmusic-sdp-bundle-negotiation-32 (Part I)<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red;mso-fareast-language:EN-US">Hi,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p>&nbsp=
;</o:p></span></p>
<div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt">
<div>
<div>
<div>
<div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt">
<div>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">OVERALL</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt;The overall framing of this document as being abo=
ut attaching multiple</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt;m=3D sections to a single &quot;shared address&qu=
ot; is extremely problematic,</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt;for two reasons:</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt;&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt;- With ICE there isn't actually any notion of a s=
hared address except</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; &nbsp;in some vague sense. I suppose you could a=
rgue that because with</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; &nbsp;ICE you are required to specify a port on =
the m=3D line then you</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; &nbsp;still have a concept of an address, but th=
at's not true in</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; &nbsp;trickle ICE, where the port is 9, so all m=
=3D lines share the same</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; &nbsp;address/port. So, actually when you use tr=
ickle a whole bunch of</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; &nbsp;the statements in this document are wrong.=
</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt;&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt;- A lot more is being overloaded here than addres=
ses. In fact, a whole</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; &nbsp;pile of semantics are being overloaded, so=
 the way to think about</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; &nbsp;this is actually as gluing a whole bunch o=
f m=3D lines together at</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; &nbsp;the transport level.</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt;&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; I think the right concept here is not &quot;shar=
ed address&quot; but &quot;bundle group&quot;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; and the document should be written in that way, =
namely that there are</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; a &nbsp;bunch of m=3D lines in a bundle group an=
d the one with the bundle tag</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&gt; is the one that sets all the shared parameters.<=
/span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">It is true that the actual port value in the m- line,=
 and the IP address in the c- line address, represent
 the address that is actually being used.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">But, even with ICE there is a shared address, isn=92t=
 there? Yes, that shared address may change, but at
 any given time there will be one address that is shared among the media st=
reams within the BUNDLE group. Or?</span><o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">Not if you trickle, no. Then all the m=3D lines have =
the same address whether they are bundled or not.</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:red">Ok, I hear you. You are basically saying that it doesn=
=92t matter whether bundled m- lines share addresses
 or not&nbsp;=96&nbsp;the ONLY thing that matters is that the m- line assoc=
iated with the bundle tag contains the address to be used.</span><o:p></o:p=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:red">The reason we mandated shared addresses, once the usage=
 of BUNDLE had been negotiated, was because of intermediaries
 that don=92t support BUNDLE (to make sure they send media towards the corr=
ect address). But, maybe we don=92t need to worry about anymore&nbsp;=96&nb=
sp;BUNDLE&nbsp;probably won=92t work reliably with such&nbsp;intermediaries=
 anyway=85</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:black">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sa=
ns-serif;color:red">Also, there is at least once case where the address mat=
ters: when you add a new m- line to a bundle group.
 If you use a unique address, and the answerer does not accept the m- line =
in the BUNDLE group, it can be used un-bundled. If you use a shared address=
, the answerer will have to reject the m- line.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I think this is all true, but what I am trying to say here is, I t=
hink, conceptually different:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">BUNDLED m=3D lines are grouped together and share a bunch of prope=
rties. Amongst those properties is that they share IP addresses, but it's n=
ot the only thing they share, nor is it
 it the indicator that they are shared (that's the a=3Dgroup:BUNDLE list). =
So the top-line category isn't shared vs/unique IP address but rather bundl=
ed vs. unbundled.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:red">Correct.
</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:red">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:red">The best thing, as far as the address in=
 the m- line is concerned, would be to simply use normal SDP procedures (re=
ad: unique addresses) also for bundled
 m- lines. And, if the offerer wants to make sure a mid-session added m- li=
ne gets accepted in the bundle group (or otherwise is rejected) he would us=
e bundle-only =96 in the same way it=92s used in the initial offer.</span><=
o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:red">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:red">Then a =93shared address=94 would only b=
e a property of the BUNDLE group =96 not related to the address put in the =
m- line.</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I worry that we're not communicating. I would have t=
his document never refer to &quot;shared&quot; or &quot;unique&quot; addres=
ses and instead refer to bundled or unbundled m=3D lines.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Earlier you said that =93shared address=
=94 is one of the PROPERTIES of a bundled m- line, and that is what I was r=
eferring to. Other than that, we would not have to talk
 about =93shared=94 or =93unique=94 addresses, as you suggest.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><i><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif;color:red">=93</span><span style=3D"color:red">BU=
NDLED m=3D lines are grouped together and share a bunch of properties. Amon=
gst those properties is that they share IP addresses,=94</span></i><i><span=
 style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color=
:red"><o:p></o:p></span></i></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Christer<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D41AC1B610717christerholmbergericssoncom_--


From nobody Wed Oct  5 04:44:08 2016
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 8C004129699 for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 04:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 aMjNNL89tduw for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 04:44:04 -0700 (PDT)
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 222B2126579 for <mmusic@ietf.org>; Wed,  5 Oct 2016 04:44:03 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-93-57f4e7822c38
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by  (Symantec Mail Security) with SMTP id A3.BB.02551.287E4F75; Wed,  5 Oct 2016 13:44:02 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0319.002; Wed, 5 Oct 2016 13:43:41 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Comments on draft-ietf-mmusic-ice-sip-sdp regarding explicit removal of candidites
Thread-Index: AQHSHv23lZBBDzjMdkmyC9773lLPTg==
Date: Wed, 5 Oct 2016 11:43:40 +0000
Message-ID: <D41AC393.10727%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.147]
Content-Type: multipart/alternative; boundary="_000_D41AC39310727christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyM2K7n27T8y/hBnt6VSymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujNOTpzIVnNWsmH1yA3sD4zqlLkZODgkBE4kVvQ2MXYxcHEIC 6xklpjReY4VwFjFKNB5+DZTh4GATsJDo/qcN0iAioC7xdW8PM4gtLBArsXfNCXaIeJLEx917 WSBsPYn7Ww6D1bAIqEj0bd3PBGLzClhLdMx4BhZnFBCT+H5qDVicWUBc4taT+UwQBwlILNlz nhnCFpV4+fgfK4gtCjTz+9fZzCDnSAgoSUzbmgbRmiDxqX071HhBiZMzn7BMYBSahWTqLCRl s5CUQcQNJN6fm88MYWtLLFv4GsrWl9j45SwjhG0t8fT4E0ZkNQsYOVYxihanFhfnphsZ66UW ZSYXF+fn6eWllmxiBEbKwS2/dXcwrn7teIhRgINRiYf3wdbP4UKsiWXFlbmHGCU4mJVEeDc8 /RIuxJuSWFmVWpQfX1Sak1p8iFGag0VJnNds5f1wIYH0xJLU7NTUgtQimCwTB6dUAyOLj4mF o/pBzXlt+8qSOjbxMj452nKnxfSpXKb8ba64P5WPwvKPm1iknStbZM+fJv98suSJcgun2J6D nQlnBSbwfHJ9eu6dX6Nr3Y7ak3Y51+x9JhqcazmzyXMC66bL12ICN57yd06M5jG8sInj64bT kx5Y1X5pP1e9/027qnPU4cL0ySqB4kosxRmJhlrMRcWJAHNcGRqQAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/CGB-ozi5WxjH12rvFFKkVqEgtMg>
Subject: [MMUSIC] Comments on draft-ietf-mmusic-ice-sip-sdp regarding explicit removal of candidites
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 11:44:06 -0000

--_000_D41AC39310727christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

I first sent the comments on draft-ietf-mmusic-ice-sip-sdp below to the ICE=
 list, but then realised they belong on the MMUSIC list.

It=92s related to the current suggestion that it should be possible to expl=
icitly remove candidates in ICE, and whether trickle assumes that candidate=
s can NOT be removed.

It has been suggested that removal of candidates should not be part of tric=
kle, but rather be defined in a separate future extension draft. The commen=
ts below are based on that such =93extension=94 may exist at some point.

The text in section 4.2 says:

   "In every INFO request agents MUST include all local candidates they
   have signaled previously.  This is necessary in order to more easily
   avoid problems that would arise from unreliable transports.  Mis-
   ordering can be detected through the CSeq: header field in the INFO
   request.  As a consequence candidates cannot be removed unless an ICE
   restart is performed.  Note that extension might be specified in the
   future that enable such removal without a restart.=94

Q1: Assuming someone does define an extension which allows removal of candi=
dates without a restart, do such candidates still have to be included in th=
e INFO, as they have been =93previously signalled"? What is the scope of =
=93previously=94? Previously since when?

Q2: What if an INFO does NOT contain a local candidate that has previously =
been signaled? Do we assume it has been removed using some =93extension=94?=
 Do we assume it=92s still there?

Q3: What if a candidate has bee removed using some =93extension=94, and the=
n it still shows up in an INFO? Does it mean it=92s automatically added bac=
k?

At one point I suggested that the INFO should ONLY contain the added candid=
ates, and would say nothing about existing candidates. But, as that was not=
 accepted I think Q1-Q3 needs to be clarified in the document.

Thanks!

Regards,

Christer

--_000_D41AC39310727christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <189848A13F5770489E600D3037811CFA@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>I first sent the comments on&nbsp;<span style=3D"orphans: 2; white-spa=
ce: pre-wrap; widows: 2;">draft-ietf-mmusic-ice-sip-sdp
</span>below to the ICE list, but then realised they belong on the MMUSIC l=
ist.</div>
<div><br>
</div>
<div>It=92s related to the current suggestion that it should be possible to=
 explicitly remove candidates in ICE, and whether trickle assumes that cand=
idates can NOT be removed.</div>
<div><br>
</div>
<div>It has been suggested that removal of candidates should not be part of=
 trickle, but rather be defined in a separate future extension draft. The c=
omments below are based on that such =93extension=94 may exist at some poin=
t.</div>
<div><br>
</div>
<div>
<div>The text in section 4.2 says:</div>
<div>
<pre style=3D"font-variant-ligatures: normal; orphans: 2; widows: 2; word-w=
rap: break-word; white-space: pre-wrap;">   &quot;In every INFO request age=
nts MUST include all local candidates they
   have signaled previously.  This is necessary in order to more easily
   avoid problems that would arise from unreliable transports.  Mis-
   ordering can be detected through the CSeq: header field in the INFO
   request.  As a consequence candidates cannot be removed unless an ICE
   restart is performed.  Note that extension might be specified in the
   future that enable such removal without a restart.=94</pre>
</div>
<div>Q1: Assuming someone does define an extension which allows removal of =
candidates without a restart, do such candidates still have to be included =
in the INFO, as they have been =93previously signalled&quot;? What is the s=
cope of =93previously=94? Previously since
 when?</div>
<div><br>
</div>
<div>Q2: What if an INFO does&nbsp;<span style=3D"font-weight: bold;">NOT</=
span>&nbsp;contain a local candidate that has previously been signaled? Do =
we assume it has been removed using some =93extension=94? Do we assume it=
=92s still there?</div>
<div><br>
</div>
<div>Q3: What if a candidate has bee removed using some =93extension=94, an=
d then it still shows up in an INFO? Does it mean it=92s automatically adde=
d back?</div>
<div><br>
</div>
<div>At one point I suggested that the INFO should&nbsp;<span style=3D"font=
-weight: bold;">ONLY</span>&nbsp;contain the added candidates, and would sa=
y nothing about existing candidates. But, as that was not accepted I think =
Q1-Q3 needs to be clarified in the document.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
</div>
</body>
</html>

--_000_D41AC39310727christerholmbergericssoncom_--


From nobody Wed Oct  5 07:09:07 2016
Return-Path: <thomass.stach@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 CF0E2129737 for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 07:09:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 GtK6FszntJnc for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 07:09:04 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 9ED4F12972C for <mmusic@ietf.org>; Wed,  5 Oct 2016 07:09:03 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id l131so213403389lfl.2 for <mmusic@ietf.org>; Wed, 05 Oct 2016 07:09:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=1Hd2JY3lxR0fBeRMOCyShMrheSJlIyqsS6vKAcBxGyY=; b=sSfgICAw8lkI6yt3xJJuj8IoJyBcLhZLCW044QTywzbNeRHf1i17Q8W/riOM2s0D6Y nqyz+xqKMNQlYszeFDTdoRA8qZeU2S7RwjYaOm35ZFxnydWBObcm3rsjccPbtMXkcVs7 JeFF4/cqeoBnkGMUxdTUXFyT2pnvZrULBY17iGXp5TmKpulU75TUcSYbxotRKKaIfk9h 98quHrFRpc7qthxq/UbiowqdwEMHM1d3ci63rRC6Ihlv4jIaVbNvsBGDTtT4DZ+m6RnQ 5XyQSc4AmzJhY3ZhFsAYYSnt+VvTHhg7Z3p0SvfD7MKQv8KeP71c3eEEl9ttioa+Jh6j UdWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=1Hd2JY3lxR0fBeRMOCyShMrheSJlIyqsS6vKAcBxGyY=; b=QO2wLOIoqi7hzTsd/GrVgye/sBgtv4ZPFNPTaTT7CQzktLzZhImDij4OnbrRvSqve5 Bo3jP4trT22W18dU/Q2Ylq2rJPdCGZFJ0XWnrH2Vjf5yRpPsjqUnGVV+38BFVe+JZLlf 1nK7gtz5Hh+A+V9booaLA4RGg/g6s0Oe/8tZeV6bsiq5MtG4sY6y1YT8SWZAiuM1cK3T CsoP9WVBhCov1sQDaxpMptN9/2AtuVovAMoVQxU3sBFR/VFooxnon7wiy6QSLbB5404i ztkGoYKQMcnV5PQk/EGJViwTUszcJqctHh8nxccONHqoQwhF0LuBUwJ/+eUbFvXPbQCm eG8g==
X-Gm-Message-State: AA6/9RkoeoGlH1eIKMSQXtZ9lWXdhE/F4s/c+eI5I8eBZDGpGPzzsU3qf3tAgTh5TWUljw==
X-Received: by 10.194.157.193 with SMTP id wo1mr7920924wjb.22.1475676541570; Wed, 05 Oct 2016 07:09:01 -0700 (PDT)
Received: from ?IPv6:2001:62a:4:41c:39e8:48c2:893:d097? ([2001:62a:4:41c:39e8:48c2:893:d097]) by smtp.googlemail.com with ESMTPSA id j198sm9798362wmg.4.2016.10.05.07.09.00 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Oct 2016 07:09:00 -0700 (PDT)
To: mmusic@ietf.org
References: <D41AC393.10727%christer.holmberg@ericsson.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <bc713d1a-acdb-af95-5391-b3e244e1126d@gmail.com>
Date: Wed, 5 Oct 2016 16:08:59 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <D41AC393.10727%christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ATUv0p5_mcNGDUzzjOjzriQvQSg>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 14:09:06 -0000

Christer,

I took the liberty to adjust the subject since the cited text is
is from draft-ietf-mmusic-trickle-ice-sip-05,
not from draft-ietf-mmusic-ice-sip-sdp.

more inline


On 2016-10-05 13:43, Christer Holmberg wrote:
> Hi,
>
> I first sent the comments on draft-ietf-mmusic-ice-sip-sdp below to 
> the ICE list, but then realised they belong on the MMUSIC list.
>
> It’s related to the current suggestion that it should be possible to 
> explicitly remove candidates in ICE, and whether trickle assumes that 
> candidates can NOT be removed
Trickle-ICE as specified in draft-ietf-ice-trickle-04 is about 
incremental provisioning of candidates. The draft does not mention 
removal of already trickled candidates anywhere in the document. This 
leads me to the conclusion that _currently_ you cannot signal that a 
candidate is to be removed again.

>
> It has been suggested that removal of candidates should not be part of 
> trickle, but rather be defined in a separate future extension draft. 
> The comments below are based on that such “extension” may exist at 
> some point.
>
> The text in section 4.2 says:
>     "In every INFO request agents MUST include all local candidates they
>     have signaled previously.  This is necessary in order to more easily
>     avoid problems that would arise from unreliable transports.  Mis-
>     ordering can be detected through the CSeq: header field in the INFO
>     request.  As a consequence candidates cannot be removed unless an ICE
>     restart is performed.  Note that extension might be specified in the
>     future that enable such removal without a restart.”
> Q1: Assuming someone does define an extension which allows removal of 
> candidates without a restart, do such candidates still have to be 
> included in the INFO, as they have been “previously signalled"?
This would have to clarified in that future extension document together 
with corresponding backward compatibility issues and/or indication of 
support for such an extension. I don't want to do design here, but 
a=ice-options might be something to look at.
> What is the scope of “previously”?
The current ICE generation (as defined by the currently used/exchanged 
ufrag/pwd)
> Previously since when?
Since current ufrag/pwd was signalled.
>
> Q2: What if an INFO does NOT contain a local candidate that has 
> previously been signaled? Do we assume it has been removed using some 
> “extension”? Do we assume it’s still there?
We could either treat this case as an error and ignore the content of 
that INFO.
Probably not the best idea, e.g. in case that a=end-of-candidates was 
included.
Or we can assume (in absence of any "removal extension") that it is 
still there. That would allow to still make use of any newly trickled 
candidates in such an INFO. This makes more sense to me.
If this is agreable I would be happy to put corresponding text into 
section 4.2.
>
> Q3: What if a candidate has bee removed using some “extension”, and 
> then it still shows up in an INFO? Does it mean it’s automatically 
> added back?
This is probably the easiest way to deal with that, as it does not 
require housekeeping. But again I see this as something that the future 
extension document has to deal with.

Regards
Thomas
>
> At one point I suggested that the INFO should ONLY contain the added 
> candidates, and would say nothing about existing candidates. But, as 
> that was not accepted I think Q1-Q3 needs to be clarified in the document.
>
> Thanks!
>
> Regards,
>
> Christer
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Wed Oct  5 07:57:02 2016
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 DCB23129770 for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 07:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 OHG2JgRpk8YD for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 07:57:00 -0700 (PDT)
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 EEC37129758 for <mmusic@ietf.org>; Wed,  5 Oct 2016 07:56:58 -0700 (PDT)
X-AuditID: c1b4fb25-5405a9800000793b-92-57f514b906f5
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by  (Symantec Mail Security) with SMTP id E1.E5.31035.9B415F75; Wed,  5 Oct 2016 16:56:57 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0319.002; Wed, 5 Oct 2016 16:56:56 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Thomas Stach <thomass.stach@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
Thread-Index: AQHSHxIL5dxB//uBWky8GjwyA0+P66CZ76sA
Date: Wed, 5 Oct 2016 14:56:55 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD1B3B2@ESESSMB209.ericsson.se>
References: <D41AC393.10727%christer.holmberg@ericsson.com> <bc713d1a-acdb-af95-5391-b3e244e1126d@gmail.com>
In-Reply-To: <bc713d1a-acdb-af95-5391-b3e244e1126d@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHLMWRmVeSWpSXmKPExsUyM2K7k+5Oka/hBnu3iltMXf6YxeLTia1M DkweO2fdZfdYsuQnUwBTFJdNSmpOZllqkb5dAlfGv2m/mQv2ylRMuviSsYHxjFgXIweHhICJ xOXjVl2MXBxCAusZJb7euMII4SxilNj5+h47SBGbgIVE9z/tLkZODhGBQInPZ44zgdQIC0xl lNjasZYZIjGNUeLpUisI20ji0/c37CA2i4CKxJa/C8FsXgFfiVvf9jGBzBQSyJPY+1gTxOQU sJXofWQAUsEoICbx/dQaJhCbWUBc4taT+WC2hICAxJI955khbFGJl4//sULYShIrtl9ihKjX kViw+xMbhK0tsWzha2aIrYISJ2c+YZnAKDILydhZSFpmIWmZhaRlASPLKkbR4tTipNx0I2O9 1KLM5OLi/Dy9vNSSTYzAWDi45bfqDsbLbxwPMQpwMCrx8D7Y+jlciDWxrLgy9xCjBAezkghv l/DXcCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8ZivvhwsJpCeWpGanphakFsFkmTg4pRoYS+cv +6C9/mgFx2WFWtEVC/YYhHx9vYrz7Lnfa9uXaOzYcqX5r0npgnK36lTtynWO6eoGsgtjpN/P q46ZtKflgfi6efNT6wt/ng95w/mjM+fpPb5tWgH3kj6+t/jAfXShANMvptWOAaXxzqk5kyZ/ YQtr7/jJcuFuGAfPRc58lhwOrkUfwr6pKbEUZyQaajEXFScCAKDckQKBAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/XT4e3g18VXP2IRJ12vqjzDyHPRY>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 14:57:02 -0000

Hi,

>I took the liberty to adjust the subject since the cited text is is from d=
raft-ietf-mmusic-trickle-ice-sip-05,
>not from draft-ietf-mmusic-ice-sip-sdp.

Thanks!

>> It has been suggested that removal of candidates should not be part of=20
>> trickle, but rather be defined in a separate future extension draft.
>> The comments below are based on that such "extension" may exist at=20
>> some point.
>>
>> The text in section 4.2 says:
>>     "In every INFO request agents MUST include all local candidates they
>>     have signaled previously.  This is necessary in order to more easily
>>     avoid problems that would arise from unreliable transports.  Mis-
>>     ordering can be detected through the CSeq: header field in the INFO
>>     request.  As a consequence candidates cannot be removed unless an IC=
E
>>     restart is performed.  Note that extension might be specified in the
>>     future that enable such removal without a restart."
>> Q1: Assuming someone does define an extension which allows removal of=20
>> candidates without a restart, do such candidates still have to be=20
>> included in the INFO, as they have been "previously signalled"?
>
> This would have to clarified in that future extension document together w=
ith corresponding backward
> compatibility issues and/or indication of support for such an extension. =
I don't want to do design here,=20
> but a=3Dice-options might be something to look at.

How you indicate support of such extension is outside the scope of this thr=
ead. I want to clarify the exact semantics of a candidate in an INFO.

>> What is the scope of "previously"?
>
>The current ICE generation (as defined by the currently used/exchanged ufr=
ag/pwd)
>> Previously since when?
> Since current ufrag/pwd was signalled.

Is that said anywhere?

Also, an "extension" could have removed candidiates since the ufrag/pwd was=
 signalled. So, you cannot simply say "since current ufrag/pwd was signalle=
d". You also need to say something like "and are still active/in use", or s=
omething like that.


>> Q2: What if an INFO does NOT contain a local candidate that has=20
>> previously been signaled? Do we assume it has been removed using some=20
>> "extension"? Do we assume it's still there?
>
> We could either treat this case as an error and ignore the content of tha=
t INFO.
> Probably not the best idea, e.g. in case that a=3Dend-of-candidates was i=
ncluded.
> Or we can assume (in absence of any "removal extension") that it is still=
 there. That=20
> would allow to still make use of any newly trickled candidates in such an=
 INFO. This makes more sense to me.
> If this is agreable I would be happy to put corresponding text into secti=
on 4.2.

...or, we could go back to my previous proposal, and say that we *ONLY* sig=
nal the new candidates, and that the INFO has no impact on any other candid=
ates :)

Also, assuming all current candidates are present in INFOs, what about peer=
 reflexive candidates? Will they be present in INFOs?

>>> Q3: What if a candidate has bee removed using some "extension", and=20
>>> then it still shows up in an INFO? Does it mean it's automatically=20
>>> added back?
>>
>>This is probably the easiest way to deal with that, as it does not requir=
e housekeeping.=20
>>But again I see this as something that the future extension document has =
to deal with.

...or, we could go back to my previous proposal, and say that we *ONLY* sig=
nal the new candidates, and that the INFO has no impact on any other candid=
ates :)

Regards,

Christer



From nobody Wed Oct  5 10:44:19 2016
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 CB5F31297B9 for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 10:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7TYs7hbyNn3l for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 10:44:14 -0700 (PDT)
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 DF7ED129587 for <mmusic@ietf.org>; Wed,  5 Oct 2016 10:44:13 -0700 (PDT)
X-AuditID: c1b4fb30-b73ff70000000cb2-8a-57f53be8c761
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by  (Symantec Mail Security) with SMTP id F2.C3.03250.8EB35F75; Wed,  5 Oct 2016 19:44:12 +0200 (CEST)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.66) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 5 Oct 2016 19:44:08 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ucYXgMeLkY0wIe0y25kjJ/WPf7fO4VtPmLJePD3oCJA=; b=Fa//LpXgJQ9upxriNot98EsWvMCIAXge0ryBVvbsooRTJsgCcRqd5SMXMojli1OvulGbLV+pjWPdYeZNY5GwmwgT9s0pCFnLiQdXkrI50soB3ENWeAssLKUoTAcRB2uE0Ed2Eb+iuH/Ja4p1TtNd/VBY3fFrASHETHSMyuAn7cc=
Received: from AM5PR0701MB2577.eurprd07.prod.outlook.com (10.173.92.21) by AM5PR0701MB2577.eurprd07.prod.outlook.com (10.173.92.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.649.16; Wed, 5 Oct 2016 17:44:06 +0000
Received: from AM5PR0701MB2577.eurprd07.prod.outlook.com ([10.173.92.21]) by AM5PR0701MB2577.eurprd07.prod.outlook.com ([10.173.92.21]) with mapi id 15.01.0649.021; Wed, 5 Oct 2016 17:44:06 +0000
From: Bo Burman <bo.burman@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
Thread-Index: AQHSHiwofDubrkbtCEu3VfmkQRPgmqCaG2pA
Date: Wed, 5 Oct 2016 17:44:06 +0000
Message-ID: <AM5PR0701MB25770AB3719E8C10A6C040058DC40@AM5PR0701MB2577.eurprd07.prod.outlook.com>
References: <D41963FD.1059F%christer.holmberg@ericsson.com>
In-Reply-To: <D41963FD.1059F%christer.holmberg@ericsson.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=bo.burman@ericsson.com; 
x-originating-ip: [192.176.1.85]
x-ld-processed: 92e84ceb-fbfd-47ab-be52-080c6b87953f,ExtAddr
x-ms-office365-filtering-correlation-id: 8de08f5d-9b64-4369-00c6-08d3ed473464
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB2577; 6:0nR5pmamm98xqDsqDFLAd1bvbaJMV21p5AFNTsfz4bP+y+TCMNPxyq6StedbIGyr6+XF5STNq/inuULOs4uf3mqDjQZaQxhF73liZwK14VwRbfHYrkTmDaivdDwfpPIBWnBpUxLChFxUIBwEaCJ+DbQaYlsGKKK4/qlabS3lfuVBRDXxODEFEQyk2+hqWI516Jih/rAdwZ16En7E6XqQ0N3zlMfTpCBM/2w0l6P33V0uXe3/wlccYidvikQ865fqV/Hyx5pGoICQFS59AbPuYCqEwFgV15KdEpQj/GFi9Sya7Bpwp8GihIAjduWTqGcd; 5:oXXqs/Ae3YTBuzYxPI5FNow52hPAsR13K+cTzbLYjrrEddow9rT2WujAS/cKtPBKLo26TFczxz21AyL0wF3xGAMMDFKuySlvHiAIMVe75JX4F/ZaDqSo5ly60He7k3mCIbkVoVNsptpdK0VG8jo07DjIVnbnoG81qE0j8VD8jWA=; 24:3rzKLtuDYk/CPW+DVf1Vjtp26SvxR2uBkODXfn4pqicYBgTc0QsZbdUplRIi/XOB1sDGv0UIFb51GdYqHXK/srJMydmyUBohzDKiTumrhCE=; 7:hup8DpsP46i59vAT4OhoyTFD7k2IrjSlCL6Ws45z9q+pVh8T2umwYNQ2C9YocFGTOwj0T4FM797SJsYmfw/F2qlDspxqm7VqfGFloO04k+Ae0aisyywgYWJ3AxaJp3iTgEo8/I+v/EI7rjokAd9RtPulFdrTDVqP13cuyFijpsKd/WpBOMk77kkL6nYQjTPYMiaCj23gy58edBEWwFnUGvqKL93tGh5XBhIPG7UMEWdeAce7Yi2N3tw5Miz/TBIRC4uMWZ9qophF8fYy6rGQdnySjfvOOs4WmNX505zWsxeJxm0ct9zdDG4Eld4NqDP3QuZV3qoG8ALudai+N+loJA==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM5PR0701MB2577;
x-microsoft-antispam-prvs: <AM5PR0701MB257795E9DB57A4BBD7C2341F8DC40@AM5PR0701MB2577.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(95692535739014)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001);  SRVR:AM5PR0701MB2577; BCL:0; PCL:0; RULEID:; SRVR:AM5PR0701MB2577; 
x-forefront-prvs: 008663486A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(199003)(54094003)(189002)(57704003)(76576001)(15975445007)(77096005)(19625215002)(122556002)(19609705001)(33656002)(66066001)(19580405001)(19580395003)(19300405004)(76176999)(87936001)(586003)(50986999)(54356999)(16236675004)(106356001)(3280700002)(106116001)(101416001)(105586002)(3660700001)(97736004)(189998001)(5001770100001)(790700001)(102836003)(3846002)(6116002)(230783001)(5002640100001)(2906002)(92566002)(2501003)(10400500002)(4326007)(11100500001)(7696004)(5660300001)(8676002)(81156014)(7736002)(9686002)(74316002)(2950100002)(68736007)(81166006)(2900100001)(8936002)(86362001)(7846002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM5PR0701MB2577; H:AM5PR0701MB2577.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM5PR0701MB25770AB3719E8C10A6C040058DC40AM5PR0701MB2577_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Oct 2016 17:44:06.5000 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2577
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Se0iTURjGOd9lfkqr49J88VIxIsK8NSIEzbJ/kkiNqJaCuaUfal4m+7xk VChk4C0SNS9dXDVdiWaJS2ED10rDVLS/FC9pzGmiqFneWFjOo9B/v+95nvOe9/k4HC15xbpz SWkZvDpNmSIVOTHVV9vO+M4FLcsDPtrYwAqdhQl8aRpnT1Nh5bZ3bJhWu05doKKdguP5lKQs Xu0fonBKNBXXU+nfYm4aHsyLctHaxULkyAE+Dn2aMVSInDgJbkbwdeS9yG5I8GcEo0NRdoPB JTSsruRtpyop6LM00ORjM/Wj/J6D/YgIH4HadvssR84Fx8DymwXKzjT2hanhTtrOe/ENsA4W iUgmGdqaRmnCMjDpW1k7M/gQtA/0bc0RYwU8GyxCZKUg6LVUb810xMEwUmre0hHeB6tfGrfv coPhyVqKdMOgNfbThF1hxrLBknwUlJX2be7MbeoH4bs+gkSCoaqocjseDr8fWSl7R8BLDlCx 8UlEjDD4+WKKJayCxgk9Reacg9m1SyRvRHDfWred8YTJafKzAOtEMNZtokkZHnRN+egh8q75 b2/CKng738/UbPV3hu7qSYboPqAxLIkIH4X657P0DveaLNT/ugY5NCBXgReupybIZH68OilO EFRpfml8RgvafD8fWm0B7WhmOtSMMIeku8QT+l9yCavMEnJSzQg4WuoiNgYuyyXieGXOLV6t ilVnpvCCGXlwjNRNfOL1uFyCE5QZfDLPp/PqHZfiHN1zUXUBivW3DKK8gt3+wppXoXSloGpR Z/BQRHTK2Gwj51XnvKBKWX/SFnqyxx0vdhSfFU5FevgMK9evDZ0/nMN0PP2T1RYxZy26k3nF 87JX2cJtfaImNe6vbN7QNRDevORe75JvXlVk27ot2sgeWXTJHrz/sc0vpKuFHz/A35VJGSFR ecybVgvKf3yZbTU7AwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/hF4e51Z-oWBUXqwGLGlrX85y7G0>
Cc: "snandaku@cisco.com" <snandaku@cisco.com>
Subject: Re: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 17:44:17 -0000

--_000_AM5PR0701MB25770AB3719E8C10A6C040058DC40AM5PR0701MB2577_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Christer,

You mean this might impact how the IDENTICAL and TRANSPORT categories shoul=
d be defined in -mux-attributes? That would be a pretty fundamental change.

4.3.  Category: IDENTICAL

   The attributes and their associated values (if any) in the IDENTICAL
   category MUST be repeated across all the media descriptions under
   multiplexing.

This text could in principle be changed say that the attribute of the "m=3D=
" line whose information is used to define the multiplexed group (for BUNDL=
E that is the "m=3D" line carrying the mid listed first on the "a=3DBUNDLE"=
 line). Would you allow "m=3D" lines in the multiplexed group to have other=
 values of an IDENTICAL category attribute, even if the value to use when m=
ultiplexed is given by the BUNDLE "m=3D" line? In what way would that be us=
eful or an improvement compared to (as now) require that values are actuall=
y identical when multiplexed?

4.5.  Category: TRANSPORT

   The attributes in the TRANSPORT category can be set normally for
   multiple items in a multiplexed group but the software MUST pick the
   one that's associated with the "m=3D" line whose information is used
   for setting up the underlying transport.

This already seems aligned with what you suggest below.

/Bo
(as individual)

From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: den 4 oktober 2016 12:44
To: mmusic@ietf.org
Cc: snandaku@cisco.com
Subject: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to manda=
te identical SDP attribute values?

Hi,

Based on Ekr's review of BUNDLE, it has been suggested that the text should=
 not focus so much on whether the bundled m- line addresses are "shared" or=
 "unique". The important thing is that the BUNDLE m- line specifies the add=
ress for the bundle group.

I wonder if the same thing applies also to SDP attributes (read: draft-ietf=
-mmusic-sdp-mux-attributes): E.g., what is important is whether an attribut=
e property is applied to all bundled m- lines or not (based on the mux cate=
gory) - not whether the SDP attribute values must be identical in different=
 m- lines.


Comments?


Regards,


Christer

--_000_AM5PR0701MB25770AB3719E8C10A6C040058DC40AM5PR0701MB2577_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Christer,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">You mean this might impact how the IDENTICAL and TR=
ANSPORT categories should be defined in -mux-attributes? That would be a pr=
etty fundamental change.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">4.3.&nbsp; Category: IDENTICAL<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&nbsp;&nbsp; The attributes and their associated va=
lues (if any) in the IDENTICAL<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&nbsp;&nbsp; category MUST be repeated across all t=
he media descriptions under<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&nbsp;&nbsp; multiplexing.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">This text could in principle be changed say that th=
e attribute of the &#8220;m=3D&#8221; line whose information is used to def=
ine the multiplexed group (for BUNDLE that is the &#8220;m=3D&#8221; line
 carrying the mid listed first on the &#8220;a=3DBUNDLE&#8221; line). Would=
 you allow &#8220;m=3D&#8221; lines in the multiplexed group to have other =
values of an IDENTICAL category attribute, even if the value to use when mu=
ltiplexed is given by the BUNDLE &#8220;m=3D&#8221; line? In what way would
 that be useful or an improvement compared to (as now) require that values =
are actually identical when multiplexed?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">4.5.&nbsp; Category: TRANSPORT<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&nbsp;&nbsp; The attributes in the TRANSPORT catego=
ry can be set normally for<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&nbsp;&nbsp; multiple items in a multiplexed group =
but the software MUST pick the<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&nbsp;&nbsp; one that's associated with the &quot;m=
=3D&quot; line whose information is used<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&nbsp;&nbsp; for setting up the underlying transpor=
t.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">This already seems aligned with what you suggest be=
low.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">/Bo<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">(as individual)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> mmusic [mailto:mmusic-bounces@=
ietf.org]
<b>On Behalf Of </b>Christer Holmberg<br>
<b>Sent:</b> den 4 oktober 2016 12:44<br>
<b>To:</b> mmusic@ietf.org<br>
<b>Cc:</b> snandaku@cisco.com<br>
<b>Subject:</b> [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need t=
o mandate identical SDP attribute values?<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Hi,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Based on Ekr&#8217;s review of BUNDLE, =
it has been suggested that the text should not focus so much on whether the=
 bundled m- line addresses are &#8220;shared&#8221; or &#8220;unique&#8221;=
.
 The important thing is that the BUNDLE m- line specifies the address for t=
he bundle group.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,sans-=
serif">I wonder if the same thing applies also to SDP attributes (read:&nbs=
p;draft-ietf-mmusic-sdp-mux-attributes): E.g., what is important is whether=
 an attribute property is applied to all bundled m-
 lines or not (based on the mux category) &#8211; not whether the SDP attri=
bute values must be identical in different m- lines.</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,sans-=
serif"><br>
<br>
</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,sans-=
serif">Comments?</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,sans-=
serif"><br>
<br>
</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,sans-=
serif">Regards,</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,sans-=
serif"><br>
<br>
</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,sans-=
serif">Christer</span><o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_AM5PR0701MB25770AB3719E8C10A6C040058DC40AM5PR0701MB2577_--


From nobody Wed Oct  5 11:15:12 2016
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 78AE01293FC for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 11:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 c6VtDmkIa-qq for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 11:15:07 -0700 (PDT)
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 798C512943D for <mmusic@ietf.org>; Wed,  5 Oct 2016 11:15:05 -0700 (PDT)
X-AuditID: c1b4fb25-5405a9800000793b-55-57f54327d077
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.183.54]) by  (Symantec Mail Security) with SMTP id 53.C4.31035.72345F75; Wed,  5 Oct 2016 20:15:03 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0319.002; Wed, 5 Oct 2016 20:14:25 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Bo Burman <bo.burman@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
Thread-Index: AQHSHiwofDubrkbtCEu3VfmkQRPgmqCaG2pAgAAN1UA=
Date: Wed, 5 Oct 2016 18:14:25 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD1BCF8@ESESSMB209.ericsson.se>
References: <D41963FD.1059F%christer.holmberg@ericsson.com> <AM5PR0701MB25770AB3719E8C10A6C040058DC40@AM5PR0701MB2577.eurprd07.prod.outlook.com>
In-Reply-To: <AM5PR0701MB25770AB3719E8C10A6C040058DC40@AM5PR0701MB2577.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BD1BCF8ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGIsWRmVeSWpSXmKPExsUyM2K7ma6689dwg82z9CymLn/MYrH4wH1W ByaPKb83snosWfKTKYApissmJTUnsyy1SN8ugSujs/EWe8GbuYwV99/+ZmlgnN/L2MXIySEh YCLx7fNLti5GLg4hgfWMEpuWLoFyFjFKnDxzn7WLkYODTcBCovufNogpIuAtca3VE6SXWUBX 4tmto8wgtrBAlsTT691sILaIQLbE9rV3mCFsK4lFd0+zg9gsAioSLzrWgNXwCvhKnF+xjx1i 1SRGiTfH57KAJDgFEiU+flgD1swoICbx/dQaJohl4hK3nsxngjhaQGLJnvPMELaoxMvH/1gh bCWJxiVPWCHq8yUmv7jKArFMUOLkzCcsExhFZiEZNQtJ2SwkZRBxHYkFuz+xQdjaEssWvmaG sc8ceMyELL6AkX0Vo2hxanFSbrqRsV5qUWZycXF+nl5easkmRmBsHdzyW3UH4+U3jocYBTgY lXh4F9h/DRdiTSwrrsw9xCjBwawkwivqBBTiTUmsrEotyo8vKs1JLT7EKM3BoiTOa7byfriQ QHpiSWp2ampBahFMlomDU6qB0U+QVUFoyQtntflvraZUX7MyDTN9x735yeXpPyzKeYX/V04M ktmolzJ3RfhtUYsZhlNEjgg22vSLz98/67Ac010OjoA9e4K4/cRjffbtD+bgTfsS2uxaw/tR +uhdvhPO8y9MUGt6UfDX7lCijrHo2w7X+3VzG+e4uASoN4d7SCtpPmsq9NJWYinOSDTUYi4q TgQAWHbJBKkCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Nlud_hUyzi08gfJwDJPZuw6HUuE>
Cc: "snandaku@cisco.com" <snandaku@cisco.com>
Subject: Re: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 18:15:10 -0000

--_000_7594FB04B1934943A5C02806D1A2204B4BD1BCF8ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

>You mean this might impact how the IDENTICAL and TRANSPORT categories shou=
ld be >defined in -mux-attributes? That would be a pretty fundamental chang=
e.

It's not related to the definition of IDENTICAL and TRANSPORT as such. It i=
s more related to mandating the same attribute values in all m- lines, as a=
t the end of the day only the attribute values in the BUNDLE m- line matter=
s.
>4.3.  Category: IDENTICAL
>
>   The attributes and their associated values (if any) in the IDENTICAL
>   category MUST be repeated across all the media descriptions under
>   multiplexing.
>
>This text could in principle be changed say that the attribute of the "m=
=3D" line whose >information is used to define the multiplexed group (for B=
UNDLE that is the "m=3D" line >carrying the mid listed first on the "a=3DBU=
NDLE" line). Would you allow "m=3D" lines in the >multiplexed group to have=
 other values of an IDENTICAL category attribute, even if the >value to use=
 when multiplexed is given by the BUNDLE "m=3D" line? In what way would >th=
at be useful or an improvement compared to (as now) require that values are=
 actually >identical when multiplexed?

In fact, based on a rather recent change, BUNDLE actually says (see below) =
that IDENTICAL and TRANSPORT attribute are ONLY inserted in the BUNDLE m- l=
ine to begin with. So, we are already misaligned, as we don't repeat them a=
cross all m- lines...

"When an offerer associates SDP attributes with a bundled "m=3D" line
              associated with a shared address, IDENTICAL and TRANSPORT mux
              category SDP attributes [I-D.ietf-mmusic-sdp-mux-attributes] =
are
              associated with the "m=3D" line only if the "m=3D" line is al=
so
              associated with the offerer BUNDLE-tag.  Otherwise the offere=
r MUST
              NOT associate such SDP attributes with the "m=3D" line."

>4.5.  Category: TRANSPORT
>
>   The attributes in the TRANSPORT category can be set normally for
>   multiple items in a multiplexed group but the software MUST pick the
>   one that's associated with the "m=3D" line whose information is used
>   for setting up the underlying transport.
>
> This already seems aligned with what you suggest below.

Yes.

Regards,

Christer


From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: den 4 oktober 2016 12:44
To: mmusic@ietf.org<mailto:mmusic@ietf.org>
Cc: snandaku@cisco.com<mailto:snandaku@cisco.com>
Subject: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to manda=
te identical SDP attribute values?

Hi,

Based on Ekr's review of BUNDLE, it has been suggested that the text should=
 not focus so much on whether the bundled m- line addresses are "shared" or=
 "unique". The important thing is that the BUNDLE m- line specifies the add=
ress for the bundle group.

I wonder if the same thing applies also to SDP attributes (read: draft-ietf=
-mmusic-sdp-mux-attributes): E.g., what is important is whether an attribut=
e property is applied to all bundled m- lines or not (based on the mux cate=
gory) - not whether the SDP attribute values must be identical in different=
 m- lines.

Comments?

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B4BD1BCF8ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US">Hi,<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">You mean this might impact how the IDENTICAL and TRANSPORT categories
 should be <span style=3D"color:#1F497D">&gt;</span>defined in -mux-attribu=
tes? That would be a pretty fundamental change.<span style=3D"color:#1F497D=
"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">It&#8217;s not related=
 to the definition of IDENTICAL and TRANSPORT as such. It is more related t=
o mandating the same attribute values in all m- lines,
 as at the end of the day only the attribute values in the BUNDLE m- line m=
atters.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">4.3.&nbsp; Category: IDENTICAL<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">&nbsp;&nbsp; The attributes and their associated values (if any) in t=
he
 IDENTICAL<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">&nbsp;&nbsp; category MUST be repeated across all the media descripti=
ons
 under<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">&nbsp;&nbsp; multiplexing.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">This text could in principle be changed say that the attribute
 of the &#8220;m=3D&#8221; line whose <span style=3D"color:#1F497D">&gt;i</=
span>nformation is used to define the multiplexed group (for BUNDLE that is=
 the &#8220;m=3D&#8221; line
<span style=3D"color:#1F497D">&gt;</span>carrying the mid listed first on t=
he &#8220;a=3DBUNDLE&#8221; line). Would you allow &#8220;m=3D&#8221; lines=
 in the
<span style=3D"color:#1F497D">&gt;</span>multiplexed group to have other va=
lues of an IDENTICAL category attribute, even if the
<span style=3D"color:#1F497D">&gt;</span>value to use when multiplexed is g=
iven by the BUNDLE &#8220;m=3D&#8221; line? In what way would
<span style=3D"color:#1F497D">&gt;</span>that be useful or an improvement c=
ompared to (as now) require that values are actually
<span style=3D"color:#1F497D">&gt;i</span>dentical when multiplexed?<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">In fact, based on a ra=
ther recent change, BUNDLE actually says (see below) that IDENTICAL and TRA=
NSPORT attribute are ONLY inserted in the BUNDLE
 m- line to begin with. So, we are already misaligned, as we don&#8217;t re=
peat them across all m- lines&#8230;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1=
F497D">&#8220;When an offerer associates SDP attributes with a bundled &quo=
t;m=3D&quot; line<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&nbsp;&nbsp; &nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; associated with a share=
d address, IDENTICAL and TRANSPORT mux<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&nbsp;&nbsp; &nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; category SDP attributes=
 [I-D.ietf-mmusic-sdp-mux-attributes] are<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&nbsp;&nbsp; &nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; associated with the &qu=
ot;m=3D&quot; line
<b>only if the &quot;m=3D&quot; line is also<o:p></o:p></b></span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&nbsp;&nbsp; &nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; associated with the =
offerer BUNDLE-tag.&nbsp; Otherwise the offerer MUST<o:p></o:p></span></b><=
/p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&nbsp;&nbsp; &nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NOT associate such S=
DP attributes with the &quot;m=3D&quot; line</span></b><span lang=3D"EN-US"=
 style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color=
:#1F497D">.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">4.5.&nbsp; Category: TRANSPORT<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">&nbsp;&nbsp; The attributes in the TRANSPORT category can be set norm=
ally
 for<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">&nbsp;&nbsp; multiple items in a multiplexed group but the software M=
UST
 pick the<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">&nbsp;&nbsp; one that's associated with the &quot;m=3D&quot; line who=
se information
 is used<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">&nbsp;&nbsp; for setting up the underlying transport.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">&gt;
</span><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif">This already seems aligned with what you suggest bel=
ow.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">Yes.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D">Christer<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span lang=3D"EN-=
US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"> =
mmusic [<a href=3D"mailto:mmusic-bounces@ietf.org">mailto:mmusic-bounces@ie=
tf.org</a>]
<b>On Behalf Of </b>Christer Holmberg<br>
<b>Sent:</b> den 4 oktober 2016 12:44<br>
<b>To:</b> <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:snandaku@cisco.com">snandaku@cisco.com</a><br>
<b>Subject:</b> [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need t=
o mandate identical SDP attribute values?<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black">Hi,<o:p></o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black"><o:p>&nbsp;</o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black">Based on Ekr&#8217;s rev=
iew of BUNDLE, it has been suggested that the text should not focus so much=
 on whether the bundled m- line addresses are &#8220;shared&#8221;
 or &#8220;unique&#8221;. The important thing is that the BUNDLE m- line sp=
ecifies the address for the bundle group.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black"><o:p>&nbsp;</o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">I wonder if the same thing applies also to SDP attrib=
utes (read:&nbsp;draft-ietf-mmusic-sdp-mux-attributes): E.g., what is impor=
tant is whether an attribute property is applied to all
 bundled m- lines or not (based on the mux category) &#8211; not whether th=
e SDP attribute values must be identical in different m- lines.</span><span=
 lang=3D"EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Comments?</span><span lang=3D"EN-US"><o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Regards,</span><span lang=3D"EN-US"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Christer</span><span lang=3D"EN-US"><o:p></o:p></span=
></p>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B4BD1BCF8ESESSMB209erics_--


From nobody Wed Oct  5 11:45:16 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 806021293F5 for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 11:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 ZCJabk-W9Eb0 for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 11:45:12 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (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 086F412940F for <mmusic@ietf.org>; Wed,  5 Oct 2016 11:45:12 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id g192so169056848ywh.1 for <mmusic@ietf.org>; Wed, 05 Oct 2016 11:45:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=sPtYQTdrKKEnFsU8S9gJ5xm4xKJh4YEQaS6vObI1ikw=; b=OHoVByO9Q5iMm4xBhWEHK78G8EkIgLUTiYEJ+mJBmMQdzHPIIxlHMz+ZlXgBJHYe2r lcKXNV/gw7EHcZVOuewVMJJRLxi21anU+/6+QkgBQA0l1aRzE+2km65ZHDyXdYQeTxBm +Q1IzC1mGzd/ydy2D3lpMuUlkaP3PMsUXSDcC2duQxwEB6OOpJfRfzGDx7FcoVUtnG3G pR9HoOiVJCkHhL8/WOpaxnQnuEYw9/9Dd0Q7l4TIIWd7MN2Zavjsz6auwF6VeoAJJNev zARXoV56ABClwrTYK1DkqCQLUY3FGSc5VAPJAa09hnQ5tcIb/eR/r6trcAgQplo27K9V vy/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=sPtYQTdrKKEnFsU8S9gJ5xm4xKJh4YEQaS6vObI1ikw=; b=OLgEAou3PvXSVBr2NA+wiSZzIuJz6Q4IoIjRJvr/3o3DmaVTecfhSeLlNS1a+qYuBL pxJ3r2LeCrlvw/CW7qaHdN/MAmaARcIUl4WwTvEpJGv4zCU9pDf6U5wN7VPXUhiC35UV ys5s6pXbkNyxKU/IIhAlm7nwfhor80EDk2xPGGQgMX1YlpoocfTkDaBVSUgw7UV8G9nu CaA3KZwMxa9FZW9pR/hDzZLc1r5LRJ+Flk48qM40AytSIWr8L1YkCbt0F01onb5k7zml wXlAS/vNosgo8hl2wAXQsgeZbio3oLvEv/20XilqMdpFaAnCG+CnR+8LwBFPyYPr0uyL pt4g==
X-Gm-Message-State: AA6/9Rlr02cHzyUR5tiH3S5SK6dVUrNWp+cX4x6D54Is92gD6im3MN904pV9CUJ1Dqrz+qWR5ibC4ISr4epjkQ==
X-Received: by 10.129.78.15 with SMTP id c15mr8268085ywb.107.1475693111274; Wed, 05 Oct 2016 11:45:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.158.73 with HTTP; Wed, 5 Oct 2016 11:45:10 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD1BCF8@ESESSMB209.ericsson.se>
References: <D41963FD.1059F%christer.holmberg@ericsson.com> <AM5PR0701MB25770AB3719E8C10A6C040058DC40@AM5PR0701MB2577.eurprd07.prod.outlook.com> <7594FB04B1934943A5C02806D1A2204B4BD1BCF8@ESESSMB209.ericsson.se>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Wed, 5 Oct 2016 11:45:10 -0700
Message-ID: <CAMRcRGQp5u_dP5L++yHu4NtfPWu+wc=v=0Xec+4WeAUw=jZWYQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a114dae52b24718053e2293e0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/HQ6TatJ65_t8F4ir3kqWiAxnc3k>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "snandaku@cisco.com" <snandaku@cisco.com>
Subject: Re: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 18:45:14 -0000

--001a114dae52b24718053e2293e0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Oct 5, 2016 at 11:14 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
>
>
> >You mean this might impact how the IDENTICAL and TRANSPORT categories
> should be >defined in -mux-attributes? That would be a pretty fundamental
> change.
>
>
>
> It=E2=80=99s not related to the definition of IDENTICAL and TRANSPORT as =
such. It
> is more related to mandating the same attribute values in all m- lines, a=
s
> at the end of the day only the attribute values in the BUNDLE m- line
> matters.
>
> >4.3.  Category: IDENTICAL
>
> >
>
> >   The attributes and their associated values (if any) in the IDENTICAL
>
> >   category MUST be repeated across all the media descriptions under
>
> >   multiplexing.
>
> >
>
> >This text could in principle be changed say that the attribute of the
> =E2=80=9Cm=3D=E2=80=9D line whose >information is used to define the mult=
iplexed group (for
> BUNDLE that is the =E2=80=9Cm=3D=E2=80=9D line >carrying the mid listed f=
irst on the
> =E2=80=9Ca=3DBUNDLE=E2=80=9D line). Would you allow =E2=80=9Cm=3D=E2=80=
=9D lines in the >multiplexed group to
> have other values of an IDENTICAL category attribute, even if the >value
> to use when multiplexed is given by the BUNDLE =E2=80=9Cm=3D=E2=80=9D lin=
e? In what way would
> >that be useful or an improvement compared to (as now) require that
> values are actually >identical when multiplexed?
>
>
>
> In fact, based on a rather recent change, BUNDLE actually says (see below=
)
> that IDENTICAL and TRANSPORT attribute are ONLY inserted in the BUNDLE m-
> line to begin with. So, we are already misaligned, as we don=E2=80=99t re=
peat them
> across all m- lines=E2=80=A6
>
>
>
> =E2=80=9CWhen an offerer associates SDP attributes with a bundled "m=3D" =
line
>
>               associated with a shared address, IDENTICAL and TRANSPORT m=
ux
>
>               category SDP attributes [I-D.ietf-mmusic-sdp-mux-attributes=
]
> are
>
>               associated with the "m=3D" line *only if the "m=3D" line is
> also*
>
> *              associated with the offerer BUNDLE-tag.  Otherwise the
> offerer MUST*
>
> *              NOT associate such SDP attributes with the "m=3D" line*.=
=E2=80=9D
>
>
>

[suhas] - So what happens if BUNDLE-tag m=3Dline in the offer gets rejected
and say rtcp-mux was just included only on  that m=3Dline as per above text
form BUNDLE text.  If i understand right, there is no rtcp mux for any of
the m=3Dlines which is not the Offerer might want




> >4.5.  Category: TRANSPORT
>
> >
>
> >   The attributes in the TRANSPORT category can be set normally for
>
> >   multiple items in a multiplexed group but the software MUST pick the
>
> >   one that's associated with the "m=3D" line whose information is used
>
> >   for setting up the underlying transport.
>
> >
>
> > This already seems aligned with what you suggest below.
>
>
>
> Yes.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>
> *From:* mmusic [mailto:mmusic-bounces@ietf.org <mmusic-bounces@ietf.org>]=
 *On
> Behalf Of *Christer Holmberg
> *Sent:* den 4 oktober 2016 12:44
> *To:* mmusic@ietf.org
> *Cc:* snandaku@cisco.com
> *Subject:* [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to
> mandate identical SDP attribute values?
>
>
>
> Hi,
>
>
>
> Based on Ekr=E2=80=99s review of BUNDLE, it has been suggested that the t=
ext
> should not focus so much on whether the bundled m- line addresses are
> =E2=80=9Cshared=E2=80=9D or =E2=80=9Cunique=E2=80=9D. The important thing=
 is that the BUNDLE m- line
> specifies the address for the bundle group.
>
>
>
> I wonder if the same thing applies also to SDP attributes
> (read: draft-ietf-mmusic-sdp-mux-attributes): E.g., what is important is
> whether an attribute property is applied to all bundled m- lines or not
> (based on the mux category) =E2=80=93 not whether the SDP attribute value=
s must be
> identical in different m- lines.
>
>
>
> Comments?
>
>
>
> Regards,
>
>
>
> Christer
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

--001a114dae52b24718053e2293e0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Wed, Oct 5, 2016 at 11:14 AM, Christer Holmberg <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christer.=
holmberg@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"m_6762535590423653551WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Hi,<u></u><u></u></span></p><span cla=
ss=3D"">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">You mean this might impact how the IDENTICAL and TRANSPORT categories
 should be <span style=3D"color:#1f497d">&gt;</span>defined in -mux-attribu=
tes? That would be a pretty fundamental change.<span style=3D"color:#1f497d=
"><u></u><u></u></span></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></=
span></p>
</span><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0p=
t;font-family:&quot;Calibri&quot;,sans-serif;color:#1f497d">It=E2=80=99s no=
t related to the definition of IDENTICAL and TRANSPORT as such. It is more =
related to mandating the same attribute values in all m- lines,
 as at the end of the day only the attribute values in the BUNDLE m- line m=
atters.<u></u><u></u></span></p><span class=3D"">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d"><u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">4.3.=C2=A0 Category: IDENTICAL<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0 The attributes and their associated values (if any) in t=
he
 IDENTICAL<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0 category MUST be repeated across all the media descripti=
ons
 under<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0 multiplexing.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">This text could in principle be changed say that the attribute
 of the =E2=80=9Cm=3D=E2=80=9D line whose <span style=3D"color:#1f497d">&gt=
;i</span>nformation is used to define the multiplexed group (for BUNDLE tha=
t is the =E2=80=9Cm=3D=E2=80=9D line
<span style=3D"color:#1f497d">&gt;</span>carrying the mid listed first on t=
he =E2=80=9Ca=3DBUNDLE=E2=80=9D line). Would you allow =E2=80=9Cm=3D=E2=80=
=9D lines in the
<span style=3D"color:#1f497d">&gt;</span>multiplexed group to have other va=
lues of an IDENTICAL category attribute, even if the
<span style=3D"color:#1f497d">&gt;</span>value to use when multiplexed is g=
iven by the BUNDLE =E2=80=9Cm=3D=E2=80=9D line? In what way would
<span style=3D"color:#1f497d">&gt;</span>that be useful or an improvement c=
ompared to (as now) require that values are actually
<span style=3D"color:#1f497d">&gt;i</span>dentical when multiplexed?<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></=
span></p>
</span><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0p=
t;font-family:&quot;Calibri&quot;,sans-serif;color:#1f497d">In fact, based =
on a rather recent change, BUNDLE actually says (see below) that IDENTICAL =
and TRANSPORT attribute are ONLY inserted in the BUNDLE
 m- line to begin with. So, we are already misaligned, as we don=E2=80=99t =
repeat them across all m- lines=E2=80=A6<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></=
span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1=
f497d">=E2=80=9CWhen an offerer associates SDP attributes with a bundled &q=
uot;m=3D&quot; line<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 associated with a share=
d address, IDENTICAL and TRANSPORT mux<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 category SDP attributes=
 [I-D.ietf-mmusic-sdp-mux-<wbr>attributes] are<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 associated with the &qu=
ot;m=3D&quot; line
<b>only if the &quot;m=3D&quot; line is also<u></u><u></u></b></span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 associated with the =
offerer BUNDLE-tag.=C2=A0 Otherwise the offerer MUST<u></u><u></u></span></=
b></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NOT associate such S=
DP attributes with the &quot;m=3D&quot; line</span></b><span lang=3D"EN-US"=
 style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color=
:#1f497d">.=E2=80=9D<u></u><u></u></span></p><span class=3D"">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0</span></=
p></span></div></div></blockquote><div><br></div><div>[suhas] - So what hap=
pens if BUNDLE-tag m=3Dline in the offer gets rejected and say rtcp-mux was=
 just included only on =C2=A0that m=3Dline as per above text form BUNDLE te=
xt.=C2=A0 If i understand right, there is no rtcp mux for any of the m=3Dli=
nes which is not the Offerer might want=C2=A0</div><div><br></div><div>=C2=
=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-GB=
" link=3D"blue" vlink=3D"purple"><div class=3D"m_6762535590423653551WordSec=
tion1"><span class=3D""><p class=3D"MsoNormal"><span lang=3D"EN-US" style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1f49=
7d"><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">4.5.=C2=A0 Category: TRANSPORT<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0 The attributes in the TRANSPORT category can be set norm=
ally
 for<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0 multiple items in a multiplexed group but the software M=
UST
 pick the<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0 one that&#39;s associated with the &quot;m=3D&quot; line=
 whose information
 is used<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0 for setting up the underlying transport.<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;
</span><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif">This already seems aligned with what you suggest bel=
ow.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></=
span></p>
</span><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0p=
t;font-family:&quot;Calibri&quot;,sans-serif;color:#1f497d">Yes.<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">Regards,<span class=3D=
"HOEnZb"><font color=3D"#888888"><u></u><u></u></font></span></span></p><sp=
an class=3D"HOEnZb"><font color=3D"#888888">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">Christer<u></u><u></u>=
</span></p></font></span><span class=3D"">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span lang=3D"EN-=
US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"> =
mmusic [<a href=3D"mailto:mmusic-bounces@ietf.org" target=3D"_blank">mailto=
:mmusic-bounces@ietf.<wbr>org</a>]
<b>On Behalf Of </b>Christer Holmberg<br>
<b>Sent:</b> den 4 oktober 2016 12:44<br>
<b>To:</b> <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf=
.org</a><br>
<b>Cc:</b> <a href=3D"mailto:snandaku@cisco.com" target=3D"_blank">snandaku=
@cisco.com</a><br>
<b>Subject:</b> [MMUSIC] draft-ietf-mmusic-sdp-mux-<wbr>attributes: Do we n=
eed to mandate identical SDP attribute values?<u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black">Hi,<u></u><u></u></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black"><u></u>=C2=A0<u></u></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black">Based on Ekr=E2=80=99s r=
eview of BUNDLE, it has been suggested that the text should not focus so mu=
ch on whether the bundled m- line addresses are =E2=80=9Cshared=E2=80=9D
 or =E2=80=9Cunique=E2=80=9D. The important thing is that the BUNDLE m- lin=
e specifies the address for the bundle group.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black"><u></u>=C2=A0<u></u></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">I wonder if the same thing applies also to SDP attrib=
utes (read:=C2=A0draft-ietf-mmusic-sdp-<wbr>mux-attributes): E.g., what is =
important is whether an attribute property is applied to all
 bundled m- lines or not (based on the mux category) =E2=80=93 not whether =
the SDP attribute values must be identical in different m- lines.</span><sp=
an lang=3D"EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Comments?</span><span lang=3D"EN-US"><u></u><u></u></=
span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Regards,</span><span lang=3D"EN-US"><u></u><u></u></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Christer</span><span lang=3D"EN-US"><u></u><u></u></s=
pan></p>
</div>
</div>
</span></div>
</div>

<br>______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
<br></blockquote></div><br></div></div>

--001a114dae52b24718053e2293e0--


From nobody Wed Oct  5 11:58:53 2016
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 583911297B6 for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 11:58:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 E6ynjWSn1rSG for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 11:58:50 -0700 (PDT)
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 E5356129405 for <mmusic@ietf.org>; Wed,  5 Oct 2016 11:58:48 -0700 (PDT)
X-AuditID: c1b4fb3a-ab7ff7000000099a-27-57f54d6617c6
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by  (Symantec Mail Security) with SMTP id 71.8C.02458.66D45F75; Wed,  5 Oct 2016 20:58:47 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0319.002; Wed, 5 Oct 2016 20:58:45 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Thread-Topic: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
Thread-Index: AQHSHiwofDubrkbtCEu3VfmkQRPgmqCaG2pAgAAN1UD//+oUAIAAIpcg
Date: Wed, 5 Oct 2016 18:58:44 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD1C066@ESESSMB209.ericsson.se>
References: <D41963FD.1059F%christer.holmberg@ericsson.com> <AM5PR0701MB25770AB3719E8C10A6C040058DC40@AM5PR0701MB2577.eurprd07.prod.outlook.com> <7594FB04B1934943A5C02806D1A2204B4BD1BCF8@ESESSMB209.ericsson.se> <CAMRcRGQp5u_dP5L++yHu4NtfPWu+wc=v=0Xec+4WeAUw=jZWYQ@mail.gmail.com>
In-Reply-To: <CAMRcRGQp5u_dP5L++yHu4NtfPWu+wc=v=0Xec+4WeAUw=jZWYQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BD1C066ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprDIsWRmVeSWpSXmKPExsUyM2J7uG6679dwg0UTRCymLn/MYrH4wH1W i51zO5gdmD2m/N7I6rFz1l12jyVLfjIFMEdx2aSk5mSWpRbp2yVwZVx+cYa94MpMporm4z2M DYxLJjF1MXJySAiYSLxdOJ21i5GLQ0hgPaPEmUvb2UESQgKLGCUWXczpYuTgYBOwkOj+pw0S FhHQkli9eC4TSJhZoEKi7Y4OSFhYoFjixdIbzBAlJRKnl29lBSkREXCT+PIKrJNFQEXi8JWp YFt5BXwl7v5byQKxdS6TxNq719hB6jkFAiWWdPCA1DAKiEl8P7UGrJ5ZQFzi1pP5UBcLSCzZ c54ZwhaVePn4HyuErSTRuOQJK0R9vkTLhMdsELsEJU7OfMIygVFkFpJRs5CUzUJSNgvsMU2J 9bv0IUoUJaZ0P2SHsDUkWufMZUcWX8DIvopRtDi1uDg33chIL7UoM7m4OD9PLy+1ZBMjMM4O bvlttYPx4HPHQ4wCHIxKPLwL7L+GC7EmlhVX5h5ilOBgVhLhveUJFOJNSaysSi3Kjy8qzUkt PsQozcGiJM5rtvJ+uJBAemJJanZqakFqEUyWiYNTqoGRxSRhdf+5RU4HplrenPPvdfvcWMGO /s7f751r70vFnl/GnizrcPCmRYJD/knO/gNV3r5evm+XJ51Lebsk1d+0bhHP+yl5O29wx8W0 2dpqZu25bSEZ6FKs+lx7pd+JH4I7YnjvSi69UFmY3J78+6354uBfAmZHZovv0o20dYx3Zltq n1m3bYkSS3FGoqEWc1FxIgAOEaNdrwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Aa7VNUMrNpPu8bOoOxu9cCdMN0E>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "snandaku@cisco.com" <snandaku@cisco.com>
Subject: Re: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 18:58:52 -0000

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

SGksDQo+WW91IG1lYW4gdGhpcyBtaWdodCBpbXBhY3QgaG93IHRoZSBJREVOVElDQUwgYW5kIFRS
QU5TUE9SVCBjYXRlZ29yaWVzIHNob3VsZCBiZSA+ZGVmaW5lZCBpbiAtbXV4LWF0dHJpYnV0ZXM/
IFRoYXQgd291bGQgYmUgYSBwcmV0dHkgZnVuZGFtZW50YWwgY2hhbmdlLg0KDQpJdOKAmXMgbm90
IHJlbGF0ZWQgdG8gdGhlIGRlZmluaXRpb24gb2YgSURFTlRJQ0FMIGFuZCBUUkFOU1BPUlQgYXMg
c3VjaC4gSXQgaXMgbW9yZSByZWxhdGVkIHRvIG1hbmRhdGluZyB0aGUgc2FtZSBhdHRyaWJ1dGUg
dmFsdWVzIGluIGFsbCBtLSBsaW5lcywgYXMgYXQgdGhlIGVuZCBvZiB0aGUgZGF5IG9ubHkgdGhl
IGF0dHJpYnV0ZSB2YWx1ZXMgaW4gdGhlIEJVTkRMRSBtLSBsaW5lIG1hdHRlcnMuDQo+NC4zLiAg
Q2F0ZWdvcnk6IElERU5USUNBTA0KPg0KPiAgIFRoZSBhdHRyaWJ1dGVzIGFuZCB0aGVpciBhc3Nv
Y2lhdGVkIHZhbHVlcyAoaWYgYW55KSBpbiB0aGUgSURFTlRJQ0FMDQo+ICAgY2F0ZWdvcnkgTVVT
VCBiZSByZXBlYXRlZCBhY3Jvc3MgYWxsIHRoZSBtZWRpYSBkZXNjcmlwdGlvbnMgdW5kZXINCj4g
ICBtdWx0aXBsZXhpbmcuDQo+DQo+VGhpcyB0ZXh0IGNvdWxkIGluIHByaW5jaXBsZSBiZSBjaGFu
Z2VkIHNheSB0aGF0IHRoZSBhdHRyaWJ1dGUgb2YgdGhlIOKAnG094oCdIGxpbmUgd2hvc2UgPmlu
Zm9ybWF0aW9uIGlzIHVzZWQgdG8gZGVmaW5lIHRoZSBtdWx0aXBsZXhlZCBncm91cCAoZm9yIEJV
TkRMRSB0aGF0IGlzIHRoZSDigJxtPeKAnSBsaW5lID5jYXJyeWluZyB0aGUgbWlkIGxpc3RlZCBm
aXJzdCBvbiB0aGUg4oCcYT1CVU5ETEXigJ0gbGluZSkuIFdvdWxkIHlvdSBhbGxvdyDigJxtPeKA
nSBsaW5lcyBpbiB0aGUgPm11bHRpcGxleGVkIGdyb3VwIHRvIGhhdmUgb3RoZXIgdmFsdWVzIG9m
IGFuIElERU5USUNBTCBjYXRlZ29yeSBhdHRyaWJ1dGUsIGV2ZW4gaWYgdGhlID52YWx1ZSB0byB1
c2Ugd2hlbiBtdWx0aXBsZXhlZCBpcyBnaXZlbiBieSB0aGUgQlVORExFIOKAnG094oCdIGxpbmU/
IEluIHdoYXQgd2F5IHdvdWxkID50aGF0IGJlIHVzZWZ1bCBvciBhbiBpbXByb3ZlbWVudCBjb21w
YXJlZCB0byAoYXMgbm93KSByZXF1aXJlIHRoYXQgdmFsdWVzIGFyZSBhY3R1YWxseSA+aWRlbnRp
Y2FsIHdoZW4gbXVsdGlwbGV4ZWQ/DQoNCkluIGZhY3QsIGJhc2VkIG9uIGEgcmF0aGVyIHJlY2Vu
dCBjaGFuZ2UsIEJVTkRMRSBhY3R1YWxseSBzYXlzIChzZWUgYmVsb3cpIHRoYXQgSURFTlRJQ0FM
IGFuZCBUUkFOU1BPUlQgYXR0cmlidXRlIGFyZSBPTkxZIGluc2VydGVkIGluIHRoZSBCVU5ETEUg
bS0gbGluZSB0byBiZWdpbiB3aXRoLiBTbywgd2UgYXJlIGFscmVhZHkgbWlzYWxpZ25lZCwgYXMg
d2UgZG9u4oCZdCByZXBlYXQgdGhlbSBhY3Jvc3MgYWxsIG0tIGxpbmVz4oCmDQoNCuKAnFdoZW4g
YW4gb2ZmZXJlciBhc3NvY2lhdGVzIFNEUCBhdHRyaWJ1dGVzIHdpdGggYSBidW5kbGVkICJtPSIg
bGluZQ0KICAgICAgICAgICAgICBhc3NvY2lhdGVkIHdpdGggYSBzaGFyZWQgYWRkcmVzcywgSURF
TlRJQ0FMIGFuZCBUUkFOU1BPUlQgbXV4DQogICAgICAgICAgICAgIGNhdGVnb3J5IFNEUCBhdHRy
aWJ1dGVzIFtJLUQuaWV0Zi1tbXVzaWMtc2RwLW11eC1hdHRyaWJ1dGVzXSBhcmUNCiAgICAgICAg
ICAgICAgYXNzb2NpYXRlZCB3aXRoIHRoZSAibT0iIGxpbmUgb25seSBpZiB0aGUgIm09IiBsaW5l
IGlzIGFsc28NCiAgICAgICAgICAgICAgYXNzb2NpYXRlZCB3aXRoIHRoZSBvZmZlcmVyIEJVTkRM
RS10YWcuICBPdGhlcndpc2UgdGhlIG9mZmVyZXIgTVVTVA0KICAgICAgICAgICAgICBOT1QgYXNz
b2NpYXRlIHN1Y2ggU0RQIGF0dHJpYnV0ZXMgd2l0aCB0aGUgIm09IiBsaW5lLuKAnQ0KDQoNCltz
dWhhc10gLSBTbyB3aGF0IGhhcHBlbnMgaWYgQlVORExFLXRhZyBtPWxpbmUgaW4gdGhlIG9mZmVy
IGdldHMgcmVqZWN0ZWQgYW5kIHNheSBydGNwLW11eCB3YXMganVzdCBpbmNsdWRlZCBvbmx5IG9u
ICB0aGF0IG09bGluZSBhcyBwZXIgYWJvdmUgdGV4dCBmb3JtIEJVTkRMRSB0ZXh0LiAgSWYgaSB1
bmRlcnN0YW5kIHJpZ2h0LCB0aGVyZSBpcyBubyBydGNwIG11eCBmb3IgYW55IG9mIHRoZSBtPWxp
bmVzIHdoaWNoIGlzIG5vdCB0aGUgT2ZmZXJlciBtaWdodCB3YW50DQoNCk5vdGUgdGhhdCB0aGUg
dGV4dCBvbmx5IGFwcGxpZXMgdG8gdGhlIGNhc2Ugd2hlbiB0aGUgbS0gbGluZSBjb250YWlucyBh
IHNoYXJlZCBhZGRyZXNzLCBpLmUuLCBpdCBoYXMgYWxyZWFkeSBiZWVuIGFjY2VwdGVkIGludG8g
dGhlIEJVTkRMRSBncm91cC4NCg0KV2hlbiB5b3Ugc2VuZCB0aGUgaW5pdGlhbCBvZmZlciAoYmVm
b3JlIHRoZSBCVU5ETEUgZ3JvdXAgaGFzIGJlZW4gY3JlYXRlZCksIG9yIHdoZW4geW91IHdhbnQg
dG8gYWRkIGEgbmV3IG0tIGxpbmUgdG8gYSBCVU5ETEUgZ3JvdXAsIHlvdSBoYXZlIHRvIGluY2x1
ZGUgYWxsIGF0dHJpYnV0ZXMgaW4gYWxsIG0tIGxpbmVzLCB1c2luZyBub3JtYWwgMzI2NCBwcm9j
ZWR1cmVzLiBCdXQsIGluIHRoYXQgY2FzZSBJIGRvbuKAmXQgdGhpbmsgZHJhZnQtbXV4LWF0dHJp
YnV0ZXMgYXBwbGllcyB0byBiZWdpbiB3aXRoLCBpLmUuLCB5b3UgY2FuIGluY2x1ZGUgd2hhdGV2
ZXIgYXR0cmlidXRlIHZhbHVlcywgYW5kIHRoZXkgd2lsbCBiZSB1c2VkIGlmIHRoZSBtLSBsaW5l
IGlzIG5vdCBhY2NlcHRlZCBpbnRvIHRoZSBCVU5ETEUgZ3JvdXAuIGRyYWZ0LW11eC1hdHRyaWJ1
dGVzIG9ubHkgYXBwbGllcyBvbmNlIHRoZSBCVU5ETEUgZ3JvdXAgaGFzIGJlZW4gY3JlYXRlZC4g
QXQgbGVhc3QgdGhhdCBpcyBteSB1bmRlcnN0YW5kaW5nLg0KDQpNeSBwb2ludCBpcyB0aGF0IHdo
YXQgaXMgaW1wb3J0YW50IGlzIHRoYXQgZHJhZnQtbXV4LWF0dHJpYnV0ZXMgZGVmaW5lcyB3aGlj
aCBjYXRlZ29yaWVzIGFwcGx5IHRvIGFsbCBtLSBsaW5lcyBpbiB0aGUgQlVORExFIGdyb3VwIOKA
kyBOT1Qgd2hldGhlciB0aGUgYXR0cmlidXRlIHZhbHVlcyBpbiB0aGUgU0RQIG5lZWQgdG8gaWRl
bnRpY2FsLCBhcyB0aGUgdmFsdWVzIGFyZSB0YWtlbiBmcm9tIHRoZSBCVU5ETEUgbS0gbGluZS4N
Cg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQoNCj40LjUuICBDYXRlZ29yeTogVFJBTlNQT1JU
DQo+DQo+ICAgVGhlIGF0dHJpYnV0ZXMgaW4gdGhlIFRSQU5TUE9SVCBjYXRlZ29yeSBjYW4gYmUg
c2V0IG5vcm1hbGx5IGZvcg0KPiAgIG11bHRpcGxlIGl0ZW1zIGluIGEgbXVsdGlwbGV4ZWQgZ3Jv
dXAgYnV0IHRoZSBzb2Z0d2FyZSBNVVNUIHBpY2sgdGhlDQo+ICAgb25lIHRoYXQncyBhc3NvY2lh
dGVkIHdpdGggdGhlICJtPSIgbGluZSB3aG9zZSBpbmZvcm1hdGlvbiBpcyB1c2VkDQo+ICAgZm9y
IHNldHRpbmcgdXAgdGhlIHVuZGVybHlpbmcgdHJhbnNwb3J0Lg0KPg0KPiBUaGlzIGFscmVhZHkg
c2VlbXMgYWxpZ25lZCB3aXRoIHdoYXQgeW91IHN1Z2dlc3QgYmVsb3cuDQoNClllcy4NCg0KUmVn
YXJkcywNCg0KQ2hyaXN0ZXINCg0KDQpGcm9tOiBtbXVzaWMgW21haWx0bzptbXVzaWMtYm91bmNl
c0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIENocmlzdGVyIEhvbG1iZXJnDQpTZW50OiBkZW4gNCBv
a3RvYmVyIDIwMTYgMTI6NDQNClRvOiBtbXVzaWNAaWV0Zi5vcmc8bWFpbHRvOm1tdXNpY0BpZXRm
Lm9yZz4NCkNjOiBzbmFuZGFrdUBjaXNjby5jb208bWFpbHRvOnNuYW5kYWt1QGNpc2NvLmNvbT4N
ClN1YmplY3Q6IFtNTVVTSUNdIGRyYWZ0LWlldGYtbW11c2ljLXNkcC1tdXgtYXR0cmlidXRlczog
RG8gd2UgbmVlZCB0byBtYW5kYXRlIGlkZW50aWNhbCBTRFAgYXR0cmlidXRlIHZhbHVlcz8NCg0K
SGksDQoNCkJhc2VkIG9uIEVrcuKAmXMgcmV2aWV3IG9mIEJVTkRMRSwgaXQgaGFzIGJlZW4gc3Vn
Z2VzdGVkIHRoYXQgdGhlIHRleHQgc2hvdWxkIG5vdCBmb2N1cyBzbyBtdWNoIG9uIHdoZXRoZXIg
dGhlIGJ1bmRsZWQgbS0gbGluZSBhZGRyZXNzZXMgYXJlIOKAnHNoYXJlZOKAnSBvciDigJx1bmlx
dWXigJ0uIFRoZSBpbXBvcnRhbnQgdGhpbmcgaXMgdGhhdCB0aGUgQlVORExFIG0tIGxpbmUgc3Bl
Y2lmaWVzIHRoZSBhZGRyZXNzIGZvciB0aGUgYnVuZGxlIGdyb3VwLg0KDQpJIHdvbmRlciBpZiB0
aGUgc2FtZSB0aGluZyBhcHBsaWVzIGFsc28gdG8gU0RQIGF0dHJpYnV0ZXMgKHJlYWQ6IGRyYWZ0
LWlldGYtbW11c2ljLXNkcC1tdXgtYXR0cmlidXRlcyk6IEUuZy4sIHdoYXQgaXMgaW1wb3J0YW50
IGlzIHdoZXRoZXIgYW4gYXR0cmlidXRlIHByb3BlcnR5IGlzIGFwcGxpZWQgdG8gYWxsIGJ1bmRs
ZWQgbS0gbGluZXMgb3Igbm90IChiYXNlZCBvbiB0aGUgbXV4IGNhdGVnb3J5KSDigJMgbm90IHdo
ZXRoZXIgdGhlIFNEUCBhdHRyaWJ1dGUgdmFsdWVzIG11c3QgYmUgaWRlbnRpY2FsIGluIGRpZmZl
cmVudCBtLSBsaW5lcy4NCg0KQ29tbWVudHM/DQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQptbXVzaWMgbWFp
bGluZyBsaXN0DQptbXVzaWNAaWV0Zi5vcmc8bWFpbHRvOm1tdXNpY0BpZXRmLm9yZz4NCmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLmhvZW56Yg0KCXttc28t
c3R5bGUtbmFtZTpob2VuemI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFG
NDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21w
b3NlOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3Rl
eHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9u
dC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4t
VVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdp
bjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdl
OldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86
c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2Vu
ZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVk
aXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+
PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1HQiIgbGluaz0iYmx1
ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVMiPkhpLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0ND
Q0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFy
Z2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mZ3Q7PC9zcGFuPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPllvdQ0KIG1lYW4gdGhpcyBtaWdodCBpbXBhY3QgaG93
IHRoZSBJREVOVElDQUwgYW5kIFRSQU5TUE9SVCBjYXRlZ29yaWVzIHNob3VsZCBiZSA8c3BhbiBz
dHlsZT0iY29sb3I6IzFGNDk3RCI+DQomZ3Q7PC9zcGFuPmRlZmluZWQgaW4gLW11eC1hdHRyaWJ1
dGVzPyBUaGF0IHdvdWxkIGJlIGEgcHJldHR5IGZ1bmRhbWVudGFsIGNoYW5nZS48L3NwYW4+PG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMx
RjQ5N0QiPkl04oCZcyBub3QgcmVsYXRlZCB0byB0aGUgZGVmaW5pdGlvbiBvZiBJREVOVElDQUwg
YW5kIFRSQU5TUE9SVCBhcyBzdWNoLiBJdCBpcyBtb3JlIHJlbGF0ZWQNCiB0byBtYW5kYXRpbmcg
dGhlIHNhbWUgYXR0cmlidXRlIHZhbHVlcyBpbiBhbGwgbS0gbGluZXMsIGFzIGF0IHRoZSBlbmQg
b2YgdGhlIGRheSBvbmx5IHRoZSBhdHRyaWJ1dGUgdmFsdWVzIGluIHRoZSBCVU5ETEUgbS0gbGlu
ZSBtYXR0ZXJzLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mZ3Q7PC9zcGFuPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjQuMy4mbmJzcDsNCiBDYXRlZ29yeTogSURFTlRJ
Q0FMPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5
N0QiPiZndDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7Jm5ic3A7
DQogVGhlIGF0dHJpYnV0ZXMgYW5kIHRoZWlyIGFzc29jaWF0ZWQgdmFsdWVzIChpZiBhbnkpIGlu
IHRoZSBJREVOVElDQUw8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jmd0Ozwvc3Bh
bj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mbmJzcDsmbmJzcDsNCiBjYXRlZ29yeSBN
VVNUIGJlIHJlcGVhdGVkIGFjcm9zcyBhbGwgdGhlIG1lZGlhIGRlc2NyaXB0aW9ucyB1bmRlcjwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mZ3Q7PC9zcGFuPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyZuYnNwOw0KIG11bHRpcGxleGluZy48L3NwYW4+PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMt
c2VyaWY7Y29sb3I6IzFGNDk3RCI+Jmd0Ozwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jmd0Ozwvc3Bhbj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5UaGlzDQogdGV4dCBjb3VsZCBpbiBwcmluY2lw
bGUgYmUgY2hhbmdlZCBzYXkgdGhhdCB0aGUgYXR0cmlidXRlIG9mIHRoZSDigJxtPeKAnSBsaW5l
IHdob3NlDQo8c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jmd0O2k8L3NwYW4+bmZvcm1hdGlv
biBpcyB1c2VkIHRvIGRlZmluZSB0aGUgbXVsdGlwbGV4ZWQgZ3JvdXAgKGZvciBCVU5ETEUgdGhh
dCBpcyB0aGUg4oCcbT3igJ0gbGluZQ0KPHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZndDs8
L3NwYW4+Y2FycnlpbmcgdGhlIG1pZCBsaXN0ZWQgZmlyc3Qgb24gdGhlIOKAnGE9QlVORExF4oCd
IGxpbmUpLiBXb3VsZCB5b3UgYWxsb3cg4oCcbT3igJ0gbGluZXMgaW4gdGhlDQo8c3BhbiBzdHls
ZT0iY29sb3I6IzFGNDk3RCI+Jmd0Ozwvc3Bhbj5tdWx0aXBsZXhlZCBncm91cCB0byBoYXZlIG90
aGVyIHZhbHVlcyBvZiBhbiBJREVOVElDQUwgY2F0ZWdvcnkgYXR0cmlidXRlLCBldmVuIGlmIHRo
ZQ0KPHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+dmFsdWUgdG8gdXNlIHdo
ZW4gbXVsdGlwbGV4ZWQgaXMgZ2l2ZW4gYnkgdGhlIEJVTkRMRSDigJxtPeKAnSBsaW5lPyBJbiB3
aGF0IHdheSB3b3VsZA0KPHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+dGhh
dCBiZSB1c2VmdWwgb3IgYW4gaW1wcm92ZW1lbnQgY29tcGFyZWQgdG8gKGFzIG5vdykgcmVxdWly
ZSB0aGF0IHZhbHVlcyBhcmUgYWN0dWFsbHkNCjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4m
Z3Q7aTwvc3Bhbj5kZW50aWNhbCB3aGVuIG11bHRpcGxleGVkPzwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+SW4g
ZmFjdCwgYmFzZWQgb24gYSByYXRoZXIgcmVjZW50IGNoYW5nZSwgQlVORExFIGFjdHVhbGx5IHNh
eXMgKHNlZSBiZWxvdykgdGhhdCBJREVOVElDQUwNCiBhbmQgVFJBTlNQT1JUIGF0dHJpYnV0ZSBh
cmUgT05MWSBpbnNlcnRlZCBpbiB0aGUgQlVORExFIG0tIGxpbmUgdG8gYmVnaW4gd2l0aC4gU28s
IHdlIGFyZSBhbHJlYWR5IG1pc2FsaWduZWQsIGFzIHdlIGRvbuKAmXQgcmVwZWF0IHRoZW0gYWNy
b3NzIGFsbCBtLSBsaW5lc+KApjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mbmJz
cDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87dGV4dC1pbmRl
bnQ6MzYuMHB0Ij4NCjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+
4oCcV2hlbiBhbiBvZmZlcmVyIGFzc29jaWF0ZXMgU0RQIGF0dHJpYnV0ZXMgd2l0aCBhIGJ1bmRs
ZWQgJnF1b3Q7bT0mcXVvdDsgbGluZTwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4m
bmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IGFzc29jaWF0ZWQgd2l0aCBhIHNoYXJlZCBhZGRyZXNzLCBJREVOVElD
QUwgYW5kIFRSQU5TUE9SVCBtdXg8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jm5i
c3A7Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBjYXRlZ29yeSBTRFAgYXR0cmlidXRlcyBbSS1ELmlldGYtbW11c2ljLXNk
cC1tdXgtYXR0cmlidXRlc10gYXJlPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZu
YnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgYXNzb2NpYXRlZCB3aXRoIHRoZSAmcXVvdDttPSZxdW90OyBsaW5lDQo8
Yj5vbmx5IGlmIHRoZSAmcXVvdDttPSZxdW90OyBsaW5lIGlzIGFsc288L2I+PC9zcGFuPjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgYXNzb2NpYXRlZCB3aXRo
IHRoZSBvZmZlcmVyIEJVTkRMRS10YWcuJm5ic3A7IE90aGVyd2lzZSB0aGUgb2ZmZXJlciBNVVNU
PC9zcGFuPjwvYj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PGI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgJm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IE5PVCBhc3NvY2lhdGUgc3VjaCBTRFAgYXR0cmlidXRlcyB3aXRoIHRoZSAmcXVvdDttPSZxdW90
OyBsaW5lPC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5
N0QiPi7igJ08L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPltzdWhhc10gLSBTbyB3aGF0IGhhcHBlbnMgaWYgQlVORExFLXRh
ZyBtPWxpbmUgaW4gdGhlIG9mZmVyIGdldHMgcmVqZWN0ZWQgYW5kIHNheSBydGNwLW11eCB3YXMg
anVzdCBpbmNsdWRlZCBvbmx5IG9uICZuYnNwO3RoYXQgbT1saW5lIGFzIHBlciBhYm92ZSB0ZXh0
IGZvcm0gQlVORExFIHRleHQuJm5ic3A7IElmIGkgdW5kZXJzdGFuZCByaWdodCwgdGhlcmUgaXMg
bm8gcnRjcCBtdXggZm9yIGFueSBvZiB0aGUgbT1saW5lcyB3aGljaA0KIGlzIG5vdCB0aGUgT2Zm
ZXJlciBtaWdodCB3YW50Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2NvbG9yOnJl
ZCI+Tm90ZSB0aGF0IHRoZSB0ZXh0IG9ubHkgYXBwbGllcyB0byB0aGUgY2FzZSB3aGVuIHRoZSBt
LSBsaW5lIGNvbnRhaW5zIGEgc2hhcmVkIGFkZHJlc3MsIGkuZS4sIGl0IGhhcyBhbHJlYWR5IGJl
ZW4gYWNjZXB0ZWQgaW50byB0aGUgQlVORExFIGdyb3VwLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOnJl
ZCI+V2hlbiB5b3Ugc2VuZCB0aGUgaW5pdGlhbCBvZmZlciAoYmVmb3JlIHRoZSBCVU5ETEUgZ3Jv
dXAgaGFzIGJlZW4gY3JlYXRlZCksIG9yIHdoZW4geW91IHdhbnQgdG8gYWRkIGEgbmV3IG0tIGxp
bmUgdG8gYSBCVU5ETEUgZ3JvdXAsIHlvdSBoYXZlIHRvIGluY2x1ZGUgYWxsIGF0dHJpYnV0ZXMN
CiBpbiBhbGwgbS0gbGluZXMsIHVzaW5nIG5vcm1hbCAzMjY0IHByb2NlZHVyZXMuIEJ1dCwgaW4g
dGhhdCBjYXNlIEkgZG9u4oCZdCB0aGluayBkcmFmdC1tdXgtYXR0cmlidXRlcyBhcHBsaWVzIHRv
IGJlZ2luIHdpdGgsIGkuZS4sIHlvdSBjYW4gaW5jbHVkZSB3aGF0ZXZlciBhdHRyaWJ1dGUgdmFs
dWVzLCBhbmQgdGhleSB3aWxsIGJlIHVzZWQgaWYgdGhlIG0tIGxpbmUgaXMgbm90IGFjY2VwdGVk
IGludG8gdGhlIEJVTkRMRSBncm91cC4gZHJhZnQtbXV4LWF0dHJpYnV0ZXMNCiBvbmx5IGFwcGxp
ZXMgb25jZSB0aGUgQlVORExFIGdyb3VwIGhhcyBiZWVuIGNyZWF0ZWQuIEF0IGxlYXN0IHRoYXQg
aXMgbXkgdW5kZXJzdGFuZGluZy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6cmVkIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6cmVkIj5N
eSBwb2ludCBpcyB0aGF0IHdoYXQgaXMgaW1wb3J0YW50IGlzIHRoYXQgZHJhZnQtbXV4LWF0dHJp
YnV0ZXMgZGVmaW5lcyB3aGljaCBjYXRlZ29yaWVzIGFwcGx5IHRvIGFsbCBtLSBsaW5lcyBpbiB0
aGUgQlVORExFIGdyb3VwIOKAkyBOT1Qgd2hldGhlciB0aGUgYXR0cmlidXRlIHZhbHVlcw0KIGlu
IHRoZSBTRFAgbmVlZCB0byBpZGVudGljYWwsIGFzIHRoZSB2YWx1ZXMgYXJlIHRha2VuIGZyb20g
dGhlIEJVTkRMRSBtLSBsaW5lLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpyZWQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpyZWQiPlJl
Z2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOnJlZCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOnJlZCI+Q2hyaXN0ZXI8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1
b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3Bh
ZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBj
bSI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mZ3Q7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWYiPjQuNS4mbmJzcDsNCiBDYXRlZ29yeTogVFJBTlNQT1JUPC9zcGFuPjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZiI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7Jm5ic3A7DQogVGhlIGF0dHJpYnV0
ZXMgaW4gdGhlIFRSQU5TUE9SVCBjYXRlZ29yeSBjYW4gYmUgc2V0IG5vcm1hbGx5IGZvcjwvc3Bh
bj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mZ3Q7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWYiPiZuYnNwOyZuYnNwOw0KIG11bHRpcGxlIGl0ZW1zIGluIGEgbXVsdGlwbGV4
ZWQgZ3JvdXAgYnV0IHRoZSBzb2Z0d2FyZSBNVVNUIHBpY2sgdGhlPC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+
Jm5ic3A7Jm5ic3A7DQogb25lIHRoYXQncyBhc3NvY2lhdGVkIHdpdGggdGhlICZxdW90O209JnF1
b3Q7IGxpbmUgd2hvc2UgaW5mb3JtYXRpb24gaXMgdXNlZDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMUY0OTdEIj4mZ3Q7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNw
OyZuYnNwOw0KIGZvciBzZXR0aW5nIHVwIHRoZSB1bmRlcmx5aW5nIHRyYW5zcG9ydC48L3NwYW4+
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jmd0Ozwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jmd0Ow0K
PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPlRoaXMgYWxyZWFkeSBzZWVtcyBh
bGlnbmVkIHdpdGggd2hhdCB5b3Ugc3VnZ2VzdCBiZWxvdy48L3NwYW4+PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPlllcy48
L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiMxRjQ5N0QiPlJlZ2FyZHMsPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Qi
PiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6Izg4ODg4OCI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMxRjQ5N0QiPkNocmlzdGVyPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojODg4
ODg4Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4w
cHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0Ux
RTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiBtbXVzaWMNCiBbPGEgaHJlZj0ibWFpbHRvOm1t
dXNpYy1ib3VuY2VzQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+bWFpbHRvOm1tdXNpYy1ib3Vu
Y2VzQGlldGYub3JnPC9hPl0NCjxiPk9uIEJlaGFsZiBPZiA8L2I+Q2hyaXN0ZXIgSG9sbWJlcmc8
YnI+DQo8Yj5TZW50OjwvYj4gZGVuIDQgb2t0b2JlciAyMDE2IDEyOjQ0PGJyPg0KPGI+VG86PC9i
PiA8YSBocmVmPSJtYWlsdG86bW11c2ljQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+bW11c2lj
QGlldGYub3JnPC9hPjxicj4NCjxiPkNjOjwvYj4gPGEgaHJlZj0ibWFpbHRvOnNuYW5kYWt1QGNp
c2NvLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnNuYW5kYWt1QGNpc2NvLmNvbTwvYT48YnI+DQo8Yj5T
dWJqZWN0OjwvYj4gW01NVVNJQ10gZHJhZnQtaWV0Zi1tbXVzaWMtc2RwLW11eC1hdHRyaWJ1dGVz
OiBEbyB3ZSBuZWVkIHRvIG1hbmRhdGUgaWRlbnRpY2FsIFNEUCBhdHRyaWJ1dGUgdmFsdWVzPzwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOmJsYWNrIj5IaSw8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Ymxh
Y2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+
QmFzZWQgb24gRWty4oCZcyByZXZpZXcgb2YgQlVORExFLCBpdCBoYXMgYmVlbiBzdWdnZXN0ZWQg
dGhhdCB0aGUgdGV4dCBzaG91bGQgbm90IGZvY3VzIHNvDQogbXVjaCBvbiB3aGV0aGVyIHRoZSBi
dW5kbGVkIG0tIGxpbmUgYWRkcmVzc2VzIGFyZSDigJxzaGFyZWTigJ0gb3Ig4oCcdW5pcXVl4oCd
LiBUaGUgaW1wb3J0YW50IHRoaW5nIGlzIHRoYXQgdGhlIEJVTkRMRSBtLSBsaW5lIHNwZWNpZmll
cyB0aGUgYWRkcmVzcyBmb3IgdGhlIGJ1bmRsZSBncm91cC48L3NwYW4+PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkkgd29uZGVy
IGlmIHRoZSBzYW1lIHRoaW5nIGFwcGxpZXMgYWxzbyB0byBTRFAgYXR0cmlidXRlcyAocmVhZDom
bmJzcDtkcmFmdC1pZXRmLW1tdXNpYy1zZHAtbXV4LWF0dHJpYnV0ZXMpOiBFLmcuLCB3aGF0IGlz
DQogaW1wb3J0YW50IGlzIHdoZXRoZXIgYW4gYXR0cmlidXRlIHByb3BlcnR5IGlzIGFwcGxpZWQg
dG8gYWxsIGJ1bmRsZWQgbS0gbGluZXMgb3Igbm90IChiYXNlZCBvbiB0aGUgbXV4IGNhdGVnb3J5
KSDigJMgbm90IHdoZXRoZXIgdGhlIFNEUCBhdHRyaWJ1dGUgdmFsdWVzIG11c3QgYmUgaWRlbnRp
Y2FsIGluIGRpZmZlcmVudCBtLSBsaW5lcy48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8L3NwYW4+
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmIj5Db21tZW50cz88L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bWFy
Z2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8L3NwYW4+PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmIj5SZWdhcmRzLDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90
dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkNo
cmlzdGVyPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxi
cj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0K
bW11c2ljIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzptbXVzaWNAaWV0Zi5vcmci
Pm1tdXNpY0BpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL21tdXNpYyIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1
b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_7594FB04B1934943A5C02806D1A2204B4BD1C066ESESSMB209erics_--


From nobody Wed Oct  5 12:09:49 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D93212982B for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 12:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 7MMq4xF_-qB7 for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 12:09:45 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 3D3C512981D for <mmusic@ietf.org>; Wed,  5 Oct 2016 12:09:45 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id u124so77162266ywg.3 for <mmusic@ietf.org>; Wed, 05 Oct 2016 12:09:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9Jmzz2ZHNWOPXhhmJ3zeWdryhg8ZZkgqHi6cSKwKGDw=; b=Bh/GZwvd1xsjp6ex0Ix8n0epENLyy8FSGq4DjIEOhkxzumqiv2VFh5QQiEI3MHo0Ne L+7MRtem8dw0kmGRu6ZgkcEqMlnPkKqtw0SkRRfTInDxWWNcJDtTCFY+MdI6Gv8UF9vq tthkd1JFbCrQ3jAwq++kWXftL8BKTczku580SdgG4MbG5c+TybqL3WE50SoC4sShV8ys m4/bgULNHlByQeyhMQhUCY7/+NCJ0KxAE8twIO2GFkUaAeAuHyd31j7DaD9aneN0KN2O 8ZCu0pqSVVlKddqzrCp5PBWxgoxY+gSB6WAufILMKN7qXps0LYk9ZAoVyzYD/e3pTwq5 NW7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=9Jmzz2ZHNWOPXhhmJ3zeWdryhg8ZZkgqHi6cSKwKGDw=; b=NGxnMMEqKH95fXshL878FI8bqtsJQH71EkTUVKl7rwX+2B8QmbBVy5oFC87gNXOsqG edDbL/bI2DTXe97uCcqLUpYFDKX7tN42+r9ktanui1+qe/uIi/0F6+megWjxIWGgyXAz OEiOYdB/H8sRb2Y4ii8JtfxwV7aracNbKs1VkftJX6hgpVaTZT5cUYPKuFLC3k12vVPb 9xonYsxlMLLaenFLCDAiYJNENixG8TBQ0bzjUm8c5YiPBoQKVlQbbvkAOLZhH8BhtqdK XClJ1aTd8V3aPyE63Dz/VbL4OTrHUBKv0JqmZji1yZhICr6cF5oee9AgywzDc+2DxlB5 lrcw==
X-Gm-Message-State: AA6/9Rn6Viib0p9EFsBAo2w6bbfS2f8oBbXd2HLTDuffuYTDLiqzJjg8ZUt2duta+tPQoJcf5jjz+jC5nl/CNg==
X-Received: by 10.37.171.74 with SMTP id u68mr8265826ybi.191.1475694584480; Wed, 05 Oct 2016 12:09:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.158.73 with HTTP; Wed, 5 Oct 2016 12:09:43 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD1C066@ESESSMB209.ericsson.se>
References: <D41963FD.1059F%christer.holmberg@ericsson.com> <AM5PR0701MB25770AB3719E8C10A6C040058DC40@AM5PR0701MB2577.eurprd07.prod.outlook.com> <7594FB04B1934943A5C02806D1A2204B4BD1BCF8@ESESSMB209.ericsson.se> <CAMRcRGQp5u_dP5L++yHu4NtfPWu+wc=v=0Xec+4WeAUw=jZWYQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1C066@ESESSMB209.ericsson.se>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Wed, 5 Oct 2016 12:09:43 -0700
Message-ID: <CAMRcRGTZumBNmKo3tVCjH_fSVm2i_UfiPRRuhbUZM9Q8-hBDAA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c184bb8814b94053e22ebea
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/AHSK_nmEfW-zgLX6VrF2InGnhmQ>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "snandaku@cisco.com" <snandaku@cisco.com>
Subject: Re: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 19:09:47 -0000

--94eb2c184bb8814b94053e22ebea
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Oct 5, 2016 at 11:58 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> >You mean this might impact how the IDENTICAL and TRANSPORT categories
> should be >defined in -mux-attributes? That would be a pretty fundamental
> change.
>
>
>
> It=E2=80=99s not related to the definition of IDENTICAL and TRANSPORT as =
such. It
> is more related to mandating the same attribute values in all m- lines, a=
s
> at the end of the day only the attribute values in the BUNDLE m- line
> matters.
>
> >4.3.  Category: IDENTICAL
>
> >
>
> >   The attributes and their associated values (if any) in the IDENTICAL
>
> >   category MUST be repeated across all the media descriptions under
>
> >   multiplexing.
>
> >
>
> >This text could in principle be changed say that the attribute of the
> =E2=80=9Cm=3D=E2=80=9D line whose >information is used to define the mult=
iplexed group (for
> BUNDLE that is the =E2=80=9Cm=3D=E2=80=9D line >carrying the mid listed f=
irst on the
> =E2=80=9Ca=3DBUNDLE=E2=80=9D line). Would you allow =E2=80=9Cm=3D=E2=80=
=9D lines in the >multiplexed group to
> have other values of an IDENTICAL category attribute, even if the >value
> to use when multiplexed is given by the BUNDLE =E2=80=9Cm=3D=E2=80=9D lin=
e? In what way would
> >that be useful or an improvement compared to (as now) require that
> values are actually >identical when multiplexed?
>
>
>
> In fact, based on a rather recent change, BUNDLE actually says (see below=
)
> that IDENTICAL and TRANSPORT attribute are ONLY inserted in the BUNDLE m-
> line to begin with. So, we are already misaligned, as we don=E2=80=99t re=
peat them
> across all m- lines=E2=80=A6
>
>
>
> =E2=80=9CWhen an offerer associates SDP attributes with a bundled "m=3D" =
line
>
>               associated with a shared address, IDENTICAL and TRANSPORT m=
ux
>
>               category SDP attributes [I-D.ietf-mmusic-sdp-mux-attributes=
]
> are
>
>               associated with the "m=3D" line *only if the "m=3D" line is
> also*
>
> *              associated with the offerer BUNDLE-tag.  Otherwise the
> offerer MUST*
>
> *              NOT associate such SDP attributes with the "m=3D" line*.=
=E2=80=9D
>
>
>
>
>
> [suhas] - So what happens if BUNDLE-tag m=3Dline in the offer gets reject=
ed
> and say rtcp-mux was just included only on  that m=3Dline as per above te=
xt
> form BUNDLE text.  If i understand right, there is no rtcp mux for any of
> the m=3Dlines which is not the Offerer might want
>
>
>
> Note that the text only applies to the case when the m- line contains a
> shared address, i.e., it has already been accepted into the BUNDLE group.
>
>
>
> When you send the initial offer (before the BUNDLE group has been
> created), or when you want to add a new m- line to a BUNDLE group, you ha=
ve
> to include all attributes in all m- lines, using normal 3264 procedures.
> But, in that case I don=E2=80=99t think draft-mux-attributes applies to b=
egin with,
> i.e., you can include whatever attribute values, and they will be used if
> the m- line is not accepted into the BUNDLE group. draft-mux-attributes
> only applies once the BUNDLE group has been created. At least that is my
> understanding
>

[Suhas]

Meta Note:
The mux draft has stayed away from offer/answer procedures to avoid
ambiguities with offers/re-offers and its focus has been defining generic
framework categorizing SDP attributes while performing Media multiplexing

Thus, the case of initial offer applies as well. In that context, on
Initial Offer, the offerer will repeat the SDP attributes that fall under
IDENTICAL category on all the m=3Dlines that it plans to multiplex.

As far as what happens in the subsequent Offer/Answers once BUNDLE address
gets selected is very BUNDLE semantic specific and its totally fine to say
that "the attributes under IDENTICAL & TRANSPORT categories needs to be
included only in the m-line  that selected for BUNDLing once BUNDLE is
successfully negotiated"







> .
>
>
>
> My point is that what is important is that draft-mux-attributes defines
> which categories apply to all m- lines in the BUNDLE group =E2=80=93 NOT =
whether
> the attribute values in the SDP need to identical, as the values are take=
n
> from the BUNDLE m- line.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>
>
>
> >4.5.  Category: TRANSPORT
>
> >
>
> >   The attributes in the TRANSPORT category can be set normally for
>
> >   multiple items in a multiplexed group but the software MUST pick the
>
> >   one that's associated with the "m=3D" line whose information is used
>
> >   for setting up the underlying transport.
>
> >
>
> > This already seems aligned with what you suggest below.
>
>
>
> Yes.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>
> *From:* mmusic [mailto:mmusic-bounces@ietf.org <mmusic-bounces@ietf.org>]=
 *On
> Behalf Of *Christer Holmberg
> *Sent:* den 4 oktober 2016 12:44
> *To:* mmusic@ietf.org
> *Cc:* snandaku@cisco.com
> *Subject:* [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to
> mandate identical SDP attribute values?
>
>
>
> Hi,
>
>
>
> Based on Ekr=E2=80=99s review of BUNDLE, it has been suggested that the t=
ext
> should not focus so much on whether the bundled m- line addresses are
> =E2=80=9Cshared=E2=80=9D or =E2=80=9Cunique=E2=80=9D. The important thing=
 is that the BUNDLE m- line
> specifies the address for the bundle group.
>
>
>
> I wonder if the same thing applies also to SDP attributes
> (read: draft-ietf-mmusic-sdp-mux-attributes): E.g., what is important is
> whether an attribute property is applied to all bundled m- lines or not
> (based on the mux category) =E2=80=93 not whether the SDP attribute value=
s must be
> identical in different m- lines.
>
>
>
> Comments?
>
>
>
> Regards,
>
>
>
> Christer
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>
>

--94eb2c184bb8814b94053e22ebea
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Oct 5, 2016 at 11:58 AM, Christer Holmberg <span dir=3D"ltr">&l=
t;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chris=
ter.holmberg@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-7613774737536997871WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Hi,<u></u><u></u></span></p>
<div>
<div>
<div><span class=3D"">
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">You
 mean this might impact how the IDENTICAL and TRANSPORT categories should b=
e <span style=3D"color:#1f497d">
&gt;</span>defined in -mux-attributes? That would be a pretty fundamental c=
hange.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">It=E2=80=99s not relat=
ed to the definition of IDENTICAL and TRANSPORT as such. It is more related
 to mandating the same attribute values in all m- lines, as at the end of t=
he day only the attribute values in the BUNDLE m- line matters.</span><u></=
u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">4.3.=C2=A0
 Category: IDENTICAL</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 The attributes and their associated values (if any) in the IDENTICAL</span=
><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 category MUST be repeated across all the media descriptions under</span><u=
></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 multiplexing.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">This
 text could in principle be changed say that the attribute of the =E2=80=9C=
m=3D=E2=80=9D line whose
<span style=3D"color:#1f497d">&gt;i</span>nformation is used to define the =
multiplexed group (for BUNDLE that is the =E2=80=9Cm=3D=E2=80=9D line
<span style=3D"color:#1f497d">&gt;</span>carrying the mid listed first on t=
he =E2=80=9Ca=3DBUNDLE=E2=80=9D line). Would you allow =E2=80=9Cm=3D=E2=80=
=9D lines in the
<span style=3D"color:#1f497d">&gt;</span>multiplexed group to have other va=
lues of an IDENTICAL category attribute, even if the
<span style=3D"color:#1f497d">&gt;</span>value to use when multiplexed is g=
iven by the BUNDLE =E2=80=9Cm=3D=E2=80=9D line? In what way would
<span style=3D"color:#1f497d">&gt;</span>that be useful or an improvement c=
ompared to (as now) require that values are actually
<span style=3D"color:#1f497d">&gt;i</span>dentical when multiplexed?</span>=
<u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">In fact, based on a ra=
ther recent change, BUNDLE actually says (see below) that IDENTICAL
 and TRANSPORT attribute are ONLY inserted in the BUNDLE m- line to begin w=
ith. So, we are already misaligned, as we don=E2=80=99t repeat them across =
all m- lines=E2=80=A6</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt">
<span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,sans-serif;color:#1f497d">=E2=80=9CWhen an offerer associates SDP attri=
butes with a bundled &quot;m=3D&quot; line</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 associated with a share=
d address, IDENTICAL and TRANSPORT mux</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 category SDP attributes=
 [I-D.ietf-mmusic-sdp-mux-<wbr>attributes] are</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 associated with the &qu=
ot;m=3D&quot; line
<b>only if the &quot;m=3D&quot; line is also</b></span><u></u><u></u></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 associated with the =
offerer BUNDLE-tag.=C2=A0 Otherwise the offerer MUST</span></b><u></u><u></=
u></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NOT associate such S=
DP attributes with the &quot;m=3D&quot; line</span></b><span lang=3D"EN-US"=
 style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color=
:#1f497d">.=E2=80=9D</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[suhas] - So what happens if BUNDLE-tag m=3Dline in =
the offer gets rejected and say rtcp-mux was just included only on =C2=A0th=
at m=3Dline as per above text form BUNDLE text.=C2=A0 If i understand right=
, there is no rtcp mux for any of the m=3Dlines which
 is not the Offerer might want=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:red">Note that=
 the text only applies to the case when the m- line contains a shared addre=
ss, i.e., it has already been accepted into the BUNDLE group.<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">When you send the initial offer (before t=
he BUNDLE group has been created), or when you want to add a new m- line to=
 a BUNDLE group, you have to include all attributes
 in all m- lines, using normal 3264 procedures. But, in that case I don=E2=
=80=99t think draft-mux-attributes applies to begin with, i.e., you can inc=
lude whatever attribute values, and they will be used if the m- line is not=
 accepted into the BUNDLE group. draft-mux-attributes
 only applies once the BUNDLE group has been created. At least that is my u=
nderstanding</span></p></div></div></div></div></div></div></blockquote><di=
v><br></div><div>[Suhas]=C2=A0</div><div><br></div><div>Meta Note:=C2=A0</d=
iv><div>The mux draft has stayed away from offer/answer procedures to avoid=
 ambiguities with offers/re-offers and its focus has been defining generic =
framework categorizing SDP attributes while performing Media multiplexing</=
div><div><br></div><div>Thus, the case of initial offer applies as well. In=
 that context, on Initial Offer, the offerer will repeat the SDP attributes=
 that fall under IDENTICAL category on all the m=3Dlines that it plans to m=
ultiplex.</div><div><br></div><div>As far as what happens in the subsequent=
 Offer/Answers once BUNDLE address gets selected is very BUNDLE semantic sp=
ecific and its totally fine to say that &quot;the attributes under IDENTICA=
L &amp; TRANSPORT categories needs to be included only in the m-line =C2=A0=
that selected for BUNDLing once BUNDLE is successfully negotiated&quot;</di=
v><div><br></div><div><br></div><div><br></div><div><br></div><div><br></di=
v><div>=C2=A0 =C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-GB=
" link=3D"blue" vlink=3D"purple"><div class=3D"m_-7613774737536997871WordSe=
ction1"><div><div><div><div><p class=3D"MsoNormal"><span style=3D"font-size=
:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:red">.<u></u><u></=
u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">My point is that what is important is tha=
t draft-mux-attributes defines which categories apply to all m- lines in th=
e BUNDLE group =E2=80=93 NOT whether the attribute values
 in the SDP need to identical, as the values are taken from the BUNDLE m- l=
ine.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Regards,<span class=3D"HOEnZb"><font colo=
r=3D"#888888"><u></u><u></u></font></span></span></p><span class=3D"HOEnZb"=
><font color=3D"#888888">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Christer<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
</font></span></div><span class=3D"">
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">4.5.=C2=A0
 Category: TRANSPORT</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 The attributes in the TRANSPORT category can be set normally for</span><u>=
</u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 multiple items in a multiplexed group but the software MUST pick the</span=
><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 one that&#39;s associated with the &quot;m=3D&quot; line whose information=
 is used</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 for setting up the underlying transport.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;
</span><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif">This already seems aligned with what you suggest bel=
ow.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">Yes.</span><u></u><u><=
/u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">Regards,</span><u></u>=
<u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><span sty=
le=3D"color:#888888"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">Christer</span><span s=
tyle=3D"color:#888888"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif">=C2=A0</span><u></u><u></u></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span lang=3D"EN-=
US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"> =
mmusic
 [<a href=3D"mailto:mmusic-bounces@ietf.org" target=3D"_blank">mailto:mmusi=
c-bounces@ietf.<wbr>org</a>]
<b>On Behalf Of </b>Christer Holmberg<br>
<b>Sent:</b> den 4 oktober 2016 12:44<br>
<b>To:</b> <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf=
.org</a><br>
<b>Cc:</b> <a href=3D"mailto:snandaku@cisco.com" target=3D"_blank">snandaku=
@cisco.com</a><br>
<b>Subject:</b> [MMUSIC] draft-ietf-mmusic-sdp-mux-<wbr>attributes: Do we n=
eed to mandate identical SDP attribute values?</span><u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black">Hi,</span><u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black">=C2=A0</span><u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black">Based on Ekr=E2=80=99s r=
eview of BUNDLE, it has been suggested that the text should not focus so
 much on whether the bundled m- line addresses are =E2=80=9Cshared=E2=80=9D=
 or =E2=80=9Cunique=E2=80=9D. The important thing is that the BUNDLE m- lin=
e specifies the address for the bundle group.</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black">=C2=A0</span><u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">I wonder if the same thing applies also to SDP attrib=
utes (read:=C2=A0draft-ietf-mmusic-sdp-<wbr>mux-attributes): E.g., what is
 important is whether an attribute property is applied to all bundled m- li=
nes or not (based on the mux category) =E2=80=93 not whether the SDP attrib=
ute values must be identical in different m- lines.</span><u></u><u></u></p=
>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Comments?</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Regards,</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Christer</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><u></u><u></u></p>
</blockquote>
</span></div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div>

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

--94eb2c184bb8814b94053e22ebea--


From nobody Wed Oct  5 12:33:12 2016
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 34FC6129857 for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 12:33:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 Wl07T6v-tUpW for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 12:33:07 -0700 (PDT)
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 5E66B129851 for <mmusic@ietf.org>; Wed,  5 Oct 2016 12:33:06 -0700 (PDT)
X-AuditID: c1b4fb30-b87ff70000000cb2-21-57f55570ed62
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by  (Symantec Mail Security) with SMTP id 55.20.03250.07555F75; Wed,  5 Oct 2016 21:33:04 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0319.002; Wed, 5 Oct 2016 21:33:02 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Thread-Topic: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
Thread-Index: AQHSHiwofDubrkbtCEu3VfmkQRPgmqCaG2pAgAAN1UD//+oUAIAAIpcg///kRYCAACZH8A==
Date: Wed, 5 Oct 2016 19:33:02 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD1C225@ESESSMB209.ericsson.se>
References: <D41963FD.1059F%christer.holmberg@ericsson.com> <AM5PR0701MB25770AB3719E8C10A6C040058DC40@AM5PR0701MB2577.eurprd07.prod.outlook.com> <7594FB04B1934943A5C02806D1A2204B4BD1BCF8@ESESSMB209.ericsson.se> <CAMRcRGQp5u_dP5L++yHu4NtfPWu+wc=v=0Xec+4WeAUw=jZWYQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1C066@ESESSMB209.ericsson.se> <CAMRcRGTZumBNmKo3tVCjH_fSVm2i_UfiPRRuhbUZM9Q8-hBDAA@mail.gmail.com>
In-Reply-To: <CAMRcRGTZumBNmKo3tVCjH_fSVm2i_UfiPRRuhbUZM9Q8-hBDAA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BD1C225ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprLIsWRmVeSWpSXmKPExsUyM2K7vW5B6Ndwg+k7VSymLn/MYrH4wH1W i51zO5gdmD2m/N7I6rFz1l12jyVLfjIFMEdx2aSk5mSWpRbp2yVwZWw92sxWMOMWU8Wju91M DYxTLjJ1MXJySAiYSDyZNw/I5uIQEljPKLF7/xE2kISQwCJGiclnQroYOTjYBCwkuv9pg4RF BLQkVi+eywQSZhaokGi7owMSFhYolnix9AYzREmJxOnlW1lBSkQEwiT2dfuDhFkEVCRO7bjD CGLzCvhK/F71HWrrCmaJ6ztfgJ3DKRAosWTqGTCbUUBM4vupNWA2s4C4xK0n86FOFpBYsuc8 M4QtKvHy8T9WCFtJonHJE1aI+nyJO8cuskEsE5Q4OfMJywRGkVlIRs1CUjYLSdkssM80Jdbv 0ocoUZSY0v2QHcLWkGidM5cdWXwBI/sqRtHi1OKk3HQjI73Uoszk4uL8PL281JJNjMBIO7jl t8EOxpfPHQ8xCnAwKvHwLrD/Gi7EmlhWXJl7iFGCg1lJhNc2GCjEm5JYWZValB9fVJqTWnyI UZqDRUmc12zl/XAhgfTEktTs1NSC1CKYLBMHp1QDo438v7RvJ8XMT1y4aDV3QmwH58HOvgV1 vR+tu/88/h/xyFNqptWS7SL8vYEhs9lun3uzKPrd/K4TDN0rt7UL/Hgz7V533sKz1gVTbx+f 8GPiz6e3i7+8+sXoWD5P6Fr6/mV/PuwqEl/CICB5PTT8zPWou/MmSU3m5NDm9nR6HDHdiEfi 9JY0q8dKLMUZiYZazEXFiQCNd3C/sAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/c4j0GJPoeup1KrcYkaACmeDqGQ4>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "snandaku@cisco.com" <snandaku@cisco.com>
Subject: Re: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 19:33:10 -0000

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

SGksDQpIaSwNCj5Zb3UgbWVhbiB0aGlzIG1pZ2h0IGltcGFjdCBob3cgdGhlIElERU5USUNBTCBh
bmQgVFJBTlNQT1JUIGNhdGVnb3JpZXMgc2hvdWxkIGJlID5kZWZpbmVkIGluIC1tdXgtYXR0cmli
dXRlcz8gVGhhdCB3b3VsZCBiZSBhIHByZXR0eSBmdW5kYW1lbnRhbCBjaGFuZ2UuDQoNCkl04oCZ
cyBub3QgcmVsYXRlZCB0byB0aGUgZGVmaW5pdGlvbiBvZiBJREVOVElDQUwgYW5kIFRSQU5TUE9S
VCBhcyBzdWNoLiBJdCBpcyBtb3JlIHJlbGF0ZWQgdG8gbWFuZGF0aW5nIHRoZSBzYW1lIGF0dHJp
YnV0ZSB2YWx1ZXMgaW4gYWxsIG0tIGxpbmVzLCBhcyBhdCB0aGUgZW5kIG9mIHRoZSBkYXkgb25s
eSB0aGUgYXR0cmlidXRlIHZhbHVlcyBpbiB0aGUgQlVORExFIG0tIGxpbmUgbWF0dGVycy4NCj40
LjMuICBDYXRlZ29yeTogSURFTlRJQ0FMDQo+DQo+ICAgVGhlIGF0dHJpYnV0ZXMgYW5kIHRoZWly
IGFzc29jaWF0ZWQgdmFsdWVzIChpZiBhbnkpIGluIHRoZSBJREVOVElDQUwNCj4gICBjYXRlZ29y
eSBNVVNUIGJlIHJlcGVhdGVkIGFjcm9zcyBhbGwgdGhlIG1lZGlhIGRlc2NyaXB0aW9ucyB1bmRl
cg0KPiAgIG11bHRpcGxleGluZy4NCj4NCj5UaGlzIHRleHQgY291bGQgaW4gcHJpbmNpcGxlIGJl
IGNoYW5nZWQgc2F5IHRoYXQgdGhlIGF0dHJpYnV0ZSBvZiB0aGUg4oCcbT3igJ0gbGluZSB3aG9z
ZSA+aW5mb3JtYXRpb24gaXMgdXNlZCB0byBkZWZpbmUgdGhlIG11bHRpcGxleGVkIGdyb3VwIChm
b3IgQlVORExFIHRoYXQgaXMgdGhlIOKAnG094oCdIGxpbmUgPmNhcnJ5aW5nIHRoZSBtaWQgbGlz
dGVkIGZpcnN0IG9uIHRoZSDigJxhPUJVTkRMReKAnSBsaW5lKS4gV291bGQgeW91IGFsbG93IOKA
nG094oCdIGxpbmVzIGluIHRoZSA+bXVsdGlwbGV4ZWQgZ3JvdXAgdG8gaGF2ZSBvdGhlciB2YWx1
ZXMgb2YgYW4gSURFTlRJQ0FMIGNhdGVnb3J5IGF0dHJpYnV0ZSwgZXZlbiBpZiB0aGUgPnZhbHVl
IHRvIHVzZSB3aGVuIG11bHRpcGxleGVkIGlzIGdpdmVuIGJ5IHRoZSBCVU5ETEUg4oCcbT3igJ0g
bGluZT8gSW4gd2hhdCB3YXkgd291bGQgPnRoYXQgYmUgdXNlZnVsIG9yIGFuIGltcHJvdmVtZW50
IGNvbXBhcmVkIHRvIChhcyBub3cpIHJlcXVpcmUgdGhhdCB2YWx1ZXMgYXJlIGFjdHVhbGx5ID5p
ZGVudGljYWwgd2hlbiBtdWx0aXBsZXhlZD8NCg0KSW4gZmFjdCwgYmFzZWQgb24gYSByYXRoZXIg
cmVjZW50IGNoYW5nZSwgQlVORExFIGFjdHVhbGx5IHNheXMgKHNlZSBiZWxvdykgdGhhdCBJREVO
VElDQUwgYW5kIFRSQU5TUE9SVCBhdHRyaWJ1dGUgYXJlIE9OTFkgaW5zZXJ0ZWQgaW4gdGhlIEJV
TkRMRSBtLSBsaW5lIHRvIGJlZ2luIHdpdGguIFNvLCB3ZSBhcmUgYWxyZWFkeSBtaXNhbGlnbmVk
LCBhcyB3ZSBkb27igJl0IHJlcGVhdCB0aGVtIGFjcm9zcyBhbGwgbS0gbGluZXPigKYNCg0K4oCc
V2hlbiBhbiBvZmZlcmVyIGFzc29jaWF0ZXMgU0RQIGF0dHJpYnV0ZXMgd2l0aCBhIGJ1bmRsZWQg
Im09IiBsaW5lDQogICAgICAgICAgICAgIGFzc29jaWF0ZWQgd2l0aCBhIHNoYXJlZCBhZGRyZXNz
LCBJREVOVElDQUwgYW5kIFRSQU5TUE9SVCBtdXgNCiAgICAgICAgICAgICAgY2F0ZWdvcnkgU0RQ
IGF0dHJpYnV0ZXMgW0ktRC5pZXRmLW1tdXNpYy1zZHAtbXV4LWF0dHJpYnV0ZXNdIGFyZQ0KICAg
ICAgICAgICAgICBhc3NvY2lhdGVkIHdpdGggdGhlICJtPSIgbGluZSBvbmx5IGlmIHRoZSAibT0i
IGxpbmUgaXMgYWxzbw0KICAgICAgICAgICAgICBhc3NvY2lhdGVkIHdpdGggdGhlIG9mZmVyZXIg
QlVORExFLXRhZy4gIE90aGVyd2lzZSB0aGUgb2ZmZXJlciBNVVNUDQogICAgICAgICAgICAgIE5P
VCBhc3NvY2lhdGUgc3VjaCBTRFAgYXR0cmlidXRlcyB3aXRoIHRoZSAibT0iIGxpbmUu4oCdDQoN
Cg0KW3N1aGFzXSAtIFNvIHdoYXQgaGFwcGVucyBpZiBCVU5ETEUtdGFnIG09bGluZSBpbiB0aGUg
b2ZmZXIgZ2V0cyByZWplY3RlZCBhbmQgc2F5IHJ0Y3AtbXV4IHdhcyBqdXN0IGluY2x1ZGVkIG9u
bHkgb24gIHRoYXQgbT1saW5lIGFzIHBlciBhYm92ZSB0ZXh0IGZvcm0gQlVORExFIHRleHQuICBJ
ZiBpIHVuZGVyc3RhbmQgcmlnaHQsIHRoZXJlIGlzIG5vIHJ0Y3AgbXV4IGZvciBhbnkgb2YgdGhl
IG09bGluZXMgd2hpY2ggaXMgbm90IHRoZSBPZmZlcmVyIG1pZ2h0IHdhbnQNCg0KTm90ZSB0aGF0
IHRoZSB0ZXh0IG9ubHkgYXBwbGllcyB0byB0aGUgY2FzZSB3aGVuIHRoZSBtLSBsaW5lIGNvbnRh
aW5zIGEgc2hhcmVkIGFkZHJlc3MsIGkuZS4sIGl0IGhhcyBhbHJlYWR5IGJlZW4gYWNjZXB0ZWQg
aW50byB0aGUgQlVORExFIGdyb3VwLg0KDQpXaGVuIHlvdSBzZW5kIHRoZSBpbml0aWFsIG9mZmVy
IChiZWZvcmUgdGhlIEJVTkRMRSBncm91cCBoYXMgYmVlbiBjcmVhdGVkKSwgb3Igd2hlbiB5b3Ug
d2FudCB0byBhZGQgYSBuZXcgbS0gbGluZSB0byBhIEJVTkRMRSBncm91cCwgeW91IGhhdmUgdG8g
aW5jbHVkZSBhbGwgYXR0cmlidXRlcyBpbiBhbGwgbS0gbGluZXMsIHVzaW5nIG5vcm1hbCAzMjY0
IHByb2NlZHVyZXMuIEJ1dCwgaW4gdGhhdCBjYXNlIEkgZG9u4oCZdCB0aGluayBkcmFmdC1tdXgt
YXR0cmlidXRlcyBhcHBsaWVzIHRvIGJlZ2luIHdpdGgsIGkuZS4sIHlvdSBjYW4gaW5jbHVkZSB3
aGF0ZXZlciBhdHRyaWJ1dGUgdmFsdWVzLCBhbmQgdGhleSB3aWxsIGJlIHVzZWQgaWYgdGhlIG0t
IGxpbmUgaXMgbm90IGFjY2VwdGVkIGludG8gdGhlIEJVTkRMRSBncm91cC4gZHJhZnQtbXV4LWF0
dHJpYnV0ZXMgb25seSBhcHBsaWVzIG9uY2UgdGhlIEJVTkRMRSBncm91cCBoYXMgYmVlbiBjcmVh
dGVkLiBBdCBsZWFzdCB0aGF0IGlzIG15IHVuZGVyc3RhbmRpbmcNCg0KW1N1aGFzXQ0KDQpNZXRh
IE5vdGU6DQpUaGUgbXV4IGRyYWZ0IGhhcyBzdGF5ZWQgYXdheSBmcm9tIG9mZmVyL2Fuc3dlciBw
cm9jZWR1cmVzIHRvIGF2b2lkIGFtYmlndWl0aWVzIHdpdGggb2ZmZXJzL3JlLW9mZmVycyBhbmQg
aXRzIGZvY3VzIGhhcyBiZWVuIGRlZmluaW5nIGdlbmVyaWMgZnJhbWV3b3JrIGNhdGVnb3Jpemlu
ZyBTRFAgYXR0cmlidXRlcyB3aGlsZSBwZXJmb3JtaW5nIE1lZGlhIG11bHRpcGxleGluZw0KDQpU
aHVzLCB0aGUgY2FzZSBvZiBpbml0aWFsIG9mZmVyIGFwcGxpZXMgYXMgd2VsbC4gSW4gdGhhdCBj
b250ZXh0LCBvbiBJbml0aWFsIE9mZmVyLCB0aGUgb2ZmZXJlciB3aWxsIHJlcGVhdCB0aGUgU0RQ
IGF0dHJpYnV0ZXMgdGhhdCBmYWxsIHVuZGVyIElERU5USUNBTCBjYXRlZ29yeSBvbiBhbGwgdGhl
IG09bGluZXMgdGhhdCBpdCBwbGFucyB0byBtdWx0aXBsZXguDQoNCldoYXQgaXMgdGhlIHJlYXNv
biBmb3IgaGF2aW5nIGRpZmZlcmVudCBydWxlcyBmb3IgSURFTlRJQ0FMIGFuZCBUUkFOUE9SVD8g
V2l0aCBUUkFOU1BPUlQgeW91IGNhbiB1c2UgZGlmZmVyZW50IGF0dHJpYnV0ZSB2YWx1ZXMsIGJl
Y2F1c2UgdGhlIOKAnHNvZnR3YXJlIHdpbGwgcGljayB0aGUgY29ycmVjdCB2YWx1ZeKAnS4gV2h5
IG5vdCB1c2UgdGhlIHNvZnR3YXJlLW11c3QtcGljayBydWxlIGFsc28gZm9yIElERU5USUNBTD8N
Cg0KDQpBcyBmYXIgYXMgd2hhdCBoYXBwZW5zIGluIHRoZSBzdWJzZXF1ZW50IE9mZmVyL0Fuc3dl
cnMgb25jZSBCVU5ETEUgYWRkcmVzcyBnZXRzIHNlbGVjdGVkIGlzIHZlcnkgQlVORExFIHNlbWFu
dGljIHNwZWNpZmljIGFuZCBpdHMgdG90YWxseSBmaW5lIHRvIHNheSB0aGF0ICJ0aGUgYXR0cmli
dXRlcyB1bmRlciBJREVOVElDQUwgJiBUUkFOU1BPUlQgY2F0ZWdvcmllcyBuZWVkcyB0byBiZSBp
bmNsdWRlZCBvbmx5IGluIHRoZSBtLWxpbmUgIHRoYXQgc2VsZWN0ZWQgZm9yIEJVTkRMaW5nIG9u
Y2UgQlVORExFIGlzIHN1Y2Nlc3NmdWxseSBuZWdvdGlhdGVkIg0KDQpHb29kLg0KDQpSZWdhcmRz
LA0KDQpDaHJpc3Rlcg0KDQoNCg0KDQouDQoNCk15IHBvaW50IGlzIHRoYXQgd2hhdCBpcyBpbXBv
cnRhbnQgaXMgdGhhdCBkcmFmdC1tdXgtYXR0cmlidXRlcyBkZWZpbmVzIHdoaWNoIGNhdGVnb3Jp
ZXMgYXBwbHkgdG8gYWxsIG0tIGxpbmVzIGluIHRoZSBCVU5ETEUgZ3JvdXAg4oCTIE5PVCB3aGV0
aGVyIHRoZSBhdHRyaWJ1dGUgdmFsdWVzIGluIHRoZSBTRFAgbmVlZCB0byBpZGVudGljYWwsIGFz
IHRoZSB2YWx1ZXMgYXJlIHRha2VuIGZyb20gdGhlIEJVTkRMRSBtLSBsaW5lLg0KDQpSZWdhcmRz
LA0KDQpDaHJpc3Rlcg0KDQoNCg0KPjQuNS4gIENhdGVnb3J5OiBUUkFOU1BPUlQNCj4NCj4gICBU
aGUgYXR0cmlidXRlcyBpbiB0aGUgVFJBTlNQT1JUIGNhdGVnb3J5IGNhbiBiZSBzZXQgbm9ybWFs
bHkgZm9yDQo+ICAgbXVsdGlwbGUgaXRlbXMgaW4gYSBtdWx0aXBsZXhlZCBncm91cCBidXQgdGhl
IHNvZnR3YXJlIE1VU1QgcGljayB0aGUNCj4gICBvbmUgdGhhdCdzIGFzc29jaWF0ZWQgd2l0aCB0
aGUgIm09IiBsaW5lIHdob3NlIGluZm9ybWF0aW9uIGlzIHVzZWQNCj4gICBmb3Igc2V0dGluZyB1
cCB0aGUgdW5kZXJseWluZyB0cmFuc3BvcnQuDQo+DQo+IFRoaXMgYWxyZWFkeSBzZWVtcyBhbGln
bmVkIHdpdGggd2hhdCB5b3Ugc3VnZ2VzdCBiZWxvdy4NCg0KWWVzLg0KDQpSZWdhcmRzLA0KDQpD
aHJpc3Rlcg0KDQoNCkZyb206IG1tdXNpYyBbbWFpbHRvOm1tdXNpYy1ib3VuY2VzQGlldGYub3Jn
XSBPbiBCZWhhbGYgT2YgQ2hyaXN0ZXIgSG9sbWJlcmcNClNlbnQ6IGRlbiA0IG9rdG9iZXIgMjAx
NiAxMjo0NA0KVG86IG1tdXNpY0BpZXRmLm9yZzxtYWlsdG86bW11c2ljQGlldGYub3JnPg0KQ2M6
IHNuYW5kYWt1QGNpc2NvLmNvbTxtYWlsdG86c25hbmRha3VAY2lzY28uY29tPg0KU3ViamVjdDog
W01NVVNJQ10gZHJhZnQtaWV0Zi1tbXVzaWMtc2RwLW11eC1hdHRyaWJ1dGVzOiBEbyB3ZSBuZWVk
IHRvIG1hbmRhdGUgaWRlbnRpY2FsIFNEUCBhdHRyaWJ1dGUgdmFsdWVzPw0KDQpIaSwNCg0KQmFz
ZWQgb24gRWty4oCZcyByZXZpZXcgb2YgQlVORExFLCBpdCBoYXMgYmVlbiBzdWdnZXN0ZWQgdGhh
dCB0aGUgdGV4dCBzaG91bGQgbm90IGZvY3VzIHNvIG11Y2ggb24gd2hldGhlciB0aGUgYnVuZGxl
ZCBtLSBsaW5lIGFkZHJlc3NlcyBhcmUg4oCcc2hhcmVk4oCdIG9yIOKAnHVuaXF1ZeKAnS4gVGhl
IGltcG9ydGFudCB0aGluZyBpcyB0aGF0IHRoZSBCVU5ETEUgbS0gbGluZSBzcGVjaWZpZXMgdGhl
IGFkZHJlc3MgZm9yIHRoZSBidW5kbGUgZ3JvdXAuDQoNCkkgd29uZGVyIGlmIHRoZSBzYW1lIHRo
aW5nIGFwcGxpZXMgYWxzbyB0byBTRFAgYXR0cmlidXRlcyAocmVhZDogZHJhZnQtaWV0Zi1tbXVz
aWMtc2RwLW11eC1hdHRyaWJ1dGVzKTogRS5nLiwgd2hhdCBpcyBpbXBvcnRhbnQgaXMgd2hldGhl
ciBhbiBhdHRyaWJ1dGUgcHJvcGVydHkgaXMgYXBwbGllZCB0byBhbGwgYnVuZGxlZCBtLSBsaW5l
cyBvciBub3QgKGJhc2VkIG9uIHRoZSBtdXggY2F0ZWdvcnkpIOKAkyBub3Qgd2hldGhlciB0aGUg
U0RQIGF0dHJpYnV0ZSB2YWx1ZXMgbXVzdCBiZSBpZGVudGljYWwgaW4gZGlmZmVyZW50IG0tIGxp
bmVzLg0KDQpDb21tZW50cz8NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1tdXNpYyBtYWlsaW5nIGxpc3QN
Cm1tdXNpY0BpZXRmLm9yZzxtYWlsdG86bW11c2ljQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMNCg0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLmhvZW56Yg0KCXttc28t
c3R5bGUtbmFtZTpob2VuemI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFG
NDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21w
b3NlOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3Rl
eHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9u
dC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4t
VVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdp
bjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdl
OldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86
c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2Vu
ZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVk
aXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+
PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1HQiIgbGluaz0iYmx1
ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOnJlZDttc28tZmFyZWFzdC1sYW5ndWFn
ZTpFTi1VUyI+SGksPG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0K
PGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0Mg
MS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4t
cmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+SGksPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0
OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVm
dDo0LjhwdDttYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTo1
LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mZ3Q7PC9zcGFuPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWYiPllvdQ0KIG1lYW4gdGhpcyBtaWdodCBpbXBhY3QgaG93IHRoZSBJREVO
VElDQUwgYW5kIFRSQU5TUE9SVCBjYXRlZ29yaWVzIHNob3VsZCBiZSA8c3BhbiBzdHlsZT0iY29s
b3I6IzFGNDk3RCI+DQomZ3Q7PC9zcGFuPmRlZmluZWQgaW4gLW11eC1hdHRyaWJ1dGVzPyBUaGF0
IHdvdWxkIGJlIGEgcHJldHR5IGZ1bmRhbWVudGFsIGNoYW5nZS48L3NwYW4+PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkl0
4oCZcyBub3QgcmVsYXRlZCB0byB0aGUgZGVmaW5pdGlvbiBvZiBJREVOVElDQUwgYW5kIFRSQU5T
UE9SVCBhcyBzdWNoLiBJdCBpcyBtb3JlIHJlbGF0ZWQNCiB0byBtYW5kYXRpbmcgdGhlIHNhbWUg
YXR0cmlidXRlIHZhbHVlcyBpbiBhbGwgbS0gbGluZXMsIGFzIGF0IHRoZSBlbmQgb2YgdGhlIGRh
eSBvbmx5IHRoZSBhdHRyaWJ1dGUgdmFsdWVzIGluIHRoZSBCVU5ETEUgbS0gbGluZSBtYXR0ZXJz
Ljwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mZ3Q7PC9zcGFuPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWYiPjQuMy4mbmJzcDsNCiBDYXRlZ29yeTogSURFTlRJQ0FMPC9zcGFu
PjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZiI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZndDs8
L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7Jm5ic3A7DQogVGhlIGF0
dHJpYnV0ZXMgYW5kIHRoZWlyIGFzc29jaWF0ZWQgdmFsdWVzIChpZiBhbnkpIGluIHRoZSBJREVO
VElDQUw8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jmd0Ozwvc3Bhbj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mbmJzcDsmbmJzcDsNCiBjYXRlZ29yeSBNVVNUIGJlIHJl
cGVhdGVkIGFjcm9zcyBhbGwgdGhlIG1lZGlhIGRlc2NyaXB0aW9ucyB1bmRlcjwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mZ3Q7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMt
c2VyaWYiPiZuYnNwOyZuYnNwOw0KIG11bHRpcGxleGluZy48L3NwYW4+PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6IzFGNDk3RCI+Jmd0Ozwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mbmJz
cDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jmd0Ozwvc3Bhbj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmIj5UaGlzDQogdGV4dCBjb3VsZCBpbiBwcmluY2lwbGUgYmUgY2hh
bmdlZCBzYXkgdGhhdCB0aGUgYXR0cmlidXRlIG9mIHRoZSDigJxtPeKAnSBsaW5lIHdob3NlDQo8
c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jmd0O2k8L3NwYW4+bmZvcm1hdGlvbiBpcyB1c2Vk
IHRvIGRlZmluZSB0aGUgbXVsdGlwbGV4ZWQgZ3JvdXAgKGZvciBCVU5ETEUgdGhhdCBpcyB0aGUg
4oCcbT3igJ0gbGluZQ0KPHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+Y2Fy
cnlpbmcgdGhlIG1pZCBsaXN0ZWQgZmlyc3Qgb24gdGhlIOKAnGE9QlVORExF4oCdIGxpbmUpLiBX
b3VsZCB5b3UgYWxsb3cg4oCcbT3igJ0gbGluZXMgaW4gdGhlDQo8c3BhbiBzdHlsZT0iY29sb3I6
IzFGNDk3RCI+Jmd0Ozwvc3Bhbj5tdWx0aXBsZXhlZCBncm91cCB0byBoYXZlIG90aGVyIHZhbHVl
cyBvZiBhbiBJREVOVElDQUwgY2F0ZWdvcnkgYXR0cmlidXRlLCBldmVuIGlmIHRoZQ0KPHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+dmFsdWUgdG8gdXNlIHdoZW4gbXVsdGlw
bGV4ZWQgaXMgZ2l2ZW4gYnkgdGhlIEJVTkRMRSDigJxtPeKAnSBsaW5lPyBJbiB3aGF0IHdheSB3
b3VsZA0KPHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+dGhhdCBiZSB1c2Vm
dWwgb3IgYW4gaW1wcm92ZW1lbnQgY29tcGFyZWQgdG8gKGFzIG5vdykgcmVxdWlyZSB0aGF0IHZh
bHVlcyBhcmUgYWN0dWFsbHkNCjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mZ3Q7aTwvc3Bh
bj5kZW50aWNhbCB3aGVuIG11bHRpcGxleGVkPzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0
OTdEIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+SW4gZmFjdCwgYmFz
ZWQgb24gYSByYXRoZXIgcmVjZW50IGNoYW5nZSwgQlVORExFIGFjdHVhbGx5IHNheXMgKHNlZSBi
ZWxvdykgdGhhdCBJREVOVElDQUwNCiBhbmQgVFJBTlNQT1JUIGF0dHJpYnV0ZSBhcmUgT05MWSBp
bnNlcnRlZCBpbiB0aGUgQlVORExFIG0tIGxpbmUgdG8gYmVnaW4gd2l0aC4gU28sIHdlIGFyZSBh
bHJlYWR5IG1pc2FsaWduZWQsIGFzIHdlIGRvbuKAmXQgcmVwZWF0IHRoZW0gYWNyb3NzIGFsbCBt
LSBsaW5lc+KApjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87dGV4dC1pbmRlbnQ6MzYuMHB0
Ij4NCjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+4oCcV2hlbiBh
biBvZmZlcmVyIGFzc29jaWF0ZXMgU0RQIGF0dHJpYnV0ZXMgd2l0aCBhIGJ1bmRsZWQgJnF1b3Q7
bT0mcXVvdDsgbGluZTwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJz
cDsgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7IGFzc29jaWF0ZWQgd2l0aCBhIHNoYXJlZCBhZGRyZXNzLCBJREVOVElDQUwgYW5kIFRS
QU5TUE9SVCBtdXg8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7
ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyBjYXRlZ29yeSBTRFAgYXR0cmlidXRlcyBbSS1ELmlldGYtbW11c2ljLXNkcC1tdXgtYXR0
cmlidXRlc10gYXJlPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNw
OyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgYXNzb2NpYXRlZCB3aXRoIHRoZSAmcXVvdDttPSZxdW90OyBsaW5lDQo8Yj5vbmx5IGlm
IHRoZSAmcXVvdDttPSZxdW90OyBsaW5lIGlzIGFsc288L2I+PC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgYXNzb2NpYXRlZCB3aXRoIHRoZSBvZmZl
cmVyIEJVTkRMRS10YWcuJm5ic3A7IE90aGVyd2lzZSB0aGUgb2ZmZXJlciBNVVNUPC9zcGFuPjwv
Yj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PGI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IE5PVCBhc3Nv
Y2lhdGUgc3VjaCBTRFAgYXR0cmlidXRlcyB3aXRoIHRoZSAmcXVvdDttPSZxdW90OyBsaW5lPC9z
cGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPi7igJ08
L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj5bc3VoYXNdIC0gU28gd2hhdCBoYXBwZW5zIGlmIEJVTkRMRS10YWcgbT1s
aW5lIGluIHRoZSBvZmZlciBnZXRzIHJlamVjdGVkIGFuZCBzYXkgcnRjcC1tdXggd2FzIGp1c3Qg
aW5jbHVkZWQgb25seSBvbiAmbmJzcDt0aGF0IG09bGluZSBhcyBwZXIgYWJvdmUgdGV4dCBmb3Jt
IEJVTkRMRSB0ZXh0LiZuYnNwOyBJZiBpIHVuZGVyc3RhbmQNCiByaWdodCwgdGhlcmUgaXMgbm8g
cnRjcCBtdXggZm9yIGFueSBvZiB0aGUgbT1saW5lcyB3aGljaCBpcyBub3QgdGhlIE9mZmVyZXIg
bWlnaHQgd2FudCZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Y29sb3I6cmVk
Ij5Ob3RlIHRoYXQgdGhlIHRleHQgb25seSBhcHBsaWVzIHRvIHRoZSBjYXNlIHdoZW4gdGhlIG0t
IGxpbmUgY29udGFpbnMgYSBzaGFyZWQgYWRkcmVzcywgaS5lLiwgaXQgaGFzIGFscmVhZHkgYmVl
biBhY2NlcHRlZCBpbnRvIHRoZSBCVU5ETEUNCiBncm91cC48L3NwYW4+PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7PC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6cmVkIj5XaGVuIHlvdSBzZW5kIHRoZSBpbml0aWFsIG9mZmVyIChiZWZvcmUgdGhlIEJVTkRM
RSBncm91cCBoYXMgYmVlbiBjcmVhdGVkKSwgb3Igd2hlbiB5b3Ugd2FudCB0byBhZGQgYSBuZXcN
CiBtLSBsaW5lIHRvIGEgQlVORExFIGdyb3VwLCB5b3UgaGF2ZSB0byBpbmNsdWRlIGFsbCBhdHRy
aWJ1dGVzIGluIGFsbCBtLSBsaW5lcywgdXNpbmcgbm9ybWFsIDMyNjQgcHJvY2VkdXJlcy4gQnV0
LCBpbiB0aGF0IGNhc2UgSSBkb27igJl0IHRoaW5rIGRyYWZ0LW11eC1hdHRyaWJ1dGVzIGFwcGxp
ZXMgdG8gYmVnaW4gd2l0aCwgaS5lLiwgeW91IGNhbiBpbmNsdWRlIHdoYXRldmVyIGF0dHJpYnV0
ZSB2YWx1ZXMsIGFuZCB0aGV5IHdpbGwgYmUgdXNlZA0KIGlmIHRoZSBtLSBsaW5lIGlzIG5vdCBh
Y2NlcHRlZCBpbnRvIHRoZSBCVU5ETEUgZ3JvdXAuIGRyYWZ0LW11eC1hdHRyaWJ1dGVzIG9ubHkg
YXBwbGllcyBvbmNlIHRoZSBCVU5ETEUgZ3JvdXAgaGFzIGJlZW4gY3JlYXRlZC4gQXQgbGVhc3Qg
dGhhdCBpcyBteSB1bmRlcnN0YW5kaW5nPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+W1N1aGFzXSZuYnNwOzxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5NZXRhIE5vdGU6Jm5ic3A7PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgbXV4
IGRyYWZ0IGhhcyBzdGF5ZWQgYXdheSBmcm9tIG9mZmVyL2Fuc3dlciBwcm9jZWR1cmVzIHRvIGF2
b2lkIGFtYmlndWl0aWVzIHdpdGggb2ZmZXJzL3JlLW9mZmVycyBhbmQgaXRzIGZvY3VzIGhhcyBi
ZWVuIGRlZmluaW5nIGdlbmVyaWMgZnJhbWV3b3JrIGNhdGVnb3JpemluZyBTRFAgYXR0cmlidXRl
cyB3aGlsZSBwZXJmb3JtaW5nIE1lZGlhIG11bHRpcGxleGluZzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaHVzLCB0aGUgY2FzZSBvZiBpbml0
aWFsIG9mZmVyIGFwcGxpZXMgYXMgd2VsbC4gSW4gdGhhdCBjb250ZXh0LCBvbiBJbml0aWFsIE9m
ZmVyLCB0aGUgb2ZmZXJlciB3aWxsIHJlcGVhdCB0aGUgU0RQIGF0dHJpYnV0ZXMgdGhhdCBmYWxs
IHVuZGVyIElERU5USUNBTCBjYXRlZ29yeSBvbiBhbGwgdGhlIG09bGluZXMgdGhhdCBpdCBwbGFu
cyB0byBtdWx0aXBsZXguPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6cmVkIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6cmVkIj5XaGF0IGlzIHRoZSBy
ZWFzb24gZm9yIGhhdmluZyBkaWZmZXJlbnQgcnVsZXMgZm9yIElERU5USUNBTCBhbmQgVFJBTlBP
UlQ/IFdpdGggVFJBTlNQT1JUIHlvdSBjYW4gdXNlIGRpZmZlcmVudCBhdHRyaWJ1dGUgdmFsdWVz
LCBiZWNhdXNlIHRoZSDigJxzb2Z0d2FyZSB3aWxsIHBpY2sgdGhlDQogY29ycmVjdCB2YWx1ZeKA
nS4gV2h5IG5vdCB1c2UgdGhlIHNvZnR3YXJlLW11c3QtcGljayBydWxlIGFsc28gZm9yIElERU5U
SUNBTD8gPG86cD4NCjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6cmVkIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFzIGZhciBhcyB3aGF0IGhhcHBlbnMg
aW4gdGhlIHN1YnNlcXVlbnQgT2ZmZXIvQW5zd2VycyBvbmNlIEJVTkRMRSBhZGRyZXNzIGdldHMg
c2VsZWN0ZWQgaXMgdmVyeSBCVU5ETEUgc2VtYW50aWMgc3BlY2lmaWMgYW5kIGl0cyB0b3RhbGx5
IGZpbmUgdG8gc2F5IHRoYXQgJnF1b3Q7dGhlIGF0dHJpYnV0ZXMgdW5kZXIgSURFTlRJQ0FMICZh
bXA7IFRSQU5TUE9SVCBjYXRlZ29yaWVzIG5lZWRzIHRvIGJlIGluY2x1ZGVkIG9ubHkNCiBpbiB0
aGUgbS1saW5lICZuYnNwO3RoYXQgc2VsZWN0ZWQgZm9yIEJVTkRMaW5nIG9uY2UgQlVORExFIGlz
IHN1Y2Nlc3NmdWxseSBuZWdvdGlhdGVkJnF1b3Q7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpyZWQiPkdv
b2QuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOnJlZCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOnJlZCI+UmVnYXJkcyw8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
cmVkIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6cmVkIj5DaHJpc3RlcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDtt
YXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOnJlZCI+Ljwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOnJlZCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6cmVkIj5N
eSBwb2ludCBpcyB0aGF0IHdoYXQgaXMgaW1wb3J0YW50IGlzIHRoYXQgZHJhZnQtbXV4LWF0dHJp
YnV0ZXMgZGVmaW5lcyB3aGljaCBjYXRlZ29yaWVzIGFwcGx5IHRvIGFsbCBtLQ0KIGxpbmVzIGlu
IHRoZSBCVU5ETEUgZ3JvdXAg4oCTIE5PVCB3aGV0aGVyIHRoZSBhdHRyaWJ1dGUgdmFsdWVzIGlu
IHRoZSBTRFAgbmVlZCB0byBpZGVudGljYWwsIGFzIHRoZSB2YWx1ZXMgYXJlIHRha2VuIGZyb20g
dGhlIEJVTkRMRSBtLSBsaW5lLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOnJlZCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6cmVk
Ij5SZWdhcmRzLDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOnJlZCI+Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xv
cjojODg4ODg4Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjpyZWQiPkNocmlzdGVyPC9zcGFuPjxzcGFuIHN0eWxlPSJj
b2xvcjojODg4ODg4Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojODg4ODg4Ij4mbmJzcDs8L3NwYW4+PHNwYW4gc3R5
bGU9ImNvbG9yOiM4ODg4ODgiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiM4ODg4ODgiPiZuYnNwOzwvc3Bhbj48c3Bh
biBzdHlsZT0iY29sb3I6Izg4ODg4OCI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0ND
Q0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJn
aW4tdG9wOjUuMHB0O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjojMUY0OTdEIj4mZ3Q7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWYiPjQuNS4mbmJzcDsNCiBDYXRlZ29yeTogVFJBTlNQT1JUPC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Jm5i
c3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7Jm5ic3A7DQogVGhlIGF0dHJpYnV0ZXMgaW4gdGhl
IFRSQU5TUE9SVCBjYXRlZ29yeSBjYW4gYmUgc2V0IG5vcm1hbGx5IGZvcjwvc3Bhbj48bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjojMUY0OTdEIj4mZ3Q7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWYiPiZuYnNwOyZuYnNwOw0KIG11bHRpcGxlIGl0ZW1zIGluIGEgbXVsdGlwbGV4ZWQgZ3JvdXAg
YnV0IHRoZSBzb2Z0d2FyZSBNVVNUIHBpY2sgdGhlPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMx
RjQ5N0QiPiZndDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7Jm5i
c3A7DQogb25lIHRoYXQncyBhc3NvY2lhdGVkIHdpdGggdGhlICZxdW90O209JnF1b3Q7IGxpbmUg
d2hvc2UgaW5mb3JtYXRpb24gaXMgdXNlZDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdE
Ij4mZ3Q7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyZuYnNwOw0K
IGZvciBzZXR0aW5nIHVwIHRoZSB1bmRlcmx5aW5nIHRyYW5zcG9ydC48L3NwYW4+PG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6IzFGNDk3RCI+Jmd0Ozwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
Ij4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jmd0Ow0KPC9zcGFuPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPlRoaXMgYWxyZWFkeSBzZWVtcyBhbGlnbmVkIHdp
dGggd2hhdCB5b3Ugc3VnZ2VzdCBiZWxvdy48L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3
RCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPlllcy48L3NwYW4+PG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMx
RjQ5N0QiPlJlZ2FyZHMsPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5DaHJpc3Rlcjwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOzwvc3Bhbj48
bzpwPjwvbzpwPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
IGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4w
cHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48Yj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZiI+IG1tdXNpYw0KIFs8YSBocmVmPSJtYWlsdG86bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmci
IHRhcmdldD0iX2JsYW5rIj5tYWlsdG86bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmc8L2E+XQ0KPGI+
T24gQmVoYWxmIE9mIDwvYj5DaHJpc3RlciBIb2xtYmVyZzxicj4NCjxiPlNlbnQ6PC9iPiBkZW4g
NCBva3RvYmVyIDIwMTYgMTI6NDQ8YnI+DQo8Yj5Ubzo8L2I+IDxhIGhyZWY9Im1haWx0bzptbXVz
aWNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5tbXVzaWNAaWV0Zi5vcmc8L2E+PGJyPg0KPGI+
Q2M6PC9iPiA8YSBocmVmPSJtYWlsdG86c25hbmRha3VAY2lzY28uY29tIiB0YXJnZXQ9Il9ibGFu
ayI+c25hbmRha3VAY2lzY28uY29tPC9hPjxicj4NCjxiPlN1YmplY3Q6PC9iPiBbTU1VU0lDXSBk
cmFmdC1pZXRmLW1tdXNpYy1zZHAtbXV4LWF0dHJpYnV0ZXM6IERvIHdlIG5lZWQgdG8gbWFuZGF0
ZSBpZGVudGljYWwgU0RQIGF0dHJpYnV0ZSB2YWx1ZXM/PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMi
PiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkhpLDwvc3Bhbj48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5CYXNlZCBvbiBFa3LigJlzIHJldmll
dyBvZiBCVU5ETEUsIGl0IGhhcyBiZWVuIHN1Z2dlc3RlZCB0aGF0IHRoZSB0ZXh0IHNob3VsZCBu
b3QgZm9jdXMgc28NCiBtdWNoIG9uIHdoZXRoZXIgdGhlIGJ1bmRsZWQgbS0gbGluZSBhZGRyZXNz
ZXMgYXJlIOKAnHNoYXJlZOKAnSBvciDigJx1bmlxdWXigJ0uIFRoZSBpbXBvcnRhbnQgdGhpbmcg
aXMgdGhhdCB0aGUgQlVORExFIG0tIGxpbmUgc3BlY2lmaWVzIHRoZSBhZGRyZXNzIGZvciB0aGUg
YnVuZGxlIGdyb3VwLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFj
ayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+SSB3b25kZXIgaWYgdGhlIHNhbWUgdGhpbmcgYXBw
bGllcyBhbHNvIHRvIFNEUCBhdHRyaWJ1dGVzIChyZWFkOiZuYnNwO2RyYWZ0LWlldGYtbW11c2lj
LXNkcC1tdXgtYXR0cmlidXRlcyk6IEUuZy4sIHdoYXQgaXMNCiBpbXBvcnRhbnQgaXMgd2hldGhl
ciBhbiBhdHRyaWJ1dGUgcHJvcGVydHkgaXMgYXBwbGllZCB0byBhbGwgYnVuZGxlZCBtLSBsaW5l
cyBvciBub3QgKGJhc2VkIG9uIHRoZSBtdXggY2F0ZWdvcnkpIOKAkyBub3Qgd2hldGhlciB0aGUg
U0RQIGF0dHJpYnV0ZSB2YWx1ZXMgbXVzdCBiZSBpZGVudGljYWwgaW4gZGlmZmVyZW50IG0tIGxp
bmVzLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBw
dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkNvbW1lbnRzPzwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNw
YW4gbGFuZz0iRU4tVVMiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPlJlZ2FyZHMsPC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5n
PSJFTi1VUyI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Q2hyaXN0ZXI8L3NwYW4+PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+
PGJyPg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+
DQptbXVzaWMgbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOm1tdXNpY0BpZXRmLm9y
ZyIgdGFyZ2V0PSJfYmxhbmsiPm1tdXNpY0BpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYyIgdGFyZ2V0PSJfYmxhbmsi
Pmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljPC9hPjxvOnA+PC9v
OnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Js
b2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_7594FB04B1934943A5C02806D1A2204B4BD1C225ESESSMB209erics_--


From nobody Wed Oct  5 12:57:18 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 010DB12987D for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 12:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 CHhakmVM1ltG for <mmusic@ietfa.amsl.com>; Wed,  5 Oct 2016 12:57:14 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (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 03A5B129455 for <mmusic@ietf.org>; Wed,  5 Oct 2016 12:57:14 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id t193so91442803ywc.2 for <mmusic@ietf.org>; Wed, 05 Oct 2016 12:57:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QfyIjz2rV6SPgCov1vywm/VwtjVNtienpqsUg0+BX4c=; b=p9B4MW3IWWcXDkg+x8pWDvXUcv3Oo6Wi35+tlGLRU6Cc4lW3prCXWVSkNPbgKl+Imc pmDSz8zWGC2BGcM1YBh66T/PkX9dwF7nZPiw2T3H9SV1g8LM4QtUNltUMjs1ddpueDJn GQlA/s0ykA1h554OsbqJ8mFJwplM2ASrJfAOxoyVSZNQajcfvr8Psy2H/dMe4S2L1HFL g3MZH8TIL6vt8X5f1b/mm+ng8D77EvMnEd2DRSoR9PRFxWxFH47s+vU9xlY6mbjRhr/Z 6f35MGhKifxrml5vCctfMT74O7sjei5Fp8yzjK2YwrVqxD4w/cq5V5JKmQ2UjwNuHum2 ZNEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QfyIjz2rV6SPgCov1vywm/VwtjVNtienpqsUg0+BX4c=; b=icSL0JvwY1E1BRo4lQJGY/MT0WLBde2AJclUqZEurXBERijmDTUBKo0LtpVRFNwVuP Q8JhDW9nG1ygrfOUT8tpoljyKE6/tb0EdDppkOOEC7Yrkb8Y0PQQzobG3LqR8r603wHN I4HGC7gsrTFUtl82pDkTzQRMawRleHFvK6Y+09j/3qO1PSA0njkKeOjv8i60ReczJF4o Ytr/pvC6PVzJuLoxZ09TGJQLhlRm6T3DBWir82L4nkS30qU/TmOM2gGVhDvzkeCod6YL 01NUFqn8eU2F3piS2EUsp//ObTX1Kh1NZGEuA6u0U8eqlSLD57PpXx8u+JBvmdS3hZf4 89CQ==
X-Gm-Message-State: AA6/9RnnxrWxr9eBWArJYvXeTft0PSc9mAfFig93LQoCrY0GKC3AgGxdM0nD93Ho/e/6KNFL83EhdXSlDcDssw==
X-Received: by 10.37.86.87 with SMTP id k84mr7303450ybb.37.1475697433198; Wed, 05 Oct 2016 12:57:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.158.73 with HTTP; Wed, 5 Oct 2016 12:57:12 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD1C225@ESESSMB209.ericsson.se>
References: <D41963FD.1059F%christer.holmberg@ericsson.com> <AM5PR0701MB25770AB3719E8C10A6C040058DC40@AM5PR0701MB2577.eurprd07.prod.outlook.com> <7594FB04B1934943A5C02806D1A2204B4BD1BCF8@ESESSMB209.ericsson.se> <CAMRcRGQp5u_dP5L++yHu4NtfPWu+wc=v=0Xec+4WeAUw=jZWYQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1C066@ESESSMB209.ericsson.se> <CAMRcRGTZumBNmKo3tVCjH_fSVm2i_UfiPRRuhbUZM9Q8-hBDAA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1C225@ESESSMB209.ericsson.se>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Wed, 5 Oct 2016 12:57:12 -0700
Message-ID: <CAMRcRGTJXgq94Z4YvrfXTVA4TNJO82k_9VFC_kByAkOfUHNOWA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a114258564d46f5053e2395c8
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/GZAPOv4JGOEtnSLS3zUG2Yx-K90>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "snandaku@cisco.com" <snandaku@cisco.com>
Subject: Re: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2016 19:57:17 -0000

--001a114258564d46f5053e2395c8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi ,


On Wed, Oct 5, 2016 at 12:33 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> Hi,
>
> >You mean this might impact how the IDENTICAL and TRANSPORT categories
> should be >defined in -mux-attributes? That would be a pretty fundamental
> change.
>
>
>
> It=E2=80=99s not related to the definition of IDENTICAL and TRANSPORT as =
such. It
> is more related to mandating the same attribute values in all m- lines, a=
s
> at the end of the day only the attribute values in the BUNDLE m- line
> matters.
>
> >4.3.  Category: IDENTICAL
>
> >
>
> >   The attributes and their associated values (if any) in the IDENTICAL
>
> >   category MUST be repeated across all the media descriptions under
>
> >   multiplexing.
>
> >
>
> >This text could in principle be changed say that the attribute of the
> =E2=80=9Cm=3D=E2=80=9D line whose >information is used to define the mult=
iplexed group (for
> BUNDLE that is the =E2=80=9Cm=3D=E2=80=9D line >carrying the mid listed f=
irst on the
> =E2=80=9Ca=3DBUNDLE=E2=80=9D line). Would you allow =E2=80=9Cm=3D=E2=80=
=9D lines in the >multiplexed group to
> have other values of an IDENTICAL category attribute, even if the >value
> to use when multiplexed is given by the BUNDLE =E2=80=9Cm=3D=E2=80=9D lin=
e? In what way would
> >that be useful or an improvement compared to (as now) require that
> values are actually >identical when multiplexed?
>
>
>
> In fact, based on a rather recent change, BUNDLE actually says (see below=
)
> that IDENTICAL and TRANSPORT attribute are ONLY inserted in the BUNDLE m-
> line to begin with. So, we are already misaligned, as we don=E2=80=99t re=
peat them
> across all m- lines=E2=80=A6
>
>
>
> =E2=80=9CWhen an offerer associates SDP attributes with a bundled "m=3D" =
line
>
>               associated with a shared address, IDENTICAL and TRANSPORT m=
ux
>
>               category SDP attributes [I-D.ietf-mmusic-sdp-mux-attributes=
]
> are
>
>               associated with the "m=3D" line *only if the "m=3D" line is
> also*
>
> *              associated with the offerer BUNDLE-tag.  Otherwise the
> offerer MUST*
>
> *              NOT associate such SDP attributes with the "m=3D" line*.=
=E2=80=9D
>
>
>
>
>
> [suhas] - So what happens if BUNDLE-tag m=3Dline in the offer gets reject=
ed
> and say rtcp-mux was just included only on  that m=3Dline as per above te=
xt
> form BUNDLE text.  If i understand right, there is no rtcp mux for any of
> the m=3Dlines which is not the Offerer might want
>
>
>
> Note that the text only applies to the case when the m- line contains a
> shared address, i.e., it has already been accepted into the BUNDLE group.
>
>
>
> When you send the initial offer (before the BUNDLE group has been
> created), or when you want to add a new m- line to a BUNDLE group, you ha=
ve
> to include all attributes in all m- lines, using normal 3264 procedures.
> But, in that case I don=E2=80=99t think draft-mux-attributes applies to b=
egin with,
> i.e., you can include whatever attribute values, and they will be used if
> the m- line is not accepted into the BUNDLE group. draft-mux-attributes
> only applies once the BUNDLE group has been created. At least that is my
> understanding
>
>
>
> [Suhas]
>
>
>
> Meta Note:
>
> The mux draft has stayed away from offer/answer procedures to avoid
> ambiguities with offers/re-offers and its focus has been defining generic
> framework categorizing SDP attributes while performing Media multiplexing
>
>
>
> Thus, the case of initial offer applies as well. In that context, on
> Initial Offer, the offerer will repeat the SDP attributes that fall under
> IDENTICAL category on all the m=3Dlines that it plans to multiplex.
>
>
>
> What is the reason for having different rules for IDENTICAL and TRANPORT?
> With TRANSPORT you can use different attribute values, because the
> =E2=80=9Csoftware will pick the correct value=E2=80=9D. Why not use the s=
oftware-must-pick
> rule also for IDENTICAL?
>
>
>

[Suhas]

 Let's try to explain this with example attributes. a=3Drtcp-mux which is
categorized as IDENTICAL and ice-candidates which falls under TRANSPORT
category.

For ice-candidates ,the offerer in the initial offer will include different
ice-pwd, candidates lines per m=3Dline since it's not sure of the BUNDLE
negotiation. Thus once BUNDLE gets successfully negotiated , the software
picks the ones from the m=3Dline that is selected for BUNDling. OTOH, if th=
e
BUNDLE get's rejected each m=3Dline's individual ice info will be used.

For a=3Drtcp-mux,  in the initial Offer, the offerer must include it in all
the m=3Dlines (repeated) since there is no way for the software to decide t=
he
intent of the Offerer in scenarios where the BUNDLE gets rejected ( If the
offerer didn't repeat the attribute, the software cannot assume the
offerer's intention of whether to imply a=3Drtcp-mux for  the m=3Dlines or =
the
Offerer itself didn't want to perform rtcp muxing )

In summary, the categories IDENTICAL and TRANSPORT serve different semantic
categories and apply to different SDP attributes.

However, when BUNDLE is successfully negotated, the semantics from the
BUNDLE spec defines how these categories and attributes are treated and as
we discussed earlier it makes sense to include those only on the BUNDLEd
m=3Dline






>
>
> As far as what happens in the subsequent Offer/Answers once BUNDLE addres=
s
> gets selected is very BUNDLE semantic specific and its totally fine to sa=
y
> that "the attributes under IDENTICAL & TRANSPORT categories needs to be
> included only in the m-line  that selected for BUNDLing once BUNDLE is
> successfully negotiated"
>
>
>
> Good.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>
>
>
>
>
> .
>
>
>
> My point is that what is important is that draft-mux-attributes defines
> which categories apply to all m- lines in the BUNDLE group =E2=80=93 NOT =
whether
> the attribute values in the SDP need to identical, as the values are take=
n
> from the BUNDLE m- line.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>
>
>
> >4.5.  Category: TRANSPORT
>
> >
>
> >   The attributes in the TRANSPORT category can be set normally for
>
> >   multiple items in a multiplexed group but the software MUST pick the
>
> >   one that's associated with the "m=3D" line whose information is used
>
> >   for setting up the underlying transport.
>
> >
>
> > This already seems aligned with what you suggest below.
>
>
>
> Yes.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>
> *From:* mmusic [mailto:mmusic-bounces@ietf.org <mmusic-bounces@ietf.org>]=
 *On
> Behalf Of *Christer Holmberg
> *Sent:* den 4 oktober 2016 12:44
> *To:* mmusic@ietf.org
> *Cc:* snandaku@cisco.com
> *Subject:* [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to
> mandate identical SDP attribute values?
>
>
>
> Hi,
>
>
>
> Based on Ekr=E2=80=99s review of BUNDLE, it has been suggested that the t=
ext
> should not focus so much on whether the bundled m- line addresses are
> =E2=80=9Cshared=E2=80=9D or =E2=80=9Cunique=E2=80=9D. The important thing=
 is that the BUNDLE m- line
> specifies the address for the bundle group.
>
>
>
> I wonder if the same thing applies also to SDP attributes
> (read: draft-ietf-mmusic-sdp-mux-attributes): E.g., what is important is
> whether an attribute property is applied to all bundled m- lines or not
> (based on the mux category) =E2=80=93 not whether the SDP attribute value=
s must be
> identical in different m- lines.
>
>
>
> Comments?
>
>
>
> Regards,
>
>
>
> Christer
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>
>
>
>

--001a114258564d46f5053e2395c8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi ,<div><br><div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote">On Wed, Oct 5, 2016 at 12:33 PM, Christer Holmberg <span dir=
=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_b=
lank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-3800002242564188715WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Hi,<u></u><u></u></span></p>
<div>
<div>
<div><span class=3D"">
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Hi,</span><u></u><u></u></p>
<div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">You
 mean this might impact how the IDENTICAL and TRANSPORT categories should b=
e <span style=3D"color:#1f497d">
&gt;</span>defined in -mux-attributes? That would be a pretty fundamental c=
hange.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">It=E2=80=99s not relat=
ed to the definition of IDENTICAL and TRANSPORT as such. It is more related
 to mandating the same attribute values in all m- lines, as at the end of t=
he day only the attribute values in the BUNDLE m- line matters.</span><u></=
u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">4.3.=C2=A0
 Category: IDENTICAL</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 The attributes and their associated values (if any) in the IDENTICAL</span=
><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 category MUST be repeated across all the media descriptions under</span><u=
></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 multiplexing.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">This
 text could in principle be changed say that the attribute of the =E2=80=9C=
m=3D=E2=80=9D line whose
<span style=3D"color:#1f497d">&gt;i</span>nformation is used to define the =
multiplexed group (for BUNDLE that is the =E2=80=9Cm=3D=E2=80=9D line
<span style=3D"color:#1f497d">&gt;</span>carrying the mid listed first on t=
he =E2=80=9Ca=3DBUNDLE=E2=80=9D line). Would you allow =E2=80=9Cm=3D=E2=80=
=9D lines in the
<span style=3D"color:#1f497d">&gt;</span>multiplexed group to have other va=
lues of an IDENTICAL category attribute, even if the
<span style=3D"color:#1f497d">&gt;</span>value to use when multiplexed is g=
iven by the BUNDLE =E2=80=9Cm=3D=E2=80=9D line? In what way would
<span style=3D"color:#1f497d">&gt;</span>that be useful or an improvement c=
ompared to (as now) require that values are actually
<span style=3D"color:#1f497d">&gt;i</span>dentical when multiplexed?</span>=
<u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">In fact, based on a ra=
ther recent change, BUNDLE actually says (see below) that IDENTICAL
 and TRANSPORT attribute are ONLY inserted in the BUNDLE m- line to begin w=
ith. So, we are already misaligned, as we don=E2=80=99t repeat them across =
all m- lines=E2=80=A6</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt">
<span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,sans-serif;color:#1f497d">=E2=80=9CWhen an offerer associates SDP attri=
butes with a bundled &quot;m=3D&quot; line</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 associated with a share=
d address, IDENTICAL and TRANSPORT mux</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 category SDP attributes=
 [I-D.ietf-mmusic-sdp-mux-<wbr>attributes] are</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 associated with the &qu=
ot;m=3D&quot; line
<b>only if the &quot;m=3D&quot; line is also</b></span><u></u><u></u></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 associated with the =
offerer BUNDLE-tag.=C2=A0 Otherwise the offerer MUST</span></b><u></u><u></=
u></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0 =C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NOT associate such S=
DP attributes with the &quot;m=3D&quot; line</span></b><span lang=3D"EN-US"=
 style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color=
:#1f497d">.=E2=80=9D</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[suhas] - So what happens if BUNDLE-tag m=3Dline in =
the offer gets rejected and say rtcp-mux was just included only on =C2=A0th=
at m=3Dline as per above text form BUNDLE text.=C2=A0 If i understand
 right, there is no rtcp mux for any of the m=3Dlines which is not the Offe=
rer might want=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:red">Note that=
 the text only applies to the case when the m- line contains a shared addre=
ss, i.e., it has already been accepted into the BUNDLE
 group.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">When you send the initial offer (before t=
he BUNDLE group has been created), or when you want to add a new
 m- line to a BUNDLE group, you have to include all attributes in all m- li=
nes, using normal 3264 procedures. But, in that case I don=E2=80=99t think =
draft-mux-attributes applies to begin with, i.e., you can include whatever =
attribute values, and they will be used
 if the m- line is not accepted into the BUNDLE group. draft-mux-attributes=
 only applies once the BUNDLE group has been created. At least that is my u=
nderstanding</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Suhas]=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Meta Note:=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The mux draft has stayed away from offer/answer proc=
edures to avoid ambiguities with offers/re-offers and its focus has been de=
fining generic framework categorizing SDP attributes while performing Media=
 multiplexing<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"">
<p class=3D"MsoNormal">Thus, the case of initial offer applies as well. In =
that context, on Initial Offer, the offerer will repeat the SDP attributes =
that fall under IDENTICAL category on all the m=3Dlines that it plans to mu=
ltiplex.<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>=C2=A0<u></u></span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,sans-serif;color:red">What is the reason for having diff=
erent rules for IDENTICAL and TRANPORT? With TRANSPORT you can use differen=
t attribute values, because the =E2=80=9Csoftware will pick the
 correct value=E2=80=9D. Why not use the software-must-pick rule also for I=
DENTICAL? <u></u>
<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>=C2=A0</span></p></div></div></div=
></div></div></div></blockquote><div><br></div><div>[Suhas]</div><div><br><=
/div><div>=C2=A0Let&#39;s try to explain this with example attributes. a=3D=
rtcp-mux which is categorized as IDENTICAL and ice-candidates which falls u=
nder TRANSPORT category.</div><div><br></div><div>For ice-candidates ,the o=
fferer in the initial offer will include different ice-pwd, candidates line=
s per m=3Dline since it&#39;s not sure of the BUNDLE negotiation. Thus once=
 BUNDLE gets successfully negotiated , the software picks the ones from the=
 m=3Dline that is selected for BUNDling. OTOH, if the BUNDLE get&#39;s reje=
cted each m=3Dline&#39;s individual ice info will be used.</div><div><br></=
div><div>For a=3Drtcp-mux, =C2=A0in the initial Offer, the offerer must inc=
lude it in all the m=3Dlines (repeated) since there is no way for the softw=
are to decide the intent of the Offerer in scenarios where the BUNDLE gets =
rejected ( If the offerer didn&#39;t repeat the attribute, the software can=
not assume the offerer&#39;s intention of whether to imply a=3Drtcp-mux for=
 =C2=A0the m=3Dlines or the Offerer itself didn&#39;t want to perform rtcp =
muxing )</div><div><br></div><div>In summary, the categories IDENTICAL and =
TRANSPORT serve different semantic categories and apply to different SDP at=
tributes.</div><div><br></div><div>However, when BUNDLE is successfully neg=
otated, the semantics from the BUNDLE spec defines how these categories and=
 attributes are treated and as we discussed earlier it makes sense to inclu=
de those only on the BUNDLEd m=3Dline</div><div><br></div><div><br></div><d=
iv><br></div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple"><div class=3D"m_-380000=
2242564188715WordSection1"><div><div><div><div><p class=3D"MsoNormal"><span=
 style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color=
:red"><u></u></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">As far as what happens in the subsequent Offer/Answe=
rs once BUNDLE address gets selected is very BUNDLE semantic specific and i=
ts totally fine to say that &quot;the attributes under IDENTICAL &amp; TRAN=
SPORT categories needs to be included only
 in the m-line =C2=A0that selected for BUNDLing once BUNDLE is successfully=
 negotiated&quot;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Good.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Regards,<span class=3D"HOEnZb"><font colo=
r=3D"#888888"><u></u><u></u></font></span></span></p><span class=3D"HOEnZb"=
><font color=3D"#888888">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Christer<u></u><u></u></span></p>
</font></span></div><div><div class=3D"h5">
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">My point is that what is important is tha=
t draft-mux-attributes defines which categories apply to all m-
 lines in the BUNDLE group =E2=80=93 NOT whether the attribute values in th=
e SDP need to identical, as the values are taken from the BUNDLE m- line.</=
span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Regards,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">=C2=A0</span><span style=3D"color:#888888=
"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Christer</span><span style=3D"color:#8888=
88"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#888888">=C2=A0</span><span style=3D"color:#88=
8888"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#888888">=C2=A0</span><span style=3D"color:#88=
8888"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">4.5.=C2=A0
 Category: TRANSPORT</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 The attributes in the TRANSPORT category can be set normally for</span><u>=
</u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 multiple items in a multiplexed group but the software MUST pick the</span=
><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 one that&#39;s associated with the &quot;m=3D&quot; line whose information=
 is used</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0=C2=A0
 for setting up the underlying transport.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;</span><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-s=
erif">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">&gt;
</span><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif">This already seems aligned with what you suggest bel=
ow.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">Yes.</span><u></u><u><=
/u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">Regards,</span><u></u>=
<u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">Christer</span><u></u>=
<u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:#1f497d">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif">=C2=A0</span><u></u><u></u></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span lang=3D"EN-=
US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"> =
mmusic
 [<a href=3D"mailto:mmusic-bounces@ietf.org" target=3D"_blank">mailto:mmusi=
c-bounces@ietf.<wbr>org</a>]
<b>On Behalf Of </b>Christer Holmberg<br>
<b>Sent:</b> den 4 oktober 2016 12:44<br>
<b>To:</b> <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf=
.org</a><br>
<b>Cc:</b> <a href=3D"mailto:snandaku@cisco.com" target=3D"_blank">snandaku=
@cisco.com</a><br>
<b>Subject:</b> [MMUSIC] draft-ietf-mmusic-sdp-mux-<wbr>attributes: Do we n=
eed to mandate identical SDP attribute values?</span><u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black">Hi,</span><u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black">=C2=A0</span><u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black">Based on Ekr=E2=80=99s r=
eview of BUNDLE, it has been suggested that the text should not focus so
 much on whether the bundled m- line addresses are =E2=80=9Cshared=E2=80=9D=
 or =E2=80=9Cunique=E2=80=9D. The important thing is that the BUNDLE m- lin=
e specifies the address for the bundle group.</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,sans-serif;color:black">=C2=A0</span><u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">I wonder if the same thing applies also to SDP attrib=
utes (read:=C2=A0draft-ietf-mmusic-sdp-<wbr>mux-attributes): E.g., what is
 important is whether an attribute property is applied to all bundled m- li=
nes or not (based on the mux category) =E2=80=93 not whether the SDP attrib=
ute values must be identical in different m- lines.</span><u></u><u></u></p=
>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Comments?</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Regards,</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Christer</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div></div></div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div>

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

--001a114258564d46f5053e2395c8--


From nobody Thu Oct  6 02:35:51 2016
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 AAA13129832 for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 02:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 N8V-05mnAVfl for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 02:35:48 -0700 (PDT)
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 F0CDE12955E for <mmusic@ietf.org>; Thu,  6 Oct 2016 02:35:47 -0700 (PDT)
X-AuditID: c1b4fb3a-aa3ff7000000099a-9b-57f61af1f196
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by  (Symantec Mail Security) with SMTP id 68.DE.02458.1FA16F75; Thu,  6 Oct 2016 11:35:46 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0319.002; Thu, 6 Oct 2016 11:35:44 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Thread-Topic: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
Thread-Index: AQHSHiwofDubrkbtCEu3VfmkQRPgmqCaG2pAgAAN1UD//+oUAIAAIpcg///kRYCAACZH8P//5v0AACMX/wA=
Date: Thu, 6 Oct 2016 09:35:44 +0000
Message-ID: <D41BF5AE.108D0%christer.holmberg@ericsson.com>
References: <D41963FD.1059F%christer.holmberg@ericsson.com> <AM5PR0701MB25770AB3719E8C10A6C040058DC40@AM5PR0701MB2577.eurprd07.prod.outlook.com> <7594FB04B1934943A5C02806D1A2204B4BD1BCF8@ESESSMB209.ericsson.se> <CAMRcRGQp5u_dP5L++yHu4NtfPWu+wc=v=0Xec+4WeAUw=jZWYQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1C066@ESESSMB209.ericsson.se> <CAMRcRGTZumBNmKo3tVCjH_fSVm2i_UfiPRRuhbUZM9Q8-hBDAA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1C225@ESESSMB209.ericsson.se> <CAMRcRGTJXgq94Z4YvrfXTVA4TNJO82k_9VFC_kByAkOfUHNOWA@mail.gmail.com>
In-Reply-To: <CAMRcRGTJXgq94Z4YvrfXTVA4TNJO82k_9VFC_kByAkOfUHNOWA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_D41BF5AE108D0christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKIsWRmVeSWpSXmKPExsUyM2K7ve4nqW/hBucviFtMXf6YxWLxgfus FjvndjA7MHtM+b2R1WPnrLvsHkuW/GQKYI7isklJzcksSy3St0vgyjh1ZjF7QZ9TxZYXs5gb GBdadDFyckgImEgcbDjP1MXIxSEksJ5R4sKT3WwQziJGiaaVK5m7GDk42AQsJLr/aYM0iAho SaxePJcJJMwsUCHRdkcHJCwsUCyx8MEtVoiSEonTy7dC2UkSb189ZwGxWQRUJH7c2MsOYvMK WEtMWdjKArFqM4vEpDm32UASnAKBEt3TbjGB2IwCYhLfT60Bs5kFxCVuPZnPBHG0gMSSPeeZ IWxRiZeP/4EtExXQk/j+dTZUXFHi46t9jBC9CRLfzu9hhlgsKHFy5hOWCYyis5CMnYWkbBaS Moi4gcT7c/OZIWxtiWULX0PZ+hIbv5xlnAUOCmuJc4vNkJUsYORYxShanFpcnJtuZKSXWpSZ XFycn6eXl1qyiREYmQe3/LbawXjwueMhRgEORiUe3gX2X8OFWBPLiitzDzFKcDArifB+lPwW LsSbklhZlVqUH19UmpNafIhRmoNFSZzXbOX9cCGB9MSS1OzU1ILUIpgsEwenVAOjRWbTvV0S Cz3Ef90rnb0642ugraHWlSSGxe++L5LvZ84zilAoDohvE3tw/oZw7ObX0004o+4fbbNYEjvj j2fszqkxGhI1bX9vP3huyPVb777wgvQAl0b2F/fSrv4XrbmaeW1v0eJclp1B9685fo41CLkT InX1PO+MqypXU2oVFtyXkShSLnyqxFKckWioxVxUnAgAwDpzw8gCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/GPQH5FwqXKRxMXsUbv6Ayw-8pvU>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "snandaku@cisco.com" <snandaku@cisco.com>
Subject: Re: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2016 09:35:51 -0000

--_000_D41BF5AE108D0christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

=85
[Suhas]

Meta Note:
The mux draft has stayed away from offer/answer procedures to avoid ambigui=
ties with offers/re-offers and its focus has been defining generic framewor=
k categorizing SDP attributes while performing Media multiplexing

Thus, the case of initial offer applies as well. In that context, on Initia=
l Offer, the offerer will repeat the SDP attributes that fall under IDENTIC=
AL category on all the m=3Dlines that it plans to multiplex.

What is the reason for having different rules for IDENTICAL and TRANPORT? W=
ith TRANSPORT you can use different attribute values, because the =93softwa=
re will pick the correct value=94. Why not use the software-must-pick rule =
also for IDENTICAL?


[Suhas]

 Let's try to explain this with example attributes. a=3Drtcp-mux which is c=
ategorized as IDENTICAL and ice-candidates which falls under TRANSPORT cate=
gory.

For ice-candidates ,the offerer in the initial offer will include different=
 ice-pwd, candidates lines per m=3Dline since it's not sure of the BUNDLE n=
egotiation. Thus once BUNDLE gets successfully negotiated , the software pi=
cks the ones from the m=3Dline that is selected for BUNDling. OTOH, if the =
BUNDLE get's rejected each m=3Dline's individual ice info will be used.

Correct.

For a=3Drtcp-mux,  in the initial Offer, the offerer must include it in all=
 the m=3Dlines (repeated) since there is no way for the software to decide =
the intent of the Offerer in scenarios where the BUNDLE gets rejected ( If =
the offerer didn't repeat the attribute, the software cannot assume the off=
erer's intention of whether to imply a=3Drtcp-mux for  the m=3Dlines or the=
 Offerer itself didn't want to perform rtcp muxing )

If there is no rtcp-mux attribute, and if the BUNDLE is rejected (or if an =
m- line is not accepted into the BUNDLE group), normal SDP O/A procedures a=
pply and there would be no RTCP MUX.

Anyway, even if we do mandate identical attribute values in case of IDENTIC=
AL, is draft-mux-categories clear that it applies already before a BUNDLE g=
roup has been created? I believe there were some clarification questions ab=
out that also earlier.

Regards,

Christer



--_000_D41BF5AE108D0christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <7AC2258C76F92C45A6109DF9C67732DA@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
Hi,</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
=85&nbsp;</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px; color: rgb(0, 0, 0);">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-3800002242564188715WordSection1"><span class=3D"">
<div>
<p class=3D"MsoNormal"><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Suhas]&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Meta Note:&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The mux draft has stayed away from offer/answer proc=
edures to avoid ambiguities with offers/re-offers and its focus has been de=
fining generic framework categorizing SDP attributes while performing Media=
 multiplexing<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
</span>
<div><span class=3D"">
<p class=3D"MsoNormal">Thus, the case of initial offer applies as well. In =
that context, on Initial Offer, the offerer will repeat the SDP attributes =
that fall under IDENTICAL category on all the m=3Dlines that it plans to mu=
ltiplex.<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>&nbsp;<u></u></span></p>
</span>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">What is the reason for having different r=
ules for IDENTICAL and TRANPORT? With TRANSPORT you can use different attri=
bute values, because the =93software will pick the
 correct value=94. Why not use the software-must-pick rule also for IDENTIC=
AL? <u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>&nbsp;</span></p>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>[Suhas]</div>
<div><br>
</div>
<div>&nbsp;Let's try to explain this with example attributes. a=3Drtcp-mux =
which is categorized as IDENTICAL and ice-candidates which falls under TRAN=
SPORT category.</div>
<div><br>
</div>
<div>For ice-candidates ,the offerer in the initial offer will include diff=
erent ice-pwd, candidates lines per m=3Dline since it's not sure of the BUN=
DLE negotiation. Thus once BUNDLE gets successfully negotiated , the softwa=
re picks the ones from the m=3Dline
 that is selected for BUNDling. OTOH, if the BUNDLE get's rejected each m=
=3Dline's individual ice info will be used.</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><font col=
or=3D"#ff0000">Correct.</font></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px; color: rgb(0, 0, 0);">
<div>
<div>
<div dir=3D"ltr">
<div>
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><br>
</div>
<div>For a=3Drtcp-mux, &nbsp;in the initial Offer, the offerer must include=
 it in all the m=3Dlines (repeated) since there is no way for the software =
to decide the intent of the Offerer in scenarios where the BUNDLE gets reje=
cted ( If the offerer didn't repeat the attribute,
 the software cannot assume the offerer's intention of whether to imply a=
=3Drtcp-mux for &nbsp;the m=3Dlines or the Offerer itself didn't want to pe=
rform rtcp muxing )</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><font col=
or=3D"#ff0000">If there is no rtcp-mux attribute, and if the BUNDLE is reje=
cted (or if an m- line is not accepted into the BUNDLE group), normal SDP O=
/A procedures apply and there would
 be no RTCP MUX.</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><font col=
or=3D"#ff0000"><br>
</font></div>
<div><span style=3D"font-family: Calibri, sans-serif; font-size: 14px; colo=
r: rgb(255, 0, 0);">Anyway, even if we do mandate identical attribute value=
s in case of IDENTICAL, is&nbsp;</span><font color=3D"#ff0000" face=3D"Cali=
bri,sans-serif">draft-mux-categories clear
 that it applies already before a BUNDLE group has been created? I&nbsp;bel=
ieve there were some clarification questions about that also earlier.</font=
></div>
<div><font color=3D"#ff0000" face=3D"Calibri,sans-serif"><br>
</font></div>
<div><font color=3D"#ff0000" face=3D"Calibri,sans-serif">Regards,</font></d=
iv>
<div><br>
</div>
<div><font color=3D"#ff0000" face=3D"Calibri,sans-serif">Christer</font></d=
iv>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px;">
<div>
<div>
<div dir=3D"ltr">
<div>
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><br>
</div>
<div style=3D"color: rgb(0, 0, 0);"><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D41BF5AE108D0christerholmbergericssoncom_--


From nobody Thu Oct  6 04:29:30 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28197129607 for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 04:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 mJ0vut8hce04 for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 04:29:26 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (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 5137D129606 for <mmusic@ietf.org>; Thu,  6 Oct 2016 04:29:26 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id i129so10947601ywb.0 for <mmusic@ietf.org>; Thu, 06 Oct 2016 04:29:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=S/fYv+1CuW2k+OLVy9NIJm10yFoLaCvgCaEQZE5Hdtk=; b=bPLc8xbhQTD3q5y/XA8/l3Gjj0IZPkZvg8PteHQn7FzlIrMACxrYHOqJm240Uqvxew 5/z8hY3iZ2PSilGGRX5BjpHtK13OgXcbYa691YuVRTjcAFKGRIXX5O+5n4wFJjW+yV/f BO8k/Nl5HBsuKPokRMtnCcCdTRQm5wCFzT0rH9PsAP82LQEP89mIzlz5uRwmdkgEcLm7 AD6uCwuLYsgLko0Hi4/kHHp1IkbeaG75TZ8/dNDFfRq4NXcLDtfDdyiwtNaaT0qtTTPb 2YEGX+KFU9Xd1myafzKzkb2EpLl106BX3TwgQDOrzhDemH510CmYrVtAfqjKmgbUFd6E oQpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=S/fYv+1CuW2k+OLVy9NIJm10yFoLaCvgCaEQZE5Hdtk=; b=KzHalpm6dGbU/cM5rkN8yVC6BISkD6H2AlNB/f+GclvaC8GB43odoev51ntgj7xU3V 54dq9cVd6tdDy+5XR75H8UGJnkpBIfAEEyFkyVcBUgy5rkQb+7ZgInrEP0DVbwfMGEu0 Twr/v9TXBJkrVLefRIYwmP9M0tOfKqbZMc5aSNPnyzkvzxC8Jb6i6JburftBZh3JLRIg LYN2xFbrL0cDxUPRHTvh6f2qZQq2H7xAlK6CLjGVszJvBOxSpt2dTsUn5MX/GE06JmMD oWg7XPNjcELk2pPXYdzBKIr9eUajvHUWoyQmVYGeR+C8IWh6rVv4joL96vrUtOWBfu/8 KlTw==
X-Gm-Message-State: AA6/9RlhtlcnOhelhvSSCxAsNc0/1yIHXA6UQXNxihBQT9UqNHSirsDI6o1pGrgXSnLfbHJwLEM97tZDV/3ZUQ==
X-Received: by 10.129.78.15 with SMTP id c15mr10723887ywb.107.1475753365508; Thu, 06 Oct 2016 04:29:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.158.73 with HTTP; Thu, 6 Oct 2016 04:29:24 -0700 (PDT)
In-Reply-To: <D41BF5AE.108D0%christer.holmberg@ericsson.com>
References: <D41963FD.1059F%christer.holmberg@ericsson.com> <AM5PR0701MB25770AB3719E8C10A6C040058DC40@AM5PR0701MB2577.eurprd07.prod.outlook.com> <7594FB04B1934943A5C02806D1A2204B4BD1BCF8@ESESSMB209.ericsson.se> <CAMRcRGQp5u_dP5L++yHu4NtfPWu+wc=v=0Xec+4WeAUw=jZWYQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1C066@ESESSMB209.ericsson.se> <CAMRcRGTZumBNmKo3tVCjH_fSVm2i_UfiPRRuhbUZM9Q8-hBDAA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1C225@ESESSMB209.ericsson.se> <CAMRcRGTJXgq94Z4YvrfXTVA4TNJO82k_9VFC_kByAkOfUHNOWA@mail.gmail.com> <D41BF5AE.108D0%christer.holmberg@ericsson.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Thu, 6 Oct 2016 04:29:24 -0700
Message-ID: <CAMRcRGTiu5u0LCSBeScBdCJGg3PRUtcogounaPHNKtZ8ienOWg@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a114dae52209f22053e309b68
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/YDlo4Uw69NhSfFXe4YXq7j5CeOM>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "snandaku@cisco.com" <snandaku@cisco.com>
Subject: Re: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2016 11:29:28 -0000

--001a114dae52209f22053e309b68
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,


On Thu, Oct 6, 2016 at 2:35 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> =E2=80=A6
>
>> [Suhas]
>>
>>
>>
>> Meta Note:
>>
>> The mux draft has stayed away from offer/answer procedures to avoid
>> ambiguities with offers/re-offers and its focus has been defining generi=
c
>> framework categorizing SDP attributes while performing Media multiplexin=
g
>>
>>
>>
>> Thus, the case of initial offer applies as well. In that context, on
>> Initial Offer, the offerer will repeat the SDP attributes that fall unde=
r
>> IDENTICAL category on all the m=3Dlines that it plans to multiplex.
>>
>>
>>
>> What is the reason for having different rules for IDENTICAL and TRANPORT=
?
>> With TRANSPORT you can use different attribute values, because the
>> =E2=80=9Csoftware will pick the correct value=E2=80=9D. Why not use the =
software-must-pick
>> rule also for IDENTICAL?
>>
>>
>>
>
> [Suhas]
>
>  Let's try to explain this with example attributes. a=3Drtcp-mux which is
> categorized as IDENTICAL and ice-candidates which falls under TRANSPORT
> category.
>
> For ice-candidates ,the offerer in the initial offer will include
> different ice-pwd, candidates lines per m=3Dline since it's not sure of t=
he
> BUNDLE negotiation. Thus once BUNDLE gets successfully negotiated , the
> software picks the ones from the m=3Dline that is selected for BUNDling.
> OTOH, if the BUNDLE get's rejected each m=3Dline's individual ice info wi=
ll
> be used.
>
> Correct.
>
> For a=3Drtcp-mux,  in the initial Offer, the offerer must include it in a=
ll
> the m=3Dlines (repeated) since there is no way for the software to decide=
 the
> intent of the Offerer in scenarios where the BUNDLE gets rejected ( If th=
e
> offerer didn't repeat the attribute, the software cannot assume the
> offerer's intention of whether to imply a=3Drtcp-mux for  the m=3Dlines o=
r the
> Offerer itself didn't want to perform rtcp muxing )
>
> If there is no rtcp-mux attribute, and if the BUNDLE is rejected (or if a=
n
> m- line is not accepted into the BUNDLE group), normal SDP O/A procedures
> apply and there would be no RTCP MUX.
>
> Anyway, even if we do mandate identical attribute values in case of
> IDENTICAL, is draft-mux-categories clear that it applies already before a
> BUNDLE group has been created? I believe there were some clarification
> questions about that also earlier.
>
>
[Suhas] .. I personally feel that clarification should be in the BUNDLE
spec. BUNDLE spec already has clarification on how IDENTICAL and TRANSPORT
categories are treated once shared address is selected as you pointed out
earlier (also in section 8.1).
Similarly, it needs to to address the case for before shared address
getting selected, if it is not already (I thought section 7.3 implied that
already).



> Regards,
>
> Christer
>
>
>

--001a114dae52209f22053e309b68
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Thu, Oct 6, 2016 at 2:35 AM, Christer Holmberg <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"=
_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">



<div style=3D"word-wrap:break-word">
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
Hi,</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
=E2=80=A6=C2=A0</div><span class=3D"">
<span id=3D"m_-5198766606641984430OLK_SRC_BODY_SECTION" style=3D"font-famil=
y:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0)">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-5198766606641984430m_-3800002242564188715WordSection1"><sp=
an>
<div>
<p class=3D"MsoNormal"><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Suhas]=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Meta Note:=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The mux draft has stayed away from offer/answer proc=
edures to avoid ambiguities with offers/re-offers and its focus has been de=
fining generic framework categorizing SDP attributes while performing Media=
 multiplexing<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span>
<div><span>
<p class=3D"MsoNormal">Thus, the case of initial offer applies as well. In =
that context, on Initial Offer, the offerer will repeat the SDP attributes =
that fall under IDENTICAL category on all the m=3Dlines that it plans to mu=
ltiplex.<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>=C2=A0<u></u></span></p>
</span>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">What is the reason for having different r=
ules for IDENTICAL and TRANPORT? With TRANSPORT you can use different attri=
bute values, because the =E2=80=9Csoftware will pick the
 correct value=E2=80=9D. Why not use the software-must-pick rule also for I=
DENTICAL? <u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>=C2=A0</span></p>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>[Suhas]</div>
<div><br>
</div>
<div>=C2=A0Let&#39;s try to explain this with example attributes. a=3Drtcp-=
mux which is categorized as IDENTICAL and ice-candidates which falls under =
TRANSPORT category.</div>
<div><br>
</div>
<div>For ice-candidates ,the offerer in the initial offer will include diff=
erent ice-pwd, candidates lines per m=3Dline since it&#39;s not sure of the=
 BUNDLE negotiation. Thus once BUNDLE gets successfully negotiated , the so=
ftware picks the ones from the m=3Dline
 that is selected for BUNDling. OTOH, if the BUNDLE get&#39;s rejected each=
 m=3Dline&#39;s individual ice info will be used.</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<br>
</div>
</span><div style=3D"font-family:Calibri,sans-serif;font-size:14px"><font c=
olor=3D"#ff0000">Correct.</font></div><span class=3D"">
<span id=3D"m_-5198766606641984430OLK_SRC_BODY_SECTION" style=3D"font-famil=
y:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0)">
<div>
<div>
<div dir=3D"ltr">
<div>
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><br>
</div>
<div>For a=3Drtcp-mux, =C2=A0in the initial Offer, the offerer must include=
 it in all the m=3Dlines (repeated) since there is no way for the software =
to decide the intent of the Offerer in scenarios where the BUNDLE gets reje=
cted ( If the offerer didn&#39;t repeat the attribute,
 the software cannot assume the offerer&#39;s intention of whether to imply=
 a=3Drtcp-mux for =C2=A0the m=3Dlines or the Offerer itself didn&#39;t want=
 to perform rtcp muxing )</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
</span><div style=3D"font-family:Calibri,sans-serif;font-size:14px"><font c=
olor=3D"#ff0000">If there is no rtcp-mux attribute, and if the BUNDLE is re=
jected (or if an m- line is not accepted into the BUNDLE group), normal SDP=
 O/A procedures apply and there would
 be no RTCP MUX.</font></div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px"><font color=3D=
"#ff0000"><br>
</font></div>
<div><span style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb=
(255,0,0)">Anyway, even if we do mandate identical attribute values in case=
 of IDENTICAL, is=C2=A0</span><font color=3D"#ff0000" face=3D"Calibri,sans-=
serif">draft-mux-categories clear
 that it applies already before a BUNDLE group has been created? I=C2=A0bel=
ieve there were some clarification questions about that also earlier.</font=
></div>
<div><font color=3D"#ff0000" face=3D"Calibri,sans-serif"><br></font></div><=
/div></blockquote><div><br></div><div>[Suhas] .. I personally feel that cla=
rification should be in the BUNDLE spec. BUNDLE spec already has clarificat=
ion on how IDENTICAL and TRANSPORT categories are treated once shared addre=
ss is selected as you pointed out earlier (also in section 8.1).=C2=A0</div=
><div>Similarly, it needs to to address the case for before shared address =
getting selected, if it is not already (I thought section 7.3 implied that =
already).</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div style=3D"word-wrap:break-word"><div><font color=3D"#ff0000" face=3D=
"Calibri,sans-serif">
</font></div>
<div><font color=3D"#ff0000" face=3D"Calibri,sans-serif">Regards,</font></d=
iv>
<div><br>
</div>
<div><font color=3D"#ff0000" face=3D"Calibri,sans-serif">Christer</font></d=
iv>
<span id=3D"m_-5198766606641984430OLK_SRC_BODY_SECTION" style=3D"font-famil=
y:Calibri,sans-serif;font-size:14px">
<div>
<div>
<div dir=3D"ltr">
<div>
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><br>
</div>
<div style=3D"color:rgb(0,0,0)"><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</div>

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

--001a114dae52209f22053e309b68--


From nobody Thu Oct  6 05:23:06 2016
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 D545812961B for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 05:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 8GdeT9SUP-MY for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 05:23:03 -0700 (PDT)
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 7BCD0129618 for <mmusic@ietf.org>; Thu,  6 Oct 2016 05:23:03 -0700 (PDT)
X-AuditID: c1b4fb30-f60a598000000cb2-b1-57f6422526cc
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by  (Symantec Mail Security) with SMTP id 9F.37.03250.52246F75; Thu,  6 Oct 2016 14:23:01 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0319.002; Thu, 6 Oct 2016 14:22:57 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Cullen Jennings <fluffy@iii.ca>, mmusic WG <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Cullen's non-major issues - normalization
Thread-Index: AQHSH8xebRDegdisu0K+VWhhqcNyEw==
Date: Thu, 6 Oct 2016 12:22:57 +0000
Message-ID: <D41C1CCB.10945%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <554F1022D0B43749B955020F5567EB93@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFLMWRmVeSWpSXmKPExsUyM2K7uq6q07dwg1O9lhYf1v9gtJi6/DGL A5PHkiU/mTwun//IGMAUxWWTkpqTWZZapG+XwJXx/94p1oKdzBVLZ3exNjDeZOpi5OCQEDCR eNJs18XIxSEksJ5R4n7/DZYuRk4gZxGjRO89A5AaNgELie5/2iBhEQEHidP7poGVCAtUSpy6 9ZoNIl4lsfDBZRYIW09i1aq5rCA2i4CKxO/1+xhBbF4Ba4nVjavYQWxGATGJ76fWMIHYzALi EreezAezJQQEJJbsOc8MYYtKvHz8D2yOKNDM719nQ8WVJH5suMQC0asncWPqFDYI21pi7r7H UDO1JZYtfM0MsVdQ4uTMJywTGEVmIVk3C0n7LCTts5C0z0LSvoCRdRWjaHFqcVJuupGRXmpR ZnJxcX6eXl5qySZGYIwc3PLbYAfjy+eOhxgFOBiVeHgX2H8NF2JNLCuuzD3EKMHBrCTCO9nu W7gQb0piZVVqUX58UWlOavEhRmkOFiVxXrOV98OFBNITS1KzU1MLUotgskwcnFINjC4XTPke XJ+R0vHIV1X3z/ZVO2UnynWzrH+/9bv4/kd1nnrd8SauzFGB5Z4TnDUT5X3m/1MumMWhq7Te 9UuMS5geV8ezI2zfvH9cvTbd5Ne5RM8Hn7PuJW98UBUSVH1r17T04PrYmLndl684zL0j9Dgm bz+fSmfa+2keaWnfd5Z3vpDpD5L+psRSnJFoqMVcVJwIACoWlNWNAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/C1sDOq08F_JdogNzrJDHIv01bNs>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Cullen's non-major issues - normalization
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2016 12:23:05 -0000

Hi,

>>14.1 specifies uses of UTF strings that implementation need to compare.
>>Should specify normalization for this.
>
>I'll look into that.

I looked into this. As far as I understand, SDP attribute values are
case-sensitive, so is there a reason why we simply can=B9t say that when th=
e
mid is carried in an RTCP MID SDES item, or in a RTP SDES header
extension, endpoints MUST use keep the case?

Regards,

Christer


From nobody Thu Oct  6 05:49:38 2016
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 B0F701295E7 for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 05:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 HUE9fE_5fso9 for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 05:49:33 -0700 (PDT)
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 26EC4127A90 for <mmusic@ietf.org>; Thu,  6 Oct 2016 05:49:32 -0700 (PDT)
X-AuditID: c1b4fb25-15fff7000000793b-d1-57f6485a39bf
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by  (Symantec Mail Security) with SMTP id BA.99.31035.A5846F75; Thu,  6 Oct 2016 14:49:31 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0319.002; Thu, 6 Oct 2016 14:49:30 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
Thread-Index: AQHSH9ATPAZhiMqWXkq+6ZcG+jYe1Q==
Date: Thu, 6 Oct 2016 12:49:29 +0000
Message-ID: <D41C238A.1095B%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="windows-1254"
Content-ID: <C984277879F71F43823A7F568A55160A@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNLMWRmVeSWpSXmKPExsUyM2K7om60x7dwg+5+FYupyx+zWKzYcIDV gcnj7/sPTB5LlvxkCmCK4rJJSc3JLEst0rdL4MqYeX8OU8Fn9YqNT+6zNjBOUOhi5OSQEDCR 2DetmamLkYtDSGA9o8TNE3PZIJxFjBJP+m6wdDFycLAJWEh0/9MGiYsINDNKrHvdzwrSLSyQ L7Hr2yFGEFtEoEDi/6k+VpB6EQE9iYubxUDCLAIqEquOrWIHsXkFrCXWbvoDVs4oICbx/dQa JhCbWUBc4taT+UwQBwlILNlznhnCFpV4+fgf2CpRoJHfv85mBhkvIaAkMW1rGkSrgcSRczdZ IWyg8d1TmCFsbYllC18zQ6wVlDg58wnLBEaRWUi2zULSPgtJ+ywk7bOQtC9gZF3FKFqcWpyU m25krJdalJlcXJyfp5eXWrKJERglB7f8Vt3BePmN4yFGAQ5GJR7eBfZfw4VYE8uKK3MPMUpw MCuJ8E62+xYuxJuSWFmVWpQfX1Sak1p8iFGag0VJnNds5f1wIYH0xJLU7NTUgtQimCwTB6dU A6NTdEXg+8y1lde/7J/+7dfB77q/dsm2NAuuOW+/U3nP6bP28Q5Tjn98aceQuv2s1LXk7wt2 fY3aLMz9PkQlaoV/yxWu3LrtVYuUim4pyUb9in677ZLIh1MFf87uTkxjm37h5PpAkafJvVLF W9+7WQpkb7Jm37Buhmml+73HU3ky//E/u59X2haqxFKckWioxVxUnAgAtgpsxY4CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/zSWiTMnBqkZktDU_iF5efbg-MAA>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2016 12:49:37 -0000

Hi,

Magnus suggested usage of RFC 6904 for encryption of the RTP SDES header
extension for MID. I guess it would be a SHUOLD?

In addition, we would say that a corresponding level of security must be
applied to the RTP SDES header extension for MID and to the RTCP SDES MID
item.

Any opinions?

Regards,

Christer





On 07/09/16 17:36, "mmusic on behalf of Paul Kyzivat"
<mmusic-bounces@ietf.org on behalf of pkyzivat@alum.mit.edu> wrote:

>Magnus,
>
>Thanks for highlighting your main issue - leakage across layers from SDP
>to RTP. I see how that could be a different sort of vulnerability.
>Encrypting RTP headers sounds like a better answer than obfuscating
>specific ids in the SDP.
>
>	Thanks,
>	Paul
>
>On 9/7/16 7:17 AM, Magnus Westerlund wrote:
>> Den 2016-09-06 kl. 21:22, skrev Paul Kyzivat:
>>> On 9/6/16 9:43 AM, Magnus Westerlund wrote:
>>>
>>>>> Note the following text in section 14.2:
>>>>>
>>>>>     "The identification-tag MUST NOT contain any user information,
>>>>>and
>>>>> applications SHALL avoid generating
>>>>>     the identification-tag using a pattern that enables application
>>>>> identification.=B2
>>>>>
>>>>
>>>> Yes, but when it comes to profiling I think the above is to unspecific
>>>> to prevent profiling. One option is a very basic algorithm that
>>>>everyone
>>>> will implement identically. However, the ordering of the m=3D line and
>>>> their media types etc etc may still allow fingerprinting of a device.
>>>> One could define it to be cryptographically random 3 character tags.
>>>> Then it would likely be difficult to get anything from it. The issue
>>>> here is really that one moves the tags from a context where the tags
>>>>is
>>>> a minor issue, as the full SDP provides so much profiling
>>>>possibilities,
>>>> to a RTP where it can be provided to completely different set of
>>>> attackers.
>>>
>>> IMO this is becoming ridiculous. Using cryptographically random tags
>>> would be annoying to implement, and would make the SDP even harder to
>>> read.
>>>
>>> I've been annoyed at the examples using small integers because that
>>> makes them hard to read. I'd be more inclined to use mnemonics, at
>>>least
>>> for examples, if not for production code.
>>
>> The point I tried to raise above is that the text in draft is
>> insufficient to prevent information leakage. This because at least the
>> implementation for the MIDs will be detectable unless one actually
>> specify it very strictly. It might be that the possibility to identify
>> the implementation is a very  minor issue here and also something that
>> is likely leaking in so many other ways.
>>
>> The more serious issue is being able to identify specific devices based
>> on the MID values. So how many MIDs that are being used or at least
>> offered will depend on the endpoints configuration in combination with
>> the software.
>>
>>>
>>> Are we getting to the point where we need to define an SDP Obfuscator
>>> (along with a SIP Obfuscator)?
>>
>> Well, that is a separate problem from the one I am bringing up here. My
>> main concern here is that due to the RTP header extension there is
>> information that exist in SDP that are leaking to some degree to the RTP
>> layer where it becomes observable by another set of potential attackers.
>>
>> The first mechanism that can be applied which will ensure protection
>> towards third parties is to use RTP header extension encryption
>> [RFC6904]. Then this information only leaks to nodes inside the security
>> context. And they likely anyway have access to the SDP. Thus removing
>> the issue.
>>
>> From my perspective mandating the use of RFC 6904 to encrypt the MID RTP
>> header extension might be the simplest choice here and provides better
>> protection against third parties. It may not give as good protection
>> against semi trusted entities. But, they already have so much other
>> information that this doesn't matter at this point.
>>
>>>
>>> If that is what we need then I think we would be better off doing it
>>> that way than doing it piecemeal, one token at a time.
>>>
>>
>> The SDP and SIP layer issues in regards to these tracking possibilities
>> are much harder, and clearly needs a more all encompassing approach.
>> What I think is important here is the leakage to another layer. That
>> should be prevented.
>>
>> Cheers
>>
>> Magnus Westerlund
>>
>> ----------------------------------------------------------------------
>> Services, Media and Network features, Ericsson Research EAB/TXM
>> ----------------------------------------------------------------------
>> Ericsson AB                 | Phone  +46 10 7148287
>> F=E4r=F6gatan 6                 | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
>>
>>
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www.ietf.org/mailman/listinfo/mmusic


From nobody Thu Oct  6 06:39:14 2016
Return-Path: <magnus.westerlund@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 A1048129657 for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 06:39:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 kURSxd2HssqW for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 06:39:09 -0700 (PDT)
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 3CE6E129653 for <mmusic@ietf.org>; Thu,  6 Oct 2016 06:39:09 -0700 (PDT)
X-AuditID: c1b4fb3a-aa3ff7000000099a-9a-57f653fa36dd
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by  (Symantec Mail Security) with SMTP id AC.79.02458.AF356F75; Thu,  6 Oct 2016 15:39:07 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.86) with Microsoft SMTP Server id 14.3.301.0; Thu, 6 Oct 2016 15:39:05 +0200
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <D41C238A.1095B%christer.holmberg@ericsson.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com>
Date: Thu, 6 Oct 2016 15:39:05 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <D41C238A.1095B%christer.holmberg@ericsson.com>
Content-Type: text/plain; charset="windows-1254"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrJLMWRmVeSWpSXmKPExsUyM2J7iO7v4G/hBid/aVhMXf6YxWLFhgOs Dkwef99/YPJYsuQnUwBTFJdNSmpOZllqkb5dAlfG0iMT2AomCFc8+fyGtYHxPH8XIyeHhICJ xL6Z51i7GLk4hATWM0r83HIRylnGKNHU18fWxcjBISyQLzF9Sh1IXESgmVHi2vnlLCDdQgLW EpevrGMHsdkELCRu/mhkA7F5BewlDt5YzghiswioSJy+dhcsLioQI3H92SOoGkGJkzOfgM3h FLCR2HsYYg4zUO+6mUegbHmJ5q2zmSF2aUs0NHWwTmDkn4WkfRaSlllIWhYwMq9iFC1OLS7O TTcy0kstykwuLs7P08tLLdnECAzAg1t+W+1gPPjc8RCjAAejEg/vAvuv4UKsiWXFlbmHGCU4 mJVEeFmCvoUL8aYkVlalFuXHF5XmpBYfYpTmYFES5zVbeT9cSCA9sSQ1OzW1ILUIJsvEwSnV wLhSINRSiE36kYMgb5m85qfX1ul31zbW7jxiG79yAvuTp/3HZaoXrbm5r7AqXZnXPvlIzO65 VddPynwWWlzLs/bWhYQploF69+X+Tk+q1189bVtv4J91aqJVSXJelyw6xCfH/fT+voxd5vnL 7W0GVUs25tz8n3vz/c3/dtKfLv+b9bNGvlj2gIgSS3FGoqEWc1FxIgD4DPvpPAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/kSJT7qzlucyoeCSMrkXXvJoIsag>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2016 13:39:13 -0000

Den 2016-10-06 kl. 14:49, skrev Christer Holmberg:
>
> Hi,
>
> Magnus suggested usage of RFC 6904 for encryption of the RTP SDES header
> extension for MID. I guess it would be a SHUOLD?
>
> In addition, we would say that a corresponding level of security must be
> applied to the RTP SDES header extension for MID and to the RTCP SDES MID
> item.
>
> Any opinions?

I think this is fine solution to this issue. I would probably formulate 
the security considerations like this.

The identfication-tag when included in the RTP MID SDES item, 
independent of transport, RTCP SDES packet or RTP header extension, can 
expose the value to parties beyond the signaling chain. Therefore, the 
identification-tag MUST NOT contain any user related information. 
However, the implementation's method for generating identfication-tags 
combined with hardware configuration can enable fingerprinting of the 
endpoint device and thus its user. As the identification-tag is also 
used to route the media stream to the right application functionality it 
is also important that the value received is the one intended by the 
sender, thus integrity and the authenticity of the source are important 
to prevent denial of service on the application. At least to prevent 
third parties from modifying the identification-tag value.

Due to the security risks associated with the MID values in RTP and RTCP 
it is strongly RECOMMENDED that the MID SDES item is both 
confidentiality protected as well as source authenticated when 
transported in either RTCP or RTP header extensions. The security 
mechanisms used SHALL provide corresponding levels of security for both 
RTP header extensions and RTCP. Confidentiality mechanisms for RTP/RTCP 
are discussed in Options for Securing RTP Sessions [RFC7201], for 
example SRTP [RFC3711] with SRTCP encryption enabled combined with 
[RFC6904] can provide the necessary security functions.


Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Oct  6 14:39:29 2016
Return-Path: <fluffy@iii.ca>
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 6EB1B1297AA for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 14:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qPP2CK1sJdJq for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 14:39:25 -0700 (PDT)
Received: from smtp74.iad3a.emailsrvr.com (smtp74.iad3a.emailsrvr.com [173.203.187.74]) (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 26AED129477 for <mmusic@ietf.org>; Thu,  6 Oct 2016 14:39:25 -0700 (PDT)
Received: from smtp26.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp26.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 5EE35C0211 for <mmusic@ietf.org>; Thu,  6 Oct 2016 17:39:22 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp26.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 1A3F1C0087 for <mmusic@ietf.org>; Thu,  6 Oct 2016 17:39:21 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [192.168.4.100] ([UNAVAILABLE]. [128.107.241.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:465 (trex/5.7.7); Thu, 06 Oct 2016 17:39:22 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com>
Date: Thu, 6 Oct 2016 15:39:20 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca>
References: <147481162395.28315.18346373858565370012.idtracker@ietfa.amsl.com> <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com>
To: mmusic <mmusic@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3BtRd91DlLFyXhsOggddgMKyAX8>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2016 21:39:27 -0000

It would be easy to rewrite it to not change it but simply clarify that =
multiple fingerprints are allowed and provide advice about additional =
ones to provide.=20


> On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy) =
<fluffy@cisco.com> wrote:
>=20
>=20
> So I still disagree that this should update 4572 and the text for the =
interoperability issue if significantly different than what many people =
proposed on list. Can we arrange a phone call to discuss this.=20
>=20
>=20
>=20
>> On Sep 25, 2016, at 7:53 AM, internet-drafts@ietf.org wrote:
>>=20
>>=20
>> 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 of the IETF.
>>=20
>>       Title           : SDP Fingerprint Attribute Usage =
Clarifications
>>       Author          : Christer Holmberg
>> 	Filename        : draft-ietf-mmusic-4572-update-07.txt
>> 	Pages           : 8
>> 	Date            : 2016-09-25
>>=20
>> Abstract:
>>  This document updates RFC 4572 by clarifying the usage of multiple
>>  SDP 'fingerprint' attributes with a single SDP media description =
("m=3D
>>  line").  The document also updates the preferred cipher suite with a
>>  stronger cipher suite.
>>=20
>>=20
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/
>>=20
>> There's also a htmlized version available at:
>> https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07
>>=20
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-4572-update-07
>>=20
>>=20
>> 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.
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Thu Oct  6 14:53:34 2016
Return-Path: <fluffy@iii.ca>
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 0DCAD129796 for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 14:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level: 
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 4lvkPltIjccv for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 14:53:32 -0700 (PDT)
Received: from smtp146.dfw.emailsrvr.com (smtp146.dfw.emailsrvr.com [67.192.241.146]) (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 D1893129418 for <mmusic@ietf.org>; Thu,  6 Oct 2016 14:53:32 -0700 (PDT)
Received: from smtp15.relay.dfw1a.emailsrvr.com (localhost [127.0.0.1]) by smtp15.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 23705C0153; Thu,  6 Oct 2016 17:53:32 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp15.relay.dfw1a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id B1DEAC01D5;  Thu,  6 Oct 2016 17:53:31 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [192.168.4.100] ([UNAVAILABLE]. [128.107.241.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:465 (trex/5.7.7); Thu, 06 Oct 2016 17:53:32 -0400
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <D41C1CCB.10945%christer.holmberg@ericsson.com>
Date: Thu, 6 Oct 2016 15:53:30 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4528FDD-49CF-411C-A8FB-77BC753F612A@iii.ca>
References: <D41C1CCB.10945%christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/kfXHAsuB0c8aHDTuCw1J3WZ3vTI>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Cullen's non-major issues - normalization
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2016 21:53:34 -0000

> On Oct 6, 2016, at 6:22 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
>>> 14.1 specifies uses of UTF strings that implementation need to =
compare.
>>> Should specify normalization for this.
>>=20
>> I'll look into that.
>=20
> I looked into this. As far as I understand, SDP attribute values are
> case-sensitive, so is there a reason why we simply can=C4=85t say that =
when the
> mid is carried in an RTCP MID SDES item, or in a RTP SDES header
> extension, endpoints MUST use keep the case?
>=20

Oh, I think comparing UTF is bit more complicated than that if we want =
to allow for UTF outside the range of the first 128 code points.=20




From nobody Thu Oct  6 14:59:18 2016
Return-Path: <fluffy@iii.ca>
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 EDA851297C9 for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 14:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level: 
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 W7GHCf6wjLkz for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 14:59:14 -0700 (PDT)
Received: from smtp130.dfw.emailsrvr.com (smtp130.dfw.emailsrvr.com [67.192.241.130]) (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 2BE671297C6 for <mmusic@ietf.org>; Thu,  6 Oct 2016 14:59:14 -0700 (PDT)
Received: from smtp17.relay.dfw1a.emailsrvr.com (localhost [127.0.0.1]) by smtp17.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 4A408201E9; Thu,  6 Oct 2016 17:59:13 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp17.relay.dfw1a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id C19E020184;  Thu,  6 Oct 2016 17:59:12 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [192.168.4.100] ([UNAVAILABLE]. [128.107.241.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:465 (trex/5.7.7); Thu, 06 Oct 2016 17:59:13 -0400
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com>
Date: Thu, 6 Oct 2016 15:59:11 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/WIF3VZT1Z6nrEA_vxhj5m7drW6w>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2016 21:59:17 -0000

I'm not getting the problem here and mandating 6904 is not an easy thing =
to do.

I'm not getting what the issue is here. If mid are random, or are just a =
count of n'th m-line in the sdp, what is the problem with exposing them =
to people are getting the media?



> On Oct 6, 2016, at 7:39 AM, Magnus Westerlund =
<magnus.westerlund@ericsson.com> wrote:
>=20
> Den 2016-10-06 kl. 14:49, skrev Christer Holmberg:
>>=20
>> Hi,
>>=20
>> Magnus suggested usage of RFC 6904 for encryption of the RTP SDES =
header
>> extension for MID. I guess it would be a SHUOLD?
>>=20
>> In addition, we would say that a corresponding level of security must =
be
>> applied to the RTP SDES header extension for MID and to the RTCP SDES =
MID
>> item.
>>=20
>> Any opinions?
>=20
> I think this is fine solution to this issue. I would probably =
formulate the security considerations like this.
>=20
> The identfication-tag when included in the RTP MID SDES item, =
independent of transport, RTCP SDES packet or RTP header extension, can =
expose the value to parties beyond the signaling chain. Therefore, the =
identification-tag MUST NOT contain any user related information. =
However, the implementation's method for generating identfication-tags =
combined with hardware configuration can enable fingerprinting of the =
endpoint device and thus its user. As the identification-tag is also =
used to route the media stream to the right application functionality it =
is also important that the value received is the one intended by the =
sender, thus integrity and the authenticity of the source are important =
to prevent denial of service on the application. At least to prevent =
third parties from modifying the identification-tag value.
>=20
> Due to the security risks associated with the MID values in RTP and =
RTCP it is strongly RECOMMENDED that the MID SDES item is both =
confidentiality protected as well as source authenticated when =
transported in either RTCP or RTP header extensions. The security =
mechanisms used SHALL provide corresponding levels of security for both =
RTP header extensions and RTCP. Confidentiality mechanisms for RTP/RTCP =
are discussed in Options for Securing RTP Sessions [RFC7201], for =
example SRTP [RFC3711] with SRTCP encryption enabled combined with =
[RFC6904] can provide the necessary security functions.
>=20
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=C3=A4r=C3=B6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Thu Oct  6 19:56:17 2016
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 EA0BD12950E for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 19:56:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 qTe-f5B1wC88 for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 19:56:14 -0700 (PDT)
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 667F7129457 for <mmusic@ietf.org>; Thu,  6 Oct 2016 19:56:14 -0700 (PDT)
X-AuditID: c1b4fb30-f60a598000000cb2-8d-57f70eccca8f
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by  (Symantec Mail Security) with SMTP id B4.A6.03250.CCE07F75; Fri,  7 Oct 2016 04:56:12 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0319.002; Fri, 7 Oct 2016 04:55:36 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Cullen Jennings <fluffy@iii.ca>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Cullen's non-major issues - normalization
Thread-Index: AQHSH8xebRDegdisu0K+VWhhqcNyE6Cb1wYAgAB18DA=
Date: Fri, 7 Oct 2016 02:55:36 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD20AB9@ESESSMB209.ericsson.se>
References: <D41C1CCB.10945%christer.holmberg@ericsson.com>, <E4528FDD-49CF-411C-A8FB-77BC753F612A@iii.ca>
In-Reply-To: <E4528FDD-49CF-411C-A8FB-77BC753F612A@iii.ca>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BD20AB9ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmplkeLIzCtJLcpLzFFi42KZGbHdRvcM3/dwg8YluhYf1v9gtJi6/DGL A5PHkiU/mTwun//IGMAUxWWTkpqTWZZapG+XwJWxZc8j5oI+nYp/65QaGF9odTFyckgImEhc +dHA2MXIxSEksJ5RYumzQ1DOIkaJ72v+sHUxcnCwCVhIdP/TBmkQEVCWOLfjLjOIzSwgL3Fh yRomEFtYoFJiycxjLBA1VRILH1yGsq0k7n4/BlbDIqAi8X75cnaQkbwCvhILDseChIUEMiW+ fF/LCmJzApX/bp8DNp5RQEzi+ymI8cwC4hJNX1ayQtwsILFkz3lmCFtU4uXjf6wQNfkSxzu/ MoLYvAKCEidnPmGZwCg8C0n7LCRls5CUzQK6iFlAU2L9Ln2IEkWJKd0P2SFsDYnWOXPZkcUX MLKvYhQtTi1Oyk03MtJLLcpMLi7Oz9PLSy3ZxAiMnINbfhvsYHz53PEQowAHoxIP74OIb+FC rIllxZW5hxglOJiVRHgn8n4PF+JNSaysSi3Kjy8qzUktPsQozcGiJM5rtvJ+uJBAemJJanZq akFqEUyWiYNTqoExtK0uefqGL3cWPfaa3HL4npreo4vHlM6fe2KtVPn4e2PqBV4Ws4D6npTm VDsL/qveD0qzL0+qeZy1S+JE3eP85I3M9p2tiUu6s2bullc72h/y8Iy8ZtzXxw3TpZsFWr88 NBT8O59rwrnXHAlntaov+VS/rTBX42BavMkrxy/h3Xaxty4t7M+UWIozEg21mIuKEwE4NyBv mAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/klPhbwPLwueklcdGe8AkIbiPlCQ>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Cullen's non-major issues - normalization
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 02:56:16 -0000

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

SGksDQoNCldlIG9ubHkgbmVlZCB0byBjb25zaWRlciBjaGFyYWN0ZXJzIHRoYXQgYXJlIGFsbG93
ZWQgd2l0aGluIHRoZSBtaWQgYXR0cmlidXRlLCBpLmUuLCB0b2tlbi4NCg0KUmVnYXJkcywNCg0K
Q2hyaXN0ZXINCg0KDQpTZW50IGZyb20gbXkgV2luZG93cyBQaG9uZQ0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCkZyb206IEN1bGxlbiBKZW5uaW5nczxtYWlsdG86Zmx1ZmZ5QGlp
aS5jYT4NClNlbnQ6IOKAjjA3L+KAjjEwL+KAjjIwMTYgMDA6NTMNClRvOiBDaHJpc3RlciBIb2xt
YmVyZzxtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPg0KQ2M6IG1tdXNpYyBX
RzxtYWlsdG86bW11c2ljQGlldGYub3JnPg0KU3ViamVjdDogUmU6IFtNTVVTSUNdIFJldmlldyBv
ZiBkcmFmdC1pZXRmLW1tdXNpYy1zZHAtYnVuZGxlLW5lZ290aWF0aW9uLTMyIC0gQ3VsbGVuJ3Mg
bm9uLW1ham9yIGlzc3VlcyAtIG5vcm1hbGl6YXRpb24NCg0KDQo+IE9uIE9jdCA2LCAyMDE2LCBh
dCA2OjIyIEFNLCBDaHJpc3RlciBIb2xtYmVyZyA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24u
Y29tPiB3cm90ZToNCj4NCj4gSGksDQo+DQo+Pj4gMTQuMSBzcGVjaWZpZXMgdXNlcyBvZiBVVEYg
c3RyaW5ncyB0aGF0IGltcGxlbWVudGF0aW9uIG5lZWQgdG8gY29tcGFyZS4NCj4+PiBTaG91bGQg
c3BlY2lmeSBub3JtYWxpemF0aW9uIGZvciB0aGlzLg0KPj4NCj4+IEknbGwgbG9vayBpbnRvIHRo
YXQuDQo+DQo+IEkgbG9va2VkIGludG8gdGhpcy4gQXMgZmFyIGFzIEkgdW5kZXJzdGFuZCwgU0RQ
IGF0dHJpYnV0ZSB2YWx1ZXMgYXJlDQo+IGNhc2Utc2Vuc2l0aXZlLCBzbyBpcyB0aGVyZSBhIHJl
YXNvbiB3aHkgd2Ugc2ltcGx5IGNhbsSFdCBzYXkgdGhhdCB3aGVuIHRoZQ0KPiBtaWQgaXMgY2Fy
cmllZCBpbiBhbiBSVENQIE1JRCBTREVTIGl0ZW0sIG9yIGluIGEgUlRQIFNERVMgaGVhZGVyDQo+
IGV4dGVuc2lvbiwgZW5kcG9pbnRzIE1VU1QgdXNlIGtlZXAgdGhlIGNhc2U/DQo+DQoNCk9oLCBJ
IHRoaW5rIGNvbXBhcmluZyBVVEYgaXMgYml0IG1vcmUgY29tcGxpY2F0ZWQgdGhhbiB0aGF0IGlm
IHdlIHdhbnQgdG8gYWxsb3cgZm9yIFVURiBvdXRzaWRlIHRoZSByYW5nZSBvZiB0aGUgZmlyc3Qg
MTI4IGNvZGUgcG9pbnRzLg0KDQoNCg0K

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

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVu
dD0iTWljcm9zb2Z0IEV4Y2hhbmdlIFNlcnZlciI+DQo8IS0tIGNvbnZlcnRlZCBmcm9tIHRleHQg
LS0+PHN0eWxlPjwhLS0gLkVtYWlsUXVvdGUgeyBtYXJnaW4tbGVmdDogMXB0OyBwYWRkaW5nLWxl
ZnQ6IDRwdDsgYm9yZGVyLWxlZnQ6ICM4MDAwMDAgMnB4IHNvbGlkOyB9IC0tPjwvc3R5bGU+DQo8
L2hlYWQ+DQo8Ym9keT4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6Q2Fs
aWJyaSxzYW5zLXNlcmlmOyBmb250LXNpemU6MTFwdCI+SGksPGJyPg0KPGJyPg0KV2Ugb25seSBu
ZWVkIHRvIGNvbnNpZGVyIGNoYXJhY3RlcnMgdGhhdCBhcmUgYWxsb3dlZCB3aXRoaW4gdGhlIG1p
ZCBhdHRyaWJ1dGUsIGkuZS4sIHRva2VuLjxicj4NCjxicj4NClJlZ2FyZHMsPGJyPg0KPGJyPg0K
Q2hyaXN0ZXI8YnI+DQo8YnI+DQo8YnI+DQpTZW50IGZyb20gbXkgV2luZG93cyBQaG9uZTwvZGl2
Pg0KPC9kaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxocj4NCjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTpDYWxpYnJpLHNhbnMtc2VyaWY7IGZvbnQtc2l6ZToxMXB0OyBmb250LXdlaWdodDpib2xkIj5G
cm9tOg0KPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7
IGZvbnQtc2l6ZToxMXB0Ij48YSBocmVmPSJtYWlsdG86Zmx1ZmZ5QGlpaS5jYSI+Q3VsbGVuIEpl
bm5pbmdzPC9hPjwvc3Bhbj48YnI+DQo8c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaSxz
YW5zLXNlcmlmOyBmb250LXNpemU6MTFwdDsgZm9udC13ZWlnaHQ6Ym9sZCI+U2VudDoNCjwvc3Bh
bj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyBmb250LXNpemU6
MTFwdCI+4oCOMDcv4oCOMTAv4oCOMjAxNiAwMDo1Mzwvc3Bhbj48YnI+DQo8c3BhbiBzdHlsZT0i
Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyBmb250LXNpemU6MTFwdDsgZm9udC13ZWln
aHQ6Ym9sZCI+VG86DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmksc2Fu
cy1zZXJpZjsgZm9udC1zaXplOjExcHQiPjxhIGhyZWY9Im1haWx0bzpjaHJpc3Rlci5ob2xtYmVy
Z0Blcmljc3Nvbi5jb20iPkNocmlzdGVyIEhvbG1iZXJnPC9hPjwvc3Bhbj48YnI+DQo8c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyBmb250LXNpemU6MTFwdDsgZm9u
dC13ZWlnaHQ6Ym9sZCI+Q2M6DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGli
cmksc2Fucy1zZXJpZjsgZm9udC1zaXplOjExcHQiPjxhIGhyZWY9Im1haWx0bzptbXVzaWNAaWV0
Zi5vcmciPm1tdXNpYyBXRzwvYT48L3NwYW4+PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OkNhbGlicmksc2Fucy1zZXJpZjsgZm9udC1zaXplOjExcHQ7IGZvbnQtd2VpZ2h0OmJvbGQiPlN1
YmplY3Q6DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJp
ZjsgZm9udC1zaXplOjExcHQiPlJlOiBbTU1VU0lDXSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1tbXVz
aWMtc2RwLWJ1bmRsZS1uZWdvdGlhdGlvbi0zMiAtIEN1bGxlbidzIG5vbi1tYWpvciBpc3N1ZXMg
LSBub3JtYWxpemF0aW9uPC9zcGFuPjxicj4NCjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8Zm9udCBz
aXplPSIyIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwcHQ7Ij4NCjxkaXYgY2xhc3M9IlBsYWlu
VGV4dCI+PGJyPg0KJmd0OyBPbiBPY3QgNiwgMjAxNiwgYXQgNjoyMiBBTSwgQ2hyaXN0ZXIgSG9s
bWJlcmcgJmx0O2NocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSZndDsgd3JvdGU6PGJyPg0K
Jmd0OyA8YnI+DQomZ3Q7IEhpLDxicj4NCiZndDsgPGJyPg0KJmd0OyZndDsmZ3Q7IDE0LjEgc3Bl
Y2lmaWVzIHVzZXMgb2YgVVRGIHN0cmluZ3MgdGhhdCBpbXBsZW1lbnRhdGlvbiBuZWVkIHRvIGNv
bXBhcmUuPGJyPg0KJmd0OyZndDsmZ3Q7IFNob3VsZCBzcGVjaWZ5IG5vcm1hbGl6YXRpb24gZm9y
IHRoaXMuPGJyPg0KJmd0OyZndDsgPGJyPg0KJmd0OyZndDsgSSdsbCBsb29rIGludG8gdGhhdC48
YnI+DQomZ3Q7IDxicj4NCiZndDsgSSBsb29rZWQgaW50byB0aGlzLiBBcyBmYXIgYXMgSSB1bmRl
cnN0YW5kLCBTRFAgYXR0cmlidXRlIHZhbHVlcyBhcmU8YnI+DQomZ3Q7IGNhc2Utc2Vuc2l0aXZl
LCBzbyBpcyB0aGVyZSBhIHJlYXNvbiB3aHkgd2Ugc2ltcGx5IGNhbsSFdCBzYXkgdGhhdCB3aGVu
IHRoZTxicj4NCiZndDsgbWlkIGlzIGNhcnJpZWQgaW4gYW4gUlRDUCBNSUQgU0RFUyBpdGVtLCBv
ciBpbiBhIFJUUCBTREVTIGhlYWRlcjxicj4NCiZndDsgZXh0ZW5zaW9uLCBlbmRwb2ludHMgTVVT
VCB1c2Uga2VlcCB0aGUgY2FzZT88YnI+DQomZ3Q7IDxicj4NCjxicj4NCk9oLCBJIHRoaW5rIGNv
bXBhcmluZyBVVEYgaXMgYml0IG1vcmUgY29tcGxpY2F0ZWQgdGhhbiB0aGF0IGlmIHdlIHdhbnQg
dG8gYWxsb3cgZm9yIFVURiBvdXRzaWRlIHRoZSByYW5nZSBvZiB0aGUgZmlyc3QgMTI4IGNvZGUg
cG9pbnRzLg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KPC9kaXY+DQo8L3NwYW4+PC9mb250Pg0K
PC9ib2R5Pg0KPC9odG1sPg0K

--_000_7594FB04B1934943A5C02806D1A2204B4BD20AB9ESESSMB209erics_--


From nobody Thu Oct  6 23:17:57 2016
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 9B4E11294AE for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 23:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dRxsgwjBfaOD for <mmusic@ietfa.amsl.com>; Thu,  6 Oct 2016 23:17:52 -0700 (PDT)
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 88AF112942F for <mmusic@ietf.org>; Thu,  6 Oct 2016 23:17:51 -0700 (PDT)
X-AuditID: c1b4fb25-14bff7000000793b-4e-57f73e0db08c
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.183.54]) by  (Symantec Mail Security) with SMTP id 5A.F1.31035.D0E37F75; Fri,  7 Oct 2016 08:17:49 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0319.002; Fri, 7 Oct 2016 08:17:48 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@nokia.com>, "Roman Shpount" <roman@telurix.com>
Thread-Topic: [MMUSIC] WG Last Call for draft-ietf-mmusic-data-channel-sdpneg-09
Thread-Index: AQHSGYjnk/WCifl7XkC0V3AzdHM2sKCO3VmAgAAoBZCAAUMWAIAMXA6A
Date: Fri, 7 Oct 2016 06:17:47 +0000
Message-ID: <D41D19E1.109F6%christer.holmberg@ericsson.com>
References: <AM3PR07MB11887A55542865A7FB23B7E58DF00@AM3PR07MB1188.eurprd07.prod.outlook.com> <CAD5OKxv7zfVyF+Jm7x6dsr3fL6DSCg22T09xRn_NnaRModSSZQ@mail.gmail.com> <a5d6affc-1405-81e4-b00e-d59b74b13c5b@alum.mit.edu> <CAD5OKxuBTimPHQb5fvNgprpNKeqfwzj_Hzj9SUwg=t0TPshCfA@mail.gmail.com> <1947c926-247d-9857-1ded-622f10a3da65@nokia.com> <5bea2b17-ac09-f30e-0fbe-231b0101fe73@nokia.com> <CAD5OKxvyWZB8gfgPVO0VB9_4s7qxJrs_goBG0d5GY=JRro+cAg@mail.gmail.com> <a48beca0-ce43-ce30-fb01-fd6e1f0473ef@nokia.com> <CAD5OKxuSY0VP=cK=WQbZKbG8Y=wPn97kfpaW7S_t1iKnMKgJOg@mail.gmail.com> <D4119B33.10038%christer.holmberg@ericsson.com> <49717688-db0e-780f-cfc9-a9a14e6e88b2@nokia.com> <7594FB04B1934943A5C02806D1A2204B4BD072A0@ESESSMB209.ericsson.se> <2f15dae6-3742-cf11-d54c-b9ca63109611@nokia.com>
In-Reply-To: <2f15dae6-3742-cf11-d54c-b9ca63109611@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.146]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha256; boundary="B_3558677048_15399992"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrIIsWRmVeSWpSXmKPExsUyM2K7mS6v3fdwgw2/tC3OPlnBaDF1+WMW ixkXpjI7MHssWfKTyePurUtMHremFAQwR3HZpKTmZJalFunbJXBlvP5iVXCwmaXiwuSLjA2M P7YydTFyckgImEi8unmNBcQWEljPKHHukgOEvYhRYl1rfhcjBwebgIVE9z9tkLCIQIbExtOr mUHCzALqElcXB4GEhQUCJZ4v6mOBKAmSOH/uGwtIiYiAm8TlVgUQk0VAReLcPn4Qk1fAWmJq W30XIxfQmsVsEp+nH2cG6eQUsJVYeeEQ2BRGATGJ76fWgN3ILCAucevJfKh7RSQeXjzNBmGL Srx8/I8VxBYV0JP4/nU2M0RcSeLHhkssEL2VEu+udIPFeQUEJU7OfMIygVF0FpKxs5CUzUJS BhF3l/h99hg7hG0g8WfxKVYIW1viybsLULa+xJSTi5gxxa0lZvw6yAZhK0pM6X4INcdU4vXR j4wLGLlXMYoWpxYn5aYbGeulFmUmFxfn5+nlpZZsYgRG9sEtv1V3MF5+43iIUYCDUYmH90HE t3Ah1sSy4srcQ4wqQHMebVh9gVGKJS8/L1VJhHeWzfdwId6UxMqq1KL8+KLSnNTiQ4zSHCxK 4rxmK++HCwmkJ5akZqemFqQWwWSZODilGhgDL6zZ9rXM8/DRPpO0vTEh5x2tC/s8n77fEbRr 7gRdlS+uy/mlHC8csHrs+D/3bdjxdfttU7ebrZ1R+O2h4FWfg2G6wkqcmVr1xz/sqPjV9f3I wSfKfHNYuRg2cj7MPeW0v3GB9Jk6LpaNXxQPpAhtvrbOqfix+o/jFZZvX18oUxb7UqKWujdN iaU4I9FQi7moOBEAr8b1qfQCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/QCtUgKezeSHL0fFaxlCb9-pa6PU>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WG Last Call for draft-ietf-mmusic-data-channel-sdpneg-09
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 06:17:56 -0000

--B_3558677048_15399992
Content-type: multipart/alternative;
	boundary="B_3558677048_15443438"


--B_3558677048_15443438
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Hi,

>Regarding the establishment of a new SCTP association, yes, agree that the
simplest way could be to request new sctp-port values being used - provided=
 a
new SDP offer/answer exchange
>is used. Would SCTP association endpoints be allowed to autonomously estab=
lish
a new SCTP association using the old sctp-port values if the previous SCTP
association failed for any reason. So far I would assume yes.

I would assume so too.
=20
>Regarding the explicit closure of an SCTP association while keeping the DT=
LS
association - right now I also only would have the BUNDLE case in mind whic=
h you
are mentioning.
>That could indeed be a valid use case as far as I am concerned.

So,  I guess we could define usage of sctp-port with a zero value for that.

Regards,

Christer


=20
=20
On 28.09.2016 17:28, Christer Holmberg wrote:
=20
=20
>    =20
> =20
>=20
> Hi,
> =20
>=20
>>  >Thanks for further feedback.
>>  >The first bullet point of section 10.5 in draft-ietf-mmusic-sctp-sdp-1=
7
>> says:
>>  >"Unless the offerer wants to re-establish an SCTP association, the off=
erer
>> MUST associate an
>>  >SDP 'sctp-port' attribute, with a new attribute value, with the m- lin=
e..."
>>  >
>>  >Now I am not sure anymore regarding the meaning of "re-established" in=
 this
>> context.
>>  >If the previous SCTP association is closed, and if then a new SCTP
>> association is established, is the idea to distinguish between a
>> "re-establishment", where >the formerly used "sctp-port" values are re-u=
sed,
>> and a "new establishment", where new values of "sctp-port" are used?
> =20
>  I was just having a chat with Roman about that.
> =20
> In my opinion, the most simply way would be to say that whenever a new SC=
TP
> association is established, one MUST use a different sctp-port value than=
 the
> previously used =AD no matter if the previous SCTP association exists or no=
t.
> =20
> Another question is whether the closure of an SCTP association requires
> explicit signalling. In that case, perhaps using a sctp-port value of zer=
o?
> One can obviously set the m- line port to zero, which will close both the=
 DTLS
> association and the SCTP association =AD but the question is whether there =
is a
> use-case where one would only want to close the SCTP association, without
> touching the DTLS association. BUNDLE?
> =20
> Regards,
> =20
> Christer
> =20
> =20
> =20
> =20
> =20
>=20
>  Thanks again,
>  Juergen
> =20
> =20
> =20
> =20
>=20
> On 28.09.2016 15:04, Christer Holmberg wrote:
> =20
> =20
>> =20
>> =20
>>=20
>> Hi,
>> =20
>> =20
>> =20
>>=20
>> =20
>> =20
>> =20
>> =20
>>=20
>> As specified in draft-ietf-mmusic-sctp-sdp, the SCTP association and DTL=
S
>> association are handled independently of each other.
>> =20
>> =20
>> =20
>>=20
>> =20
>> =20
>> =20
>> =20
>>=20
>> And, in order to re-establish an SCTP association, an endpoint needs to
>> provide a new SDP 'sctp-port' attribute value.
>> =20
>> =20
>> =20
>>=20
>> =20
>> =20
>> =20
>> =20
>>=20
>> Regards,
>> =20
>> =20
>> =20
>>=20
>> =20
>> =20
>> =20
>> =20
>>=20
>> Christer
>> =20
>> =20
>> =20
>>=20
>> =20
>> =20
>> =20
>> =20
>>=20
>> From: mmusic <mmusic-bounces@ietf.org> on behalf of Roman Shpount
>> <roman@telurix.com>
>>  Date: Wednesday 28 September 2016 at 15:34
>>  To: Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@nokia.com>
>>  Cc: "mmusic@ietf.org" <mmusic@ietf.org>
>>  Subject: Re: [MMUSIC] WG Last Call for
>> draft-ietf-mmusic-data-channel-sdpneg-09
>> =20
>> =20
>> =20
>>=20
>> =20
>> =20
>> =20
>> =20
>> =20
>> =20
>>=20
>> Juergen,
>> =20
>> =20
>>=20
>> =20
>> =20
>> =20
>> =20
>>=20
>> This was my understanding as well but I would also like the rest of the =
group
>> to confirm.
>> =20
>> =20
>> =20
>>=20
>> =20
>> =20
>> =20
>> =20
>>=20
>> Regards,
>> =20
>> =20
>> =20
>> =20
>>=20
>>=20
>> =20
>> =20
>> =20
>> =20
>>=20
>> _____________
>>  Roman Shpount
>> =20
>> =20
>> =20
>> =20
>> =20
>> =20
>>=20
>> On Wed, Sep 28, 2016 at 7:39 AM, Juergen Stoetzer-Bradler
>> <Juergen.Stoetzer-Bradler@nokia.com> wrote:
>> =20
>>> =20
>>> =20
>>>=20
>>> Roman,
>>> =20
>>>  As per my understanding it should indeed be allowed to shutdown an SCT=
P
>>> association and then to establish a new one over the same DTLS associat=
ion.
>>> Both SCTP association endpoints would have to choose new values for the
>>> initiate tags / verification tags, such that received SCTP packets coul=
d be
>>> uniquely associated with either the previous or the new SCTP associatio=
n.
>>>  However, I am not an SCTP expert - might be good to hear additional
>>> feedback.
>>> =20
>>>  Best regards,
>>>  Juergen=20
>>> =20
>>> =20
>>> =20
>>>=20
>>> =20
>>> =20
>>> =20
>>>=20
>>> On 27.09.2016 20:19, Roman Shpount wrote:
>>> =20
>>> =20
>>>> =20
>>>> =20
>>>>=20
>>>> Juergen,=20
>>>> =20
>>>> =20
>>>>=20
>>>> =20
>>>> =20
>>>> =20
>>>> =20
>>>>=20
>>>> The proposed language looks good.
>>>> =20
>>>> =20
>>>> =20
>>>>=20
>>>> =20
>>>> =20
>>>> =20
>>>> =20
>>>>=20
>>>> After reading the multiplexing language, I have a related question: Is=
 it
>>>> allowed to tear down the SCTP association and setup a new SCTP associa=
tion
>>>> over the same DTLS association?
>>>> =20
>>>> =20
>>>> =20
>>>>=20
>>>> =20
>>>> =20
>>>> =20
>>>> =20
>>>>=20
>>>> Regards,
>>>> =20
>>>> =20
>>>> =20
>>>> =20
>>>>=20
>>>>=20
>>>> =20
>>>> =20
>>>> =20
>>>> =20
>>>>=20
>>>> _____________
>>>>  Roman Shpount
>>>> =20
>>>> =20
>>>> =20
>>>> =20
>>>> =20
>>>> =20
>>>>=20
>>>> On Tue, Sep 27, 2016 at 8:11 AM, Juergen Stoetzer-Bradler
>>>> <Juergen.Stoetzer-Bradler@nokia.com> wrote:
>>>> =20
>>>>> =20
>>>>> =20
>>>>>=20
>>>>> Roman, Paul,
>>>>> =20
>>>>>  Based on your comments I would propose to modify the text in the
>>>>> introduction and in the dcmap and dcsa multiplexing category sections=
 as
>>>>> follows.
>>>>>  I've removed all text parts, in which the "m" line proto values "SCT=
P"
>>>>> and "SCTP/DTLS" had been mentioned.
>>>>> =20
>>>>>  Are you ok with these changes?
>>>>> =20
>>>>>  Thanks again,
>>>>>  Juergen
>>>>> =20
>>>>> 1.  Introduction
>>>>> =20
>>>>> =20
>>>>> =20
>>>>>    The RTCWeb working group has defined the concept of bi-directional
>>>>> =20
>>>>>    data channels running on top of the Stream Control Transmission
>>>>> =20
>>>>>    Protocol (SCTP).  ...
>>>>> =20
>>>>>   =20
>>>>> =20
>>>>>    ...
>>>>> =20
>>>>>   =20
>>>>> =20
>>>>>    This document defines SDP offer/answer negotiation procedures to
>>>>> =20
>>>>>    establish data channels for transport of well-defined subprotocols=
,
>>>>> =20
>>>>>    to enable out-of-band negotiation.  These procedures are based on
>>>>> =20
>>>>>    generic SDP offer/answer negotiation rules for SCTP based media
>>>>> =20
>>>>>    transport as specified in [I-D.ietf-mmusic-sctp-sdp] for the SDP "=
m"
>>>>> =20
>>>>>    line proto values UDP/DTLS/SCTP and TCP/DTLS/SCTP.  In future data
>>>>> =20
>>>>>    channels could be defined over other SCTP based protocols, such as
>>>>> =20
>>>>>    SCTP over IP.  However, corresponding potential other "m" line pro=
to
>>>>> =20
>>>>>    values are not considered in this document.
>>>>> =20
>>>>> =20
>>>>> =20
>>>>>    ...
>>>>> =20
>>>>> =20
>>>>> =20
>>>>> 5.1.1.2.  dcmap Multiplexing Category
>>>>> =20
>>>>> =20
>>>>> =20
>>>>>    ...
>>>>> =20
>>>>> =20
>>>>> =20
>>>>>    As the usage of multiple SCTP associations on top of a single DTLS
>>>>> =20
>>>>>    connection is outside the scope of [I-D.ietf-mmusic-sctp-sdp], no
>>>>> =20
>>>>>    "a=3Ddcmap:" attribute multiplexing rules are specified for the
>>>>> =20
>>>>>    UDP/DTLS/SCTP and TCP/DTLS/SCTP proto values.  If future extension=
s
>>>>> =20
>>>>>    of [I-D.ietf-mmusic-sctp-sdp] define how to negotiate multiplexing=
 of
>>>>> =20
>>>>>    multiple SCTP associations on top of a single DTLS connection, or =
how
>>>>> =20
>>>>>    to add multiple SCTP associations to one BUNDLE group, then
>>>>> =20
>>>>>    multiplexing rules for the "a=3Ddcmap:" attribute need to be defined=
 as
>>>>> =20
>>>>>    well, for instance in an extension of this SDP based data channel
>>>>> =20
>>>>>    negotiation specification.
>>>>> =20
>>>>> =20
>>>>> =20
>>>>> 5.1.2.2.  dcsa Multiplexing Category
>>>>> =20
>>>>> =20
>>>>> =20
>>>>>    ...
>>>>> =20
>>>>> =20
>>>>> =20
>>>>>    As the usage of multiple SCTP associations on top of a single DTLS
>>>>> =20
>>>>>    connection is outside the scope of [I-D.ietf-mmusic-sctp-sdp], no
>>>>> =20
>>>>>    "a=3Ddcsa:" attribute multiplexing rules are specified for the
>>>>> =20
>>>>>    UDP/DTLS/SCTP and TCP/DTLS/SCTP proto values.  If future extension=
s
>>>>> =20
>>>>>    of [I-D.ietf-mmusic-sctp-sdp] define how to negotiate multiplexing=
 of
>>>>> =20
>>>>>    multiple SCTP associations on top of a single DTLS connection, or =
how
>>>>> =20
>>>>>    to add multiple SCTP associations to one BUNDLE group, then
>>>>> =20
>>>>>    multiplexing rules for the "a=3Ddcsa:" attribute need to be defined =
as
>>>>> =20
>>>>>    well, for instance in an extension of this SDP based data channel
>>>>> =20
>>>>>    negotiation specification.
>>>>> =20
>>>>> =20
>>>>> =20
>>>>>=20
>>>>> =20
>>>>> =20
>>>>> =20
>>>>>=20
>>>>> On 21.09.2016 14:17, Juergen Stoetzer-Bradler wrote:
>>>>> =20
>>>>> =20
>>>>>> =20
>>>>>> Roman, Paul,
>>>>>> =20
>>>>>>  Thanks for your comments.
>>>>>> =20
>>>>>>  The protocol stack notation "SCTP/DTLS" in the introduction was act=
ually
>>>>>> meant to refer to the "SCTP on top of DTLS" case, which is also ment=
ioned
>>>>>> in the succeeding parentheses. I fully agree that this is confusing =
and
>>>>>> would propose to remove "SCTP/DTLS" from the introduction and instea=
d to
>>>>>> just say:
>>>>>>  "The RTCWeb working group has defined the concept of bi-directional=
 data
>>>>>> channels running on top of SCTP over the Datagram Transport Layer
>>>>>> Security protocol.".
>>>>>>  Or just "... on top of SCTP over DTLS".
>>>>>> =20
>>>>>>  And indeed, as draft-ietf-mmusic-sctp-sdp doesn't contain m-line pr=
oto
>>>>>> value "SCTP/DTLS" at all anymore, I would agree to remove it from
>>>>>> sections 5.1.1.2 and 5.1.2.2.
>>>>>>  Also agree to restrict the scope of the whole document to the two
>>>>>> "UDP/DTLS/SCTP" and "TCP/DTLS/SCTP" transport stack cases and to
>>>>>> explicitly say so e.g. in the introduction. This would be inline wit=
h the
>>>>>> definition of "data channel" in the terminology section, which expli=
citly
>>>>>> refers to draft-ietf-rtcweb-data-channel, where only these two trans=
port
>>>>>> stack cases are considered.
>>>>>> =20
>>>>>>  Regards,
>>>>>>  Juergen
>>>>>> =20
>>>>>> =20
>>>>>>=20
>>>>>> On 16.09.2016 01:30, Roman Shpount wrote:
>>>>>> =20
>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>> On Thu, Sep 15, 2016 at 6:54 PM, Paul Kyzivat <pkyzivat@alum.mit.ed=
u>
>>>>>>> wrote:
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>> On 9/15/16 5:51 PM, Roman Shpount wrote:
>>>>>>> =20
>>>>>>> =20
>>>>>>> RTCWeb defines data channels running over DTLS/SCTP (SCTP over the
>>>>>>>  Datagram Transport Layer Security protocol) not SCTP/DTLS which is=
 DTLS
>>>>>>>  over SCTP and is a completely different thing.
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>>  SCTP/DTLS is now gone, so we don't need to consider it.
>>>>>>> =20
>>>>>>>  IIUC RTCWEB needs for data channels to be defined over at least tw=
o
>>>>>>> lower layers: UDP/DTLS/SCTP and TCP/DTLS/SCTP. (Because ICE might e=
nd up
>>>>>>> having to run over TCP rather than UDP.)
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>> SCTP/DTLS is mentioned in the introduction
>>>>>>> (https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-=
09#se
>>>>>>> ction-1). Should be replaced with UDP/DTLS/SCTP and TCP/DTLS/SCTP.
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> Do we even define data channels on top of SCTP and SCTP/DTLS transp=
orts?
>>>>>>>  These are definitely not used in RTCWeb. I think these should be
>>>>>>> removed
>>>>>>>  from the document.
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>>  Fundamentally data channels are defined over SCTP. Whether that is=
 over
>>>>>>> UDP, TCP or IP or something else is irrelevant to its definition. T=
he
>>>>>>> only thing that is relevant is to have a <proto> value that has SCT=
P on
>>>>>>> top, and for both ends to agree on that. (And those proto values ar=
e
>>>>>>> defined in draft-ietf-mmusic-sctp-sdp, not here.)
>>>>>>> =20
>>>>>>>  So why does this draft have to say *anything* about what is under =
SCTP?
>>>>>>> That is just a matter for each specific usage.
>>>>>>> =20
>>>>>>>  But, if that is too much of a change, then I guess the next best i=
s to
>>>>>>> only define UDP/DTLS/SCTP and TCP/DTLS/SCTP, and note that definiti=
on
>>>>>>> for use of SCTP over other lower layers is left for future definiti=
on.
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>> The document mentions SCTP/DTLS as well as SCTP in the same list as
>>>>>>> UDP/DTLS/SCTP and TCP/DTLS/SCTP
>>>>>>> (https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-=
09#se
>>>>>>> ction-5.1.1.2 and
>>>>>>> https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-0=
9#sec
>>>>>>> tion-5.1.2.2 for instance). These mentions should be removed. If ne=
eded,
>>>>>>> introduction can mention that data channel can be defined in the fu=
ture
>>>>>>> over other SCTP based protocols, such as plain SCTP and SCTP/DTLS.
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>> Regards,=20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>> _____________
>>>>>>>  Roman Shpount
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>>=20
>>>>>>>  ailman/listinfo/mmusic
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>>> =20
>>>>>> =20
>>>>>> =20
>>>>>> =20
>>>>> =20
>>>>> =20
>>>>> =20
>>>>> =20
>>>>> =20
>>>>> =20
>>>>>=20
>>>>> _______________________________________________
>>>>>  mmusic mailing list
>>>>>  mmusic@ietf.org
>>>>>  https://www.ietf.org/mailman/listinfo/mmusic
>>>>> =20
>>>> =20
>>>> =20
>>>> =20
>>>> =20
>>>> =20
>>> =20
>>> =20
>>> =20
>>> =20
>>> =20
>>> =20
>> =20
>> =20
>> =20
>> =20
>> =20
>> =20
>> =20
> =20
> =20
> =20
> =20
=20
=20



--B_3558677048_15443438
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif;"><div>Hi,</div><div><br></div><span=
 id=3D"OLK_SRC_BODY_SECTION"><div><div bgcolor=3D"#FFFFFF" text=3D"#000000">&gt;Re=
garding the establishment of a new SCTP association, yes, agree
    that the simplest way could be to request new sctp-port values being
    used - provided a new SDP offer/answer exchange</div></div></span><div>=
&gt;is used. Would SCTP
    association endpoints be allowed to autonomously establish a new
    SCTP association using the old sctp-port values if the previous SCTP
    association failed for any reason. So far I would assume yes.</div><div=
><br></div><div>I would assume so too.&nbsp;</div><span id=3D"OLK_SRC_BODY_SEC=
TION"><div><div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <br>&gt;Regarding the explicit closure of an SCTP association while kee=
ping
    the DTLS association - right now I also only would have the BUNDLE
    case in mind which you are mentioning.<br>&gt;That could indeed be a va=
lid use case as far as I am concerned.<br></div></div></span><div><br></div>=
<div>So, &nbsp;I guess we could define usage of sctp-port with a zero value =
for that.</div><div><br></div><div>Regards,</div><div><br></div><div>Christe=
r</div><div><br></div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div><d=
iv bgcolor=3D"#FFFFFF" text=3D"#000000">
    <br>
    <div class=3D"moz-cite-prefix">On 28.09.2016 17:28, Christer Holmberg
      wrote:<br>
    </div>
    <blockquote cite=3D"mid:7594FB04B1934943A5C02806D1A2204B4BD072A0@ESESSMB2=
09.ericsson.se" type=3D"cite">
      <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
      <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Consolas",serif;
	color:black;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
      <div class=3D"WordSection1">
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quo=
t;Calibri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US">Hi,<o:p=
></o:p></span></p>
        <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
          <span style=3D"color:windowtext">&gt;</span>Thanks for further
          feedback.<br>
          <span style=3D"color:windowtext">&gt;</span>The first bullet
          point of section 10.5 in draft-ietf-mmusic-sctp-sdp-17 says:<br>
          <span style=3D"color:windowtext">&gt;</span>"Unless the offerer
          wants to re-establish an SCTP association, the offerer MUST
          associate an <span style=3D"color:windowtext"><br>
            &gt;</span>SDP 'sctp-port' attribute, with a new attribute
          value, with the m- line..."<br>
          <span style=3D"color:windowtext">&gt;</span><br>
          <span style=3D"color:windowtext">&gt;</span>Now I am not sure
          anymore regarding the meaning of "re-established" in this
          context.<br>
          <span style=3D"color:windowtext">&gt;</span>If the previous SCTP
          association is closed, and if then a new SCTP association is
          established, is the idea to distinguish between a
          "re-establishment", where <span style=3D"color:windowtext">&gt;</sp=
an>the
          formerly used "sctp-port" values are re-used, and a "new
          establishment", where new values of "sctp-port" are used?<br>
          <span style=3D"color:windowtext"><br>
            I was just having a chat with Roman about that.<o:p></o:p></spa=
n></p>
        <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"colo=
r:windowtext">In my opinion, the most simply way
            would be to say that whenever a new SCTP association is
            established, one MUST use a different sctp-port value than
            the previously used &#8211; no matter if the previous SCTP
            association exists or not.<o:p></o:p></span></p>
        <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"colo=
r:windowtext">Another question is whether the
            closure of an SCTP association requires explicit signalling.
            In that case, perhaps using a sctp-port value of zero? One
            can obviously set the m- line port to zero, which will close
            both the DTLS association and the SCTP association &#8211; but =
the
            question is whether there is a use-case where one would only
            want to close the SCTP association, without touching the
            DTLS association. BUNDLE?<o:p></o:p></span></p>
        <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"colo=
r:windowtext">Regards,<o:p></o:p></span></p>
        <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"colo=
r:windowtext">Christer<o:p></o:p></span></p>
        <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:windowtext"><o=
:p>&nbsp;</o:p></span></p>
        <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:windowtext"><o=
:p>&nbsp;</o:p></span></p>
        <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
          Thanks again,<br>
          Juergen<br>
          <br>
          <span style=3D"color:windowtext"><o:p></o:p></span></p>
        <div>
          <p class=3D"MsoNormal">On 28.09.2016 15:04, Christer Holmberg
            wrote:<o:p></o:p></p>
        </div>
        <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
          <div>
            <p class=3D"MsoNormal">Hi,<o:p></o:p></p>
          </div>
          <div>
            <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
          <div>
            <p class=3D"MsoNormal">As specified
              in&nbsp;draft-ietf-mmusic-sctp-sdp, the SCTP association and
              DTLS association are handled independently of each other.<o:p=
></o:p></p>
          </div>
          <div>
            <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
          <div>
            <p class=3D"MsoNormal">And, in order to re-establish an SCTP
              association, an endpoint needs to provide a new SDP
              'sctp-port' attribute value.<o:p></o:p></p>
          </div>
          <div>
            <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
          <div>
            <p class=3D"MsoNormal">Regards,<o:p></o:p></p>
          </div>
          <div>
            <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
          <div>
            <p class=3D"MsoNormal">Christer<o:p></o:p></p>
          </div>
          <div>
            <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
          <div style=3D"border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-fami=
ly:&quot;Calibri&quot;,sans-serif">From:
                </span></b><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,sans-serif">mmusic
                &lt;<a moz-do-not-send=3D"true" href=3D"mailto:mmusic-bounces@i=
etf.org">mmusic-bounces@ietf.org</a>&gt;
                on behalf of Roman Shpount &lt;<a moz-do-not-send=3D"true" hr=
ef=3D"mailto:roman@telurix.com">roman@telurix.com</a>&gt;<br>
                <b>Date: </b>Wednesday 28 September 2016 at 15:34<br>
                <b>To: </b>Juergen Stoetzer-Bradler &lt;<a moz-do-not-send=3D=
"true" href=3D"mailto:Juergen.Stoetzer-Bradler@nokia.com">Juergen.Stoetzer-Bra=
dler@nokia.com</a>&gt;<br>
                <b>Cc: </b>"<a moz-do-not-send=3D"true" href=3D"mailto:mmusic@i=
etf.org">mmusic@ietf.org</a>"
                &lt;<a moz-do-not-send=3D"true" href=3D"mailto:mmusic@ietf.org"=
>mmusic@ietf.org</a>&gt;<br>
                <b>Subject: </b>Re: [MMUSIC] WG Last Call for
                draft-ietf-mmusic-data-channel-sdpneg-09<o:p></o:p></span><=
/p>
          </div>
          <div>
            <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
          <div>
            <div>
              <div>
                <p class=3D"MsoNormal"><span style=3D"font-size:9.5pt">Juergen,=
</span><o:p></o:p></p>
                <div>
                  <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
                </div>
                <div>
                  <p class=3D"MsoNormal"><span style=3D"font-size:9.5pt">This
                      was my understanding as well but I would also like
                      the rest of the group to confirm.</span><o:p></o:p></=
p>
                </div>
                <div>
                  <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
                </div>
                <div>
                  <p class=3D"MsoNormal"><span style=3D"font-size:9.5pt">Regard=
s,</span><o:p></o:p></p>
                </div>
              </div>
              <div>
                <p class=3D"MsoNormal"><br clear=3D"all">
                  <o:p></o:p></p>
                <div>
                  <div>
                    <p class=3D"MsoNormal">_____________<br>
                      Roman Shpount<o:p></o:p></p>
                  </div>
                </div>
                <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
                <div>
                  <p class=3D"MsoNormal">On Wed, Sep 28, 2016 at 7:39 AM,
                    Juergen Stoetzer-Bradler &lt;<a moz-do-not-send=3D"true" =
href=3D"mailto:Juergen.Stoetzer-Bradler@nokia.com" target=3D"_blank">Juergen.Sto=
etzer-Bradler@nokia.com</a>&gt;
                    wrote:<o:p></o:p></p>
                  <blockquote style=3D"border:none;border-left:solid
                    #CCCCCC 1.0pt;padding:0cm 0cm 0cm
                    6.0pt;margin-left:4.8pt;margin-right:0cm">
                    <div>
                      <p class=3D"MsoNormal">Roman,<br>
                        <br>
                        As per my understanding it should indeed be
                        allowed to shutdown an SCTP association and then
                        to establish a new one over the same DTLS
                        association. Both SCTP association endpoints
                        would have to choose new values for the initiate
                        tags / verification tags, such that received
                        SCTP packets could be uniquely associated with
                        either the previous or the new SCTP association.<br=
>
                        However, I am not an SCTP expert - might be good
                        to hear additional feedback.<br>
                        <br>
                        Best regards,<br>
                        Juergen <o:p></o:p></p>
                      <div>
                        <div>
                          <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"=
><o:p>&nbsp;</o:p></p>
                          <div>
                            <p class=3D"MsoNormal">On 27.09.2016 20:19,
                              Roman Shpount wrote:<o:p></o:p></p>
                          </div>
                          <blockquote style=3D"margin-top:5.0pt;margin-bottom=
:5.0pt">
                            <div>
                              <p class=3D"MsoNormal">Juergen, <o:p></o:p></p>=

                              <div>
                                <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
                              </div>
                              <div>
                                <p class=3D"MsoNormal">The proposed
                                  language looks good.<o:p></o:p></p>
                              </div>
                              <div>
                                <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
                              </div>
                              <div>
                                <p class=3D"MsoNormal">After reading the
                                  multiplexing language, I have a
                                  related question: Is it allowed to
                                  tear down the SCTP association and
                                  setup a new SCTP association over the
                                  same DTLS association?<o:p></o:p></p>
                              </div>
                              <div>
                                <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
                              </div>
                              <div>
                                <p class=3D"MsoNormal">Regards,<o:p></o:p></p=
>
                              </div>
                            </div>
                            <div>
                              <p class=3D"MsoNormal"><br clear=3D"all">
                                <o:p></o:p></p>
                              <div>
                                <div>
                                  <p class=3D"MsoNormal">_____________<br>
                                    Roman Shpount<o:p></o:p></p>
                                </div>
                              </div>
                              <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
                              <div>
                                <p class=3D"MsoNormal">On Tue, Sep 27,
                                  2016 at 8:11 AM, Juergen
                                  Stoetzer-Bradler &lt;<a moz-do-not-send=3D"=
true" href=3D"mailto:Juergen.Stoetzer-Bradler@nokia.com" target=3D"_blank">Juerg=
en.Stoetzer-Bradler@nokia.com</a>&gt;
                                  wrote:<o:p></o:p></p>
                                <blockquote style=3D"border:none;border-left:=
solid
                                  #CCCCCC 1.0pt;padding:0cm 0cm 0cm
                                  6.0pt;margin-left:4.8pt;margin-right:0cm"=
>
                                  <div>
                                    <p class=3D"MsoNormal" style=3D"margin-bott=
om:12.0pt">Roman,
                                      Paul,<br>
                                      <br>
                                      Based on your comments I would
                                      propose to modify the text in the
                                      introduction and in the dcmap and
                                      dcsa multiplexing category
                                      sections as follows.<br>
                                      I've removed all text parts, in
                                      which the "m" line proto values
                                      "SCTP" and "SCTP/DTLS" had been
                                      mentioned.<br>
                                      <br>
                                      Are you ok with these changes?<br>
                                      <br>
                                      Thanks again,<br>
                                      Juergen<o:p></o:p></p>
                                    <pre>1.&nbsp; Introduction<o:p></o:p></=
pre>
                                    <pre><o:p>&nbsp;</o:p></pre>
                                    <pre>&nbsp;&nbsp; The RTCWeb working gr=
oup has defined the concept of bi-directional<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; data channels running=
 on top of the Stream Control Transmission<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; Protocol (SCTP).&nbsp=
; ...<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; <o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp;&nbsp;...<o:p></o:p></=
pre>
                                    <pre>&nbsp;&nbsp; <o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp;&nbsp;This document de=
fines SDP offer/answer negotiation procedures to<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; establish data channe=
ls for transport of well-defined subprotocols,<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; to enable out-of-band=
 negotiation.&nbsp; These procedures are based on<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; generic SDP offer/ans=
wer negotiation rules for SCTP based media<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; transport as specifie=
d in [I-D.ietf-mmusic-sctp-sdp] for the SDP "m"<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; line proto values UDP=
/DTLS/SCTP and TCP/DTLS/SCTP.&nbsp; In future data<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; channels could be def=
ined over other SCTP based protocols, such as<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; SCTP over IP.&nbsp; H=
owever, corresponding potential other "m" line proto<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; values are not consid=
ered in this document.<o:p></o:p></pre>
                                    <pre><o:p>&nbsp;</o:p></pre>
                                    <pre>&nbsp;&nbsp; ...<o:p></o:p></pre>
                                    <p class=3D"MsoNormal"><o:p>&nbsp;</o:p><=
/p>
                                    <pre>5.1.1.2.&nbsp; dcmap Multiplexing =
Category<o:p></o:p></pre>
                                    <pre><o:p>&nbsp;</o:p></pre>
                                    <pre>&nbsp;&nbsp; ...<o:p></o:p></pre>
                                    <pre><o:p>&nbsp;</o:p></pre>
                                    <pre>&nbsp;&nbsp; As the usage of multi=
ple SCTP associations on top of a single DTLS<o:p></o:p></pre>
                                    <pre>&nbsp; &nbsp;connection is outside=
 the scope of [I-D.ietf-mmusic-sctp-sdp], no<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; "a=3Ddcmap:" attribute =
multiplexing rules are specified for the<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; UDP/DTLS/SCTP and TCP=
/DTLS/SCTP proto values.&nbsp; If future extensions<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; of [I-D.ietf-mmusic-s=
ctp-sdp] define how to negotiate multiplexing of<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; multiple SCTP associa=
tions on top of a single DTLS connection, or how<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; to add multiple SCTP =
associations to one BUNDLE group, then<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; multiplexing rules fo=
r the "a=3Ddcmap:" attribute need to be defined as<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; well, for instance in=
 an extension of this SDP based data channel<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; negotiation specifica=
tion.<o:p></o:p></pre>
                                    <p class=3D"MsoNormal"><o:p>&nbsp;</o:p><=
/p>
                                    <pre>5.1.2.2.&nbsp; dcsa Multiplexing C=
ategory<o:p></o:p></pre>
                                    <pre><o:p>&nbsp;</o:p></pre>
                                    <pre>&nbsp;&nbsp; ...<o:p></o:p></pre>
                                    <pre><o:p>&nbsp;</o:p></pre>
                                    <pre>&nbsp;&nbsp; As the usage of multi=
ple SCTP associations on top of a single DTLS<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; connection is outside=
 the scope of [I-D.ietf-mmusic-sctp-sdp], no<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; "a=3Ddcsa:" attribute m=
ultiplexing rules are specified for the<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; UDP/DTLS/SCTP and TCP=
/DTLS/SCTP proto values.&nbsp; If future extensions<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; of [I-D.ietf-mmusic-s=
ctp-sdp] define how to negotiate multiplexing of<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; multiple SCTP associa=
tions on top of a single DTLS connection, or how<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; to add multiple SCTP =
associations to one BUNDLE group, then<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; multiplexing rules fo=
r the "a=3Ddcsa:" attribute need to be defined as<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; well, for instance in=
 an extension of this SDP based data channel<o:p></o:p></pre>
                                    <pre>&nbsp;&nbsp; negotiation specifica=
tion.<o:p></o:p></pre>
                                    <div>
                                      <div>
                                        <p class=3D"MsoNormal" style=3D"margin-=
bottom:12.0pt"><o:p>&nbsp;</o:p></p>
                                        <div>
                                          <p class=3D"MsoNormal">On
                                            21.09.2016 14:17, Juergen
                                            Stoetzer-Bradler wrote:<o:p></o=
:p></p>
                                        </div>
                                        <blockquote style=3D"margin-top:5.0pt=
;margin-bottom:5.0pt">
                                          <p class=3D"MsoNormal" style=3D"margi=
n-bottom:12.0pt">Roman,
                                            Paul,<br>
                                            <br>
                                            Thanks for your comments.<br>
                                            <br>
                                            The protocol stack notation
                                            "SCTP/DTLS" in the
                                            introduction was actually
                                            meant to refer to the "SCTP
                                            on top of DTLS" case, which
                                            is also mentioned in the
                                            succeeding parentheses. I
                                            fully agree that this is
                                            confusing and would propose
                                            to remove "SCTP/DTLS" from
                                            the introduction and instead
                                            to just say:<br>
                                            "The RTCWeb working group
                                            has defined the concept of
                                            bi-directional data channels
                                            running on top of SCTP over
                                            the Datagram Transport Layer
                                            Security protocol.".<br>
                                            Or just "... on top of SCTP
                                            over DTLS".<br>
                                            <br>
                                            And indeed, as
                                            draft-ietf-mmusic-sctp-sdp
                                            doesn't contain m-line proto
                                            value "SCTP/DTLS" at all
                                            anymore, I would agree to
                                            remove it from sections
                                            5.1.1.2 and 5.1.2.2. <br>
                                            Also agree to restrict the
                                            scope of the whole document
                                            to the two "UDP/DTLS/SCTP"
                                            and "TCP/DTLS/SCTP"
                                            transport stack cases and to
                                            explicitly say so e.g. in
                                            the introduction. This would
                                            be inline with the
                                            definition of "data channel"
                                            in the terminology section,
                                            which explicitly refers to
                                            draft-ietf-rtcweb-data-channel,=

                                            where only these two
                                            transport stack cases are
                                            considered.<br>
                                            <br>
                                            Regards,<br>
                                            Juergen<o:p></o:p></p>
                                          <div>
                                            <p class=3D"MsoNormal">On
                                              16.09.2016 01:30, Roman
                                              Shpount wrote:<o:p></o:p></p>=

                                          </div>
                                          <blockquote style=3D"margin-top:5.0=
pt;margin-bottom:5.0pt">
                                            <div>
                                              <div>
                                                <div>
                                                  <div>
                                                    <p class=3D"MsoNormal">On=

                                                      Thu, Sep 15, 2016
                                                      at 6:54 PM, Paul
                                                      Kyzivat &lt;<a moz-do=
-not-send=3D"true" href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyziva=
t@alum.mit.edu</a>&gt;
                                                      wrote:<o:p></o:p></p>=

                                                  </div>
                                                </div>
                                                <div>
                                                  <blockquote style=3D"border=
:none;border-left:solid
                                                    #CCCCCC
                                                    1.0pt;padding:0cm
                                                    0cm 0cm
                                                    6.0pt;margin-left:4.8pt=
;margin-right:0cm">
                                                    <p class=3D"MsoNormal" st=
yle=3D"margin-bottom:12.0pt">On 9/15/16 5:51 PM, Roman Shpount wrote:<o:p></o:=
p></p>
                                                    <blockquote style=3D"bord=
er:none;border-left:solid
                                                      #CCCCCC
                                                      1.0pt;padding:0cm
                                                      0cm 0cm
                                                      6.0pt;margin-left:4.8=
pt;margin-right:0cm">
                                                      <p class=3D"MsoNormal">=
RTCWeb
                                                        defines data
                                                        channels running
                                                        over DTLS/SCTP
                                                        (SCTP over the<br>
                                                        Datagram
                                                        Transport Layer
                                                        Security
                                                        protocol) not
                                                        SCTP/DTLS which
                                                        is DTLS<br>
                                                        over SCTP and is
                                                        a completely
                                                        different thing.<o:=
p></o:p></p>
                                                    </blockquote>
                                                    <p class=3D"MsoNormal"><b=
r>
                                                      SCTP/DTLS is now
                                                      gone, so we don't
                                                      need to consider
                                                      it.<br>
                                                      <br>
                                                      IIUC RTCWEB needs
                                                      for data channels
                                                      to be defined over
                                                      at least two lower
                                                      layers:
                                                      UDP/DTLS/SCTP and
                                                      TCP/DTLS/SCTP.
                                                      (Because ICE might
                                                      end up having to
                                                      run over TCP
                                                      rather than UDP.)<o:p=
></o:p></p>
                                                  </blockquote>
                                                  <div>
                                                    <p class=3D"MsoNormal"><o=
:p>&nbsp;</o:p></p>
                                                  </div>
                                                  <div>
                                                    <p class=3D"MsoNormal">SC=
TP/DTLS
                                                      is mentioned in
                                                      the introduction (<a =
moz-do-not-send=3D"true" href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-d=
ata-channel-sdpneg-09#section-1" target=3D"_blank">https://tools.ietf.org/html=
/draft-ietf-mmusic-data-channel-sdpneg-09#section-1</a>).
                                                      Should be replaced
                                                      with UDP/DTLS/SCTP
                                                      and TCP/DTLS/SCTP.<o:=
p></o:p></p>
                                                  </div>
                                                  <div>
                                                    <p class=3D"MsoNormal"><o=
:p>&nbsp;</o:p></p>
                                                  </div>
                                                  <blockquote style=3D"border=
:none;border-left:solid
                                                    #CCCCCC
                                                    1.0pt;padding:0cm
                                                    0cm 0cm
                                                    6.0pt;margin-left:4.8pt=
;margin-right:0cm">
                                                    <blockquote style=3D"bord=
er:none;border-left:solid
                                                      #CCCCCC
                                                      1.0pt;padding:0cm
                                                      0cm 0cm
                                                      6.0pt;margin-left:4.8=
pt;margin-right:0cm">
                                                      <p class=3D"MsoNormal">=
Do
                                                        we even define
                                                        data channels on
                                                        top of SCTP and
                                                        SCTP/DTLS
                                                        transports?<br>
                                                        These are
                                                        definitely not
                                                        used in RTCWeb.
                                                        I think these
                                                        should be
                                                        removed<br>
                                                        from the
                                                        document.<o:p></o:p=
></p>
                                                    </blockquote>
                                                    <p class=3D"MsoNormal"><b=
r>
                                                      Fundamentally data
                                                      channels are
                                                      defined over SCTP.
                                                      Whether that is
                                                      over UDP, TCP or
                                                      IP or something
                                                      else is irrelevant
                                                      to its definition.
                                                      The only thing
                                                      that is relevant
                                                      is to have a
                                                      &lt;proto&gt;
                                                      value that has
                                                      SCTP on top, and
                                                      for both ends to
                                                      agree on that.
                                                      (And those proto
                                                      values are defined
                                                      in
                                                      draft-ietf-mmusic-sct=
p-sdp,
                                                      not here.)<br>
                                                      <br>
                                                      So why does this
                                                      draft have to say
                                                      *anything* about
                                                      what is under
                                                      SCTP? That is just
                                                      a matter for each
                                                      specific usage.<br>
                                                      <br>
                                                      But, if that is
                                                      too much of a
                                                      change, then I
                                                      guess the next
                                                      best is to only
                                                      define
                                                      UDP/DTLS/SCTP and
                                                      TCP/DTLS/SCTP, and
                                                      note that
                                                      definition for use
                                                      of SCTP over other
                                                      lower layers is
                                                      left for future
                                                      definition.<o:p></o:p=
></p>
                                                  </blockquote>
                                                  <div>
                                                    <p class=3D"MsoNormal"><o=
:p>&nbsp;</o:p></p>
                                                  </div>
                                                  <div>
                                                    <p class=3D"MsoNormal">Th=
e
                                                      document mentions
                                                      SCTP/DTLS as well
                                                      as SCTP in the
                                                      same list as
                                                      UDP/DTLS/SCTP and
                                                      TCP/DTLS/SCTP (<a moz=
-do-not-send=3D"true" href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-data=
-channel-sdpneg-09#section-5.1.1.2" target=3D"_blank">https://tools.ietf.org/h=
tml/draft-ietf-mmusic-data-channel-sdpneg-09#section-5.1.1.2</a>
                                                      and&nbsp;<a moz-do-no=
t-send=3D"true" href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-data-chann=
el-sdpneg-09#section-5.1.2.2" target=3D"_blank">https://tools.ietf.org/html/dr=
aft-ietf-mmusic-data-channel-sdpneg-09#section-5.1.2.2</a>
                                                      for instance).
                                                      These mentions
                                                      should be removed.
                                                      If needed,
                                                      introduction can
                                                      mention that data
                                                      channel can be
                                                      defined in the
                                                      future over other
                                                      SCTP based
                                                      protocols, such as
                                                      plain SCTP and
                                                      SCTP/DTLS.<o:p></o:p>=
</p>
                                                  </div>
                                                  <div>
                                                    <p class=3D"MsoNormal"><o=
:p>&nbsp;</o:p></p>
                                                  </div>
                                                  <div>
                                                    <p class=3D"MsoNormal">Re=
gards,&nbsp;<o:p></o:p></p>
                                                  </div>
                                                  <div>
                                                    <div>
                                                      <p class=3D"MsoNormal">=
_____________<br>
                                                        Roman Shpount<o:p><=
/o:p></p>
                                                    </div>
                                                  </div>
                                                  <div>
                                                    <p class=3D"MsoNormal">&n=
bsp;ailman/listinfo/mmusic
                                                      <o:p></o:p></p>
                                                  </div>
                                                </div>
                                              </div>
                                            </div>
                                          </blockquote>
                                          <p class=3D"MsoNormal"><o:p>&nbsp;<=
/o:p></p>
                                        </blockquote>
                                        <p class=3D"MsoNormal"><o:p>&nbsp;</o=
:p></p>
                                      </div>
                                    </div>
                                  </div>
                                  <p class=3D"MsoNormal" style=3D"margin-bottom=
:12.0pt"><br>
_______________________________________________<br>
                                    mmusic mailing list<br>
                                    <a moz-do-not-send=3D"true" href=3D"mailto:=
mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br>
                                    <a moz-do-not-send=3D"true" href=3D"https:/=
/www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">https://www.ietf.org/=
mailman/listinfo/mmusic</a><o:p></o:p></p>
                                </blockquote>
                              </div>
                              <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
                            </div>
                          </blockquote>
                          <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                </div>
                <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
              </div>
            </div>
          </div>
        </blockquote>
        <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    <br>
  </div></div></span></body></html>

--B_3558677048_15443438--

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

MIIUEwYJKoZIhvcNAQcCoIIUBDCCFAACAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0B
BwGgghHzMIIF+TCCA+GgAwIBAgIQMQ1yPcGTNYDzhYWhrkFQyDANBgkqhkiG9w0BAQUFADA6
MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBD
QSB2MjAeFw0xNDExMDQxMjI4MTlaFw0xNzExMDQxMjI4MThaMG8xETAPBgNVBAoMCEVyaWNz
c29uMRowGAYDVQQDDBFDaHJpc3RlciBIb2xtYmVyZzEtMCsGCSqGSIb3DQEJARYeY2hyaXN0
ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tMQ8wDQYDVQQFEwZMTUZDSEgwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQCMb7fHWIV9CIFYYov86NR/6ibdVV0I+ZqVLE21zQB7otFv
6DTKlVXE7iiC4HCvMhlGkg3/qFmAhAti5Z1Z7+5eEMEIP5JJEZ7fMm6BME33Bkdgg4EfJrq4
FUG28Hw2//0qx3jZWvK2W751AmEuUJ5nkZ6F00GnzJmOhbveadC8E5keqwow9ria0/WazHiK
3wxzjbanoQaZIA+oCKj5YyCv8cCTaSk4pEAbXwxthJ97BaZPahsnb4EZEP08gxR5IE9NRi47
Eqh6LtBjiWpaB42EmCEBxc2uIQ87tlJ0e2SvCo74rqxndXtUeaWauMjjt4DnhJdiXZY244D5
J1gWssRFAgMBAAGjggHEMIIBwDBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9lcmljc3Nvbm5saW5kaXZpZHVhbGNhdjIuY3JsMIGCBggrBgEFBQcBAQR2
MHQwKAYIKwYBBQUHMAGGHGh0dHA6Ly9vY3NwMi50cnVzdC50ZWxpYS5jb20wSAYIKwYBBQUH
MAKGPGh0dHA6Ly9jYS50cnVzdC50ZWxpYXNvbmVyYS5jb20vZXJpY3Nzb25ubGluZGl2aWR1
YWxjYXYyLmNlcjApBgNVHREEIjAggR5jaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20w
VQYDVR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBv
c2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQG
CCsGAQUFBwMCMB0GA1UdDgQWBBRUo03/DrRAW2xpMmhN2uGkvDgx6jAfBgNVHSMEGDAWgBSx
DcrURrevhgLDL28Gyg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIB
ALbwqG5inhl/xPxsuQWcH7GOUZIPAw0JlKltVQ/TlsF7ig0J1iyzao6GsXItJ9H3WZPrCy5E
QchJm7qcn2kKX8OGb+Yr53FisLR2gx+qkrQMDOdix9Was0cvIjDWjAQnEZbxz/a+dzdAP0Tr
wNvD8282bIy0fCt/3uoBfzMnvQG+4wG018bDunc+NCj1FkSKkSRb9fP2Z2li65pfJcxtGIfb
5zsXJZG4Gtbe0/hxlj3NccjB/zVPO7PQ+lnWmxtOiJQ2loA+62vQreUQr328XK4IHFnoU+zX
iVfUN2urvvirQH7Ha70TBMa20J8Nn2aEvY6QYMEQJhAiVmNTiv4EGGv5heX5vb8yaj7pr4YI
vb6D0r+pwpvfEE8YhAEWJgCZP7k5zQwhrpuSF/s+wEruXo59sq9bOCefghktc5fwDu8ved98
cifRPUnuT/c5slJJ8LjFn8d+LnGklUdFA9kLjIJVVx+TM4D/OTaRG+mPFbY2pTyR0V84PG7H
LekupNsFzcme7IBkQ+1zkb9hjz6pyiodf6rh7ph+8XHWNgzbC5PdGCANg8fVWrxqqOoEzvcU
cPMy6XXJs0JWhWas8mJdHq2kGDDEpA7BbBatmtEqziXRnYGJeQK3eMDXXtmOeBSA4y7YZ47y
+CxvbknSQ5dyghwkEq+a7ORPGVjsjtWJYJ6dMIIGtjCCBJ6gAwIBAgIRAKAMy8ybmZjs4jpw
9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmExHzAdBgNVBAMM
FlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3MDc0NjIx
WjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVh
bCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9
ZZeE9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF
6EGtodlpusaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcN
BEjsu8yJm1VqqK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpI
Wt3QPtMYm2R2V1Um0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQ
MaMD8LFf1oLlWLUQxEmI4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7i
rYUYFpq4TyocQ7qpHdYASC+NV8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3Y
Nd2+j7p4C3jkGG+Z6RrZOskPEwtaIHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nO
bPFvedPWIe57lyj0n3e1rTqTGIBIe9wjNnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJ
qTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCBigYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzAB
hiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVyYS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6
Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNvbS90ZWxpYXNvbmVyYXJvb3RjYXYx
LmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQECMDow
OAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20v
Q1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50ZWxpYXNvbmVyYS5j
b20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUF
BwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/SzcwHwYD
VR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4HIGyv
rHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ
37GGx/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbP
d+91zLTj9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2
d6yzd7WoAS55JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss
5lY6zfwVCEZYdZcjSDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1
vLCER9ePEsgLdCG27mUk9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH
3bBt6FJkPeZJIB6YNXAYHZi7RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6S
QSYmp7qDhdJAWPiaq3C+qE/h2DZAJwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn
96Y63AIZdDq1kIHIw0vF4PBTVMZtMIIFODCCAyCgAwIBAgIRAJW+FqD3LkbxezmCcvqLzZYw
DQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmExHzAdBgNVBAMMFlRlbGlh
U29uZXJhIFJvb3QgQ0EgdjEwHhcNMDcxMDE4MTIwMDUwWhcNMzIxMDE4MTIwMDUwWjA3MRQw
EgYDVQQKDAtUZWxpYVNvbmVyYTEfMB0GA1UEAwwWVGVsaWFTb25lcmEgUm9vdCBDQSB2MTCC
AiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAMK+6yfwIaPzaSZVfp3FVRaRXP3vIb9T
gHot0pGMYzHw7CTww6XScnwQbfQ3t+XmfHnqjLWCi65ItqwA3GV17CpNX8GH9SBlK4GoRz6J
I5UwFpB/6FcHSOcZrr9FZ7E3GwYq/t75rH2D+1665I+XZ75Ljo1kB1c4VWk0Nj0TSO9P4tNm
HqTPGrdeNjPUtAa9GAH9d4RQAEX1jF3oI7x+/jXh7VB7qTCNGdMJjmhnXb88lxhTuylixcpe
csHHltTbLaC0H2kD7OriUPEMPPCs81Mt8Bz17Ww5OXOAFshSsCPN4D7c3TxHoLs1iuKYaIu+
5b9y7tL6pe0S7fyYGKkmdtwoSxAgHNN/Fnct7W+A90m7UwW7XWjH1Mh1Fj+JWov3F0fUTPHS
iXk+TT2YqGHeOh7S+F4D4MHJHIzTjU3TlTazN19jY5szFPAtJmtTfImMMsJu7D0hADnJoWji
UIMusDor8zagrC/kb2HCUQk5PotTubtn2txTuXZZNp1D5SDgPTJghSJRt8czu90VL6R4pgd7
gUY2BIbdeTXHlSw7sKMXNeVzH7RcWe/a6hBle3rQf5+ztCo3O3CLm1u5K7fsslESl1MpWtTw
EhDcTwK7EpIvYtQ/aUN8Ddb8WHUBiJ1YFkveupD/RwGJBmr2X7KQarMCpgKIv7NHfirZ1fpo
eDVNAgMBAAGjPzA9MA8GA1UdEwEB/wQFMAMBAf8wCwYDVR0PBAQDAgEGMB0GA1UdDgQWBBTw
j1k4ALP1j5qWDNXr+nuqF+gTEjANBgkqhkiG9w0BAQUFAAOCAgEAvuRcYk4k9AwI//DTDGjk
k0kiP0Qnb7tt3oNmzqjMDfz1mgbldxSR651Be5kqhOX//CHBXfDkH1e3damhXwIm/9fH907e
T/j3HEbAek9ALCI18Bmx0GtnLLCo4MBANzX2hFxc469CeP6nyQ1Q6g2EdvZR74NTxnr/DlZJ
Lo961gzmJ1TjTQpgcmLNkQfWpb/ImWvtxBnmq0wROMVvMeJuScg/doAmAyYp4Db29iBT4xdw
NBedY2gea+zDTYa4EzAvXUYNR0PVG6pZDrlcjQZIrXSHX8f8MVRBE+LHIQ6e4B4N4cB7Q4WQ
xYpYxmUKeFfyxiMPAdkgS94P+5KFdSpcc41teyWRyu5FrgZLAMzTsVlQ2jqIOylDRl6XK1TO
U2+NSueW+r9xDkKLfP0ooNBIytrEgUy7onOTJsjrDNYmiLbAJM+7vVvrdX3pCI6GMyx5dwlp
pYn8s3CQh3aP0yK7Qs69cwsgJirQmz1wHiRszYd2qReWt88NkvuOGKmYSdGe/mBEciG5Ge3C
9THxOUiIkCR1VBatzvT4aRRkOfujuLpwQMcnHL/EVlP6Y2XQ8xwOFvVrhlhNGNTkDY6lnVuR
3HYkUD/GKvvZt5y11ubQ2egZixVxSK236thZiNSQvxaz2emsWWFUyBy6ysHK4bkgTI86k4ml
oMy/0/Z1pHWWbVYxggHkMIIB4AIBATBOMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhAxDXI9wZM1gPOFhaGuQVDIMA0GCWCG
SAFlAwQCAQUAoGkwLwYJKoZIhvcNAQkEMSIEIEc3xfn8oq8g8H5ckvq6Tm0nGDwGwV6f3FkU
qd3C0k+jMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE2MTAw
NzA2MjQwOFowDQYJKoZIhvcNAQEBBQAEggEAfix2wJMkMODNrfX/FdztFbQynmNGIxUZUAic
HWD2JQCPWLMGAxNMy6RzPQ2kIzyPRbahmK3UeTmeNytEqWJvYQml4OyDHrR18s+d8AkoSyLk
oXBkA+l/5eR/X978emjxCITAEK/sCJUSL5GY8gLq0pFIK/XJrsj+2+M1Uly1rP3APS+yBwcS
43YcM8pLWlTTbLUdEIxFM9Fa0D4K1Bup7AfwRQv+bh1glR0vCqbIKYjoRf/8eAayAwMpw8AM
VIBrQN6S5Q96VTf8QIJTGvzX0m83smz2AIfNiT2hd0dIcgeg1DcDmBF5gxpQpRh1+hkaWJbx
2VgPQ5AZkqRAhQCKvw==

--B_3558677048_15399992--


From nobody Fri Oct  7 01:42:01 2016
Return-Path: <magnus.westerlund@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 749B1129536 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 01:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ql1bFakUPmbb for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 01:41:58 -0700 (PDT)
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 69565129497 for <mmusic@ietf.org>; Fri,  7 Oct 2016 01:41:58 -0700 (PDT)
X-AuditID: c1b4fb2d-1c7ff700000009f7-c1-57f75fd3fcce
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by  (Symantec Mail Security) with SMTP id 53.58.02551.3DF57F75; Fri,  7 Oct 2016 10:41:56 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.29) with Microsoft SMTP Server id 14.3.319.2; Fri, 7 Oct 2016 10:41:55 +0200
To: Cullen Jennings <fluffy@iii.ca>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com>
Date: Fri, 7 Oct 2016 10:41:52 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrLLMWRmVeSWpSXmKPExsUyM2K7tO6V+O/hBnevalh8WP+D0WLq8scs Fis2HGB1YPb4+/4Dk8eSJT+ZPC6f/8gYwBzFZZOSmpNZllqkb5fAlXH8+SLGgk8aFecPdLM3 MPYpdjFyckgImEjs6//E2MXIxSEksJ5R4tqT3YwgCSGBZYwSxy6ndzFycAgL5EtMn1IHEhYR UJY4t+MuM0T9QkaJnxMms4I4zALNjBJ7Z+9iBaliE7CQuPmjkQ3E5hWwl5jb1cAKMohFQEXi TlMNSFhUIEbi+rNHUCWCEidnPmEBKeEUsJJYcFcQJMwMNGXm/POMELa8RPPW2cwQp2lLNDR1 sE5gFJiFpHsWkpZZSFoWMDKvYhQtTi0uzk03MtZLLcpMLi7Oz9PLSy3ZxAgM1INbfuvuYFz9 2vEQowAHoxIP74OIb+FCrIllxZW5hxglOJiVRHhbY7+HC/GmJFZWpRblxxeV5qQWH2KU5mBR Euc1W3k/XEggPbEkNTs1tSC1CCbLxMEp1cCYtdTu8Pt9P7dcjuJ0dmEqst12vJiRS0AheE64 ++Pbn/49UnmicEW5+H2a7bk1KwQeW7gqc2/dM7P+s2rG1bSZk45PPsXz5eWG1oZPwT0X5+Wq Rr+6bSmXeSxv/j2N8F+TV61qSEjUKoxJfX0+WTPTqyzu5TN+1z+P//j6h2qstV/Ivo778k4D JZbijERDLeai4kQAndDLllACAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MrR12RspZ2pQmEBkzylZVpMaOCQ>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 08:42:00 -0000

Den 2016-10-06 kl. 23:59, skrev Cullen Jennings:
>
> I'm not getting the problem here and mandating 6904 is not an easy
> thing to do.

So, lets be clear on what I have proposed. For bundle in general it is 
RECOMMENDED to encrypt MIDs in RTP header extensions. I have also 
proposed that for RTCWeb implementation and use should be mandated. I 
was not clear in what applies when an WebRTC endpoint talks to a legacy 
endpoint what is expected here. I guess this is the thorny issue.

>
> I'm not getting what the issue is here. If mid are random, or are
> just a count of n'th m-line in the sdp, what is the problem with
> exposing them to people are getting the media?

The issue is that these identifiers are going from having only been 
visiable in the signalling messages to be visible also on the RTP media 
plane. And without RFC6904 even if one uses SRTP, these values are 
exposed. This have several different effects as I see it. So if the 
generation algorithm are not strictly defined, the implementation gets 
possible to fingerprint. In addition the device gets to be fingerprinted 
based on the number of streams offered and their identifiers. Thus, it 
is not only what is actually used that is exposed, but what was 
originally offered, i.e. the full offer leaks into unencrypted domain on 
the media plane. Note, this later can't be dealt with any mid id 
creation rules, it will still leak. Thus devices that have more exotic 
configurations when it comes to media streams, i.e. number of cameras 
etc this can still be fingerprinted by passive attacks from third parties.

It is the passive attack from third parties that has me worried here. A 
peer in the signalling has massively more powerful fingerprinting, but 
that requires one to be in the signalling context, not passively observe 
traffic that goes past.


Cheers

Magnus


>
>
>
>> On Oct 6, 2016, at 7:39 AM, Magnus Westerlund
>> <magnus.westerlund@ericsson.com> wrote:
>>
>> Den 2016-10-06 kl. 14:49, skrev Christer Holmberg:
>>>
>>> Hi,
>>>
>>> Magnus suggested usage of RFC 6904 for encryption of the RTP SDES
>>> header extension for MID. I guess it would be a SHUOLD?
>>>
>>> In addition, we would say that a corresponding level of security
>>> must be applied to the RTP SDES header extension for MID and to
>>> the RTCP SDES MID item.
>>>
>>> Any opinions?
>>
>> I think this is fine solution to this issue. I would probably
>> formulate the security considerations like this.
>>
>> The identfication-tag when included in the RTP MID SDES item,
>> independent of transport, RTCP SDES packet or RTP header extension,
>> can expose the value to parties beyond the signaling chain.
>> Therefore, the identification-tag MUST NOT contain any user related
>> information. However, the implementation's method for generating
>> identfication-tags combined with hardware configuration can enable
>> fingerprinting of the endpoint device and thus its user. As the
>> identification-tag is also used to route the media stream to the
>> right application functionality it is also important that the value
>> received is the one intended by the sender, thus integrity and the
>> authenticity of the source are important to prevent denial of
>> service on the application. At least to prevent third parties from
>> modifying the identification-tag value.
>>
>> Due to the security risks associated with the MID values in RTP and
>> RTCP it is strongly RECOMMENDED that the MID SDES item is both
>> confidentiality protected as well as source authenticated when
>> transported in either RTCP or RTP header extensions. The security
>> mechanisms used SHALL provide corresponding levels of security for
>> both RTP header extensions and RTCP. Confidentiality mechanisms for
>> RTP/RTCP are discussed in Options for Securing RTP Sessions
>> [RFC7201], for example SRTP [RFC3711] with SRTCP encryption enabled
>> combined with [RFC6904] can provide the necessary security
>> functions.
>>
>>
>> Cheers
>>
>> Magnus Westerlund
>>
>> ----------------------------------------------------------------------
>>
>>
Services, Media and Network features, Ericsson Research EAB/TXM
>> ----------------------------------------------------------------------
>>
>>
Ericsson AB                 | Phone  +46 10 7148287
>> FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079 SE-164 80
>> Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
>>
>>
>>
_______________________________________________
>> mmusic mailing list mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>
>


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Fri Oct  7 02:49:42 2016
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 1769212954B for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 02:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 Q3UHISq1oLk1 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 02:49:32 -0700 (PDT)
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 1045212954A for <mmusic@ietf.org>; Fri,  7 Oct 2016 02:49:31 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-69-57f76fa9255f
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by  (Symantec Mail Security) with SMTP id E8.A7.02458.9AF67F75; Fri,  7 Oct 2016 11:49:29 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0319.002; Fri, 7 Oct 2016 11:49:09 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Cullen Jennings <fluffy@iii.ca>, mmusic <mmusic@ietf.org>
Thread-Topic: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
Thread-Index: AQHSG0GgBWsMgAttg0WZUBo1tL92NKCb3CYAgAD/+IA=
Date: Fri, 7 Oct 2016 09:49:09 +0000
Message-ID: <D41D4800.10A3F%christer.holmberg@ericsson.com>
References: <147481162395.28315.18346373858565370012.idtracker@ietfa.amsl.com> <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com> <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca>
In-Reply-To: <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <D1F5CA9DF2EA67489B931EBCB0310BAD@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCIsWRmVeSWpSXmKPExsUyM2K7je7K/O/hBm8bLC0+rP/BaDF1+WMW ByaPJUt+MnlcPv+RMYApissmJTUnsyy1SN8ugSvj47HN7AVXpSv+nPvP2sB4SayLkZNDQsBE om3hf5YuRi4OIYH1jBIXT/1mhHAWMUpMnbYSyOHgYBOwkOj+pw3SICJgK9G36wQziC0s4Cbx +/oCJoi4u8TsWfPYQMpFBKwkJn2zAwmzCKhI3JzXwgJi8wpYS9yZeJoZYvxGRokzZ2czgiQ4 geo3nLsKVsQoICbx/dQasJnMAuISt57MZ4I4VEBiyZ7zzBC2qMTLx/9YQWxRAT2J719nQ8UV JXaebWeG6NWTuDF1ChuEbS2xpnsxlK0tsWzha2aIgwQlTs58wjKBUWwWknWzkLTPQtI+C0n7 LCTtCxhZVzGKFqcWF+emGxnppRZlJhcX5+fp5aWWbGIExtXBLb+tdjAefO54iFGAg1GJh/dB xLdwIdbEsuLK3EOMEhzMSiK8s7O/hwvxpiRWVqUW5ccXleakFh9ilOZgURLnNVt5P1xIID2x JDU7NbUgtQgmy8TBKdXAWMc0Xb8rRKvksoR4+Szx7o7EtUKZn+qCF7wSr7W5Lf3l9uTXBq3c WvnT+9aWc03L2Fb4/xGnt53z3CMh8xexFbOopq4plv9/uK86Q+/xSb5dbBv/GRVX2Gw2Ntn4 5U/Zk97o11Yc2w/lbGae93yP0e7X0h1f5v38XajrnfAmJHb6ftmzZxcwKbEUZyQaajEXFScC AI8pX/inAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/8Mx2DcsAxbBwJfR_kYOK59OVRNo>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 09:49:34 -0000

Hi,

First, being this late in the process, I think it would be fair to explain
(I would have expected the chairs to request the same) what the problem
is. We HAVE added the note saying that the draft does NOT make existing
4572 implementations non-compliant. What else is missing?

Second, IMO the draft says a little more than =B3multiple fingerprints are
allowed=B2. It also specifies HOW multiple fingerprints are used, HOW they
must be matched etc - using RFC 2119 terminology (there is a number of
MUSTs). Do we consider that =B3advice=B2? Or, do you want to REMOVE that?

Last, if we don=B9t indicate the draft as a =B34572 update=B2, people will =
not
automatically be made aware of it when looking for 4572, as it will not be
listed as an 4572 update. Is that a good thing?

Regards,

Christer





On 07/10/16 00:39, "mmusic on behalf of Cullen Jennings"
<mmusic-bounces@ietf.org on behalf of fluffy@iii.ca> wrote:

>
>It would be easy to rewrite it to not change it but simply clarify that
>multiple fingerprints are allowed and provide advice about additional
>ones to provide.=20
>
>
>> On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)
>><fluffy@cisco.com> wrote:
>>=20
>>=20
>> So I still disagree that this should update 4572 and the text for the
>>interoperability issue if significantly different than what many people
>>proposed on list. Can we arrange a phone call to discuss this.
>>=20
>>=20
>>=20
>>> On Sep 25, 2016, at 7:53 AM, internet-drafts@ietf.org wrote:
>>>=20
>>>=20
>>> 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
>>>of the IETF.
>>>=20
>>>       Title           : SDP Fingerprint Attribute Usage Clarifications
>>>       Author          : Christer Holmberg
>>> 	Filename        : draft-ietf-mmusic-4572-update-07.txt
>>> 	Pages           : 8
>>> 	Date            : 2016-09-25
>>>=20
>>> Abstract:
>>>  This document updates RFC 4572 by clarifying the usage of multiple
>>>  SDP 'fingerprint' attributes with a single SDP media description ("m=
=3D
>>>  line").  The document also updates the preferred cipher suite with a
>>>  stronger cipher suite.
>>>=20
>>>=20
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/
>>>=20
>>> There's also a htmlized version available at:
>>> https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07
>>>=20
>>> A diff from the previous version is available at:
>>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-4572-update-07
>>>=20
>>>=20
>>> 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.
>>>=20
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>=20
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> I-D-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>=20
>> _______________________________________________
>> 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 Fri Oct  7 04:00:55 2016
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 87C3512948D; Fri,  7 Oct 2016 04:00:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147583805155.8987.15480373290368613040.idtracker@ietfa.amsl.com>
Date: Fri, 07 Oct 2016 04:00:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/uEsrHuEYvopuumkCyC4vJpL08Tc>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-bundle-negotiation-33.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 11:00:51 -0000

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

        Title           : Negotiating Media Multiplexing Using the Session Description Protocol (SDP)
        Authors         : Christer Holmberg
                          Harald Tveit Alvestrand
                          Cullen Jennings
	Filename        : draft-ietf-mmusic-sdp-bundle-negotiation-33.txt
	Pages           : 55
	Date            : 2016-10-07

Abstract:
   This specification defines a new Session Description Protocol (SDP)
   Grouping Framework extension, 'BUNDLE'.  The extension can be used
   with the SDP Offer/Answer mechanism to negotiate the usage of a
   single address:port combination (BUNDLE address) for receiving media,
   referred to as bundled media, specified by multiple SDP media
   descriptions ("m=" lines).

   To assist endpoints in negotiating the use of bundle this
   specification defines a new SDP attribute, 'bundle-only', which can
   be used to request that specific media is only used if bundled.  The
   specification also updates RFC 3264, to allow usage of zero port
   values without meaning that media is rejected.

   There are multiple ways to correlate the bundled RTP packets with the
   appropriate media descriptions.  This specification defines a new
   Real-time Transport Protocol (RTP) source description (SDES) item and
   a new RTP header extension that provides an additional way to do this
   correlation by using them to carry a value that associates the RTP/
   RTCP packets with a specific media description.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation-33

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-bundle-negotiation-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 Oct  7 04:08:54 2016
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 82D46129545 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 04:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 xbxQnvW5D9y0 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 04:08:52 -0700 (PDT)
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 DB3C112950A for <mmusic@ietf.org>; Fri,  7 Oct 2016 04:08:51 -0700 (PDT)
X-AuditID: c1b4fb3a-ab7ff7000000099a-b2-57f78241be73
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by  (Symantec Mail Security) with SMTP id 3B.AA.02458.14287F75; Fri,  7 Oct 2016 13:08:50 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0319.002; Fri, 7 Oct 2016 13:08:48 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: BUNDLE-33
Thread-Index: AQHSIIstcTd2Um+ywkGOwYtfzzEvWA==
Date: Fri, 7 Oct 2016 11:08:48 +0000
Message-ID: <D41D5E6D.10A91%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_D41D5E6D10A91christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyM2K7rq5T0/dwg1l/eCymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujD3N/1gKFghX3N+6lbmBcbZAFyMnh4SAicSJjfuZuxi5OIQE 1jNKzNp0lR3CWcQo0dS7GyjDwcEmYCHR/U8bpEFEQF3i694eZhBbWEBV4ubfOawQcS2J92sf Q9l6EvuObGABsVkEVCR2/l3MBmLzClhL/NowA6yGUUBM4vupNUwgNrOAuMStJ/OZIA4SkFiy 5zwzhC0q8fLxP7B6UaCZ37/OhoorSfzYcIkFojdBYtXtE4wQ8wUlTs58wjKBUWgWkrGzkJTN QlIGETeQeH9uPjOErS2xbOFrKFtfYuOXs0D1HEC2tcT7x2LIShYwcqxiFC1OLS7OTTcy0kst ykwuLs7P08tLLdnECIyUg1t+W+1gPPjc8RCjAAejEg/vg4hv4UKsiWXFlbmHGCU4mJVEeG/U fQ8X4k1JrKxKLcqPLyrNSS0+xCjNwaIkzmu28n64kEB6YklqdmpqQWoRTJaJg1OqgbGcdXFa j9hX+c89V0wObqk7/0fg6x8pxzdpPz1LWGvmzrOvUC6VLFw6N1BQjDlsQfp15Ve6LAwKn0oM e3yrf/+akMqeLfosm2tBah/nwukpv8Qf/lDfeyPqU/isCb/fpMhEyhoHcO+pSQnnmbVDJfdo R5bP1GzrjxxBb/TexH1wq81f97lAXYmlOCPRUIu5qDgRAKwQMzKQAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/n7kl-Wnm7t4WfLn4qHxiluO0j5E>
Subject: [MMUSIC] Draft new version: BUNDLE-33
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 11:08:53 -0000

--_000_D41D5E6D10A91christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

I=92ve submitted a new version (-33) of BUNDLE.

The new version contains the easy editorial non-technical changes based on =
Ekr=92s and Cullens=92 comments.

The currently major issues on my mind are:

  *   Ekr=92s issue on "shared address". While mostly an editorial change, =
it does require quite a bit of re-writing.
  *   Magnus=92s issue on RTP header extension/RTCP SDES item security for =
MID. Once we agree on a way forward, the change should be rather straight f=
orward: add some text to the Security Considerations section.

There was also an issue regarding usage of different terminology in JSEP an=
d BUNDLE. However, I=92ll leave that to the MMUSIC and RTCWEB chairs to dis=
cuss what/if to do something about.

Regards,

Christer

--_000_D41D5E6D10A91christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <3F665A0577DE82459F47E1477BFC9C0E@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>I=92ve submitted a new version (-33) of BUNDLE.</div>
<div><br>
</div>
<div>The new version contains the easy editorial non-technical changes base=
d on Ekr=92s and Cullens=92 comments.</div>
<div><br>
</div>
<div>The currently major issues on my mind are:</div>
<ul>
<li>Ekr=92s issue on &quot;shared address&quot;. While mostly an editorial =
change, it does require quite a bit of re-writing.</li><li>Magnus=92s issue=
 on RTP header extension/RTCP SDES item security for MID. Once we agree on =
a way forward, the change should be rather straight forward: add some text =
to the Security Considerations section.</li></ul>
<div>There was also an issue regarding usage of different terminology in JS=
EP and BUNDLE. However, I=92ll leave that to the MMUSIC and RTCWEB chairs t=
o discuss what/if to do something about.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
</body>
</html>

--_000_D41D5E6D10A91christerholmbergericssoncom_--


From nobody Fri Oct  7 04:16:55 2016
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 7C0DE129541 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 04:16:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 yW6pvswleQCh for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 04:16:52 -0700 (PDT)
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 E71B81293EE for <mmusic@ietf.org>; Fri,  7 Oct 2016 04:16:51 -0700 (PDT)
X-AuditID: c1b4fb25-15fff7000000793b-34-57f784213daa
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by  (Symantec Mail Security) with SMTP id D5.E7.31035.12487F75; Fri,  7 Oct 2016 13:16:50 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0319.002; Fri, 7 Oct 2016 13:16:49 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Draft new version: BUNDLE-33
Thread-Index: AQHSIIxLs2vrYp5hOk2zNo1pBcZ6cA==
Date: Fri, 7 Oct 2016 11:16:48 +0000
Message-ID: <D41D5FEF.10A94%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_D41D5FEF10A94christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyM2K7ga5Sy/dwgxtfRC2mLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujA8/xQruKFVc37GNqYHxgWwXIyeHhICJxObr75m6GLk4hATW M0q07L3OApIQEljEKDFtY1AXIwcHm4CFRPc/bZCwiECsxNd1IPWcHMICRhJ3pvYyQ8SNJY5P bGSBsPUk3l9Yww5iswioSFw+PZsNxOYVsJb4sLsZrJ5RQEzi+6k1YHOYBcQlbj2ZzwRxj4DE kj3nmSFsUYmXj/+xgtiiQDO/f50NFVeS+LHhEgtEb4JEY/cDqPmCEidnPmGZwCg0C8nYWUjK ZiEpg4gbSLw/N58ZwtaWWLbwNZStL7Hxy1lGCNtaYse39ShqFjByrGIULU4tTspNNzLWSy3K TC4uzs/Ty0st2cQIjJODW36r7mC8/MbxEKMAB6MSD++DiG/hQqyJZcWVuYcYJTiYlUR4b9R9 DxfiTUmsrEotyo8vKs1JLT7EKM3BoiTOa7byfriQQHpiSWp2ampBahFMlomDU6qBUXrle59P uyu4eTY4CSQqPLUyfzSZ1bTOXvHrYredfxfsVBWK/3Qk1Odw2bIvdTLZdlEnzk488m7jCUd+ 5y1/KyaFT9m1PseY794d2eOecy3O7BLb9oD/5qoLlXd7O62faTl87F9jdDqxNnoTR12fVz7L owDRt8tzvm1SLg+Qrpw7Zea/p84SW5VYijMSDbWYi4oTAYPDkVaPAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/tE_dMdFSvFDX0S4BICLVeTn0Bhg>
Subject: Re: [MMUSIC] Draft new version: BUNDLE-33
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 11:16:53 -0000

--_000_D41D5FEF10A94christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

Of course, there is also the issue on RTP demux. But, I ask people to actua=
lly provide text (per e-mail or GitHub PR).

Regards,

Christer

From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on b=
ehalf of Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.=
holmberg@ericsson.com>>
Date: Friday 7 October 2016 at 14:08
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>
Subject: [MMUSIC] Draft new version: BUNDLE-33

Hi,

I=92ve submitted a new version (-33) of BUNDLE.

The new version contains the easy editorial non-technical changes based on =
Ekr=92s and Cullens=92 comments.

The currently major issues on my mind are:

  *   Ekr=92s issue on "shared address". While mostly an editorial change, =
it does require quite a bit of re-writing.
  *   Magnus=92s issue on RTP header extension/RTCP SDES item security for =
MID. Once we agree on a way forward, the change should be rather straight f=
orward: add some text to the Security Considerations section.

There was also an issue regarding usage of different terminology in JSEP an=
d BUNDLE. However, I=92ll leave that to the MMUSIC and RTCWEB chairs to dis=
cuss what/if to do something about.

Regards,

Christer

--_000_D41D5FEF10A94christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <A779870FC5C32747817E2985700F75B0@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>Of course, there is also the issue on RTP demux. But, I ask people to =
actually provide text (per e-mail or GitHub PR).</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>mmusic &lt;<a href=3D"mailto:=
mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a>&gt; on behalf of Chris=
ter Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">christer=
.holmberg@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday 7 October 2016 at 14:0=
8<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:mmusic@=
ietf.org">mmusic@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org">=
mmusic@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[MMUSIC] Draft new version=
: BUNDLE-33<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>I=92ve submitted a new version (-33) of BUNDLE.</div>
<div><br>
</div>
<div>The new version contains the easy editorial non-technical changes base=
d on Ekr=92s and Cullens=92 comments.</div>
<div><br>
</div>
<div>The currently major issues on my mind are:</div>
<ul>
<li>Ekr=92s issue on &quot;shared address&quot;. While mostly an editorial =
change, it does require quite a bit of re-writing.</li><li>Magnus=92s issue=
 on RTP header extension/RTCP SDES item security for MID. Once we agree on =
a way forward, the change should be rather straight forward: add some text =
to the Security Considerations section.</li></ul>
<div>There was also an issue regarding usage of different terminology in JS=
EP and BUNDLE. However, I=92ll leave that to the MMUSIC and RTCWEB chairs t=
o discuss what/if to do something about.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
</div>
</div>
</span>
</body>
</html>

--_000_D41D5FEF10A94christerholmbergericssoncom_--


From nobody Fri Oct  7 05:38:36 2016
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 CC72A129585 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 05:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5] 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 8ZPv8YkYbuGr for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 05:38:34 -0700 (PDT)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (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 54B61129579 for <mmusic@ietf.org>; Fri,  7 Oct 2016 05:38:34 -0700 (PDT)
Received: by mail-it0-x22e.google.com with SMTP id z65so5722067itc.0 for <mmusic@ietf.org>; Fri, 07 Oct 2016 05:38:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Ta7emB9zPnIuTeAcgJVT5/rPfl0Ss3nyTDLvXwNi0Qc=; b=W+QON+Di+QOnbuU/nkS5xTo5UEqqPf72lK6sGX7hivgSaCfJiO4YdCIhkYxN7KOrtq VcOjh7xVRQPK2Nm7u65NhNgD0V5Wd2Y/flJgxdnzWF89bpCaBsLXZ3IZKgVsFL0w4OGF Y7D8A0YYTZ2TWSNh8SpPsRjFpGGUv1bEIxShxsu9Uf7Cuj9PrN481KIwns5wBOYKn7Ov Y/L+T+t5P3dmFwPGCKQUWRHawCd1NTQj20QIQAhoglJIA2e9HleysJOMWjQjE7567P2u kQa2sSS+KIBpQLnZ5XIAI2KCn8OjuoWTgEA4HkTQTMakWWPDFeN0plRVVbh/k/ztIf/q 9xCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Ta7emB9zPnIuTeAcgJVT5/rPfl0Ss3nyTDLvXwNi0Qc=; b=EPIwWDMl7bl1XFgVB2bqMSZwwHpKzFNiEU2bRCYDWh+HmI0HODKDGA7GFdIE9RhOg0 L9P4w2zKge86F9HUbp4fdK+GwAN7AZTzva70YnGLhVr87p7DLAMw2G5kKpap+RHu4Ocl fJdhcNABOr09vdcrFt0AcPefB0VTV5MkDut+gPDTsuQmN7Z+lTChGV4sZnyJGULV++1q wyRxUMviWqrNp+WUwox1J8C9fEYdu3XS0FfoNP9Ombp39Y59OK0yJhyoOkMaBo19EcAb NcuAODk8YlAvfxC6qXAkwLw5SlAlDz0B3gy2/K28H2dGnGTsRzgpNkNKNCi+G4KlSBvv oTGw==
X-Gm-Message-State: AA6/9RlPO4tQ5SXLMFXfZliVj0DhkT4giLiA0Z31kJnq5FO+bFqliWl2b58HSXNpeNRwPw==
X-Received: by 10.36.204.139 with SMTP id x133mr40606528itf.86.1475843913246;  Fri, 07 Oct 2016 05:38:33 -0700 (PDT)
Received: from mail-it0-f53.google.com (mail-it0-f53.google.com. [209.85.214.53]) by smtp.gmail.com with ESMTPSA id t14sm1086512itb.22.2016.10.07.05.38.32 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Oct 2016 05:38:32 -0700 (PDT)
Received: by mail-it0-f53.google.com with SMTP id z65so5721559itc.0 for <mmusic@ietf.org>; Fri, 07 Oct 2016 05:38:32 -0700 (PDT)
X-Received: by 10.36.25.82 with SMTP id b79mr3110777itb.122.1475843912274; Fri, 07 Oct 2016 05:38:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.110.18 with HTTP; Fri, 7 Oct 2016 05:38:31 -0700 (PDT)
In-Reply-To: <2f15dae6-3742-cf11-d54c-b9ca63109611@nokia.com>
References: <AM3PR07MB11887A55542865A7FB23B7E58DF00@AM3PR07MB1188.eurprd07.prod.outlook.com> <CAD5OKxv7zfVyF+Jm7x6dsr3fL6DSCg22T09xRn_NnaRModSSZQ@mail.gmail.com> <a5d6affc-1405-81e4-b00e-d59b74b13c5b@alum.mit.edu> <CAD5OKxuBTimPHQb5fvNgprpNKeqfwzj_Hzj9SUwg=t0TPshCfA@mail.gmail.com> <1947c926-247d-9857-1ded-622f10a3da65@nokia.com> <5bea2b17-ac09-f30e-0fbe-231b0101fe73@nokia.com> <CAD5OKxvyWZB8gfgPVO0VB9_4s7qxJrs_goBG0d5GY=JRro+cAg@mail.gmail.com> <a48beca0-ce43-ce30-fb01-fd6e1f0473ef@nokia.com> <CAD5OKxuSY0VP=cK=WQbZKbG8Y=wPn97kfpaW7S_t1iKnMKgJOg@mail.gmail.com> <D4119B33.10038%christer.holmberg@ericsson.com> <49717688-db0e-780f-cfc9-a9a14e6e88b2@nokia.com> <7594FB04B1934943A5C02806D1A2204B4BD072A0@ESESSMB209.ericsson.se> <2f15dae6-3742-cf11-d54c-b9ca63109611@nokia.com>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 7 Oct 2016 08:38:31 -0400
X-Gmail-Original-Message-ID: <CAD5OKxv3wuyu6nChjoj-OXftS-BD3wt9ktoEd-0Z3kUUsLOgeA@mail.gmail.com>
Message-ID: <CAD5OKxv3wuyu6nChjoj-OXftS-BD3wt9ktoEd-0Z3kUUsLOgeA@mail.gmail.com>
To: Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@nokia.com>
Content-Type: multipart/alternative; boundary=001a114409ac22a041053e45b0c0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ViiqN7yAa0K0fIqWqMcPBWEqE0Q>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] WG Last Call for draft-ietf-mmusic-data-channel-sdpneg-09
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 12:38:36 -0000

--001a114409ac22a041053e45b0c0
Content-Type: text/plain; charset=UTF-8

On Thu, Sep 29, 2016 at 8:39 AM, Juergen Stoetzer-Bradler <
Juergen.Stoetzer-Bradler@nokia.com> wrote:

> Regarding the establishment of a new SCTP association, yes, agree that the
> simplest way could be to request new sctp-port values being used - provided
> a new SDP offer/answer exchange is used. Would SCTP association endpoints
> be allowed to autonomously establish a new SCTP association using the old
> sctp-port values if the previous SCTP association failed for any reason. So
> far I would assume yes.
>

Would both end points agree that SCTP association failed at the same time?
Would they be able to restart SCTP association at the same time? SCTP setup
is active/active in the current draft. Unless both endpoints detect the
failure simultaneously and recover from whatever caused it sententiously,
they will not both start to re-establish the connection at the same time.
It would be much cleaner if SCTP association would only be re-established
after O/A exchange. Furthermore, SCTP should be able to handle short
network connectivity disruptions. If SCTP actually failed, it means
something fairly serious happened with the network connection (or client
stack). It is unclear that SCTP association would easily automatically
recover in such cases.

Also, I assume you do not want to automatically re-establish an SCTP
association if one of the end points gracefully closes it using SCTP
SHUTDOWN.
_____________
Roman Shpount

--001a114409ac22a041053e45b0c0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Thu, Sep 29, 2016 at 8:39 AM, Juergen Stoetzer-Bradler <span dir=3D=
"ltr">&lt;<a href=3D"mailto:Juergen.Stoetzer-Bradler@nokia.com" target=3D"_=
blank">Juergen.Stoetzer-Bradler@nokia.com</a>&gt;</span> wrote:<br></div></=
div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF">Regarding the establishment of a new SCTP associ=
ation, yes, agree
    that the simplest way could be to request new sctp-port values being
    used - provided a new SDP offer/answer exchange is used. Would SCTP
    association endpoints be allowed to autonomously establish a new
    SCTP association using the old sctp-port values if the previous SCTP
    association failed for any reason. So far I would assume yes.<br></div>=
</blockquote><div><br></div><div>Would both end points agree that SCTP asso=
ciation failed at the same time? Would they be able to restart SCTP associa=
tion at the same time? SCTP setup is active/active in the current draft. Un=
less both endpoints detect the failure simultaneously and recover from what=
ever caused it sententiously, they will not both start to re-establish the =
connection at the same time. It would be much cleaner if SCTP association w=
ould only be re-established after O/A exchange. Furthermore, SCTP should be=
 able to handle short network connectivity disruptions. If SCTP actually fa=
iled, it means something fairly serious happened with the network connectio=
n (or client stack). It is unclear that SCTP association would easily autom=
atically recover in such cases.=C2=A0</div><div><br></div><div>Also, I assu=
me you do not want to automatically re-establish an SCTP association if one=
 of the end points gracefully closes it using SCTP SHUTDOWN.=C2=A0</div><di=
v><div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div>=
<div>=C2=A0</div></div></div></div>

--001a114409ac22a041053e45b0c0--


From nobody Fri Oct  7 06:32:28 2016
Return-Path: <prvs=4088fb606e=jonathan@vidyo.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 5EAEF1295D5 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 06:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.896
X-Spam-Level: 
X-Spam-Status: No, score=0.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=3.496, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uzKexLbVjkn6 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 06:32:25 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0b-00198e01.pphosted.com [67.231.157.197]) (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 90F791295D8 for <mmusic@ietf.org>; Fri,  7 Oct 2016 06:32:25 -0700 (PDT)
Received: from pps.filterd (m0073110.ppops.net [127.0.0.1]) by mx0b-00198e01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u97DT7UM014309; Fri, 7 Oct 2016 09:32:21 -0400
Received: from mail.vidyo.com ([162.209.16.214]) by mx0b-00198e01.pphosted.com with ESMTP id 25wj2194jt-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Fri, 07 Oct 2016 09:32:20 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Fri, 7 Oct 2016 08:32:19 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
Thread-Index: AQHSIJ7bI6DSyxAykkyV07AZPatBU6CdUQYA
Date: Fri, 7 Oct 2016 13:32:18 +0000
Message-ID: <FEB4A43F-B38F-43C3-A3D7-345C97AC73DC@vidyo.com>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com>
In-Reply-To: <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [160.79.219.114]
Content-Type: multipart/alternative; boundary="_000_FEB4A43FB38F43C3A3D7345C97AC73DCvidyocom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-10-07_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609300000 definitions=main-1610070233
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/8F5G1cQFPKFCwHgfhdSCinQZtR8>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, mmusic <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 13:32:27 -0000

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

DQpPbiBPY3QgNywgMjAxNiwgYXQgNDo0MSBBTSwgTWFnbnVzIFdlc3Rlcmx1bmQgPG1hZ251cy53
ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbTxtYWlsdG86bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24u
Y29tPj4gd3JvdGU6DQoNCkRlbiAyMDE2LTEwLTA2IGtsLiAyMzo1OSwgc2tyZXYgQ3VsbGVuIEpl
bm5pbmdzOg0KDQpJJ20gbm90IGdldHRpbmcgdGhlIHByb2JsZW0gaGVyZSBhbmQgbWFuZGF0aW5n
IDY5MDQgaXMgbm90IGFuIGVhc3kNCnRoaW5nIHRvIGRvLg0KDQpTbywgbGV0cyBiZSBjbGVhciBv
biB3aGF0IEkgaGF2ZSBwcm9wb3NlZC4gRm9yIGJ1bmRsZSBpbiBnZW5lcmFsIGl0IGlzIFJFQ09N
TUVOREVEIHRvIGVuY3J5cHQgTUlEcyBpbiBSVFAgaGVhZGVyIGV4dGVuc2lvbnMuIEkgaGF2ZSBh
bHNvIHByb3Bvc2VkIHRoYXQgZm9yIFJUQ1dlYiBpbXBsZW1lbnRhdGlvbiBhbmQgdXNlIHNob3Vs
ZCBiZSBtYW5kYXRlZC4gSSB3YXMgbm90IGNsZWFyIGluIHdoYXQgYXBwbGllcyB3aGVuIGFuIFdl
YlJUQyBlbmRwb2ludCB0YWxrcyB0byBhIGxlZ2FjeSBlbmRwb2ludCB3aGF0IGlzIGV4cGVjdGVk
IGhlcmUuIEkgZ3Vlc3MgdGhpcyBpcyB0aGUgdGhvcm55IGlzc3VlLg0KDQpSRkMgNzkwNCAoU0RF
UyBoZWFkZXIgZXh0ZW5zaW9ucykgc2F5czoNCg0KDQogICBJbiBSVFAgc2Vzc2lvbnMgd2hlcmUg
YW55IHR5cGUgb2YgY29uZmlkZW50aWFsaXR5IHByb3RlY3Rpb24gaXMNCiAgIGVuYWJsZWQgZm9y
IFJUQ1AsIHRoZSBTREVTIGl0ZW0gaGVhZGVyIGV4dGVuc2lvbnMgTVVTVCBhbHNvIGJlDQogICBw
cm90ZWN0ZWQuICBUaGlzIGltcGxpZXMgdGhhdCB0byBwcm92aWRlIGNvbmZpZGVudGlhbGl0eSwg
dXNlcnMgb2YNCiAgIHRoZSBTZWN1cmUgUmVhbC10aW1lIFRyYW5zcG9ydCBQcm90b2NvbCAoU1JU
UCkgbmVlZCB0byBpbXBsZW1lbnQgYW5kDQogICB1c2UgZW5jcnlwdGVkIGhlYWRlciBleHRlbnNp
b25zIHBlciBbUkZDNjkwNDxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNjkwND5dLg0K
DQpUaGlzIHdhcyBhZnRlciBhIGZhaXIgYml0IG9mIGJhY2stYW5kLWZvcnRoIHdpdGggdGhlIHNl
Y3VyaXR5IEFEcy4gIE1JRCBpcyBhIDc5MDQgaGVhZGVyIGV4dGVuc2lvbiwgc28gSSBkb27igJl0
IHRoaW5rIEJVTkRMRSBjYW4gb3ZlcnJpZGUgdGhpcyBNVVNULg0KDQoNCkknbSBub3QgZ2V0dGlu
ZyB3aGF0IHRoZSBpc3N1ZSBpcyBoZXJlLiBJZiBtaWQgYXJlIHJhbmRvbSwgb3IgYXJlDQpqdXN0
IGEgY291bnQgb2Ygbid0aCBtLWxpbmUgaW4gdGhlIHNkcCwgd2hhdCBpcyB0aGUgcHJvYmxlbSB3
aXRoDQpleHBvc2luZyB0aGVtIHRvIHBlb3BsZSBhcmUgZ2V0dGluZyB0aGUgbWVkaWE/DQoNClRo
ZSBpc3N1ZSBpcyB0aGF0IHRoZXNlIGlkZW50aWZpZXJzIGFyZSBnb2luZyBmcm9tIGhhdmluZyBv
bmx5IGJlZW4gdmlzaWFibGUgaW4gdGhlIHNpZ25hbGxpbmcgbWVzc2FnZXMgdG8gYmUgdmlzaWJs
ZSBhbHNvIG9uIHRoZSBSVFAgbWVkaWEgcGxhbmUuIEFuZCB3aXRob3V0IFJGQzY5MDQgZXZlbiBp
ZiBvbmUgdXNlcyBTUlRQLCB0aGVzZSB2YWx1ZXMgYXJlIGV4cG9zZWQuIFRoaXMgaGF2ZSBzZXZl
cmFsIGRpZmZlcmVudCBlZmZlY3RzIGFzIEkgc2VlIGl0LiBTbyBpZiB0aGUgZ2VuZXJhdGlvbiBh
bGdvcml0aG0gYXJlIG5vdCBzdHJpY3RseSBkZWZpbmVkLCB0aGUgaW1wbGVtZW50YXRpb24gZ2V0
cyBwb3NzaWJsZSB0byBmaW5nZXJwcmludC4gSW4gYWRkaXRpb24gdGhlIGRldmljZSBnZXRzIHRv
IGJlIGZpbmdlcnByaW50ZWQgYmFzZWQgb24gdGhlIG51bWJlciBvZiBzdHJlYW1zIG9mZmVyZWQg
YW5kIHRoZWlyIGlkZW50aWZpZXJzLiBUaHVzLCBpdCBpcyBub3Qgb25seSB3aGF0IGlzIGFjdHVh
bGx5IHVzZWQgdGhhdCBpcyBleHBvc2VkLCBidXQgd2hhdCB3YXMgb3JpZ2luYWxseSBvZmZlcmVk
LCBpLmUuIHRoZSBmdWxsIG9mZmVyIGxlYWtzIGludG8gdW5lbmNyeXB0ZWQgZG9tYWluIG9uIHRo
ZSBtZWRpYSBwbGFuZS4gTm90ZSwgdGhpcyBsYXRlciBjYW4ndCBiZSBkZWFsdCB3aXRoIGFueSBt
aWQgaWQgY3JlYXRpb24gcnVsZXMsIGl0IHdpbGwgc3RpbGwgbGVhay4gVGh1cyBkZXZpY2VzIHRo
YXQgaGF2ZSBtb3JlIGV4b3RpYyBjb25maWd1cmF0aW9ucyB3aGVuIGl0IGNvbWVzIHRvIG1lZGlh
IHN0cmVhbXMsIGkuZS4gbnVtYmVyIG9mIGNhbWVyYXMgZXRjIHRoaXMgY2FuIHN0aWxsIGJlIGZp
bmdlcnByaW50ZWQgYnkgcGFzc2l2ZSBhdHRhY2tzIGZyb20gdGhpcmQgcGFydGllcy4NCg0KSXQg
aXMgdGhlIHBhc3NpdmUgYXR0YWNrIGZyb20gdGhpcmQgcGFydGllcyB0aGF0IGhhcyBtZSB3b3Jy
aWVkIGhlcmUuIEEgcGVlciBpbiB0aGUgc2lnbmFsbGluZyBoYXMgbWFzc2l2ZWx5IG1vcmUgcG93
ZXJmdWwgZmluZ2VycHJpbnRpbmcsIGJ1dCB0aGF0IHJlcXVpcmVzIG9uZSB0byBiZSBpbiB0aGUg
c2lnbmFsbGluZyBjb250ZXh0LCBub3QgcGFzc2l2ZWx5IG9ic2VydmUgdHJhZmZpYyB0aGF0IGdv
ZXMgcGFzdC4NCg0KDQpDaGVlcnMNCg0KTWFnbnVzDQoNCg0KDQoNCg0KT24gT2N0IDYsIDIwMTYs
IGF0IDc6MzkgQU0sIE1hZ251cyBXZXN0ZXJsdW5kDQo8bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nz
b24uY29tPG1haWx0bzptYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20+PiB3cm90ZToNCg0K
RGVuIDIwMTYtMTAtMDYga2wuIDE0OjQ5LCBza3JldiBDaHJpc3RlciBIb2xtYmVyZzoNCg0KSGks
DQoNCk1hZ251cyBzdWdnZXN0ZWQgdXNhZ2Ugb2YgUkZDIDY5MDQgZm9yIGVuY3J5cHRpb24gb2Yg
dGhlIFJUUCBTREVTDQpoZWFkZXIgZXh0ZW5zaW9uIGZvciBNSUQuIEkgZ3Vlc3MgaXQgd291bGQg
YmUgYSBTSFVPTEQ/DQoNCkluIGFkZGl0aW9uLCB3ZSB3b3VsZCBzYXkgdGhhdCBhIGNvcnJlc3Bv
bmRpbmcgbGV2ZWwgb2Ygc2VjdXJpdHkNCm11c3QgYmUgYXBwbGllZCB0byB0aGUgUlRQIFNERVMg
aGVhZGVyIGV4dGVuc2lvbiBmb3IgTUlEIGFuZCB0bw0KdGhlIFJUQ1AgU0RFUyBNSUQgaXRlbS4N
Cg0KQW55IG9waW5pb25zPw0KDQpJIHRoaW5rIHRoaXMgaXMgZmluZSBzb2x1dGlvbiB0byB0aGlz
IGlzc3VlLiBJIHdvdWxkIHByb2JhYmx5DQpmb3JtdWxhdGUgdGhlIHNlY3VyaXR5IGNvbnNpZGVy
YXRpb25zIGxpa2UgdGhpcy4NCg0KVGhlIGlkZW50ZmljYXRpb24tdGFnIHdoZW4gaW5jbHVkZWQg
aW4gdGhlIFJUUCBNSUQgU0RFUyBpdGVtLA0KaW5kZXBlbmRlbnQgb2YgdHJhbnNwb3J0LCBSVENQ
IFNERVMgcGFja2V0IG9yIFJUUCBoZWFkZXIgZXh0ZW5zaW9uLA0KY2FuIGV4cG9zZSB0aGUgdmFs
dWUgdG8gcGFydGllcyBiZXlvbmQgdGhlIHNpZ25hbGluZyBjaGFpbi4NClRoZXJlZm9yZSwgdGhl
IGlkZW50aWZpY2F0aW9uLXRhZyBNVVNUIE5PVCBjb250YWluIGFueSB1c2VyIHJlbGF0ZWQNCmlu
Zm9ybWF0aW9uLiBIb3dldmVyLCB0aGUgaW1wbGVtZW50YXRpb24ncyBtZXRob2QgZm9yIGdlbmVy
YXRpbmcNCmlkZW50ZmljYXRpb24tdGFncyBjb21iaW5lZCB3aXRoIGhhcmR3YXJlIGNvbmZpZ3Vy
YXRpb24gY2FuIGVuYWJsZQ0KZmluZ2VycHJpbnRpbmcgb2YgdGhlIGVuZHBvaW50IGRldmljZSBh
bmQgdGh1cyBpdHMgdXNlci4gQXMgdGhlDQppZGVudGlmaWNhdGlvbi10YWcgaXMgYWxzbyB1c2Vk
IHRvIHJvdXRlIHRoZSBtZWRpYSBzdHJlYW0gdG8gdGhlDQpyaWdodCBhcHBsaWNhdGlvbiBmdW5j
dGlvbmFsaXR5IGl0IGlzIGFsc28gaW1wb3J0YW50IHRoYXQgdGhlIHZhbHVlDQpyZWNlaXZlZCBp
cyB0aGUgb25lIGludGVuZGVkIGJ5IHRoZSBzZW5kZXIsIHRodXMgaW50ZWdyaXR5IGFuZCB0aGUN
CmF1dGhlbnRpY2l0eSBvZiB0aGUgc291cmNlIGFyZSBpbXBvcnRhbnQgdG8gcHJldmVudCBkZW5p
YWwgb2YNCnNlcnZpY2Ugb24gdGhlIGFwcGxpY2F0aW9uLiBBdCBsZWFzdCB0byBwcmV2ZW50IHRo
aXJkIHBhcnRpZXMgZnJvbQ0KbW9kaWZ5aW5nIHRoZSBpZGVudGlmaWNhdGlvbi10YWcgdmFsdWUu
DQoNCkR1ZSB0byB0aGUgc2VjdXJpdHkgcmlza3MgYXNzb2NpYXRlZCB3aXRoIHRoZSBNSUQgdmFs
dWVzIGluIFJUUCBhbmQNClJUQ1AgaXQgaXMgc3Ryb25nbHkgUkVDT01NRU5ERUQgdGhhdCB0aGUg
TUlEIFNERVMgaXRlbSBpcyBib3RoDQpjb25maWRlbnRpYWxpdHkgcHJvdGVjdGVkIGFzIHdlbGwg
YXMgc291cmNlIGF1dGhlbnRpY2F0ZWQgd2hlbg0KdHJhbnNwb3J0ZWQgaW4gZWl0aGVyIFJUQ1Ag
b3IgUlRQIGhlYWRlciBleHRlbnNpb25zLiBUaGUgc2VjdXJpdHkNCm1lY2hhbmlzbXMgdXNlZCBT
SEFMTCBwcm92aWRlIGNvcnJlc3BvbmRpbmcgbGV2ZWxzIG9mIHNlY3VyaXR5IGZvcg0KYm90aCBS
VFAgaGVhZGVyIGV4dGVuc2lvbnMgYW5kIFJUQ1AuIENvbmZpZGVudGlhbGl0eSBtZWNoYW5pc21z
IGZvcg0KUlRQL1JUQ1AgYXJlIGRpc2N1c3NlZCBpbiBPcHRpb25zIGZvciBTZWN1cmluZyBSVFAg
U2Vzc2lvbnMNCltSRkM3MjAxXSwgZm9yIGV4YW1wbGUgU1JUUCBbUkZDMzcxMV0gd2l0aCBTUlRD
UCBlbmNyeXB0aW9uIGVuYWJsZWQNCmNvbWJpbmVkIHdpdGggW1JGQzY5MDRdIGNhbiBwcm92aWRl
IHRoZSBuZWNlc3Nhcnkgc2VjdXJpdHkNCmZ1bmN0aW9ucy4NCg0KDQpDaGVlcnMNCg0KTWFnbnVz
IFdlc3Rlcmx1bmQNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQoNClNlcnZpY2VzLCBNZWRpYSBhbmQgTmV0
d29yayBmZWF0dXJlcywgRXJpY3Nzb24gUmVzZWFyY2ggRUFCL1RYTQ0KLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K
DQoNCkVyaWNzc29uIEFCICAgICAgICAgICAgICAgICB8IFBob25lICArNDYgMTAgNzE0ODI4Nw0K
RsOkcsO2Z2F0YW4gNiAgICAgICAgICAgICAgICAgfCBNb2JpbGUgKzQ2IDczIDA5NDkwNzkgU0Ut
MTY0IDgwDQpTdG9ja2hvbG0sIFN3ZWRlbiB8IG1haWx0bzogbWFnbnVzLndlc3Rlcmx1bmRAZXJp
Y3Nzb24uY29tPG1haWx0bzptYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20+DQotLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KbW11c2ljIG1haWxpbmcgbGlzdCBtbXVzaWNAaWV0Zi5vcmc8bWFpbHRvOm1tdXNpY0Bp
ZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljDQoN
Cg0KDQoNCi0tDQoNCk1hZ251cyBXZXN0ZXJsdW5kDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClNlcnZpY2Vz
LCBNZWRpYSBhbmQgTmV0d29yayBmZWF0dXJlcywgRXJpY3Nzb24gUmVzZWFyY2ggRUFCL1RYTQ0K
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KRXJpY3Nzb24gQUIgICAgICAgICAgICAgICAgIHwgUGhvbmUgICs0NiAx
MCA3MTQ4Mjg3DQpGw6Ryw7ZnYXRhbiA2ICAgICAgICAgICAgICAgICB8IE1vYmlsZSArNDYgNzMg
MDk0OTA3OQ0KU0UtMTY0IDgwIFN0b2NraG9sbSwgU3dlZGVuIHwgbWFpbHRvOiBtYWdudXMud2Vz
dGVybHVuZEBlcmljc3Nvbi5jb208bWFpbHRvOm1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNv
bT4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCm1tdXNpYyBtYWlsaW5nIGxpc3QNCm1tdXNpY0BpZXRmLm9yZzxtYWlsdG86
bW11c2ljQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9t
bXVzaWMNCg0K

--_000_FEB4A43FB38F43C3A3D7345C97AC73DCvidyocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <8BCB98BB7A65A04E87E9D9F2D70A3CF7@vidyo.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGRpdj4N
CjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5PbiBPY3Qg
NywgMjAxNiwgYXQgNDo0MSBBTSwgTWFnbnVzIFdlc3Rlcmx1bmQgJmx0OzxhIGhyZWY9Im1haWx0
bzptYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20iIGNsYXNzPSIiPm1hZ251cy53ZXN0ZXJs
dW5kQGVyaWNzc29uLmNvbTwvYT4mZ3Q7IHdyb3RlOjwvZGl2Pg0KPGJyIGNsYXNzPSJBcHBsZS1p
bnRlcmNoYW5nZS1uZXdsaW5lIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPkRlbiAy
MDE2LTEwLTA2IGtsLiAyMzo1OSwgc2tyZXYgQ3VsbGVuIEplbm5pbmdzOjxiciBjbGFzcz0iIj4N
CjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCkknbSBub3Qg
Z2V0dGluZyB0aGUgcHJvYmxlbSBoZXJlIGFuZCBtYW5kYXRpbmcgNjkwNCBpcyBub3QgYW4gZWFz
eTxiciBjbGFzcz0iIj4NCnRoaW5nIHRvIGRvLjxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4N
CjxiciBjbGFzcz0iIj4NClNvLCBsZXRzIGJlIGNsZWFyIG9uIHdoYXQgSSBoYXZlIHByb3Bvc2Vk
LiBGb3IgYnVuZGxlIGluIGdlbmVyYWwgaXQgaXMgUkVDT01NRU5ERUQgdG8gZW5jcnlwdCBNSURz
IGluIFJUUCBoZWFkZXIgZXh0ZW5zaW9ucy4gSSBoYXZlIGFsc28gcHJvcG9zZWQgdGhhdCBmb3Ig
UlRDV2ViIGltcGxlbWVudGF0aW9uIGFuZCB1c2Ugc2hvdWxkIGJlIG1hbmRhdGVkLiBJIHdhcyBu
b3QgY2xlYXIgaW4gd2hhdCBhcHBsaWVzIHdoZW4gYW4gV2ViUlRDIGVuZHBvaW50DQogdGFsa3Mg
dG8gYSBsZWdhY3kgZW5kcG9pbnQgd2hhdCBpcyBleHBlY3RlZCBoZXJlLiBJIGd1ZXNzIHRoaXMg
aXMgdGhlIHRob3JueSBpc3N1ZS48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9j
a3F1b3RlPg0KPGRpdj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXY+UkZDIDc5MDQgKFNERVMg
aGVhZGVyIGV4dGVuc2lvbnMpIHNheXM6PC9kaXY+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2
Pg0KPGRpdj4NCjxwcmUgY2xhc3M9Im5ld3BhZ2UiPiAgIEluIFJUUCBzZXNzaW9ucyB3aGVyZSBh
bnkgdHlwZSBvZiBjb25maWRlbnRpYWxpdHkgcHJvdGVjdGlvbiBpcw0KICAgZW5hYmxlZCBmb3Ig
UlRDUCwgdGhlIFNERVMgaXRlbSBoZWFkZXIgZXh0ZW5zaW9ucyBNVVNUIGFsc28gYmUNCiAgIHBy
b3RlY3RlZC4gIFRoaXMgaW1wbGllcyB0aGF0IHRvIHByb3ZpZGUgY29uZmlkZW50aWFsaXR5LCB1
c2VycyBvZg0KICAgdGhlIFNlY3VyZSBSZWFsLXRpbWUgVHJhbnNwb3J0IFByb3RvY29sIChTUlRQ
KSBuZWVkIHRvIGltcGxlbWVudCBhbmQNCiAgIHVzZSBlbmNyeXB0ZWQgaGVhZGVyIGV4dGVuc2lv
bnMgcGVyIFs8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNjkwNCIgdGl0
bGU9IiZxdW90O0VuY3J5cHRpb24gb2YgSGVhZGVyIEV4dGVuc2lvbnMgaW4gdGhlIFNlY3VyZSBS
ZWFsLXRpbWUgVHJhbnNwb3J0IFByb3RvY29sIChTUlRQKSZxdW90OyIgY2xhc3M9IiI+UkZDNjkw
NDwvYT5dLjwvcHJlPg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYg
Y2xhc3M9IiI+VGhpcyB3YXMgYWZ0ZXIgYSBmYWlyIGJpdCBvZiBiYWNrLWFuZC1mb3J0aCB3aXRo
IHRoZSBzZWN1cml0eSBBRHMuICZuYnNwO01JRCBpcyBhIDc5MDQgaGVhZGVyIGV4dGVuc2lvbiwg
c28gSSBkb27igJl0IHRoaW5rIEJVTkRMRSBjYW4gb3ZlcnJpZGUgdGhpcyBNVVNULjwvZGl2Pg0K
PC9kaXY+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPGJsb2Nr
cXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0i
Ij4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPkknbSBub3QgZ2V0dGluZyB3aGF0
IHRoZSBpc3N1ZSBpcyBoZXJlLiBJZiBtaWQgYXJlIHJhbmRvbSwgb3IgYXJlPGJyIGNsYXNzPSIi
Pg0KanVzdCBhIGNvdW50IG9mIG4ndGggbS1saW5lIGluIHRoZSBzZHAsIHdoYXQgaXMgdGhlIHBy
b2JsZW0gd2l0aDxiciBjbGFzcz0iIj4NCmV4cG9zaW5nIHRoZW0gdG8gcGVvcGxlIGFyZSBnZXR0
aW5nIHRoZSBtZWRpYT88YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQo8YnIgY2xhc3M9IiI+
DQpUaGUgaXNzdWUgaXMgdGhhdCB0aGVzZSBpZGVudGlmaWVycyBhcmUgZ29pbmcgZnJvbSBoYXZp
bmcgb25seSBiZWVuIHZpc2lhYmxlIGluIHRoZSBzaWduYWxsaW5nIG1lc3NhZ2VzIHRvIGJlIHZp
c2libGUgYWxzbyBvbiB0aGUgUlRQIG1lZGlhIHBsYW5lLiBBbmQgd2l0aG91dCBSRkM2OTA0IGV2
ZW4gaWYgb25lIHVzZXMgU1JUUCwgdGhlc2UgdmFsdWVzIGFyZSBleHBvc2VkLiBUaGlzIGhhdmUg
c2V2ZXJhbCBkaWZmZXJlbnQgZWZmZWN0cyBhcyBJDQogc2VlIGl0LiBTbyBpZiB0aGUgZ2VuZXJh
dGlvbiBhbGdvcml0aG0gYXJlIG5vdCBzdHJpY3RseSBkZWZpbmVkLCB0aGUgaW1wbGVtZW50YXRp
b24gZ2V0cyBwb3NzaWJsZSB0byBmaW5nZXJwcmludC4gSW4gYWRkaXRpb24gdGhlIGRldmljZSBn
ZXRzIHRvIGJlIGZpbmdlcnByaW50ZWQgYmFzZWQgb24gdGhlIG51bWJlciBvZiBzdHJlYW1zIG9m
ZmVyZWQgYW5kIHRoZWlyIGlkZW50aWZpZXJzLiBUaHVzLCBpdCBpcyBub3Qgb25seSB3aGF0IGlz
IGFjdHVhbGx5DQogdXNlZCB0aGF0IGlzIGV4cG9zZWQsIGJ1dCB3aGF0IHdhcyBvcmlnaW5hbGx5
IG9mZmVyZWQsIGkuZS4gdGhlIGZ1bGwgb2ZmZXIgbGVha3MgaW50byB1bmVuY3J5cHRlZCBkb21h
aW4gb24gdGhlIG1lZGlhIHBsYW5lLiBOb3RlLCB0aGlzIGxhdGVyIGNhbid0IGJlIGRlYWx0IHdp
dGggYW55IG1pZCBpZCBjcmVhdGlvbiBydWxlcywgaXQgd2lsbCBzdGlsbCBsZWFrLiBUaHVzIGRl
dmljZXMgdGhhdCBoYXZlIG1vcmUgZXhvdGljIGNvbmZpZ3VyYXRpb25zDQogd2hlbiBpdCBjb21l
cyB0byBtZWRpYSBzdHJlYW1zLCBpLmUuIG51bWJlciBvZiBjYW1lcmFzIGV0YyB0aGlzIGNhbiBz
dGlsbCBiZSBmaW5nZXJwcmludGVkIGJ5IHBhc3NpdmUgYXR0YWNrcyBmcm9tIHRoaXJkIHBhcnRp
ZXMuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KSXQgaXMgdGhlIHBhc3NpdmUgYXR0YWNr
IGZyb20gdGhpcmQgcGFydGllcyB0aGF0IGhhcyBtZSB3b3JyaWVkIGhlcmUuIEEgcGVlciBpbiB0
aGUgc2lnbmFsbGluZyBoYXMgbWFzc2l2ZWx5IG1vcmUgcG93ZXJmdWwgZmluZ2VycHJpbnRpbmcs
IGJ1dCB0aGF0IHJlcXVpcmVzIG9uZSB0byBiZSBpbiB0aGUgc2lnbmFsbGluZyBjb250ZXh0LCBu
b3QgcGFzc2l2ZWx5IG9ic2VydmUgdHJhZmZpYyB0aGF0IGdvZXMgcGFzdC48YnIgY2xhc3M9IiI+
DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpDaGVlcnM8YnIgY2xhc3M9IiI+DQo8YnIg
Y2xhc3M9IiI+DQpNYWdudXM8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9
IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8YnIg
Y2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0i
Ij5PbiBPY3QgNiwgMjAxNiwgYXQgNzozOSBBTSwgTWFnbnVzIFdlc3Rlcmx1bmQ8YnIgY2xhc3M9
IiI+DQombHQ7PGEgaHJlZj0ibWFpbHRvOm1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbSIg
Y2xhc3M9IiI+bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPC9hPiZndDsgd3JvdGU6PGJy
IGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KRGVuIDIwMTYtMTAtMDYga2wuIDE0OjQ5LCBza3Jl
diBDaHJpc3RlciBIb2xtYmVyZzo8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRl
IiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQpIaSw8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+
DQpNYWdudXMgc3VnZ2VzdGVkIHVzYWdlIG9mIFJGQyA2OTA0IGZvciBlbmNyeXB0aW9uIG9mIHRo
ZSBSVFAgU0RFUzxiciBjbGFzcz0iIj4NCmhlYWRlciBleHRlbnNpb24gZm9yIE1JRC4gSSBndWVz
cyBpdCB3b3VsZCBiZSBhIFNIVU9MRD88YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpJbiBh
ZGRpdGlvbiwgd2Ugd291bGQgc2F5IHRoYXQgYSBjb3JyZXNwb25kaW5nIGxldmVsIG9mIHNlY3Vy
aXR5PGJyIGNsYXNzPSIiPg0KbXVzdCBiZSBhcHBsaWVkIHRvIHRoZSBSVFAgU0RFUyBoZWFkZXIg
ZXh0ZW5zaW9uIGZvciBNSUQgYW5kIHRvPGJyIGNsYXNzPSIiPg0KdGhlIFJUQ1AgU0RFUyBNSUQg
aXRlbS48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpBbnkgb3BpbmlvbnM/PGJyIGNsYXNz
PSIiPg0KPC9ibG9ja3F1b3RlPg0KPGJyIGNsYXNzPSIiPg0KSSB0aGluayB0aGlzIGlzIGZpbmUg
c29sdXRpb24gdG8gdGhpcyBpc3N1ZS4gSSB3b3VsZCBwcm9iYWJseTxiciBjbGFzcz0iIj4NCmZv
cm11bGF0ZSB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgbGlrZSB0aGlzLjxiciBjbGFzcz0i
Ij4NCjxiciBjbGFzcz0iIj4NClRoZSBpZGVudGZpY2F0aW9uLXRhZyB3aGVuIGluY2x1ZGVkIGlu
IHRoZSBSVFAgTUlEIFNERVMgaXRlbSw8YnIgY2xhc3M9IiI+DQppbmRlcGVuZGVudCBvZiB0cmFu
c3BvcnQsIFJUQ1AgU0RFUyBwYWNrZXQgb3IgUlRQIGhlYWRlciBleHRlbnNpb24sPGJyIGNsYXNz
PSIiPg0KY2FuIGV4cG9zZSB0aGUgdmFsdWUgdG8gcGFydGllcyBiZXlvbmQgdGhlIHNpZ25hbGlu
ZyBjaGFpbi48YnIgY2xhc3M9IiI+DQpUaGVyZWZvcmUsIHRoZSBpZGVudGlmaWNhdGlvbi10YWcg
TVVTVCBOT1QgY29udGFpbiBhbnkgdXNlciByZWxhdGVkPGJyIGNsYXNzPSIiPg0KaW5mb3JtYXRp
b24uIEhvd2V2ZXIsIHRoZSBpbXBsZW1lbnRhdGlvbidzIG1ldGhvZCBmb3IgZ2VuZXJhdGluZzxi
ciBjbGFzcz0iIj4NCmlkZW50ZmljYXRpb24tdGFncyBjb21iaW5lZCB3aXRoIGhhcmR3YXJlIGNv
bmZpZ3VyYXRpb24gY2FuIGVuYWJsZTxiciBjbGFzcz0iIj4NCmZpbmdlcnByaW50aW5nIG9mIHRo
ZSBlbmRwb2ludCBkZXZpY2UgYW5kIHRodXMgaXRzIHVzZXIuIEFzIHRoZTxiciBjbGFzcz0iIj4N
CmlkZW50aWZpY2F0aW9uLXRhZyBpcyBhbHNvIHVzZWQgdG8gcm91dGUgdGhlIG1lZGlhIHN0cmVh
bSB0byB0aGU8YnIgY2xhc3M9IiI+DQpyaWdodCBhcHBsaWNhdGlvbiBmdW5jdGlvbmFsaXR5IGl0
IGlzIGFsc28gaW1wb3J0YW50IHRoYXQgdGhlIHZhbHVlPGJyIGNsYXNzPSIiPg0KcmVjZWl2ZWQg
aXMgdGhlIG9uZSBpbnRlbmRlZCBieSB0aGUgc2VuZGVyLCB0aHVzIGludGVncml0eSBhbmQgdGhl
PGJyIGNsYXNzPSIiPg0KYXV0aGVudGljaXR5IG9mIHRoZSBzb3VyY2UgYXJlIGltcG9ydGFudCB0
byBwcmV2ZW50IGRlbmlhbCBvZjxiciBjbGFzcz0iIj4NCnNlcnZpY2Ugb24gdGhlIGFwcGxpY2F0
aW9uLiBBdCBsZWFzdCB0byBwcmV2ZW50IHRoaXJkIHBhcnRpZXMgZnJvbTxiciBjbGFzcz0iIj4N
Cm1vZGlmeWluZyB0aGUgaWRlbnRpZmljYXRpb24tdGFnIHZhbHVlLjxiciBjbGFzcz0iIj4NCjxi
ciBjbGFzcz0iIj4NCkR1ZSB0byB0aGUgc2VjdXJpdHkgcmlza3MgYXNzb2NpYXRlZCB3aXRoIHRo
ZSBNSUQgdmFsdWVzIGluIFJUUCBhbmQ8YnIgY2xhc3M9IiI+DQpSVENQIGl0IGlzIHN0cm9uZ2x5
IFJFQ09NTUVOREVEIHRoYXQgdGhlIE1JRCBTREVTIGl0ZW0gaXMgYm90aDxiciBjbGFzcz0iIj4N
CmNvbmZpZGVudGlhbGl0eSBwcm90ZWN0ZWQgYXMgd2VsbCBhcyBzb3VyY2UgYXV0aGVudGljYXRl
ZCB3aGVuPGJyIGNsYXNzPSIiPg0KdHJhbnNwb3J0ZWQgaW4gZWl0aGVyIFJUQ1Agb3IgUlRQIGhl
YWRlciBleHRlbnNpb25zLiBUaGUgc2VjdXJpdHk8YnIgY2xhc3M9IiI+DQptZWNoYW5pc21zIHVz
ZWQgU0hBTEwgcHJvdmlkZSBjb3JyZXNwb25kaW5nIGxldmVscyBvZiBzZWN1cml0eSBmb3I8YnIg
Y2xhc3M9IiI+DQpib3RoIFJUUCBoZWFkZXIgZXh0ZW5zaW9ucyBhbmQgUlRDUC4gQ29uZmlkZW50
aWFsaXR5IG1lY2hhbmlzbXMgZm9yPGJyIGNsYXNzPSIiPg0KUlRQL1JUQ1AgYXJlIGRpc2N1c3Nl
ZCBpbiBPcHRpb25zIGZvciBTZWN1cmluZyBSVFAgU2Vzc2lvbnM8YnIgY2xhc3M9IiI+DQpbUkZD
NzIwMV0sIGZvciBleGFtcGxlIFNSVFAgW1JGQzM3MTFdIHdpdGggU1JUQ1AgZW5jcnlwdGlvbiBl
bmFibGVkPGJyIGNsYXNzPSIiPg0KY29tYmluZWQgd2l0aCBbUkZDNjkwNF0gY2FuIHByb3ZpZGUg
dGhlIG5lY2Vzc2FyeSBzZWN1cml0eTxiciBjbGFzcz0iIj4NCmZ1bmN0aW9ucy48YnIgY2xhc3M9
IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpDaGVlcnM8YnIgY2xhc3M9IiI+DQo8
YnIgY2xhc3M9IiI+DQpNYWdudXMgV2VzdGVybHVuZDxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0i
Ij4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS08YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9
IiI+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQpTZXJ2aWNlcywgTWVkaWEgYW5kIE5l
dHdvcmsgZmVhdHVyZXMsIEVyaWNzc29uIFJlc2VhcmNoIEVBQi9UWE08YnIgY2xhc3M9IiI+DQo8
YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUi
IGNsYXNzPSIiPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIg
Y2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQpFcmljc3NvbiBBQiAmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDt8IFBob25lICZuYnNwOyYjNDM7NDYg
MTAgNzE0ODI4NzxiciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIi
Pg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+RsOkcsO2Z2F0YW4gNiAmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDt8IE1vYmlsZSAmIzQzOzQ2IDczIDA5NDkw
NzkgU0UtMTY0IDgwPGJyIGNsYXNzPSIiPg0KU3RvY2tob2xtLCBTd2VkZW4gfCBtYWlsdG86IDxh
IGhyZWY9Im1haWx0bzptYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20iIGNsYXNzPSIiPg0K
bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPC9hPjxiciBjbGFzcz0iIj4NCi0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS08YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xh
c3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQpfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXzxiciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5
cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+bW11
c2ljIG1haWxpbmcgbGlzdCA8YSBocmVmPSJtYWlsdG86bW11c2ljQGlldGYub3JnIiBjbGFzcz0i
Ij4NCm1tdXNpY0BpZXRmLm9yZzwvYT48YnIgY2xhc3M9IiI+DQo8YSBocmVmPSJodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYyIgY2xhc3M9IiI+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWM8L2E+PGJyIGNsYXNzPSIiPg0KPC9ibG9j
a3F1b3RlPg0KPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KPGJy
IGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KLS0gPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIi
Pg0KTWFnbnVzIFdlc3Rlcmx1bmQ8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQotLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tPGJyIGNsYXNzPSIiPg0KU2VydmljZXMsIE1lZGlhIGFuZCBOZXR3b3JrIGZlYXR1cmVz
LCBFcmljc3NvbiBSZXNlYXJjaCBFQUIvVFhNPGJyIGNsYXNzPSIiPg0KLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxi
ciBjbGFzcz0iIj4NCkVyaWNzc29uIEFCICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwO3wgUGhvbmUgJm5ic3A7JiM0Mzs0NiAxMCA3MTQ4Mjg3PGJyIGNsYXNzPSIiPg0KRsOk
csO2Z2F0YW4gNiAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDt8IE1vYmls
ZSAmIzQzOzQ2IDczIDA5NDkwNzk8YnIgY2xhc3M9IiI+DQpTRS0xNjQgODAgU3RvY2tob2xtLCBT
d2VkZW4gfCBtYWlsdG86IDxhIGhyZWY9Im1haWx0bzptYWdudXMud2VzdGVybHVuZEBlcmljc3Nv
bi5jb20iIGNsYXNzPSIiPg0KbWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPC9hPjxiciBj
bGFzcz0iIj4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxiciBjbGFzcz0iIj4N
Cm1tdXNpYyBtYWlsaW5nIGxpc3Q8YnIgY2xhc3M9IiI+DQo8YSBocmVmPSJtYWlsdG86bW11c2lj
QGlldGYub3JnIiBjbGFzcz0iIj5tbXVzaWNAaWV0Zi5vcmc8L2E+PGJyIGNsYXNzPSIiPg0KaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWM8YnIgY2xhc3M9IiI+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8YnIgY2xhc3M9IiI+DQo8L2Jv
ZHk+DQo8L2h0bWw+DQo=

--_000_FEB4A43FB38F43C3A3D7345C97AC73DCvidyocom_--


From nobody Fri Oct  7 07:04:45 2016
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 5B685129590; Fri,  7 Oct 2016 07:04:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147584908036.8975.395520925893381410.idtracker@ietfa.amsl.com>
Date: Fri, 07 Oct 2016 07:04:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/SfNKB9qe5b_sT9xhYhwDdiP6POI>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sctp-sdp-18.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 14:04:40 -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 of the IETF.

        Title           : Session Description Protocol (SDP) Offer/Answer Procedures For Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport.
        Authors         : Christer Holmberg
                          Roman Shpount
                          Salvatore Loreto
                          Gonzalo Camarillo
	Filename        : draft-ietf-mmusic-sctp-sdp-18.txt
	Pages           : 24
	Date            : 2016-10-07

Abstract:
   The Stream Control Transmission Protocol (SCTP) is a transport
   protocol used to establish associations between two endpoints.
   draft-ietf-tsvwg-sctp-dtls-encaps-09 specifies how SCTP can be used
   on top of the Datagram Transport Layer Security (DTLS) protocol,
   referred to as SCTP-over-DTLS.

   This specification defines the following new Session Description
   Protocol (SDP) protocol identifiers (proto values):'UDP/DTLS/SCTP'
   and 'TCP/DTLS/SCTP'.  This specification also specifies how to use
   the new proto values with the SDP Offer/Answer mechanism for
   negotiating SCTP-over-DTLS associations.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-sctp-sdp-18

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


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 Oct  7 07:09:03 2016
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 E863D129606; Fri,  7 Oct 2016 07:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 k4RPFlfcnONX; Fri,  7 Oct 2016 07:09:00 -0700 (PDT)
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 C47BA1295EF; Fri,  7 Oct 2016 07:08:59 -0700 (PDT)
X-AuditID: c1b4fb30-b87ff70000000cb2-1c-57f7ac782afa
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by  (Symantec Mail Security) with SMTP id 03.31.03250.87CA7F75; Fri,  7 Oct 2016 16:08:58 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0319.002; Fri, 7 Oct 2016 16:08:56 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: draft-ietf-mmusic-sctp-sdp-18
Thread-Index: AQHSIKRXgQzqqG/GpEupMf4Ta91hyA==
Date: Fri, 7 Oct 2016 14:08:56 +0000
Message-ID: <D41D88A5.10B49%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_D41D88A510B49christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupgkeLIzCtJLcpLzFFi42KZGbHdSbdqzfdwg6mOFud3rmeymLr8MYsD k8eSJT+ZAhijuGxSUnMyy1KL9O0SuDKaDi5gL5itWNHwoqiBcZpsFyMnh4SAicThqe+YQGwh gfWMEnfey3cxcgHZixgl1k/4yN7FyMHBJmAh0f1PG6RGREBd4uveHmYQm1nAVOLhqzWMICXC ApYS3/fHQZTYSaxeO5EJwtaTWN02ixWkhEVAReLEO1OQMK+AtcTUDxNZQGxGATGJ76fWMEFM FJe49WQ+E8RlAhJL9pxnhrBFJV4+/scKYosCjfz+dTZUXFHi46t9YBcwCyRIfFhdDzFeUOLk zCcsExiFZyGZOguhahaSKogSA4n35+YzQ9jaEssWvoay9SU2fjnLCGFbS/xbsIAJWc0CRo5V jKLFqcVJuelGRnqpRZnJxcX5eXp5qSWbGIHxc3DLb4MdjC+fOx5iFOBgVOLhfRDxLVyINbGs uDL3EKMEB7OSCO++Fd/DhXhTEiurUovy44tKc1KLDzFKc7AoifOarbwfLiSQnliSmp2aWpBa BJNl4uCUamB0ffM+/oBNKNe6h+16ksztn5bNXtl2ipU995TwRjmdZ5e72r8uOvmDb57J3unu Dy4cN5MOnzbxJlvWhIVp4td2f6v4IzVjf6vFs8J1vDn1wjF3fvbxfpst7+5k6HQlVtWkONyi zfCs190ty0u6Hj1+8FneaO4p21z2Ra/Oy/rt4VH85NCw4n65EktxRqKhFnNRcSIA+PXLPJsC AAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3EQOKPq7YK2TonvvkPway78nzCM>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
Subject: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-18
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 14:09:02 -0000

--_000_D41D88A510B49christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

We=92ve submitted a new version (-18) of draft-ietf-mmusic-sctp-sdp.

Note that the draft now only covers TCP/DTLS/SCTP and UDP/DTLS/SCTP =96 pla=
in SCTP is gone. Due to the change, the title of the draft has also changed=
.

Other changes are clarifications to the association management-, O/A- and I=
CE consideration sections.

The authors would like those interested to take a look, and see whether the=
re are any major issue that need to be solved before WGLC (we actually are =
in WGLC, AFAIR, but there has been some major changes, so=85).

The good news: this draft doesn=92t update any RFCs :)

Regards,

Christer

--_000_D41D88A510B49christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <81D6F5E207F87C4FB2B8554CBF6B5853@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Hi,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
We=92ve submitted a new version (-18) of&nbsp;<span style=3D"orphans: 2; wh=
ite-space: pre-wrap; widows: 2;">draft-ietf-mmusic-sctp-sdp.</span></div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<span style=3D"orphans: 2; white-space: pre-wrap; widows: 2;"><br>
</span></div>
<div><span style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-seri=
f"><span style=3D"white-space: pre-wrap;">Note that the draft now only cove=
rs TCP/DTLS/SCTP and UDP/DTLS/SCTP =96 plain SCTP is gone. Due to the chang=
e, the title of the draft has also changed.</span></font></span></div>
<div><span style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-seri=
f"><span style=3D"white-space: pre-wrap;"><br>
</span></font></span></div>
<div><span style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-seri=
f"><span style=3D"white-space: pre-wrap;">Other changes are clarifications =
to the association management-, O/A- and ICE consideration sections.</span>=
</font></span></div>
<div><span style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-seri=
f"><span style=3D"white-space: pre-wrap;"><br>
</span></font></span></div>
<div><span style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-seri=
f"><span style=3D"white-space: pre-wrap;">The authors would like those inte=
rested to take a look, and see whether there are any major issue that need =
to be solved before WGLC (we actually
 are in WGLC, AFAIR, but there has been some major changes, so</span></font=
></span><font face=3D"Calibri,sans-serif"><span style=3D"white-space: pre-w=
rap;">=85).</span></font></div>
<div><span style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-seri=
f"><span style=3D"white-space: pre-wrap;"><br>
</span></font></span></div>
<div><span style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-seri=
f"><span style=3D"white-space: pre-wrap;">The good news: this draft doesn=
=92t update any RFCs :)</span></font></span></div>
<div><span style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-seri=
f"><span style=3D"white-space: pre-wrap;"><br>
</span></font></span></div>
<div><span style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-seri=
f"><span style=3D"white-space: pre-wrap;">Regards,</span></font></span></di=
v>
<div><span style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-seri=
f"><span style=3D"white-space: pre-wrap;"><br>
</span></font></span></div>
<div><span style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-seri=
f"><span style=3D"white-space: pre-wrap;">Christer</span></font></span></di=
v>
</body>
</html>

--_000_D41D88A510B49christerholmbergericssoncom_--


From nobody Fri Oct  7 11:23:48 2016
Return-Path: <fluffy@iii.ca>
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 1CB07128B44 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 11:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sFmNWE6s-GNs for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 11:23:41 -0700 (PDT)
Received: from smtp82.iad3a.emailsrvr.com (smtp82.iad3a.emailsrvr.com [173.203.187.82]) (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 A439B129498 for <mmusic@ietf.org>; Fri,  7 Oct 2016 11:23:41 -0700 (PDT)
Received: from smtp19.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp19.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id E518DC054E; Fri,  7 Oct 2016 14:23:40 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp19.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 44A9AC050F;  Fri,  7 Oct 2016 14:23:40 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.24.90.15] ([UNAVAILABLE]. [128.107.241.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.7); Fri, 07 Oct 2016 14:23:40 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com>
Date: Fri, 7 Oct 2016 11:23:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0D4078A-3B33-4A17-A82B-BACC0FACF8BE@iii.ca>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/sakILzev-X5NFEFQ8flYJJxq9wc>
Cc: RTCWeb IETF <rtcweb@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 18:23:43 -0000

> On Oct 7, 2016, at 1:41 AM, Magnus Westerlund =
<magnus.westerlund@ericsson.com> wrote:
>=20
> Den 2016-10-06 kl. 23:59, skrev Cullen Jennings:
>>=20
>> I'm not getting the problem here and mandating 6904 is not an easy
>> thing to do.
>=20
> So, lets be clear on what I have proposed. For bundle in general it is =
RECOMMENDED to encrypt MIDs in RTP header extensions. I have also =
proposed that for RTCWeb implementation and use should be mandated. I =
was not clear in what applies when an WebRTC endpoint talks to a legacy =
endpoint what is expected here. I guess this is the thorny issue.
>=20
>>=20
>> I'm not getting what the issue is here. If mid are random, or are
>> just a count of n'th m-line in the sdp, what is the problem with
>> exposing them to people are getting the media?
>=20
> The issue is that these identifiers are going from having only been =
visiable in the signalling messages to be visible also on the RTP media =
plane. And without RFC6904 even if one uses SRTP, these values are =
exposed. This have several different effects as I see it. So if the =
generation algorithm are not strictly defined, the implementation gets =
possible to fingerprint. In addition the device gets to be fingerprinted =
based on the number of streams offered and their identifiers. Thus, it =
is not only what is actually used that is exposed, but what was =
originally offered, i.e. the full offer leaks into unencrypted domain on =
the media plane. Note, this later can't be dealt with any mid id =
creation rules, it will still leak. Thus devices that have more exotic =
configurations when it comes to media streams, i.e. number of cameras =
etc this can still be fingerprinted by passive attacks from third =
parties.
>=20
> It is the passive attack from third parties that has me worried here. =
A peer in the signalling has massively more powerful fingerprinting, but =
that requires one to be in the signalling context, not passively observe =
traffic that goes past.
>=20

I'm still not getting the fingerprint problem. How is this different =
than PT and SSRC. Yes, I agree the MID and RID - which were always =
intended to go in the RTP packet need to be generated not to have =
sensitive information in them.=20


From nobody Fri Oct  7 11:34:33 2016
Return-Path: <ekr@rtfm.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 99D881296BF for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 11:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ZLSztzf3PfY for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 11:34:29 -0700 (PDT)
Received: from mail-yb0-x232.google.com (mail-yb0-x232.google.com [IPv6:2607:f8b0:4002:c09::232]) (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 2680F1295DC for <mmusic@ietf.org>; Fri,  7 Oct 2016 11:34:29 -0700 (PDT)
Received: by mail-yb0-x232.google.com with SMTP id e20so19048392ybb.0 for <mmusic@ietf.org>; Fri, 07 Oct 2016 11:34:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IyrMTrl5CRJ2yLYOr4vGGEV3ESJvvXX+4ahgGhDzzQs=; b=aySU/5Trae9jJURzUSTCho28Mi12L0nnykbKm7uUFE/AYnIsEOdIXYChvlpaCIyxP1 lQ62Zfl4PgYDOu6SypzEHjNvS43+SnMQSQL8ll59+vZU35jRbfLFdbsIpK5iivbeatup dRovBkGLgY3UK5DuULdZOg+Fda5CJFMYN+aI+O3pdCthname9vGxinVSTSmBK4m50GLm 5DMB6tQnp+3drJl/FEW864Egyof46ozbyZFKR8M7JsiAiFOMeTYPO3miJDW5088nfLe+ rQmWo8SvBgP+kOuwA6S+7vjEyRA5veSMFgeH1vP3NaWJ0qH4yC1JsSeIN6JBHiz94/dM XSHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IyrMTrl5CRJ2yLYOr4vGGEV3ESJvvXX+4ahgGhDzzQs=; b=QksajkR6pWlH7T2f28UNeUodoDPtAoWIMJDn3CB9coxpRhY38jMxAP5VJ7bbaf3jAP xq7VjTh5f6ewHrmofx99RMTvthLptinM5Szs/cTRrITudbLVJ63PF1+LGwpcGTAlJKuN qOC+yjOT9IDvkZJ8g+LjLQFUaoFeyAkoTJ7KPw+NQUlMKfe5CihG8/jasR2gazfd68vz B9aD8CmcPXeIo+5RTxzLmYfjUIQi2LV0aJc8D5mxRoHWDXgJjwOwZpvHIBJVfLfKdtTy pegjRcRFLiQD/eszTdVmwXgKEp1l4fACDmq/rsnFm80kY/OnRs197c/UOoTN/Bvx7xGY ACdg==
X-Gm-Message-State: AA6/9RlSMLhCMRiPfbX4aQ4RGdgHoNpwtEiSteIFU1SZfCMQEHfw1TJvza/38V37CjeXqplLbNJi8/cuZMckjQ==
X-Received: by 10.37.80.12 with SMTP id e12mr16258596ybb.105.1475865268310; Fri, 07 Oct 2016 11:34:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.75.212 with HTTP; Fri, 7 Oct 2016 11:33:47 -0700 (PDT)
In-Reply-To: <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 7 Oct 2016 11:33:47 -0700
Message-ID: <CABcZeBOkj908hNQqGMrP0DvStXPW5EpgMeYDkCTa68O9uBC8-Q@mail.gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: multipart/alternative; boundary=001a113e86cc0e0a6f053e4aa9da
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9mvPkJ4KaZutUNtNLT10zkiyD2E>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 18:34:31 -0000

--001a113e86cc0e0a6f053e4aa9da
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

ISTM that there are two risks:
1. That people might use structured RIDs, MIDs, etc. and that that will
leak a lot of information about
2. That just the structure of the media streams is a fingerprinting risk.

The first of these seems addressable by guidance about how to construct
these IDs. I note that we
have only very limited guidance on how to construct ICE ufrag/passwords....
The second seems
not that interesting as I bet you can get a lot by other metadata (packet
size, PT, etc).

-Ekr


On Fri, Oct 7, 2016 at 1:41 AM, Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> Den 2016-10-06 kl. 23:59, skrev Cullen Jennings:
>
>>
>> I'm not getting the problem here and mandating 6904 is not an easy
>> thing to do.
>>
>
> So, lets be clear on what I have proposed. For bundle in general it is
> RECOMMENDED to encrypt MIDs in RTP header extensions. I have also propose=
d
> that for RTCWeb implementation and use should be mandated. I was not clea=
r
> in what applies when an WebRTC endpoint talks to a legacy endpoint what i=
s
> expected here. I guess this is the thorny issue.
>
>
>> I'm not getting what the issue is here. If mid are random, or are
>> just a count of n'th m-line in the sdp, what is the problem with
>> exposing them to people are getting the media?
>>
>
> The issue is that these identifiers are going from having only been
> visiable in the signalling messages to be visible also on the RTP media
> plane. And without RFC6904 even if one uses SRTP, these values are expose=
d.
> This have several different effects as I see it. So if the generation
> algorithm are not strictly defined, the implementation gets possible to
> fingerprint. In addition the device gets to be fingerprinted based on the
> number of streams offered and their identifiers. Thus, it is not only wha=
t
> is actually used that is exposed, but what was originally offered, i.e. t=
he
> full offer leaks into unencrypted domain on the media plane. Note, this
> later can't be dealt with any mid id creation rules, it will still leak.
> Thus devices that have more exotic configurations when it comes to media
> streams, i.e. number of cameras etc this can still be fingerprinted by
> passive attacks from third parties.
>
> It is the passive attack from third parties that has me worried here. A
> peer in the signalling has massively more powerful fingerprinting, but th=
at
> requires one to be in the signalling context, not passively observe traff=
ic
> that goes past.
>
>
> Cheers
>
> Magnus
>
>
>
>
>>
>>
>> On Oct 6, 2016, at 7:39 AM, Magnus Westerlund
>>> <magnus.westerlund@ericsson.com> wrote:
>>>
>>> Den 2016-10-06 kl. 14:49, skrev Christer Holmberg:
>>>
>>>>
>>>> Hi,
>>>>
>>>> Magnus suggested usage of RFC 6904 for encryption of the RTP SDES
>>>> header extension for MID. I guess it would be a SHUOLD?
>>>>
>>>> In addition, we would say that a corresponding level of security
>>>> must be applied to the RTP SDES header extension for MID and to
>>>> the RTCP SDES MID item.
>>>>
>>>> Any opinions?
>>>>
>>>
>>> I think this is fine solution to this issue. I would probably
>>> formulate the security considerations like this.
>>>
>>> The identfication-tag when included in the RTP MID SDES item,
>>> independent of transport, RTCP SDES packet or RTP header extension,
>>> can expose the value to parties beyond the signaling chain.
>>> Therefore, the identification-tag MUST NOT contain any user related
>>> information. However, the implementation's method for generating
>>> identfication-tags combined with hardware configuration can enable
>>> fingerprinting of the endpoint device and thus its user. As the
>>> identification-tag is also used to route the media stream to the
>>> right application functionality it is also important that the value
>>> received is the one intended by the sender, thus integrity and the
>>> authenticity of the source are important to prevent denial of
>>> service on the application. At least to prevent third parties from
>>> modifying the identification-tag value.
>>>
>>> Due to the security risks associated with the MID values in RTP and
>>> RTCP it is strongly RECOMMENDED that the MID SDES item is both
>>> confidentiality protected as well as source authenticated when
>>> transported in either RTCP or RTP header extensions. The security
>>> mechanisms used SHALL provide corresponding levels of security for
>>> both RTP header extensions and RTCP. Confidentiality mechanisms for
>>> RTP/RTCP are discussed in Options for Securing RTP Sessions
>>> [RFC7201], for example SRTP [RFC3711] with SRTCP encryption enabled
>>> combined with [RFC6904] can provide the necessary security
>>> functions.
>>>
>>>
>>> Cheers
>>>
>>> Magnus Westerlund
>>>
>>> ----------------------------------------------------------------------
>>>
>>>
>>> Services, Media and Network features, Ericsson Research EAB/TXM
>
>> ----------------------------------------------------------------------
>>>
>>>
>>> Ericsson AB                 | Phone  +46 10 7148287
>
>> F=C3=A4r=C3=B6gatan 6                 | Mobile +46 73 0949079 SE-164 80
>>> Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>>> ----------------------------------------------------------------------
>>>
>>>
>>>
>>> _______________________________________________
>
>> mmusic mailing list mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>
>>
>>
>>
>
> --
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=C3=A4r=C3=B6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--001a113e86cc0e0a6f053e4aa9da
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>ISTM that there are two risks:<br></div><div>1. That =
people might use structured RIDs, MIDs, etc. and that that will leak a lot =
of information about</div><div>2. That just the structure of the media stre=
ams is a fingerprinting risk.</div><div><br></div><div>The first of these s=
eems addressable by guidance about how to construct these IDs. I note that =
we</div><div>have only very limited guidance on how to construct ICE ufrag/=
passwords.... The second seems</div><div>not that interesting as I bet you =
can get a lot by other metadata (packet size, PT, etc).</div><div><br></div=
><div>-Ekr<br></div><div><div><br></div></div></div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Fri, Oct 7, 2016 at 1:41 AM, Magnus W=
esterlund <span dir=3D"ltr">&lt;<a href=3D"mailto:magnus.westerlund@ericsso=
n.com" target=3D"_blank">magnus.westerlund@ericsson.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><span class=3D"">Den 2016-10-06 kl. 23=
:59, skrev Cullen Jennings:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
I&#39;m not getting the problem here and mandating 6904 is not an easy<br>
thing to do.<br>
</blockquote>
<br></span>
So, lets be clear on what I have proposed. For bundle in general it is RECO=
MMENDED to encrypt MIDs in RTP header extensions. I have also proposed that=
 for RTCWeb implementation and use should be mandated. I was not clear in w=
hat applies when an WebRTC endpoint talks to a legacy endpoint what is expe=
cted here. I guess this is the thorny issue.<span class=3D""><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
I&#39;m not getting what the issue is here. If mid are random, or are<br>
just a count of n&#39;th m-line in the sdp, what is the problem with<br>
exposing them to people are getting the media?<br>
</blockquote>
<br></span>
The issue is that these identifiers are going from having only been visiabl=
e in the signalling messages to be visible also on the RTP media plane. And=
 without RFC6904 even if one uses SRTP, these values are exposed. This have=
 several different effects as I see it. So if the generation algorithm are =
not strictly defined, the implementation gets possible to fingerprint. In a=
ddition the device gets to be fingerprinted based on the number of streams =
offered and their identifiers. Thus, it is not only what is actually used t=
hat is exposed, but what was originally offered, i.e. the full offer leaks =
into unencrypted domain on the media plane. Note, this later can&#39;t be d=
ealt with any mid id creation rules, it will still leak. Thus devices that =
have more exotic configurations when it comes to media streams, i.e. number=
 of cameras etc this can still be fingerprinted by passive attacks from thi=
rd parties.<br>
<br>
It is the passive attack from third parties that has me worried here. A pee=
r in the signalling has massively more powerful fingerprinting, but that re=
quires one to be in the signalling context, not passively observe traffic t=
hat goes past.<br>
<br>
<br>
Cheers<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
Magnus</font></span><div><div class=3D"h5"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Oct 6, 2016, at 7:39 AM, Magnus Westerlund<br>
&lt;<a href=3D"mailto:magnus.westerlund@ericsson.com" target=3D"_blank">mag=
nus.westerlund@ericsson.co<wbr>m</a>&gt; wrote:<br>
<br>
Den 2016-10-06 kl. 14:49, skrev Christer Holmberg:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Hi,<br>
<br>
Magnus suggested usage of RFC 6904 for encryption of the RTP SDES<br>
header extension for MID. I guess it would be a SHUOLD?<br>
<br>
In addition, we would say that a corresponding level of security<br>
must be applied to the RTP SDES header extension for MID and to<br>
the RTCP SDES MID item.<br>
<br>
Any opinions?<br>
</blockquote>
<br>
I think this is fine solution to this issue. I would probably<br>
formulate the security considerations like this.<br>
<br>
The identfication-tag when included in the RTP MID SDES item,<br>
independent of transport, RTCP SDES packet or RTP header extension,<br>
can expose the value to parties beyond the signaling chain.<br>
Therefore, the identification-tag MUST NOT contain any user related<br>
information. However, the implementation&#39;s method for generating<br>
identfication-tags combined with hardware configuration can enable<br>
fingerprinting of the endpoint device and thus its user. As the<br>
identification-tag is also used to route the media stream to the<br>
right application functionality it is also important that the value<br>
received is the one intended by the sender, thus integrity and the<br>
authenticity of the source are important to prevent denial of<br>
service on the application. At least to prevent third parties from<br>
modifying the identification-tag value.<br>
<br>
Due to the security risks associated with the MID values in RTP and<br>
RTCP it is strongly RECOMMENDED that the MID SDES item is both<br>
confidentiality protected as well as source authenticated when<br>
transported in either RTCP or RTP header extensions. The security<br>
mechanisms used SHALL provide corresponding levels of security for<br>
both RTP header extensions and RTCP. Confidentiality mechanisms for<br>
RTP/RTCP are discussed in Options for Securing RTP Sessions<br>
[RFC7201], for example SRTP [RFC3711] with SRTCP encryption enabled<br>
combined with [RFC6904] can provide the necessary security<br>
functions.<br>
<br>
<br>
Cheers<br>
<br>
Magnus Westerlund<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
<br>
</blockquote></blockquote>
Services, Media and Network features, Ericsson Research EAB/TXM<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
<br>
</blockquote></blockquote>
Ericsson AB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =
Phone=C2=A0 <a href=3D"tel:%2B46%2010%207148287" value=3D"+46107148287" tar=
get=3D"_blank">+46 10 7148287</a><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
F=C3=A4r=C3=B6gatan 6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0| Mobile <a href=3D"tel:%2B46%2073%200949079" value=3D"+467309490=
79" target=3D"_blank">+46 73 0949079</a> SE-164 80<br>
Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@ericsson.co=
m" target=3D"_blank">magnus.westerlund@ericsson.com</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
<br>
<br>
</blockquote></blockquote>
______________________________<wbr>_________________<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
mmusic mailing list <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mm=
usic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br></div></div>
-- <br><div class=3D"HOEnZb"><div class=3D"h5">
<br>
Magnus Westerlund<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
Services, Media and Network features, Ericsson Research EAB/TXM<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
Ericsson AB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =
Phone=C2=A0 <a href=3D"tel:%2B46%2010%207148287" value=3D"+46107148287" tar=
get=3D"_blank">+46 10 7148287</a><br>
F=C3=A4r=C3=B6gatan 6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0| Mobile <a href=3D"tel:%2B46%2073%200949079" value=3D"+467309490=
79" target=3D"_blank">+46 73 0949079</a><br>
SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@e=
ricsson.com" target=3D"_blank">magnus.westerlund@ericsson.com</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div>

--001a113e86cc0e0a6f053e4aa9da--


From nobody Fri Oct  7 11:42:52 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 420D41296C3 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 11:42:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBY4M_X6zWZ5 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 11:42:49 -0700 (PDT)
Received: from mail-yb0-x236.google.com (mail-yb0-x236.google.com [IPv6:2607:f8b0:4002:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A45E61296BA for <mmusic@ietf.org>; Fri,  7 Oct 2016 11:42:49 -0700 (PDT)
Received: by mail-yb0-x236.google.com with SMTP id e2so19191627ybi.1 for <mmusic@ietf.org>; Fri, 07 Oct 2016 11:42:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HiPRK43d31uFdgAz5LE2HLPZO7h+kc3AMpzVhCJRebg=; b=eYLBsOfDLl4ARAe9zRn8QiVaEeWGVanxXUK+SRAPnQSY2kRWyCqP8X8H1TG3irw/LI 3rFOnSgmL4gknSYMBG0QCf+Mscb9/8xauBHvFlzl9s9lDDOYkRgk5QCAkA3Jj1ecr/p4 hBhjgE1vXElX7Kuo3y32XFw/Xgy8knFjmy43SkgyeiChnpCKr4r5eKq76qdDFNjxKeqS MtyPVZttYJ1UnLnGw054urVzmuawhFRG3tWPu/9bV8WHn6enjRae0rHfKHsCDF9YvXlg M0dMrQT5sBtEBI7UoO5/brZrILlrxbH8yyvQq95kZdQi30XDQMifkD1DzlTu8ncYOpJf V7Lg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HiPRK43d31uFdgAz5LE2HLPZO7h+kc3AMpzVhCJRebg=; b=LFvFdcoe4CSzG/4twJz7svaGVh6CSGl0fyOyXKB5TUqdjF4W5ocT1txFaZZHvsVIkQ ppUh3SEvVtJtwTFazhf4nmBAHGcCQ42zgacuhPx69e/cWrjw96aI0Wg2IRe2zs0YDzZA mylCyVOYlj+0nJxe65bi2UXdK+IF5mgshwMQ8Obf2D8bmFyqzE349R3gWRSAYTIf9BwA ECL1oUDpjKatnVpz8XG2oErnbUlb9p/HKCBhc8HinhRUQ/mLgQDE7NLN4UUdGEBOdtYZ ehoBs5BkWwc7sE9rcTJjZ+IgX0IWa1hu3jv6fRNTiagzpHJkpH4QNgmkYprNuq+1sThl 6eJg==
X-Gm-Message-State: AA6/9RnwdBDzcCFPcvua9akHEyyanZDuACRwPDFz9anUunAGLWXdL5q9eTNGIRtPiNr9I+h+f9QKjUYad0FMXQ==
X-Received: by 10.37.113.197 with SMTP id m188mr5636789ybc.109.1475865768897;  Fri, 07 Oct 2016 11:42:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.158.73 with HTTP; Fri, 7 Oct 2016 11:42:48 -0700 (PDT)
In-Reply-To: <CAMRcRGTiu5u0LCSBeScBdCJGg3PRUtcogounaPHNKtZ8ienOWg@mail.gmail.com>
References: <D41963FD.1059F%christer.holmberg@ericsson.com> <AM5PR0701MB25770AB3719E8C10A6C040058DC40@AM5PR0701MB2577.eurprd07.prod.outlook.com> <7594FB04B1934943A5C02806D1A2204B4BD1BCF8@ESESSMB209.ericsson.se> <CAMRcRGQp5u_dP5L++yHu4NtfPWu+wc=v=0Xec+4WeAUw=jZWYQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1C066@ESESSMB209.ericsson.se> <CAMRcRGTZumBNmKo3tVCjH_fSVm2i_UfiPRRuhbUZM9Q8-hBDAA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1C225@ESESSMB209.ericsson.se> <CAMRcRGTJXgq94Z4YvrfXTVA4TNJO82k_9VFC_kByAkOfUHNOWA@mail.gmail.com> <D41BF5AE.108D0%christer.holmberg@ericsson.com> <CAMRcRGTiu5u0LCSBeScBdCJGg3PRUtcogounaPHNKtZ8ienOWg@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Fri, 7 Oct 2016 11:42:48 -0700
Message-ID: <CAMRcRGRFu4eXSza=OxR=-F-yRB97PFzTxjAuLTTD=tX30BbRzA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a1148b6f2e4300e053e4ac6ba
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/EYsBAAQrJbTaq_FuCWjpFY3PkyE>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "snandaku@cisco.com" <snandaku@cisco.com>
Subject: Re: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes: Do we need to mandate identical SDP attribute values?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 18:42:51 -0000

--001a1148b6f2e4300e053e4ac6ba
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Christer,Bo

   Just to close the loop on this topic, I don't see misalignment between
Bundle and Mux specs. However, adding  clarification on the fact that the
categories apply even during the initial offer(or before bundle gets
negotiated) and their semantics apply , might be needed in the Bundle spec,
if it is not already clear

Section 8.1 already talks about categories interpretation once bundle gets
negotiated. That section might be a right place to add above clarification.
I would leave the decision to Christer on that :)

Thanks
Suhas

On Thursday, October 6, 2016, Suhas Nandakumar <suhasietf@gmail.com> wrote:

> Hi,
>
>
> On Thu, Oct 6, 2016 at 2:35 AM, Christer Holmberg <
> christer.holmberg@ericsson.com
> <javascript:_e(%7B%7D,'cvml','christer.holmberg@ericsson.com');>> wrote:
>
>> Hi,
>>
>> =E2=80=A6
>>
>>> [Suhas]
>>>
>>>
>>>
>>> Meta Note:
>>>
>>> The mux draft has stayed away from offer/answer procedures to avoid
>>> ambiguities with offers/re-offers and its focus has been defining gener=
ic
>>> framework categorizing SDP attributes while performing Media multiplexi=
ng
>>>
>>>
>>>
>>> Thus, the case of initial offer applies as well. In that context, on
>>> Initial Offer, the offerer will repeat the SDP attributes that fall und=
er
>>> IDENTICAL category on all the m=3Dlines that it plans to multiplex.
>>>
>>>
>>>
>>> What is the reason for having different rules for IDENTICAL and
>>> TRANPORT? With TRANSPORT you can use different attribute values, becaus=
e
>>> the =E2=80=9Csoftware will pick the correct value=E2=80=9D. Why not use=
 the
>>> software-must-pick rule also for IDENTICAL?
>>>
>>>
>>>
>>
>> [Suhas]
>>
>>  Let's try to explain this with example attributes. a=3Drtcp-mux which i=
s
>> categorized as IDENTICAL and ice-candidates which falls under TRANSPORT
>> category.
>>
>> For ice-candidates ,the offerer in the initial offer will include
>> different ice-pwd, candidates lines per m=3Dline since it's not sure of =
the
>> BUNDLE negotiation. Thus once BUNDLE gets successfully negotiated , the
>> software picks the ones from the m=3Dline that is selected for BUNDling.
>> OTOH, if the BUNDLE get's rejected each m=3Dline's individual ice info w=
ill
>> be used.
>>
>> Correct.
>>
>> For a=3Drtcp-mux,  in the initial Offer, the offerer must include it in =
all
>> the m=3Dlines (repeated) since there is no way for the software to decid=
e the
>> intent of the Offerer in scenarios where the BUNDLE gets rejected ( If t=
he
>> offerer didn't repeat the attribute, the software cannot assume the
>> offerer's intention of whether to imply a=3Drtcp-mux for  the m=3Dlines =
or the
>> Offerer itself didn't want to perform rtcp muxing )
>>
>> If there is no rtcp-mux attribute, and if the BUNDLE is rejected (or if
>> an m- line is not accepted into the BUNDLE group), normal SDP O/A
>> procedures apply and there would be no RTCP MUX.
>>
>> Anyway, even if we do mandate identical attribute values in case of
>> IDENTICAL, is draft-mux-categories clear that it applies already before
>> a BUNDLE group has been created? I believe there were some clarification
>> questions about that also earlier.
>>
>>
> [Suhas] .. I personally feel that clarification should be in the BUNDLE
> spec. BUNDLE spec already has clarification on how IDENTICAL and TRANSPOR=
T
> categories are treated once shared address is selected as you pointed out
> earlier (also in section 8.1).
> Similarly, it needs to to address the case for before shared address
> getting selected, if it is not already (I thought section 7.3 implied tha=
t
> already).
>
>
>
>> Regards,
>>
>> Christer
>>
>>
>>
>

--001a1148b6f2e4300e053e4ac6ba
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Christer,Bo<div><br></div><div>=C2=A0 =C2=A0Just to close the loop on th=
is topic, I don&#39;t see misalignment between Bundle and Mux specs. Howeve=
r, adding =C2=A0clarification on the fact that the categories apply even du=
ring=C2=A0the initial offer(or before bundle gets negotiated)=C2=A0<span></=
span>and their semantics apply ,=C2=A0might be needed in the Bundle spec, i=
f it is not already clear</div><div><br></div>Section 8.1 already talks abo=
ut categories interpretation once bundle gets negotiated. That section migh=
t be a right place to add above clarification. I would leave the decision t=
o Christer on that :)<div><br></div><div>Thanks</div><div>Suhas<br><div><br=
>On Thursday, October 6, 2016, Suhas Nandakumar &lt;<a href=3D"mailto:suhas=
ietf@gmail.com">suhasietf@gmail.com</a>&gt; wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"><div dir=3D"ltr">Hi,<div><br></div><div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">On Thu, Oct 6, 2016 at 2:35 AM, Christer Holmbe=
rg <span dir=3D"ltr">&lt;<a href=3D"javascript:_e(%7B%7D,&#39;cvml&#39;,&#3=
9;christer.holmberg@ericsson.com&#39;);" target=3D"_blank">christer.holmber=
g@ericsson.<wbr>com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>



<div style=3D"word-wrap:break-word">
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
Hi,</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<br>
</div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
=E2=80=A6=C2=A0</div><span>
<span style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,=
0)">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div><span>
<div>
<p class=3D"MsoNormal"><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Suhas]=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Meta Note:=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The mux draft has stayed away from offer/answer proc=
edures to avoid ambiguities with offers/re-offers and its focus has been de=
fining generic framework categorizing SDP attributes while performing Media=
 multiplexing<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span>
<div><span>
<p class=3D"MsoNormal">Thus, the case of initial offer applies as well. In =
that context, on Initial Offer, the offerer will repeat the SDP attributes =
that fall under IDENTICAL category on all the m=3Dlines that it plans to mu=
ltiplex.<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>=C2=A0<u></u></span></p>
</span>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">What is the reason for having different r=
ules for IDENTICAL and TRANPORT? With TRANSPORT you can use different attri=
bute values, because the =E2=80=9Csoftware will pick the
 correct value=E2=80=9D. Why not use the software-must-pick rule also for I=
DENTICAL? <u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><u></u>=C2=A0</span></p>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>[Suhas]</div>
<div><br>
</div>
<div>=C2=A0Let&#39;s try to explain this with example attributes. a=3Drtcp-=
mux which is categorized as IDENTICAL and ice-candidates which falls under =
TRANSPORT category.</div>
<div><br>
</div>
<div>For ice-candidates ,the offerer in the initial offer will include diff=
erent ice-pwd, candidates lines per m=3Dline since it&#39;s not sure of the=
 BUNDLE negotiation. Thus once BUNDLE gets successfully negotiated , the so=
ftware picks the ones from the m=3Dline
 that is selected for BUNDling. OTOH, if the BUNDLE get&#39;s rejected each=
 m=3Dline&#39;s individual ice info will be used.</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,0=
)">
<br>
</div>
</span><div style=3D"font-family:Calibri,sans-serif;font-size:14px"><font c=
olor=3D"#ff0000">Correct.</font></div><span>
<span style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb(0,0,=
0)">
<div>
<div>
<div dir=3D"ltr">
<div>
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><br>
</div>
<div>For a=3Drtcp-mux, =C2=A0in the initial Offer, the offerer must include=
 it in all the m=3Dlines (repeated) since there is no way for the software =
to decide the intent of the Offerer in scenarios where the BUNDLE gets reje=
cted ( If the offerer didn&#39;t repeat the attribute,
 the software cannot assume the offerer&#39;s intention of whether to imply=
 a=3Drtcp-mux for =C2=A0the m=3Dlines or the Offerer itself didn&#39;t want=
 to perform rtcp muxing )</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
</span><div style=3D"font-family:Calibri,sans-serif;font-size:14px"><font c=
olor=3D"#ff0000">If there is no rtcp-mux attribute, and if the BUNDLE is re=
jected (or if an m- line is not accepted into the BUNDLE group), normal SDP=
 O/A procedures apply and there would
 be no RTCP MUX.</font></div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px"><font color=3D=
"#ff0000"><br>
</font></div>
<div><span style=3D"font-family:Calibri,sans-serif;font-size:14px;color:rgb=
(255,0,0)">Anyway, even if we do mandate identical attribute values in case=
 of IDENTICAL, is=C2=A0</span><font color=3D"#ff0000" face=3D"Calibri,sans-=
serif">draft-mux-categories clear
 that it applies already before a BUNDLE group has been created? I=C2=A0bel=
ieve there were some clarification questions about that also earlier.</font=
></div>
<div><font color=3D"#ff0000" face=3D"Calibri,sans-serif"><br></font></div><=
/div></blockquote><div><br></div><div>[Suhas] .. I personally feel that cla=
rification should be in the BUNDLE spec. BUNDLE spec already has clarificat=
ion on how IDENTICAL and TRANSPORT categories are treated once shared addre=
ss is selected as you pointed out earlier (also in section 8.1).=C2=A0</div=
><div>Similarly, it needs to to address the case for before shared address =
getting selected, if it is not already (I thought section 7.3 implied that =
already).</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div style=3D"word-wrap:break-word"><div><font color=3D"#ff0000" face=3D=
"Calibri,sans-serif">
</font></div>
<div><font color=3D"#ff0000" face=3D"Calibri,sans-serif">Regards,</font></d=
iv>
<div><br>
</div>
<div><font color=3D"#ff0000" face=3D"Calibri,sans-serif">Christer</font></d=
iv>
<span style=3D"font-family:Calibri,sans-serif;font-size:14px">
<div>
<div>
<div dir=3D"ltr">
<div>
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><br>
</div>
<div style=3D"color:rgb(0,0,0)"><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</div>

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

--001a1148b6f2e4300e053e4ac6ba--


From nobody Fri Oct  7 16:42:07 2016
Return-Path: <ekr@rtfm.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 9D25A126D74 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 16:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAZCGVBrYaie for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 16:42:03 -0700 (PDT)
Received: from mail-yb0-x232.google.com (mail-yb0-x232.google.com [IPv6:2607:f8b0:4002:c09::232]) (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 AFC03129441 for <mmusic@ietf.org>; Fri,  7 Oct 2016 16:42:03 -0700 (PDT)
Received: by mail-yb0-x232.google.com with SMTP id 191so21086432ybv.3 for <mmusic@ietf.org>; Fri, 07 Oct 2016 16:42:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=h2RIMdPhz7pi/AkFpEmCZfS4HpX0U4GlbyO7jtJ6Di0=; b=Kun4+E1IatoyO6KSqfvBzDJ8js7qrTeNBXZnSchCzMGiEaTLdTpumwC1yylJibOdvG 8sch64qopXPrYWuIwog65+6ihVT+2NhDAZuz672LHabjEcnnb8C1k9K1n1J2heyFCZnN a09zZ34eyCp2Cw2PBBCDaVZl8+s6rwIv9i5wwj6YxLaouyf7c1Fkn989FMpkw0T7+VsJ cmuO916WDeUoIOwpitaLbmbWVfumeEis2FXTih6TUVftA43eJg7jT+eWcyw88Pu/3NIg cJ7HrgnZe/uTEA2Nj9hCarp2+Wjm8Q315AFYOMrsfNf9m3/tonIAfXv+zBD7w92W5lvg XqSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=h2RIMdPhz7pi/AkFpEmCZfS4HpX0U4GlbyO7jtJ6Di0=; b=R0JFb1Ju/AZJgYebrAL4VUtegfQOrPkrXQvbeVWhTTVRnSY6vckTcHW1UTA6iUkhG1 J6Ywy7qqPkcW87FEVSqKfYQklLOUDUF/Q6tugQd6GXybRho+nOYkqDHtq1dTilJ5CEID p+4f4GmkQbSM6Wk+ZsagEIMzTi7wrbdz0N9O0eurNsLHnAMCjf5g8St+mejyGPf4uNXq T1BGgjSEccD0zQoleTztRDoiD9JDbzJ+9Vk1j8jMDL0OyhIbzh2Q7dzWHaD56mvwOfDj 38tOP88SHX/wKilCT4wU9LmPDEyCYvqEqIeFtqKYwPAUHENDqT33b5to0cu9dDBJTexN eVpA==
X-Gm-Message-State: AA6/9Rk3TQzrSGvHnFNVvKGKYp7PCwL6+z5shQkUqnR8oKA38M/IZ7Lxtx6V8pzPNjV2+Vif1Itl/rA4ejcy6Q==
X-Received: by 10.37.3.132 with SMTP id 126mr17642094ybd.64.1475883722794; Fri, 07 Oct 2016 16:42:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.75.212 with HTTP; Fri, 7 Oct 2016 16:41:22 -0700 (PDT)
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 7 Oct 2016 16:41:22 -0700
Message-ID: <CABcZeBPpTskVnvFXgBNe=AfXFtu4R=1OMumsuWW8_th5KuLfyA@mail.gmail.com>
To: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c06d5207185e053e4ef5c8
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/XQ7FvJIXFZEWcJwGwGWiTJJ7TNw>
Subject: [MMUSIC] To duplicate or not duplicate
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 23:42:05 -0000

--001a11c06d5207185e053e4ef5c8
Content-Type: text/plain; charset=UTF-8

Section 4.3 of the sdp-mux-attributes document says:
https://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-14#section-4.3

    The attributes and their associated values (if any) in the IDENTICAL
    category MUST be repeated across all the media descriptions under
    multiplexing.


Section 8.1 of the BUNDLE document says:
https://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation-33#section-8.1

   When an offerer associates SDP attributes with a bundled "m=" line
   associated with a shared address, IDENTICAL and TRANSPORT mux
   category SDP attributes [I-D.ietf-mmusic-sdp-mux-attributes] are
   associated with the "m=" line only if the "m=" line is also
   associated with the offerer BUNDLE-tag.  Otherwise the offerer MUST
   NOT associate such SDP attributes with the "m=" line.


I submit that BUNDLE is right here and the mux attributes document is wrong
and
we should not duplicate.

-Ekr

--001a11c06d5207185e053e4ef5c8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Section 4.3 of the sdp-mux-attributes document says:<=
/div><div><a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-=
attributes-14#section-4.3">https://tools.ietf.org/html/draft-ietf-mmusic-sd=
p-mux-attributes-14#section-4.3</a></div><div><br></div><div>=C2=A0 =C2=A0 =
The attributes and their associated values (if any) in the IDENTICAL</div><=
div>=C2=A0 =C2=A0 category MUST be repeated across all the media descriptio=
ns under</div><div>=C2=A0 =C2=A0 multiplexing.</div><div><br></div><div><br=
></div><div>Section 8.1 of the BUNDLE document says:</div><div><a href=3D"h=
ttps://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation-33#sect=
ion-8.1">https://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiati=
on-33#section-8.1</a></div><div><br></div><div>=C2=A0 =C2=A0When an offerer=
 associates SDP attributes with a bundled &quot;m=3D&quot; line</div><div>=
=C2=A0 =C2=A0associated with a shared address, IDENTICAL and TRANSPORT mux<=
/div><div>=C2=A0 =C2=A0category SDP attributes [I-D.ietf-mmusic-sdp-mux-att=
ributes] are</div><div>=C2=A0 =C2=A0associated with the &quot;m=3D&quot; li=
ne only if the &quot;m=3D&quot; line is also</div><div>=C2=A0 =C2=A0associa=
ted with the offerer BUNDLE-tag.=C2=A0 Otherwise the offerer MUST</div><div=
>=C2=A0 =C2=A0NOT associate such SDP attributes with the &quot;m=3D&quot; l=
ine.</div><div><br></div><div><br></div><div>I submit that BUNDLE is right =
here and the mux attributes document is wrong and</div><div>we should not d=
uplicate.</div><div><br></div><div>-Ekr</div><div><br></div></div>

--001a11c06d5207185e053e4ef5c8--


From nobody Fri Oct  7 16:42:48 2016
Return-Path: <fluffy@iii.ca>
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 93BFA12949D for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 16:42:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 DGZbCj-sEDlT for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 16:42:43 -0700 (PDT)
Received: from smtp90.ord1c.emailsrvr.com (smtp90.ord1c.emailsrvr.com [108.166.43.90]) (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 6A7E112949A for <mmusic@ietf.org>; Fri,  7 Oct 2016 16:42:43 -0700 (PDT)
Received: from smtp12.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp12.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id D119EC0243; Fri,  7 Oct 2016 19:42:42 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp12.relay.ord1c.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 695B2C0241;  Fri,  7 Oct 2016 19:42:42 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.24.90.15] ([UNAVAILABLE]. [128.107.241.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.7); Fri, 07 Oct 2016 19:42:42 -0400
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <D41D4800.10A3F%christer.holmberg@ericsson.com>
Date: Fri, 7 Oct 2016 16:42:41 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <68971202-4458-407D-A4AF-BCDCE54F2F78@iii.ca>
References: <147481162395.28315.18346373858565370012.idtracker@ietfa.amsl.com> <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com> <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca> <D41D4800.10A3F%christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/08dZrbqBaZD9BPyeJKzmgunTy-E>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2016 23:42:46 -0000

There are lots of people using 4572 and there is nothing wrong with it. =
What is proposed in this draft is also fine and it if was RFCAAAA that =
is fine. But telling people doing 4572 that they have to do AAAA is not =
OK. You make not think that is what update means but it is what I and =
many others think update means. Given this disagreement on what update =
means, I don't want to use update.=20

I'd be happy to write an alternative draft that does not need to be an =
update if that is the issue but I plan to get JSEP ready first.=20


> On Oct 7, 2016, at 2:49 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> First, being this late in the process, I think it would be fair to =
explain
> (I would have expected the chairs to request the same) what the =
problem
> is. We HAVE added the note saying that the draft does NOT make =
existing
> 4572 implementations non-compliant. What else is missing?
>=20
> Second, IMO the draft says a little more than =B3multiple fingerprints =
are
> allowed=B2. It also specifies HOW multiple fingerprints are used, HOW =
they
> must be matched etc - using RFC 2119 terminology (there is a number of
> MUSTs). Do we consider that =B3advice=B2? Or, do you want to REMOVE =
that?
>=20
> Last, if we don=B9t indicate the draft as a =B34572 update=B2, people =
will not
> automatically be made aware of it when looking for 4572, as it will =
not be
> listed as an 4572 update. Is that a good thing?
>=20
> Regards,
>=20
> Christer
>=20
>=20
>=20
>=20
>=20
> On 07/10/16 00:39, "mmusic on behalf of Cullen Jennings"
> <mmusic-bounces@ietf.org on behalf of fluffy@iii.ca> wrote:
>=20
>>=20
>> It would be easy to rewrite it to not change it but simply clarify =
that
>> multiple fingerprints are allowed and provide advice about additional
>> ones to provide.=20
>>=20
>>=20
>>> On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)
>>> <fluffy@cisco.com> wrote:
>>>=20
>>>=20
>>> So I still disagree that this should update 4572 and the text for =
the
>>> interoperability issue if significantly different than what many =
people
>>> proposed on list. Can we arrange a phone call to discuss this.
>>>=20
>>>=20
>>>=20
>>>> On Sep 25, 2016, at 7:53 AM, internet-drafts@ietf.org wrote:
>>>>=20
>>>>=20
>>>> 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
>>>> of the IETF.
>>>>=20
>>>>      Title           : SDP Fingerprint Attribute Usage =
Clarifications
>>>>      Author          : Christer Holmberg
>>>> 	Filename        : draft-ietf-mmusic-4572-update-07.txt
>>>> 	Pages           : 8
>>>> 	Date            : 2016-09-25
>>>>=20
>>>> Abstract:
>>>> This document updates RFC 4572 by clarifying the usage of multiple
>>>> SDP 'fingerprint' attributes with a single SDP media description =
("m=3D
>>>> line").  The document also updates the preferred cipher suite with =
a
>>>> stronger cipher suite.
>>>>=20
>>>>=20
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/
>>>>=20
>>>> There's also a htmlized version available at:
>>>> https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07
>>>>=20
>>>> A diff from the previous version is available at:
>>>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-4572-update-07
>>>>=20
>>>>=20
>>>> 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.
>>>>=20
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>=20
>>>> _______________________________________________
>>>> I-D-Announce mailing list
>>>> I-D-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>=20
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>=20
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Fri Oct  7 17:03:09 2016
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 D9E761294A6 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 17:03:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5] 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 IqWMYw2x9ZMw for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 17:03:05 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E05CC1294A3 for <mmusic@ietf.org>; Fri,  7 Oct 2016 17:03:04 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id o19so31520582ito.1 for <mmusic@ietf.org>; Fri, 07 Oct 2016 17:03:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XTvg4Bceu/diMekfGZulmZucy0QUbfKNpHdyCtxPqvA=; b=x15kaKi2jR0YYgZdSgZn7xOiz3IymINycaGsa12dcRFDK57hOuPFEkr7XVOzFmFYS2 pVb/wfr+07IkfMsi3DYd40vcZ/GB6Fn6bSnnPJfYUsAsrSwZLiuSmW89F7/9Nz2xdds3 wBFxiIGuUM1uUhtiUlu2JanTfu+fsNEtvjkcG3Zwi/B42jyaelMaYEJVzCATM/83XLdH xme7hzryi5eGClwCHVHR8udL3n42z57tlibJFUejdUqpGSBWxPq6XS+VyXLpfBCDKE1c Yx0i4U4nglfWf61tTRIZH15Cd3wiL3mEW79HHKe9UJbNRv7p9sbpzFSei/z4TNu6yfZb 2kiw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XTvg4Bceu/diMekfGZulmZucy0QUbfKNpHdyCtxPqvA=; b=WLHoCDweUJMP3PG9BwVncBWfe82F4zb43+mxBAU0D7NvDFT4P8BdnYkB5uK7AMZXQf NgCXPa3ja6ZhwOXJfj6mtHkqSf66fLauo4WsLI20LBy0FOGWK+e9u85B0INDku8Tbfp0 SSYql6rMnuVDkX12njuk159EknZFP4FUWLWB12MWp7wxsWoiJn4gyGNgu8wa5Ax50rjL RDH5RtwwcPBq4NTaL6kJJclckUGQ4s4nCKxmgxnNXu9UO8ElVV2ZiejyOCgw3ehLYvFy +5qalNuV2ESg/neWZ/5bnvtS2TDk9pp8OqflrwJNJP8Zgpgop2N7fWqxsBxgfXpm/OCh 8gmA==
X-Gm-Message-State: AA6/9RmpsWtiFrATm7Nc5SULliZCs/kwNQaxqsNn8ed/aiaw/hm0UbFVLqCY2AXOkHxv9w==
X-Received: by 10.36.60.131 with SMTP id m125mr1164158ita.4.1475884983666; Fri, 07 Oct 2016 17:03:03 -0700 (PDT)
Received: from mail-io0-f177.google.com (mail-io0-f177.google.com. [209.85.223.177]) by smtp.gmail.com with ESMTPSA id j98sm7490140ioo.11.2016.10.07.17.03.02 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Oct 2016 17:03:02 -0700 (PDT)
Received: by mail-io0-f177.google.com with SMTP id r30so62105223ioi.1 for <mmusic@ietf.org>; Fri, 07 Oct 2016 17:03:02 -0700 (PDT)
X-Received: by 10.107.132.206 with SMTP id o75mr16252286ioi.234.1475884982537;  Fri, 07 Oct 2016 17:03:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.110.18 with HTTP; Fri, 7 Oct 2016 17:03:01 -0700 (PDT)
In-Reply-To: <68971202-4458-407D-A4AF-BCDCE54F2F78@iii.ca>
References: <147481162395.28315.18346373858565370012.idtracker@ietfa.amsl.com> <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com> <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca> <D41D4800.10A3F%christer.holmberg@ericsson.com> <68971202-4458-407D-A4AF-BCDCE54F2F78@iii.ca>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 7 Oct 2016 20:03:01 -0400
X-Gmail-Original-Message-ID: <CAD5OKxvgTAw2ptSupXuEvTS8k=5Pncv0aYV=XRX81jTPjB5VSA@mail.gmail.com>
Message-ID: <CAD5OKxvgTAw2ptSupXuEvTS8k=5Pncv0aYV=XRX81jTPjB5VSA@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: multipart/alternative; boundary=001a113fe12e1d3afe053e4f40f5
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/bGUxIKLGMt-LTGduWVQIu4CoPhs>
Cc: mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 00:03:08 -0000

--001a113fe12e1d3afe053e4f40f5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Cullen,

Can you answer a fundamental question related to 4572: Does it allow
multiple fingerprint attributes per one m- line or not? Can you point to
the exact language in the RFC which says that?

There are people (including the authors of RFC 4572) which gave
contradictory answers to this question. Because of these contradictory
answers, you can create two implementations which claim to be compatible
with 4572 but incompatible with each other. For instance Firefox will fail
to establish a connection if multiple fingerprints per m- line are
provided. So, I would say, we definitely need a document update to resolve
this ambiguity.

Regards,
_____________
Roman Shpount

On Fri, Oct 7, 2016 at 7:42 PM, Cullen Jennings <fluffy@iii.ca> wrote:

>
> There are lots of people using 4572 and there is nothing wrong with it.
> What is proposed in this draft is also fine and it if was RFCAAAA that is
> fine. But telling people doing 4572 that they have to do AAAA is not OK.
> You make not think that is what update means but it is what I and many
> others think update means. Given this disagreement on what update means, =
I
> don't want to use update.
>
> I'd be happy to write an alternative draft that does not need to be an
> update if that is the issue but I plan to get JSEP ready first.
>
>
> > On Oct 7, 2016, at 2:49 AM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
> >
> > Hi,
> >
> > First, being this late in the process, I think it would be fair to
> explain
> > (I would have expected the chairs to request the same) what the problem
> > is. We HAVE added the note saying that the draft does NOT make existing
> > 4572 implementations non-compliant. What else is missing?
> >
> > Second, IMO the draft says a little more than =C2=B3multiple fingerprin=
ts are
> > allowed=C2=B2. It also specifies HOW multiple fingerprints are used, HO=
W they
> > must be matched etc - using RFC 2119 terminology (there is a number of
> > MUSTs). Do we consider that =C2=B3advice=C2=B2? Or, do you want to REMO=
VE that?
> >
> > Last, if we don=C2=B9t indicate the draft as a =C2=B34572 update=C2=B2,=
 people will not
> > automatically be made aware of it when looking for 4572, as it will not
> be
> > listed as an 4572 update. Is that a good thing?
> >
> > Regards,
> >
> > Christer
> >
> >
> >
> >
> >
> > On 07/10/16 00:39, "mmusic on behalf of Cullen Jennings"
> > <mmusic-bounces@ietf.org on behalf of fluffy@iii.ca> wrote:
> >
> >>
> >> It would be easy to rewrite it to not change it but simply clarify tha=
t
> >> multiple fingerprints are allowed and provide advice about additional
> >> ones to provide.
> >>
> >>
> >>> On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)
> >>> <fluffy@cisco.com> wrote:
> >>>
> >>>
> >>> So I still disagree that this should update 4572 and the text for the
> >>> interoperability issue if significantly different than what many peop=
le
> >>> proposed on list. Can we arrange a phone call to discuss this.
> >>>
> >>>
> >>>
> >>>> On Sep 25, 2016, at 7:53 AM, internet-drafts@ietf.org wrote:
> >>>>
> >>>>
> >>>> A New Internet-Draft is available from the on-line Internet-Drafts
> >>>> directories.
> >>>> This draft is a work item of the Multiparty Multimedia Session Contr=
ol
> >>>> of the IETF.
> >>>>
> >>>>      Title           : SDP Fingerprint Attribute Usage Clarification=
s
> >>>>      Author          : Christer Holmberg
> >>>>    Filename        : draft-ietf-mmusic-4572-update-07.txt
> >>>>    Pages           : 8
> >>>>    Date            : 2016-09-25
> >>>>
> >>>> Abstract:
> >>>> This document updates RFC 4572 by clarifying the usage of multiple
> >>>> SDP 'fingerprint' attributes with a single SDP media description ("m=
=3D
> >>>> line").  The document also updates the preferred cipher suite with a
> >>>> stronger cipher suite.
> >>>>
> >>>>
> >>>> The IETF datatracker status page for this draft is:
> >>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/
> >>>>
> >>>> There's also a htmlized version available at:
> >>>> https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07
> >>>>
> >>>> A diff from the previous version is available at:
> >>>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-4572-update-07
> >>>>
> >>>>
> >>>> 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/
> >>>>
> >>>> _______________________________________________
> >>>> I-D-Announce mailing list
> >>>> I-D-Announce@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/i-d-announce
> >>>> Internet-Draft directories: http://www.ietf.org/shadow.html
> >>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>>
> >>> _______________________________________________
> >>> 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
> >
> > _______________________________________________
> > 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
>

--001a113fe12e1d3afe053e4f40f5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Cullen,<div><br></div><div>Can you answer a fundamental qu=
estion related to 4572: Does it allow multiple fingerprint attributes per o=
ne m- line or not? Can you point to the exact language in the RFC which say=
s that?</div><div><br></div><div>There are people (including the authors of=
 RFC 4572) which gave contradictory answers to this question. Because of th=
ese contradictory answers, you can create two implementations which claim t=
o be compatible with 4572 but incompatible with each other. For instance Fi=
refox will fail to establish a connection if multiple fingerprints per m- l=
ine are provided. So, I would say, we definitely need a document update to =
resolve this ambiguity.<div class=3D"gmail_extra"><br></div><div class=3D"g=
mail_extra">Regards,<br clear=3D"all"><div><div class=3D"gmail_signature" d=
ata-smartmail=3D"gmail_signature">_____________<br>Roman Shpount</div></div=
>
<br><div class=3D"gmail_quote">On Fri, Oct 7, 2016 at 7:42 PM, Cullen Jenni=
ngs <span dir=3D"ltr">&lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank=
">fluffy@iii.ca</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br=
>
There are lots of people using 4572 and there is nothing wrong with it. Wha=
t is proposed in this draft is also fine and it if was RFCAAAA that is fine=
. But telling people doing 4572 that they have to do AAAA is not OK. You ma=
ke not think that is what update means but it is what I and many others thi=
nk update means. Given this disagreement on what update means, I don&#39;t =
want to use update.<br>
<br>
I&#39;d be happy to write an alternative draft that does not need to be an =
update if that is the issue but I plan to get JSEP ready first.<br>
<br>
<br>
&gt; On Oct 7, 2016, at 2:49 AM, Christer Holmberg &lt;<a href=3D"mailto:ch=
rister.holmberg@ericsson.com">christer.holmberg@ericsson.<wbr>com</a>&gt; w=
rote:<br>
&gt;<br>
&gt; Hi,<br>
&gt;<br>
&gt; First, being this late in the process, I think it would be fair to exp=
lain<br>
&gt; (I would have expected the chairs to request the same) what the proble=
m<br>
&gt; is. We HAVE added the note saying that the draft does NOT make existin=
g<br>
&gt; 4572 implementations non-compliant. What else is missing?<br>
&gt;<br>
&gt; Second, IMO the draft says a little more than =C2=B3multiple fingerpri=
nts are<br>
&gt; allowed=C2=B2. It also specifies HOW multiple fingerprints are used, H=
OW they<br>
&gt; must be matched etc - using RFC 2119 terminology (there is a number of=
<br>
&gt; MUSTs). Do we consider that =C2=B3advice=C2=B2? Or, do you want to REM=
OVE that?<br>
&gt;<br>
&gt; Last, if we don=C2=B9t indicate the draft as a =C2=B34572 update=C2=B2=
, people will not<br>
&gt; automatically be made aware of it when looking for 4572, as it will no=
t be<br>
&gt; listed as an 4572 update. Is that a good thing?<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Christer<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On 07/10/16 00:39, &quot;mmusic on behalf of Cullen Jennings&quot;<br>
&gt; &lt;<a href=3D"mailto:mmusic-bounces@ietf.org">mmusic-bounces@ietf.org=
</a> on behalf of <a href=3D"mailto:fluffy@iii.ca">fluffy@iii.ca</a>&gt; wr=
ote:<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; It would be easy to rewrite it to not change it but simply clarify=
 that<br>
&gt;&gt; multiple fingerprints are allowed and provide advice about additio=
nal<br>
&gt;&gt; ones to provide.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)<br>
&gt;&gt;&gt; &lt;<a href=3D"mailto:fluffy@cisco.com">fluffy@cisco.com</a>&g=
t; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; So I still disagree that this should update 4572 and the text =
for the<br>
&gt;&gt;&gt; interoperability issue if significantly different than what ma=
ny people<br>
&gt;&gt;&gt; proposed on list. Can we arrange a phone call to discuss this.=
<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On Sep 25, 2016, at 7:53 AM, <a href=3D"mailto:internet-dr=
afts@ietf.org">internet-drafts@ietf.org</a> wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; A New Internet-Draft is available from the on-line Interne=
t-Drafts<br>
&gt;&gt;&gt;&gt; directories.<br>
&gt;&gt;&gt;&gt; This draft is a work item of the Multiparty Multimedia Ses=
sion Control<br>
&gt;&gt;&gt;&gt; of the IETF.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0: SDP Fingerprint Attribute Usage Clarifications<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 : Christer Holmberg<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-i=
etf-mmusic-4572-update-<wbr>07.txt<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0: 8<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 : 2016-09-25<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Abstract:<br>
&gt;&gt;&gt;&gt; This document updates RFC 4572 by clarifying the usage of =
multiple<br>
&gt;&gt;&gt;&gt; SDP &#39;fingerprint&#39; attributes with a single SDP med=
ia description (&quot;m=3D<br>
&gt;&gt;&gt;&gt; line&quot;).=C2=A0 The document also updates the preferred=
 cipher suite with a<br>
&gt;&gt;&gt;&gt; stronger cipher suite.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The IETF datatracker status page for this draft is:<br>
&gt;&gt;&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmu=
sic-4572-update/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.=
ietf.org/<wbr>doc/draft-ietf-mmusic-4572-<wbr>update/</a><br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; There&#39;s also a htmlized version available at:<br>
&gt;&gt;&gt;&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-4=
572-update-07" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/=
html/<wbr>draft-ietf-mmusic-4572-update-<wbr>07</a><br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; A diff from the previous version is available at:<br>
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-=
mmusic-4572-update-07" rel=3D"noreferrer" target=3D"_blank">https://www.iet=
f.org/rfcdiff?<wbr>url2=3Ddraft-ietf-mmusic-4572-<wbr>update-07</a><br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Please note that it may take a couple of minutes from the =
time of<br>
&gt;&gt;&gt;&gt; submission<br>
&gt;&gt;&gt;&gt; until the htmlized version and diff are available at <a hr=
ef=3D"http://tools.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.iet=
f.org</a>.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Internet-Drafts are also available by anonymous FTP at:<br=
>
&gt;&gt;&gt;&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"nor=
eferrer" target=3D"_blank">ftp://ftp.ietf.org/internet-<wbr>drafts/</a><br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt;&gt;&gt; I-D-Announce mailing list<br>
&gt;&gt;&gt;&gt; <a href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf=
.org</a><br>
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/i-d-annou=
nce" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr=
>listinfo/i-d-announce</a><br>
&gt;&gt;&gt;&gt; Internet-Draft directories: <a href=3D"http://www.ietf.org=
/shadow.html" rel=3D"noreferrer" target=3D"_blank">http://www.ietf.org/shad=
ow.<wbr>html</a><br>
&gt;&gt;&gt;&gt; or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" r=
el=3D"noreferrer" target=3D"_blank">ftp://ftp.ietf.org/ietf/<wbr>1shadow-si=
tes.txt</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt;&gt; mmusic mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinf=
o/mmusic</a><br>
&gt;&gt;<br>
&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt; mmusic mailing list<br>
&gt;&gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"no=
referrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmus=
ic</a><br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; mmusic mailing list<br>
&gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"norefe=
rrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</=
a><br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
</blockquote></div><br></div></div></div>

--001a113fe12e1d3afe053e4f40f5--


From nobody Fri Oct  7 21:53:08 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79673129435 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 21:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 pPES7-49FO99 for <mmusic@ietfa.amsl.com>; Fri,  7 Oct 2016 21:53:04 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 D560F1293F4 for <mmusic@ietf.org>; Fri,  7 Oct 2016 21:53:03 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id t193so43383939ywc.2 for <mmusic@ietf.org>; Fri, 07 Oct 2016 21:53:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WWa3P9tUnIOA10bkfp2HPa7mghlvUwh3QeLj+O/jBDI=; b=p0nKuOcqRtw22tBDCiXeYCxOt3Bc13y/ih96bJX7vYWwz3tHIfVfwyRtbDatvjvxrM 3PcXTEoixApdb06f7Z5dPeHRukYUObVUR9vtPuQpmTkFSH24Yx3Z8d3nFOP8zBvJVqC4 duODrBkrdrBHcTjJw7RGulzkZ1NkKJLWddGKXLVKdpl7/b8OxqKWlyuKyB56nSHooodW 0LYaR7eV5qwjPiqogjUkzrqIv6dOVeIU2vY0j55lq7ZnR1kDJFltdvCf2FL7vdKzk2Wk IL8+z80LYE6w8z5YVgTelX741tOtTRJytYEOmHXJ8p0dVActV0XR1Cp7z8f5iCvPlkgP wSGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WWa3P9tUnIOA10bkfp2HPa7mghlvUwh3QeLj+O/jBDI=; b=MRmsUgycSBhY019z2xmd7VTvwIwMERSaTXt0GQT7ldMMun3fCO3WkRBVHHluClbjB3 3l8IIJHEEDzDlnKqzcG/bZ0zm6sazX+x2R7ejZ89JHcZOXYkbf5KJVgHNDLLEXtk1ig8 nXKKhj5Xdpb4JfVuE/lNLPgTa79D61NkF1YKjDzH7a2GKDAfVdDnceV5ceXJnXVXWDg0 0BllhaUGkbp1UxvGeq0BxaPJ/uLl18z3LM9qbMyCwE7CowsOwY0D6AlrWpiXCcmuxnAI aBGBHzL2FWxybx/saVb5uvbEeJsZcqiMbFL9WrJN3PbFQ8/TchR1BG/Am3uJS2phM+B0 TK3w==
X-Gm-Message-State: AA6/9Rl/4aEX71uG9XUgyO+n3XerAsabi+N+ouaVQn8e4wk7fP6JYnR00lQD8yZnbspG0o0VKOvsdTpw5F+tpQ==
X-Received: by 10.13.236.13 with SMTP id v13mr18153781ywe.5.1475902382892; Fri, 07 Oct 2016 21:53:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.158.73 with HTTP; Fri, 7 Oct 2016 21:53:02 -0700 (PDT)
In-Reply-To: <CABcZeBPpTskVnvFXgBNe=AfXFtu4R=1OMumsuWW8_th5KuLfyA@mail.gmail.com>
References: <CABcZeBPpTskVnvFXgBNe=AfXFtu4R=1OMumsuWW8_th5KuLfyA@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Fri, 7 Oct 2016 21:53:02 -0700
Message-ID: <CAMRcRGSr9ZWCSOLDH6-Nm-W+ppHnUSkc2Fau9+WzVVOTPpS3nQ@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Content-Type: multipart/alternative; boundary=94eb2c087e62417139053e534d3f
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/qdOeHA3aOQ5HRJkf-Pol1ZFuaWE>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] To duplicate or not duplicate
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 04:53:06 -0000

--94eb2c087e62417139053e534d3f
Content-Type: text/plain; charset=UTF-8

Hello Ekr

  Thoughts inline.

On Fri, Oct 7, 2016 at 4:41 PM, Eric Rescorla <ekr@rtfm.com> wrote:

> Section 4.3 of the sdp-mux-attributes document says:
> https://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-
> attributes-14#section-4.3
>
>     The attributes and their associated values (if any) in the IDENTICAL
>     category MUST be repeated across all the media descriptions under
>     multiplexing.
>
>
> Section 8.1 of the BUNDLE document says:
> https://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-
> negotiation-33#section-8.1
>
>    When an offerer associates SDP attributes with a bundled "m=" line
>    associated with a shared address, IDENTICAL and TRANSPORT mux
>    category SDP attributes [I-D.ietf-mmusic-sdp-mux-attributes] are
>    associated with the "m=" line only if the "m=" line is also
>    associated with the offerer BUNDLE-tag.  Otherwise the offerer MUST
>    NOT associate such SDP attributes with the "m=" line.
>
>
[Suhas]

I am not sure if you were able to follow the discussions on the same topic
here :

  https://www.ietf.org/mail-archive/web/mmusic/current/msg16929.html

I will try to summarize some points from the above discussion below :-

a) Section 8.1 of the BUNDLE spec refers to the state of the system when
the shared address is already known (after successful  bundle negotiation,
for example).
I do agree that once the BUNDLE address is know ,  the IDENTICAL and
TRANSPORT category attributes needs to be specified on that m=line alone.

b) Section 8.1 doesn't talk about the case for the initial offer (or when
the BUNDLE address is not yet known). The IDENTICAL category  is required
in this case for the Offerer to specify its intent as the Software is
unable to make the decision otherwise.
The very specific example is a=rtcp-mux attribute. In the initial Offer, if
the Offerer wants to multiplex RTP/RTCP it needs to include it in all the
m=lines (as defined by the IDENTICAL category). This is because, if the
BUNDLE semantics gets rejected the offerer can still do
 RTP/RTCP multiplexing on all the m=lines.
OTOH, if a=rtcp-mux was included only in the m=line whose mid was listed as
the first in the a=group:BUNDLE line and the BUNDLE semantics gets
rejected, there is no way for the Software to auto imply RTCP multiplexing
or not. This is when the current semantics of the IDENTICAL category ( as
defined in section 4.3 of mux-attributes draft) come into play.

Thus i do believe that there needs to be clarification, in the Section 8.1
of BUNDLE spec, on the interpretation of the IDENTICAL category attributes
before and after the BUNDLE address selection process. It already handles
the post shared address selection but it lacks the pre-selection
consideration.



> I submit that BUNDLE is right here and the mux attributes document is
> wrong and
> we should not duplicate.
>
> -Ekr
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

--94eb2c087e62417139053e534d3f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div>Hello Ekr</div><div><br></div><div>=C2=A0 Thought=
s inline.</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On=
 Fri, Oct 7, 2016 at 4:41 PM, Eric Rescorla <span dir=3D"ltr">&lt;<a href=
=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt;</span> wrot=
e:<br><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>Section 4.3 of the sdp-mux-attributes document says:</div><div><a href=
=3D"https://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-14#sec=
tion-4.3" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft-ietf-mmu=
sic-sdp-mux-<wbr>attributes-14#section-4.3</a></div><div><br></div><div>=C2=
=A0 =C2=A0 The attributes and their associated values (if any) in the IDENT=
ICAL</div><div>=C2=A0 =C2=A0 category MUST be repeated across all the media=
 descriptions under</div><div>=C2=A0 =C2=A0 multiplexing.</div><div><br></d=
iv><div><br></div><div>Section 8.1 of the BUNDLE document says:</div><div><=
a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiat=
ion-33#section-8.1" target=3D"_blank">https://tools.ietf.org/html/<wbr>draf=
t-ietf-mmusic-sdp-bundle-<wbr>negotiation-33#section-8.1</a></div><div><br>=
</div><div>=C2=A0 =C2=A0When an offerer associates SDP attributes with a bu=
ndled &quot;m=3D&quot; line</div><div>=C2=A0 =C2=A0associated with a shared=
 address, IDENTICAL and TRANSPORT mux</div><div>=C2=A0 =C2=A0category SDP a=
ttributes [I-D.ietf-mmusic-sdp-mux-<wbr>attributes] are</div><div>=C2=A0 =
=C2=A0associated with the &quot;m=3D&quot; line only if the &quot;m=3D&quot=
; line is also</div><div>=C2=A0 =C2=A0associated with the offerer BUNDLE-ta=
g.=C2=A0 Otherwise the offerer MUST</div><div>=C2=A0 =C2=A0NOT associate su=
ch SDP attributes with the &quot;m=3D&quot; line.</div><div><br></div></div=
></blockquote><div><br></div><div><font color=3D"#cc0000">[Suhas]</font></d=
iv><div><font color=3D"#cc0000"><br></font></div><div><font color=3D"#cc000=
0">I am not sure if you were able to follow the discussions on the same top=
ic here :=C2=A0</font></div><div><font color=3D"#cc0000"><br></font></div><=
div><font color=3D"#cc0000">=C2=A0 <a href=3D"https://www.ietf.org/mail-arc=
hive/web/mmusic/current/msg16929.html">https://www.ietf.org/mail-archive/we=
b/mmusic/current/msg16929.html</a></font></div><div><font color=3D"#cc0000"=
><br></font></div><div><font color=3D"#cc0000">I will try to summarize some=
 points from the above discussion below :-</font></div><div><font color=3D"=
#cc0000"><br></font></div><div><font color=3D"#cc0000">a) Section 8.1 of th=
e BUNDLE spec refers to the state of the system when the shared address is =
already known (after successful =C2=A0bundle negotiation, for example).=C2=
=A0</font></div><div><font color=3D"#cc0000">I do agree that once the BUNDL=
E address is know , =C2=A0the IDENTICAL and TRANSPORT category attributes n=
eeds to be specified on that m=3Dline alone.</font></div><div><font color=
=3D"#cc0000"><br></font></div><div><font color=3D"#cc0000">b) Section 8.1 d=
oesn&#39;t talk about the case for the initial offer (or when the BUNDLE ad=
dress is not yet known). The IDENTICAL category =C2=A0is required in this c=
ase for the Offerer to specify its intent as the Software is unable to make=
 the decision otherwise.=C2=A0</font></div><div><font color=3D"#cc0000">The=
 very specific example is a=3Drtcp-mux attribute. In the initial Offer, if =
the Offerer wants to multiplex RTP/RTCP it needs to include it in all the m=
=3Dlines (as defined by the IDENTICAL category). This is because, if the BU=
NDLE semantics gets rejected the offerer can still do =C2=A0RTP/RTCP=C2=A0m=
ultiplexing on all the m=3Dlines.=C2=A0</font></div><div><font color=3D"#cc=
0000">OTOH, if a=3Drtcp-mux was included only in the m=3Dline whose mid was=
 listed as the first in the a=3Dgroup:BUNDLE line and the BUNDLE semantics =
gets rejected, there is no way for the Software to auto imply RTCP multiple=
xing or not. This is when the current semantics of the IDENTICAL category (=
 as defined in section 4.3 of mux-attributes draft) come into play.</font><=
/div><div><font color=3D"#cc0000"><br></font></div><div><font color=3D"#cc0=
000">Thus i do believe that there needs to be clarification, in the Section=
 8.1 of BUNDLE spec, on the interpretation of the IDENTICAL category attrib=
utes before and after the BUNDLE address selection process. It already hand=
les the post shared address selection but it lacks the pre-selection consid=
eration.</font></div><div><font color=3D"#351c75"><br></font></div><div><br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><=
div></div><div><br></div><div>I submit that BUNDLE is right here and the mu=
x attributes document is wrong and</div><div>we should not duplicate.</div>=
<div><br></div><div>-Ekr</div><div><br></div></div>
<br>______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
<br></blockquote></div><br></div></div>

--94eb2c087e62417139053e534d3f--


From nobody Sat Oct  8 09:01:53 2016
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 994CF129567 for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 09:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.197
X-Spam-Level: 
X-Spam-Status: No, score=-7.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.996, 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 athP2muwmJfw for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 09:01:50 -0700 (PDT)
Received: from alum-mailsec-scanner-2.mit.edu (alum-mailsec-scanner-2.mit.edu [18.7.68.13]) by ietfa.amsl.com (Postfix) with ESMTP id 31810129544 for <mmusic@ietf.org>; Sat,  8 Oct 2016 09:01:50 -0700 (PDT)
X-AuditID: 1207440d-4ddff700000009a7-ae-57f9186c1ba1
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id 6E.26.02471.C6819F75; Sat,  8 Oct 2016 12:01:49 -0400 (EDT)
Received: from [192.168.1.110] (c-73-186-127-100.hsd1.ma.comcast.net [73.186.127.100]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id u98G1lcH002459 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Sat, 8 Oct 2016 12:01:48 -0400
To: mmusic@ietf.org
References: <147481162395.28315.18346373858565370012.idtracker@ietfa.amsl.com> <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com> <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca> <D41D4800.10A3F%christer.holmberg@ericsson.com> <68971202-4458-407D-A4AF-BCDCE54F2F78@iii.ca>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <ba29c562-fe49-c1f1-d2ba-5bdf3621f9b6@alum.mit.edu>
Date: Sat, 8 Oct 2016 12:01:47 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <68971202-4458-407D-A4AF-BCDCE54F2F78@iii.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNIsWRmVeSWpSXmKPExsUixO6iqJsr8TPc4NteGYupyx+zODB6LFny kymAMYrLJiU1J7MstUjfLoErY/GepewFn9Uq1s3eytjA+FS+i5GTQ0LARGLSsrMsXYxcHEIC lxkl9l5azw7hvGGS2LL7PAtIlbCAm8Tv6wuYQGwRAWGJGW//skEUTWaSOPXyKFgRm4CWxJxD /8FsXgF7ia0bNgBN4uBgEVCR2PjfAiQsKpAmsX3dbmaIEkGJkzOfgJVzClhJvPt9ghXEZhaw lbgzF6KGWUBeonnrbOYJjHyzkLTMQlI2C0nZAkbmVYxyiTmlubq5iZk5xanJusXJiXl5qUW6 Rnq5mSV6qSmlmxghYca7g/H/OplDjAIcjEo8vALrv4cLsSaWFVfmHmKU5GBSEuVNPPEjXIgv KT+lMiOxOCO+qDQntfgQowQHs5IIb574z3Ah3pTEyqrUonyYlDQHi5I4r9oSdT8hgfTEktTs 1NSC1CKYrAwHh5IErxNIo2BRanpqRVpmTglCmomDE2Q4D9BwU7DhxQWJucWZ6RD5U4yKUuK8 C8WAEgIgiYzSPLheWBp4xSgO9IowbwtIOw8whcB1vwIazAQ0mGXxD5DBJYkIKakGxtzH+9i3 yKiWCq2/8S/7CPdU+3Dt542GO87YGVTvuOR08d6zehW1BMdLHFNupUV8fPb07bGdysncXvpu D+NuFt9fd1S00+aWzvOHhtPMK7hPhdrOTTAvbo/oWbKfWTRDbN/+q9v/yvv8n6XI37v961mb v8LpPkfDFOZuX/8xONu44+NRe9nrW5VYijMSDbWYi4oTAVGFD97eAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/h5U3MJUWUuY_DW8eV7RPRVtOPkQ>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 16:01:52 -0000

Cullen,

On 10/7/16 7:42 PM, Cullen Jennings wrote:
>
> There are lots of people using 4572 and there is nothing wrong with it. What is proposed in this draft is also fine and it if was RFCAAAA that is fine. But telling people doing 4572 that they have to do AAAA is not OK. You make not think that is what update means but it is what I and many others think update means. Given this disagreement on what update means, I don't want to use update.

I know you were following the wgchairs thread on '"Updates: RFC xxx" - 
what does it actually mean ?' because you replied in that thread. If you 
agree with the conclusion there then I don't see how you can conclude 
that people implementing a base draft MUST implement a "updates" draft.

	Thanks,
	Paul

> I'd be happy to write an alternative draft that does not need to be an update if that is the issue but I plan to get JSEP ready first.
>
>
>> On Oct 7, 2016, at 2:49 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
>>
>> Hi,
>>
>> First, being this late in the process, I think it would be fair to explain
>> (I would have expected the chairs to request the same) what the problem
>> is. We HAVE added the note saying that the draft does NOT make existing
>> 4572 implementations non-compliant. What else is missing?
>>
>> Second, IMO the draft says a little more than ³multiple fingerprints are
>> allowed². It also specifies HOW multiple fingerprints are used, HOW they
>> must be matched etc - using RFC 2119 terminology (there is a number of
>> MUSTs). Do we consider that ³advice²? Or, do you want to REMOVE that?
>>
>> Last, if we don¹t indicate the draft as a ³4572 update², people will not
>> automatically be made aware of it when looking for 4572, as it will not be
>> listed as an 4572 update. Is that a good thing?
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>>
>>
>> On 07/10/16 00:39, "mmusic on behalf of Cullen Jennings"
>> <mmusic-bounces@ietf.org on behalf of fluffy@iii.ca> wrote:
>>
>>>
>>> It would be easy to rewrite it to not change it but simply clarify that
>>> multiple fingerprints are allowed and provide advice about additional
>>> ones to provide.
>>>
>>>
>>>> On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)
>>>> <fluffy@cisco.com> wrote:
>>>>
>>>>
>>>> So I still disagree that this should update 4572 and the text for the
>>>> interoperability issue if significantly different than what many people
>>>> proposed on list. Can we arrange a phone call to discuss this.
>>>>
>>>>
>>>>
>>>>> On Sep 25, 2016, at 7:53 AM, internet-drafts@ietf.org wrote:
>>>>>
>>>>>
>>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>>> directories.
>>>>> This draft is a work item of the Multiparty Multimedia Session Control
>>>>> of the IETF.
>>>>>
>>>>>      Title           : SDP Fingerprint Attribute Usage Clarifications
>>>>>      Author          : Christer Holmberg
>>>>> 	Filename        : draft-ietf-mmusic-4572-update-07.txt
>>>>> 	Pages           : 8
>>>>> 	Date            : 2016-09-25
>>>>>
>>>>> Abstract:
>>>>> This document updates RFC 4572 by clarifying the usage of multiple
>>>>> SDP 'fingerprint' attributes with a single SDP media description ("m=
>>>>> line").  The document also updates the preferred cipher suite with a
>>>>> stronger cipher suite.
>>>>>
>>>>>
>>>>> The IETF datatracker status page for this draft is:
>>>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/
>>>>>
>>>>> There's also a htmlized version available at:
>>>>> https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07
>>>>>
>>>>> A diff from the previous version is available at:
>>>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-4572-update-07
>>>>>
>>>>>
>>>>> 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/
>>>>>
>>>>> _______________________________________________
>>>>> I-D-Announce mailing list
>>>>> I-D-Announce@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>>
>>>> _______________________________________________
>>>> 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
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Sat Oct  8 10:19:19 2016
Return-Path: <fluffy@iii.ca>
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 5DF5D129544 for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 10:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 4QGNCwJ92uCM for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 10:19:15 -0700 (PDT)
Received: from smtp90.ord1c.emailsrvr.com (smtp90.ord1c.emailsrvr.com [108.166.43.90]) (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 5DC531295EB for <mmusic@ietf.org>; Sat,  8 Oct 2016 10:19:12 -0700 (PDT)
Received: from smtp4.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id B9828A0146; Sat,  8 Oct 2016 13:19:11 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 1174DA0132;  Sat,  8 Oct 2016 13:19:10 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.24.57.2] ([UNAVAILABLE]. [128.107.241.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.7); Sat, 08 Oct 2016 13:19:11 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_ABF35C9C-DE5B-4757-911B-EF6DFA79645C"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CAD5OKxvgTAw2ptSupXuEvTS8k=5Pncv0aYV=XRX81jTPjB5VSA@mail.gmail.com>
Date: Sat, 8 Oct 2016 10:19:09 -0700
Message-Id: <35A6A72A-5832-48D1-81D3-AF1AF31E34B5@iii.ca>
References: <147481162395.28315.18346373858565370012.idtracker@ietfa.amsl.com> <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com> <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca> <D41D4800.10A3F%christer.holmberg@ericsson.com> <68971202-4458-407D-A4AF-BCDCE54F2F78@iii.ca> <CAD5OKxvgTAw2ptSupXuEvTS8k=5Pncv0aYV=XRX81jTPjB5VSA@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ZBN-Vm57eaAz5yhsbqr3tisI5Ac>
Cc: mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 17:19:18 -0000

--Apple-Mail=_ABF35C9C-DE5B-4757-911B-EF6DFA79645C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


I am one of the people that believes they are allowed by 4572 because =
SDP explicitly allows multiple copies of a=3D extensions and this =
defines an a=3D extension. I believe SDP explicitly says that. However, =
I agree with your point that is not clear. As I have said in the past, I =
am fine with an update that clarifies this point.

I am not fine with an update that changes what ciphers are needed. I am =
fine with an extention, not update, that mandates the SHA 256 and people =
that want to implement that can but people that do not can still do =
4572.=20


> On Oct 7, 2016, at 5:03 PM, Roman Shpount <roman@telurix.com> wrote:
>=20
> Cullen,
>=20
> Can you answer a fundamental question related to 4572: Does it allow =
multiple fingerprint attributes per one m- line or not? Can you point to =
the exact language in the RFC which says that?
>=20
> There are people (including the authors of RFC 4572) which gave =
contradictory answers to this question. Because of these contradictory =
answers, you can create two implementations which claim to be compatible =
with 4572 but incompatible with each other. For instance Firefox will =
fail to establish a connection if multiple fingerprints per m- line are =
provided. So, I would say, we definitely need a document update to =
resolve this ambiguity.
>=20
> Regards,
> _____________
> Roman Shpount
>=20
> On Fri, Oct 7, 2016 at 7:42 PM, Cullen Jennings <fluffy@iii.ca =
<mailto:fluffy@iii.ca>> wrote:
>=20
> There are lots of people using 4572 and there is nothing wrong with =
it. What is proposed in this draft is also fine and it if was RFCAAAA =
that is fine. But telling people doing 4572 that they have to do AAAA is =
not OK. You make not think that is what update means but it is what I =
and many others think update means. Given this disagreement on what =
update means, I don't want to use update.
>=20
> I'd be happy to write an alternative draft that does not need to be an =
update if that is the issue but I plan to get JSEP ready first.
>=20
>=20
> > On Oct 7, 2016, at 2:49 AM, Christer Holmberg =
<christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>> =
wrote:
> >
> > Hi,
> >
> > First, being this late in the process, I think it would be fair to =
explain
> > (I would have expected the chairs to request the same) what the =
problem
> > is. We HAVE added the note saying that the draft does NOT make =
existing
> > 4572 implementations non-compliant. What else is missing?
> >
> > Second, IMO the draft says a little more than =C2=B3multiple =
fingerprints are
> > allowed=C2=B2. It also specifies HOW multiple fingerprints are used, =
HOW they
> > must be matched etc - using RFC 2119 terminology (there is a number =
of
> > MUSTs). Do we consider that =C2=B3advice=C2=B2? Or, do you want to =
REMOVE that?
> >
> > Last, if we don=C2=B9t indicate the draft as a =C2=B34572 update=C2=B2=
, people will not
> > automatically be made aware of it when looking for 4572, as it will =
not be
> > listed as an 4572 update. Is that a good thing?
> >
> > Regards,
> >
> > Christer
> >
> >
> >
> >
> >
> > On 07/10/16 00:39, "mmusic on behalf of Cullen Jennings"
> > <mmusic-bounces@ietf.org <mailto:mmusic-bounces@ietf.org> on behalf =
of fluffy@iii.ca <mailto:fluffy@iii.ca>> wrote:
> >
> >>
> >> It would be easy to rewrite it to not change it but simply clarify =
that
> >> multiple fingerprints are allowed and provide advice about =
additional
> >> ones to provide.
> >>
> >>
> >>> On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)
> >>> <fluffy@cisco.com <mailto:fluffy@cisco.com>> wrote:
> >>>
> >>>
> >>> So I still disagree that this should update 4572 and the text for =
the
> >>> interoperability issue if significantly different than what many =
people
> >>> proposed on list. Can we arrange a phone call to discuss this.
> >>>
> >>>
> >>>
> >>>> On Sep 25, 2016, at 7:53 AM, internet-drafts@ietf.org =
<mailto:internet-drafts@ietf.org> wrote:
> >>>>
> >>>>
> >>>> A New Internet-Draft is available from the on-line =
Internet-Drafts
> >>>> directories.
> >>>> This draft is a work item of the Multiparty Multimedia Session =
Control
> >>>> of the IETF.
> >>>>
> >>>>      Title           : SDP Fingerprint Attribute Usage =
Clarifications
> >>>>      Author          : Christer Holmberg
> >>>>    Filename        : draft-ietf-mmusic-4572-update-07.txt
> >>>>    Pages           : 8
> >>>>    Date            : 2016-09-25
> >>>>
> >>>> Abstract:
> >>>> This document updates RFC 4572 by clarifying the usage of =
multiple
> >>>> SDP 'fingerprint' attributes with a single SDP media description =
("m=3D
> >>>> line").  The document also updates the preferred cipher suite =
with a
> >>>> stronger cipher suite.
> >>>>
> >>>>
> >>>> The IETF datatracker status page for this draft is:
> >>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/ =
<https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/>
> >>>>
> >>>> There's also a htmlized version available at:
> >>>> https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07 =
<https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07>
> >>>>
> >>>> A diff from the previous version is available at:
> >>>> =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-4572-update-07 =
<https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-4572-update-07>
> >>>>
> >>>>
> >>>> Please note that it may take a couple of minutes from the time of
> >>>> submission
> >>>> until the htmlized version and diff are available at =
tools.ietf.org <http://tools.ietf.org/>.
> >>>>
> >>>> Internet-Drafts are also available by anonymous FTP at:
> >>>> ftp://ftp.ietf.org/internet-drafts/ =
<ftp://ftp.ietf.org/internet-drafts/>
> >>>>
> >>>> _______________________________________________
> >>>> I-D-Announce mailing list
> >>>> I-D-Announce@ietf.org <mailto:I-D-Announce@ietf.org>
> >>>> https://www.ietf.org/mailman/listinfo/i-d-announce =
<https://www.ietf.org/mailman/listinfo/i-d-announce>
> >>>> Internet-Draft directories: http://www.ietf.org/shadow.html =
<http://www.ietf.org/shadow.html>
> >>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt =
<ftp://ftp.ietf.org/ietf/1shadow-sites.txt>
> >>>
> >>> _______________________________________________
> >>> mmusic mailing list
> >>> mmusic@ietf.org <mailto:mmusic@ietf.org>
> >>> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
> >>
> >> _______________________________________________
> >> mmusic mailing list
> >> mmusic@ietf.org <mailto:mmusic@ietf.org>
> >> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org <mailto:mmusic@ietf.org>
> > https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org <mailto:mmusic@ietf.org>
> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


--Apple-Mail=_ABF35C9C-DE5B-4757-911B-EF6DFA79645C
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; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D""><br class=3D""></div>I am one of the people =
that believes they are allowed by 4572 because SDP explicitly allows =
multiple copies of a=3D extensions and this defines an a=3D extension. I =
believe SDP explicitly says that. However, I agree with your point that =
is not clear. As I have said in the past, I am fine with an update that =
clarifies this point.<div class=3D""><br class=3D""></div><div =
class=3D"">I am not fine with an update that changes what ciphers are =
needed. I am fine with an extention, not update, that mandates the SHA =
256 and people that want to implement that can but people that do not =
can still do 4572.&nbsp;</div><div class=3D""><br class=3D""><div =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Oct 7, 2016, at 5:03 PM, 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"">Cullen,<div class=3D""><br class=3D""></div><div =
class=3D"">Can you answer a fundamental question related to 4572: Does =
it allow multiple fingerprint attributes per one m- line or not? Can you =
point to the exact language in the RFC which says that?</div><div =
class=3D""><br class=3D""></div><div class=3D"">There are people =
(including the authors of RFC 4572) which gave contradictory answers to =
this question. Because of these contradictory answers, you can create =
two implementations which claim to be compatible with 4572 but =
incompatible with each other. For instance Firefox will fail to =
establish a connection if multiple fingerprints per m- line are =
provided. So, I would say, we definitely need a document update to =
resolve this ambiguity.<div class=3D"gmail_extra"><br =
class=3D""></div><div class=3D"gmail_extra">Regards,<br clear=3D"all" =
class=3D""><div class=3D""><div class=3D"gmail_signature" =
data-smartmail=3D"gmail_signature">_____________<br class=3D"">Roman =
Shpount</div></div>
<br class=3D""><div class=3D"gmail_quote">On Fri, Oct 7, 2016 at 7:42 =
PM, Cullen Jennings <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:fluffy@iii.ca" target=3D"_blank" =
class=3D"">fluffy@iii.ca</a>&gt;</span> wrote:<br class=3D""><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><br class=3D"">
There are lots of people using 4572 and there is nothing wrong with it. =
What is proposed in this draft is also fine and it if was RFCAAAA that =
is fine. But telling people doing 4572 that they have to do AAAA is not =
OK. You make not think that is what update means but it is what I and =
many others think update means. Given this disagreement on what update =
means, I don't want to use update.<br class=3D"">
<br class=3D"">
I'd be happy to write an alternative draft that does not need to be an =
update if that is the issue but I plan to get JSEP ready first.<br =
class=3D"">
<br class=3D"">
<br class=3D"">
&gt; On Oct 7, 2016, at 2:49 AM, Christer Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com" =
class=3D"">christer.holmberg@ericsson.<wbr class=3D"">com</a>&gt; =
wrote:<br class=3D"">
&gt;<br class=3D"">
&gt; Hi,<br class=3D"">
&gt;<br class=3D"">
&gt; First, being this late in the process, I think it would be fair to =
explain<br class=3D"">
&gt; (I would have expected the chairs to request the same) what the =
problem<br class=3D"">
&gt; is. We HAVE added the note saying that the draft does NOT make =
existing<br class=3D"">
&gt; 4572 implementations non-compliant. What else is missing?<br =
class=3D"">
&gt;<br class=3D"">
&gt; Second, IMO the draft says a little more than =C2=B3multiple =
fingerprints are<br class=3D"">
&gt; allowed=C2=B2. It also specifies HOW multiple fingerprints are =
used, HOW they<br class=3D"">
&gt; must be matched etc - using RFC 2119 terminology (there is a number =
of<br class=3D"">
&gt; MUSTs). Do we consider that =C2=B3advice=C2=B2? Or, do you want to =
REMOVE that?<br class=3D"">
&gt;<br class=3D"">
&gt; Last, if we don=C2=B9t indicate the draft as a =C2=B34572 update=C2=B2=
, people will not<br class=3D"">
&gt; automatically be made aware of it when looking for 4572, as it will =
not be<br class=3D"">
&gt; listed as an 4572 update. Is that a good thing?<br class=3D"">
&gt;<br class=3D"">
&gt; Regards,<br class=3D"">
&gt;<br class=3D"">
&gt; Christer<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt; On 07/10/16 00:39, "mmusic on behalf of Cullen Jennings"<br =
class=3D"">
&gt; &lt;<a href=3D"mailto:mmusic-bounces@ietf.org" =
class=3D"">mmusic-bounces@ietf.org</a> on behalf of <a =
href=3D"mailto:fluffy@iii.ca" class=3D"">fluffy@iii.ca</a>&gt; wrote:<br =
class=3D"">
&gt;<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; It would be easy to rewrite it to not change it but simply =
clarify that<br class=3D"">
&gt;&gt; multiple fingerprints are allowed and provide advice about =
additional<br class=3D"">
&gt;&gt; ones to provide.<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt;&gt; On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)<br =
class=3D"">
&gt;&gt;&gt; &lt;<a href=3D"mailto:fluffy@cisco.com" =
class=3D"">fluffy@cisco.com</a>&gt; wrote:<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt; So I still disagree that this should update 4572 and the =
text for the<br class=3D"">
&gt;&gt;&gt; interoperability issue if significantly different than what =
many people<br class=3D"">
&gt;&gt;&gt; proposed on list. Can we arrange a phone call to discuss =
this.<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; On Sep 25, 2016, at 7:53 AM, <a =
href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a> wrote:<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; A New Internet-Draft is available from the on-line =
Internet-Drafts<br class=3D"">
&gt;&gt;&gt;&gt; directories.<br class=3D"">
&gt;&gt;&gt;&gt; This draft is a work item of the Multiparty Multimedia =
Session Control<br class=3D"">
&gt;&gt;&gt;&gt; of the IETF.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; Title&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;: SDP Fingerprint Attribute Usage Clarifications<br =
class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; Author&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; : Christer Holmberg<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; Filename&nbsp; &nbsp; &nbsp; &nbsp; : =
draft-ietf-mmusic-4572-update-<wbr class=3D"">07.txt<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; Pages&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;: 8<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; Date&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; : 2016-09-25<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Abstract:<br class=3D"">
&gt;&gt;&gt;&gt; This document updates RFC 4572 by clarifying the usage =
of multiple<br class=3D"">
&gt;&gt;&gt;&gt; SDP 'fingerprint' attributes with a single SDP media =
description ("m=3D<br class=3D"">
&gt;&gt;&gt;&gt; line").&nbsp; The document also updates the preferred =
cipher suite with a<br class=3D"">
&gt;&gt;&gt;&gt; stronger cipher suite.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; The IETF datatracker status page for this draft is:<br =
class=3D"">
&gt;&gt;&gt;&gt; <a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://datatracker.ietf.org/<wbr =
class=3D"">doc/draft-ietf-mmusic-4572-<wbr class=3D"">update/</a><br =
class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; There's also a htmlized version available at:<br =
class=3D"">
&gt;&gt;&gt;&gt; <a =
href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/<wbr =
class=3D"">draft-ietf-mmusic-4572-update-<wbr class=3D"">07</a><br =
class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; A diff from the previous version is available at:<br =
class=3D"">
&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-4572-update-=
07" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/rfcdiff?<wbr =
class=3D"">url2=3Ddraft-ietf-mmusic-4572-<wbr class=3D"">update-07</a><br =
class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Please note that it may take a couple of minutes from =
the time of<br class=3D"">
&gt;&gt;&gt;&gt; submission<br class=3D"">
&gt;&gt;&gt;&gt; until the htmlized version and diff are available at <a =
href=3D"http://tools.ietf.org/" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">tools.ietf.org</a>.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Internet-Drafts are also available by anonymous FTP =
at:<br class=3D"">
&gt;&gt;&gt;&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">ftp://ftp.ietf.org/internet-<wbr class=3D"">drafts/</a><br =
class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; ______________________________<wbr =
class=3D"">_________________<br class=3D"">
&gt;&gt;&gt;&gt; I-D-Announce mailing list<br class=3D"">
&gt;&gt;&gt;&gt; <a href=3D"mailto:I-D-Announce@ietf.org" =
class=3D"">I-D-Announce@ietf.org</a><br class=3D"">
&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/<wbr =
class=3D"">listinfo/i-d-announce</a><br class=3D"">
&gt;&gt;&gt;&gt; Internet-Draft directories: <a =
href=3D"http://www.ietf.org/shadow.html" rel=3D"noreferrer" =
target=3D"_blank" class=3D"">http://www.ietf.org/shadow.<wbr =
class=3D"">html</a><br class=3D"">
&gt;&gt;&gt;&gt; or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">ftp://ftp.ietf.org/ietf/<wbr =
class=3D"">1shadow-sites.txt</a><br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt; ______________________________<wbr =
class=3D"">_________________<br class=3D"">
&gt;&gt;&gt; mmusic mailing list<br class=3D"">
&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" =
class=3D"">mmusic@ietf.org</a><br class=3D"">
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/<wbr =
class=3D"">listinfo/mmusic</a><br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; ______________________________<wbr =
class=3D"">_________________<br class=3D"">
&gt;&gt; mmusic mailing list<br class=3D"">
&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" =
class=3D"">mmusic@ietf.org</a><br class=3D"">
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/<wbr =
class=3D"">listinfo/mmusic</a><br class=3D"">
&gt;<br class=3D"">
&gt; ______________________________<wbr class=3D"">_________________<br =
class=3D"">
&gt; mmusic mailing list<br class=3D"">
&gt; <a href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a><br =
class=3D"">
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/<wbr =
class=3D"">listinfo/mmusic</a><br class=3D"">
<br class=3D"">
______________________________<wbr class=3D"">_________________<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"">
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/<wbr =
class=3D"">listinfo/mmusic</a><br class=3D"">
</blockquote></div><br class=3D""></div></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></div></body></html>=

--Apple-Mail=_ABF35C9C-DE5B-4757-911B-EF6DFA79645C--


From nobody Sat Oct  8 11:33:37 2016
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 D8288129503 for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 11:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 qA7p9TxfSYbB for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 11:33:34 -0700 (PDT)
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 B16FB1295F8 for <mmusic@ietf.org>; Sat,  8 Oct 2016 11:33:33 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-61-57f93bfbc322
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by  (Symantec Mail Security) with SMTP id 84.32.02458.BFB39F75; Sat,  8 Oct 2016 20:33:31 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0319.002; Sat, 8 Oct 2016 20:33:29 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Cullen Jennings <fluffy@iii.ca>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
Thread-Index: AQHSG0GgBWsMgAttg0WZUBo1tL92NKCb3CYAgAD/+ICAALTUgIAABa6AgAEhfoCAADZLPA==
Date: Sat, 8 Oct 2016 18:33:28 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD3994A@ESESSMB209.ericsson.se>
References: <147481162395.28315.18346373858565370012.idtracker@ietfa.amsl.com> <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com> <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca> <D41D4800.10A3F%christer.holmberg@ericsson.com> <68971202-4458-407D-A4AF-BCDCE54F2F78@iii.ca> <CAD5OKxvgTAw2ptSupXuEvTS8k=5Pncv0aYV=XRX81jTPjB5VSA@mail.gmail.com>, <35A6A72A-5832-48D1-81D3-AF1AF31E34B5@iii.ca>
In-Reply-To: <35A6A72A-5832-48D1-81D3-AF1AF31E34B5@iii.ca>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BD3994AESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIIsWRmVeSWpSXmKPExsUyM2K7tO5v65/hBifvmFp8WP+D0WLq8scs FjMuTGV2YPZYsuQnk8fl8x8ZPW5NKQhgjuKySUnNySxLLdK3S+DKWPtErmDrCsaKBxPrGhgb JjJ2MXJySAiYSJyYtp65i5GLQ0hgPaPE4p4drBDOYkaJRTtfAWU4ONgELCS6/2mDNIgIuEns fv+VDcRmFpCRmHG2kQmkRBgovvaxJUSJu8TsWfPYIOwwiZ9rJ7OA2CwCKhKfTmwFi/MK+Eo8 W/iCEWJVB7PE+stnmUASnAJWEhOv/AVrYBQQk/h+ag0TxC5xiaYvK1khjhaQWLLnPDOELSrx 8vE/VoiafInL3Y3sEAsEJU7OfMIygVF4FpL2WUjKZiEpg4gbSHx5fxvK1pZYtvA1M4StL9H9 /jQTsvgCRvZVjKLFqcXFuelGRnqpRZnJxcX5eXp5qSWbGIERdXDLb6sdjAefOx5iFOBgVOLh XfDoe7gQa2JZcWXuIUYJDmYlEd5gi5/hQrwpiZVVqUX58UWlOanFhxilOViUxHnNVt4PFxJI TyxJzU5NLUgtgskycXBKNTCu49FKSRUWqbM/7e54ykSi5JObwcsjJxvORP/3qtqSVH0kJDs7 pG1L+KZF8hfytp4992wm///Z1i07rq5xdz/5Q+3jwSz/hLk3dB03/uqUOJzO6cdw9cLZ1SUy AvO2cAhcmjPNYfW93l/7H7d7rbog2qq653x3j6iKvfBV+ctnpsTXrVnB5nRViaU4I9FQi7mo OBEAzJTFqKQCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9wUcDgtNutg3IcHrCl7aq_pMMgw>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 18:33:37 -0000

--_000_7594FB04B1934943A5C02806D1A2204B4BD3994AESESSMB209erics_
Content-Type: text/plain; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

Hi,

Would you be ok with the draft if we removed the cipher change?

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Cullen Jennings<mailto:fluffy@iii.ca>
Sent: =FD08/=FD10/=FD2016 20:19
To: Roman Shpount<mailto:roman@telurix.com>
Cc: mmusic<mailto:mmusic@ietf.org>; Christer Holmberg<mailto:christer.holmb=
erg@ericsson.com>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt


I am one of the people that believes they are allowed by 4572 because SDP e=
xplicitly allows multiple copies of a=3D extensions and this defines an a=
=3D extension. I believe SDP explicitly says that. However, I agree with yo=
ur point that is not clear. As I have said in the past, I am fine with an u=
pdate that clarifies this point.

I am not fine with an update that changes what ciphers are needed. I am fin=
e with an extention, not update, that mandates the SHA 256 and people that =
want to implement that can but people that do not can still do 4572.


On Oct 7, 2016, at 5:03 PM, Roman Shpount <roman@telurix.com<mailto:roman@t=
elurix.com>> wrote:

Cullen,

Can you answer a fundamental question related to 4572: Does it allow multip=
le fingerprint attributes per one m- line or not? Can you point to the exac=
t language in the RFC which says that?

There are people (including the authors of RFC 4572) which gave contradicto=
ry answers to this question. Because of these contradictory answers, you ca=
n create two implementations which claim to be compatible with 4572 but inc=
ompatible with each other. For instance Firefox will fail to establish a co=
nnection if multiple fingerprints per m- line are provided. So, I would say=
, we definitely need a document update to resolve this ambiguity.

Regards,
_____________
Roman Shpount

On Fri, Oct 7, 2016 at 7:42 PM, Cullen Jennings <fluffy@iii.ca<mailto:fluff=
y@iii.ca>> wrote:

There are lots of people using 4572 and there is nothing wrong with it. Wha=
t is proposed in this draft is also fine and it if was RFCAAAA that is fine=
. But telling people doing 4572 that they have to do AAAA is not OK. You ma=
ke not think that is what update means but it is what I and many others thi=
nk update means. Given this disagreement on what update means, I don't want=
 to use update.

I'd be happy to write an alternative draft that does not need to be an upda=
te if that is the issue but I plan to get JSEP ready first.


> On Oct 7, 2016, at 2:49 AM, Christer Holmberg <christer.holmberg@ericsson=
.com<mailto:christer.holmberg@ericsson.com>> wrote:
>
> Hi,
>
> First, being this late in the process, I think it would be fair to explai=
n
> (I would have expected the chairs to request the same) what the problem
> is. We HAVE added the note saying that the draft does NOT make existing
> 4572 implementations non-compliant. What else is missing?
>
> Second, IMO the draft says a little more than =B3multiple fingerprints ar=
e
> allowed=B2. It also specifies HOW multiple fingerprints are used, HOW the=
y
> must be matched etc - using RFC 2119 terminology (there is a number of
> MUSTs). Do we consider that =B3advice=B2? Or, do you want to REMOVE that?
>
> Last, if we don=B9t indicate the draft as a =B34572 update=B2, people wil=
l not
> automatically be made aware of it when looking for 4572, as it will not b=
e
> listed as an 4572 update. Is that a good thing?
>
> Regards,
>
> Christer
>
>
>
>
>
> On 07/10/16 00:39, "mmusic on behalf of Cullen Jennings"
> <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org> on behalf of flu=
ffy@iii.ca<mailto:fluffy@iii.ca>> wrote:
>
>>
>> It would be easy to rewrite it to not change it but simply clarify that
>> multiple fingerprints are allowed and provide advice about additional
>> ones to provide.
>>
>>
>>> On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)
>>> <fluffy@cisco.com<mailto:fluffy@cisco.com>> wrote:
>>>
>>>
>>> So I still disagree that this should update 4572 and the text for the
>>> interoperability issue if significantly different than what many people
>>> proposed on list. Can we arrange a phone call to discuss this.
>>>
>>>
>>>
>>>> On Sep 25, 2016, at 7:53 AM, internet-drafts@ietf.org<mailto:internet-=
drafts@ietf.org> wrote:
>>>>
>>>>
>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>> directories.
>>>> This draft is a work item of the Multiparty Multimedia Session Control
>>>> of the IETF.
>>>>
>>>>      Title           : SDP Fingerprint Attribute Usage Clarifications
>>>>      Author          : Christer Holmberg
>>>>    Filename        : draft-ietf-mmusic-4572-update-07.txt
>>>>    Pages           : 8
>>>>    Date            : 2016-09-25
>>>>
>>>> Abstract:
>>>> This document updates RFC 4572 by clarifying the usage of multiple
>>>> SDP 'fingerprint' attributes with a single SDP media description ("m=
=3D
>>>> line").  The document also updates the preferred cipher suite with a
>>>> stronger cipher suite.
>>>>
>>>>
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/
>>>>
>>>> There's also a htmlized version available at:
>>>> https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07
>>>>
>>>> A diff from the previous version is available at:
>>>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-4572-update-07
>>>>
>>>>
>>>> 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<ht=
tp://tools.ietf.org/>.
>>>>
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>> _______________________________________________
>>>> I-D-Announce mailing list
>>>> I-D-Announce@ietf.org<mailto:I-D-Announce@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org<mailto:mmusic@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org<mailto:mmusic@ietf.org>
>> https://www.ietf.org/mailman/listinfo/mmusic
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org<mailto:mmusic@ietf.org>
> https://www.ietf.org/mailman/listinfo/mmusic

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

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


--_000_7594FB04B1934943A5C02806D1A2204B4BD3994AESESSMB209erics_
Content-Type: text/html; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
256">
</head>
<body class=3D"" style=3D"word-wrap:break-word">
<div>
<div style=3D"font-family:Calibri,sans-serif; font-size:11pt">Hi,<br>
<br>
Would you be ok with the draft if we removed the cipher change?<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">From:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:fluffy@iii.ca">Cullen Jennings</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Sent:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">=FD08=
/=FD10/=FD2016 20:19</span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">To:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:roman@telurix.com">Roman Shpount</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Cc:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:mmusic@ietf.org">mmusic</a>;
<a href=3D"mailto:christer.holmberg@ericsson.com">Christer Holmberg</a></sp=
an><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Subject:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">Re: [=
MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt</span><br>
<br>
</div>
<div>
<div class=3D""><br class=3D"">
</div>
I am one of the people that believes they are allowed by 4572 because SDP e=
xplicitly allows multiple copies of a=3D extensions and this defines an a=
=3D extension. I believe SDP explicitly says that. However, I agree with yo=
ur point that is not clear. As I have
 said in the past, I am fine with an update that clarifies this point.
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I am not fine with an update that changes what ciphers are =
needed. I am fine with an extention, not update, that mandates the SHA 256 =
and people that want to implement that can but people that do not can still=
 do 4572.&nbsp;</div>
<div class=3D""><br class=3D"">
<div class=3D""><br class=3D"">
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On Oct 7, 2016, at 5:03 PM, Roman Shpount &lt;<a href=3D"ma=
ilto: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"">Cullen,
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Can you answer a fundamental question related to 4572: Does=
 it allow multiple fingerprint attributes per one m- line or not? Can you p=
oint to the exact language in the RFC which says that?</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">There are people (including the authors of RFC 4572) which =
gave contradictory answers to this question. Because of these contradictory=
 answers, you can create two implementations which claim to be compatible w=
ith 4572 but incompatible with each
 other. For instance Firefox will fail to establish a connection if multipl=
e fingerprints per m- line are provided. So, I would say, we definitely nee=
d a document update to resolve this ambiguity.
<div class=3D"gmail_extra"><br class=3D"">
</div>
<div class=3D"gmail_extra">Regards,<br clear=3D"all" class=3D"">
<div class=3D"">
<div class=3D"gmail_signature">_____________<br class=3D"">
Roman Shpount</div>
</div>
<br class=3D"">
<div class=3D"gmail_quote">On Fri, Oct 7, 2016 at 7:42 PM, Cullen Jennings =
<span dir=3D"ltr" class=3D"">
&lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank" class=3D"">fluffy@ii=
i.ca</a>&gt;</span> wrote:<br class=3D"">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<br class=3D"">
There are lots of people using 4572 and there is nothing wrong with it. Wha=
t is proposed in this draft is also fine and it if was RFCAAAA that is fine=
. But telling people doing 4572 that they have to do AAAA is not OK. You ma=
ke not think that is what update
 means but it is what I and many others think update means. Given this disa=
greement on what update means, I don't want to use update.<br class=3D"">
<br class=3D"">
I'd be happy to write an alternative draft that does not need to be an upda=
te if that is the issue but I plan to get JSEP ready first.<br class=3D"">
<br class=3D"">
<br class=3D"">
&gt; On Oct 7, 2016, at 2:49 AM, Christer Holmberg &lt;<a href=3D"mailto:ch=
rister.holmberg@ericsson.com" class=3D"">christer.holmberg@ericsson.<wbr cl=
ass=3D"">com</a>&gt; wrote:<br class=3D"">
&gt;<br class=3D"">
&gt; Hi,<br class=3D"">
&gt;<br class=3D"">
&gt; First, being this late in the process, I think it would be fair to exp=
lain<br class=3D"">
&gt; (I would have expected the chairs to request the same) what the proble=
m<br class=3D"">
&gt; is. We HAVE added the note saying that the draft does NOT make existin=
g<br class=3D"">
&gt; 4572 implementations non-compliant. What else is missing?<br class=3D"=
">
&gt;<br class=3D"">
&gt; Second, IMO the draft says a little more than =B3multiple fingerprints=
 are<br class=3D"">
&gt; allowed=B2. It also specifies HOW multiple fingerprints are used, HOW =
they<br class=3D"">
&gt; must be matched etc - using RFC 2119 terminology (there is a number of=
<br class=3D"">
&gt; MUSTs). Do we consider that =B3advice=B2? Or, do you want to REMOVE th=
at?<br class=3D"">
&gt;<br class=3D"">
&gt; Last, if we don=B9t indicate the draft as a =B34572 update=B2, people =
will not<br class=3D"">
&gt; automatically be made aware of it when looking for 4572, as it will no=
t be<br class=3D"">
&gt; listed as an 4572 update. Is that a good thing?<br class=3D"">
&gt;<br class=3D"">
&gt; Regards,<br class=3D"">
&gt;<br class=3D"">
&gt; Christer<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt; On 07/10/16 00:39, &quot;mmusic on behalf of Cullen Jennings&quot;<br =
class=3D"">
&gt; &lt;<a href=3D"mailto:mmusic-bounces@ietf.org" class=3D"">mmusic-bounc=
es@ietf.org</a> on behalf of
<a href=3D"mailto:fluffy@iii.ca" class=3D"">fluffy@iii.ca</a>&gt; wrote:<br=
 class=3D"">
&gt;<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; It would be easy to rewrite it to not change it but simply clarify=
 that<br class=3D"">
&gt;&gt; multiple fingerprints are allowed and provide advice about additio=
nal<br class=3D"">
&gt;&gt; ones to provide.<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt;&gt; On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)<br clas=
s=3D"">
&gt;&gt;&gt; &lt;<a href=3D"mailto:fluffy@cisco.com" class=3D"">fluffy@cisc=
o.com</a>&gt; wrote:<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt; So I still disagree that this should update 4572 and the text =
for the<br class=3D"">
&gt;&gt;&gt; interoperability issue if significantly different than what ma=
ny people<br class=3D"">
&gt;&gt;&gt; proposed on list. Can we arrange a phone call to discuss this.=
<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; On Sep 25, 2016, at 7:53 AM, <a href=3D"mailto:internet-dr=
afts@ietf.org" class=3D"">
internet-drafts@ietf.org</a> wrote:<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; A New Internet-Draft is available from the on-line Interne=
t-Drafts<br class=3D"">
&gt;&gt;&gt;&gt; directories.<br class=3D"">
&gt;&gt;&gt;&gt; This draft is a work item of the Multiparty Multimedia Ses=
sion Control<br class=3D"">
&gt;&gt;&gt;&gt; of the IETF.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; Title&nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp;: SDP Fingerprint Attribute Usage Clarifications<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; Author&nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; : Christer Holmberg<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; Filename&nbsp; &nbsp; &nbsp; &nbsp; : draft-i=
etf-mmusic-4572-update-<wbr class=3D"">07.txt<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; Pages&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;: 8<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; Date&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 : 2016-09-25<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Abstract:<br class=3D"">
&gt;&gt;&gt;&gt; This document updates RFC 4572 by clarifying the usage of =
multiple<br class=3D"">
&gt;&gt;&gt;&gt; SDP 'fingerprint' attributes with a single SDP media descr=
iption (&quot;m=3D<br class=3D"">
&gt;&gt;&gt;&gt; line&quot;).&nbsp; The document also updates the preferred=
 cipher suite with a<br class=3D"">
&gt;&gt;&gt;&gt; stronger cipher suite.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; The IETF datatracker status page for this draft is:<br cla=
ss=3D"">
&gt;&gt;&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmu=
sic-4572-update/" rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://datatracker.ietf.org/<wbr class=3D"">doc/draft-ietf-mmusic-4572-<wb=
r class=3D"">update/</a><br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; There's also a htmlized version available at:<br class=3D"=
">
&gt;&gt;&gt;&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-4=
572-update-07" rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://tools.ietf.org/html/<wbr class=3D"">draft-ietf-mmusic-4572-update-<=
wbr class=3D"">07</a><br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; A diff from the previous version is available at:<br class=
=3D"">
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-=
mmusic-4572-update-07" rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://www.ietf.org/rfcdiff?<wbr class=3D"">url2=3Ddraft-ietf-mmusic-4572-=
<wbr class=3D"">update-07</a><br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Please note that it may take a couple of minutes from the =
time of<br class=3D"">
&gt;&gt;&gt;&gt; submission<br class=3D"">
&gt;&gt;&gt;&gt; until the htmlized version and diff are available at <a hr=
ef=3D"http://tools.ietf.org/" rel=3D"noreferrer" target=3D"_blank" class=3D=
"">
tools.ietf.org</a>.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Internet-Drafts are also available by anonymous FTP at:<br=
 class=3D"">
&gt;&gt;&gt;&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"nor=
eferrer" target=3D"_blank" class=3D"">
ftp://ftp.ietf.org/internet-<wbr class=3D"">drafts/</a><br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; ______________________________<wbr class=3D"">____________=
_____<br class=3D"">
&gt;&gt;&gt;&gt; I-D-Announce mailing list<br class=3D"">
&gt;&gt;&gt;&gt; <a href=3D"mailto:I-D-Announce@ietf.org" class=3D"">I-D-An=
nounce@ietf.org</a><br class=3D"">
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/i-d-annou=
nce" rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://www.ietf.org/mailman/<wbr class=3D"">listinfo/i-d-announce</a><br c=
lass=3D"">
&gt;&gt;&gt;&gt; Internet-Draft directories: <a href=3D"http://www.ietf.org=
/shadow.html" rel=3D"noreferrer" target=3D"_blank" class=3D"">
http://www.ietf.org/shadow.<wbr class=3D"">html</a><br class=3D"">
&gt;&gt;&gt;&gt; or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" r=
el=3D"noreferrer" target=3D"_blank" class=3D"">
ftp://ftp.ietf.org/ietf/<wbr class=3D"">1shadow-sites.txt</a><br class=3D""=
>
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt; ______________________________<wbr class=3D"">________________=
_<br class=3D"">
&gt;&gt;&gt; mmusic mailing list<br class=3D"">
&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org<=
/a><br class=3D"">
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=
=3D"noreferrer" target=3D"_blank" class=3D"">
https://www.ietf.org/mailman/<wbr class=3D"">listinfo/mmusic</a><br class=
=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; ______________________________<wbr class=3D"">_________________<br=
 class=3D"">
&gt;&gt; mmusic mailing list<br class=3D"">
&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a><=
br class=3D"">
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"no=
referrer" target=3D"_blank" class=3D"">
https://www.ietf.org/mailman/<wbr class=3D"">listinfo/mmusic</a><br class=
=3D"">
&gt;<br class=3D"">
&gt; ______________________________<wbr class=3D"">_________________<br cla=
ss=3D"">
&gt; mmusic mailing list<br class=3D"">
&gt; <a href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a><br c=
lass=3D"">
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"norefe=
rrer" target=3D"_blank" class=3D"">
https://www.ietf.org/mailman/<wbr class=3D"">listinfo/mmusic</a><br class=
=3D"">
<br class=3D"">
______________________________<wbr class=3D"">_________________<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"">
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank" class=3D"">https://www.ietf.org/mailman/<wbr class=3D"">=
listinfo/mmusic</a><br class=3D"">
</blockquote>
</div>
<br class=3D"">
</div>
</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>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B4BD3994AESESSMB209erics_--


From nobody Sat Oct  8 11:42:39 2016
Return-Path: <fluffy@iii.ca>
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 C8F491295F4 for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 11:42:37 -0700 (PDT)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aNeEfiX5g6Hv for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 11:42:36 -0700 (PDT)
Received: from smtp82.ord1c.emailsrvr.com (smtp82.ord1c.emailsrvr.com [108.166.43.82]) (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 69955129493 for <mmusic@ietf.org>; Sat,  8 Oct 2016 11:42:36 -0700 (PDT)
Received: from smtp27.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp27.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id B6CF940106; Sat,  8 Oct 2016 14:42:35 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp27.relay.ord1c.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 6E7DC40096;  Sat,  8 Oct 2016 14:42:35 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.24.57.2] ([UNAVAILABLE]. [128.107.241.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.7); Sat, 08 Oct 2016 14:42:35 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_FC03FF55-2073-4660-A000-8E8C511A8F07"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <ba29c562-fe49-c1f1-d2ba-5bdf3621f9b6@alum.mit.edu>
Date: Sat, 8 Oct 2016 11:42:34 -0700
Message-Id: <BEA54B46-C68E-44DC-BA7F-16E2E80094A9@iii.ca>
References: <147481162395.28315.18346373858565370012.idtracker@ietfa.amsl.com> <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com> <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca> <D41D4800.10A3F%christer.holmberg@ericsson.com> <68971202-4458-407D-A4AF-BCDCE54F2F78@iii.ca> <ba29c562-fe49-c1f1-d2ba-5bdf3621f9b6@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/EOpkjQs-mfvfEF-y-ZTDacw98PE>
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 18:42:38 -0000

--Apple-Mail=_FC03FF55-2073-4660-A000-8E8C511A8F07
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


> On Oct 8, 2016, at 9:01 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>=20
>=20
> I know you were following the wgchairs thread on '"Updates: RFC xxx" - =
what does it actually mean ?' because you replied in that thread. If you =
agree with the conclusion there th

The conclusion of that thread - after it expanded beyond the chairs list =
- was AFAIC, that this was unclear and someone should write a RFC to =
clarify it. If you think there was consensus on what update means, then =
I strongly agree and invite you to go look at number of people that put =
out position on each side. Until a new RFC gets issues, I will use the =
meaning in the only published RFC that defined this even though it was =
deprecated by a later RFC that did not provide any definition one way or =
the other. =20

And to be clear, what I am proposing here is a simple way for this WG to =
move forward without having to resolve that debate or wait for consensus =
on what update means.=20



--Apple-Mail=_FC03FF55-2073-4660-A000-8E8C511A8F07
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Oct 8, 2016, at 9:01 AM, Paul Kyzivat &lt;<a =
href=3D"mailto:pkyzivat@alum.mit.edu" =
class=3D"">pkyzivat@alum.mit.edu</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><br =
style=3D"font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">I know you were =
following the wgchairs thread on '"Updates: RFC xxx" - what does it =
actually mean ?' because you replied in that thread. If you agree with =
the conclusion there th</span></div></blockquote></div><br class=3D""><div=
 class=3D"">The conclusion of that thread - after it expanded beyond the =
chairs list - was AFAIC, that this was unclear and someone should write =
a RFC to clarify it. If you think there was consensus on what update =
means, then I strongly agree and invite you to go look at number of =
people that put out position on each side. Until a new RFC gets issues, =
I will use the meaning in the only published RFC that defined this even =
though it was deprecated by a later RFC that did not provide any =
definition one way or the other. &nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">And to be clear, what I am proposing =
here is a simple way for this WG to move forward without having to =
resolve that debate or wait for consensus on what update =
means.&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D""><br=
 class=3D""></div></body></html>=

--Apple-Mail=_FC03FF55-2073-4660-A000-8E8C511A8F07--


From nobody Sat Oct  8 11:45:28 2016
Return-Path: <fluffy@iii.ca>
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 F178D1295F4 for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 11:45:25 -0700 (PDT)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tKr8tm5HbzW1 for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 11:45:23 -0700 (PDT)
Received: from smtp122.iad3a.emailsrvr.com (smtp122.iad3a.emailsrvr.com [173.203.187.122]) (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 3C379129493 for <mmusic@ietf.org>; Sat,  8 Oct 2016 11:45:23 -0700 (PDT)
Received: from smtp40.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp40.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 8227F24CFC; Sat,  8 Oct 2016 14:45:17 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp40.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id C0AFE24C94;  Sat,  8 Oct 2016 14:45:16 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.24.57.2] ([UNAVAILABLE]. [128.107.241.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.7); Sat, 08 Oct 2016 14:45:17 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_72CC25CC-1C56-4F8A-8937-C80869BE57FF"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD3994A@ESESSMB209.ericsson.se>
Date: Sat, 8 Oct 2016 11:45:15 -0700
Message-Id: <7FB846E7-8D25-43CA-B08C-EB73EEE635C9@iii.ca>
References: <147481162395.28315.18346373858565370012.idtracker@ietfa.amsl.com> <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com> <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca> <D41D4800.10A3F%christer.holmberg@ericsson.com> <68971202-4458-407D-A4AF-BCDCE54F2F78@iii.ca> <CAD5OKxvgTAw2ptSupXuEvTS8k=5Pncv0aYV=XRX81jTPjB5VSA@mail.gmail.com> <35A6A72A-5832-48D1-81D3-AF1AF31E34B5@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD3994A@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/VH3PIm4rFZ0yT-PzIKxnRX0Ayh8>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 18:45:26 -0000

--Apple-Mail=_72CC25CC-1C56-4F8A-8937-C80869BE57FF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

or split the change to clarify multiple fingerprints in a a draft that =
was and update and then published something along the lines of this =
draft that added the requirement for SHA 256. I'm not at all against =
requiring SHA 256 for WebRTC or other things, I'm against requiring that =
for things that do 4572.=20

> On Oct 8, 2016, at 11:33 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> Would you be ok with the draft if we removed the cipher change?
>=20
> Regards,
>=20
> Christer
>=20
> Sent from my Windows Phone
> From: Cullen Jennings <mailto:fluffy@iii.ca>
> Sent: =E2=80=8E08/=E2=80=8E10/=E2=80=8E2016 20:19
> To: Roman Shpount <mailto:roman@telurix.com>
> Cc: mmusic <mailto:mmusic@ietf.org>; Christer Holmberg =
<mailto:christer.holmberg@ericsson.com>
> Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
>=20
>=20
> I am one of the people that believes they are allowed by 4572 because =
SDP explicitly allows multiple copies of a=3D extensions and this =
defines an a=3D extension. I believe SDP explicitly says that. However, =
I agree with your point that is not clear. As I have said in the past, I =
am fine with an update that clarifies this point.
>=20
> I am not fine with an update that changes what ciphers are needed. I =
am fine with an extention, not update, that mandates the SHA 256 and =
people that want to implement that can but people that do not can still =
do 4572.=20
>=20
>=20
>> On Oct 7, 2016, at 5:03 PM, Roman Shpount <roman@telurix.com =
<mailto:roman@telurix.com>> wrote:
>>=20
>> Cullen,
>>=20
>> Can you answer a fundamental question related to 4572: Does it allow =
multiple fingerprint attributes per one m- line or not? Can you point to =
the exact language in the RFC which says that?
>>=20
>> There are people (including the authors of RFC 4572) which gave =
contradictory answers to this question. Because of these contradictory =
answers, you can create two implementations which claim to be compatible =
with 4572 but incompatible with each other. For instance Firefox will =
fail to establish a connection if multiple fingerprints per m- line are =
provided. So, I would say, we definitely need a document update to =
resolve this ambiguity.
>>=20
>> Regards,
>> _____________
>> Roman Shpount
>>=20
>> On Fri, Oct 7, 2016 at 7:42 PM, Cullen Jennings <fluffy@iii.ca =
<mailto:fluffy@iii.ca>> wrote:
>>=20
>> There are lots of people using 4572 and there is nothing wrong with =
it. What is proposed in this draft is also fine and it if was RFCAAAA =
that is fine. But telling people doing 4572 that they have to do AAAA is =
not OK. You make not think that is what update means but it is what I =
and many others think update means. Given this disagreement on what =
update means, I don't want to use update.
>>=20
>> I'd be happy to write an alternative draft that does not need to be =
an update if that is the issue but I plan to get JSEP ready first.
>>=20
>>=20
>> > On Oct 7, 2016, at 2:49 AM, Christer Holmberg =
<christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>> =
wrote:
>> >
>> > Hi,
>> >
>> > First, being this late in the process, I think it would be fair to =
explain
>> > (I would have expected the chairs to request the same) what the =
problem
>> > is. We HAVE added the note saying that the draft does NOT make =
existing
>> > 4572 implementations non-compliant. What else is missing?
>> >
>> > Second, IMO the draft says a little more than =C2=B3multiple =
fingerprints are
>> > allowed=C2=B2. It also specifies HOW multiple fingerprints are =
used, HOW they
>> > must be matched etc - using RFC 2119 terminology (there is a number =
of
>> > MUSTs). Do we consider that =C2=B3advice=C2=B2? Or, do you want to =
REMOVE that?
>> >
>> > Last, if we don=C2=B9t indicate the draft as a =C2=B34572 update=C2=B2=
, people will not
>> > automatically be made aware of it when looking for 4572, as it will =
not be
>> > listed as an 4572 update. Is that a good thing?
>> >
>> > Regards,
>> >
>> > Christer
>> >
>> >
>> >
>> >
>> >
>> > On 07/10/16 00:39, "mmusic on behalf of Cullen Jennings"
>> > <mmusic-bounces@ietf.org <mailto:mmusic-bounces@ietf.org> on behalf =
of fluffy@iii.ca <mailto:fluffy@iii.ca>> wrote:
>> >
>> >>
>> >> It would be easy to rewrite it to not change it but simply clarify =
that
>> >> multiple fingerprints are allowed and provide advice about =
additional
>> >> ones to provide.
>> >>
>> >>
>> >>> On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)
>> >>> <fluffy@cisco.com <mailto:fluffy@cisco.com>> wrote:
>> >>>
>> >>>
>> >>> So I still disagree that this should update 4572 and the text for =
the
>> >>> interoperability issue if significantly different than what many =
people
>> >>> proposed on list. Can we arrange a phone call to discuss this.
>> >>>
>> >>>
>> >>>
>> >>>> On Sep 25, 2016, at 7:53 AM, internet-drafts@ietf.org =
<mailto:internet-drafts@ietf.org> wrote:
>> >>>>
>> >>>>
>> >>>> A New Internet-Draft is available from the on-line =
Internet-Drafts
>> >>>> directories.
>> >>>> This draft is a work item of the Multiparty Multimedia Session =
Control
>> >>>> of the IETF.
>> >>>>
>> >>>>      Title           : SDP Fingerprint Attribute Usage =
Clarifications
>> >>>>      Author          : Christer Holmberg
>> >>>>    Filename        : draft-ietf-mmusic-4572-update-07.txt
>> >>>>    Pages           : 8
>> >>>>    Date            : 2016-09-25
>> >>>>
>> >>>> Abstract:
>> >>>> This document updates RFC 4572 by clarifying the usage of =
multiple
>> >>>> SDP 'fingerprint' attributes with a single SDP media description =
("m=3D
>> >>>> line").  The document also updates the preferred cipher suite =
with a
>> >>>> stronger cipher suite.
>> >>>>
>> >>>>
>> >>>> The IETF datatracker status page for this draft is:
>> >>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/ =
<https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/>
>> >>>>
>> >>>> There's also a htmlized version available at:
>> >>>> https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07 =
<https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07>
>> >>>>
>> >>>> A diff from the previous version is available at:
>> >>>> =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-4572-update-07 =
<https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-4572-update-07>
>> >>>>
>> >>>>
>> >>>> Please note that it may take a couple of minutes from the time =
of
>> >>>> submission
>> >>>> until the htmlized version and diff are available at =
tools.ietf.org <http://tools.ietf.org/>.
>> >>>>
>> >>>> Internet-Drafts are also available by anonymous FTP at:
>> >>>> ftp://ftp.ietf.org/internet-drafts/ =
<ftp://ftp.ietf.org/internet-drafts/>
>> >>>>
>> >>>> _______________________________________________
>> >>>> I-D-Announce mailing list
>> >>>> I-D-Announce@ietf.org <mailto:I-D-Announce@ietf.org>
>> >>>> https://www.ietf.org/mailman/listinfo/i-d-announce =
<https://www.ietf.org/mailman/listinfo/i-d-announce>
>> >>>> Internet-Draft directories: http://www.ietf.org/shadow.html =
<http://www.ietf.org/shadow.html>
>> >>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt =
<ftp://ftp.ietf.org/ietf/1shadow-sites.txt>
>> >>>
>> >>> _______________________________________________
>> >>> mmusic mailing list
>> >>> mmusic@ietf.org <mailto:mmusic@ietf.org>
>> >>> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
>> >>
>> >> _______________________________________________
>> >> mmusic mailing list
>> >> mmusic@ietf.org <mailto:mmusic@ietf.org>
>> >> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
>> >
>> > _______________________________________________
>> > mmusic mailing list
>> > mmusic@ietf.org <mailto:mmusic@ietf.org>
>> > https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
>>=20
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org <mailto:mmusic@ietf.org>
>> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
>>=20
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org <mailto:mmusic@ietf.org>
>> https://www.ietf.org/mailman/listinfo/mmusic
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


--Apple-Mail=_72CC25CC-1C56-4F8A-8937-C80869BE57FF
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; -webkit-line-break: after-white-space;" =
class=3D"">or split the change to clarify multiple fingerprints in a a =
draft that was and update and then published something along the lines =
of this draft that added the requirement for SHA 256. I'm not at all =
against requiring SHA 256 for WebRTC or other things, I'm against =
requiring that for things that do 4572.&nbsp;<div class=3D""><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Oct 8, 2016, at 11:33 AM, Christer Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com" =
class=3D"">christer.holmberg@ericsson.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dwindows-1256" class=3D"">

<div class=3D"" style=3D"word-wrap:break-word">
<div class=3D"">
<div style=3D"font-family:Calibri,sans-serif; font-size:11pt" =
class=3D"">Hi,<br class=3D"">
<br class=3D"">
Would you be ok with the draft if we removed the cipher change?<br =
class=3D"">
<br class=3D"">
Regards,<br class=3D"">
<br class=3D"">
Christer<br class=3D"">
<br class=3D"">
Sent from my Windows Phone</div>
</div>
<div dir=3D"ltr" class=3D"">
<hr class=3D"">
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; =
font-weight:bold" class=3D"">From:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt" =
class=3D""><a href=3D"mailto:fluffy@iii.ca" class=3D"">Cullen =
Jennings</a></span><br class=3D"">
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; =
font-weight:bold" class=3D"">Sent:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt" =
class=3D"">=E2=80=8E08/=E2=80=8E10/=E2=80=8E2016 20:19</span><br =
class=3D"">
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; =
font-weight:bold" class=3D"">To:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt" =
class=3D""><a href=3D"mailto:roman@telurix.com" class=3D"">Roman =
Shpount</a></span><br class=3D"">
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; =
font-weight:bold" class=3D"">Cc:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt" =
class=3D""><a href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic</a>;
<a href=3D"mailto:christer.holmberg@ericsson.com" class=3D"">Christer =
Holmberg</a></span><br class=3D"">
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; =
font-weight:bold" class=3D"">Subject:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt" =
class=3D"">Re: [MMUSIC] I-D Action: =
draft-ietf-mmusic-4572-update-07.txt</span><br class=3D"">
<br class=3D"">
</div>
<div class=3D"">
<div class=3D""><br class=3D"">
</div>
I am one of the people that believes they are allowed by 4572 because =
SDP explicitly allows multiple copies of a=3D extensions and this =
defines an a=3D extension. I believe SDP explicitly says that. However, =
I agree with your point that is not clear. As I have
 said in the past, I am fine with an update that clarifies this point.
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I am not fine with an update that changes what ciphers =
are needed. I am fine with an extention, not update, that mandates the =
SHA 256 and people that want to implement that can but people that do =
not can still do 4572.&nbsp;</div>
<div class=3D""><br class=3D"">
<div class=3D""><br class=3D"">
<div class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On Oct 7, 2016, at 5:03 PM, 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"">Cullen,
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Can you answer a fundamental question related to 4572: =
Does it allow multiple fingerprint attributes per one m- line or not? =
Can you point to the exact language in the RFC which says that?</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">There are people (including the authors of RFC 4572) =
which gave contradictory answers to this question. Because of these =
contradictory answers, you can create two implementations which claim to =
be compatible with 4572 but incompatible with each
 other. For instance Firefox will fail to establish a connection if =
multiple fingerprints per m- line are provided. So, I would say, we =
definitely need a document update to resolve this ambiguity.
<div class=3D"gmail_extra"><br class=3D"">
</div>
<div class=3D"gmail_extra">Regards,<br clear=3D"all" class=3D"">
<div class=3D"">
<div class=3D"gmail_signature">_____________<br class=3D"">
Roman Shpount</div>
</div>
<br class=3D"">
<div class=3D"gmail_quote">On Fri, Oct 7, 2016 at 7:42 PM, Cullen =
Jennings <span dir=3D"ltr" class=3D"">
&lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank" =
class=3D"">fluffy@iii.ca</a>&gt;</span> wrote:<br class=3D"">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; =
border-left:1px #ccc solid; padding-left:1ex">
<br class=3D"">
There are lots of people using 4572 and there is nothing wrong with it. =
What is proposed in this draft is also fine and it if was RFCAAAA that =
is fine. But telling people doing 4572 that they have to do AAAA is not =
OK. You make not think that is what update
 means but it is what I and many others think update means. Given this =
disagreement on what update means, I don't want to use update.<br =
class=3D"">
<br class=3D"">
I'd be happy to write an alternative draft that does not need to be an =
update if that is the issue but I plan to get JSEP ready first.<br =
class=3D"">
<br class=3D"">
<br class=3D"">
&gt; On Oct 7, 2016, at 2:49 AM, Christer Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com" =
class=3D"">christer.holmberg@ericsson.<wbr class=3D"">com</a>&gt; =
wrote:<br class=3D"">
&gt;<br class=3D"">
&gt; Hi,<br class=3D"">
&gt;<br class=3D"">
&gt; First, being this late in the process, I think it would be fair to =
explain<br class=3D"">
&gt; (I would have expected the chairs to request the same) what the =
problem<br class=3D"">
&gt; is. We HAVE added the note saying that the draft does NOT make =
existing<br class=3D"">
&gt; 4572 implementations non-compliant. What else is missing?<br =
class=3D"">
&gt;<br class=3D"">
&gt; Second, IMO the draft says a little more than =C2=B3multiple =
fingerprints are<br class=3D"">
&gt; allowed=C2=B2. It also specifies HOW multiple fingerprints are =
used, HOW they<br class=3D"">
&gt; must be matched etc - using RFC 2119 terminology (there is a number =
of<br class=3D"">
&gt; MUSTs). Do we consider that =C2=B3advice=C2=B2? Or, do you want to =
REMOVE that?<br class=3D"">
&gt;<br class=3D"">
&gt; Last, if we don=C2=B9t indicate the draft as a =C2=B34572 update=C2=B2=
, people will not<br class=3D"">
&gt; automatically be made aware of it when looking for 4572, as it will =
not be<br class=3D"">
&gt; listed as an 4572 update. Is that a good thing?<br class=3D"">
&gt;<br class=3D"">
&gt; Regards,<br class=3D"">
&gt;<br class=3D"">
&gt; Christer<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt; On 07/10/16 00:39, "mmusic on behalf of Cullen Jennings"<br =
class=3D"">
&gt; &lt;<a href=3D"mailto:mmusic-bounces@ietf.org" =
class=3D"">mmusic-bounces@ietf.org</a> on behalf of
<a href=3D"mailto:fluffy@iii.ca" class=3D"">fluffy@iii.ca</a>&gt; =
wrote:<br class=3D"">
&gt;<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; It would be easy to rewrite it to not change it but simply =
clarify that<br class=3D"">
&gt;&gt; multiple fingerprints are allowed and provide advice about =
additional<br class=3D"">
&gt;&gt; ones to provide.<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt;&gt; On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)<br =
class=3D"">
&gt;&gt;&gt; &lt;<a href=3D"mailto:fluffy@cisco.com" =
class=3D"">fluffy@cisco.com</a>&gt; wrote:<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt; So I still disagree that this should update 4572 and the =
text for the<br class=3D"">
&gt;&gt;&gt; interoperability issue if significantly different than what =
many people<br class=3D"">
&gt;&gt;&gt; proposed on list. Can we arrange a phone call to discuss =
this.<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; On Sep 25, 2016, at 7:53 AM, <a =
href=3D"mailto:internet-drafts@ietf.org" class=3D"">
internet-drafts@ietf.org</a> wrote:<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; A New Internet-Draft is available from the on-line =
Internet-Drafts<br class=3D"">
&gt;&gt;&gt;&gt; directories.<br class=3D"">
&gt;&gt;&gt;&gt; This draft is a work item of the Multiparty Multimedia =
Session Control<br class=3D"">
&gt;&gt;&gt;&gt; of the IETF.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; Title&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;: SDP Fingerprint Attribute Usage Clarifications<br =
class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; Author&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; : Christer Holmberg<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; Filename&nbsp; &nbsp; &nbsp; &nbsp; : =
draft-ietf-mmusic-4572-update-<wbr class=3D"">07.txt<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; Pages&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;: 8<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; Date&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; : 2016-09-25<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Abstract:<br class=3D"">
&gt;&gt;&gt;&gt; This document updates RFC 4572 by clarifying the usage =
of multiple<br class=3D"">
&gt;&gt;&gt;&gt; SDP 'fingerprint' attributes with a single SDP media =
description ("m=3D<br class=3D"">
&gt;&gt;&gt;&gt; line").&nbsp; The document also updates the preferred =
cipher suite with a<br class=3D"">
&gt;&gt;&gt;&gt; stronger cipher suite.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; The IETF datatracker status page for this draft is:<br =
class=3D"">
&gt;&gt;&gt;&gt; <a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/" =
rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://datatracker.ietf.org/<wbr =
class=3D"">doc/draft-ietf-mmusic-4572-<wbr class=3D"">update/</a><br =
class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; There's also a htmlized version available at:<br =
class=3D"">
&gt;&gt;&gt;&gt; <a =
href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07" =
rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://tools.ietf.org/html/<wbr =
class=3D"">draft-ietf-mmusic-4572-update-<wbr class=3D"">07</a><br =
class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; A diff from the previous version is available at:<br =
class=3D"">
&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-4572-update-=
07" rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://www.ietf.org/rfcdiff?<wbr =
class=3D"">url2=3Ddraft-ietf-mmusic-4572-<wbr class=3D"">update-07</a><br =
class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Please note that it may take a couple of minutes from =
the time of<br class=3D"">
&gt;&gt;&gt;&gt; submission<br class=3D"">
&gt;&gt;&gt;&gt; until the htmlized version and diff are available at <a =
href=3D"http://tools.ietf.org/" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">
tools.ietf.org</a>.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Internet-Drafts are also available by anonymous FTP =
at:<br class=3D"">
&gt;&gt;&gt;&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" =
rel=3D"noreferrer" target=3D"_blank" class=3D"">
ftp://ftp.ietf.org/internet-<wbr class=3D"">drafts/</a><br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; ______________________________<wbr =
class=3D"">_________________<br class=3D"">
&gt;&gt;&gt;&gt; I-D-Announce mailing list<br class=3D"">
&gt;&gt;&gt;&gt; <a href=3D"mailto:I-D-Announce@ietf.org" =
class=3D"">I-D-Announce@ietf.org</a><br class=3D"">
&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce" =
rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://www.ietf.org/mailman/<wbr class=3D"">listinfo/i-d-announce</a><br =
class=3D"">
&gt;&gt;&gt;&gt; Internet-Draft directories: <a =
href=3D"http://www.ietf.org/shadow.html" rel=3D"noreferrer" =
target=3D"_blank" class=3D"">
http://www.ietf.org/shadow.<wbr class=3D"">html</a><br class=3D"">
&gt;&gt;&gt;&gt; or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" =
rel=3D"noreferrer" target=3D"_blank" class=3D"">
ftp://ftp.ietf.org/ietf/<wbr class=3D"">1shadow-sites.txt</a><br =
class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt; ______________________________<wbr =
class=3D"">_________________<br class=3D"">
&gt;&gt;&gt; mmusic mailing list<br class=3D"">
&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" =
class=3D"">mmusic@ietf.org</a><br class=3D"">
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://www.ietf.org/mailman/<wbr class=3D"">listinfo/mmusic</a><br =
class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; ______________________________<wbr =
class=3D"">_________________<br class=3D"">
&gt;&gt; mmusic mailing list<br class=3D"">
&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" =
class=3D"">mmusic@ietf.org</a><br class=3D"">
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://www.ietf.org/mailman/<wbr class=3D"">listinfo/mmusic</a><br =
class=3D"">
&gt;<br class=3D"">
&gt; ______________________________<wbr class=3D"">_________________<br =
class=3D"">
&gt; mmusic mailing list<br class=3D"">
&gt; <a href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a><br =
class=3D"">
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://www.ietf.org/mailman/<wbr class=3D"">listinfo/mmusic</a><br =
class=3D"">
<br class=3D"">
______________________________<wbr class=3D"">_________________<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"">
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/<wbr =
class=3D"">listinfo/mmusic</a><br class=3D"">
</blockquote>
</div>
<br class=3D"">
</div>
</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"">
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
class=3D"">https://www.ietf.org/mailman/listinfo/mmusic</a><br class=3D"">=

</div>
</blockquote>
</div>
<br class=3D"">
</div>
</div>
</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=_72CC25CC-1C56-4F8A-8937-C80869BE57FF--


From nobody Sat Oct  8 11:52:44 2016
Return-Path: <fluffy@iii.ca>
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 E4BFB1295FB for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 11:52:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 diW_KA5IIKf4 for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 11:52:42 -0700 (PDT)
Received: from smtp90.ord1c.emailsrvr.com (smtp90.ord1c.emailsrvr.com [108.166.43.90]) (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 B274D1295F8 for <mmusic@ietf.org>; Sat,  8 Oct 2016 11:52:42 -0700 (PDT)
Received: from smtp4.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 2070AA0196; Sat,  8 Oct 2016 14:52:40 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id D12CDA0193;  Sat,  8 Oct 2016 14:52:39 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.24.57.2] ([UNAVAILABLE]. [128.107.241.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.7); Sat, 08 Oct 2016 14:52:40 -0400
From: Cullen Jennings <fluffy@iii.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Sat, 8 Oct 2016 11:52:38 -0700
Message-Id: <B8CCCE95-5080-4B97-9043-3EEE8AAA8ECA@iii.ca>
To: mmusic <mmusic@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/i7n2aBIO0G0xTvwUNERz5RrILGg>
Cc: Suhas Nandakumar <snandaku@cisco.com>
Subject: [MMUSIC] rtcp-mux in SDP mux
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 18:52:44 -0000

Question came up if this morning if rtcp-mux should be TRANSPORT instead =
of IDENTICAL. Anyone remember why it is not TRANSPORT.=20



From nobody Sat Oct  8 12:02:03 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83FBD1295CF for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 12:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 V6_euvH2UM0q for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 12:01:59 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E3C7129493 for <mmusic@ietf.org>; Sat,  8 Oct 2016 12:01:59 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id t192so30259675ywf.0 for <mmusic@ietf.org>; Sat, 08 Oct 2016 12:01:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6ycd6rIqkcyYrMldD47Opk/tlIU2NQv5uRnW62pQbf4=; b=YdeVXaOlTwBuszs4RnkayHxGdjt/+ii8y0p6aXtZpZuE7613gDrCkYczpJrOlSowBO 5dCciOj4FksNYN0CfmaMUgf4fqOMRbtjDw9GkH+U9l97WK9zelfowQWYbovpw5n760cD akoWrCvVGsIZiSoUlYWTeWeuBXigCsxXzAMmAAhDH3Oe5ekzx1RTcMZniToLegLmz4Kk 3dwdUy7zOOx1EHhWfgZ2/L/neftwsOrGfJglje/g01f3pu0Ara9qIfesOJNHLZ3QTuGE u8A4FZU/+aNEgQSFtfF5TP02js+7usiwQjU7VKM359AabSsSDthPokCJHjT5KHFl4gRI 5UHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6ycd6rIqkcyYrMldD47Opk/tlIU2NQv5uRnW62pQbf4=; b=i/Hl0Fn0kF+k6y6THxeIsUb0n3okTDslUc1UjV398pLGuA06U/c5E5BsAJ3KbKxDMj RYFTWMnxCMTVm3ZILUdDDbCtrGaXDTGPxuB/fEiR4z//NaSqgbN5PROdjMJ8FUQ+h2Ji 1vgfWAGcbmlc6A5wVHnJfgvV96Ghk7PWjUFCLe+rBSr0X8J5u+ac3oOnTOaWnPnKupLD IR6owcwPdqVWxBEDratDBYfihi068/rc7DK1bCPSmng/Wa4GsiUoOWQFyONzbvalUaJy TLqB/+k39bxU6Sr7a5p7TnQ2vKzYXpB8FDqu+agxEffcaDscYvo99SZauRznGw+Vv19x rE/g==
X-Gm-Message-State: AA6/9RnjgiyXICkLSB+0PpykQ9WueNZPM8BR2Yx++xSSntCxgz5m2p90T1N8NPzagq+UQVoY+h8yK1kxwTdE+A==
X-Received: by 10.129.78.15 with SMTP id c15mr21057645ywb.107.1475953318879; Sat, 08 Oct 2016 12:01:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.158.73 with HTTP; Sat, 8 Oct 2016 12:01:58 -0700 (PDT)
In-Reply-To: <B8CCCE95-5080-4B97-9043-3EEE8AAA8ECA@iii.ca>
References: <B8CCCE95-5080-4B97-9043-3EEE8AAA8ECA@iii.ca>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Sat, 8 Oct 2016 12:01:58 -0700
Message-ID: <CAMRcRGSwhxpUvjx1id-a-wRwTKYwJ3VKbDKQQ36RjPMgOgBuHw@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: multipart/alternative; boundary=001a114dae5246e7e5053e5f2963
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/bVuNhO7G5iK66wom-e75LUKQRbk>
Cc: mmusic <mmusic@ietf.org>, Suhas Nandakumar <snandaku@cisco.com>
Subject: Re: [MMUSIC] rtcp-mux in SDP mux
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 19:02:01 -0000

--001a114dae5246e7e5053e5f2963
Content-Type: text/plain; charset=UTF-8

Hello Cullen

   The reasoning for IDENTICAL category for a=rtcp-mux was to handle the
case of  Initial Offers ( pre bundle address selection) so as to enable the
Offerer to multiplex RTP/RTCP even in the case of BUNDLE semantics being
rejected in the Answer.

So,  In the initial Offer, if the Offerer wants to multiplex RTP/RTCP it
needs to include it in all the m=lines (as defined by the IDENTICAL
category). This is because, if the BUNDLE semantics gets rejected the
offerer can still do  RTP/RTCP multiplexing on those m=lines.
OTOH, if a=rtcp-mux was included only in the m=line whose mid was listed as
the first in the a=group:BUNDLE line (TRANSPORT) and the BUNDLE semantics
gets rejected, there is no way for the Software to imply RTCP Mux or not to.

However once BUNDLE gets accepted and shared address is chosen, the
eventual Offers/Answers can have IDENTICAL category attributes included in
just the bundled m=line than repeatng ( as defined in Section 8.1 of the
BUNDLE spec)

Hope this answers the question

Cheers
Suhas







On Sat, Oct 8, 2016 at 11:52 AM, Cullen Jennings <fluffy@iii.ca> wrote:

>
> Question came up if this morning if rtcp-mux should be TRANSPORT instead
> of IDENTICAL. Anyone remember why it is not TRANSPORT.
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--001a114dae5246e7e5053e5f2963
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><font color=3D"#134f5c">Hello Cullen</font><div><font colo=
r=3D"#134f5c"><br></font></div><div><font color=3D"#134f5c">=C2=A0 =C2=A0Th=
e reasoning for IDENTICAL category for a=3Drtcp-mux was to handle the case =
of =C2=A0Initial Offers ( pre bundle address selection) so as to enable the=
 Offerer to multiplex RTP/RTCP even in the case of BUNDLE semantics being r=
ejected in the Answer.</font></div><div><font color=3D"#134f5c"><br></font>=
</div><div><font color=3D"#134f5c"><span style=3D"font-size:12.8px">So, =C2=
=A0In the initial Offer, if the Offerer wants to multiplex RTP/RTCP it need=
s to include it in all the m=3Dlines (as defined by the IDENTICAL category)=
. This is because, if the BUNDLE semantics gets rejected the offerer can st=
ill do =C2=A0RTP/RTCP=C2=A0multiplexing on those m=3Dlines.=C2=A0</span><br=
></font></div><div style=3D"font-size:12.8px"><font color=3D"#134f5c">OTOH,=
 if a=3Drtcp-mux was included only in the m=3Dline whose mid was listed as =
the first in the a=3Dgroup:BUNDLE line (TRANSPORT) and the BUNDLE semantics=
 gets rejected, there is no way for the Software to imply RTCP Mux or not t=
o.</font></div><div style=3D"font-size:12.8px"><font color=3D"#134f5c"><br>=
</font></div><div style=3D"font-size:12.8px"><font color=3D"#134f5c">Howeve=
r once BUNDLE gets accepted and shared address is chosen, the eventual Offe=
rs/Answers can have IDENTICAL category attributes included in just the bund=
led m=3Dline than repeatng ( as defined in Section 8.1 of the BUNDLE spec)<=
/font></div><div style=3D"font-size:12.8px"><font color=3D"#134f5c"><br></f=
ont></div><div style=3D"font-size:12.8px"><font color=3D"#134f5c">Hope this=
 answers the question</font></div><div style=3D"font-size:12.8px"><font col=
or=3D"#134f5c"><br></font></div><div style=3D"font-size:12.8px"><font color=
=3D"#134f5c">Cheers</font></div><div style=3D"font-size:12.8px"><font color=
=3D"#134f5c">Suhas</font></div><div style=3D"font-size:12.8px"><font color=
=3D"#cc0000"><br></font></div><div style=3D"font-size:12.8px"><font color=
=3D"#cc0000"><br></font></div><div style=3D"font-size:12.8px"><font color=
=3D"#cc0000"><br></font></div><div style=3D"font-size:12.8px"><font color=
=3D"#cc0000"><br></font></div><div><br></div><div>=C2=A0=C2=A0</div><div cl=
ass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sat, Oct 8, 2016 at 1=
1:52 AM, Cullen Jennings <span dir=3D"ltr">&lt;<a href=3D"mailto:fluffy@iii=
.ca" target=3D"_blank">fluffy@iii.ca</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><br>
Question came up if this morning if rtcp-mux should be TRANSPORT instead of=
 IDENTICAL. Anyone remember why it is not TRANSPORT.<br>
<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
</blockquote></div><br></div></div>

--001a114dae5246e7e5053e5f2963--


From nobody Sat Oct  8 12:31:19 2016
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 430C51293E1 for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 12:31:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ucw3awj-4nBN for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 12:31:15 -0700 (PDT)
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 AC59B126B6D for <mmusic@ietf.org>; Sat,  8 Oct 2016 12:31:14 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-fa-57f949809ac9
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by  (Symantec Mail Security) with SMTP id 3B.3A.02551.08949F75; Sat,  8 Oct 2016 21:31:12 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0319.002; Sat, 8 Oct 2016 21:30:48 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Cullen Jennings <fluffy@iii.ca>
Thread-Topic: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
Thread-Index: AQHSG0GgBWsMgAttg0WZUBo1tL92NKCb3CYAgAD/+ICAALTUgIAABa6AgAEhfoCAADZLPP//4cOAgAAuQP4=
Date: Sat, 8 Oct 2016 19:30:47 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD39A68@ESESSMB209.ericsson.se>
References: <147481162395.28315.18346373858565370012.idtracker@ietfa.amsl.com> <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com> <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca> <D41D4800.10A3F%christer.holmberg@ericsson.com> <68971202-4458-407D-A4AF-BCDCE54F2F78@iii.ca> <CAD5OKxvgTAw2ptSupXuEvTS8k=5Pncv0aYV=XRX81jTPjB5VSA@mail.gmail.com> <35A6A72A-5832-48D1-81D3-AF1AF31E34B5@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD3994A@ESESSMB209.ericsson.se>, <7FB846E7-8D25-43CA-B08C-EB73EEE635C9@iii.ca>
In-Reply-To: <7FB846E7-8D25-43CA-B08C-EB73EEE635C9@iii.ca>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BD39A68ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIIsWRmVeSWpSXmKPExsUyM2J7uG6D589wg6l35C0+rP/BaDF1+WMW ixkXpjI7MHssWfKTyePy+Y+MHremFAQwR3HZpKTmZJalFunbJXBlHJvQwV4w5RRjxZUbeg2M l9cxdjFyckgImEgcPbqLqYuRi0NIYD2jRF/TbVaQhJDAYkaJpuO6XYwcHGwCFhLd/7RBwiIC yhLndtxlBrGZBewlnj7vZgEpERZwk1j72BKixF1i9qx5bBB2ksTGq0vAVrEIqEhMm3sSLM4r 4Cvx48pPdoi1f5glWt/9ZAJJcApYSVyZswBsPqOAmMT3U2uYIHaJSzR9WckKcbOAxJI955kh bFGJl4//sULU5EtsX7qPHWKBoMTJmU9YJjAKz0LSPgtJ2SwkZRBxA4kv729D2doSyxa+Zoaw 9SW6359mQhZfwMi+ilG0OLW4ODfdyFgvtSgzubg4P08vL7VkEyMwog5u+a27g3H1a8dDjAIc jEo8vAsefQ8XYk0sK67MPcQowcGsJMI71e1nuBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXFes5X3 w4UE0hNLUrNTUwtSi2CyTBycUg2MuTOWMXdvNLhrxH5dP+jQ7mQWmdMxPJ5njRyYJgg+8v6w J0S14lKM4uOYD8KJxxpu1wp5Lf7bf+kkj0qor8mcG9LORbcfvTi32dVj/cHKzt9/FobyfJ3P emjTwcrjC65p6KzyYf4WnB31K7+UK6P84s9ep4vzWi/eqDQ4vVDgv3zP8ojmYgseJZbijERD Leai4kQAeZEtt6QCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/cgg1Pfv9XPJ1-u55il1TBMi2Sbw>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 19:31:18 -0000

--_000_7594FB04B1934943A5C02806D1A2204B4BD39A68ESESSMB209erics_
Content-Type: text/plain; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

Hi,

I think the clarification of multiple fingerprints is the most time critica=
l (it's also the reason we wrote the draft to begin with), so I'd prefer to=
 remove the cipher update and move the draft forward.

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Cullen Jennings<mailto:fluffy@iii.ca>
Sent: =FD08/=FD10/=FD2016 21:45
To: Christer Holmberg<mailto:christer.holmberg@ericsson.com>
Cc: Roman Shpount<mailto:roman@telurix.com>; mmusic<mailto:mmusic@ietf.org>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt

or split the change to clarify multiple fingerprints in a a draft that was =
and update and then published something along the lines of this draft that =
added the requirement for SHA 256. I'm not at all against requiring SHA 256=
 for WebRTC or other things, I'm against requiring that for things that do =
4572.

On Oct 8, 2016, at 11:33 AM, Christer Holmberg <christer.holmberg@ericsson.=
com<mailto:christer.holmberg@ericsson.com>> wrote:

Hi,

Would you be ok with the draft if we removed the cipher change?

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Cullen Jennings<mailto:fluffy@iii.ca>
Sent: =FD08/=FD10/=FD2016 20:19
To: Roman Shpount<mailto:roman@telurix.com>
Cc: mmusic<mailto:mmusic@ietf.org>; Christer Holmberg<mailto:christer.holmb=
erg@ericsson.com>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt


I am one of the people that believes they are allowed by 4572 because SDP e=
xplicitly allows multiple copies of a=3D extensions and this defines an a=
=3D extension. I believe SDP explicitly says that. However, I agree with yo=
ur point that is not clear. As I have said in the past, I am fine with an u=
pdate that clarifies this point.

I am not fine with an update that changes what ciphers are needed. I am fin=
e with an extention, not update, that mandates the SHA 256 and people that =
want to implement that can but people that do not can still do 4572.


On Oct 7, 2016, at 5:03 PM, Roman Shpount <roman@telurix.com<mailto:roman@t=
elurix.com>> wrote:

Cullen,

Can you answer a fundamental question related to 4572: Does it allow multip=
le fingerprint attributes per one m- line or not? Can you point to the exac=
t language in the RFC which says that?

There are people (including the authors of RFC 4572) which gave contradicto=
ry answers to this question. Because of these contradictory answers, you ca=
n create two implementations which claim to be compatible with 4572 but inc=
ompatible with each other. For instance Firefox will fail to establish a co=
nnection if multiple fingerprints per m- line are provided. So, I would say=
, we definitely need a document update to resolve this ambiguity.

Regards,
_____________
Roman Shpount

On Fri, Oct 7, 2016 at 7:42 PM, Cullen Jennings <fluffy@iii.ca<mailto:fluff=
y@iii.ca>> wrote:

There are lots of people using 4572 and there is nothing wrong with it. Wha=
t is proposed in this draft is also fine and it if was RFCAAAA that is fine=
. But telling people doing 4572 that they have to do AAAA is not OK. You ma=
ke not think that is what update means but it is what I and many others thi=
nk update means. Given this disagreement on what update means, I don't want=
 to use update.

I'd be happy to write an alternative draft that does not need to be an upda=
te if that is the issue but I plan to get JSEP ready first.


> On Oct 7, 2016, at 2:49 AM, Christer Holmberg <christer.holmberg@ericsson=
.com<mailto:christer.holmberg@ericsson.com>> wrote:
>
> Hi,
>
> First, being this late in the process, I think it would be fair to explai=
n
> (I would have expected the chairs to request the same) what the problem
> is. We HAVE added the note saying that the draft does NOT make existing
> 4572 implementations non-compliant. What else is missing?
>
> Second, IMO the draft says a little more than =B3multiple fingerprints ar=
e
> allowed=B2. It also specifies HOW multiple fingerprints are used, HOW the=
y
> must be matched etc - using RFC 2119 terminology (there is a number of
> MUSTs). Do we consider that =B3advice=B2? Or, do you want to REMOVE that?
>
> Last, if we don=B9t indicate the draft as a =B34572 update=B2, people wil=
l not
> automatically be made aware of it when looking for 4572, as it will not b=
e
> listed as an 4572 update. Is that a good thing?
>
> Regards,
>
> Christer
>
>
>
>
>
> On 07/10/16 00:39, "mmusic on behalf of Cullen Jennings"
> <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org> on behalf of flu=
ffy@iii.ca<mailto:fluffy@iii.ca>> wrote:
>
>>
>> It would be easy to rewrite it to not change it but simply clarify that
>> multiple fingerprints are allowed and provide advice about additional
>> ones to provide.
>>
>>
>>> On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)
>>> <fluffy@cisco.com<mailto:fluffy@cisco.com>> wrote:
>>>
>>>
>>> So I still disagree that this should update 4572 and the text for the
>>> interoperability issue if significantly different than what many people
>>> proposed on list. Can we arrange a phone call to discuss this.
>>>
>>>
>>>
>>>> On Sep 25, 2016, at 7:53 AM, internet-drafts@ietf.org<mailto:internet-=
drafts@ietf.org> wrote:
>>>>
>>>>
>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>> directories.
>>>> This draft is a work item of the Multiparty Multimedia Session Control
>>>> of the IETF.
>>>>
>>>>      Title           : SDP Fingerprint Attribute Usage Clarifications
>>>>      Author          : Christer Holmberg
>>>>    Filename        : draft-ietf-mmusic-4572-update-07.txt
>>>>    Pages           : 8
>>>>    Date            : 2016-09-25
>>>>
>>>> Abstract:
>>>> This document updates RFC 4572 by clarifying the usage of multiple
>>>> SDP 'fingerprint' attributes with a single SDP media description ("m=
=3D
>>>> line").  The document also updates the preferred cipher suite with a
>>>> stronger cipher suite.
>>>>
>>>>
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/
>>>>
>>>> There's also a htmlized version available at:
>>>> https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-07
>>>>
>>>> A diff from the previous version is available at:
>>>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-4572-update-07
>>>>
>>>>
>>>> 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<ht=
tp://tools.ietf.org/>.
>>>>
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>> _______________________________________________
>>>> I-D-Announce mailing list
>>>> I-D-Announce@ietf.org<mailto:I-D-Announce@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org<mailto:mmusic@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org<mailto:mmusic@ietf.org>
>> https://www.ietf.org/mailman/listinfo/mmusic
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org<mailto:mmusic@ietf.org>
> https://www.ietf.org/mailman/listinfo/mmusic

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

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

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


--_000_7594FB04B1934943A5C02806D1A2204B4BD39A68ESESSMB209erics_
Content-Type: text/html; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
256">
</head>
<body class=3D"" style=3D"word-wrap:break-word">
<div>
<div style=3D"font-family:Calibri,sans-serif; font-size:11pt">Hi,<br>
<br>
I think the clarification of multiple fingerprints is the most time critica=
l (it's also the reason we wrote the draft to begin with), so I'd prefer to=
 remove the cipher update and move the draft forward.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">From:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:fluffy@iii.ca">Cullen Jennings</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Sent:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">=FD08=
/=FD10/=FD2016 21:45</span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">To:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">Christer Holmberg</a></span><b=
r>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Cc:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:roman@telurix.com">Roman Shpount</a>;
<a href=3D"mailto:mmusic@ietf.org">mmusic</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Subject:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">Re: [=
MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt</span><br>
<br>
</div>
<div>or split the change to clarify multiple fingerprints in a a draft that=
 was and update and then published something along the lines of this draft =
that added the requirement for SHA 256. I'm not at all against requiring SH=
A 256 for WebRTC or other things,
 I'm against requiring that for things that do 4572.&nbsp;
<div class=3D""><br class=3D"">
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On Oct 8, 2016, at 11:33 AM, Christer Holmberg &lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com" class=3D"">christer.holmberg@eri=
csson.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<div class=3D"" style=3D"word-wrap:break-word">
<div class=3D"">
<div class=3D"" style=3D"font-family:Calibri,sans-serif; font-size:11pt">Hi=
,<br class=3D"">
<br class=3D"">
Would you be ok with the draft if we removed the cipher change?<br class=3D=
"">
<br class=3D"">
Regards,<br class=3D"">
<br class=3D"">
Christer<br class=3D"">
<br class=3D"">
Sent from my Windows Phone</div>
</div>
<div dir=3D"ltr" class=3D"">
<hr class=3D"">
<span class=3D"" style=3D"font-family:Calibri,sans-serif; font-size:11pt; f=
ont-weight:bold">From:
</span><span class=3D"" style=3D"font-family:Calibri,sans-serif; font-size:=
11pt"><a href=3D"mailto:fluffy@iii.ca" class=3D"">Cullen Jennings</a></span=
><br class=3D"">
<span class=3D"" style=3D"font-family:Calibri,sans-serif; font-size:11pt; f=
ont-weight:bold">Sent:
</span><span class=3D"" style=3D"font-family:Calibri,sans-serif; font-size:=
11pt">=FD08/=FD10/=FD2016 20:19</span><br class=3D"">
<span class=3D"" style=3D"font-family:Calibri,sans-serif; font-size:11pt; f=
ont-weight:bold">To:
</span><span class=3D"" style=3D"font-family:Calibri,sans-serif; font-size:=
11pt"><a href=3D"mailto:roman@telurix.com" class=3D"">Roman Shpount</a></sp=
an><br class=3D"">
<span class=3D"" style=3D"font-family:Calibri,sans-serif; font-size:11pt; f=
ont-weight:bold">Cc:
</span><span class=3D"" style=3D"font-family:Calibri,sans-serif; font-size:=
11pt"><a href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic</a>;
<a href=3D"mailto:christer.holmberg@ericsson.com" class=3D"">Christer Holmb=
erg</a></span><br class=3D"">
<span class=3D"" style=3D"font-family:Calibri,sans-serif; font-size:11pt; f=
ont-weight:bold">Subject:
</span><span class=3D"" style=3D"font-family:Calibri,sans-serif; font-size:=
11pt">Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt</span><=
br class=3D"">
<br class=3D"">
</div>
<div class=3D"">
<div class=3D""><br class=3D"">
</div>
I am one of the people that believes they are allowed by 4572 because SDP e=
xplicitly allows multiple copies of a=3D extensions and this defines an a=
=3D extension. I believe SDP explicitly says that. However, I agree with yo=
ur point that is not clear. As I have
 said in the past, I am fine with an update that clarifies this point.
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I am not fine with an update that changes what ciphers are =
needed. I am fine with an extention, not update, that mandates the SHA 256 =
and people that want to implement that can but people that do not can still=
 do 4572.&nbsp;</div>
<div class=3D""><br class=3D"">
<div class=3D""><br class=3D"">
<div class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On Oct 7, 2016, at 5:03 PM, Roman Shpount &lt;<a href=3D"ma=
ilto: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"">Cullen,
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Can you answer a fundamental question related to 4572: Does=
 it allow multiple fingerprint attributes per one m- line or not? Can you p=
oint to the exact language in the RFC which says that?</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">There are people (including the authors of RFC 4572) which =
gave contradictory answers to this question. Because of these contradictory=
 answers, you can create two implementations which claim to be compatible w=
ith 4572 but incompatible with each
 other. For instance Firefox will fail to establish a connection if multipl=
e fingerprints per m- line are provided. So, I would say, we definitely nee=
d a document update to resolve this ambiguity.
<div class=3D"gmail_extra"><br class=3D"">
</div>
<div class=3D"gmail_extra">Regards,<br clear=3D"all" class=3D"">
<div class=3D"">
<div class=3D"gmail_signature">_____________<br class=3D"">
Roman Shpount</div>
</div>
<br class=3D"">
<div class=3D"gmail_quote">On Fri, Oct 7, 2016 at 7:42 PM, Cullen Jennings =
<span dir=3D"ltr" class=3D"">
&lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank" class=3D"">fluffy@ii=
i.ca</a>&gt;</span> wrote:<br class=3D"">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<br class=3D"">
There are lots of people using 4572 and there is nothing wrong with it. Wha=
t is proposed in this draft is also fine and it if was RFCAAAA that is fine=
. But telling people doing 4572 that they have to do AAAA is not OK. You ma=
ke not think that is what update
 means but it is what I and many others think update means. Given this disa=
greement on what update means, I don't want to use update.<br class=3D"">
<br class=3D"">
I'd be happy to write an alternative draft that does not need to be an upda=
te if that is the issue but I plan to get JSEP ready first.<br class=3D"">
<br class=3D"">
<br class=3D"">
&gt; On Oct 7, 2016, at 2:49 AM, Christer Holmberg &lt;<a href=3D"mailto:ch=
rister.holmberg@ericsson.com" class=3D"">christer.holmberg@ericsson.<wbr cl=
ass=3D"">com</a>&gt; wrote:<br class=3D"">
&gt;<br class=3D"">
&gt; Hi,<br class=3D"">
&gt;<br class=3D"">
&gt; First, being this late in the process, I think it would be fair to exp=
lain<br class=3D"">
&gt; (I would have expected the chairs to request the same) what the proble=
m<br class=3D"">
&gt; is. We HAVE added the note saying that the draft does NOT make existin=
g<br class=3D"">
&gt; 4572 implementations non-compliant. What else is missing?<br class=3D"=
">
&gt;<br class=3D"">
&gt; Second, IMO the draft says a little more than =B3multiple fingerprints=
 are<br class=3D"">
&gt; allowed=B2. It also specifies HOW multiple fingerprints are used, HOW =
they<br class=3D"">
&gt; must be matched etc - using RFC 2119 terminology (there is a number of=
<br class=3D"">
&gt; MUSTs). Do we consider that =B3advice=B2? Or, do you want to REMOVE th=
at?<br class=3D"">
&gt;<br class=3D"">
&gt; Last, if we don=B9t indicate the draft as a =B34572 update=B2, people =
will not<br class=3D"">
&gt; automatically be made aware of it when looking for 4572, as it will no=
t be<br class=3D"">
&gt; listed as an 4572 update. Is that a good thing?<br class=3D"">
&gt;<br class=3D"">
&gt; Regards,<br class=3D"">
&gt;<br class=3D"">
&gt; Christer<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt; On 07/10/16 00:39, &quot;mmusic on behalf of Cullen Jennings&quot;<br =
class=3D"">
&gt; &lt;<a href=3D"mailto:mmusic-bounces@ietf.org" class=3D"">mmusic-bounc=
es@ietf.org</a> on behalf of
<a href=3D"mailto:fluffy@iii.ca" class=3D"">fluffy@iii.ca</a>&gt; wrote:<br=
 class=3D"">
&gt;<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; It would be easy to rewrite it to not change it but simply clarify=
 that<br class=3D"">
&gt;&gt; multiple fingerprints are allowed and provide advice about additio=
nal<br class=3D"">
&gt;&gt; ones to provide.<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt;&gt; On Sep 30, 2016, at 11:39 AM, Cullen Jennings (fluffy)<br clas=
s=3D"">
&gt;&gt;&gt; &lt;<a href=3D"mailto:fluffy@cisco.com" class=3D"">fluffy@cisc=
o.com</a>&gt; wrote:<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt; So I still disagree that this should update 4572 and the text =
for the<br class=3D"">
&gt;&gt;&gt; interoperability issue if significantly different than what ma=
ny people<br class=3D"">
&gt;&gt;&gt; proposed on list. Can we arrange a phone call to discuss this.=
<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; On Sep 25, 2016, at 7:53 AM, <a href=3D"mailto:internet-dr=
afts@ietf.org" class=3D"">
internet-drafts@ietf.org</a> wrote:<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; A New Internet-Draft is available from the on-line Interne=
t-Drafts<br class=3D"">
&gt;&gt;&gt;&gt; directories.<br class=3D"">
&gt;&gt;&gt;&gt; This draft is a work item of the Multiparty Multimedia Ses=
sion Control<br class=3D"">
&gt;&gt;&gt;&gt; of the IETF.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; Title&nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp;: SDP Fingerprint Attribute Usage Clarifications<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; Author&nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; : Christer Holmberg<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; Filename&nbsp; &nbsp; &nbsp; &nbsp; : draft-i=
etf-mmusic-4572-update-<wbr class=3D"">07.txt<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; Pages&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;: 8<br class=3D"">
&gt;&gt;&gt;&gt;&nbsp; &nbsp; Date&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 : 2016-09-25<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Abstract:<br class=3D"">
&gt;&gt;&gt;&gt; This document updates RFC 4572 by clarifying the usage of =
multiple<br class=3D"">
&gt;&gt;&gt;&gt; SDP 'fingerprint' attributes with a single SDP media descr=
iption (&quot;m=3D<br class=3D"">
&gt;&gt;&gt;&gt; line&quot;).&nbsp; The document also updates the preferred=
 cipher suite with a<br class=3D"">
&gt;&gt;&gt;&gt; stronger cipher suite.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; The IETF datatracker status page for this draft is:<br cla=
ss=3D"">
&gt;&gt;&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmu=
sic-4572-update/" rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://datatracker.ietf.org/<wbr class=3D"">doc/draft-ietf-mmusic-4572-<wb=
r class=3D"">update/</a><br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; There's also a htmlized version available at:<br class=3D"=
">
&gt;&gt;&gt;&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-4=
572-update-07" rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://tools.ietf.org/html/<wbr class=3D"">draft-ietf-mmusic-4572-update-<=
wbr class=3D"">07</a><br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; A diff from the previous version is available at:<br class=
=3D"">
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-=
mmusic-4572-update-07" rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://www.ietf.org/rfcdiff?<wbr class=3D"">url2=3Ddraft-ietf-mmusic-4572-=
<wbr class=3D"">update-07</a><br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Please note that it may take a couple of minutes from the =
time of<br class=3D"">
&gt;&gt;&gt;&gt; submission<br class=3D"">
&gt;&gt;&gt;&gt; until the htmlized version and diff are available at <a hr=
ef=3D"http://tools.ietf.org/" rel=3D"noreferrer" target=3D"_blank" class=3D=
"">
tools.ietf.org</a>.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Internet-Drafts are also available by anonymous FTP at:<br=
 class=3D"">
&gt;&gt;&gt;&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"nor=
eferrer" target=3D"_blank" class=3D"">
ftp://ftp.ietf.org/internet-<wbr class=3D"">drafts/</a><br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; ______________________________<wbr class=3D"">____________=
_____<br class=3D"">
&gt;&gt;&gt;&gt; I-D-Announce mailing list<br class=3D"">
&gt;&gt;&gt;&gt; <a href=3D"mailto:I-D-Announce@ietf.org" class=3D"">I-D-An=
nounce@ietf.org</a><br class=3D"">
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/i-d-annou=
nce" rel=3D"noreferrer" target=3D"_blank" class=3D"">
https://www.ietf.org/mailman/<wbr class=3D"">listinfo/i-d-announce</a><br c=
lass=3D"">
&gt;&gt;&gt;&gt; Internet-Draft directories: <a href=3D"http://www.ietf.org=
/shadow.html" rel=3D"noreferrer" target=3D"_blank" class=3D"">
http://www.ietf.org/shadow.<wbr class=3D"">html</a><br class=3D"">
&gt;&gt;&gt;&gt; or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" r=
el=3D"noreferrer" target=3D"_blank" class=3D"">
ftp://ftp.ietf.org/ietf/<wbr class=3D"">1shadow-sites.txt</a><br class=3D""=
>
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt; ______________________________<wbr class=3D"">________________=
_<br class=3D"">
&gt;&gt;&gt; mmusic mailing list<br class=3D"">
&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org<=
/a><br class=3D"">
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=
=3D"noreferrer" target=3D"_blank" class=3D"">
https://www.ietf.org/mailman/<wbr class=3D"">listinfo/mmusic</a><br class=
=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; ______________________________<wbr class=3D"">_________________<br=
 class=3D"">
&gt;&gt; mmusic mailing list<br class=3D"">
&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a><=
br class=3D"">
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"no=
referrer" target=3D"_blank" class=3D"">
https://www.ietf.org/mailman/<wbr class=3D"">listinfo/mmusic</a><br class=
=3D"">
&gt;<br class=3D"">
&gt; ______________________________<wbr class=3D"">_________________<br cla=
ss=3D"">
&gt; mmusic mailing list<br class=3D"">
&gt; <a href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a><br c=
lass=3D"">
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"norefe=
rrer" target=3D"_blank" class=3D"">
https://www.ietf.org/mailman/<wbr class=3D"">listinfo/mmusic</a><br class=
=3D"">
<br class=3D"">
______________________________<wbr class=3D"">_________________<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"">
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank" class=3D"">https://www.ietf.org/mailman/<wbr class=3D"">=
listinfo/mmusic</a><br class=3D"">
</blockquote>
</div>
<br class=3D"">
</div>
</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"">
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" class=3D"">https:/=
/www.ietf.org/mailman/listinfo/mmusic</a><br class=3D"">
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</div>
</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>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B4BD39A68ESESSMB209erics_--


From nobody Sat Oct  8 12:57:08 2016
Return-Path: <deadbeef@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 C4C0B127735 for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 12:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.696
X-Spam-Level: 
X-Spam-Status: No, score=-5.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_PASS=-0.001] 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 KtWGevxY6QFp for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 12:57:04 -0700 (PDT)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 A1DF0120726 for <mmusic@ietf.org>; Sat,  8 Oct 2016 12:57:04 -0700 (PDT)
Received: by mail-qk0-x22b.google.com with SMTP id n189so69560363qke.0 for <mmusic@ietf.org>; Sat, 08 Oct 2016 12:57:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IdhPWnuDSqch/y8DyJcwib6+LkahBL3ERA/JIwW3Q/g=; b=iRL63P+ky26me3M2aHeSiOD2elS0QMfnt8WhAL1ItqlAShZlwuT0WDmwFa7ShMFQpI AdPR2dyFrRDHZdc+ToZadIoNNQ9xcEysV2iOlObGvLaf0u5vexuT9I2HN1rMX/mguifT RNL8DUds/sem5gvbBxH/T7UfWyLNQa3Mf9/xTnUxSvh7jE7Qum5aa3MMRGtmRmNWC5L3 +mgjZtTV3TyPHpD1iI6bJbaHoP6K+osunkfMziJY+WYWJwZQmeltAljaDrGYMsA7B1se f8MCJMThySgcT3Ve85CGk6H4H+ZjgwVS+tBJC6Tn7T3ILZ0rQblegnscCXmkGxxmxjVa n1wQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IdhPWnuDSqch/y8DyJcwib6+LkahBL3ERA/JIwW3Q/g=; b=XWkc8X43KSmyUV2GcfaGZropb2k+FIyLFugAlYfVReVbo2S0+1vgHH1vAHa5yEZyrS 56Pu4XvOpc90DdyvOO4rYXP4VWo+39FPTJW92dlWkS8RemqPaWPLZnU1uiJylqTz2kBD lVV6J2Sfst1xYeWPZDGDTy61h+onk0oWBkcQ27wWAKumjhO+PMfIu6Us1+BBMZcko/lq KCdenaI7CgYgw2uJ939WdiCK4OcKKt23UDbhzmuA20/rxMQBC6JACuX3pM0VBsx6zwYy 7bo60bCyjJA/pdZphbQf9E0Lx60ToKDo5xL9GlAYwnx2QJ8C7utu+H1EWhbtdzGhyEcB fuxQ==
X-Gm-Message-State: AA6/9RnUw0OkGT/KZ1LIfgmBvbLn8e3aTtBxkLZzjJW8hQ+1ajz4Sbov7hq0obZeHNswkONbftrVcrFz18BN1n7Y
X-Received: by 10.233.232.71 with SMTP id a68mr26748424qkg.208.1475956623670;  Sat, 08 Oct 2016 12:57:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.49.33 with HTTP; Sat, 8 Oct 2016 12:57:02 -0700 (PDT)
In-Reply-To: <CAMRcRGSwhxpUvjx1id-a-wRwTKYwJ3VKbDKQQ36RjPMgOgBuHw@mail.gmail.com>
References: <B8CCCE95-5080-4B97-9043-3EEE8AAA8ECA@iii.ca> <CAMRcRGSwhxpUvjx1id-a-wRwTKYwJ3VKbDKQQ36RjPMgOgBuHw@mail.gmail.com>
From: Taylor Brandstetter <deadbeef@google.com>
Date: Sat, 8 Oct 2016 12:57:02 -0700
Message-ID: <CAK35n0bOzKPVpD_wYyXvnG_dFE68KZ5RcNAPisx0eJLDM7cv2A@mail.gmail.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c041fb242713b053e5fee3f
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/7dS2eWDHye8crDwFHy7khpouGoA>
Cc: mmusic <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Suhas Nandakumar <snandaku@cisco.com>
Subject: Re: [MMUSIC] rtcp-mux in SDP mux
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 19:57:07 -0000

--94eb2c041fb242713b053e5fee3f
Content-Type: text/plain; charset=UTF-8

If the offerer wants to multiplex RTP/RTCP regardless of whether or not
bundling is enabled, it can do this even if rtcp-mux is in the TRANSPORT
category, correct? TRANSPORT doesn't seem to prevent putting the same
attribute in every media description.

So, what exactly does being in the IDENTICAL category protect against?
That's what I'm having a hard time understanding.

On Sat, Oct 8, 2016 at 12:01 PM, Suhas Nandakumar <suhasietf@gmail.com>
wrote:

> Hello Cullen
>
>    The reasoning for IDENTICAL category for a=rtcp-mux was to handle the
> case of  Initial Offers ( pre bundle address selection) so as to enable the
> Offerer to multiplex RTP/RTCP even in the case of BUNDLE semantics being
> rejected in the Answer.
>
> So,  In the initial Offer, if the Offerer wants to multiplex RTP/RTCP it
> needs to include it in all the m=lines (as defined by the IDENTICAL
> category). This is because, if the BUNDLE semantics gets rejected the
> offerer can still do  RTP/RTCP multiplexing on those m=lines.
> OTOH, if a=rtcp-mux was included only in the m=line whose mid was listed
> as the first in the a=group:BUNDLE line (TRANSPORT) and the BUNDLE
> semantics gets rejected, there is no way for the Software to imply RTCP Mux
> or not to.
>
> However once BUNDLE gets accepted and shared address is chosen, the
> eventual Offers/Answers can have IDENTICAL category attributes included in
> just the bundled m=line than repeatng ( as defined in Section 8.1 of the
> BUNDLE spec)
>
> Hope this answers the question
>
> Cheers
> Suhas
>
>
>
>
>
>
>
> On Sat, Oct 8, 2016 at 11:52 AM, Cullen Jennings <fluffy@iii.ca> wrote:
>
>>
>> Question came up if this morning if rtcp-mux should be TRANSPORT instead
>> of IDENTICAL. Anyone remember why it is not TRANSPORT.
>>
>>
>> _______________________________________________
>> 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
>
>

--94eb2c041fb242713b053e5fee3f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">If the offerer wants to multiplex RTP/RTCP regardless of w=
hether or not bundling is enabled, it can do this even if rtcp-mux is in th=
e TRANSPORT category, correct? TRANSPORT doesn&#39;t seem to prevent puttin=
g the same attribute in every media description.<div><br></div><div>So, wha=
t exactly does being in the IDENTICAL category protect against? That&#39;s =
what I&#39;m having a hard time understanding.</div></div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Sat, Oct 8, 2016 at 12:01 PM, S=
uhas Nandakumar <span dir=3D"ltr">&lt;<a href=3D"mailto:suhasietf@gmail.com=
" target=3D"_blank">suhasietf@gmail.com</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><div dir=3D"ltr"><font color=3D"#134f5c">Hello Cullen<=
/font><div><font color=3D"#134f5c"><br></font></div><div><font color=3D"#13=
4f5c">=C2=A0 =C2=A0The reasoning for IDENTICAL category for a=3Drtcp-mux wa=
s to handle the case of =C2=A0Initial Offers ( pre bundle address selection=
) so as to enable the Offerer to multiplex RTP/RTCP even in the case of BUN=
DLE semantics being rejected in the Answer.</font></div><div><font color=3D=
"#134f5c"><br></font></div><div><font color=3D"#134f5c"><span style=3D"font=
-size:12.8px">So, =C2=A0In the initial Offer, if the Offerer wants to multi=
plex RTP/RTCP it needs to include it in all the m=3Dlines (as defined by th=
e IDENTICAL category). This is because, if the BUNDLE semantics gets reject=
ed the offerer can still do =C2=A0RTP/RTCP=C2=A0multiplexing on those m=3Dl=
ines.=C2=A0</span><br></font></div><div style=3D"font-size:12.8px"><font co=
lor=3D"#134f5c">OTOH, if a=3Drtcp-mux was included only in the m=3Dline who=
se mid was listed as the first in the a=3Dgroup:BUNDLE line (TRANSPORT) and=
 the BUNDLE semantics gets rejected, there is no way for the Software to im=
ply RTCP Mux or not to.</font></div><div style=3D"font-size:12.8px"><font c=
olor=3D"#134f5c"><br></font></div><div style=3D"font-size:12.8px"><font col=
or=3D"#134f5c">However once BUNDLE gets accepted and shared address is chos=
en, the eventual Offers/Answers can have IDENTICAL category attributes incl=
uded in just the bundled m=3Dline than repeatng ( as defined in Section 8.1=
 of the BUNDLE spec)</font></div><div style=3D"font-size:12.8px"><font colo=
r=3D"#134f5c"><br></font></div><div style=3D"font-size:12.8px"><font color=
=3D"#134f5c">Hope this answers the question</font></div><div style=3D"font-=
size:12.8px"><font color=3D"#134f5c"><br></font></div><div style=3D"font-si=
ze:12.8px"><font color=3D"#134f5c">Cheers</font></div><span class=3D"HOEnZb=
"><font color=3D"#888888"><div style=3D"font-size:12.8px"><font color=3D"#1=
34f5c">Suhas</font></div></font></span><div><div class=3D"h5"><div style=3D=
"font-size:12.8px"><font color=3D"#cc0000"><br></font></div><div style=3D"f=
ont-size:12.8px"><font color=3D"#cc0000"><br></font></div><div style=3D"fon=
t-size:12.8px"><font color=3D"#cc0000"><br></font></div><div style=3D"font-=
size:12.8px"><font color=3D"#cc0000"><br></font></div><div><br></div><div>=
=C2=A0=C2=A0</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"=
>On Sat, Oct 8, 2016 at 11:52 AM, Cullen Jennings <span dir=3D"ltr">&lt;<a =
href=3D"mailto:fluffy@iii.ca" target=3D"_blank">fluffy@iii.ca</a>&gt;</span=
> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><br>
Question came up if this morning if rtcp-mux should be TRANSPORT instead of=
 IDENTICAL. Anyone remember why it is not TRANSPORT.<br>
<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote></div><br></div></div></div></div>
<br>______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
<br></blockquote></div><br></div>

--94eb2c041fb242713b053e5fee3f--


From nobody Sat Oct  8 13:20:32 2016
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 689341293D9 for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 13:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VSfGs5CxOwPv for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 13:20:29 -0700 (PDT)
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 51B17120726 for <mmusic@ietf.org>; Sat,  8 Oct 2016 13:20:29 -0700 (PDT)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-05v.sys.comcast.net with SMTP id sy6Ubxb4h2FGMsy6ebyc5l; Sat, 08 Oct 2016 20:20:28 +0000
Received: from [192.168.1.110] ([73.186.127.100]) by resomta-ch2-05v.sys.comcast.net with SMTP id sy6dbI1kV80BXsy6dbEvuy; Sat, 08 Oct 2016 20:20:28 +0000
To: Cullen Jennings <fluffy@iii.ca>
References: <147481162395.28315.18346373858565370012.idtracker@ietfa.amsl.com> <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com> <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca> <D41D4800.10A3F%christer.holmberg@ericsson.com> <68971202-4458-407D-A4AF-BCDCE54F2F78@iii.ca> <ba29c562-fe49-c1f1-d2ba-5bdf3621f9b6@alum.mit.edu> <BEA54B46-C68E-44DC-BA7F-16E2E80094A9@iii.ca>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <a0667b00-ac54-10ba-e9ec-3fe67a4e19f7@alum.mit.edu>
Date: Sat, 8 Oct 2016 16:20:27 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <BEA54B46-C68E-44DC-BA7F-16E2E80094A9@iii.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfPKRcH1cLeCzUFLSgi0C7cv6cPnULqN02EmF1BE7Tn80l53OYNgGO8sxQyapWIm3i/ix/FAfjo1q5hHBrGu4B0e0b/NWOgyh8OzKB366tzAUsuCCpXGa dlwF5OEfb0yxt1/ofifbQRJWkGL8Fl+SLc1e5pki51aVFyOfKNKklYNKH5AWfHHSOplqbEQeAsJ7dg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MLRkrHby1R1kBr6V_gN8b1qucmI>
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 20:20:30 -0000

On 10/8/16 2:42 PM, Cullen Jennings wrote:
>
>> On Oct 8, 2016, at 9:01 AM, Paul Kyzivat <pkyzivat@alum.mit.edu
>> <mailto:pkyzivat@alum.mit.edu>> wrote:
>>
>>
>> I know you were following the wgchairs thread on '"Updates: RFC xxx" -
>> what does it actually mean ?' because you replied in that thread. If
>> you agree with the conclusion there th
>
> The conclusion of that thread - after it expanded beyond the chairs list
> - was AFAIC, that this was unclear and someone should write a RFC to
> clarify it. If you think there was consensus on what update means, then
> I strongly agree and invite you to go look at number of people that put
> out position on each side. Until a new RFC gets issues, I will use the
> meaning in the only published RFC that defined this even though it was
> deprecated by a later RFC that did not provide any definition one way or
> the other.

My understanding was that it is unclear and people were happy to leave 
it unclear. Instead of clarifying it, individual drafts are expected to 
add prominent text that explains what it means in the context of that draft.

I don't *like* that conclusion, but I don't consider it worthwhile to 
pursue it further.

> And to be clear, what I am proposing here is a simple way for this WG to
> move forward without having to resolve that debate or wait for consensus
> on what update means.

If splitting this into two drafts will satisfy you, then I'm ok with that.

But it also seems like it ought to be adequate to leave it one document, 
with Updates, and a clear statement of what Updates does and doesn't 
mean in this case.

	Thanks,
	Paul


From nobody Sat Oct  8 13:32:29 2016
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 838831293D8 for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 13:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 2YfJCI9ogSF0 for <mmusic@ietfa.amsl.com>; Sat,  8 Oct 2016 13:32:25 -0700 (PDT)
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 257FC129401 for <mmusic@ietf.org>; Sat,  8 Oct 2016 13:32:24 -0700 (PDT)
X-AuditID: c1b4fb25-15fff7000000793b-07-57f957d6de22
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by  (Symantec Mail Security) with SMTP id 96.16.31035.6D759F75; Sat,  8 Oct 2016 22:32:23 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0319.002; Sat, 8 Oct 2016 22:32:22 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Taylor Brandstetter <deadbeef@google.com>, Suhas Nandakumar <suhasietf@gmail.com>
Thread-Topic: [MMUSIC] rtcp-mux in SDP mux
Thread-Index: AQHSIZUqDPd/JqOcIEyoir+BQep+zaCeyDEAgAAPYwCAACtlag==
Date: Sat, 8 Oct 2016 20:32:21 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD39C7D@ESESSMB209.ericsson.se>
References: <B8CCCE95-5080-4B97-9043-3EEE8AAA8ECA@iii.ca> <CAMRcRGSwhxpUvjx1id-a-wRwTKYwJ3VKbDKQQ36RjPMgOgBuHw@mail.gmail.com>, <CAK35n0bOzKPVpD_wYyXvnG_dFE68KZ5RcNAPisx0eJLDM7cv2A@mail.gmail.com>
In-Reply-To: <CAK35n0bOzKPVpD_wYyXvnG_dFE68KZ5RcNAPisx0eJLDM7cv2A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BD39C7DESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMIsWRmVeSWpSXmKPExsUyM2K7qO718J/hBnsbuCwur3jIavFh/Q9G i6nLH7NYLD5wn9Vi59wOZgdWjym/N7J67Jx1l91jwaZSjyVLfjJ5XD7/kTGANYrLJiU1J7Ms tUjfLoErY+PqsoIDnhXv7m9mbGC8Zd/FyMkhIWAiMXNRO2MXIxeHkMB6RonmxussEM5iRonL R58BORwcbAIWEt3/tEFMEYFwiYlLgkB6mQUyJKZcO8AIYgsLaErcfLSUBcQWEdCSmLP8LzuE 7SRx8fQlNhCbRUBF4u30t4wgY3gFfCVWPpGB2HSUUeJl20dmkBpOgUCJN88egtmMAmIS30+t YYLYJS7R9GUlK8TNAhJL9pxnhrBFJV4+/scKUZMv8b9xFZjNKyAocXLmE5YJjMKzkLTPQlI2 C0kZRNxA4sv721C2tsSyha+ZIWx9ie73p5mQxRcwsq9iFC1OLU7KTTcy1kstykwuLs7P08tL LdnECIy6g1t+q+5gvPzG8RCjAAejEg/vgkffw4VYE8uKK3MPMUpwMCuJ8G4O+RkuxJuSWFmV WpQfX1Sak1p8iFGag0VJnNds5f1wIYH0xJLU7NTUgtQimCwTB6dUA+Mkrr/lu98GphRe4dV0 +v1E5JzEPOGYeKF5R9vVLKdmT9lvtyjRar01X3d3j/BHxgNWxo+eB//Y1/9p/TuOhGqHlGdy qc93OJ5/cs0+Um22iNcCH+bZ5wNbhN95v3/NnV9f1TRr9aTA89P6nLeYRAmy6X7KXDG3Leaf k/Hbd54LBDQ11d3+piqxFGckGmoxFxUnAgDLSXvvtgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Abbsgqj9puauLgYF8oAWCHPWESU>
Cc: mmusic <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Suhas Nandakumar <snandaku@cisco.com>
Subject: Re: [MMUSIC] rtcp-mux in SDP mux
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 20:32:27 -0000

--_000_7594FB04B1934943A5C02806D1A2204B4BD39C7DESESSMB209erics_
Content-Type: text/plain; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

Hi,

Note that when the initial offer is sent, it is yet not known which m- line=
 will become the BUNDLE m- line. For that reason a=3Drtcp-mux needs to be a=
ssociated with every m- line.

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Taylor Brandstetter<mailto:deadbeef@google.com>
Sent: =FD08/=FD10/=FD2016 22:57
To: Suhas Nandakumar<mailto:suhasietf@gmail.com>
Cc: mmusic<mailto:mmusic@ietf.org>; Cullen Jennings<mailto:fluffy@iii.ca>; =
Suhas Nandakumar<mailto:snandaku@cisco.com>
Subject: Re: [MMUSIC] rtcp-mux in SDP mux

If the offerer wants to multiplex RTP/RTCP regardless of whether or not bun=
dling is enabled, it can do this even if rtcp-mux is in the TRANSPORT categ=
ory, correct? TRANSPORT doesn't seem to prevent putting the same attribute =
in every media description.

So, what exactly does being in the IDENTICAL category protect against? That=
's what I'm having a hard time understanding.

On Sat, Oct 8, 2016 at 12:01 PM, Suhas Nandakumar <suhasietf@gmail.com<mail=
to:suhasietf@gmail.com>> wrote:
Hello Cullen

   The reasoning for IDENTICAL category for a=3Drtcp-mux was to handle the =
case of  Initial Offers ( pre bundle address selection) so as to enable the=
 Offerer to multiplex RTP/RTCP even in the case of BUNDLE semantics being r=
ejected in the Answer.

So,  In the initial Offer, if the Offerer wants to multiplex RTP/RTCP it ne=
eds to include it in all the m=3Dlines (as defined by the IDENTICAL categor=
y). This is because, if the BUNDLE semantics gets rejected the offerer can =
still do  RTP/RTCP multiplexing on those m=3Dlines.
OTOH, if a=3Drtcp-mux was included only in the m=3Dline whose mid was liste=
d as the first in the a=3Dgroup:BUNDLE line (TRANSPORT) and the BUNDLE sema=
ntics gets rejected, there is no way for the Software to imply RTCP Mux or =
not to.

However once BUNDLE gets accepted and shared address is chosen, the eventua=
l Offers/Answers can have IDENTICAL category attributes included in just th=
e bundled m=3Dline than repeatng ( as defined in Section 8.1 of the BUNDLE =
spec)

Hope this answers the question

Cheers
Suhas







On Sat, Oct 8, 2016 at 11:52 AM, Cullen Jennings <fluffy@iii.ca<mailto:fluf=
fy@iii.ca>> wrote:

Question came up if this morning if rtcp-mux should be TRANSPORT instead of=
 IDENTICAL. Anyone remember why it is not TRANSPORT.


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


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



--_000_7594FB04B1934943A5C02806D1A2204B4BD39C7DESESSMB209erics_
Content-Type: text/html; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
256">
</head>
<body>
<div>
<div style=3D"font-family:Calibri,sans-serif; font-size:11pt">Hi,<br>
<br>
Note that when the initial offer is sent, it is yet not known which m- line=
 will become the BUNDLE m- line. For that reason a=3Drtcp-mux needs to be a=
ssociated with every m- line.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">From:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:deadbeef@google.com">Taylor Brandstetter</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Sent:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">=FD08=
/=FD10/=FD2016 22:57</span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">To:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:suhasietf@gmail.com">Suhas Nandakumar</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Cc:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:mmusic@ietf.org">mmusic</a>;
<a href=3D"mailto:fluffy@iii.ca">Cullen Jennings</a>; <a href=3D"mailto:sna=
ndaku@cisco.com">
Suhas Nandakumar</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Subject:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">Re: [=
MMUSIC] rtcp-mux in SDP mux</span><br>
<br>
</div>
<div>
<div dir=3D"ltr">If the offerer wants to multiplex RTP/RTCP regardless of w=
hether or not bundling is enabled, it can do this even if rtcp-mux is in th=
e TRANSPORT category, correct? TRANSPORT doesn't seem to prevent putting th=
e same attribute in every media description.
<div><br>
</div>
<div>So, what exactly does being in the IDENTICAL category protect against?=
 That's what I'm having a hard time understanding.</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Sat, Oct 8, 2016 at 12:01 PM, Suhas Nandakuma=
r <span dir=3D"ltr">
&lt;<a href=3D"mailto:suhasietf@gmail.com" target=3D"_blank">suhasietf@gmai=
l.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<div dir=3D"ltr"><font color=3D"#134f5c">Hello Cullen</font>
<div><font color=3D"#134f5c"><br>
</font></div>
<div><font color=3D"#134f5c">&nbsp; &nbsp;The reasoning for IDENTICAL categ=
ory for a=3Drtcp-mux was to handle the case of &nbsp;Initial Offers ( pre b=
undle address selection) so as to enable the Offerer to multiplex RTP/RTCP =
even in the case of BUNDLE semantics being rejected
 in the Answer.</font></div>
<div><font color=3D"#134f5c"><br>
</font></div>
<div><font color=3D"#134f5c"><span style=3D"font-size:12.8px">So, &nbsp;In =
the initial Offer, if the Offerer wants to multiplex RTP/RTCP it needs to i=
nclude it in all the m=3Dlines (as defined by the IDENTICAL category). This=
 is because, if the BUNDLE semantics gets rejected
 the offerer can still do &nbsp;RTP/RTCP&nbsp;multiplexing on those m=3Dlin=
es.&nbsp;</span><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c">OTOH, if a=3Drtcp-m=
ux was included only in the m=3Dline whose mid was listed as the first in t=
he a=3Dgroup:BUNDLE line (TRANSPORT) and the BUNDLE semantics gets rejected=
, there is no way for the Software to imply
 RTCP Mux or not to.</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c"><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c">However once BUNDLE=
 gets accepted and shared address is chosen, the eventual Offers/Answers ca=
n have IDENTICAL category attributes included in just the bundled m=3Dline =
than repeatng ( as defined in Section
 8.1 of the BUNDLE spec)</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c"><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c">Hope this answers t=
he question</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c"><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c">Cheers</font></div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div style=3D"font-size:12.8px"><font color=3D"#134f5c">Suhas</font></div>
</font></span>
<div>
<div class=3D"h5">
<div style=3D"font-size:12.8px"><font color=3D"#cc0000"><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#cc0000"><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#cc0000"><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#cc0000"><br>
</font></div>
<div><br>
</div>
<div>&nbsp;&nbsp;</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Sat, Oct 8, 2016 at 11:52 AM, Cullen Jennings=
 <span dir=3D"ltr">
&lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank">fluffy@iii.ca</a>&gt=
;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<br>
Question came up if this morning if rtcp-mux should be TRANSPORT instead of=
 IDENTICAL. Anyone remember why it is not TRANSPORT.<br>
<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B4BD39C7DESESSMB209erics_--


From nobody Sun Oct  9 00:01:43 2016
Return-Path: <deadbeef@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 0468F1294AD for <mmusic@ietfa.amsl.com>; Sun,  9 Oct 2016 00:01:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.216
X-Spam-Level: 
X-Spam-Status: No, score=-5.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-2.996, SPF_PASS=-0.001] 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 c75l1JYquSYs for <mmusic@ietfa.amsl.com>; Sun,  9 Oct 2016 00:01:39 -0700 (PDT)
Received: from mail-qt0-f175.google.com (mail-qt0-f175.google.com [209.85.216.175]) (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 4E9A812948C for <mmusic@ietf.org>; Sun,  9 Oct 2016 00:01:39 -0700 (PDT)
Received: by mail-qt0-f175.google.com with SMTP id f6so37379766qtd.2 for <mmusic@ietf.org>; Sun, 09 Oct 2016 00:01:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=r7pQDUCJeA1pR+y/WJXGMb0C4tvTTh+tgEzB+Ps3AuU=; b=Z1Pg0UxPrcspC2YF5HDKz+RhKr0g2Lj7Y/8taAEkyMw5CJt1ZtyXrG+s4JeC47fYtd 94vrZcjeP8qTk8WxFC7pJUodLAxv5O5WwlSQtO6qwnweM8okbQ7h0UMlcMaFXaIizigf jgU5PypHXYGNFN10v6Ry7jnC6jnRgWt3pnA08vFe34bJuXB42PLXsSLTmnRL+u5BUPfI vpLbePQUlOGTxqhIABoM/xshmWce09+3ECMH4AN1XH6CkAyXPhnsBjSyDsJXJyB8g628 99tARLrl/UeOxC/nbONLqrVcdjt6Cb6lrP0S0YOF8YWC8j/m064ZH0jrgHorVwsZa9ww BZcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=r7pQDUCJeA1pR+y/WJXGMb0C4tvTTh+tgEzB+Ps3AuU=; b=Zy1/yq2JnuUBm8FNyntworGZZhNj00D6lX3rV8nAiNbZ0iV598y4dETu0uTrY2nNog w78Da4zdFZshFgch5UPcEPqMoUT+gJIKt55sn0JU1JGt4+uhCxK9ma0wVu8s3KdMsr5m hP7rpjJW9S2ojRLFzOQaOSTq5jHvUNm0hia6p4IcfuUs8sVRcspqPHs3soGT6NiBF3h1 8HL9hgfcZLmB9xqQac7RvUtL2NqJDhDIMdWtV+0HdRRfVVfsrAPlV/D/aDSIe+Sjzuit zrx/ZOoQ4eX8i9qW4IcuF3z45RarfOTQvh5q+rwHvvHinw3Uda+JlF9cW2YmvzvJtwxD VJ7g==
X-Gm-Message-State: AA6/9Rn4cxae6jxWxKib1qnbQnDUnr0lgCLS7sLo4cTcZyRVgFfGxfSFfHYLzjBqLOIqt3bwPF25nKCf5KeC2w2a
X-Received: by 10.200.41.201 with SMTP id 9mr1542691qtt.138.1475996438283; Sun, 09 Oct 2016 00:00:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.49.33 with HTTP; Sun, 9 Oct 2016 00:00:37 -0700 (PDT)
Received: by 10.237.49.33 with HTTP; Sun, 9 Oct 2016 00:00:37 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD39C7D@ESESSMB209.ericsson.se>
References: <B8CCCE95-5080-4B97-9043-3EEE8AAA8ECA@iii.ca> <CAMRcRGSwhxpUvjx1id-a-wRwTKYwJ3VKbDKQQ36RjPMgOgBuHw@mail.gmail.com> <CAK35n0bOzKPVpD_wYyXvnG_dFE68KZ5RcNAPisx0eJLDM7cv2A@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD39C7D@ESESSMB209.ericsson.se>
From: Taylor Brandstetter <deadbeef@google.com>
Date: Sun, 9 Oct 2016 00:00:37 -0700
Message-ID: <CAK35n0ZEcKLA9UyH-_8YEHN=y8kdirH11y3xb4ySSAJKsoSB-A@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a1139743a650fd7053e6933ba
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/-GWmVAlIjijkytvh9weq0aGByC8>
Cc: mmusic WG <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Suhas Nandakumar <snandaku@cisco.com>
Subject: Re: [MMUSIC] rtcp-mux in SDP mux
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Oct 2016 07:01:42 -0000

--001a1139743a650fd7053e6933ba
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Can you elaborate more? What negative outcome would occur if the IDENTICAL
rule wasn't followed? Even if RTCP mux negotiation depended on which m=3D
line was selected for bundling, the offerer would still always have enough
information to demux RTCP, correct?

Is this just to prevent implementations from doing something they probably
didn't intend to do, or to simplify implementations? If so, I can accept
that argument, I just want to clearly understand the motivation. I've
noticed at least one attribute move from "IDENTICAL" to "TRANSPORT", so it
would be useful to know where the line is being drawn.

On Oct 8, 2016 1:32 PM, "Christer Holmberg" <christer.holmberg@ericsson.com=
>
wrote:

> Hi,
>
> Note that when the initial offer is sent, it is yet not known which m-
> line will become the BUNDLE m- line. For that reason a=3Drtcp-mux needs t=
o be
> associated with every m- line.
>
> Regards,
>
> Christer
>
> Sent from my Windows Phone
> ------------------------------
> From: Taylor Brandstetter <deadbeef@google.com>
> Sent: =E2=80=8E08/=E2=80=8E10/=E2=80=8E2016 22:57
> To: Suhas Nandakumar <suhasietf@gmail.com>
> Cc: mmusic <mmusic@ietf.org>; Cullen Jennings <fluffy@iii.ca>; Suhas
> Nandakumar <snandaku@cisco.com>
> Subject: Re: [MMUSIC] rtcp-mux in SDP mux
>
> If the offerer wants to multiplex RTP/RTCP regardless of whether or not
> bundling is enabled, it can do this even if rtcp-mux is in the TRANSPORT
> category, correct? TRANSPORT doesn't seem to prevent putting the same
> attribute in every media description.
>
> So, what exactly does being in the IDENTICAL category protect against?
> That's what I'm having a hard time understanding.
>
> On Sat, Oct 8, 2016 at 12:01 PM, Suhas Nandakumar <suhasietf@gmail.com>
> wrote:
>
>> Hello Cullen
>>
>>    The reasoning for IDENTICAL category for a=3Drtcp-mux was to handle t=
he
>> case of  Initial Offers ( pre bundle address selection) so as to enable =
the
>> Offerer to multiplex RTP/RTCP even in the case of BUNDLE semantics being
>> rejected in the Answer.
>>
>> So,  In the initial Offer, if the Offerer wants to multiplex RTP/RTCP it
>> needs to include it in all the m=3Dlines (as defined by the IDENTICAL
>> category). This is because, if the BUNDLE semantics gets rejected the
>> offerer can still do  RTP/RTCP multiplexing on those m=3Dlines.
>> OTOH, if a=3Drtcp-mux was included only in the m=3Dline whose mid was li=
sted
>> as the first in the a=3Dgroup:BUNDLE line (TRANSPORT) and the BUNDLE
>> semantics gets rejected, there is no way for the Software to imply RTCP =
Mux
>> or not to.
>>
>> However once BUNDLE gets accepted and shared address is chosen, the
>> eventual Offers/Answers can have IDENTICAL category attributes included =
in
>> just the bundled m=3Dline than repeatng ( as defined in Section 8.1 of t=
he
>> BUNDLE spec)
>>
>> Hope this answers the question
>>
>> Cheers
>> Suhas
>>
>>
>>
>>
>>
>>
>>
>> On Sat, Oct 8, 2016 at 11:52 AM, Cullen Jennings <fluffy@iii.ca> wrote:
>>
>>>
>>> Question came up if this morning if rtcp-mux should be TRANSPORT instea=
d
>>> of IDENTICAL. Anyone remember why it is not TRANSPORT.
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>

--001a1139743a650fd7053e6933ba
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Can you elaborate more? What negative outcome would occur if=
 the IDENTICAL rule wasn&#39;t followed? Even if RTCP mux negotiation depen=
ded on which m=3D line was selected for bundling, the offerer would still a=
lways have enough information to demux RTCP, correct?</p>
<p dir=3D"ltr">Is this just to prevent implementations from doing something=
 they probably didn&#39;t intend to do, or to simplify implementations? If =
so, I can accept that argument, I just want to clearly understand the motiv=
ation. I&#39;ve noticed at least one attribute move from &quot;IDENTICAL&qu=
ot; to &quot;TRANSPORT&quot;, so it would be useful to know where the line =
is being drawn.</p>
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Oct 8, 2016 1:=
32 PM, &quot;Christer Holmberg&quot; &lt;<a href=3D"mailto:christer.holmber=
g@ericsson.com">christer.holmberg@ericsson.com</a>&gt; wrote:<br type=3D"at=
tribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">



<div>
<div>
<div style=3D"font-family:Calibri,sans-serif;font-size:11pt">Hi,<br>
<br>
Note that when the initial offer is sent, it is yet not known which m- line=
 will become the BUNDLE m- line. For that reason a=3Drtcp-mux needs to be a=
ssociated with every m- line.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">From:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt"><a hre=
f=3D"mailto:deadbeef@google.com" target=3D"_blank">Taylor Brandstetter</a><=
/span><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">Sent:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt">=E2=80=
=8E08/=E2=80=8E10/=E2=80=8E2016 22:57</span><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">To:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt"><a hre=
f=3D"mailto:suhasietf@gmail.com" target=3D"_blank">Suhas Nandakumar</a></sp=
an><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">Cc:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt"><a hre=
f=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic</a>;
<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank">Cullen Jennings</a>; <a =
href=3D"mailto:snandaku@cisco.com" target=3D"_blank">
Suhas Nandakumar</a></span><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">Subject:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt">Re: [M=
MUSIC] rtcp-mux in SDP mux</span><br>
<br>
</div>
<div>
<div dir=3D"ltr">If the offerer wants to multiplex RTP/RTCP regardless of w=
hether or not bundling is enabled, it can do this even if rtcp-mux is in th=
e TRANSPORT category, correct? TRANSPORT doesn&#39;t seem to prevent puttin=
g the same attribute in every media description.
<div><br>
</div>
<div>So, what exactly does being in the IDENTICAL category protect against?=
 That&#39;s what I&#39;m having a hard time understanding.</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Sat, Oct 8, 2016 at 12:01 PM, Suhas Nandakuma=
r <span dir=3D"ltr">
&lt;<a href=3D"mailto:suhasietf@gmail.com" target=3D"_blank">suhasietf@gmai=
l.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><font color=3D"#134f5c">Hello Cullen</font>
<div><font color=3D"#134f5c"><br>
</font></div>
<div><font color=3D"#134f5c">=C2=A0 =C2=A0The reasoning for IDENTICAL categ=
ory for a=3Drtcp-mux was to handle the case of =C2=A0Initial Offers ( pre b=
undle address selection) so as to enable the Offerer to multiplex RTP/RTCP =
even in the case of BUNDLE semantics being rejected
 in the Answer.</font></div>
<div><font color=3D"#134f5c"><br>
</font></div>
<div><font color=3D"#134f5c"><span style=3D"font-size:12.8px">So, =C2=A0In =
the initial Offer, if the Offerer wants to multiplex RTP/RTCP it needs to i=
nclude it in all the m=3Dlines (as defined by the IDENTICAL category). This=
 is because, if the BUNDLE semantics gets rejected
 the offerer can still do =C2=A0RTP/RTCP=C2=A0multiplexing on those m=3Dlin=
es.=C2=A0</span><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c">OTOH, if a=3Drtcp-m=
ux was included only in the m=3Dline whose mid was listed as the first in t=
he a=3Dgroup:BUNDLE line (TRANSPORT) and the BUNDLE semantics gets rejected=
, there is no way for the Software to imply
 RTCP Mux or not to.</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c"><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c">However once BUNDLE=
 gets accepted and shared address is chosen, the eventual Offers/Answers ca=
n have IDENTICAL category attributes included in just the bundled m=3Dline =
than repeatng ( as defined in Section
 8.1 of the BUNDLE spec)</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c"><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c">Hope this answers t=
he question</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c"><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#134f5c">Cheers</font></div>
<span class=3D"m_-4797842707380663036HOEnZb"><font color=3D"#888888">
<div style=3D"font-size:12.8px"><font color=3D"#134f5c">Suhas</font></div>
</font></span>
<div>
<div class=3D"m_-4797842707380663036h5">
<div style=3D"font-size:12.8px"><font color=3D"#cc0000"><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#cc0000"><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#cc0000"><br>
</font></div>
<div style=3D"font-size:12.8px"><font color=3D"#cc0000"><br>
</font></div>
<div><br>
</div>
<div>=C2=A0=C2=A0</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Sat, Oct 8, 2016 at 11:52 AM, Cullen Jennings=
 <span dir=3D"ltr">
&lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank">fluffy@iii.ca</a>&gt=
;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Question came up if this morning if rtcp-mux should be TRANSPORT instead of=
 IDENTICAL. Anyone remember why it is not TRANSPORT.<br>
<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>

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

--001a1139743a650fd7053e6933ba--


From nobody Sun Oct  9 01:30:40 2016
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 66F821294DF for <mmusic@ietfa.amsl.com>; Sun,  9 Oct 2016 01:30:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 GocBWfqV9xCv for <mmusic@ietfa.amsl.com>; Sun,  9 Oct 2016 01:30:37 -0700 (PDT)
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 5F0CE1294DB for <mmusic@ietf.org>; Sun,  9 Oct 2016 01:30:37 -0700 (PDT)
X-AuditID: c1b4fb2d-1c7ff700000009f7-f1-57fa0029e95f
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by  (Symantec Mail Security) with SMTP id 98.A7.02551.9200AF75; Sun,  9 Oct 2016 10:30:35 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0319.002; Sun, 9 Oct 2016 10:30:33 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Taylor Brandstetter <deadbeef@google.com>
Thread-Topic: [MMUSIC] rtcp-mux in SDP mux
Thread-Index: AQHSIZUqDPd/JqOcIEyoir+BQep+zaCeyDEAgAAPYwCAACtlaoAAjgKAgAA4kLA=
Date: Sun, 9 Oct 2016 08:30:32 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD3C70A@ESESSMB209.ericsson.se>
References: <B8CCCE95-5080-4B97-9043-3EEE8AAA8ECA@iii.ca> <CAMRcRGSwhxpUvjx1id-a-wRwTKYwJ3VKbDKQQ36RjPMgOgBuHw@mail.gmail.com> <CAK35n0bOzKPVpD_wYyXvnG_dFE68KZ5RcNAPisx0eJLDM7cv2A@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD39C7D@ESESSMB209.ericsson.se> <CAK35n0ZEcKLA9UyH-_8YEHN=y8kdirH11y3xb4ySSAJKsoSB-A@mail.gmail.com>
In-Reply-To: <CAK35n0ZEcKLA9UyH-_8YEHN=y8kdirH11y3xb4ySSAJKsoSB-A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBIsWRmVeSWpSXmKPExsUyM2J7oK42w69wg4a7BhaXVzxktfiw/gej xdTlj1ksFh+4z2qxc24HswOrx5TfG1k9ds66y+6xYFOpx5IlP5k8Lp//yBjAGsVlk5Kak1mW WqRvl8CVceTiBfaCHo2KGVsuMzcwdqh3MXJySAiYSMybfYqli5GLQ0hgPaPEzrWfGSGcxYwS 0x80M3UxcnCwCVhIdP/TBmkQEdCVuPl1IRtIDbPAZEaJNa8PsYMkhAU0JW4+WsoCUaQlMWf5 X3YI20+i8+QHZhCbRUBF4urSTjCbV8BX4mHLGmaIZZeYJHYsmMUCsoxTIFDi6GoHkBpGATGJ 76fWMIHYzALiEreezGeCuFpAYsme88wQtqjEy8f/WCFsJYlFtz+D3cwMdM/6XfoQrYoSU7of skOsFZQ4OfMJywRG0VlIps5C6JiFpGMWko4FjCyrGEWLU4uLc9ONjPVSizKTi4vz8/TyUks2 MQLj6+CW37o7GFe/djzEKMDBqMTDm5DzM1yINbGsuDL3EKMEB7OSCG/TP6AQb0piZVVqUX58 UWlOavEhRmkOFiVxXrOV98OFBNITS1KzU1MLUotgskwcnFINjCofsnIFFR4t3Vn5rs33U+qS 1X1m95I39BTPdxeuSHmpw993Ysr6G3siIg+EHBQOaRBonVhVKKmmf7pwZ4OV9/Ur0gytr7Sn ZG55fbhRxHN2ZtEKYebDnH+mdn3e/9uNc++Zt5xKXKVLNRV6rbxSUm04/GaUWUrvueOX9TzA O7lonvz3yPMMSizFGYmGWsxFxYkA4XmlXqsCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ExKH0aRXHJjI9on26-ISEQXzCvg>
Cc: mmusic WG <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Suhas Nandakumar <snandaku@cisco.com>
Subject: Re: [MMUSIC] rtcp-mux in SDP mux
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Oct 2016 08:30:39 -0000

SGksDQoNCj5DYW4geW91IGVsYWJvcmF0ZSBtb3JlPyBXaGF0IG5lZ2F0aXZlIG91dGNvbWUgd291
bGQgb2NjdXIgaWYgdGhlIElERU5USUNBTCBydWxlDQo+d2Fzbid0IGZvbGxvd2VkPyBFdmVuIGlm
IFJUQ1AgbXV4IG5lZ290aWF0aW9uIGRlcGVuZGVkIG9uIHdoaWNoIG09IGxpbmUgd2FzIHNlbGVj
dGVkIA0KPmZvciBidW5kbGluZywgdGhlIG9mZmVyZXIgd291bGQgc3RpbGwgYWx3YXlzIGhhdmUg
ZW5vdWdoIGluZm9ybWF0aW9uIHRvIGRlbXV4IFJUQ1AsIGNvcnJlY3Q/DQo+DQo+SXMgdGhpcyBq
dXN0IHRvIHByZXZlbnQgaW1wbGVtZW50YXRpb25zIGZyb20gZG9pbmcgc29tZXRoaW5nIHRoZXkg
cHJvYmFibHkgZGlkbid0IGludGVuZCB0bw0KPmRvLCBvciB0byBzaW1wbGlmeSBpbXBsZW1lbnRh
dGlvbnM/IElmIHNvLCBJIGNhbiBhY2NlcHQgdGhhdCBhcmd1bWVudCwgSSBqdXN0IHdhbnQgdG8g
Y2xlYXJseQ0KPnVuZGVyc3RhbmQgdGhlIG1vdGl2YXRpb24uIEkndmUgbm90aWNlZCBhdCBsZWFz
dCBvbmUgYXR0cmlidXRlIG1vdmUgZnJvbSAiSURFTlRJQ0FMIiB0bw0KPiJUUkFOU1BPUlQiLCBz
byBpdCB3b3VsZCBiZSB1c2VmdWwgdG8ga25vdyB3aGVyZSB0aGUgbGluZSBpcyBiZWluZyBkcmF3
bi4NCg0KVGhlIGJ1bmRsZSBtLSBsaW5lIHNoYWxsIGV4cGxpY2l0bHkgY29udGFpbiBhbGwgY29t
bW9uIGluZm9ybWF0aW9uIGFzc29jaWF0ZWQgd2l0aCB0aGUgQlVORExFIGdyb3VwLiBUaGF0IG1l
YW5zIElERU5USUNBTCBjYXRlZ29yeSBTRFAgYXR0cmlidXRlcy4gRW5kcG9pbnRzIHNoYWxsIG5v
dCBoYXZlIHRvIGxvb2sgaW4gb3RoZXIgbS0gbGluZXMgd2l0aGluIHRoZSBCVU5ETEUgZ3JvdXAg
dG8gZmluZCB0aGUgY29tbW9uIGluZm9ybWF0aW9uLg0KDQpOb3csIGluIHRoZSBjYXNlIG9mIFJU
UC9SVENQIG11eCwgb25lIGNvdWxkIG9mIGNvdXJzZSBzYXkgdGhhdCBpdCBkb2Vzbid0IG1hdHRl
ciBpZiBhPXJ0Y3AtbXV4IGlzIHByZXNlbnQgaW4gdGhlIGJ1bmRsZSBtPSBsaW5lIG9yIG5vdCwg
YXMgUlRQL1JUQ1AgYnkgZGVmYXVsdCBtdXN0IGJlIHVzZWQgd2l0aGluIHRoZSBCVU5ETEUgZ3Jv
dXAgKHBlciBhZ3JlZW1lbnQgYXQgSUVURiM5NCkuIEJ1dCwgSSB0aGluayBpdCBpcyBiZXR0ZXIg
dG8gYmUgY29uc2lzdGVudC4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQoNCg0KT24gT2N0
IDgsIDIwMTYgMTozMiBQTSwgIkNocmlzdGVyIEhvbG1iZXJnIiA8Y2hyaXN0ZXIuaG9sbWJlcmdA
ZXJpY3Nzb24uY29tPiB3cm90ZToNCkhpLA0KDQpOb3RlIHRoYXQgd2hlbiB0aGUgaW5pdGlhbCBv
ZmZlciBpcyBzZW50LCBpdCBpcyB5ZXQgbm90IGtub3duIHdoaWNoIG0tIGxpbmUgd2lsbCBiZWNv
bWUgdGhlIEJVTkRMRSBtLSBsaW5lLiBGb3IgdGhhdCByZWFzb24gYT1ydGNwLW11eCBuZWVkcyB0
byBiZSBhc3NvY2lhdGVkIHdpdGggZXZlcnkgbS0gbGluZS4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0
ZXINCg0KU2VudCBmcm9tIG15IFdpbmRvd3MgUGhvbmUNCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCkZyb206IFRheWxvciBCcmFuZHN0ZXR0ZXINClNlbnQ6IOKAjjA4
L+KAjjEwL+KAjjIwMTYgMjI6NTcNClRvOiBTdWhhcyBOYW5kYWt1bWFyDQpDYzogbW11c2ljOyBD
dWxsZW4gSmVubmluZ3M7IFN1aGFzIE5hbmRha3VtYXINClN1YmplY3Q6IFJlOiBbTU1VU0lDXSBy
dGNwLW11eCBpbiBTRFAgbXV4DQpJZiB0aGUgb2ZmZXJlciB3YW50cyB0byBtdWx0aXBsZXggUlRQ
L1JUQ1AgcmVnYXJkbGVzcyBvZiB3aGV0aGVyIG9yIG5vdCBidW5kbGluZyBpcyBlbmFibGVkLCBp
dCBjYW4gZG8gdGhpcyBldmVuIGlmIHJ0Y3AtbXV4IGlzIGluIHRoZSBUUkFOU1BPUlQgY2F0ZWdv
cnksIGNvcnJlY3Q/IFRSQU5TUE9SVCBkb2Vzbid0IHNlZW0gdG8gcHJldmVudCBwdXR0aW5nIHRo
ZSBzYW1lIGF0dHJpYnV0ZSBpbiBldmVyeSBtZWRpYSBkZXNjcmlwdGlvbi4gDQoNClNvLCB3aGF0
IGV4YWN0bHkgZG9lcyBiZWluZyBpbiB0aGUgSURFTlRJQ0FMIGNhdGVnb3J5IHByb3RlY3QgYWdh
aW5zdD8gVGhhdCdzIHdoYXQgSSdtIGhhdmluZyBhIGhhcmQgdGltZSB1bmRlcnN0YW5kaW5nLg0K
DQpPbiBTYXQsIE9jdCA4LCAyMDE2IGF0IDEyOjAxIFBNLCBTdWhhcyBOYW5kYWt1bWFyIDxzdWhh
c2lldGZAZ21haWwuY29tPiB3cm90ZToNCkhlbGxvIEN1bGxlbiANCg0KwqAgwqBUaGUgcmVhc29u
aW5nIGZvciBJREVOVElDQUwgY2F0ZWdvcnkgZm9yIGE9cnRjcC1tdXggd2FzIHRvIGhhbmRsZSB0
aGUgY2FzZSBvZiDCoEluaXRpYWwgT2ZmZXJzICggcHJlIGJ1bmRsZSBhZGRyZXNzIHNlbGVjdGlv
bikgc28gYXMgdG8gZW5hYmxlIHRoZSBPZmZlcmVyIHRvIG11bHRpcGxleCBSVFAvUlRDUCBldmVu
IGluIHRoZSBjYXNlIG9mIEJVTkRMRSBzZW1hbnRpY3MgYmVpbmcgcmVqZWN0ZWQgaW4gdGhlIEFu
c3dlci4NCg0KU28sIMKgSW4gdGhlIGluaXRpYWwgT2ZmZXIsIGlmIHRoZSBPZmZlcmVyIHdhbnRz
IHRvIG11bHRpcGxleCBSVFAvUlRDUCBpdCBuZWVkcyB0byBpbmNsdWRlIGl0IGluIGFsbCB0aGUg
bT1saW5lcyAoYXMgZGVmaW5lZCBieSB0aGUgSURFTlRJQ0FMIGNhdGVnb3J5KS4gVGhpcyBpcyBi
ZWNhdXNlLCBpZiB0aGUgQlVORExFIHNlbWFudGljcyBnZXRzIHJlamVjdGVkIHRoZSBvZmZlcmVy
IGNhbiBzdGlsbCBkbyDCoFJUUC9SVENQwqBtdWx0aXBsZXhpbmcgb24gdGhvc2UgbT1saW5lcy7C
oA0KT1RPSCwgaWYgYT1ydGNwLW11eCB3YXMgaW5jbHVkZWQgb25seSBpbiB0aGUgbT1saW5lIHdo
b3NlIG1pZCB3YXMgbGlzdGVkIGFzIHRoZSBmaXJzdCBpbiB0aGUgYT1ncm91cDpCVU5ETEUgbGlu
ZSAoVFJBTlNQT1JUKSBhbmQgdGhlIEJVTkRMRSBzZW1hbnRpY3MgZ2V0cyByZWplY3RlZCwgdGhl
cmUgaXMgbm8gd2F5IGZvciB0aGUgU29mdHdhcmUgdG8gaW1wbHkgUlRDUCBNdXggb3Igbm90IHRv
Lg0KDQpIb3dldmVyIG9uY2UgQlVORExFIGdldHMgYWNjZXB0ZWQgYW5kIHNoYXJlZCBhZGRyZXNz
IGlzIGNob3NlbiwgdGhlIGV2ZW50dWFsIE9mZmVycy9BbnN3ZXJzIGNhbiBoYXZlIElERU5USUNB
TCBjYXRlZ29yeSBhdHRyaWJ1dGVzIGluY2x1ZGVkIGluIGp1c3QgdGhlIGJ1bmRsZWQgbT1saW5l
IHRoYW4gcmVwZWF0bmcgKCBhcyBkZWZpbmVkIGluIFNlY3Rpb24gOC4xIG9mIHRoZSBCVU5ETEUg
c3BlYykNCg0KSG9wZSB0aGlzIGFuc3dlcnMgdGhlIHF1ZXN0aW9uDQoNCkNoZWVycw0KU3VoYXMN
Cg0KDQoNCg0KDQrCoMKgDQoNCk9uIFNhdCwgT2N0IDgsIDIwMTYgYXQgMTE6NTIgQU0sIEN1bGxl
biBKZW5uaW5ncyA8Zmx1ZmZ5QGlpaS5jYT4gd3JvdGU6DQoNClF1ZXN0aW9uIGNhbWUgdXAgaWYg
dGhpcyBtb3JuaW5nIGlmIHJ0Y3AtbXV4IHNob3VsZCBiZSBUUkFOU1BPUlQgaW5zdGVhZCBvZiBJ
REVOVElDQUwuIEFueW9uZSByZW1lbWJlciB3aHkgaXQgaXMgbm90IFRSQU5TUE9SVC4NCg0KDQpf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KbW11c2ljIG1h
aWxpbmcgbGlzdA0KbW11c2ljQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL21tdXNpYw0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQptbXVzaWMgbWFpbGluZyBsaXN0DQptbXVzaWNAaWV0Zi5vcmcNCmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljDQoNCg==


From nobody Sun Oct  9 01:47:21 2016
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 9D97C1294FF for <mmusic@ietfa.amsl.com>; Sun,  9 Oct 2016 01:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 aldUutTCyY42 for <mmusic@ietfa.amsl.com>; Sun,  9 Oct 2016 01:47:18 -0700 (PDT)
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 D78371294EB for <mmusic@ietf.org>; Sun,  9 Oct 2016 01:47:17 -0700 (PDT)
X-AuditID: c1b4fb3a-ab7ff7000000099a-02-57fa0411c2b3
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by  (Symantec Mail Security) with SMTP id 0C.45.02458.1140AF75; Sun,  9 Oct 2016 10:47:15 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0319.002; Sun, 9 Oct 2016 10:47:13 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Cullen Jennings <fluffy@iii.ca>
Thread-Topic: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
Thread-Index: AQHSG0GgBWsMgAttg0WZUBo1tL92NKCb3CYAgAD/+ICAALTUgIABEY6AgAAs7QCAABtZgIAA7eSA
Date: Sun, 9 Oct 2016 08:47:13 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD3C780@ESESSMB209.ericsson.se>
References: <147481162395.28315.18346373858565370012.idtracker@ietfa.amsl.com> <A1093C70-CAC8-4A08-8D42-F5395B88A951@cisco.com> <988175E4-B54A-4B29-BAE0-B3F98C22B475@iii.ca> <D41D4800.10A3F%christer.holmberg@ericsson.com> <68971202-4458-407D-A4AF-BCDCE54F2F78@iii.ca> <ba29c562-fe49-c1f1-d2ba-5bdf3621f9b6@alum.mit.edu> <BEA54B46-C68E-44DC-BA7F-16E2E80094A9@iii.ca> <a0667b00-ac54-10ba-e9ec-3fe67a4e19f7@alum.mit.edu>
In-Reply-To: <a0667b00-ac54-10ba-e9ec-3fe67a4e19f7@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpikeLIzCtJLcpLzFFi42KZGbFdWleY5Ve4wa3rlhYf1v9gtJi6/DGL xYoNB1gdmD3+vv/A5LFkyU8mj8vnPzIGMEdx2aSk5mSWpRbp2yVwZfzs/8lYsE+w4mvbK8YG xru8XYycHBICJhJXbqxlB7GFBNYzSlyfE9TFyAVkL2aUuH+lgamLkYODTcBCovufNkiNiICn xNIfP1lAwswC6hJXFweBmMICbhJrH1tCVLhLzJ41jw3CjpL43/GLGaSERUBF4shZJRCTV8BX 4sUpA4g965klpqzdwQJSzingILHu0kKwVkYBMYnvp9YwgdjMAuISt57MZ4I4WEBiyZ7zzBC2 qMTLx/9YIWwliUW3P0PV60gs2P2JDcLWlli28DVYPa+AoMTJmU9YJjCKzkIydhaSlllIWmYh aVnAyLKKUbQ4tbg4N93ISC+1KDO5uDg/Ty8vtWQTIzBmDm75bbWD8eBzx0OMAhyMSjy8D+78 DBdiTSwrrsw9xCjBwawkwvuN6Ve4EG9KYmVValF+fFFpTmrxIUZpDhYlcV6zlffDhQTSE0tS s1NTC1KLYLJMHJxSDYxG2peWzus+rdH9R82i4t5h4Ybag+VXwg/nm6wsc3U87Tt9eWXp57uP Tx35dWwiC7vqdoUXDfbbtq3Zlp7WdXIdI2NHbtHdaqNHwse5rmnUftoraVLjyK54yefKa82y A0/D+xKWe726VGO81ND6lKpd3GO3cwKVp2ufrLd7ZSqquUSp/OEiNyElluKMREMt5qLiRABd HU/4lQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/IAfWnsHMtlxNRo9XZpkRqsYeL9U>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Oct 2016 08:47:19 -0000

Hi,

>>> I know you were following the wgchairs thread on '"Updates: RFC xxx"=20
>>> - what does it actually mean ?' because you replied in that thread.=20
>>> If you agree with the conclusion there th
>>
>> The conclusion of that thread - after it expanded beyond the chairs=20
>> list
>> - was AFAIC, that this was unclear and someone should write a RFC to=20
>> clarify it. If you think there was consensus on what update means,=20
>> then I strongly agree and invite you to go look at number of people=20
>> that put out position on each side. Until a new RFC gets issues, I=20
>> will use the meaning in the only published RFC that defined this even=20
>> though it was deprecated by a later RFC that did not provide any=20
>> definition one way or the other.
>
> My understanding was that it is unclear and people were happy to leave it=
 unclear. Instead
> of clarifying it, individual drafts are expected to add prominent text th=
at explains what it=20
> means in the context of that draft.

...which is exactly what we have done in the latest version of draft-4572-u=
pdate.

But, again, if that's enough, I'm personally ok to remove the cipher update=
.

> I don't *like* that conclusion, but I don't consider it worthwhile to pur=
sue it further.
>
>> And to be clear, what I am proposing here is a simple way for this WG=20
>> to move forward without having to resolve that debate or wait for=20
>> consensus on what update means.
>
> If splitting this into two drafts will satisfy you, then I'm ok with that=
.
>
> But it also seems like it ought to be adequate to leave it one document, =
with Updates, and a clear statement of what Updates does and doesn't mean i=
n this case.

In my opinion, the most time critical is to get the multiple fingerprint cl=
arification done, so I'll start working on a pull request that removes all =
the SHA-256 stuff.

I do think it's sad that issues like this are raised in the last minute - e=
specially by people that for sure have been aware of the work - e.g., when =
others have spent lots of time in order to come up with agreeable text. But=
, at the end of the day what matters is to finalize the work...

Regards,

Christer


From nobody Sun Oct  9 03:20:17 2016
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 59271129527 for <mmusic@ietfa.amsl.com>; Sun,  9 Oct 2016 03:20:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 vvu8g3ZWob5S for <mmusic@ietfa.amsl.com>; Sun,  9 Oct 2016 03:20:13 -0700 (PDT)
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 4F5FE1294F3 for <mmusic@ietf.org>; Sun,  9 Oct 2016 03:20:12 -0700 (PDT)
X-AuditID: c1b4fb30-b73ff70000000cb2-03-57fa19d9b437
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by  (Symantec Mail Security) with SMTP id DC.8C.03250.9D91AF75; Sun,  9 Oct 2016 12:20:11 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0319.002; Sun, 9 Oct 2016 12:20:09 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Cullen Jennings <fluffy@iii.ca>
Thread-Topic: draft-4572-update: Pull request to remove update of preferred cipher
Thread-Index: AdIiFoXGguc+z2LxTw6plGTOMKHxJA==
Date: Sun, 9 Oct 2016 10:20:09 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD3D963@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyM2K7pe5tyV/hBm9O8Vp8WP+D0WLq8scs Fis2HGB1YPb4+/4Dk8eSJT+ZPC6f/8gYwBzFZZOSmpNZllqkb5fAlTHp9RzWgv9iFTcPTmFr YNwp1MXIySEhYCLRMqGTtYuRi0NIYD2jxOeZd5ghnMWMEt+f3WPrYuTgYBOwkOj+pw3SICJQ L/H133ZWkDCzgLrE1cVBIGFhAV+JVS9fM0OUhEhc6fnIBmHrScxe0MIOYrMIqEjc39APVsML VH/3aScLiM0oICbx/dQaJhCbWUBc4taT+UwQtwlILNlznhnCFpV4+fgfK4StJLHo9meoeh2J Bbs/sUHY2hLLFr6Gmi8ocXLmE5YJjMKzkIydhaRlFpKWWUhaFjCyrGIULU4tTspNNzLSSy3K TC4uzs/Ty0st2cQIjISDW34b7GB8+dzxEKMAB6MSD29Czs9wIdbEsuLK3EOMEhzMSiK8h0R/ hQvxpiRWVqUW5ccXleakFh9ilOZgURLnNVt5P1xIID2xJDU7NbUgtQgmy8TBKdXAKCzucGnS C5FjeRrFWmKFxjONv/IFpi0pftw8ac9rw+qQydz9xgI3XLcUi/o98psw5cgZ+/uBccJvf0z4 x5AwU2ZG8twrQme2+SScOrXg4rukzVeMNtSv6Jt/+XbE5GVr+5cypjT68q3uuf2vU4fr0cHq /b07lZxE9sdPmc15u/++T5ng1dZlDEosxRmJhlrMRcWJAOrZCS6AAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/SKdbDWBoT-9EgLWwIUvvjCTiaKA>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: [MMUSIC] draft-4572-update: Pull request to remove update of preferred cipher
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Oct 2016 10:20:15 -0000

Hi,

I've created a PR that removes all text regarding updating the preferred ci=
pher suite of RFC 4572. The text now only contains the multiple fingerprint=
 clarifications.

https://github.com/cdh4u/draft-4572-update/pull/6

Regards,

Christer


-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: 09 October 2016 11:47
To: Paul Kyzivat <pkyzivat@alum.mit.edu>; Cullen Jennings <fluffy@iii.ca>
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt

Hi,

>>> I know you were following the wgchairs thread on '"Updates: RFC xxx"=20
>>> - what does it actually mean ?' because you replied in that thread.=20
>>> If you agree with the conclusion there th
>>
>> The conclusion of that thread - after it expanded beyond the chairs=20
>> list
>> - was AFAIC, that this was unclear and someone should write a RFC to=20
>> clarify it. If you think there was consensus on what update means,=20
>> then I strongly agree and invite you to go look at number of people=20
>> that put out position on each side. Until a new RFC gets issues, I=20
>> will use the meaning in the only published RFC that defined this even=20
>> though it was deprecated by a later RFC that did not provide any=20
>> definition one way or the other.
>
> My understanding was that it is unclear and people were happy to leave=20
> it unclear. Instead of clarifying it, individual drafts are expected=20
> to add prominent text that explains what it means in the context of that =
draft.

...which is exactly what we have done in the latest version of draft-4572-u=
pdate.

But, again, if that's enough, I'm personally ok to remove the cipher update=
.

> I don't *like* that conclusion, but I don't consider it worthwhile to pur=
sue it further.
>
>> And to be clear, what I am proposing here is a simple way for this WG=20
>> to move forward without having to resolve that debate or wait for=20
>> consensus on what update means.
>
> If splitting this into two drafts will satisfy you, then I'm ok with that=
.
>
> But it also seems like it ought to be adequate to leave it one document, =
with Updates, and a clear statement of what Updates does and doesn't mean i=
n this case.

In my opinion, the most time critical is to get the multiple fingerprint cl=
arification done, so I'll start working on a pull request that removes all =
the SHA-256 stuff.

I do think it's sad that issues like this are raised in the last minute - e=
specially by people that for sure have been aware of the work - e.g., when =
others have spent lots of time in order to come up with agreeable text. But=
, at the end of the day what matters is to finalize the work...

Regards,

Christer

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


From nobody Sun Oct  9 16:33:30 2016
Return-Path: <martin.thomson@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 83279128E19 for <mmusic@ietfa.amsl.com>; Sun,  9 Oct 2016 16:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 66Z6y4s6rEPj for <mmusic@ietfa.amsl.com>; Sun,  9 Oct 2016 16:33:27 -0700 (PDT)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 464F8124281 for <mmusic@ietf.org>; Sun,  9 Oct 2016 16:33:27 -0700 (PDT)
Received: by mail-qt0-x236.google.com with SMTP id q7so42698905qtq.1 for <mmusic@ietf.org>; Sun, 09 Oct 2016 16:33:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=5KhipPJH1Fxi76Sn98yWZnLuVZlI+wxMR7a9l7ukj9Q=; b=KOgHcjxxkI8NP8Bw4Cq42Y6LCh8TSbmYSEE+ZFL1TwBIggnpxOc5TFxZ7+7YtKXv0O Sa2Te6Gw4pDaTOSaGBBoD/7RSm5z3uVmgHhBrGqFiMCwG91o3at+Lvsm2eQmwu55WeP5 MCK8B7b2Cw4DGJFXqvMD+gKGOFsH1OghBbbMVn7NI6Owp9hKxgIfPn6cy+Q6wWXh4ynE dtAzN5q40+arAfuWBbXhChXIEULVoDC2MJXYSTN0uKMrTms7KIInK5Roe1dv9gTE1qF+ vma2mcKuokxVJ5JqKwwGJA5NSUhwV/MlDqw1gzyTavcOF8TPudYlocghCrTK7i+44rLs BEWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=5KhipPJH1Fxi76Sn98yWZnLuVZlI+wxMR7a9l7ukj9Q=; b=G5+RBipcY5J8pHJD5AFKlCygu6YW20vZcM9/Q2m7hf9dncnfBFCID/9ohJDZJJzuWS BhEbIuWw0cbPHH3abcyrn7tFKJpADh7BI8ABg1szkmso63AWVFaIDTAL8vS96/d7pfNc HC6Ts/EJsDPt/3TxkVJTy0VjT0JQhEbhRFVIQuYpGyxdgnf5qjxKVULoFQwpmN1Ev27i 5pAFm18GoIjZJetB6EI2X2bOl6/dC+kmtuL2Lc+D/X295LHqyO/ieXWYRechfNx1H6yf 0lq+ZJMYBCQj38Q4WNE+t7/hXCrXz/VEcPKn80h4V8nmSKZ22QLcy2oM/MZ3rbEK05zr 26+Q==
X-Gm-Message-State: AA6/9Rkk8Jjzizp9DvwtZrfmfiTNPALA9sEGUbCzBDQEkHZnRv/WZmsBN+9atmnq/VSRtw5DgRwIePzAB9Pdew==
X-Received: by 10.200.34.66 with SMTP id p2mr6271406qtp.107.1476056006177; Sun, 09 Oct 2016 16:33:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.85.7 with HTTP; Sun, 9 Oct 2016 16:33:25 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD3D963@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B4BD3D963@ESESSMB209.ericsson.se>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 10 Oct 2016 10:33:25 +1100
Message-ID: <CABkgnnXL7dBvpqVD+nEoG8F-+xahDwgu+0GXKGbxRQuZsoKesA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/0Tqdoym-yYWrfyets3jDYqCfn64>
Cc: Cullen Jennings <fluffy@iii.ca>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-4572-update: Pull request to remove update of preferred cipher
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Oct 2016 23:33:29 -0000

I think that this is a step backwards.  I wholeheartedly disagree with
Cullen's view that using "Updates" forces us to be constrained by the
document we are updating.  The whole point of "Updates" is to update
things.

Yes, that means that implementations that are 4572-compliant will now
be 4572-plus-update non-compliant.  But those are two different
things, we don't render a 4572-compliant implementation non-compliant
by publishing another document.

If we were to write yet another trivial draft to update to SHA-256, I
would argue that it update RFC 4572.  SHA-1 collision resistance is so
far gone at this point we'd be irresponsible to do otherwise.  So I
don't see what the paper-shuffling gains us.

On 9 October 2016 at 21:20, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> Hi,
>
> I've created a PR that removes all text regarding updating the preferred =
cipher suite of RFC 4572. The text now only contains the multiple fingerpri=
nt clarifications.
>
> https://github.com/cdh4u/draft-4572-update/pull/6
>
> Regards,
>
> Christer
>
>
> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmb=
erg
> Sent: 09 October 2016 11:47
> To: Paul Kyzivat <pkyzivat@alum.mit.edu>; Cullen Jennings <fluffy@iii.ca>
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-07.txt
>
> Hi,
>
>>>> I know you were following the wgchairs thread on '"Updates: RFC xxx"
>>>> - what does it actually mean ?' because you replied in that thread.
>>>> If you agree with the conclusion there th
>>>
>>> The conclusion of that thread - after it expanded beyond the chairs
>>> list
>>> - was AFAIC, that this was unclear and someone should write a RFC to
>>> clarify it. If you think there was consensus on what update means,
>>> then I strongly agree and invite you to go look at number of people
>>> that put out position on each side. Until a new RFC gets issues, I
>>> will use the meaning in the only published RFC that defined this even
>>> though it was deprecated by a later RFC that did not provide any
>>> definition one way or the other.
>>
>> My understanding was that it is unclear and people were happy to leave
>> it unclear. Instead of clarifying it, individual drafts are expected
>> to add prominent text that explains what it means in the context of that=
 draft.
>
> ...which is exactly what we have done in the latest version of draft-4572=
-update.
>
> But, again, if that's enough, I'm personally ok to remove the cipher upda=
te.
>
>> I don't *like* that conclusion, but I don't consider it worthwhile to pu=
rsue it further.
>>
>>> And to be clear, what I am proposing here is a simple way for this WG
>>> to move forward without having to resolve that debate or wait for
>>> consensus on what update means.
>>
>> If splitting this into two drafts will satisfy you, then I'm ok with tha=
t.
>>
>> But it also seems like it ought to be adequate to leave it one document,=
 with Updates, and a clear statement of what Updates does and doesn't mean =
in this case.
>
> In my opinion, the most time critical is to get the multiple fingerprint =
clarification done, so I'll start working on a pull request that removes al=
l the SHA-256 stuff.
>
> I do think it's sad that issues like this are raised in the last minute -=
 especially by people that for sure have been aware of the work - e.g., whe=
n others have spent lots of time in order to come up with agreeable text. B=
ut, at the end of the day what matters is to finalize the work...
>
> Regards,
>
> Christer
>
> _______________________________________________
> 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 Mon Oct 10 01:11:43 2016
Return-Path: <thomass.stach@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 43CAE1295F1 for <mmusic@ietfa.amsl.com>; Mon, 10 Oct 2016 01:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 b29CqqQmNvyE for <mmusic@ietfa.amsl.com>; Mon, 10 Oct 2016 01:11:40 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 D2A3412940E for <mmusic@ietf.org>; Mon, 10 Oct 2016 01:11:39 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id l131so112093530lfl.2 for <mmusic@ietf.org>; Mon, 10 Oct 2016 01:11:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=to:cc:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=nNy3urDOOQmDmINs4nq9O0bYF07FfQ0b+BZwy3Gh2IM=; b=PThLqJWOsKMj1CaRcHSva/gQjXxBtEJkQqfB4Nv/BQoygmeCfyX+dnmQY+gCELNTkS ad3OkE+MLRHdyvjoCPcdLBJPCMd/h/8R+bRJIhsreJqhR92Y8uSGf0r+iwvGDB95MGwl N3Ig6P1UJKfec5nIjPlhmBKwxWTPvj35QpGyLZkbEQUx+UBsoHpLoAQIe56aC3bnlbhp s1KbiWPyMbqfGRN+jmFOkDIL9KvCbIyiMKQMRROVo+ud8y6NhUBCTZvf/RRYKrPHGZZj WndQu9E/qDNcdUt9cboQXvSB9j8ONQPHkG311dEuFqCRBYdCiBrdQt2djA/QpmDdhXzl dxrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:cc:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=nNy3urDOOQmDmINs4nq9O0bYF07FfQ0b+BZwy3Gh2IM=; b=KgU+rrtdBK7ltI5J0wGs6dmCuO1OpesmyDtCsSWmUtbYmwOnfW1pdqro9QGC7YyB4E OPCxD9ODCaSNvUO2g/i3VVpUNBfT2BKHfiwauGIO+cMDx31sXWRNV6MdfyuKMEPQ9eiQ UIsDhtehOAYgjCwFzUssF0Mlh0DH8vUlbklyTOAeCF8S8pmiYeAnwViLMWygyXPvvx1F v2uuvE6b0VEbvhoyiYyU2nrPb1ewZfsCQPyL9AD9ARzw9xD7u2bZWtrJNs0mG+JlpM2Z 9XMM4agaZBxNdmxF/i3ayX4VJcDtwXLXYVbuUriv40AKOge0tU9XQKL4pl6w7Co5gZcS baxA==
X-Gm-Message-State: AA6/9RlDTc8U1YBZLXI19ZW1kYVr0jXCVA1Z/Zfwv3uoV4+H26sZw4ZJ+HfCac6f+/zc3A==
X-Received: by 10.46.5.8 with SMTP id 8mr8173691ljf.64.1476087096775; Mon, 10 Oct 2016 01:11:36 -0700 (PDT)
Received: from [192.168.2.110] (d91-130-16-98.cust.tele2.at. [91.130.16.98]) by smtp.googlemail.com with ESMTPSA id e65sm237885lji.18.2016.10.10.01.11.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Oct 2016 01:11:36 -0700 (PDT)
To: MMUSIC <mmusic@ietf.org>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <fdaa941a-8143-8caf-7feb-3ea6c37c837d@gmail.com>
Date: Mon, 10 Oct 2016 10:11:35 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/z_0HCQby4a5UIjgHJZPu7emCOc8>
Cc: draft-ietf-mmusic-ice-sip-sdp@tools.ietf.org
Subject: [MMUSIC] Review of draft-ietf-mmusic-ice-sip-sdp
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 10 Oct 2016 08:11:42 -0000

All,

I did a review of draft-ietf-mmusic-ice-sip-sdp.
Apart from some editorial stuff (at the end), my two main points are
- there is some text throughout the document, that in my opinion does 
not cover SDP/SIP issues,
   but rather some details of the ICE algorithm.
   Therefore it might be better to have that text in 
draft-ietf-ice-rfc5245bis.
   Details below
- There has been a lot of discussion about the updated offer.
   Is it the rough(?) consensus of the WG that it is still required?
   Note that for BUNDLE, which has similar issues, this requirement was 
removed.


Technical

Sections 4.1.1.1 .

  ... an updated offer/answer will be
    required after ICE processing completes in order to "fix up" the SDP ...

    and 4.1.5.1.1

  If any of those
    candidate pairs differ from the default candidate pairs in the most
    recent offer/answer exchange, the controlling agent MUST generate an
    updated offer as described in Section 4.2.

These are the sections that cover the updated offer.
they might need some changes dependent on what the WG's consensus on the 
issue.


Section 4.1.2.4
This text has nothing to do with SDP and should go to the end of section 
5.1.2. of draft-ietf-ice-rfc5245bis.
The same applies for Annex C, that gives the motivation.
BTW: The reference to 6.1.2.3. of ICE-BIS is wrong it should be 6.1.3.1

Section 4.1.4
Again, this text has nothing to do with SDP and should go to 
draft-ietf-ice-rfc5245bis (somewhere in section 6?).

Section 4.1.5
Except for the bit about forking and the updated offer I again think 
that this section should go to draft-ietf-ice-rfc5245bis as this section 
mostly describes ICE algorithm details and not SDP specifics.

Section 4.2.4
Once more this section describes details of the ICE algorithm and might 
be better suited for draft-ietf-ice-rfc5245bis.
However, the paragraph assumes that media streams are only added/removed 
via offer/answer, possibly together with an ICE restart. Since ICEbis 
should be usable by other protocols than SIP, moving the text from the 
above sections would also require a slightly more generic term than 
"offer/answer".

Section 5
I haven't checked up to 5.4 this since I assume it was a pure cut&paste 
from 5245.
Section 5.5 refers to section 11 of draft-ietf-ice-rfc5245bis, shouldn't 
that be section 12?

BTW: Section 11 of draft-ietf-ice-rfc5245bis talks about Extensibility 
Considerations. Shouldn't some text from there go into this document, 
e.g. the text about the a=ice-options attribute?

Section 10
Again I think this text belongs to draft-ietf-ice-rfc5245bis.




Editorial

Global

There is some variety how SDP attributes are written in the text.
I found
"There will be a candidate attribute for each candidate... "
"... it MUST include an "a=ice-lite" session-level attribute ..."
"... the "a=ice-options:ice2" SDP line ..."
You might want to consider doing some harmonization.

Similar with "offer", "answer", "SDP offer", "SDP answer"


Section 1
consider adding articles in first sentence (ditto in the Abstract)

old
.. is used with Session Description Protocol (SDP) offer/answer
    [RFC3264] and Session Initiation Protocol (SIP).
new
  ... is used with the Session Description Protocol (SDP) offer/answer
    [RFC3264] and the Session Initiation Protocol (SIP).

consider clarifying the following
old
     Note that ICE is not intended for NAT traversal for SIP, which is
     assumed to be provided via another mechanism [RFC5626].

new
     Note that ICE is only intended for NAT traversal of UDP-based 
multimedia
     and not intended for NAT traversal of SIP messages, which is
     assumed to be provided via another mechanism [RFC5626].


Section 2
The following reads a bit awkward.
old
     For the RTCP component, it is in the rtcp
       attribute when present, and when not present, the IP address is in
       the "c=" line and 1 plus the port is in the "m=" line.
new
For the RTCP component, it is in the rtcp
       attribute when present, and when not present, it is the same 
address and
    the next higher port number of the RTP candidate


Section 3

missing comma in last sentence, unnecessary article

old
     ... from the [ICE-BIS] respectively.
new
     ... from [ICE-BIS], respectively.

Section 4.1.1

could be misleading
old
        The offerer shall follow the procedures defined in section 4 of
    [ICE-BIS] to gather, prioritize and eliminate the redundant
    candidates.

new
        The offerer shall follow the procedures defined in section 4 of
    [ICE-BIS] to gather and prioritize candidates and to eliminate the 
redundant
    candidates.

section 4.1.1.1, 4.1.5

Why all caps for " DEFAULT DESTINATION" ?
Section 2 defines "Default Destination"


Section 4.1.1.2, 1st para
old
     The process of encoding the SDP is identical between full and lite
    implementations.
new
     Section 4.1.1.2
     The process of encoding the SDP is identical between full and lite
    implementations, except for including the "a=ice-lite" attribute.

    Alternatively, you could also consider removing that sentence since 
the 4th para gives explicit instructions.

Section 4.1.1.2, 5th para
s/compliancy/compliance/
s/to the [RFC5245]/to [RFC5245]

Section 4.1.1.2, 7th para
s/if RTCP candidate is present/if a RTCP candidate is present/


Section 4.1.1.2, 1st para
s/The answerer shall then follow/The answerer SHALL then follow/

Section 4.1.2.3, 1st bullet item
Old
The agent MUST follow the rules of section 8 of [ICE-BIS] ...
new
The agent MUST follow the rules of section 9 of [ICE-BIS] ...

You might want to consider referring to section 11.2.2 that gives the 
motivation for these procedures.
The same reference is already in the corresponding section 4.1.2.1 for 
the answerer.

Section 4.1.3 3rd para
    If the offerer had included the "ice2" ICE Option in the offer and
    the SDP answer also includes a similar session level ICE option, then
    the peers are [ICE-BIS] complaint implementations.

    s/a similar/the same/
    s/complaint/compliant/

Section 5
I haven't checked up to 5.4 this since I assume it was a pure cut&paste 
from 5245.
Section 5.5 refers to section 11 of ICEbis, shouldn't that be section 12?

BTW: Section 11 of ICEbis talks about Extensibility Considerations. 
Shouldn't some text from there go into this document, e.g. the text 
about the a=ice-options attribute?

Section 8.2
[RFC5768]  misses a hyperlink.
Section 8.4
Mentioning the RFC number twice like in "... RFC 3312 [RFC3312] ..." 
looks awkward,
found also in other places of the document.

Section 9
Is this still necessary since already RFC5245 deprecated ANAT?
If still necessary this history should be somehow reflected by 
rephrasing the content accordingly.

Section 12
    Contact Name:  Jonathan Rosenberg, jdrosen@jdrosen.net.
Is this still appropriate?

Section 12.2
draft-ietf-mmusic-rfc4566bis-17 does the IANA registering in a more 
formal way.
There are drafts that already adhere to this, e.g. 
draft-ietf-mmusic-trickle-ice-sip and 
draft-ietf-mmusic-sdp-bundle-negotiation. Shouldn't this document do the 
same for the ice2 option?




Regards

Thomas


From nobody Mon Oct 10 01:37:24 2016
Return-Path: <magnus.westerlund@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 BA6CF1294B4 for <mmusic@ietfa.amsl.com>; Mon, 10 Oct 2016 01:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 P0PpaYxr9CI8 for <mmusic@ietfa.amsl.com>; Mon, 10 Oct 2016 01:37:20 -0700 (PDT)
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 38BA2129455 for <mmusic@ietf.org>; Mon, 10 Oct 2016 01:37:20 -0700 (PDT)
X-AuditID: c1b4fb3a-aa3ff7000000099a-00-57fb533ecb04
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by  (Symantec Mail Security) with SMTP id C9.77.02458.E335BF75; Mon, 10 Oct 2016 10:37:18 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.83) with Microsoft SMTP Server id 14.3.319.2; Mon, 10 Oct 2016 10:37:17 +0200
To: Jonathan Lennox <jonathan@vidyo.com>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com> <FEB4A43F-B38F-43C3-A3D7-345C97AC73DC@vidyo.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <6dce0cc5-ff98-4099-c81b-35d5550a34bc@ericsson.com>
Date: Mon, 10 Oct 2016 10:37:16 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <FEB4A43F-B38F-43C3-A3D7-345C97AC73DC@vidyo.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOLMWRmVeSWpSXmKPExsUyM2J7oK5d8O9wg+aXyhYf1v9gtNi/+Dyz xdTlj1ksVmw4wOrA4vH3/QcmjyVLfjJ5XD7/kdGj7dkd9gCWKC6blNSczLLUIn27BK6MjuXV BevdKro3+jcw3rbsYuTkkBAwkWhcc5ypi5GLQ0hgPaPE1DO7WSCc5YwS+7acYuti5OAQFsiX mD6lDqRBREBD4uKzD2wQNV1MEg1X1zGDOMwCMxklVl/rYQSpYhOwkLj5oxGsmVfAXuLfXU2Q MIuAqsSSAzvBSkQFYiSuP3vEBmLzCghKnJz5hAXE5hSwlbi7ZztYnBlozMz55xkhbHmJ5q2z mUFsIQFtiYamDtYJjAKzkLTPQtIyC0nLAkbmVYyixanFxbnpRkZ6qUWZycXF+Xl6eaklmxiB wXtwy2+rHYwHnzseYhTgYFTi4V3Q+itciDWxrLgy9xCjBAezkggvb8DvcCHelMTKqtSi/Pii 0pzU4kOM0hwsSuK8ZivvhwsJpCeWpGanphakFsFkmTg4pRoY59nf1P0llPjzJUdNYOmlFVmi ffx6XxhurdiTGZD2tneWYerqjc9KkhrPFOR8dDg0+2fSnOg5sq+vT14XPPFMneLE3nBrt1Ib LsOGoF9Xiyuvpy89zWCYYnaqx7VpmxH/t+Dpl3Tqr+hzNehYOL3cvohr3eN/M49KMNydlW9x r0JUcsGf/gAbJZbijERDLeai4kQA72nEwVoCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/D5pobbDMp87aVO6BVwnoq1QYXDk>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, mmusic <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 10 Oct 2016 08:37:23 -0000

Den 2016-10-07 kl. 15:32, skrev Jonathan Lennox:
>
>> On Oct 7, 2016, at 4:41 AM, Magnus Westerlund
>> <magnus.westerlund@ericsson.com
>> <mailto:magnus.westerlund@ericsson.com>> wrote:
>>
>> Den 2016-10-06 kl. 23:59, skrev Cullen Jennings:
>>>
>>> I'm not getting the problem here and mandating 6904 is not an easy
>>> thing to do.
>>
>> So, lets be clear on what I have proposed. For bundle in general it is
>> RECOMMENDED to encrypt MIDs in RTP header extensions. I have also
>> proposed that for RTCWeb implementation and use should be mandated. I
>> was not clear in what applies when an WebRTC endpoint talks to a
>> legacy endpoint what is expected here. I guess this is the thorny issue.
>
> RFC 7904 (SDES header extensions) says:
>
>    In RTP sessions where any type of confidentiality protection is
>    enabled for RTCP, the SDES item header extensions MUST also be
>    protected.  This implies that to provide confidentiality, users of
>    the Secure Real-time Transport Protocol (SRTP) need to implement and
>    use encrypted header extensions per [RFC6904 <https://tools.ietf.org/html/rfc6904>].
>
>
> This was after a fair bit of back-and-forth with the security ADs.  MID
> is a 7904 header extension, so I donâ€™t think BUNDLE can override this MUST.
>

Okay, forgot about that requirement. However, I don't think that really 
contradicts what was written. The proposed text recommends use of 
encryption of RTCP. RFC7904 mandates that if RTCP is encrypted then RTP 
header extension must also be encrypted. There should be a reference to 
this requirement in the text below, so I will update the text proposal.


The identfication-tag when included in the RTP MID SDES item, 
independent of transport, RTCP SDES packet or RTP header extension, can 
expose the value to parties beyond the signaling chain. Therefore, the 
identification-tag MUST NOT contain any user related information. 
However, the implementation's method for generating identfication-tags 
combined with hardware configuration can enable fingerprinting of the 
endpoint device and thus its user. As the identification-tag is also 
used to route the media stream to the right application functionality it 
is also important that the value received is the one intended by the 
sender, thus integrity and the authenticity of the source are important 
to prevent denial of service on the application. At least to prevent 
third parties from modifying the identification-tag value.

Due to the security risks associated with the MID values in RTP and RTCP 
it is RECOMMENDED that the MID SDES item is confidentiality protected as 
well as source authenticated. The SDES RTP header extensions [RFC7904] 
requires encryption of the header extension in cases when the RTCP 
encrypts the SDES item. The security mechanisms used SHALL provide 
corresponding levels of security for both RTP header extensions and 
RTCP. Confidentiality mechanisms for RTP/RTCP are discussed in Options 
for Securing RTP Sessions [RFC7201], for example SRTP [RFC3711] with 
SRTCP encryption enabled combined with [RFC6904] can provide the 
necessary security functions.

>
>>> I'm not getting what the issue is here. If mid are random, or are
>>> just a count of n'th m-line in the sdp, what is the problem with
>>> exposing them to people are getting the media?
>>
>> The issue is that these identifiers are going from having only been
>> visiable in the signalling messages to be visible also on the RTP
>> media plane. And without RFC6904 even if one uses SRTP, these values
>> are exposed. This have several different effects as I see it. So if
>> the generation algorithm are not strictly defined, the implementation
>> gets possible to fingerprint. In addition the device gets to be
>> fingerprinted based on the number of streams offered and their
>> identifiers. Thus, it is not only what is actually used that is
>> exposed, but what was originally offered, i.e. the full offer leaks
>> into unencrypted domain on the media plane. Note, this later can't be
>> dealt with any mid id creation rules, it will still leak. Thus devices
>> that have more exotic configurations when it comes to media streams,
>> i.e. number of cameras etc this can still be fingerprinted by passive
>> attacks from third parties.
>>
>> It is the passive attack from third parties that has me worried here.
>> A peer in the signalling has massively more powerful fingerprinting,
>> but that requires one to be in the signalling context, not passively
>> observe traffic that goes past.
>>
>>
>> Cheers
>>
>> Magnus
>>
>>
>>>
>>>
>>>
>>>> On Oct 6, 2016, at 7:39 AM, Magnus Westerlund
>>>> <magnus.westerlund@ericsson.com
>>>> <mailto:magnus.westerlund@ericsson.com>> wrote:
>>>>
>>>> Den 2016-10-06 kl. 14:49, skrev Christer Holmberg:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Magnus suggested usage of RFC 6904 for encryption of the RTP SDES
>>>>> header extension for MID. I guess it would be a SHUOLD?
>>>>>
>>>>> In addition, we would say that a corresponding level of security
>>>>> must be applied to the RTP SDES header extension for MID and to
>>>>> the RTCP SDES MID item.
>>>>>
>>>>> Any opinions?
>>>>
>>>> I think this is fine solution to this issue. I would probably
>>>> formulate the security considerations like this.
>>>>
>>>> The identfication-tag when included in the RTP MID SDES item,
>>>> independent of transport, RTCP SDES packet or RTP header extension,
>>>> can expose the value to parties beyond the signaling chain.
>>>> Therefore, the identification-tag MUST NOT contain any user related
>>>> information. However, the implementation's method for generating
>>>> identfication-tags combined with hardware configuration can enable
>>>> fingerprinting of the endpoint device and thus its user. As the
>>>> identification-tag is also used to route the media stream to the
>>>> right application functionality it is also important that the value
>>>> received is the one intended by the sender, thus integrity and the
>>>> authenticity of the source are important to prevent denial of
>>>> service on the application. At least to prevent third parties from
>>>> modifying the identification-tag value.
>>>>
>>>> Due to the security risks associated with the MID values in RTP and
>>>> RTCP it is strongly RECOMMENDED that the MID SDES item is both
>>>> confidentiality protected as well as source authenticated when
>>>> transported in either RTCP or RTP header extensions. The security
>>>> mechanisms used SHALL provide corresponding levels of security for
>>>> both RTP header extensions and RTCP. Confidentiality mechanisms for
>>>> RTP/RTCP are discussed in Options for Securing RTP Sessions
>>>> [RFC7201], for example SRTP [RFC3711] with SRTCP encryption enabled
>>>> combined with [RFC6904] can provide the necessary security
>>>> functions.
>>>>
>>>>
>>>> Cheers
>>>>
>>>> Magnus Westerlund
>>>>
>>>> ----------------------------------------------------------------------
>>>>
>>>>
>> Services, Media and Network features, Ericsson Research EAB/TXM
>>>> ----------------------------------------------------------------------
>>>>
>>>>
>> Ericsson AB                 | Phone  +46 10 7148287
>>>> FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079 SE-164 80
>>>> Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>>>> <mailto:magnus.westerlund@ericsson.com>
>>>> ----------------------------------------------------------------------
>>>>
>>>>
>>>>
>> _______________________________________________
>>>> mmusic mailing list mmusic@ietf.org <mailto:mmusic@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>
>>>
>>
>>
>> --
>>
>> Magnus Westerlund
>>
>> ----------------------------------------------------------------------
>> Services, Media and Network features, Ericsson Research EAB/TXM
>> ----------------------------------------------------------------------
>> Ericsson AB                 | Phone  +46 10 7148287
>> FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>> <mailto:magnus.westerlund@ericsson.com>
>> ----------------------------------------------------------------------
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org <mailto:mmusic@ietf.org>
>> https://www.ietf.org/mailman/listinfo/mmusic
>


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Mon Oct 10 01:48:57 2016
Return-Path: <magnus.westerlund@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 899A21295F9 for <mmusic@ietfa.amsl.com>; Mon, 10 Oct 2016 01:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 kALszEvFKSGS for <mmusic@ietfa.amsl.com>; Mon, 10 Oct 2016 01:48:55 -0700 (PDT)
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 B0D601294B2 for <mmusic@ietf.org>; Mon, 10 Oct 2016 01:48:54 -0700 (PDT)
X-AuditID: c1b4fb30-b73ff70000000cb2-ba-57fb55f484ce
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by  (Symantec Mail Security) with SMTP id C8.59.03250.4F55BF75; Mon, 10 Oct 2016 10:48:53 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.68) with Microsoft SMTP Server id 14.3.319.2; Mon, 10 Oct 2016 10:48:51 +0200
To: Eric Rescorla <ekr@rtfm.com>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com> <CABcZeBOkj908hNQqGMrP0DvStXPW5EpgMeYDkCTa68O9uBC8-Q@mail.gmail.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <8bbd0b10-00a4-d360-adc5-dadeed80df19@ericsson.com>
Date: Mon, 10 Oct 2016 10:48:50 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBOkj908hNQqGMrP0DvStXPW5EpgMeYDkCTa68O9uBC8-Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM2K7k+7X0N/hBkfWc1qseH2O3eLD+h+M FlOXP2axWLHhAKsDi8ff9x+YPJYs+cnkcfn8R0aPyY/bmANYorhsUlJzMstSi/TtErgyjt58 yFQwQbBi0+Mm9gbGm7xdjJwcEgImErf+rmHsYuTiEBJYzyjxf3YzO0hCSGA5o0TnVq0uRg4O YYF8ielT6kDCIgIKEr/+nGCBqJ/HJLGoYzsziMMssIxR4trei4wgVWwCFhI3fzSygdi8AvYS E6fsYQaxWQRUJS59eA4WFxWIkbj+7BFUjaDEyZlPWEBsToFAiTtzjjCB2MxAc2bOP88IYctL NG+dzQxxnLZEQ1MH6wRGgVlI2mchaZmFpGUBI/MqRtHi1OKk3HQjI73Uoszk4uL8PL281JJN jMAAPrjlt8EOxpfPHQ8xCnAwKvHwLmj9FS7EmlhWXJl7iFGCg1lJhHdPyO9wId6UxMqq1KL8 +KLSnNTiQ4zSHCxK4rxmK++HCwmkJ5akZqemFqQWwWSZODilGhhDewXLtT0mxEq8OXd4AfOb gsXlAb/08lS+GC9IffNKq/v+yw8Ne28cX+YoozVb6vGDghUz5jvVOrlmyCXNVJL4aHBP3ywg 4dgdt1kJ9nuz032W3OctV2KrXFLQmb490/SNgZNGM4/474lJ3WLZbtPL4x77z1j1fj3v0ta+ RZGV0jxf5555sFmJpTgj0VCLuag4EQBDZyzJXAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/_TdANbawPz08JNWM0v0h32uG3n4>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 10 Oct 2016 08:48:56 -0000

Den 2016-10-07 kl. 20:33, skrev Eric Rescorla:
> ISTM that there are two risks:
> 1. That people might use structured RIDs, MIDs, etc. and that that will
> leak a lot of information about
> 2. That just the structure of the media streams is a fingerprinting risk.
>
> The first of these seems addressable by guidance about how to construct
> these IDs. I note that we
> have only very limited guidance on how to construct ICE
> ufrag/passwords....

So, the difference here from stuff that normally exists in SDP is that 
it goes in many RTP packets in the clear compared to only over the 
signaling path. The ICE ufrag is in that sense equivalent as that is 
also sent in the clear and in all ICE connectivity checks.


The second seems
> not that interesting as I bet you can get a lot by other metadata
> (packet size, PT, etc).

Well, yes there are some other leakages. However, we don't need to 
increase the exposure, just because there are shortcomings today.

So lets review what the current proposal is:

1. Bundle RECOMMENDS encryption of the MID values, do you think that is 
unnecessary? Should we have no recommendation about confidentiality 
protection at all?

2. The above point is not relevant in a WebRTC perspective. In WebRTC we 
already have mandated encryption of RTCP. Thus, RFC 7904 mandates that 
we also encrypt the MID RTP header extension. Thus, for WebRTC we 
already have a result, that is not possible to change without revising 
RFC 7904 and argue that the conclusion there is wrong, which I don't 
think it is. If we protect information RTCP, it should be protected also 
in RTP headers.

So, anything you like to change here?

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Mon Oct 10 14:20:29 2016
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 647911295B0 for <mmusic@ietfa.amsl.com>; Mon, 10 Oct 2016 14:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5] 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 5lCmvreFHM3t for <mmusic@ietfa.amsl.com>; Mon, 10 Oct 2016 14:20:26 -0700 (PDT)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 9F01F129550 for <mmusic@ietf.org>; Mon, 10 Oct 2016 14:20:26 -0700 (PDT)
Received: by mail-it0-x230.google.com with SMTP id e203so25896526itc.0 for <mmusic@ietf.org>; Mon, 10 Oct 2016 14:20:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iV3dl045seZ72qAzcKWsrbt8Wa5R0/xrYFchRvC3xkM=; b=aJ3j2xAd/1m8ysyuz6HabdcZHYOi0Z83rtO0K1aW21V74AHg1l6EvfICfLVu678zJu llbTXWoggQjol6Y7d08aJu7OsSrYDNhB+6/dudjqRvHYzoPCdi2TRN9pp2zc4580OmbV LExvjBqKBPBmcuARqWppTxt/+eSAqW9FF5KMx5z2s+9zLmOLgduuG0JEwbtJgxzt2NyZ tgAMPnLredLinVPVMm8qgQc/2/qhPnVZWtgdAEW4hCKBjHMQHkC017jmeRYbM4L5yZff dAt4mPrVdN1dM9AyD29xLNpIfUPiWXSPY93+/33memr/E5sInprwj2HfUTz6k36R+1rz K9GQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iV3dl045seZ72qAzcKWsrbt8Wa5R0/xrYFchRvC3xkM=; b=Oz3F+sIEwcYi789q5BnTA9hF2EuVwoqoSkoanP5lN9Q0vN4ODq6YGf4NRTtdj1W/M3 0ogczL0dK5qLaWoo5SCCTcOJ1CySsLLNuQziDHLd5m7HHfknSwV0WYAWmJbxu/dtAuOg w+wqWpkPmeCAPSbZ8i0LJr1jhmK9z4N1Vsm+DaE6zaKqW8WJI7VH2VSmVNJXne/ebwhm WcG1Iw7QFeMoFvR7LGN9a3Okw7R7RLjo3qU3zgYKKmHunZLVKqzM+rsJqmd7we0BMCSt MpafubppKVNszYTQWp4KaC2BIHNP3DTaOnSm9ZwP1aNe+nqaQfwH1J749SLiIM9VVCPt xH+Q==
X-Gm-Message-State: AA6/9RlD7FPLssLlwR2PIcETH1slUVUha5i+8WYf91paP18rF9kxsDP6RGxOyfAXpnqVTg==
X-Received: by 10.36.68.65 with SMTP id o62mr1338787ita.82.1476134425939; Mon, 10 Oct 2016 14:20:25 -0700 (PDT)
Received: from mail-io0-f176.google.com (mail-io0-f176.google.com. [209.85.223.176]) by smtp.gmail.com with ESMTPSA id c36sm223648itd.2.2016.10.10.14.20.25 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Oct 2016 14:20:25 -0700 (PDT)
Received: by mail-io0-f176.google.com with SMTP id r30so6024794ioi.1 for <mmusic@ietf.org>; Mon, 10 Oct 2016 14:20:25 -0700 (PDT)
X-Received: by 10.107.163.72 with SMTP id m69mr1362940ioe.106.1476134424923; Mon, 10 Oct 2016 14:20:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.110.18 with HTTP; Mon, 10 Oct 2016 14:20:24 -0700 (PDT)
In-Reply-To: <fdaa941a-8143-8caf-7feb-3ea6c37c837d@gmail.com>
References: <fdaa941a-8143-8caf-7feb-3ea6c37c837d@gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Mon, 10 Oct 2016 17:20:24 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtjY1fSr93YNs2OuhX8w-qnqiRSoLXWG6OGbKQ=91G=yw@mail.gmail.com>
Message-ID: <CAD5OKxtjY1fSr93YNs2OuhX8w-qnqiRSoLXWG6OGbKQ=91G=yw@mail.gmail.com>
To: Thomas Stach <thomass.stach@gmail.com>
Content-Type: multipart/alternative; boundary=001a1140e8180a05d5053e8954c9
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/mOxwTH8ChQ_3P2xc-5TcArqoG1s>
Cc: MMUSIC <mmusic@ietf.org>, draft-ietf-mmusic-ice-sip-sdp@tools.ietf.org
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-ice-sip-sdp
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 10 Oct 2016 21:20:28 -0000

--001a1140e8180a05d5053e8954c9
Content-Type: text/plain; charset=UTF-8

On Mon, Oct 10, 2016 at 4:11 AM, Thomas Stach <thomass.stach@gmail.com>
wrote:

> - There has been a lot of discussion about the updated offer.
>   Is it the rough(?) consensus of the WG that it is still required?
>   Note that for BUNDLE, which has similar issues, this requirement was
> removed.
>


I would prefer this update offer removed or at least indicate that this
update offer is not needed.

Regards,
_____________
Roman Shpount

--001a1140e8180a05d5053e8954c9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Oct 10, 2016 at 4:11 AM, Thomas Stach <span dir=3D"ltr">&lt;<a href=3D"=
mailto:thomass.stach@gmail.com" target=3D"_blank">thomass.stach@gmail.com</=
a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">-=
 There has been a lot of discussion about the updated offer.<br>
=C2=A0 Is it the rough(?) consensus of the WG that it is still required?<br=
>
=C2=A0 Note that for BUNDLE, which has similar issues, this requirement was=
 removed.<br></blockquote><div><br></div><div><br></div>I would prefer this=
 update offer removed or at least indicate that this update offer is not ne=
eded.</div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">=
Regards,<div class=3D"gmail_extra"><div><div class=3D"gmail_signature">____=
_________<br>Roman Shpount</div></div></div><div>=C2=A0</div></div></div></=
div>

--001a1140e8180a05d5053e8954c9--


From nobody Mon Oct 10 14:48:50 2016
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 5BC32129794 for <mmusic@ietfa.amsl.com>; Mon, 10 Oct 2016 14:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 ieCpGbN-xqeB for <mmusic@ietfa.amsl.com>; Mon, 10 Oct 2016 14:48:47 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3018D129793 for <mmusic@ietf.org>; Mon, 10 Oct 2016 14:48:47 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id z65so5515733itc.0 for <mmusic@ietf.org>; Mon, 10 Oct 2016 14:48:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KA33oKVT/7vjC8aDgKh1vj4wo64pAHb6lXiqaePCwAI=; b=YPpHhQF9BbZleOL1u69yUS6bHKWaX+XAVerwCdf5qvK4ku7pstjXudrkt2P4VsjkEA rKWjM49XPgzOpxOqpzPXjURl52PxB/5TTqU4DMHQh7NEXQ8LX9/bpS+GLsfJcFYY47/b Rv1OpbwE5U0ZWFoA6idULf4LtSyjJJ8k2K27RWxd/Yvl7MsySzcYwEm4qI1p60ZHveQB PvppPYOAafZfszzZSh7b37xzRaR72IIAZ4hhi7WV5hFI9JjP0N1F89q4KJMVsFBFKI8x vyV8Dmn55kO6rXDtPhceaEnjxT4WhM2JTJgbx8XgrcabU8J5PRWc5W/XIlRfzHxmpCDU gIaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KA33oKVT/7vjC8aDgKh1vj4wo64pAHb6lXiqaePCwAI=; b=Nfgg7iwBsghVVhoV0UiAvig12+BThh1vP7/TcrC6y7a9lZ4wa0qzbuIbXzDW1OJhcE k+sVp9RRbTahw6y3FxRkiu75UBpF/UQ3HMur5jDAc8YhTket/IM54Cww9zSfig5n3hAu UtANQj/2kLPyF7f81HCBH/vcYEQ8BhjtLOsmpeHfDQC2uvGXYSQb1Wmnb1i1M7VifcfX lD+1Yqmbo6LKhPbGsK0ZXdUZLVzpEAkkp3AEG2HhBL0iy2mW2btE0vpo7SrlEjHCT3fn sU484lIO9NIVXR+muKupGG+Eu3uw+ofu4oSGL7FioVTSgInwaMRRlWPJQ/KyEFeYUDel JPYw==
X-Gm-Message-State: AA6/9RmqsDGA3HntrufhZzCKveyCqGmeSY/x5PY8l6kXp6xXtVBBdwl2jY/86iyGaRJIGA==
X-Received: by 10.36.213.196 with SMTP id a187mr13179292itg.63.1476136126077;  Mon, 10 Oct 2016 14:48:46 -0700 (PDT)
Received: from mail-it0-f49.google.com (mail-it0-f49.google.com. [209.85.214.49]) by smtp.gmail.com with ESMTPSA id b133sm249398iti.14.2016.10.10.14.48.45 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Oct 2016 14:48:45 -0700 (PDT)
Received: by mail-it0-f49.google.com with SMTP id 189so15049623ity.1 for <mmusic@ietf.org>; Mon, 10 Oct 2016 14:48:45 -0700 (PDT)
X-Received: by 10.36.238.134 with SMTP id b128mr1536170iti.72.1476136125122; Mon, 10 Oct 2016 14:48:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.110.18 with HTTP; Mon, 10 Oct 2016 14:48:44 -0700 (PDT)
In-Reply-To: <CABkgnnXL7dBvpqVD+nEoG8F-+xahDwgu+0GXKGbxRQuZsoKesA@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B4BD3D963@ESESSMB209.ericsson.se> <CABkgnnXL7dBvpqVD+nEoG8F-+xahDwgu+0GXKGbxRQuZsoKesA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Mon, 10 Oct 2016 17:48:44 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtUrTCp=F=-P9cfZw6Z3PQkYr8DPmrDMuu4JR8J4s5ZpQ@mail.gmail.com>
Message-ID: <CAD5OKxtUrTCp=F=-P9cfZw6Z3PQkYr8DPmrDMuu4JR8J4s5ZpQ@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>,  Christer Holmberg <christer.holmberg@ericsson.com>, Cullen Jennings <fluffy@iii.ca>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=f403045c0e5660cf7e053e89b9c2
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/s8SmqvZdT7JydUgcw_NldS20cZE>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-4572-update: Pull request to remove update of preferred cipher
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 10 Oct 2016 21:48:48 -0000

--f403045c0e5660cf7e053e89b9c2
Content-Type: text/plain; charset=UTF-8

Just to add an observation regarding current implementations:

1. Most implementations already use SHA-256 or will accept it.
2. A lot of implementations will fail to establish a connection if they
receive an SDP with multiple fingerprints
3. Hash function match between certificate and fingerprint is irrelevant. I
am not aware of anybody checking this.

Based on this, a lot, if not most of the implementations will need to be
updated to be compatible with 4572 with multiple fingerprints.  This new
draft simply clarifies this point, since it is not a new requirement. It
also clarifies how multiple fingerprints should be generated and matched.
Additional code required to support SHA-256 is typically already present in
the existing implementations so will require trivial amount of effort to
implement.

Bottom line, we have a lot of theoretical problems with backwards
compatibility related to which hashes are used to create the fingerprint
which actually do not exist in practice. On the other hand we have one real
problem: will remote end point accept multiple fingerprints or not? While
we are are spinning our wheels about solving problems that are not there,
the only way to make sure multiple fingerprints are supported is to do a
version check on remote end point. Since I am doing version checks anyway,
and since I consider not supporting multiple fingerprints a bug, I can live
with the new draft with or without SHA-256.

If you consider version checks evil, then draft needs to be updated to
indicate that multiple fingerprints are supported or to use different
attribute to provide multiple fingerprints. Since this is very late in the
process I prefer to release the current document.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr">Just to add an observation regarding current implementatio=
ns:<div><br></div><div>1. Most implementations already use SHA-256 or will =
accept it.</div><div>2. A lot of implementations will fail to establish a c=
onnection if they receive an SDP with multiple fingerprints</div><div>3. Ha=
sh function match between certificate and fingerprint is irrelevant. I am n=
ot aware of anybody checking this.<br><div class=3D"gmail_extra"><br></div>=
<div class=3D"gmail_extra">Based on this, a lot, if not most of the impleme=
ntations will need to be updated to be compatible with 4572 with multiple f=
ingerprints.=C2=A0 This new draft simply clarifies this point, since it is =
not a new requirement. It also clarifies how multiple fingerprints should b=
e generated and matched. Additional code required to support SHA-256 is typ=
ically already present in the existing implementations so will require triv=
ial amount of effort to implement.</div><div class=3D"gmail_extra"><br></di=
v><div class=3D"gmail_extra">Bottom line, we have a lot of theoretical prob=
lems with backwards compatibility related to which hashes are used to creat=
e the fingerprint which actually do not exist in practice. On the other han=
d we have one real problem: will remote end point accept multiple fingerpri=
nts or not? While we are are spinning our wheels about solving problems tha=
t are not there, the only way to make sure multiple fingerprints are suppor=
ted is to do a version check on remote end point. Since I am doing version =
checks anyway, and since I consider not supporting multiple fingerprints a =
bug, I can live with the new draft with or without SHA-256.</div><div class=
=3D"gmail_extra"><br></div><div class=3D"gmail_extra">If you consider versi=
on checks evil, then draft needs to be updated to indicate that multiple fi=
ngerprints are supported or to use different attribute to provide multiple =
fingerprints. Since this is very late in the process I prefer to release th=
e current document.</div><div class=3D"gmail_extra"><br></div><div class=3D=
"gmail_extra">Regards,<br clear=3D"all"><div><div class=3D"gmail_signature"=
 data-smartmail=3D"gmail_signature">_____________<br>Roman Shpount</div></d=
iv></div></div></div>

--f403045c0e5660cf7e053e89b9c2--


From nobody Mon Oct 10 23:58:44 2016
Return-Path: <thomass.stach@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 B575612945A for <mmusic@ietfa.amsl.com>; Mon, 10 Oct 2016 23:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 Q6CnI12IESTd for <mmusic@ietfa.amsl.com>; Mon, 10 Oct 2016 23:58:40 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (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 20299129487 for <mmusic@ietf.org>; Mon, 10 Oct 2016 23:58:40 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id b75so25663905lfg.3 for <mmusic@ietf.org>; Mon, 10 Oct 2016 23:58:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=4qSdehtDummvAknCKUEb3NQv2QLzkePjyZxVd88iZec=; b=JnHMv7Ygt91s3xMhUApexCQiirblFCP+IfZqtCHKckwUyboGSL1OZkXMhYBfBhBF1L I6Ah+AIhEBbql2mJa7SxQ9J0HTcaNIW4/e0ArRCaoJusmZQnY03RmgF6ed4DvjAUUENU cyvfgQfIB1S3qpEb0sCb0RylSa0ZqbwPjCV/gwCk9QvEksvSYewsXcqdXPo3QWyb0qx/ MZ/SZn5sQUMn2SIibZm6kBdihGs4OzbGtkgzuVzlKz4eQ+Zr1uuw/VkwlJ6z5GIL1wDK wcNAmPyI6cBWDMtQT0qFOMuQK37StPze78JAVJRHBlF18/r00KE0ni8vDvAKIQv3e7O9 UIog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=4qSdehtDummvAknCKUEb3NQv2QLzkePjyZxVd88iZec=; b=dWVpcbjeKaJNTmkxTEDbjHf44E9zcSczH4TC28E+J2nE12jRbEtJ2eaRmfiZjTQzPD Rr6s08aJIknoBRzM5TMXNBpWA22FmSy47yAl6wT/stbINXKVa5P4/2AJoQ2FF5zCzcF0 Qu9LoHvjgBby11HKvKttPGqqvPbKw3VWMG7T/OvtwSm1LiB9pHZFYpBAxS7KQAHUPP9A 2ZWBZFsULe/b09M3c/5LVCSYkpbxZ/vABGwMF785BkJvgJc5deZqNvlMJ+RXAHD/+QiZ 1eo4ZepPpWz/sTrS4yntAD28m5vC1JZtkbj18rbx0RUcCIB/VLRr/gVbQ9ukPZI49RGz 2/mA==
X-Gm-Message-State: AA6/9RmBUKROuXu1hMi1lWknTAQhmhwLsSGK45rP1eFe+z44ggY/JN73+VN9PCPmftxMHQ==
X-Received: by 10.25.150.84 with SMTP id y81mr1340226lfd.26.1476169118034; Mon, 10 Oct 2016 23:58:38 -0700 (PDT)
Received: from [192.168.2.111] (d91-130-16-98.cust.tele2.at. [91.130.16.98]) by smtp.googlemail.com with ESMTPSA id 15sm336829ljf.5.2016.10.10.23.58.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Oct 2016 23:58:37 -0700 (PDT)
From: Thomas Stach <thomass.stach@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <D41AC393.10727%christer.holmberg@ericsson.com> <bc713d1a-acdb-af95-5391-b3e244e1126d@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1B3B2@ESESSMB209.ericsson.se>
Message-ID: <e44e62ff-1b0d-9180-2872-b98c84cbb6f6@gmail.com>
Date: Tue, 11 Oct 2016 08:58:36 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD1B3B2@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/0ecct0BpwCN2QDbrZysszG0sFEs>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2016 06:58:43 -0000

Christer,



On 2016-10-05 16:56, Christer Holmberg wrote:
> Hi,
>
>> I took the liberty to adjust the subject since the cited text is is from draft-ietf-mmusic-trickle-ice-sip-05,
>> not from draft-ietf-mmusic-ice-sip-sdp.
> Thanks!
>
>>> It has been suggested that removal of candidates should not be part of
>>> trickle, but rather be defined in a separate future extension draft.
>>> The comments below are based on that such "extension" may exist at
>>> some point.
>>>
>>> The text in section 4.2 says:
>>>      "In every INFO request agents MUST include all local candidates they
>>>      have signaled previously.  This is necessary in order to more easily
>>>      avoid problems that would arise from unreliable transports.  Mis-
>>>      ordering can be detected through the CSeq: header field in the INFO
>>>      request.  As a consequence candidates cannot be removed unless an ICE
>>>      restart is performed.  Note that extension might be specified in the
>>>      future that enable such removal without a restart."
>>> Q1: Assuming someone does define an extension which allows removal of
>>> candidates without a restart, do such candidates still have to be
>>> included in the INFO, as they have been "previously signalled"?
>> This would have to clarified in that future extension document together with corresponding backward
>> compatibility issues and/or indication of support for such an extension. I don't want to do design here,
>> but a=ice-options might be something to look at.
> How you indicate support of such extension is outside the scope of this thread. I want to clarify the exact semantics of a candidate in an INFO.
>
>>> What is the scope of "previously"?
>> The current ICE generation (as defined by the currently used/exchanged ufrag/pwd)
>>> Previously since when?
>> Since current ufrag/pwd was signalled.
> Is that said anywhere?
Not explicitly, but provided that all INFOs MUST also include the 
current ufrag/pwd (see the preceding paragraph in that section), what 
other interpretation of "previously" would make sense?
> Also, an "extension" could have removed candidiates since the ufrag/pwd was signalled. So, you cannot simply say "since current ufrag/pwd was signalled". You also need to say something like "and are still active/in use", or something like that.
Why would I have to?
As long as we remain within the currently specified Trickle-ICE 
functionality, all candidates that where exchanged within the scope of 
the current ufrag/pwd
are "active/in use" in the sense of being subject to 
pairing/pruning/connectivity checking.
A potential  future extension would have to deal with such issues and 
provide appropriate text.
>
>>> Q2: What if an INFO does NOT contain a local candidate that has
>>> previously been signaled? Do we assume it has been removed using some
>>> "extension"? Do we assume it's still there?
>> We could either treat this case as an error and ignore the content of that INFO.
>> Probably not the best idea, e.g. in case that a=end-of-candidates was included.
>> Or we can assume (in absence of any "removal extension") that it is still there. That
>> would allow to still make use of any newly trickled candidates in such an INFO. This makes more sense to me.
>> If this is agreable I would be happy to put corresponding text into section 4.2.
> ...or, we could go back to my previous proposal, and say that we *ONLY* signal the new candidates, and that the INFO has no impact on any other candidates :)
Well, there is consensus since  2013 that the INFO carries all candidates.
It was one outcome of the thread that started here
https://mailarchive.ietf.org/arch/search/?email_list=mmusic&gbt=1&index=T7R18RumQQJrmtHRh1lmcf9wcqs 

I can't remember that this consensus was not challenged since then, but 
I guess that all implementations will expect all candidates in the INFO.
>
> Also, assuming all current candidates are present in INFOs, what about peer reflexive candidates? Will they be present in INFOs?
Actually there is no real need to put peer reflexive candidates into the 
INFO package since the ICE Agents learn them from the STUN checks.
However,  the current text does not preclude that you signal the peer 
reflexives redundantly in the INFO package.
Regards
Thomas
>
>>>> Q3: What if a candidate has bee removed using some "extension", and
>>>> then it still shows up in an INFO? Does it mean it's automatically
>>>> added back?
>>> This is probably the easiest way to deal with that, as it does not require housekeeping.
>>> But again I see this as something that the future extension document has to deal with.
> ...or, we could go back to my previous proposal, and say that we *ONLY* signal the new candidates, and that the INFO has no impact on any other candidates :)
>
> Regards,
>
> Christer
>
>
>


From nobody Tue Oct 11 00:39:35 2016
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 1D4D71297D0 for <mmusic@ietfa.amsl.com>; Tue, 11 Oct 2016 00:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 XfGD7ituSD5Y for <mmusic@ietfa.amsl.com>; Tue, 11 Oct 2016 00:39:22 -0700 (PDT)
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 899D21297DC for <mmusic@ietf.org>; Tue, 11 Oct 2016 00:39:22 -0700 (PDT)
X-AuditID: c1b4fb25-5405a9800000793b-3c-57fc9728092e
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by  (Symantec Mail Security) with SMTP id 52.48.31035.8279CF75; Tue, 11 Oct 2016 09:39:20 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0319.002; Tue, 11 Oct 2016 09:39:20 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Thomas Stach <thomass.stach@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
Thread-Index: AQHSHxIL5dxB//uBWky8GjwyA0+P66CZ76sAgAjKcACAAD99AA==
Date: Tue, 11 Oct 2016 07:39:19 +0000
Message-ID: <D4226F4E.10D4F%christer.holmberg@ericsson.com>
References: <D41AC393.10727%christer.holmberg@ericsson.com> <bc713d1a-acdb-af95-5391-b3e244e1126d@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1B3B2@ESESSMB209.ericsson.se> <e44e62ff-1b0d-9180-2872-b98c84cbb6f6@gmail.com>
In-Reply-To: <e44e62ff-1b0d-9180-2872-b98c84cbb6f6@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <DF51B42878C93745AE2D6E57BB992B1A@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGIsWRmVeSWpSXmKPExsUyM2K7hK7G9D/hBi8/mlpMXf6YxeLTia1M DkweO2fdZfdYsuQnUwBTFJdNSmpOZllqkb5dAlfGu6/X2Qp2GVRcf72MtYHxq1oXIyeHhICJ xKyfbexdjFwcQgLrGSWWXFjDBOEsYZS4dKqBpYuRg4NNwEKi+582SIOIQKDE5zPHwWqEBaYy Slw/3ccKkZjGKPF0qRWE7STxadt9JhCbRUBV4uWuFrAaXgFriceftrBBLHjKKDHl2E82kASn gK3Eld8HwBoYBcQkvp9aA2YzC4hL3HoynwniVAGJJXvOM0PYohIvH/8DGyoqoCfx/etsqLii xM6z7cwQvXoSN6ZOYYOwrSVet61igbC1JZYtfM0McZCgxMmZT1gmMIrNQrJuFpL2WUjaZyFp n4WkfQEj6ypG0eLU4qTcdCNjvdSizOTi4vw8vbzUkk2MwNg6uOW36g7Gy28cDzEKcDAq8fAq XP8dLsSaWFZcmXuIUYKDWUmE9/2UP+FCvCmJlVWpRfnxRaU5qcWHGKU5WJTEec1W3g8XEkhP LEnNTk0tSC2CyTJxcEo1MOZyG933mmc2Y42ZdP7/0gDTSIe9sq8vqS25xXR+AVPGp6SjZrVH NZWyL3+cnCCRc+Wsxxf9N+WLnU81JCd/SfiaqlB1c8m5awVvDGenac2RV/KNLX4ndbN3nfDd f1zVR7Ic3s70XHOAMUmbe+qnuC8qc/xSjuTPjr4Ss2BSidY3mwNl3BwSF5RYijMSDbWYi4oT AQhC1KCpAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/byJbRpCUFMn8JWMzhBRPBqhQhhg>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2016 07:39:32 -0000

Hi,

>>>>It has been suggested that removal of candidates should not be part of
>>>> trickle, but rather be defined in a separate future extension draft.
>>>> The comments below are based on that such "extension" may exist at
>>>> some point.
>>>>
>>>> The text in section 4.2 says:
>>>>      "In every INFO request agents MUST include all local candidates
>>>>they
>>>>      have signaled previously.  This is necessary in order to more
>>>>easily
>>>>      avoid problems that would arise from unreliable transports.  Mis-
>>>>      ordering can be detected through the CSeq: header field in the
>>>>INFO
>>>>      request.  As a consequence candidates cannot be removed unless
>>>>an ICE
>>>>      restart is performed.  Note that extension might be specified in
>>>>the
>>>>      future that enable such removal without a restart."
>>>> Q1: Assuming someone does define an extension which allows removal of
>>>> candidates without a restart, do such candidates still have to be
>>>> included in the INFO, as they have been "previously signalled"?
>>> This would have to clarified in that future extension document
>>>together with corresponding backward
>>> compatibility issues and/or indication of support for such an
>>>extension. I don't want to do design here,
>>> but a=3Dice-options might be something to look at.
>> How you indicate support of such extension is outside the scope of this
>>thread. I want to clarify the exact semantics of a candidate in an INFO.

Again, I agree that how candidates are removed is outside the scope. But,
that doesn=B9t change the fact that trickle needs to define exactly what th=
e
semantic of the signalled candidates. I do NOT want a future extension to
change that semantic.


>>>> What is the scope of "previously"?
>>> The current ICE generation (as defined by the currently used/exchanged
>>>ufrag/pwd)
>>>> Previously since when?
>>> Since current ufrag/pwd was signalled.
>> Is that said anywhere?
>Not explicitly, but provided that all INFOs MUST also include the
>current ufrag/pwd (see the preceding paragraph in that section), what
>other interpretation of "previously" would make sense?

I don=B9t know - we have to ask the implementers that have not been involve=
d
in the IETF work about that.

We shall not make assumptions that readers will interpret things in a
certain way - the text shall be clear, and not open for interpretation.


>> Also, an "extension" could have removed candidiates since the ufrag/pwd
>>was signalled. So, you cannot simply say "since current ufrag/pwd was
>>signalled". You also need to say something like "and are still active/in
>>use", or something like that.
>Why would I have to?

Because I assume we only want to signal candidates that are still in use.

That is what I meant by the semantic comment earlier. I don=B9t want the
semantic of a signalled candidate to be =B3It was signalled at some point
with the current ufrag/pwd, but it may no longer be in use=B2. I want it to
be =B3It was signalled at some point with the current ufrag/pwd, and it is
still in use=B2.

>As long as we remain within the currently specified Trickle-ICE
>functionality, all candidates that where exchanged within the scope of
>the current ufrag/pwd
>are "active/in use" in the sense of being subject to
>pairing/pruning/connectivity checking.
>A potential  future extension would have to deal with such issues and
>provide appropriate text.

We KNOW that there is a wish to be able to remove candidates, so while
trickle doesn't specify how it is done we shall assume it can be done some
way. Otherwise we may end up in a situation where we=B9ll either have to
update trickle and/or do some dirty hacks in order to get things to work.


>>>> Q2: What if an INFO does NOT contain a local candidate that has
>>>> previously been signaled? Do we assume it has been removed using some
>>>> "extension"? Do we assume it's still there?
>>> We could either treat this case as an error and ignore the content of
>>>that INFO.
>>> Probably not the best idea, e.g. in case that a=3Dend-of-candidates was
>>>included.
>>> Or we can assume (in absence of any "removal extension") that it is
>>>still there. That
>>> would allow to still make use of any newly trickled candidates in such
>>>an INFO. This makes more sense to me.
>>> If this is agreable I would be happy to put corresponding text into
>>>section 4.2.
>> ...or, we could go back to my previous proposal, and say that we *ONLY*
>>signal the new candidates, and that the INFO has no impact on any other
>>candidates :)
>Well, there is consensus since  2013 that the INFO carries all candidates.
>It was one outcome of the thread that started here
>https://mailarchive.ietf.org/arch/search/?email_list=3Dmmusic&gbt=3D1&inde=
x=3DT7
>R18RumQQJrmtHRh1lmcf9wcqs
>
>I can't remember that this consensus was not challenged since then, but
>I guess that all implementations will expect all candidates in the INFO.

We didn=B9t discuss removal of candidates back in 2013, so I think we shall
re-ask the community.


>> Also, assuming all current candidates are present in INFOs, what about
>>peer reflexive candidates? Will they be present in INFOs?
>Actually there is no real need to put peer reflexive candidates into the
>INFO package since the ICE Agents learn them from the STUN checks.
>However,  the current text does not preclude that you signal the peer
>reflexives redundantly in the INFO package.

Again - that needs to be clarified.

Regards,

Christer



>>>>>Q3: What if a candidate has bee removed using some "extension", and
>>>>> then it still shows up in an INFO? Does it mean it's automatically
>>>>> added back?
>>>> This is probably the easiest way to deal with that, as it does not
>>>>require housekeeping.
>>>> But again I see this as something that the future extension document
>>>>has to deal with.
>> ...or, we could go back to my previous proposal, and say that we *ONLY*
>>signal the new candidates, and that the INFO has no impact on any other
>>candidates :)
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>


From nobody Tue Oct 11 11:52:57 2016
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 E59C4129671; Tue, 11 Oct 2016 11:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.518
X-Spam-Level: 
X-Spam-Status: No, score=-17.518 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, 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 zz3BV_b8RVBs; Tue, 11 Oct 2016 11:52:54 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3633912965B; Tue, 11 Oct 2016 11:52:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=481; q=dns/txt; s=iport; t=1476211974; x=1477421574; h=to:cc:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=Tj2iX9LyMpQrTP+QlhLLrYFQu5AJGIxwOWwBIS/Thh4=; b=l2oBO6HKgHxj5IQKxwF42vvafPt8R+93D4oqvU5w/decxAOtkYNakLNC o+7Oidm/X9KuKAeVpSr6cH83EzW09TKm7nL27tdBVWku5ezLjZxLD4kfE yEzOmjY6GT6eO3oNQKWfR99//507DW+2fNw8E50EHQ7af5L8EVxG8TNCX 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CdAgAsNP1X/5BdJa1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgzwBAQEBAR1XKlKNM6kogg+CCyaFeoIJOBQBAgEBAQEBAQFeJ4ULFUE?= =?us-ascii?q?1AiYCXw0IAQGITA62G40EAQEBAQEBBAEBAQEBAR0FgQeFNoF9iiOCWwEEmgKPf?= =?us-ascii?q?YFYARWEZ4MUhGWBJ4x5g38eNk2EfCI0AYhjAQEB?=
X-IronPort-AV: E=Sophos;i="5.31,330,1473120000"; d="scan'208";a="162281243"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Oct 2016 18:52:53 +0000
Received: from [10.155.84.246] (dhcp-10-155-84-246.cisco.com [10.155.84.246]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u9BIqqdc019560; Tue, 11 Oct 2016 18:52:53 GMT
To: mmusic <mmusic@ietf.org>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <19028e81-8f2e-090f-7cdf-5d942382d393@cisco.com>
Date: Tue, 11 Oct 2016 14:53:04 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/0DmpWG-mL9IFOfcv_s5pxiGk2HQ>
Cc: "draft-ietf-mmusic-sctp-sdp@ietf.org" <draft-ietf-mmusic-sctp-sdp@ietf.org>
Subject: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2016 18:52:56 -0000

Greetings MMUSIC

This is to announce a 2 week WGLC on the draft:

     https://www.ietf.org/id/draft-ietf-mmusic-sctp-sdp-18.txt

as Proposed Standard. Please review and provide any comments you may 
have on the document by Tuesday, October 25, 2016. 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)


From nobody Tue Oct 11 15:05:10 2016
Return-Path: <btdingle@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 095041293D9; Tue, 11 Oct 2016 15:05:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 2RuhP8lmw1eN; Tue, 11 Oct 2016 15:05:07 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 15BCF12946C; Tue, 11 Oct 2016 15:05:04 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id t73so40864252oie.1; Tue, 11 Oct 2016 15:05:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3lXP6z2VWoO92EaIhdjfu86g19l97WoeRDzxrNRj/UE=; b=YZTucAWvwR4IErDVEIesjCTOojakSHAo7zSP9N2X5EStZ0aSOvb0XmVZyMhe4gS0qB MGr7EMvnNTMOj4rGPOLC+pCzY6yTktwpVa2UQ9WuxtsDuytevgZlu9pg0o2b43BruFZ/ Aia6+P6dfJsDltJDI0gEZDt36RgxhOqHdbzNXxq9obBKsJO2L7hgl4DHREIPqVewQ43y HuU0rg3tU80UJKTMB8J+foy4CGdAHq/k/TfeIwYGRT/6+kxXQ/Ofr9cx7PsC3iHHH6bV bJn0aR64sj+OfMPg1nrjk6HrSJRsS1xLzwps8TJIEPIL/jQNhdPTJJDNBhAKD0TxTvcO INOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3lXP6z2VWoO92EaIhdjfu86g19l97WoeRDzxrNRj/UE=; b=ZZERMArBci7fq+zWG+rTZSZdyqJeUHz++I6dlT1k61s655wOa6lYXG2gLY6H6qGfMU 37bpJC5mG06XVinZMJ5SC7fy9kkM9Ic7uABzcAG+10HWW1yPJ3uXq9lTPcQTOilE0d+o XD2K18f1G2f++oh8Wz+DNcOTscyeI1WzuHwp2taYr6LbAc08t42D365c4yD4i9gCvpHF Z61YCNoTUL5CSBho6LaZk2tCNBw2i71QG1UljW+77/jQ/ldicqGY5TDnaB8exxBE38G0 +fQybpBxKithjZTnhZMzp2YIfpny67NjWQW290nJDcio0weRxiPd4bBezQtLwuEM/PgM 8rkQ==
X-Gm-Message-State: AA6/9RkGmQvp9y6vXKbh87ncQQA2IwrejFI2KaYwzDt6VylV4/yQfiCp/tJAH2Ua2IBJvtvqco5bQi6QXlz6kw==
X-Received: by 10.157.22.201 with SMTP id s9mr3546559ots.194.1476223503449; Tue, 11 Oct 2016 15:05:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.14.240 with HTTP; Tue, 11 Oct 2016 15:04:43 -0700 (PDT)
In-Reply-To: <19028e81-8f2e-090f-7cdf-5d942382d393@cisco.com>
References: <19028e81-8f2e-090f-7cdf-5d942382d393@cisco.com>
From: Barry Dingle <btdingle@gmail.com>
Date: Wed, 12 Oct 2016 09:04:43 +1100
Message-ID: <CAN=GVAs8M-4D6vLUB-T0r8jNC=hGBPCD8YFdS0UBnitnvpf9vw@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Content-Type: multipart/alternative; boundary=001a113d1250884899053e9e113d
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/-g_zYAhp_BVrbFPN9NHFNKGflZQ>
Cc: "draft-ietf-mmusic-sctp-sdp@ietf.org" <draft-ietf-mmusic-sctp-sdp@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2016 22:05:09 -0000

--001a113d1250884899053e9e113d
Content-Type: text/plain; charset=UTF-8

Small editorial -

The second paragraph in the Introduction section is entirely repeated in
the start of the third paragraph.


Barry Dingle
Fixed - 03-9725-3937    Mob - 041-911-7578
Melbourne, Australia

On 12 October 2016 at 05:53, Flemming Andreasen <fandreas@cisco.com> wrote:

> Greetings MMUSIC
>
> This is to announce a 2 week WGLC on the draft:
>
>     https://www.ietf.org/id/draft-ietf-mmusic-sctp-sdp-18.txt
>
> as Proposed Standard. Please review and provide any comments you may have
> on the document by Tuesday, October 25, 2016. 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
>

--001a113d1250884899053e9e113d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Small editorial - <br><br></div>The second paragraph =
in the Introduction section is entirely repeated in the start of the third =
paragraph. <br><div class=3D"gmail_extra"><br><div><div class=3D"gmail_sign=
ature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D=
"ltr"><div><div dir=3D"ltr"><br>Barry Dingle<br>Fixed - 03-9725-3937=C2=A0 =
=C2=A0 Mob - 041-911-7578=C2=A0=C2=A0 <br>Melbourne, Australia <br></div></=
div></div></div></div></div></div>
<br><div class=3D"gmail_quote">On 12 October 2016 at 05:53, Flemming Andrea=
sen <span dir=3D"ltr">&lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_=
blank">fandreas@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">Greetings MMUSIC<br>
<br>
This is to announce a 2 week WGLC on the draft:<br>
<br>
=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/id/draft-ietf-mmusic-sctp-sdp=
-18.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/id/draft=
-<wbr>ietf-mmusic-sctp-sdp-18.txt</a><br>
<br>
as Proposed Standard. Please review and provide any comments you may have o=
n the document by Tuesday, October 25, 2016. 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>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote></div><br></div></div>

--001a113d1250884899053e9e113d--


From nobody Tue Oct 11 23:01:36 2016
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 4AD971295D9; Tue, 11 Oct 2016 23:01:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 BI9zrHHHej_F; Tue, 11 Oct 2016 23:01:33 -0700 (PDT)
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 17A191295D3; Tue, 11 Oct 2016 23:01:32 -0700 (PDT)
X-AuditID: c1b4fb25-14bff7000000793b-d5-57fdd1ba862d
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by  (Symantec Mail Security) with SMTP id B5.F3.31035.AB1DDF75; Wed, 12 Oct 2016 08:01:31 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0319.002; Wed, 12 Oct 2016 08:01:29 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Barry Dingle <btdingle@gmail.com>, Flemming Andreasen <fandreas@cisco.com>
Thread-Topic: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18
Thread-Index: AQHSI/CuxO4Zl9OCVEaLjVJgwoDZXKCjrYiAgAC5VYA=
Date: Wed, 12 Oct 2016 06:01:29 +0000
Message-ID: <D423ADD5.10F05%christer.holmberg@ericsson.com>
References: <19028e81-8f2e-090f-7cdf-5d942382d393@cisco.com> <CAN=GVAs8M-4D6vLUB-T0r8jNC=hGBPCD8YFdS0UBnitnvpf9vw@mail.gmail.com>
In-Reply-To: <CAN=GVAs8M-4D6vLUB-T0r8jNC=hGBPCD8YFdS0UBnitnvpf9vw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_D423ADD510F05christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrJIsWRmVeSWpSXmKPExsUyM2K7ru7ui3/DDbbs4bR4fN/W4tW6+cwW 7y/oWkxd/pjFgcVjyu+NrB47Z91l91iy5CdTAHMUl01Kak5mWWqRvl0CV8a+N+dYCv7KVPT8 X8vcwPhaoouRk0NCwETi4ddbTF2MXBxCAusZJZac6GQBSQgJLGGUeLO3pIuRg4NNwEKi+582 SFhEwE/i8fo2NhCbWSBb4ti+F8wgtrCAtcSRH4vZIGpsJCYfvcQCYVtJzL2xHCzOIqAq0dre yApi8wLVNzRuYobY28wocWzdErAiToFAid/3r4INZRQQk/h+ag0TxDJxiVtP5jNBHC0gsWTP eWYIW1Ti5eN/YENFBfQkvn+dDRVXlPj4ah8jRG+CxL/m0ywQiwUlTs58wjKBUXQWkrGzkJTN QlIGETeQeH9uPjOErS2xbOFrKFtfYuOXs4wQtrXEvbnPmZDVLGDkWMUoWpxanJSbbmSsl1qU mVxcnJ+nl5dasokRGKEHt/xW3cF4+Y3jIUYBDkYlHt4FGn/DhVgTy4orcw8xSnAwK4nwHjwN FOJNSaysSi3Kjy8qzUktPsQozcGiJM5rtvJ+uJBAemJJanZqakFqEUyWiYNTqoFRrGXzse+H Dh4Jny5Q9kbvmEM+G9/BvLj0Mm1uc7XqLe6PN7RJzPz8VVXsE/vW49f2+vS+9NqUu7WMqXHv LKY/jO85z61LfVTj0n3+4KHcoCnnb85t/qvg9IRVw1F9Z/5l4Xdr58k4df/tStidycmy8qte qfh9i62vUnfduVD0/HiHbvBVwTWNSizFGYmGWsxFxYkAhw6N0MwCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/z3RXV5j6lKVejcqIWmdrRlGk8gI>
Cc: "draft-ietf-mmusic-sctp-sdp@ietf.org" <draft-ietf-mmusic-sctp-sdp@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 06:01:35 -0000

--_000_D423ADD510F05christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Barry,

>Small editorial -
>
>The second paragraph in the Introduction section is entirely repeated in t=
he start of the third paragraph.

I=92ll remove the second paragraph.

Thanks!

Regards,

Christer



On 12 October 2016 at 05:53, Flemming Andreasen <fandreas@cisco.com<mailto:=
fandreas@cisco.com>> wrote:
Greetings MMUSIC

This is to announce a 2 week WGLC on the draft:

    https://www.ietf.org/id/draft-ietf-mmusic-sctp-sdp-18.txt

as Proposed Standard. Please review and provide any comments you may have o=
n the document by Tuesday, October 25, 2016. 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<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


--_000_D423ADD510F05christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <4801263ECF833449B6D55DE58D3343A3@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi Barry,</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir=3D"ltr">
<div>&gt;Small editorial - <br>
&gt;</div>
&gt;The second paragraph in the Introduction section is entirely repeated i=
n the start of the third paragraph.
<br>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div>I=92ll remove the second paragraph.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On 12 October 2016 at 05:53, Flemming Andreasen =
<span dir=3D"ltr">
&lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank">fandreas@cisco.=
com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Greetings MMUSIC<br>
<br>
This is to announce a 2 week WGLC on the draft:<br>
<br>
&nbsp; &nbsp; <a href=3D"https://www.ietf.org/id/draft-ietf-mmusic-sctp-sdp=
-18.txt" rel=3D"noreferrer" target=3D"_blank">
https://www.ietf.org/id/draft-<wbr>ietf-mmusic-sctp-sdp-18.txt</a><br>
<br>
as Proposed Standard. Please review and provide any comments you may have o=
n the document by Tuesday, October 25, 2016. 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>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D423ADD510F05christerholmbergericssoncom_--


From nobody Wed Oct 12 00:46:58 2016
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 E66C612953E for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 00:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 jCk-Lk9Ibw4U for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 00:46:55 -0700 (PDT)
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 E6216129494 for <mmusic@ietf.org>; Wed, 12 Oct 2016 00:46:54 -0700 (PDT)
X-AuditID: c1b4fb2d-1dbff700000009f7-86-57fdea6c2a52
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by  (Symantec Mail Security) with SMTP id DC.5A.02551.C6AEDF75; Wed, 12 Oct 2016 09:46:53 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0319.002; Wed, 12 Oct 2016 09:46:51 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: draft-ietf-mmusic-trickle-ice-sip-05: Christer's comments on Section 3
Thread-Index: AQHSJFzLq093QcOlP0+G3o9im3jSOA==
Date: Wed, 12 Oct 2016 07:46:51 +0000
Message-ID: <D423C6A6.10F6A%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <BCDAB66AD99FE945B2345D817DA73BA2@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM2K7vW7uq7/hBt+mcFtMXf6YxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGdM+72IsOCZScX79MtYGxkaBLkZODgkBE4m+vVvYQWwhgfWM EvvepnUxcgHZSxglujaeZO1i5OBgE7CQ6P6nDVIjIqAu8XVvDzNIWFggUOLWYVWIcJjEwQVn mCFsPYkHGz8ygtgsAqoS+x9PYQcp5xWwlpjaFAkSZhQQk/h+ag0TiM0sIC5x68l8JohrBCSW 7DnPDGGLSrx8/I8VxBYFGvn962youJLEjw2XWCB69SRuTJ3CBmFbS9z98xXK1pZYtvA1WD2v gKDEyZlPWCYwisxCsm4WkvZZSNpnIWmfhaR9ASPrKkbR4tTi4tx0I2O91KLM5OLi/Dy9vNSS TYzAaDi45bfuDsbVrx0PMQpwMCrx8C7Q+BsuxJpYVlyZe4hRgoNZSYRX/QVQiDclsbIqtSg/ vqg0J7X4EKM0B4uSOK/ZyvvhQgLpiSWp2ampBalFMFkmDk6pBsam6e0vmi7aa8ts0Ylbtrhr k0fqp4j8PVuPaxxYtpLn5rEzytpTP+n0fXu9VNvrhOoElQdx3gIVX/JZL2fXnBPIPBR2ilPv 8qKueZ6RdXPsl+rcPlDceshjHs/UyA2XTj86xVXPz+3d3jlRsnCnUTDTJ6GO/bms1xiuCixI 6lQ80KTCEN2b16jEUpyRaKjFXFScCABUcgPUggIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/GmKRuCFfGxw6RPgavMb7O7Eiz2w>
Subject: [MMUSIC] draft-ietf-mmusic-trickle-ice-sip-05: Christer's comments on Section 3
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 07:46:57 -0000

Hi,

Below are comments on Section 3. In general, it=B9s about editorial stuff.
There is too much text, and text that is very difficult to understand.

Regards,

Christer

----------

Q1:

The text in Section 3 says:

   "The semantics that Vanilla ICE for SIP [I-D.ietf-mmusic-ice-sip-sdp]
   defines for exchanging ICE candidates are exclusively based on use of
   Offers and Answers as per [RFC3264] over the Session Description
   Protocol (SDP) [RFC4566].=B2

I think that text is messy. Why not simply say that, when using Vanilla
ICE (or whatever we=B9ll end up calling it),
ICE candidates are exchanged using the Offer/Answer mechanism.



Q2:

The text in Section 3 says:

   "This specification extends these mechanism
    by allowing ICE candidates to also be sent in parallel to the Offer/
    Answer negotiation or after the completion of Offer/Answer
    negotiation.=B2


First, I am not sure exactly what =B3these mechanism=B2 mean, and what you =
are
extending. Why not simply say that this specification defines a mechanism
where candidates can be exchanged using INFO requests.

Second, the =B3parallel=B2 wording is confusing. It sounds like you=B9re on=
ly
allowed to use trickle while you have ongoing O/A negotiations.



Q3:

The text in Section 3 says:

    "Typically, in cases where Trickle ICE is fully supported, a candidate
     exchange would happen along the following lines: The Offerer would
     send an INVITE containing a subset of candidates and then wait for an
     early dialog to be established.  Once that happens, it will be able
     to continue sending candidates through in INFO requests and within
     the same dialog.

     Similarly, an Answerer can start or continue "trickling" ICE
     candidates using INFO messages within the dialog established by its
     18x provisional response.  Figure 1 shows such a sample exchange:=B2


I suggest to simply say that, once the early dialog has been established,
additional candidates can be exchanged using INFO requests.



Q4:

I think we can remove Section 3.1. The text belongs in the Info Package
definition (Section 10).



Q5:

In Section 3.3, both paragraphs are very difficult to read and understand.

I think what you want to say is that while INFOs are not considered
Offers/Answers, and do not increment the o=3D line value etc, candidates
that have been exchanged using INFO shall
be included in subsequent Offers/Answers carrying candidates.

Talking about =B3traditional SIP=B2, =B3offer/answer modules=B2 etc is just
confusing.



From nobody Wed Oct 12 02:32:30 2016
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 8A4EE1295BB for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 02:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 rZthHnzNPEzm for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 02:32:27 -0700 (PDT)
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 B37FE129445 for <mmusic@ietf.org>; Wed, 12 Oct 2016 02:32:26 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-37-57fe0328b61e
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by  (Symantec Mail Security) with SMTP id 66.30.02458.8230EF75; Wed, 12 Oct 2016 11:32:24 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0319.002; Wed, 12 Oct 2016 11:32:23 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Cullen Jennings <fluffy@iii.ca>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
Thread-Index: AQHSH9ATPAZhiMqWXkq+6ZcG+jYe1aCbTNuAgACLuoCAALOQAIAIHeaA
Date: Wed, 12 Oct 2016 09:32:22 +0000
Message-ID: <D423DEE7.1101D%christer.holmberg@ericsson.com>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com>
In-Reply-To: <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <437624109B9A7F4D800E2ABBFEBB374E@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFIsWRmVeSWpSXmKPExsUyM2K7qK4G879wg+6X6hYf1v9gtJi6/DGL xYoNB1gdmD3+vv/A5LFkyU8mj8vnPzIGMEdx2aSk5mSWpRbp2yVwZVyadJut4BxvxdP5Oxgb GOdwdzFyckgImEhcPraJqYuRi0NIYD2jxLNF71ggnCWMEpOm/WDtYuTgYBOwkOj+pw3SICIQ KbFw0gQmEJtZwFfi5YIvzCC2sEC+xK5vhxghagok/p/qA2sVEXCTWPZIECTMIqAq8XjyU1YQ m1fAWuL68t1Qe68zShxYsI0FJMEp4CAxsf81G4jNKCAm8f3UGqhd4hK3nsxngjhaQGLJnvPM ELaoxMvH/8CGigroSXz/Ohsqrijx8dU+RoheHYkFuz+xQdjWEn92t7FA2NoSyxa+ZoY4SFDi 5MwnLBMYxWchWTcLSfssJO2zkLTPQtK+gJF1FaNocWpxcW66kZFealFmcnFxfp5eXmrJJkZg DB7c8ttqB+PB546HGAU4GJV4eBdo/A0XYk0sK67MPcQowcGsJMK79j9QiDclsbIqtSg/vqg0 J7X4EKM0B4uSOK/ZyvvhQgLpiSWp2ampBalFMFkmDk6pBsbJ/JMtFym5BBlP+HPF52/i/oy7 TFUz7oRf9jz4+uO2PF4fkwz560c+zrgZ9uVx/5KSJ+GuS+1OyRTM27b/pfY9XlO1pesqFx94 f84ndM6y0kucH6PPn5JKePjr8zVprZIrK4PmXPix+FTWxIw3jX5bA7dotb9PeWf3ToSN+aHD RHeLovpG3iMflViKMxINtZiLihMBeKG+eL0CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/fr5E3FZr5zLHAcJDZsmaleQDm48>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 09:32:29 -0000

Hi,

Based on the discussions, and input that has been provided, are people ok
with adding the text Magnus suggested (see below) to the Security
Considerations of BUNDLE?

Regards,

Christer


>>> The identfication-tag when included in the RTP MID SDES item,
>>> independent of transport, RTCP SDES packet or RTP header extension,
>>> can expose the value to parties beyond the signaling chain.
>>> Therefore, the identification-tag MUST NOT contain any user related
>>> information. However, the implementation's method for generating
>>> identfication-tags combined with hardware configuration can enable
>>> fingerprinting of the endpoint device and thus its user. As the
>>> identification-tag is also used to route the media stream to the
>>> right application functionality it is also important that the value
>>> received is the one intended by the sender, thus integrity and the
>>> authenticity of the source are important to prevent denial of
>>> service on the application. At least to prevent third parties from
>>> modifying the identification-tag value.
>>>
>>> Due to the security risks associated with the MID values in RTP and
>>> RTCP it is strongly RECOMMENDED that the MID SDES item is both
>>> confidentiality protected as well as source authenticated when
>>> transported in either RTCP or RTP header extensions. The security
>>> mechanisms used SHALL provide corresponding levels of security for
>>> both RTP header extensions and RTCP. Confidentiality mechanisms for
>>> RTP/RTCP are discussed in Options for Securing RTP Sessions
>>> [RFC7201], for example SRTP [RFC3711] with SRTCP encryption enabled
>>> combined with [RFC6904] can provide the necessary security
>>> functions.


From nobody Wed Oct 12 03:37:38 2016
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 0F16A129760 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 03:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 NsRn_ss8vh27 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 03:37:35 -0700 (PDT)
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 C2D1F1296F1 for <mmusic@ietf.org>; Wed, 12 Oct 2016 03:37:34 -0700 (PDT)
X-AuditID: c1b4fb30-b73ff70000000cb2-6f-57fe126c5e84
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by  (Symantec Mail Security) with SMTP id E7.CD.03250.C621EF75; Wed, 12 Oct 2016 12:37:33 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0319.002; Wed, 12 Oct 2016 12:37:31 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
Thread-Index: AQHSJHSivk5Ucbs2BE2kFscuEARQNA==
Date: Wed, 12 Oct 2016 10:37:31 +0000
Message-ID: <D423EDCF.1102F%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <AE57D950F3FD664B951D194C032745E2@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOIsWRmVeSWpSXmKPExsUyM2K7om6u0L9wg1/fuC027PvPbPFh/Q9G i2tn/jFaTF3+mMWBxWPnrLvsHkuW/GTyuHz+I2MAcxSXTUpqTmZZapG+XQJXxrQTLxgLrjFW dHw6zdrAuJ6xi5GTQ0LARGLtstfMXYxcHEIC6xklFrWdYYdwljBKPDl+k62LkYODTcBCovuf NkiDiIC6xNe9PWANzCANcz8+ZQZJCAtkSHw+uowJpF5EIFNixUo/iHo9iXuzVjOB2CwCqhI7 DmwCs3kFrCWWX24CsxkFxCS+n1oDZjMLiEvcejKfCeI4AYkle84zQ9iiEi8f/2MFsUWBZn7/ OhsqrijR/rSBEaJXT+LG1ClsELa1xPWjE6FsbYllC18zQ+wVlDg58wnLBEbRWUjWzULSPgtJ +ywk7bOQtC9gZF3FKFqcWpyUm25kpJdalJlcXJyfp5eXWrKJERhdB7f8NtjB+PK54yFGAQ5G JR7eBRp/w4VYE8uKK3MPMUpwMCuJ8B7n/RcuxJuSWFmVWpQfX1Sak1p8iFGag0VJnNds5f1w IYH0xJLU7NTUgtQimCwTB6dUA2OndbLoutuqH7JUOGvu2XdrbNv254qa8rVOo+ve0f+nHXtn sGPb27ezFcy+yP/v/vTk7vPfCRE7jD63+4m/WtHSnHHKf9FCFd+OqXZ57icnLN4tJ7Bs/bf2 4zPervNi3HLspcXmjxaHhQKWz2fJWCTJmh2sdJ6XNfxRwt1WdmXRlCc3dhy3ublAiaU4I9FQ i7moOBEAYfw4W6oCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/OsRi9pGCUJ4bFpfXJxNC5waR1uI>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 10:37:37 -0000

Hi,

I=B9ve created a pull request with additional text regarding associating
RTP/RTCP packets with the correct =B3m=3D=B3 line.

https://github.com/cdh4u/draft-sdp-bundle/pull/10


Regards,

Christer


From nobody Wed Oct 12 04:01:30 2016
Return-Path: <thomass.stach@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 6EC26129750 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 04:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oF-Ph910ewlg for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 04:01:26 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 77A4212963F for <mmusic@ietf.org>; Wed, 12 Oct 2016 04:01:26 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id b81so68994414lfe.1 for <mmusic@ietf.org>; Wed, 12 Oct 2016 04:01:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=dfC+07x84PFmx9EIKI4EqBcNSCxuXqRmL6e2TX7umW8=; b=OQFlWaIY2r48ni+NL9aYhWUhl6HhRxN8ZThCK0kwvp7LCQNC5uZtC/jmskjmeuf591 fLNwUngmSBSJS3fLJyd+dypJiWTRKlVb9FDWIHyJQDZssn5HLbmSaSAbxCbJkozfoLbg rjEirviKgIXhG6zl40XpeRHPS5xw6NotGDoGjXav+rnJG0KSSxQFNJcdX/vUdAPjTIyC 3yg36e0ODQNwvqu9nOegfIMZLTQXO6Z7NL4tAM7qTnqDmxMnku7hyLaZN57nUNRzeALP ODHl1jdqhv1FyqLaOgaStiqWhkaZyUZtC4rWVTTNb7AolvUqxIjA3SJ+HiriBewAL8RU sEvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=dfC+07x84PFmx9EIKI4EqBcNSCxuXqRmL6e2TX7umW8=; b=mKju7B8BR+y9/33+f6IzsyxCEW/YcZVnLnP4r5yUpETP1NQZmurbtGPd3/mT3VM5Ki IlhgiD2vFaVR6qm5M25ymWC8Dr602TZHqK8bpPvibk6OWwLBna7d9L9d6yJIZeeIo/Mx niU9qJnuXVYTHDc035DMkSPS73iN5iBUpYetHG66+oPUAs1NKNt6ImRPuwBaC87HzwkC G+OjKI+tJif3jhm0E5dzQLGdu0drtoyjuy2i47E74d7iwFyWl51vLh7LcLFlEsd3pOIy 7qsPJ0TWqF58BwtQyIgkeLg9VIxX5XRmUbaHwi3ORhC+nCWjn6W6tncTTU032b3Ucb50 pWfg==
X-Gm-Message-State: AA6/9RnmMuHnPKlLCpy2k1/AbfjtwIPHulog+RGZnWvFLWB1AeaJIeBq8c87mF8/lwp3zA==
X-Received: by 10.25.24.154 with SMTP id 26mr396605lfy.3.1476270084404; Wed, 12 Oct 2016 04:01:24 -0700 (PDT)
Received: from ?IPv6:2001:62a:4:41c:251f:c545:184:5e15? ([2001:62a:4:41c:251f:c545:184:5e15]) by smtp.googlemail.com with ESMTPSA id p76sm2011695lfd.11.2016.10.12.04.01.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Oct 2016 04:01:23 -0700 (PDT)
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <D41AC393.10727%christer.holmberg@ericsson.com> <bc713d1a-acdb-af95-5391-b3e244e1126d@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1B3B2@ESESSMB209.ericsson.se> <e44e62ff-1b0d-9180-2872-b98c84cbb6f6@gmail.com> <D4226F4E.10D4F%christer.holmberg@ericsson.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <7c516d72-ef2a-e928-dc4a-ee77298ebb22@gmail.com>
Date: Wed, 12 Oct 2016 13:01:22 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <D4226F4E.10D4F%christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/A-qke3iUclHE_pcK5uTYDbEBvqE>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 11:01:29 -0000

inline


On 2016-10-11 09:39, Christer Holmberg wrote:
> Hi,
>
>>>>> It has been suggested that removal of candidates should not be part of
>>>>> trickle, but rather be defined in a separate future extension draft.
>>>>> The comments below are based on that such "extension" may exist at
>>>>> some point.
>>>>>
>>>>> The text in section 4.2 says:
>>>>>       "In every INFO request agents MUST include all local candidates
>>>>> they
>>>>>       have signaled previously.  This is necessary in order to more
>>>>> easily
>>>>>       avoid problems that would arise from unreliable transports.  Mis-
>>>>>       ordering can be detected through the CSeq: header field in the
>>>>> INFO
>>>>>       request.  As a consequence candidates cannot be removed unless
>>>>> an ICE
>>>>>       restart is performed.  Note that extension might be specified in
>>>>> the
>>>>>       future that enable such removal without a restart."
>>>>> Q1: Assuming someone does define an extension which allows removal of
>>>>> candidates without a restart, do such candidates still have to be
>>>>> included in the INFO, as they have been "previously signalled"?
>>>> This would have to clarified in that future extension document
>>>> together with corresponding backward
>>>> compatibility issues and/or indication of support for such an
>>>> extension. I don't want to do design here,
>>>> but a=ice-options might be something to look at.
>>> How you indicate support of such extension is outside the scope of this
>>> thread. I want to clarify the exact semantics of a candidate in an INFO.
> Again, I agree that how candidates are removed is outside the scope. But,
> that doesn¹t change the fact that trickle needs to define exactly what the
> semantic of the signalled candidates. I do NOT want a future extension to
> change that semantic.
I don't how you want to preclude an arbitrary future extension to do 
such a change,
but in case of a "candidate removal" extension I don't see a problem 
with the current concept.
The current concept is (as I understand it):
- An INFO always carries all candidates that belong to the currently 
valid ufrag/pwd.
- We have the restriction that in subsequent INFOs the number of these 
candidates can
  only increase or remain constant until end-of-candidates is signalled.

If someone wants to define a "candidate removal" extension, he/she can keep
the semantics of the first item, i.e.
- An INFO always carries all candidates that belong to the currently 
valid ufrag/pwd.
  and would have to do the following
- modify the constraint to something like  "In subsequent INFOs the 
number of these candidates can increase, _decrease_ or remain constant "
- define how support for the "candidate removal" extension is 
negotiated  and how backward compatibility is achieved
-  define how candidates are actually removed

<snip/>
>>> Also, an "extension" could have removed candidiates since the ufrag/pwd
>>> was signalled. So, you cannot simply say "since current ufrag/pwd was
>>> signalled". You also need to say something like "and are still active/in
>>> use", or something like that.
>> Why would I have to?
> Because I assume we only want to signal candidates that are still in use.
>
> That is what I meant by the semantic comment earlier. I don¹t want the
> semantic of a signalled candidate to be ³It was signalled at some point
> with the current ufrag/pwd, but it may no longer be in use². I want it to
> be ³It was signalled at some point with the current ufrag/pwd, and it is
> still in use².
Does my answer from above work for you?
If yes, then I think we are not to far apart from each other and I could 
work on some improved text.
>
>> As long as we remain within the currently specified Trickle-ICE
>> functionality, all candidates that where exchanged within the scope of
>> the current ufrag/pwd
>> are "active/in use" in the sense of being subject to
>> pairing/pruning/connectivity checking.
>> A potential  future extension would have to deal with such issues and
>> provide appropriate text.
> We KNOW that there is a wish to be able to remove candidates, so while
> trickle doesn't specify how it is done we shall assume it can be done some
> way. Otherwise we may end up in a situation where we¹ll either have to
> update trickle and/or do some dirty hacks in order to get things to work.

>
>
>>>>> Q2: What if an INFO does NOT contain a local candidate that has
>>>>> previously been signaled? Do we assume it has been removed using some
>>>>> "extension"? Do we assume it's still there?
>>>> We could either treat this case as an error and ignore the content of
>>>> that INFO.
>>>> Probably not the best idea, e.g. in case that a=end-of-candidates was
>>>> included.
>>>> Or we can assume (in absence of any "removal extension") that it is
>>>> still there. That
>>>> would allow to still make use of any newly trickled candidates in such
>>>> an INFO. This makes more sense to me.
>>>> If this is agreable I would be happy to put corresponding text into
>>>> section 4.2.
>>> ...or, we could go back to my previous proposal, and say that we *ONLY*
>>> signal the new candidates, and that the INFO has no impact on any other
>>> candidates :)
>> Well, there is consensus since  2013 that the INFO carries all candidates.
>> It was one outcome of the thread that started here
>> https://mailarchive.ietf.org/arch/search/?email_list=mmusic&gbt=1&index=T7
>> R18RumQQJrmtHRh1lmcf9wcqs
>>
>> I can't remember that this consensus was not challenged since then, but
>> I guess that all implementations will expect all candidates in the INFO.
> We didn¹t discuss removal of candidates back in 2013, so I think we shall
> re-ask the community.
I still think that the current concept works, so will you want to ask 
that then?
>
>
>>> Also, assuming all current candidates are present in INFOs, what about
>>> peer reflexive candidates? Will they be present in INFOs?
>> Actually there is no real need to put peer reflexive candidates into the
>> INFO package since the ICE Agents learn them from the STUN checks.
>> However,  the current text does not preclude that you signal the peer
>> reflexives redundantly in the INFO package.
> Again - that needs to be clarified.
I can mention that
Thanks
Thomas
>
> Regards,
>
> Christer
>
>
>
>>>>>> Q3: What if a candidate has bee removed using some "extension", and
>>>>>> then it still shows up in an INFO? Does it mean it's automatically
>>>>>> added back?
>>>>> This is probably the easiest way to deal with that, as it does not
>>>>> require housekeeping.
>>>>> But again I see this as something that the future extension document
>>>>> has to deal with.
>>> ...or, we could go back to my previous proposal, and say that we *ONLY*
>>> signal the new candidates, and that the INFO has no impact on any other
>>> candidates :)
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>
>>>
>


From nobody Wed Oct 12 04:09:58 2016
Return-Path: <thomass.stach@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 CAB94129780 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 04:09:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 doBCqaf6iuEv for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 04:09:56 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 C391412977E for <mmusic@ietf.org>; Wed, 12 Oct 2016 04:09:55 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id x79so72142345lff.0 for <mmusic@ietf.org>; Wed, 12 Oct 2016 04:09:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=LChKWwEkiBVpL8mIheRC8cBJ7EPOvkXU25x9qYtluQ8=; b=0jD3cr/aXrPaQnykO+3kWXHRC4GqI+o7B7IWlH7RsVRbZqsje80KSjiX2dqTg9/Zwt tTVWTb3c7D/8i6mLbM144a/qVrGTG/0lk03E5Zm9CXCbaX296C5EhL4ucgoBgPzTJoXa EIN5yuNQaU4cj34rQIDtSpey1cGl8leMPEsMnXijHWI7jbum+TtByYuRlh59n2FnOeze tGZeQJV9VoNr7CMDHh6KHWKQa8iJ/wMlCTdgfIrZYdve7zGM5LA7460yExybGDyi8CpM A4uq9CmF0/lMG6BiBUIGKaZPqekOTuiptBHpV2a6UFNaVta8K/M5PTFI8Iv0SN0Zimic vfjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=LChKWwEkiBVpL8mIheRC8cBJ7EPOvkXU25x9qYtluQ8=; b=W7dd9qZrKzPgyrGHH8w7uz3gyvyN5SnMykwrrQbnRWYGPLwNEJGk6eRMnw3F6utWN1 RZjKl3Fi5ZmGKmDmQuEj4eKg8IgA5G756EbC3uRm7Ju07pW/hg/8AQSCZTQK/liD9jdq Fkg89QC5iVRqNs6K1ZblaBr9/fM3ib+vB0A4lIMJW4p5hVHrxIBKzk7XHnXUYeFDjd5W zqyrfUGDPJe+IZYWtoG16nvNP1fbXf5RxJ+YH/vpxDnpmORjI1bgscSwA/cpopLahOLR P9a+MGFM5lGZeohoWTLrPXQbsC3Vfw2EZnQOblv8qGgFC2pnYyBVFEPPh2WZXSYfPIvh xwCA==
X-Gm-Message-State: AA6/9Rnn1DL29A7FaD6tZsBhEsiqE7ThmgxscoGl5KeTDdkNb9ShHUGpS4h9xezqnebSdg==
X-Received: by 10.25.150.84 with SMTP id y81mr478803lfd.26.1476270593778; Wed, 12 Oct 2016 04:09:53 -0700 (PDT)
Received: from ?IPv6:2001:62a:4:41c:251f:c545:184:5e15? ([2001:62a:4:41c:251f:c545:184:5e15]) by smtp.googlemail.com with ESMTPSA id 35sm2018032lfp.5.2016.10.12.04.09.52 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Oct 2016 04:09:52 -0700 (PDT)
To: mmusic@ietf.org
References: <D423C6A6.10F6A%christer.holmberg@ericsson.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <de7d224b-e025-102c-41e5-48fe28e01ba6@gmail.com>
Date: Wed, 12 Oct 2016 13:09:52 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <D423C6A6.10F6A%christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jq-n7Xvup0gZ3qx2uBAYVP3Pd7Q>
Subject: Re: [MMUSIC] draft-ietf-mmusic-trickle-ice-sip-05: Christer's comments on Section 3
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 11:09:58 -0000

Christer,


thanks for the feedback.

I'll address it in the next update.

Just a clarifiying question below.


On 2016-10-12 09:46, Christer Holmberg wrote:
> Hi,
>
> Below are comments on Section 3. In general, it¹s about editorial stuff.
> There is too much text, and text that is very difficult to understand.
>
> Regards,
>
> Christer
>
> ----------
>
> Q1:
>
> The text in Section 3 says:
>
>     "The semantics that Vanilla ICE for SIP [I-D.ietf-mmusic-ice-sip-sdp]
>     defines for exchanging ICE candidates are exclusively based on use of
>     Offers and Answers as per [RFC3264] over the Session Description
>     Protocol (SDP) [RFC4566].²
>
> I think that text is messy. Why not simply say that, when using Vanilla
> ICE (or whatever we¹ll end up calling it),
> ICE candidates are exchanged using the Offer/Answer mechanism.
>
>
>
> Q2:
>
> The text in Section 3 says:
>
>     "This specification extends these mechanism
>      by allowing ICE candidates to also be sent in parallel to the Offer/
>      Answer negotiation or after the completion of Offer/Answer
>      negotiation.²
>
>
> First, I am not sure exactly what ³these mechanism² mean, and what you are
> extending. Why not simply say that this specification defines a mechanism
> where candidates can be exchanged using INFO requests.
>
> Second, the ³parallel² wording is confusing. It sounds like you¹re only
> allowed to use trickle while you have ongoing O/A negotiations.
>
>
>
> Q3:
>
> The text in Section 3 says:
>
>      "Typically, in cases where Trickle ICE is fully supported, a candidate
>       exchange would happen along the following lines: The Offerer would
>       send an INVITE containing a subset of candidates and then wait for an
>       early dialog to be established.  Once that happens, it will be able
>       to continue sending candidates through in INFO requests and within
>       the same dialog.
>
>       Similarly, an Answerer can start or continue "trickling" ICE
>       candidates using INFO messages within the dialog established by its
>       18x provisional response.  Figure 1 shows such a sample exchange:²
>
>
> I suggest to simply say that, once the early dialog has been established,
> additional candidates can be exchanged using INFO requests.
>
>
>
> Q4:
>
> I think we can remove Section 3.1. The text belongs in the Info Package
> definition (Section 10).
Do you propose to remove the text in 3.1 completely or to move it 
section 10?
Regards
Thomas
>
>
>
> Q5:
>
> In Section 3.3, both paragraphs are very difficult to read and understand.
>
> I think what you want to say is that while INFOs are not considered
> Offers/Answers, and do not increment the o= line value etc, candidates
> that have been exchanged using INFO shall
> be included in subsequent Offers/Answers carrying candidates.
>
> Talking about ³traditional SIP², ³offer/answer modules² etc is just
> confusing.
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Wed Oct 12 04:20:34 2016
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 E1005129484 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 04:20:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 p8fdvZIy7SxX for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 04:20:31 -0700 (PDT)
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 2F3FC128E18 for <mmusic@ietf.org>; Wed, 12 Oct 2016 04:20:31 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-dd-57fe1c7d3860
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by  (Symantec Mail Security) with SMTP id B5.38.02458.D7C1EF75; Wed, 12 Oct 2016 13:20:29 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0319.002; Wed, 12 Oct 2016 13:20:16 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Thomas Stach <thomass.stach@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] draft-ietf-mmusic-trickle-ice-sip-05: Christer's comments on Section 3
Thread-Index: AQHSJFzLq093QcOlP0+G3o9im3jSOKCkiA4AgAA3CAA=
Date: Wed, 12 Oct 2016 11:20:15 +0000
Message-ID: <D423F7F8.1105B%christer.holmberg@ericsson.com>
References: <D423C6A6.10F6A%christer.holmberg@ericsson.com> <de7d224b-e025-102c-41e5-48fe28e01ba6@gmail.com>
In-Reply-To: <de7d224b-e025-102c-41e5-48fe28e01ba6@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8FCEAF36520011488A9E579888E47714@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprEIsWRmVeSWpSXmKPExsUyM2K7t26tzL9wg8k/VSymLn/MYvHpxFYm ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugSvjy8PzLAVdrBWbNs5jaWD8ydzFyMkhIWAi 8XPZMVYQW0hgPaPEhXt8XYxcQPYSRolZsxewdDFycLAJWEh0/9MGqRERCJT4fOY4E4gtLBAn 8bN3OStEPF7i1IWNbBC2lcTl9XvA4iwCqhI75+8Ci/MKWEusOb2eHWJXnsSKzV1gczgFbCVW zbgGFmcUEJP4fmoNWJxZQFzi1pP5TBB3Ckgs2XMe6mZRiZeP/4HNFxXQk/j+dTYzyJkSAkoS 07amQbTqSdyYOoUNwraWuNWxCsrWlli28DUzxDmCEidnPmGZwCg2C8m2WUjaZyFpn4WkfRaS 9gWMrKsYRYtTi4tz042M9FKLMpOLi/Pz9PJSSzYxAmPq4JbfVjsYDz53PMQowMGoxMO7QONv uBBrYllxZe4hRgkOZiURXn3xf+FCvCmJlVWpRfnxRaU5qcWHGKU5WJTEec1W3g8XEkhPLEnN Tk0tSC2CyTJxcEo1MHZe/mIi1y7Tuen/QamlKUFx7J2hF1MSP/PLa9x2WvmcMYVtvUL2ueB5 Um81+eJj5l1cLOW9JW37YnOpK2Jty1RSZM80WJgf47nUbceh3Wq8dNOGeyXN317bFwvZqdie cyg8GSHkk/Pr29WseQ6uese7Jy881fDmQPmkRuP0bTu/OFyr5WP5qsRSnJFoqMVcVJwIAHhU wTqlAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/m3BriSivApS_do_c4cvQPuPeR-w>
Subject: Re: [MMUSIC] draft-ietf-mmusic-trickle-ice-sip-05: Christer's comments on Section 3
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 11:20:33 -0000

Hi,

>>Q4:
>>
>> I think we can remove Section 3.1. The text belongs in the Info Package
>> definition (Section 10).
>Do you propose to remove the text in 3.1 completely or to move it
>section 10?

I didn=B9t check what you have in section 10, but per RFC 6086 the Info
Package definition needs to explain why INFO was chosen instead of other
alternatives.

So, unless you have done that, you can move the text from section 3.1. I
do think you should make it a little shorter, though. I personally think
INFO is the obvious choice in this case, so I don=B9t think you=B9ll need t=
oo
much justification.

Regards,

Christer



From nobody Wed Oct 12 04:47:19 2016
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 CA9E012948B for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 04:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 1qc4ciXCtrw5 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 04:47:17 -0700 (PDT)
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 A67191297A0 for <mmusic@ietf.org>; Wed, 12 Oct 2016 04:47:16 -0700 (PDT)
X-AuditID: c1b4fb3a-aa3ff7000000099a-52-57fe22c210b3
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.183.42]) by  (Symantec Mail Security) with SMTP id DC.DD.02458.2C22EF75; Wed, 12 Oct 2016 13:47:15 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.03.0319.002; Wed, 12 Oct 2016 13:47:13 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, Cullen Jennings <fluffy@iii.ca>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
Thread-Index: AQHSH9ATPAZhiMqWXkq+6ZcG+jYe1aCbTNuAgACLuoCAALOQAIAIHeaAgAAlrQA=
Date: Wed, 12 Oct 2016 11:47:12 +0000
Message-ID: <D423FEEE.11074%christer.holmberg@ericsson.com>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com> <D423DEE7.1101D%christer.holmberg@ericsson.com>
In-Reply-To: <D423DEE7.1101D%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0933DD8759E43646AB4A500ABD75E284@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFIsWRmVeSWpSXmKPExsUyM2K7lu5hpX/hBm+OcFh8WP+D0WLq8scs Fis2HGB1YPb4+/4Dk8eSJT+ZPC6f/8gYwBzFZZOSmpNZllqkb5fAlfGm9xtjwReBimPzdrE3 MPbwdTFyckgImEjsa9vL1MXIxSEksJ5R4vqqZ2wgCSGBJYwS99rUuxg5ONgELCS6/2mD1IgI 9DJKTH58iwWkhlnAV+L9z+nsILawQL7Erm+HGEFsEYECif+n+lghbD+Jw28vs4DMYRFQlbj1 RgIkzCtgLfH99C8WiL2dTBLf1lwC28spYCOx/XYL2BxGATGJ76fWMEHsEpe49WQ+E8TRAhJL 9pxnhrBFJV4+/ge2S1RAT+L719lQcUWJ9qcNjBC9OhILdn9ig7CtJQ4u3wZ1v7bEsoWvmSEO EpQ4OfMJywRG8VlI1s1C0j4LSfssJO2zkLQvYGRdxShanFpcnJtuZKSXWpSZXFycn6eXl1qy iREYgwe3/LbawXjwueMhRgEORiUe3gUaf8OFWBPLiitzDzFKcDArifBOU/gXLsSbklhZlVqU H19UmpNafIhRmoNFSZzXbOX9cCGB9MSS1OzU1ILUIpgsEwenVANjKLtQRJyWs8GBlmX7Jve5 vpiZc4LHi+O715NfJ2/8Xln3qETE+uwmlnN3lzeKzb1/89yCwuInqwp+16lV3v9e0+Fw6rVo 2WHHLyc2vOxdZtAm5hrH5py+81zaHJZ0u6unIqYFRAiHBwZ9T7bK40t0/fjo7su/jTpsVV5G Qf/cNWUyXr9mq/+pxFKckWioxVxUnAgAqDhaC70CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/1-NEMD6aslFAlZfpfun3GfsBIgE>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 11:47:19 -0000

Pull request created.

https://github.com/cdh4u/draft-sdp-bundle/pull/11


Regards,

Christer


On 12/10/16 12:32, "mmusic on behalf of Christer Holmberg"
<mmusic-bounces@ietf.org on behalf of christer.holmberg@ericsson.com>
wrote:

>Hi,
>
>Based on the discussions, and input that has been provided, are people ok
>with adding the text Magnus suggested (see below) to the Security
>Considerations of BUNDLE?
>
>Regards,
>
>Christer
>
>
>>>> The identfication-tag when included in the RTP MID SDES item,
>>>> independent of transport, RTCP SDES packet or RTP header extension,
>>>> can expose the value to parties beyond the signaling chain.
>>>> Therefore, the identification-tag MUST NOT contain any user related
>>>> information. However, the implementation's method for generating
>>>> identfication-tags combined with hardware configuration can enable
>>>> fingerprinting of the endpoint device and thus its user. As the
>>>> identification-tag is also used to route the media stream to the
>>>> right application functionality it is also important that the value
>>>> received is the one intended by the sender, thus integrity and the
>>>> authenticity of the source are important to prevent denial of
>>>> service on the application. At least to prevent third parties from
>>>> modifying the identification-tag value.
>>>>
>>>> Due to the security risks associated with the MID values in RTP and
>>>> RTCP it is strongly RECOMMENDED that the MID SDES item is both
>>>> confidentiality protected as well as source authenticated when
>>>> transported in either RTCP or RTP header extensions. The security
>>>> mechanisms used SHALL provide corresponding levels of security for
>>>> both RTP header extensions and RTCP. Confidentiality mechanisms for
>>>> RTP/RTCP are discussed in Options for Securing RTP Sessions
>>>> [RFC7201], for example SRTP [RFC3711] with SRTCP encryption enabled
>>>> combined with [RFC6904] can provide the necessary security
>>>> functions.
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www.ietf.org/mailman/listinfo/mmusic


From nobody Wed Oct 12 09:58:07 2016
Return-Path: <ekr@rtfm.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 0EC4912961D for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 09:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k9fTz2OGAJTw for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 09:58:04 -0700 (PDT)
Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D75B129619 for <mmusic@ietf.org>; Wed, 12 Oct 2016 09:58:04 -0700 (PDT)
Received: by mail-yw0-x233.google.com with SMTP id t192so37049199ywf.0 for <mmusic@ietf.org>; Wed, 12 Oct 2016 09:58:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mjwluU3skCdwEEAujIcAkT+E6r2OUX5nw4TcPrh++Wo=; b=V0x06bdQekYxTH9JFWi+kZ1f/1v2eSmsIKDxPrWiRDi4btTeX+eCPFUlR9fNIOvk3g mdb86RQ/AGxmYkUpvemJP2sE46qE+y3yXpIXe+JfYFFLjzgZMop64fl13aoZmiII8zC6 iWY4TlDqHjmvxOSRLwiJIL+oKpOQtm35ZOwX9VQLoI7jkPi1Bvk94F40OaZmCWMQI1Dg BqPHj3EaOrY9CGts67S4eAWwNI9pCLRqTL9JMZgRnXhu6rOAMnpxaojeE8vqnk0+TgH/ 0T415VeP6CTnRNhm9AhBZlfL8HrDJ7AcaOlGyYx1FJEIpsimbb+35BuZg+S9LhwUuGJ8 9thQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mjwluU3skCdwEEAujIcAkT+E6r2OUX5nw4TcPrh++Wo=; b=JhTESHi7abzUO/LmZGNfUmiLHERGt91D5agckXkB+PcUJ8afnwsjngg3rp61EeXk+X jXpqHD8haUE/hjs4sRbSjbDB/9fIkc0y3E/fEhfrWiiW9yDerNwLgYdQBstqzS6asUJS gnx/ioj5YZbDBXViDH6ivph+SCmXsgxKwKxOtBM2vQeuM6YM0FpO0GIh8Q/7XbpMZloI Ru4A5miF4Vz4mWl+i80PynxhrKxc0YYOr05vhwqaXBcPpYB59dd+xXA0QSFSwATpGQ0b VWBHr/pC/pdKyQuRFa2ZuSQbdh8N619J0YG/Lm8oIYFTtF8qMLysuuiIAy04XDOxzfbI dFTw==
X-Gm-Message-State: AA6/9Rn4ql1paUYTeDx7edkedQlFCM+BLyAn6FUMm44kWXKwSFKs1g2XaMEqQLweyKTE1cROBLS2SHX0QWeFYw==
X-Received: by 10.129.121.206 with SMTP id u197mr1884225ywc.146.1476291483526;  Wed, 12 Oct 2016 09:58:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.75.212 with HTTP; Wed, 12 Oct 2016 09:57:22 -0700 (PDT)
In-Reply-To: <D423FEEE.11074%christer.holmberg@ericsson.com>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com> <D423DEE7.1101D%christer.holmberg@ericsson.com> <D423FEEE.11074%christer.holmberg@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 12 Oct 2016 09:57:22 -0700
Message-ID: <CABcZeBO7b3XGRTCzN4-Z-6=8sTD3nrr8HtgN1q9np-hZ3tqbMQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c0b0f68761918053eade571
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ib95a90BH6p3edMS9B5CVDws2Fk>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 16:58:06 -0000

--94eb2c0b0f68761918053eade571
Content-Type: text/plain; charset=UTF-8

I don't think there is anything like consensus for a 2919-level RECOMMENDED
to encrypt the MID.

On Wed, Oct 12, 2016 at 4:47 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Pull request created.
>
> https://github.com/cdh4u/draft-sdp-bundle/pull/11
>
>
> Regards,
>
> Christer
>
>
> On 12/10/16 12:32, "mmusic on behalf of Christer Holmberg"
> <mmusic-bounces@ietf.org on behalf of christer.holmberg@ericsson.com>
> wrote:
>
> >Hi,
> >
> >Based on the discussions, and input that has been provided, are people ok
> >with adding the text Magnus suggested (see below) to the Security
> >Considerations of BUNDLE?
> >
> >Regards,
> >
> >Christer
> >
> >
> >>>> The identfication-tag when included in the RTP MID SDES item,
> >>>> independent of transport, RTCP SDES packet or RTP header extension,
> >>>> can expose the value to parties beyond the signaling chain.
> >>>> Therefore, the identification-tag MUST NOT contain any user related
> >>>> information. However, the implementation's method for generating
> >>>> identfication-tags combined with hardware configuration can enable
> >>>> fingerprinting of the endpoint device and thus its user. As the
> >>>> identification-tag is also used to route the media stream to the
> >>>> right application functionality it is also important that the value
> >>>> received is the one intended by the sender, thus integrity and the
> >>>> authenticity of the source are important to prevent denial of
> >>>> service on the application. At least to prevent third parties from
> >>>> modifying the identification-tag value.
> >>>>
> >>>> Due to the security risks associated with the MID values in RTP and
> >>>> RTCP it is strongly RECOMMENDED that the MID SDES item is both
> >>>> confidentiality protected as well as source authenticated when
> >>>> transported in either RTCP or RTP header extensions. The security
> >>>> mechanisms used SHALL provide corresponding levels of security for
> >>>> both RTP header extensions and RTCP. Confidentiality mechanisms for
> >>>> RTP/RTCP are discussed in Options for Securing RTP Sessions
> >>>> [RFC7201], for example SRTP [RFC3711] with SRTCP encryption enabled
> >>>> combined with [RFC6904] can provide the necessary security
> >>>> functions.
> >
> >_______________________________________________
> >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
>

--94eb2c0b0f68761918053eade571
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I don&#39;t think there is anything like consensus for a 2=
919-level RECOMMENDED to encrypt the MID.</div><div class=3D"gmail_extra"><=
br><div class=3D"gmail_quote">On Wed, Oct 12, 2016 at 4:47 AM, Christer Hol=
mberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.co=
m" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">Pull request created.<br>
<br>
<a href=3D"https://github.com/cdh4u/draft-sdp-bundle/pull/11" rel=3D"norefe=
rrer" target=3D"_blank">https://github.com/cdh4u/<wbr>draft-sdp-bundle/pull=
/11</a><br>
<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
<br>
On 12/10/16 12:32, &quot;mmusic on behalf of Christer Holmberg&quot;<br>
&lt;<a href=3D"mailto:mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a> =
on behalf of <a href=3D"mailto:christer.holmberg@ericsson.com">christer.hol=
mberg@ericsson.com</a><wbr>&gt;<br>
wrote:<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt;Hi,<br>
&gt;<br>
&gt;Based on the discussions, and input that has been provided, are people =
ok<br>
&gt;with adding the text Magnus suggested (see below) to the Security<br>
&gt;Considerations of BUNDLE?<br>
&gt;<br>
&gt;Regards,<br>
&gt;<br>
&gt;Christer<br>
&gt;<br>
&gt;<br>
&gt;&gt;&gt;&gt; The identfication-tag when included in the RTP MID SDES it=
em,<br>
&gt;&gt;&gt;&gt; independent of transport, RTCP SDES packet or RTP header e=
xtension,<br>
&gt;&gt;&gt;&gt; can expose the value to parties beyond the signaling chain=
.<br>
&gt;&gt;&gt;&gt; Therefore, the identification-tag MUST NOT contain any use=
r related<br>
&gt;&gt;&gt;&gt; information. However, the implementation&#39;s method for =
generating<br>
&gt;&gt;&gt;&gt; identfication-tags combined with hardware configuration ca=
n enable<br>
&gt;&gt;&gt;&gt; fingerprinting of the endpoint device and thus its user. A=
s the<br>
&gt;&gt;&gt;&gt; identification-tag is also used to route the media stream =
to the<br>
&gt;&gt;&gt;&gt; right application functionality it is also important that =
the value<br>
&gt;&gt;&gt;&gt; received is the one intended by the sender, thus integrity=
 and the<br>
&gt;&gt;&gt;&gt; authenticity of the source are important to prevent denial=
 of<br>
&gt;&gt;&gt;&gt; service on the application. At least to prevent third part=
ies from<br>
&gt;&gt;&gt;&gt; modifying the identification-tag value.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Due to the security risks associated with the MID values i=
n RTP and<br>
&gt;&gt;&gt;&gt; RTCP it is strongly RECOMMENDED that the MID SDES item is =
both<br>
&gt;&gt;&gt;&gt; confidentiality protected as well as source authenticated =
when<br>
&gt;&gt;&gt;&gt; transported in either RTCP or RTP header extensions. The s=
ecurity<br>
&gt;&gt;&gt;&gt; mechanisms used SHALL provide corresponding levels of secu=
rity for<br>
&gt;&gt;&gt;&gt; both RTP header extensions and RTCP. Confidentiality mecha=
nisms for<br>
&gt;&gt;&gt;&gt; RTP/RTCP are discussed in Options for Securing RTP Session=
s<br>
&gt;&gt;&gt;&gt; [RFC7201], for example SRTP [RFC3711] with SRTCP encryptio=
n enabled<br>
&gt;&gt;&gt;&gt; combined with [RFC6904] can provide the necessary security=
<br>
&gt;&gt;&gt;&gt; functions.<br>
&gt;<br>
&gt;_____________________________<wbr>__________________<br>
&gt;mmusic mailing list<br>
&gt;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a=
><br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div>

--94eb2c0b0f68761918053eade571--


From nobody Wed Oct 12 12:51:07 2016
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 D45C51294F4 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 12:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 Sg2zslIPjlkW for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 12:51:04 -0700 (PDT)
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 4CA221294D0 for <mmusic@ietf.org>; Wed, 12 Oct 2016 12:51:04 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-31-57fe94261042
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.183.42]) by  (Symantec Mail Security) with SMTP id CD.69.02458.6249EF75; Wed, 12 Oct 2016 21:51:02 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.03.0319.002; Wed, 12 Oct 2016 21:51:00 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Thomas Stach <thomass.stach@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
Thread-Index: AQHSHxIL5dxB//uBWky8GjwyA0+P66CZ76sAgAjKcACAAD99AIABlqsAgACw0bA=
Date: Wed, 12 Oct 2016 19:51:00 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD668A9@ESESSMB209.ericsson.se>
References: <D41AC393.10727%christer.holmberg@ericsson.com> <bc713d1a-acdb-af95-5391-b3e244e1126d@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1B3B2@ESESSMB209.ericsson.se> <e44e62ff-1b0d-9180-2872-b98c84cbb6f6@gmail.com> <D4226F4E.10D4F%christer.holmberg@ericsson.com> <7c516d72-ef2a-e928-dc4a-ee77298ebb22@gmail.com>
In-Reply-To: <7c516d72-ef2a-e928-dc4a-ee77298ebb22@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrILMWRmVeSWpSXmKPExsUyM2K7lq7alH/hBrsWK1hMXf6YxeLTia1M DkweO2fdZfdYsuQnUwBTFJdNSmpOZllqkb5dAlfG2j3iBXeMKg7um8HYwHhWo4uRk0NCwETi 2ezvLF2MXBxCAusZJWZOO8sO4SxhlJh08QZrFyMHB5uAhUT3P22QBhGBQInPZ44zgdQIC0xl lNjasZYZIjGNUeLpUisI209i3cGnbCA2i4CqxPV/x9hBbF4BX4nLrxuZIBacYpK4vuMgE0iC U8BWYvvTg2BFjAJiEt9PrQGLMwuIS9x6Mp8J4lQBiSV7zjND2KISLx//Y4WwlSTWHt7OAlGv J3Fj6hQ2CFtbYtnC18wQiwUlTs58wjKBUWQWkrGzkLTMQtIyC0nLAkaWVYyixanFxbnpRkZ6 qUWZycXF+Xl6eaklmxiBEXFwy2+rHYwHnzseYhTgYFTi4VWo+hcuxJpYVlyZe4hRgoNZSYRX pBcoxJuSWFmVWpQfX1Sak1p8iFGag0VJnNds5f1wIYH0xJLU7NTUgtQimCwTB6dUA2P51k0H 3DdxeVyqqKidVD1Jbt/5kpslhfc7QiNNbP8/+zkrs7xdTrlVVnZf+Kb4nPDD2ceecFy98Orx vFY/r5qnCx+dmybKnTt3oUXNzYQPdx9E3JrdwhberqUm9Uno24zLP4q3sWb73DEyfbDhzq29 nnUq+Yf+nbhku2VZdJNWmkTrur0SDNeUWIozEg21mIuKEwFq/XKphAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jMgGwpYrdrCzdKxQ6u6ZIOYzzDU>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 19:51:07 -0000

Hi,

>>>>>>> It has been suggested that removal of candidates should not be=20
>>>>>>> part of trickle, but rather be defined in a separate future extensi=
on draft.
>>>>>>> The comments below are based on that such "extension" may exist at=
=20
>>>>>>> some point.
>>>>>>>
>>>>>>> The text in section 4.2 says:
>>>>>>>       "In every INFO request agents MUST include all local=20
>>>>>>>       candidates they have signaled previously.  This is necessary =
in order to=20
>>>>>>>       more easily avoid problems that would arise from unreliable t=
ransports.  Mis-
>>>>>>>       ordering can be detected through the CSeq: header field in th=
e INFO
>>>>>>>       request.  As a consequence candidates cannot be removed unles=
s an ICE
>>>>>>>       restart is performed.  Note that extension might be specified=
 in the
>>>>>>>       future that enable such removal without a restart."
>>>>>>> Q1: Assuming someone does define an extension which allows removal=
=20
>>>>>>> of candidates without a restart, do such candidates still have to=20
>>>>>>> be included in the INFO, as they have been "previously signalled"?
>>>>>>
>>>>>> This would have to clarified in that future extension document=20
>>>>>> together with corresponding backward compatibility issues and/or=20
>>>>>> indication of support for such an extension. I don't want to do=20
>>>>>> design here, but a=3Dice-options might be something to look at.
>>>>>
>>>>> How you indicate support of such extension is outside the scope of=20
>>>>> this thread. I want to clarify the exact semantics of a candidate in =
an INFO.
>>> Again, I agree that how candidates are removed is outside the scope.=20
>>> But, that doesn=B9t change the fact that trickle needs to define exactl=
y=20
>>> what the semantic of the signalled candidates. I do NOT want a future=20
>>> extension to change that semantic.
> I don't how you want to preclude an arbitrary future extension to do such=
 a change,=20
> but in case of a "candidate removal" extension I don't see a problem with=
 the current >concept.
> The current concept is (as I understand it):
> - An INFO always carries all candidates that belong to the currently vali=
d ufrag/pwd.

But that is not what the text is saying. "That belong" is not the same as "=
Previously signalled". "That belong" means they are still valid/active - at=
 least in my ears.

> - We have the restriction that in subsequent INFOs the number of these ca=
ndidates can
>  only increase or remain constant until end-of-candidates is signalled.

I think we should remove that restriction.

Even if we don't have a defined mechanism for removing candidates, they can=
 disappear anyway. The TURN server may crash, etc. Why should we keep signa=
lling such candidates? We could of course do an ICE re-start whenever a can=
didate is removed (one way or another), but I don't think we want to do tha=
t...

But, again, by ONLY signalling the added candidates we don't have the issue=
 with removed candidates to begin with.=20

>If someone wants to define a "candidate removal" extension, he/she can kee=
p the semantics of the first item, i.e.
>- An INFO always carries all candidates that belong to the currently valid=
 ufrag/pwd.

Again, I don't think that is what "previously signalled" means.

>  and would have to do the following
>- modify the constraint to something like  "In subsequent INFOs the number=
 of these candidates can increase, _decrease_ or remain constant "

I see no reason to have that constraint to begin with.

>- define how support for the "candidate removal" extension is negotiated  =
and how backward compatibility is achieved
>-  define how candidates are actually removed

I agree the negotiation and mechanism should be defined elsewhere.

But, again again, I'd like to hear whether people would be ok to only signa=
l the added candidates in INFO.

<snip/>
>>>> Also, an "extension" could have removed candidiates since the=20
>>>> ufrag/pwd was signalled. So, you cannot simply say "since current=20
>>>> ufrag/pwd was signalled". You also need to say something like "and=20
>>>> are still active/in use", or something like that.
>>> Why would I have to?
>> Because I assume we only want to signal candidates that are still in use=
.
>>
>> That is what I meant by the semantic comment earlier. I don=B9t want the=
=20
>> semantic of a signalled candidate to be =B3It was signalled at some=20
>> point with the current ufrag/pwd, but it may no longer be in use=B2. I=20
>> want it to be =B3It was signalled at some point with the current=20
>> ufrag/pwd, and it is still in use=B2.
>Does my answer from above work for you?

Partly. But, again, I don't think what you are saying is what is written in=
 the draft :)

>>>>>> Q2: What if an INFO does NOT contain a local candidate that has=20
>>>>>> previously been signaled? Do we assume it has been removed using=20
>>>>>> some "extension"? Do we assume it's still there?
>>>>> We could either treat this case as an error and ignore the content=20
>>>>> of that INFO.
>>>>> Probably not the best idea, e.g. in case that a=3Dend-of-candidates=20
>>>>> was included.
>>>>> Or we can assume (in absence of any "removal extension") that it is=20
>>>>> still there. That would allow to still make use of any newly=20
>>>>> trickled candidates in such an INFO. This makes more sense to me.
>>>>> If this is agreable I would be happy to put corresponding text into=20
>>>>> section 4.2.
>>>> ...or, we could go back to my previous proposal, and say that we=20
>>>> *ONLY* signal the new candidates, and that the INFO has no impact on=20
>>>> any other candidates :)
>>> Well, there is consensus since  2013 that the INFO carries all candidat=
es.
>>> It was one outcome of the thread that started here
>>> https://mailarchive.ietf.org/arch/search/?email_list=3Dmmusic&gbt=3D1&i=
nd
>>> ex=3DT7R18RumQQJrmtHRh1lmcf9wcqs
>>>
>>> I can't remember that this consensus was not challenged since then,=20
>>> but I guess that all implementations will expect all candidates in the =
INFO.
>> We didn=B9t discuss removal of candidates back in 2013, so I think we=20
>> shall re-ask the community.
>I still think that the current concept works, so will you want to ask that=
 then?

I am asking as we speak. Anyone who does not agree with the suggestion shou=
ld speak up :)

Regards,

Christer


From nobody Wed Oct 12 12:54:43 2016
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 66DB112965D for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 12:54:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 XJY0CeSxj9Nj for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 12:54:39 -0700 (PDT)
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 CCD7F1294F4 for <mmusic@ietf.org>; Wed, 12 Oct 2016 12:54:38 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-f6-57fe94fc794e
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by  (Symantec Mail Security) with SMTP id 97.D9.02458.CF49EF75; Wed, 12 Oct 2016 21:54:37 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0319.002; Wed, 12 Oct 2016 21:54:35 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
Thread-Index: AQHSH9ATPAZhiMqWXkq+6ZcG+jYe1aCbTNuAgACLuoCAALOQAIAIHeaAgAAlrQCAACKGAIAAUtbw
Date: Wed, 12 Oct 2016 19:54:33 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD668D1@ESESSMB209.ericsson.se>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com> <D423DEE7.1101D%christer.holmberg@ericsson.com> <D423FEEE.11074%christer.holmberg@ericsson.com> <CABcZeBO7b3XGRTCzN4-Z-6=8sTD3nrr8HtgN1q9np-hZ3tqbMQ@mail.gmail.com>
In-Reply-To: <CABcZeBO7b3XGRTCzN4-Z-6=8sTD3nrr8HtgN1q9np-hZ3tqbMQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BD668D1ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOIsWRmVeSWpSXmKPExsUyM2K7se7fKf/CDRpO81useH2O3eLD+h+M FlOXP2axWLHhAKsDi8ff9x+YPJYs+cnkcfn8R0aPyY/bmANYorhsUlJzMstSi/TtErgyjt1Z xlYwqa7izJsFTA2MD6q6GDk4JARMJE5uU+pi5OIQEljPKPHrzWIWCGcJo8SJexNZQIrYBCwk uv9pdzFycogIKEj8+nMCrIZZYBmjRP+UbSwgCWGBfIkJe26xQRQVSPw/1ccKYUdJ/Jw4lxHE ZhFQlfjU1wsW5xXwlVi9/grUsiZmiasr57KDLOMUCJToWJQFUsMoICbx/dQaJhCbWUBc4taT +WC2hICAxJI955khbFGJl4//sULYShJrD29ngajPl2j6uoURYpegxMmZT1gmMIrMQjJqFpKy WUjKZgFdwSygKbF+lz5EiaLElO6H7BC2hkTrnLnsyOILGNlXMYoWpxYX56YbGemlFmUmFxfn 5+nlpZZsYgRG38Etv612MB587niIUYCDUYmHV6HqX7gQa2JZcWXuIUYJDmYlEV6RXqAQb0pi ZVVqUX58UWlOavEhRmkOFiVxXrOV98OFBNITS1KzU1MLUotgskwcnFINjJqi4YvTFNmelF59 smTDFo6Za9vT+vYHikzatvzQlvj7jl/6ev/Ex222fV3GIGJq1jbB8vJHpw3cLIKfJFPXP9wm sDuiNkVpi+vsqpAFiqr9P9Vcju03eBgYyL7k7kmLJa/CI6+8reVdus+lRFkgT/pa7/5T+7oP dv2fG5iseJ2r3mpVa3lgmRJLcUaioRZzUXEiAJSsp4y6AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/dBPYQO8f4Wd5ntb8PKJiwomBYYk>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Cullen Jennings <fluffy@iii.ca>, "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 19:54:41 -0000

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

SGksDQoNCk15IGludGVudGlvbiB3YXMgbm90IHRvIGNsYWltIHdlIGhhdmUgY29uc2Vuc3VzLiBJ
IGp1c3Qgd2FudGVkIHRvIHB1dCBmb3J3YXJkIHNvbWUgdGV4dCB0byBzZWUgd2hldGhlciBpdOKA
mXMgc29tZXRoaW5nIHdlIGNhbiB3b3JrIG9uLg0KDQpPciwgd291bGQgeW91IHByZWZlciB0byBu
b3Qgc2F5aW5nIGFueXRoaW5nPw0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQpGcm9tOiBtbXVz
aWMgW21haWx0bzptbXVzaWMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEVyaWMgUmVz
Y29ybGENClNlbnQ6IDEyIE9jdG9iZXIgMjAxNiAxOTo1Nw0KVG86IENocmlzdGVyIEhvbG1iZXJn
IDxjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+DQpDYzogTWFnbnVzIFdlc3Rlcmx1bmQg
PG1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbT47IFBhdWwgS3l6aXZhdCA8cGt5eml2YXRA
YWx1bS5taXQuZWR1PjsgbW11c2ljQGlldGYub3JnOyBDdWxsZW4gSmVubmluZ3MgPGZsdWZmeUBp
aWkuY2E+DQpTdWJqZWN0OiBSZTogW01NVVNJQ10gUmV2aWV3IG9mIGRyYWZ0LWlldGYtbW11c2lj
LXNkcC1idW5kbGUtbmVnb3RpYXRpb24tMzIgLSBNYWdudXMnIGNvbW1lbnRzIC0gTUlEIHNlY3Vy
aXR5DQoNCkkgZG9uJ3QgdGhpbmsgdGhlcmUgaXMgYW55dGhpbmcgbGlrZSBjb25zZW5zdXMgZm9y
IGEgMjkxOS1sZXZlbCBSRUNPTU1FTkRFRCB0byBlbmNyeXB0IHRoZSBNSUQuDQoNCk9uIFdlZCwg
T2N0IDEyLCAyMDE2IGF0IDQ6NDcgQU0sIENocmlzdGVyIEhvbG1iZXJnIDxjaHJpc3Rlci5ob2xt
YmVyZ0Blcmljc3Nvbi5jb208bWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4+
IHdyb3RlOg0KUHVsbCByZXF1ZXN0IGNyZWF0ZWQuDQoNCmh0dHBzOi8vZ2l0aHViLmNvbS9jZGg0
dS9kcmFmdC1zZHAtYnVuZGxlL3B1bGwvMTENCg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoN
Ck9uIDEyLzEwLzE2IDEyOjMyLCAibW11c2ljIG9uIGJlaGFsZiBvZiBDaHJpc3RlciBIb2xtYmVy
ZyINCjxtbXVzaWMtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86bW11c2ljLWJvdW5jZXNAaWV0Zi5v
cmc+IG9uIGJlaGFsZiBvZiBjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb208bWFpbHRvOmNo
cmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4+DQp3cm90ZToNCg0KPkhpLA0KPg0KPkJhc2Vk
IG9uIHRoZSBkaXNjdXNzaW9ucywgYW5kIGlucHV0IHRoYXQgaGFzIGJlZW4gcHJvdmlkZWQsIGFy
ZSBwZW9wbGUgb2sNCj53aXRoIGFkZGluZyB0aGUgdGV4dCBNYWdudXMgc3VnZ2VzdGVkIChzZWUg
YmVsb3cpIHRvIHRoZSBTZWN1cml0eQ0KPkNvbnNpZGVyYXRpb25zIG9mIEJVTkRMRT8NCj4NCj5S
ZWdhcmRzLA0KPg0KPkNocmlzdGVyDQo+DQo+DQo+Pj4+IFRoZSBpZGVudGZpY2F0aW9uLXRhZyB3
aGVuIGluY2x1ZGVkIGluIHRoZSBSVFAgTUlEIFNERVMgaXRlbSwNCj4+Pj4gaW5kZXBlbmRlbnQg
b2YgdHJhbnNwb3J0LCBSVENQIFNERVMgcGFja2V0IG9yIFJUUCBoZWFkZXIgZXh0ZW5zaW9uLA0K
Pj4+PiBjYW4gZXhwb3NlIHRoZSB2YWx1ZSB0byBwYXJ0aWVzIGJleW9uZCB0aGUgc2lnbmFsaW5n
IGNoYWluLg0KPj4+PiBUaGVyZWZvcmUsIHRoZSBpZGVudGlmaWNhdGlvbi10YWcgTVVTVCBOT1Qg
Y29udGFpbiBhbnkgdXNlciByZWxhdGVkDQo+Pj4+IGluZm9ybWF0aW9uLiBIb3dldmVyLCB0aGUg
aW1wbGVtZW50YXRpb24ncyBtZXRob2QgZm9yIGdlbmVyYXRpbmcNCj4+Pj4gaWRlbnRmaWNhdGlv
bi10YWdzIGNvbWJpbmVkIHdpdGggaGFyZHdhcmUgY29uZmlndXJhdGlvbiBjYW4gZW5hYmxlDQo+
Pj4+IGZpbmdlcnByaW50aW5nIG9mIHRoZSBlbmRwb2ludCBkZXZpY2UgYW5kIHRodXMgaXRzIHVz
ZXIuIEFzIHRoZQ0KPj4+PiBpZGVudGlmaWNhdGlvbi10YWcgaXMgYWxzbyB1c2VkIHRvIHJvdXRl
IHRoZSBtZWRpYSBzdHJlYW0gdG8gdGhlDQo+Pj4+IHJpZ2h0IGFwcGxpY2F0aW9uIGZ1bmN0aW9u
YWxpdHkgaXQgaXMgYWxzbyBpbXBvcnRhbnQgdGhhdCB0aGUgdmFsdWUNCj4+Pj4gcmVjZWl2ZWQg
aXMgdGhlIG9uZSBpbnRlbmRlZCBieSB0aGUgc2VuZGVyLCB0aHVzIGludGVncml0eSBhbmQgdGhl
DQo+Pj4+IGF1dGhlbnRpY2l0eSBvZiB0aGUgc291cmNlIGFyZSBpbXBvcnRhbnQgdG8gcHJldmVu
dCBkZW5pYWwgb2YNCj4+Pj4gc2VydmljZSBvbiB0aGUgYXBwbGljYXRpb24uIEF0IGxlYXN0IHRv
IHByZXZlbnQgdGhpcmQgcGFydGllcyBmcm9tDQo+Pj4+IG1vZGlmeWluZyB0aGUgaWRlbnRpZmlj
YXRpb24tdGFnIHZhbHVlLg0KPj4+Pg0KPj4+PiBEdWUgdG8gdGhlIHNlY3VyaXR5IHJpc2tzIGFz
c29jaWF0ZWQgd2l0aCB0aGUgTUlEIHZhbHVlcyBpbiBSVFAgYW5kDQo+Pj4+IFJUQ1AgaXQgaXMg
c3Ryb25nbHkgUkVDT01NRU5ERUQgdGhhdCB0aGUgTUlEIFNERVMgaXRlbSBpcyBib3RoDQo+Pj4+
IGNvbmZpZGVudGlhbGl0eSBwcm90ZWN0ZWQgYXMgd2VsbCBhcyBzb3VyY2UgYXV0aGVudGljYXRl
ZCB3aGVuDQo+Pj4+IHRyYW5zcG9ydGVkIGluIGVpdGhlciBSVENQIG9yIFJUUCBoZWFkZXIgZXh0
ZW5zaW9ucy4gVGhlIHNlY3VyaXR5DQo+Pj4+IG1lY2hhbmlzbXMgdXNlZCBTSEFMTCBwcm92aWRl
IGNvcnJlc3BvbmRpbmcgbGV2ZWxzIG9mIHNlY3VyaXR5IGZvcg0KPj4+PiBib3RoIFJUUCBoZWFk
ZXIgZXh0ZW5zaW9ucyBhbmQgUlRDUC4gQ29uZmlkZW50aWFsaXR5IG1lY2hhbmlzbXMgZm9yDQo+
Pj4+IFJUUC9SVENQIGFyZSBkaXNjdXNzZWQgaW4gT3B0aW9ucyBmb3IgU2VjdXJpbmcgUlRQIFNl
c3Npb25zDQo+Pj4+IFtSRkM3MjAxXSwgZm9yIGV4YW1wbGUgU1JUUCBbUkZDMzcxMV0gd2l0aCBT
UlRDUCBlbmNyeXB0aW9uIGVuYWJsZWQNCj4+Pj4gY29tYmluZWQgd2l0aCBbUkZDNjkwNF0gY2Fu
IHByb3ZpZGUgdGhlIG5lY2Vzc2FyeSBzZWN1cml0eQ0KPj4+PiBmdW5jdGlvbnMuDQo+DQo+X19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5tbXVzaWMgbWFp
bGluZyBsaXN0DQo+bW11c2ljQGlldGYub3JnPG1haWx0bzptbXVzaWNAaWV0Zi5vcmc+DQo+aHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMNCg0KX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1tdXNpYyBtYWlsaW5nIGxpc3QN
Cm1tdXNpY0BpZXRmLm9yZzxtYWlsdG86bW11c2ljQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHls
ZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0K
CW1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXpl
OjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30N
CmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0t
W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRt
YXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4N
CjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRh
PSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJv
ZHkgbGFuZz0iRU4tR0IiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0i
V29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5IaSw8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3
RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPk15IGludGVudGlvbiB3YXMgbm90IHRvIGNsYWltIHdl
IGhhdmUgY29uc2Vuc3VzLiBJIGp1c3Qgd2FudGVkIHRvIHB1dCBmb3J3YXJkIHNvbWUgdGV4dCB0
byBzZWUgd2hldGhlciBpdOKAmXMgc29tZXRoaW5nIHdlIGNhbiB3b3JrIG9uLjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3
RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+T3IsIHdvdWxkIHlvdSBwcmVmZXIgdG8gbm90
IHNheWluZyBhbnl0aGluZz88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpF
Ti1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
PlJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5DaHJpc3Rl
cjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIG5hbWU9Il9N
YWlsRW5kQ29tcG9zZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3Qt
bGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvYT48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5Gcm9tOjwvc3Bh
bj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IG1tdXNpYyBbbWFpbHRvOm1tdXNp
Yy1ib3VuY2VzQGlldGYub3JnXQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5FcmljIFJlc2NvcmxhPGJy
Pg0KPGI+U2VudDo8L2I+IDEyIE9jdG9iZXIgMjAxNiAxOTo1Nzxicj4NCjxiPlRvOjwvYj4gQ2hy
aXN0ZXIgSG9sbWJlcmcgJmx0O2NocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSZndDs8YnI+
DQo8Yj5DYzo8L2I+IE1hZ251cyBXZXN0ZXJsdW5kICZsdDttYWdudXMud2VzdGVybHVuZEBlcmlj
c3Nvbi5jb20mZ3Q7OyBQYXVsIEt5eml2YXQgJmx0O3BreXppdmF0QGFsdW0ubWl0LmVkdSZndDs7
IG1tdXNpY0BpZXRmLm9yZzsgQ3VsbGVuIEplbm5pbmdzICZsdDtmbHVmZnlAaWlpLmNhJmd0Ozxi
cj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW01NVVNJQ10gUmV2aWV3IG9mIGRyYWZ0LWlldGYtbW11
c2ljLXNkcC1idW5kbGUtbmVnb3RpYXRpb24tMzIgLSBNYWdudXMnIGNvbW1lbnRzIC0gTUlEIHNl
Y3VyaXR5PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBkb24ndCB0aGlu
ayB0aGVyZSBpcyBhbnl0aGluZyBsaWtlIGNvbnNlbnN1cyBmb3IgYSAyOTE5LWxldmVsIFJFQ09N
TUVOREVEIHRvIGVuY3J5cHQgdGhlIE1JRC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPk9uIFdlZCwgT2N0IDEyLCAyMDE2IGF0IDQ6NDcgQU0sIENocmlzdGVy
IEhvbG1iZXJnICZsdDs8YSBocmVmPSJtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24u
Y29tIiB0YXJnZXQ9Il9ibGFuayI+Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPC9hPiZn
dDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0
O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+UHVsbCByZXF1ZXN0IGNyZWF0ZWQuPGJyPg0KPGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly9naXRo
dWIuY29tL2NkaDR1L2RyYWZ0LXNkcC1idW5kbGUvcHVsbC8xMSIgdGFyZ2V0PSJfYmxhbmsiPmh0
dHBzOi8vZ2l0aHViLmNvbS9jZGg0dS9kcmFmdC1zZHAtYnVuZGxlL3B1bGwvMTE8L2E+PGJyPg0K
PGJyPg0KPGJyPg0KUmVnYXJkcyw8YnI+DQo8YnI+DQpDaHJpc3Rlcjxicj4NCjxicj4NCjxicj4N
Ck9uIDEyLzEwLzE2IDEyOjMyLCAmcXVvdDttbXVzaWMgb24gYmVoYWxmIG9mIENocmlzdGVyIEhv
bG1iZXJnJnF1b3Q7PGJyPg0KJmx0OzxhIGhyZWY9Im1haWx0bzptbXVzaWMtYm91bmNlc0BpZXRm
Lm9yZyI+bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmc8L2E+IG9uIGJlaGFsZiBvZg0KPGEgaHJlZj0i
bWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSI+Y2hyaXN0ZXIuaG9sbWJlcmdA
ZXJpY3Nzb24uY29tPC9hPiZndDs8YnI+DQp3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KJmd0O0hpLDxicj4NCiZndDs8YnI+DQom
Z3Q7QmFzZWQgb24gdGhlIGRpc2N1c3Npb25zLCBhbmQgaW5wdXQgdGhhdCBoYXMgYmVlbiBwcm92
aWRlZCwgYXJlIHBlb3BsZSBvazxicj4NCiZndDt3aXRoIGFkZGluZyB0aGUgdGV4dCBNYWdudXMg
c3VnZ2VzdGVkIChzZWUgYmVsb3cpIHRvIHRoZSBTZWN1cml0eTxicj4NCiZndDtDb25zaWRlcmF0
aW9ucyBvZiBCVU5ETEU/PGJyPg0KJmd0Ozxicj4NCiZndDtSZWdhcmRzLDxicj4NCiZndDs8YnI+
DQomZ3Q7Q2hyaXN0ZXI8YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsg
VGhlIGlkZW50ZmljYXRpb24tdGFnIHdoZW4gaW5jbHVkZWQgaW4gdGhlIFJUUCBNSUQgU0RFUyBp
dGVtLDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgaW5kZXBlbmRlbnQgb2YgdHJhbnNwb3J0LCBSVENQ
IFNERVMgcGFja2V0IG9yIFJUUCBoZWFkZXIgZXh0ZW5zaW9uLDxicj4NCiZndDsmZ3Q7Jmd0OyZn
dDsgY2FuIGV4cG9zZSB0aGUgdmFsdWUgdG8gcGFydGllcyBiZXlvbmQgdGhlIHNpZ25hbGluZyBj
aGFpbi48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IFRoZXJlZm9yZSwgdGhlIGlkZW50aWZpY2F0aW9u
LXRhZyBNVVNUIE5PVCBjb250YWluIGFueSB1c2VyIHJlbGF0ZWQ8YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7IGluZm9ybWF0aW9uLiBIb3dldmVyLCB0aGUgaW1wbGVtZW50YXRpb24ncyBtZXRob2QgZm9y
IGdlbmVyYXRpbmc8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IGlkZW50ZmljYXRpb24tdGFncyBjb21i
aW5lZCB3aXRoIGhhcmR3YXJlIGNvbmZpZ3VyYXRpb24gY2FuIGVuYWJsZTxicj4NCiZndDsmZ3Q7
Jmd0OyZndDsgZmluZ2VycHJpbnRpbmcgb2YgdGhlIGVuZHBvaW50IGRldmljZSBhbmQgdGh1cyBp
dHMgdXNlci4gQXMgdGhlPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyBpZGVudGlmaWNhdGlvbi10YWcg
aXMgYWxzbyB1c2VkIHRvIHJvdXRlIHRoZSBtZWRpYSBzdHJlYW0gdG8gdGhlPGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyByaWdodCBhcHBsaWNhdGlvbiBmdW5jdGlvbmFsaXR5IGl0IGlzIGFsc28gaW1w
b3J0YW50IHRoYXQgdGhlIHZhbHVlPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyByZWNlaXZlZCBpcyB0
aGUgb25lIGludGVuZGVkIGJ5IHRoZSBzZW5kZXIsIHRodXMgaW50ZWdyaXR5IGFuZCB0aGU8YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7IGF1dGhlbnRpY2l0eSBvZiB0aGUgc291cmNlIGFyZSBpbXBvcnRh
bnQgdG8gcHJldmVudCBkZW5pYWwgb2Y8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IHNlcnZpY2Ugb24g
dGhlIGFwcGxpY2F0aW9uLiBBdCBsZWFzdCB0byBwcmV2ZW50IHRoaXJkIHBhcnRpZXMgZnJvbTxi
cj4NCiZndDsmZ3Q7Jmd0OyZndDsgbW9kaWZ5aW5nIHRoZSBpZGVudGlmaWNhdGlvbi10YWcgdmFs
dWUuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgRHVlIHRvIHRo
ZSBzZWN1cml0eSByaXNrcyBhc3NvY2lhdGVkIHdpdGggdGhlIE1JRCB2YWx1ZXMgaW4gUlRQIGFu
ZDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgUlRDUCBpdCBpcyBzdHJvbmdseSBSRUNPTU1FTkRFRCB0
aGF0IHRoZSBNSUQgU0RFUyBpdGVtIGlzIGJvdGg8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IGNvbmZp
ZGVudGlhbGl0eSBwcm90ZWN0ZWQgYXMgd2VsbCBhcyBzb3VyY2UgYXV0aGVudGljYXRlZCB3aGVu
PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyB0cmFuc3BvcnRlZCBpbiBlaXRoZXIgUlRDUCBvciBSVFAg
aGVhZGVyIGV4dGVuc2lvbnMuIFRoZSBzZWN1cml0eTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgbWVj
aGFuaXNtcyB1c2VkIFNIQUxMIHByb3ZpZGUgY29ycmVzcG9uZGluZyBsZXZlbHMgb2Ygc2VjdXJp
dHkgZm9yPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyBib3RoIFJUUCBoZWFkZXIgZXh0ZW5zaW9ucyBh
bmQgUlRDUC4gQ29uZmlkZW50aWFsaXR5IG1lY2hhbmlzbXMgZm9yPGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyBSVFAvUlRDUCBhcmUgZGlzY3Vzc2VkIGluIE9wdGlvbnMgZm9yIFNlY3VyaW5nIFJUUCBT
ZXNzaW9uczxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgW1JGQzcyMDFdLCBmb3IgZXhhbXBsZSBTUlRQ
IFtSRkMzNzExXSB3aXRoIFNSVENQIGVuY3J5cHRpb24gZW5hYmxlZDxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsgY29tYmluZWQgd2l0aCBbUkZDNjkwNF0gY2FuIHByb3ZpZGUgdGhlIG5lY2Vzc2FyeSBz
ZWN1cml0eTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgZnVuY3Rpb25zLjxicj4NCiZndDs8YnI+DQom
Z3Q7X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQom
Z3Q7bW11c2ljIG1haWxpbmcgbGlzdDxicj4NCiZndDs8YSBocmVmPSJtYWlsdG86bW11c2ljQGll
dGYub3JnIj5tbXVzaWNAaWV0Zi5vcmc8L2E+PGJyPg0KJmd0OzxhIGhyZWY9Imh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWM8L2E+PGJyPg0KPGJyPg0KX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQptbXVzaWMg
bWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOm1tdXNpY0BpZXRmLm9yZyI+bW11c2lj
QGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vbW11c2ljIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9tbXVzaWM8L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_7594FB04B1934943A5C02806D1A2204B4BD668D1ESESSMB209erics_--


From nobody Wed Oct 12 15:23:31 2016
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 79F831293FE for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 15:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.517
X-Spam-Level: 
X-Spam-Status: No, score=-17.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, 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 Pr6W2FP-PLk6 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 15:23:28 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0097A128B44 for <mmusic@ietf.org>; Wed, 12 Oct 2016 15:23:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1088; q=dns/txt; s=iport; t=1476311007; x=1477520607; h=to:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=DSSuhS2IUes5yO9JZffY/YeFtArGZMmFkMtXMvRijC0=; b=mU0Z5iorX1+cCn3JXEf/++gkc512hdBTdKXGOPbHOZK6VlUnARdKByTw F5sbnrfDZljN56EUhYTJ+E2giaMP2AiFfzJ1t/+EvsZRCKctn3rO7Ukft R0QT9hmgObCEXyGcZi6qdDfMgNVsYpkOmvWZqcLC+q6K6eWvTnj+1WBtz o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AXAwAwt/5X/40NJK1cGwEBAQMBAQEJA?= =?us-ascii?q?QEBgzwBAQEBAR2BAY4Fo3KEX4JnggyIHDgUAQIBAQEBAQEBXieFCxV2AiYCXw0?= =?us-ascii?q?IAQGITKZPj2yNCAEBAQEGAgElgQeFNoF9CIobglsBBJoCizyDYl+BboRngxSGD?= =?us-ascii?q?IcQiWgeNk6EfiKJGAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.31,485,1473120000"; d="scan'208";a="157301258"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 12 Oct 2016 22:23:27 +0000
Received: from [10.155.84.246] (dhcp-10-155-84-246.cisco.com [10.155.84.246]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u9CMNQ5i001710 for <mmusic@ietf.org>; Wed, 12 Oct 2016 22:23:27 GMT
To: mmusic <mmusic@ietf.org>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
Date: Wed, 12 Oct 2016 18:23:26 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/VBEx6OX5e9saCbRUY8XtX7a2c54>
Subject: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 22:23:29 -0000

Greetings

There has been quite a bit of discussion on 
draft-ietf-mmusic-4572-update (currently -07), which had previously 
completed WGLC when a few concerns were raised. The document currently:
1. Clarifies the usage of multiple SDP 'fingerprint' attributes
2. Updates the preferred cipher-suite with a stronger cipher suite
3. Updates RFC 4572.

Item 1 seems to be generally agreeable, whereas items 2 and 3 are not. 
The chairs are hereby soliciting WG feedback on how to proceed based on 
the following choices:

a) Proceed with publication of 4572-update-07 in its current form (i.e. 
covering all 3 items above)

b) Remove item 2 from 4572-update, i.e. do not update the preferred 
cipher-suite

c) Remove item 3 from 4572-update, i.e. do not indicate that this 
document constitutes an update to RFC 4572.


Note that choice a) is mutually exclusive with b) and c), but b) and c) 
are not mutually exclusive.

Please let us know your preference wrt to the above no later than Friday 
October 14th.


Thanks

        Flemming & Bo (MMUSIC chairs)


From nobody Wed Oct 12 15:32:53 2016
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 DA90E129438 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 15:32:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_SORBS_SPAM=0.5] autolearn=no 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 F0axshzB6Dms for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 15:32:50 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 6516D1293FE for <mmusic@ietf.org>; Wed, 12 Oct 2016 15:32:50 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id i202so65810596ioi.2 for <mmusic@ietf.org>; Wed, 12 Oct 2016 15:32:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=82IryMOxNPPMAazxoZcG1m/oTLeB1N76myXiGCpm65I=; b=fS8suVHdZ+8QOOJmhuS60P4rCih5ISWKKaG5ngV8bX+BmLNsMSLZ1cN1TG6Bj19wLv zsbdDXLHN4A0+MfDCSCXZnXEE+FqlerKysaMXaYfkqdCeCEkB1H5JwqIzZA0tZ0sCwum ynJsixqQM4ZEq8c9xra5BoWqebeLtM1rMyGA2MYr5cYbc4GVaA6Et/BxiPKe/ukG9a17 LArbghvlMnmDV4VeGacnz4C10HGhvP8Zm1NWZKxmIaBY14McitQmR9p6gKsrPu9Ba5Q+ IdE0SrZdgQu3Tp1yq4Wxx45bLnZzm9champTxbhjtwQniSZ9yLhDwFHmrjkvznT/d03p g7ZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=82IryMOxNPPMAazxoZcG1m/oTLeB1N76myXiGCpm65I=; b=ZjP5C8YL6wGt6j1PzcbsdJ1fe35paWJHNyd7IF/ids6TKaF1PZPXclvzkPBQXLLDy+ n5k5GHU0UjUT0wDNFzFTzMH9UwQNxYABrWDnWaw/ag+8OvWXrEENo27wG5ih/FTzuxKl yTvm8nQlpfhkkyN32cRBQSDS61nHG0tXnJhLGGhgF4hG/g6GkrVoKdV3OjHQMyoT0anT vPgUnaxI1n7REOBZWQhTABpiWAUBtDbCZG4T2jw4edKv1Kmta/bzMcy58CIznbXYwkZs cs04wYY37k7KMoO1TuRl37cP5wyoyltcq9kzJbCQEntARQuKQWMxlZQH08LMx5V07IF9 xRRQ==
X-Gm-Message-State: AA6/9RmDlWQ51R14ermoS50I6PQ+pJZ5GL6IHwJl2/NDqVlj6QjEk+0N+862xmHXCWOmwg==
X-Received: by 10.107.31.78 with SMTP id f75mr4025241iof.141.1476311569413; Wed, 12 Oct 2016 15:32:49 -0700 (PDT)
Received: from mail-it0-f48.google.com (mail-it0-f48.google.com. [209.85.214.48]) by smtp.gmail.com with ESMTPSA id u6sm11674950itb.3.2016.10.12.15.32.48 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Oct 2016 15:32:48 -0700 (PDT)
Received: by mail-it0-f48.google.com with SMTP id z65so68151470itc.0 for <mmusic@ietf.org>; Wed, 12 Oct 2016 15:32:48 -0700 (PDT)
X-Received: by 10.36.238.134 with SMTP id b128mr3987986iti.72.1476311568487; Wed, 12 Oct 2016 15:32:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.110.18 with HTTP; Wed, 12 Oct 2016 15:32:48 -0700 (PDT)
In-Reply-To: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
From: Roman Shpount <roman@telurix.com>
Date: Wed, 12 Oct 2016 18:32:48 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuRBD=EifwFMXRGSG5ajEsaNLqi0mTt7HSp6aJ-2ZEEbQ@mail.gmail.com>
Message-ID: <CAD5OKxuRBD=EifwFMXRGSG5ajEsaNLqi0mTt7HSp6aJ-2ZEEbQ@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Content-Type: multipart/alternative; boundary=f403045c0e569e1fd5053eb2926d
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/SwG86cx7D4DOEPZ7RM_LFGYfudQ>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 22:32:52 -0000

--f403045c0e569e1fd5053eb2926d
Content-Type: text/plain; charset=UTF-8

Hi All,

I would prefer *a* -- proceed with publication in its current form and
update 4572. Chrome and Firefox already do SHA-256 and that seems to cause
no issues. Multiple fingerprint language is required to create 4572
implementations which are compatible with each other. The current language
in 4572 is ambiguous enough so that you can create two implementations
which would supposedly be compatible with 4572 (establish connection when
getting SDP with multiple fingerprints or failing to do so), but will not
work with each other. Because of this I think 4572 needs to be updated.

Regards,

_____________
Roman Shpount

On Wed, Oct 12, 2016 at 6:23 PM, Flemming Andreasen <fandreas@cisco.com>
wrote:

> Greetings
>
> There has been quite a bit of discussion on draft-ietf-mmusic-4572-update
> (currently -07), which had previously completed WGLC when a few concerns
> were raised. The document currently:
> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
> 2. Updates the preferred cipher-suite with a stronger cipher suite
> 3. Updates RFC 4572.
>
> Item 1 seems to be generally agreeable, whereas items 2 and 3 are not. The
> chairs are hereby soliciting WG feedback on how to proceed based on the
> following choices:
>
> a) Proceed with publication of 4572-update-07 in its current form (i.e.
> covering all 3 items above)
>
> b) Remove item 2 from 4572-update, i.e. do not update the preferred
> cipher-suite
>
> c) Remove item 3 from 4572-update, i.e. do not indicate that this document
> constitutes an update to RFC 4572.
>
>
> Note that choice a) is mutually exclusive with b) and c), but b) and c)
> are not mutually exclusive.
>
> Please let us know your preference wrt to the above no later than Friday
> October 14th.
>
>
> Thanks
>
>        Flemming & Bo (MMUSIC chairs)
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr"><div>Hi All,</div><div><br></div>I would prefer *a* -- pro=
ceed with publication in its current form and update 4572. Chrome and Firef=
ox already do SHA-256 and that seems to cause no issues. Multiple fingerpri=
nt language is required to create 4572 implementations which are compatible=
 with each other. The current language in 4572 is ambiguous enough so that =
you can create two implementations which would supposedly be compatible wit=
h 4572 (establish connection when getting SDP with multiple fingerprints or=
 failing to do so), but will not work with each other. Because of this I th=
ink 4572 needs to be updated.<div><br></div><div>Regards,</div></div><div c=
lass=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gmail_signature" =
data-smartmail=3D"gmail_signature">_____________<br>Roman Shpount</div></di=
v>
<br><div class=3D"gmail_quote">On Wed, Oct 12, 2016 at 6:23 PM, Flemming An=
dreasen <span dir=3D"ltr">&lt;<a href=3D"mailto:fandreas@cisco.com" target=
=3D"_blank">fandreas@cisco.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Greetings<br>
<br>
There has been quite a bit of discussion on draft-ietf-mmusic-4572-update (=
currently -07), which had previously completed WGLC when a few concerns wer=
e raised. The document currently:<br>
1. Clarifies the usage of multiple SDP &#39;fingerprint&#39; attributes<br>
2. Updates the preferred cipher-suite with a stronger cipher suite<br>
3. Updates RFC 4572.<br>
<br>
Item 1 seems to be generally agreeable, whereas items 2 and 3 are not. The =
chairs are hereby soliciting WG feedback on how to proceed based on the fol=
lowing choices:<br>
<br>
a) Proceed with publication of 4572-update-07 in its current form (i.e. cov=
ering all 3 items above)<br>
<br>
b) Remove item 2 from 4572-update, i.e. do not update the preferred cipher-=
suite<br>
<br>
c) Remove item 3 from 4572-update, i.e. do not indicate that this document =
constitutes an update to RFC 4572.<br>
<br>
<br>
Note that choice a) is mutually exclusive with b) and c), but b) and c) are=
 not mutually exclusive.<br>
<br>
Please let us know your preference wrt to the above no later than Friday Oc=
tober 14th.<br>
<br>
<br>
Thanks<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Flemming &amp; Bo (MMUSIC chairs)<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote></div><br></div>

--f403045c0e569e1fd5053eb2926d--


From nobody Wed Oct 12 15:39:13 2016
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 7F838129459; Wed, 12 Oct 2016 15:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.517
X-Spam-Level: 
X-Spam-Status: No, score=-17.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, 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 kLlaAn6SFvFN; Wed, 12 Oct 2016 15:39:09 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21CAD129438; Wed, 12 Oct 2016 15:39:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3912; q=dns/txt; s=iport; t=1476311948; x=1477521548; h=from:to:cc:subject:message-id:date:mime-version: content-transfer-encoding; bh=4U3jKaQD2RfRZPsox+PHj31UkSwbVU1mEWbmLZ8Shi0=; b=GZT/ykaBZ5jcPJS9nSVahKVI3d0brGgrqfuee8EOzwmIC6Vt5jJcleXS COERE9gnWoJiGuQz7gnuWdRzrJGINT0icFv18n2dufJeQ/pI652gZ69yN p9CORde6augm65f4ftw+AqU06Eq3URCE9CVgtth2nIJCMD7HDDWe3CjaP I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CnAgB4uv5X/4MNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgzwBAQEBAR1XKlKNM6NyhDMsWIIPggwmhXqBfDgUAQIBAQEBAQEBXie?= =?us-ascii?q?FCxU2CzUCJgJfDQgBAYhMDrYxjQgBAQEBAQEBAQEBAQEBAQEBARwFgQeFNoF9C?= =?us-ascii?q?IZpEQGDIIJbBZoCgTqEbYUVhEGBboRngxSGDIx5g38eNk6EfiI0AYY0DxcEggU?= =?us-ascii?q?BAQE?=
X-IronPort-AV: E=Sophos;i="5.31,485,1473120000"; d="scan'208";a="334178968"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 12 Oct 2016 22:39:07 +0000
Received: from [10.155.84.246] (dhcp-10-155-84-246.cisco.com [10.155.84.246]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u9CMd6Tm028852; Wed, 12 Oct 2016 22:39:07 GMT
From: Flemming Andreasen <fandreas@cisco.com>
To: mmusic <mmusic@ietf.org>
Message-ID: <73e2dc63-1712-525b-7e98-08607a56939f@cisco.com>
Date: Wed, 12 Oct 2016 18:39:06 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/x6Xv7Div_gAZIuapR1xim2IOqaM>
Cc: draft-ietf-mmusic-rfc2326bis@ietf.org
Subject: [MMUSIC] Consensus call on Auth48 changes to RTSP 2.0 (draft-ietf-mmusic-rfc2326bis-40)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 22:39:11 -0000

Greetings

This email is to initiate a consensus call on the changes the authors 
propose in Auth48 for RTSP 2.0 
(https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/). The 
consensus call is only on the proposed changes. The deadline for 
feedback is October 26, 2016. If you have objections to the changes 
please raise them on the MMUSIC mailing list.


Below is a list (courtesy of Magnus) of the significant changes since 
the last draft version that was approved by IESG. There are many more 
editorial changes. For that purpose you are provided with two diffs.

The first diff is containing all the changes significant and editorial 
that the authors have proposed. This base version for this diff is the 
version of RFC7826-to-be that the RFC-editor provided at the start of 
the AUTH48:

https://www.rfc-editor.org/authors/rfc7826-lastdiff.html

The second diff is to enable you two see all changes in RFC7826-to-be 
compared to the last draft version. This is thus both the RFC-editor's 
changes and the authors' changes combined compared to -40 draft version. 
This version is even more cluttered, but can provide the full context of 
the changes when RFC-editor editing and the authors changes interact.

https://www.rfc-editor.org/authors/rfc7826-diff.html

The following are seen as significant changes, i.e. changes in RFC 2119 
terms, changes of normative references, changes potentially affecting 
behavior, are the following:

- Section 3.2: Definition of Live (significantly reformulated even if 
intention is the same)

- General: Updated the previous RFC 2616 HTTP/1.1 references to 
RFC7230-7235.

- Section 8: New MAY: "Responses using the response code class 1xx is 
the only class for which there MAY be sent one or more responses prior 
to the final response message."

- Section 10.5: New MUST: "RTSP servers MUST support the SET_PARAMETER 
method, so that clients can always use this mechanism."

- Section 13.5.1: New MAY: The sender of a
    PLAY_NOTIFY MAY issue an updated PLAY_NOTIFY, in the case of a
    PLAY_NOTIFY sent with wrong information.

- Section 13.9: New MUST: If
    the Session header is present in a request, the value of a parameter
    MUST be retrieved in the specified session context.

- Section 13.9: New MUST: The responder to a SET_PARAMETER request MUST 
use the media type of the request for the response.  For additional 
considerations regarding message body negotiation, see Section 9.3.

- Section 17.3.3: New MUST: The Location header MUST be included in the
    response.

- Section 17.3.6: New MUST: The requested resource MUST be accessed 
through the proxy given by the Location header that MUST be included.

- Section 17.4.2, 17.4.8, 18.7, 18.8, 18.34, 18.35, 18.36, 18.58, 19.1, 
19.1.1: Changed the normative definition of the HTTP authentication 
mechanism from RFC 2617 to RFC 7235, RFC 7615, RFC 7616, RFC 7617. 
Resulting in reformulation in a number of places.

- Section 18.42: A new recommendation about CSeq numbers to avoid 
ambigouties in the Request-Status header.

- Section 18.44: New MAY: A response using 413 (Request
    Message Body Too Large) when the restriction is temporary MAY also
    include the Retry-After header.

- Section 18.57: Significant clarification on how Via in RTSP works, 
which is like HTTP, not like the via header in SIP.

- Section 19.1: New MUST NOT: The WWW-Authenticate
    (Section 18.58), Authorization (Section 18.8), and Authentication-
    Info (Section 18.7) headers are end-to-end and MUST NOT be modified
    by proxies.

- Section 20.2.3: Referencing ABNF for content of Authorization related 
headers information from RFC 7615 and 7235. See auth-param-list, 
challenge-list and credentials constructs.


Regards (and special thanks to Magnus)

     -- Flemming (as MMUSIC co-chair)


From nobody Wed Oct 12 17:52:02 2016
Return-Path: <ekr@rtfm.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 7A0851295F0 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 17:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ByFSal3BjT6u for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 17:51:58 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 E3C2A1295DA for <mmusic@ietf.org>; Wed, 12 Oct 2016 17:51:57 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id t193so43608814ywc.2 for <mmusic@ietf.org>; Wed, 12 Oct 2016 17:51:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=UG6AnG60BLWWb9lE450pqdc8gX4WhiWChTe9IZOjQLY=; b=wGGAONiwEH5ul8sdgqypVklM9YmhEbUG9W9yZOJVXt9glienYF+UB5kZVSRznSPoEl kCxdjhGpMLB5fPHW6fit4EYea7TEBAR4MMsoC9OCk5KhMi3GxHhRI8RBk1fzGOTflMyn UfNgBLpLcswCwWZxu0dAh3hVHwk3FQT0VA3WUuT9OGuiJCFY91fLigz5KcfI/ij5+wML MqRPfeIz5hjubWBzN0pxBL4NtWITOBqbiWfsbX3r7MmOiZ24Wb69gE2pv/T5NnjJgELC rzdg7bm291hFNAWSNf+yGZDPGEqik+9M5toePGxUSATTl+LsGs114dmrqLqdBwuhVIhB lt3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UG6AnG60BLWWb9lE450pqdc8gX4WhiWChTe9IZOjQLY=; b=X3gJsTkl5RFRsmDBCsPBWa2see4UkBCOazxjdQY6yM4VzACxQr4GoSR8TC+GQge8m5 g+IPh8N1N76lGOVtn/+K93vxJhy1a3hxzt6kVvbP33i7Fz1utRwndq6pxSw2Azi+Qlx4 s42ott+7aXEkY3ZuUrD34B3qQu84HulJA3iHu167v/qQFs6YrOKLxGdQBEqKbSTauCNw cbLCjCM027KeIIGpi9IFJPUS2//lsAuT9GvEmliRAmvSAzIbbfVT3i16dBWwehfNKy7I 1/T+Hge/ZI3mVHftpNegPF5G9iMLX/eDbffEtXNzXNq5FkEBOfKQDQ+CePMm83Ofhuo7 qIXA==
X-Gm-Message-State: AA6/9Rlw1S4LwfOId3KXLhLXfSnnMvg94fBQ4OMIO9kuHU66NCIz1+CpFH9v8xKlMAH6JNbTNCyAslrW+r+pqg==
X-Received: by 10.129.60.10 with SMTP id j10mr3705685ywa.354.1476319917167; Wed, 12 Oct 2016 17:51:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.75.212 with HTTP; Wed, 12 Oct 2016 17:51:16 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD668D1@ESESSMB209.ericsson.se>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com> <D423DEE7.1101D%christer.holmberg@ericsson.com> <D423FEEE.11074%christer.holmberg@ericsson.com> <CABcZeBO7b3XGRTCzN4-Z-6=8sTD3nrr8HtgN1q9np-hZ3tqbMQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD668D1@ESESSMB209.ericsson.se>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 12 Oct 2016 17:51:16 -0700
Message-ID: <CABcZeBNDpt5F_HZeHC9tavPUKzq-Dw3u2SroKcH4U-k-hWNmyg@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a114270263d3356053eb48408
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/HIz6Kyt41PbMVIbrxUlfm4Dlvo4>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Cullen Jennings <fluffy@iii.ca>, "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 00:52:00 -0000

--001a114270263d3356053eb48408
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Oct 12, 2016 at 12:54 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
>
>
> My intention was not to claim we have consensus. I just wanted to put
> forward some text to see whether it=E2=80=99s something we can work on.
>
>
>
> Or, would you prefer to not saying anything?
>

I don't think we need to say anything normative.

-Ekr


>
>
> Regards,
>
>
>
> Christer
>
>
>
> *From:* mmusic [mailto:mmusic-bounces@ietf.org] *On Behalf Of *Eric
> Rescorla
> *Sent:* 12 October 2016 19:57
> *To:* Christer Holmberg <christer.holmberg@ericsson.com>
> *Cc:* Magnus Westerlund <magnus.westerlund@ericsson.com>; Paul Kyzivat <
> pkyzivat@alum.mit.edu>; mmusic@ietf.org; Cullen Jennings <fluffy@iii.ca>
> *Subject:* Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiatio=
n-32
> - Magnus' comments - MID security
>
>
>
> I don't think there is anything like consensus for a 2919-level
> RECOMMENDED to encrypt the MID.
>
>
>
> On Wed, Oct 12, 2016 at 4:47 AM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
> Pull request created.
>
> https://github.com/cdh4u/draft-sdp-bundle/pull/11
>
>
> Regards,
>
> Christer
>
>
> On 12/10/16 12:32, "mmusic on behalf of Christer Holmberg"
> <mmusic-bounces@ietf.org on behalf of christer.holmberg@ericsson.com>
> wrote:
>
>
> >Hi,
> >
> >Based on the discussions, and input that has been provided, are people o=
k
> >with adding the text Magnus suggested (see below) to the Security
> >Considerations of BUNDLE?
> >
> >Regards,
> >
> >Christer
> >
> >
> >>>> The identfication-tag when included in the RTP MID SDES item,
> >>>> independent of transport, RTCP SDES packet or RTP header extension,
> >>>> can expose the value to parties beyond the signaling chain.
> >>>> Therefore, the identification-tag MUST NOT contain any user related
> >>>> information. However, the implementation's method for generating
> >>>> identfication-tags combined with hardware configuration can enable
> >>>> fingerprinting of the endpoint device and thus its user. As the
> >>>> identification-tag is also used to route the media stream to the
> >>>> right application functionality it is also important that the value
> >>>> received is the one intended by the sender, thus integrity and the
> >>>> authenticity of the source are important to prevent denial of
> >>>> service on the application. At least to prevent third parties from
> >>>> modifying the identification-tag value.
> >>>>
> >>>> Due to the security risks associated with the MID values in RTP and
> >>>> RTCP it is strongly RECOMMENDED that the MID SDES item is both
> >>>> confidentiality protected as well as source authenticated when
> >>>> transported in either RTCP or RTP header extensions. The security
> >>>> mechanisms used SHALL provide corresponding levels of security for
> >>>> both RTP header extensions and RTCP. Confidentiality mechanisms for
> >>>> RTP/RTCP are discussed in Options for Securing RTP Sessions
> >>>> [RFC7201], for example SRTP [RFC3711] with SRTCP encryption enabled
> >>>> combined with [RFC6904] can provide the necessary security
> >>>> functions.
> >
> >_______________________________________________
> >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
>
>
>

--001a114270263d3356053eb48408
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Oct 12, 2016 at 12:54 PM, Christer Holmberg <span dir=3D"ltr">&=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.<wbr>com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-2780569002444393897m_-233346272746139386WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Hi,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">My intention was not to claim we have=
 consensus. I just wanted to put forward some text to see whether it=E2=80=
=99s something we can work on.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Or, would you prefer to not saying an=
ything?</span></p></div></div></blockquote><div><br></div><div>I don&#39;t =
think we need to say anything normative.</div><div><br></div><div>-Ekr</div=
><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-GB" link=
=3D"blue" vlink=3D"purple"><div class=3D"m_-2780569002444393897m_-233346272=
746139386WordSection1"><p class=3D"MsoNormal"><span style=3D"font-size:11.0=
pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1f497d"><u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Regards,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Christer<u></u><u></u></span></p>
<p class=3D"MsoNormal"><a name=3D"m_-2780569002444393897_m_-233346272746139=
386__MailEndCompose"><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></a></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span lang=3D"EN-=
US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"> =
mmusic [mailto:<a href=3D"mailto:mmusic-bounces@ietf.org" target=3D"_blank"=
>mmusic-bounces@ietf.or<wbr>g</a>]
<b>On Behalf Of </b>Eric Rescorla<br>
<b>Sent:</b> 12 October 2016 19:57<br>
<b>To:</b> Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericss=
on.com" target=3D"_blank">christer.holmberg@ericsson.co<wbr>m</a>&gt;<br>
<b>Cc:</b> Magnus Westerlund &lt;<a href=3D"mailto:magnus.westerlund@ericss=
on.com" target=3D"_blank">magnus.westerlund@ericsson.co<wbr>m</a>&gt;; Paul=
 Kyzivat &lt;<a href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pky=
zivat@alum.mit.edu</a>&gt;; <a href=3D"mailto:mmusic@ietf.org" target=3D"_b=
lank">mmusic@ietf.org</a>; Cullen Jennings &lt;<a href=3D"mailto:fluffy@iii=
.ca" target=3D"_blank">fluffy@iii.ca</a>&gt;<br>
<b>Subject:</b> Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-n<wbr>e=
gotiation-32 - Magnus&#39; comments - MID security<u></u><u></u></span></p>=
<div><div class=3D"m_-2780569002444393897h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">I don&#39;t think there is anything like consensus f=
or a 2919-level RECOMMENDED to encrypt the MID.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, Oct 12, 2016 at 4:47 AM, Christer Holmberg &=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.co<wbr>m</a>&gt; wrote:<u></u><u></u></p>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal">Pull request created.<br>
<br>
<a href=3D"https://github.com/cdh4u/draft-sdp-bundle/pull/11" target=3D"_bl=
ank">https://github.com/cdh4u/draft<wbr>-sdp-bundle/pull/11</a><br>
<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
<br>
On 12/10/16 12:32, &quot;mmusic on behalf of Christer Holmberg&quot;<br>
&lt;<a href=3D"mailto:mmusic-bounces@ietf.org" target=3D"_blank">mmusic-bou=
nces@ietf.org</a> on behalf of
<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christe=
r.holmberg@ericsson.com</a><wbr>&gt;<br>
wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
&gt;Hi,<br>
&gt;<br>
&gt;Based on the discussions, and input that has been provided, are people =
ok<br>
&gt;with adding the text Magnus suggested (see below) to the Security<br>
&gt;Considerations of BUNDLE?<br>
&gt;<br>
&gt;Regards,<br>
&gt;<br>
&gt;Christer<br>
&gt;<br>
&gt;<br>
&gt;&gt;&gt;&gt; The identfication-tag when included in the RTP MID SDES it=
em,<br>
&gt;&gt;&gt;&gt; independent of transport, RTCP SDES packet or RTP header e=
xtension,<br>
&gt;&gt;&gt;&gt; can expose the value to parties beyond the signaling chain=
.<br>
&gt;&gt;&gt;&gt; Therefore, the identification-tag MUST NOT contain any use=
r related<br>
&gt;&gt;&gt;&gt; information. However, the implementation&#39;s method for =
generating<br>
&gt;&gt;&gt;&gt; identfication-tags combined with hardware configuration ca=
n enable<br>
&gt;&gt;&gt;&gt; fingerprinting of the endpoint device and thus its user. A=
s the<br>
&gt;&gt;&gt;&gt; identification-tag is also used to route the media stream =
to the<br>
&gt;&gt;&gt;&gt; right application functionality it is also important that =
the value<br>
&gt;&gt;&gt;&gt; received is the one intended by the sender, thus integrity=
 and the<br>
&gt;&gt;&gt;&gt; authenticity of the source are important to prevent denial=
 of<br>
&gt;&gt;&gt;&gt; service on the application. At least to prevent third part=
ies from<br>
&gt;&gt;&gt;&gt; modifying the identification-tag value.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Due to the security risks associated with the MID values i=
n RTP and<br>
&gt;&gt;&gt;&gt; RTCP it is strongly RECOMMENDED that the MID SDES item is =
both<br>
&gt;&gt;&gt;&gt; confidentiality protected as well as source authenticated =
when<br>
&gt;&gt;&gt;&gt; transported in either RTCP or RTP header extensions. The s=
ecurity<br>
&gt;&gt;&gt;&gt; mechanisms used SHALL provide corresponding levels of secu=
rity for<br>
&gt;&gt;&gt;&gt; both RTP header extensions and RTCP. Confidentiality mecha=
nisms for<br>
&gt;&gt;&gt;&gt; RTP/RTCP are discussed in Options for Securing RTP Session=
s<br>
&gt;&gt;&gt;&gt; [RFC7201], for example SRTP [RFC3711] with SRTCP encryptio=
n enabled<br>
&gt;&gt;&gt;&gt; combined with [RFC6904] can provide the necessary security=
<br>
&gt;&gt;&gt;&gt; functions.<br>
&gt;<br>
&gt;_____________________________<wbr>__________________<br>
&gt;mmusic mailing list<br>
&gt;<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a=
><br>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_bla=
nk">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><u></u><u></u></p>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div></div></div>
</div>

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

--001a114270263d3356053eb48408--


From nobody Wed Oct 12 18:09:18 2016
Return-Path: <martin.thomson@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 A9AFF129681 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 18:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 8tA4cbLeAZ5S for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 18:09:10 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5C79129656 for <mmusic@ietf.org>; Wed, 12 Oct 2016 18:09:09 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id z190so62059672qkc.2 for <mmusic@ietf.org>; Wed, 12 Oct 2016 18:09:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SxQqq+r0einM6rPjQ806D2xAeK8kyZoo+XZHikddzhM=; b=cam7f50hEK6KN+kDfDauHMnJc8b1szebBXGy8D9ehRsyMAEsHg7m1kk+sFH+HXQOyG MHN6ejDMOZHNcJV1R4YGF7RBfe2a9S1JIoQc5MQzo4X5VX1cVfUseGlCkOo6vlaeSbhA pU2oGBRddmm1YFW/Q4wmZSLxQY15lZCvrE7X0b/ZQUdbZ19AHN6Nj8NMCdlAFl1wKMAL uM8qELTbs3dDiw+9HTycZv7G5hLJoqJv3Z6l7RnmliJegdQuyWGu5dYBuPUIfAieHVsI uSPkq19F3nkBNF3MHbOW7Ia76NoEduhlYTkg5yKl6dwJLoxL87QggoCLq+vDgE8t7IAA p2Uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SxQqq+r0einM6rPjQ806D2xAeK8kyZoo+XZHikddzhM=; b=T3HMXg4/0odO4+tJjJ2bVaEN7topWfhh/Q8Jg8frtEG8D9fDrNOXguZt0equMRaPdE ds3vj9p6hnXHK9frK6xsmGQq7h6arY3I2ZpNTyCef8bFfND4vTRqln6jNRTsxr2kYWZx +r1DFcKNGAnVJX70dTPy/de6gIlHqmTYI7EKGL4Hsx7Z5u7Ha5xaTnkorhZyDVkGmvzP iQ/ub6Eck/eMTgxLpQ2SN2iKoknvJbXq0sgRFv5Q+EZyUdhFiYS/5kt2NLVCojqPDBAE 962S9aLE58U56sl0+vL7XNQDRGlun0ojx6oiQToDoELZm1So4C1iWXJMwoSaPOY3A31B 2Lxg==
X-Gm-Message-State: AA6/9Rm31/JFnIHXUabW16DS0mnoCYHrV3cwV88FwiYXSBgHQyPMxh+cIPYMX7a4NY8VhprNdIy3ryHTD3PvXw==
X-Received: by 10.55.158.139 with SMTP id h133mr4673209qke.202.1476320949099;  Wed, 12 Oct 2016 18:09:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.85.7 with HTTP; Wed, 12 Oct 2016 18:09:08 -0700 (PDT)
In-Reply-To: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 13 Oct 2016 12:09:08 +1100
Message-ID: <CABkgnnVfX9DnzzNufEH_J2appHD6Yspd4W7aynrogWP3LSQ1vA@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/EI9AAT-VON_7-44QZtl3wJe9B3g>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 01:09:11 -0000

On 13 October 2016 at 09:23, Flemming Andreasen <fandreas@cisco.com> wrote:
> a) Proceed with publication of 4572-update-07 in its current form (i.e.
> covering all 3 items above)

I would prefer this option.


From nobody Wed Oct 12 19:13:51 2016
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 1517312966C for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 19:13:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.197
X-Spam-Level: 
X-Spam-Status: No, score=-7.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.996, 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 3tcGvehVotyB for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 19:13:48 -0700 (PDT)
Received: from alum-mailsec-scanner-1.mit.edu (alum-mailsec-scanner-1.mit.edu [18.7.68.12]) by ietfa.amsl.com (Postfix) with ESMTP id 51F8A129659 for <mmusic@ietf.org>; Wed, 12 Oct 2016 19:13:47 -0700 (PDT)
X-AuditID: 1207440c-d67ff700000009a7-bf-57feedda8a55
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-1.mit.edu (Symantec Messaging Gateway) with SMTP id 13.A4.02471.ADDEEF75; Wed, 12 Oct 2016 22:13:46 -0400 (EDT)
Received: from [192.168.1.110] (c-73-186-127-100.hsd1.ma.comcast.net [73.186.127.100]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id u9D2DjYA005033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Wed, 12 Oct 2016 22:13:46 -0400
To: mmusic@ietf.org
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <adf8f295-df23-58bb-0d0c-5812b7b007a1@alum.mit.edu>
Date: Wed, 12 Oct 2016 22:13:45 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBIsWRmVeSWpSXmKPExsUixO6iqHvr7b9wgwMvbCymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujAe7+1gKDnNVTD33ibWBcT1HFyMnh4SAicTEc7uZuhi5OIQE LjNKHPnUB+W8ZZJoO93B0sXIwSEs4CFxdmUNSIOIgLDEjLd/2UDCQgI2Ei1T40DCbAJaEnMO /WcBsXkF7CVu9mxmB7FZBFQlJs+7wgxiiwqkSWxft5sZokZQ4uTMJ2DTOQVsJd79dgUJMwOZ d+ZClDALyEtsfzuHeQIj3ywkHbOQlM1CUraAkXkVo1xiTmmubm5iZk5xarJucXJiXl5qka6h Xm5miV5qSukmRkiA8exg/LZO5hCjAAejEg+vR9C/cCHWxLLiytxDjJIcTEqivNfuAoX4kvJT KjMSizPii0pzUosPMUpwMCuJ8HY9A8rxpiRWVqUW5cOkpDlYlMR5VZeo+wkJpCeWpGanphak FsFkZTg4lCR4f70BahQsSk1PrUjLzClBSDNxcIIM5wEaXg5Sw1tckJhbnJkOkT/FqCglzlsH khAASWSU5sH1whLAK0ZxoFeEeY2A6UCIB5g84LpfAQ1mAhpsM+kPyOCSRISUVANjrdVaB5Ps BdoCYZv1+//P28O3XOZ7uQK/TyJ75MLt9htXfppquV7r11OfzVylXIcNLAXUT56WeXT0z6pZ 9T/4rrxm+L04cHpDUJ+xpk1e7evs/ldxm+e0XjvlvXX56QeeG4LU06bleV21LFiW4f/jwa6m E6kexjIzl3MyOEZL3xQSWJrF3/ZOiaU4I9FQi7moOBEAy9mZHdsCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/L16FcslU8AkxWxRSPdvTD52wNao>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 02:13:50 -0000

I prefer (a).

On 10/12/16 6:23 PM, Flemming Andreasen wrote:
> Greetings
>
> There has been quite a bit of discussion on
> draft-ietf-mmusic-4572-update (currently -07), which had previously
> completed WGLC when a few concerns were raised. The document currently:
> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
> 2. Updates the preferred cipher-suite with a stronger cipher suite
> 3. Updates RFC 4572.
>
> Item 1 seems to be generally agreeable, whereas items 2 and 3 are not.
> The chairs are hereby soliciting WG feedback on how to proceed based on
> the following choices:
>
> a) Proceed with publication of 4572-update-07 in its current form (i.e.
> covering all 3 items above)
>
> b) Remove item 2 from 4572-update, i.e. do not update the preferred
> cipher-suite
>
> c) Remove item 3 from 4572-update, i.e. do not indicate that this
> document constitutes an update to RFC 4572.
>
>
> Note that choice a) is mutually exclusive with b) and c), but b) and c)
> are not mutually exclusive.
>
> Please let us know your preference wrt to the above no later than Friday
> October 14th.
>
>
> Thanks
>
>        Flemming & Bo (MMUSIC chairs)
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Wed Oct 12 19:36:59 2016
Return-Path: <fluffy@iii.ca>
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 26D5A129691 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 19:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, 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 UnoBm5IzKGGR for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 19:36:56 -0700 (PDT)
Received: from smtp154.dfw.emailsrvr.com (smtp154.dfw.emailsrvr.com [67.192.241.154]) (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 680D412967A for <mmusic@ietf.org>; Wed, 12 Oct 2016 19:36:56 -0700 (PDT)
Received: from smtp28.relay.dfw1a.emailsrvr.com (localhost [127.0.0.1]) by smtp28.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id AEE632014F; Wed, 12 Oct 2016 22:36:55 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp28.relay.dfw1a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 636FC200F4;  Wed, 12 Oct 2016 22:36:55 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [192.168.4.100] ([UNAVAILABLE]. [128.107.241.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:465 (trex/5.7.7); Wed, 12 Oct 2016 22:36:55 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
Date: Wed, 12 Oct 2016 20:36:54 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
To: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/UBd9nwbNCcWrelyeLhlPXjqJfDI>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 02:36:58 -0000

I really object to this. I think there is a much better option than any =
of these three options and I have asked us to have a phone call to =
discuss it. I'd like a chance to actually consider the issue here before =
we take a consensus call where we hear from a bunch of people that =
aren't building  products that do the current 4572.=20

Once again, can we please have a phone call to discuss this.=20


> On Oct 12, 2016, at 4:23 PM, Flemming Andreasen <fandreas@cisco.com> =
wrote:
>=20
> Greetings
>=20
> There has been quite a bit of discussion on =
draft-ietf-mmusic-4572-update (currently -07), which had previously =
completed WGLC when a few concerns were raised. The document currently:
> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
> 2. Updates the preferred cipher-suite with a stronger cipher suite
> 3. Updates RFC 4572.
>=20
> Item 1 seems to be generally agreeable, whereas items 2 and 3 are not. =
The chairs are hereby soliciting WG feedback on how to proceed based on =
the following choices:
>=20
> a) Proceed with publication of 4572-update-07 in its current form =
(i.e. covering all 3 items above)
>=20
> b) Remove item 2 from 4572-update, i.e. do not update the preferred =
cipher-suite
>=20
> c) Remove item 3 from 4572-update, i.e. do not indicate that this =
document constitutes an update to RFC 4572.
>=20
>=20
> Note that choice a) is mutually exclusive with b) and c), but b) and =
c) are not mutually exclusive.
>=20
> Please let us know your preference wrt to the above no later than =
Friday October 14th.
>=20
>=20
> Thanks
>=20
>       Flemming & Bo (MMUSIC chairs)
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Wed Oct 12 19:37:09 2016
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 97DB712967A for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 19:36:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 IGRdj46ZFuio for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 19:36:56 -0700 (PDT)
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 B0B8012966C for <mmusic@ietf.org>; Wed, 12 Oct 2016 19:36:54 -0700 (PDT)
X-AuditID: c1b4fb30-f60a598000000cb2-06-57fef3440690
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by  (Symantec Mail Security) with SMTP id B9.9E.03250.443FEF75; Thu, 13 Oct 2016 04:36:52 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0319.002; Thu, 13 Oct 2016 04:36:50 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Flemming Andreasen <fandreas@cisco.com>, mmusic <mmusic@ietf.org>
Thread-Topic: [MMUSIC] 4572-update: Consensus call on how to move forward
Thread-Index: AQHSJNdEtWk4xt51MEuwAe7K/vKCE6Clq1lg
Date: Thu, 13 Oct 2016 02:36:49 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD6725E@ESESSMB209.ericsson.se>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
In-Reply-To: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrJLMWRmVeSWpSXmKPExsUyM2K7va7L53/hBr2fFS3eX9C1mLr8MYsD k8eU3xtZPZYs+ckUwBTFZZOSmpNZllqkb5fAlXHi6H/Ggh/cFW9WP2NuYLzI2cXIwSEhYCLx 8Z1hFyMnh5DAekaJaz1CXYxcQPYSRoljm7czgtSwCVhIdP/TBqkREXCVOLLwLhNIWFjAQ+Ls LB0QU0TAU+L9G3uICiOJCd03mUFsFgFViSNLF7CB2LwCvhJ/ureAdQoJ2Ei0TI0DMTkFbCXe /XYFqWAUEJP4fmoNE4jNLCAucevJfDBbQkBAYsme88wQtqjEy8f/WCFsJYnGJU9YIep1JBbs /sQGYWtLLFv4mhliq6DEyZlPWCYwisxCMnYWkpZZSFpmIWlZwMiyilG0OLU4KTfdyEgvtSgz ubg4P08vL7VkEyMwAg5u+W2wg/Hlc8dDjAIcjEo8vApV/8KFWBPLiitzDzFKcDArifC+fw8U 4k1JrKxKLcqPLyrNSS0+xCjNwaIkzmu28n64kEB6YklqdmpqQWoRTJaJg1OqgZF3GfuWFWej Dq27XPCa/1xjmnWnxo3wBw+ZC27dmPBpm2r0ExfhuP3yyb+PNlfryDWs5ynOZalYF1ikO1tJ e4PUz84T/7geHrxhfNMjSCHRzfjTr6w+vlc+IRbzZly871ItM9E/V+lDlfGfbC65/AOzoqvK lmnL3lCXqD/D/c6BTerEaxHvY0osxRmJhlrMRcWJACEZvGB8AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9gmffZGm4z6nOVzfsSfZK2mgGAo>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 02:36:59 -0000

Hi,

I prefer a).

Regards,

Christer

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Flemming Andreas=
en
Sent: 13 October 2016 01:23
To: mmusic <mmusic@ietf.org>
Subject: [MMUSIC] 4572-update: Consensus call on how to move forward

Greetings

There has been quite a bit of discussion on draft-ietf-mmusic-4572-update (=
currently -07), which had previously completed WGLC when a few concerns wer=
e raised. The document currently:
1. Clarifies the usage of multiple SDP 'fingerprint' attributes 2. Updates =
the preferred cipher-suite with a stronger cipher suite 3. Updates RFC 4572=
.

Item 1 seems to be generally agreeable, whereas items 2 and 3 are not.=20
The chairs are hereby soliciting WG feedback on how to proceed based on the=
 following choices:

a) Proceed with publication of 4572-update-07 in its current form (i.e.=20
covering all 3 items above)

b) Remove item 2 from 4572-update, i.e. do not update the preferred cipher-=
suite

c) Remove item 3 from 4572-update, i.e. do not indicate that this document =
constitutes an update to RFC 4572.


Note that choice a) is mutually exclusive with b) and c), but b) and c)=20
are not mutually exclusive.

Please let us know your preference wrt to the above no later than Friday=20
October 14th.


Thanks

        Flemming & Bo (MMUSIC chairs)

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


From nobody Wed Oct 12 19:39:57 2016
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 AC9EF12969D for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 19:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 828VRyHJHSAy for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 19:39:54 -0700 (PDT)
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 8A77912966C for <mmusic@ietf.org>; Wed, 12 Oct 2016 19:39:54 -0700 (PDT)
X-AuditID: c1b4fb25-5405a9800000793b-b7-57fef3f8b518
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by  (Symantec Mail Security) with SMTP id 6F.72.31035.8F3FEF75; Thu, 13 Oct 2016 04:39:52 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0319.002; Thu, 13 Oct 2016 04:39:50 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Cullen Jennings <fluffy@iii.ca>, Flemming Andreasen <fandreas@cisco.com>
Thread-Topic: [MMUSIC] 4572-update: Consensus call on how to move forward
Thread-Index: AQHSJNdEtWk4xt51MEuwAe7K/vKCE6ClihwAgAAiP8A=
Date: Thu, 13 Oct 2016 02:39:50 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD672F8@ESESSMB209.ericsson.se>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca>
In-Reply-To: <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpikeLIzCtJLcpLzFFi42KZGbFdQvfH53/hBjfOWVi8v6Br8WH9D0aL qcsfszgwe0z5vZHVY8mSn0wel89/ZAxgjuKySUnNySxLLdK3S+DK6Fj3ga2gTahi5s/7bA2M Z/i6GDk5JARMJI5dm8/cxcjFISSwnlFi4doXrBDOEkaJxbsPM3YxcnCwCVhIdP/TBmkQEfCR WP3gADOIzSwgIzHjbCMTSImwgIfE2Vk6IKaIgKfE+zf2ENVWEodudTKB2CwCqhJ7lk1gBLF5 BXwlFq/fwQZSLiSQI/FpWhVImBOo/N2V5SwgNqOAmMT3U2uYIBaJS9x6Mp8J4mIBiSV7zjND 2KISLx//Y4WwlSQalzxhhajXkViw+xMbhK0tsWzha2aItYISJ2c+YZnAKDoLydhZSFpmIWmZ haRlASPLKkbR4tTipNx0I2O91KLM5OLi/Dy9vNSSTYzAmDm45bfqDsbLbxwPMQpwMCrx8CpU /QsXYk0sK67MPcQowcGsJML7/j1QiDclsbIqtSg/vqg0J7X4EKM0B4uSOK/ZyvvhQgLpiSWp 2ampBalFMFkmDk6pBsYcyatttxYIaRhcy/PP6Dy74OjE39/vqTFd/Hfv29I81pjrJ35crS4O fFrT5rdm9ZM1fVuqy3dWaP/4sfi8NMfdDXLv2aQVdC7fcpkq/a5jT99yU50Kv0z+8DDWp5f7 5Koftl09uvzei0dPpV1NkorUzUO1WhOjNwjevjHPZv3zrpWzuKxTdhcqsRRnJBpqMRcVJwIA jTH585UCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/coMIEBBuBo5IlP1lRGm-sx4m9_c>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 02:39:57 -0000

Hi Cullen,

I build products.

Regards,

Christer

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Cullen Jennings
Sent: 13 October 2016 05:37
To: Flemming Andreasen <fandreas@cisco.com>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward


I really object to this. I think there is a much better option than any of =
these three options and I have asked us to have a phone call to discuss it.=
 I'd like a chance to actually consider the issue here before we take a con=
sensus call where we hear from a bunch of people that aren't building  prod=
ucts that do the current 4572.=20

Once again, can we please have a phone call to discuss this.=20


> On Oct 12, 2016, at 4:23 PM, Flemming Andreasen <fandreas@cisco.com> wrot=
e:
>=20
> Greetings
>=20
> There has been quite a bit of discussion on draft-ietf-mmusic-4572-update=
 (currently -07), which had previously completed WGLC when a few concerns w=
ere raised. The document currently:
> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes 2.=20
> Updates the preferred cipher-suite with a stronger cipher suite 3.=20
> Updates RFC 4572.
>=20
> Item 1 seems to be generally agreeable, whereas items 2 and 3 are not. Th=
e chairs are hereby soliciting WG feedback on how to proceed based on the f=
ollowing choices:
>=20
> a) Proceed with publication of 4572-update-07 in its current form=20
> (i.e. covering all 3 items above)
>=20
> b) Remove item 2 from 4572-update, i.e. do not update the preferred=20
> cipher-suite
>=20
> c) Remove item 3 from 4572-update, i.e. do not indicate that this documen=
t constitutes an update to RFC 4572.
>=20
>=20
> Note that choice a) is mutually exclusive with b) and c), but b) and c) a=
re not mutually exclusive.
>=20
> Please let us know your preference wrt to the above no later than Friday =
October 14th.
>=20
>=20
> Thanks
>=20
>       Flemming & Bo (MMUSIC chairs)
>=20
> _______________________________________________
> 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 Oct 12 19:44:19 2016
Return-Path: <fluffy@iii.ca>
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 686C512969A for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 19:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, 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 ko0wQ9g2wxHa for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 19:44:15 -0700 (PDT)
Received: from smtp146.dfw.emailsrvr.com (smtp146.dfw.emailsrvr.com [67.192.241.146]) (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 75648129673 for <mmusic@ietf.org>; Wed, 12 Oct 2016 19:44:15 -0700 (PDT)
Received: from smtp27.relay.dfw1a.emailsrvr.com (localhost [127.0.0.1]) by smtp27.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id CB30AA01F8; Wed, 12 Oct 2016 22:44:14 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp27.relay.dfw1a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 688ACA01CB;  Wed, 12 Oct 2016 22:44:14 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [192.168.4.100] ([UNAVAILABLE]. [128.107.241.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:465 (trex/5.7.7); Wed, 12 Oct 2016 22:44:14 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD672F8@ESESSMB209.ericsson.se>
Date: Wed, 12 Oct 2016 20:44:13 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E683192-23E5-457F-9C6E-C13300B181B1@iii.ca>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD672F8@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/rz6_xPhXGM7s873meYkfQL8ElRg>
Cc: Flemming Andreasen <fandreas@cisco.com>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 02:44:17 -0000

Yes, I'm aware you  do and other people on this thread too. I'm not sure =
how many stuff deployed that uses 4572 is done by too many. But ignoring =
all that, I would expect you of all people to be willing to have a call =
and see if we can come up with something that meets what everyones =
desires before just stuffing this though. Why wouldn't you do that?=20


> On Oct 12, 2016, at 8:39 PM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi Cullen,
>=20
> I build products.
>=20
> Regards,
>=20
> Christer
>=20
> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Cullen =
Jennings
> Sent: 13 October 2016 05:37
> To: Flemming Andreasen <fandreas@cisco.com>
> Cc: mmusic <mmusic@ietf.org>
> Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move =
forward
>=20
>=20
> I really object to this. I think there is a much better option than =
any of these three options and I have asked us to have a phone call to =
discuss it. I'd like a chance to actually consider the issue here before =
we take a consensus call where we hear from a bunch of people that =
aren't building  products that do the current 4572.=20
>=20
> Once again, can we please have a phone call to discuss this.=20
>=20
>=20
>> On Oct 12, 2016, at 4:23 PM, Flemming Andreasen <fandreas@cisco.com> =
wrote:
>>=20
>> Greetings
>>=20
>> There has been quite a bit of discussion on =
draft-ietf-mmusic-4572-update (currently -07), which had previously =
completed WGLC when a few concerns were raised. The document currently:
>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes 2.=20
>> Updates the preferred cipher-suite with a stronger cipher suite 3.=20
>> Updates RFC 4572.
>>=20
>> Item 1 seems to be generally agreeable, whereas items 2 and 3 are =
not. The chairs are hereby soliciting WG feedback on how to proceed =
based on the following choices:
>>=20
>> a) Proceed with publication of 4572-update-07 in its current form=20
>> (i.e. covering all 3 items above)
>>=20
>> b) Remove item 2 from 4572-update, i.e. do not update the preferred=20=

>> cipher-suite
>>=20
>> c) Remove item 3 from 4572-update, i.e. do not indicate that this =
document constitutes an update to RFC 4572.
>>=20
>>=20
>> Note that choice a) is mutually exclusive with b) and c), but b) and =
c) are not mutually exclusive.
>>=20
>> Please let us know your preference wrt to the above no later than =
Friday October 14th.
>>=20
>>=20
>> Thanks
>>=20
>>      Flemming & Bo (MMUSIC chairs)
>>=20
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Wed Oct 12 19:53:40 2016
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 714211296A7 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 19:53:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5] 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 Pb2aSBbHJrnM for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 19:53:34 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 9150E1296B5 for <mmusic@ietf.org>; Wed, 12 Oct 2016 19:53:24 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id q192so71401671iod.0 for <mmusic@ietf.org>; Wed, 12 Oct 2016 19:53:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0yMzWfiUp+qs58Nzg0mW3fAAOE6aM8uXC1cZ6BLVCBc=; b=qLE1AfVvTkt2estxipGXc5wJNV2MkgVXIWWb59Dkg5jmwlscZYVnT8mI817v4l3Qx1 pxdc746GH/LS+rVlPR7jHUSjvux2FGSnl5ZvZ9xXONIKnkxOb6i2rxXIWPmtAHfaNi0C eFwcxecgnYNfzoWd0tuTa2fmjmEfioGE+FY3rhN1fd8Hk4+uTJagQ/nbYXYpyfA+0EpO ibkfUjUwSRQv6QHRGR27CieppnrxG/TPaWUk2D1/0p44B26eR89u3hH7WDmz8gBDLvYa sJmWTokerD3NK1DbJwq//heDRSg9GeUgiOxj0qf465kcv2SoKIyWIHzpwu8Pqr1JrcCH ReFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0yMzWfiUp+qs58Nzg0mW3fAAOE6aM8uXC1cZ6BLVCBc=; b=It32FVNJKvU7gSUBnJkPxVSbysi2n/9M6kV5g3HklnqCIg76rs4vF/eQSPB7PwFn/s H47KXvxEqwqTsJj36gJ2sagr/g0/yknLgvyE7Slcv3Ft3hYJF35SgCZqKKgauHsXdYDZ UK5Q87f1YRuvoza4nRYIDx+zwzSG8GbHXwDFESpfPs/YfKDwkSbP8bw3JwCghMw5OncV c0Yt38rwqMaz/ciEhZwt+GKT0wn7cajjZpCOiWVQr11fryIBTJbGMO9BF1df2pg1gSzo E7OqsDqFMqDKXWQlx/ENtgePYxBSjX7g6tzQPS0ulKEOtjYgf0JXksqyGl1mxT2SOEnk 34XA==
X-Gm-Message-State: AA6/9RmOk3MwBkdRAigYwJIsLJMUSBOzo0QPcAC3r+0AWn0I0CjkTsCIf2fDAY3PJqdhyg==
X-Received: by 10.107.9.136 with SMTP id 8mr4404047ioj.204.1476327203502; Wed, 12 Oct 2016 19:53:23 -0700 (PDT)
Received: from mail-io0-f177.google.com (mail-io0-f177.google.com. [209.85.223.177]) by smtp.gmail.com with ESMTPSA id i80sm4868767ita.5.2016.10.12.19.53.22 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Oct 2016 19:53:22 -0700 (PDT)
Received: by mail-io0-f177.google.com with SMTP id j37so71109696ioo.3 for <mmusic@ietf.org>; Wed, 12 Oct 2016 19:53:22 -0700 (PDT)
X-Received: by 10.107.132.206 with SMTP id o75mr4433536ioi.234.1476327202465;  Wed, 12 Oct 2016 19:53:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.110.18 with HTTP; Wed, 12 Oct 2016 19:53:21 -0700 (PDT)
Received: by 10.36.110.18 with HTTP; Wed, 12 Oct 2016 19:53:21 -0700 (PDT)
In-Reply-To: <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca>
From: Roman Shpount <roman@telurix.com>
Date: Wed, 12 Oct 2016 22:53:21 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtxXhvcTjOA9V2tXiNF1WKhMrNEjtA5vsgn4+ZybX9_GA@mail.gmail.com>
Message-ID: <CAD5OKxtxXhvcTjOA9V2tXiNF1WKhMrNEjtA5vsgn4+ZybX9_GA@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: multipart/alternative; boundary=001a113fe12e79b5a1053eb63648
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/hjNZAfn6hREFH3Y8lpkCT4lIrxM>
Cc: lemming Andreasen <fandreas@cisco.com>, mmusic@ietf.org
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 02:53:38 -0000

--001a113fe12e79b5a1053eb63648
Content-Type: text/plain; charset=UTF-8

I do build products as well. I would be happy to get on the call. Can you
at least give us a hint what product is affected or at least what is the
exact problem you are trying to prevent?

Roman Shpount

On Oct 12, 2016 10:37 PM, "Cullen Jennings" <fluffy@iii.ca> wrote:

>
> I really object to this. I think there is a much better option than any of
> these three options and I have asked us to have a phone call to discuss it.
> I'd like a chance to actually consider the issue here before we take a
> consensus call where we hear from a bunch of people that aren't building
> products that do the current 4572.
>
> Once again, can we please have a phone call to discuss this.
>
>
> > On Oct 12, 2016, at 4:23 PM, Flemming Andreasen <fandreas@cisco.com>
> wrote:
> >
> > Greetings
> >
> > There has been quite a bit of discussion on
> draft-ietf-mmusic-4572-update (currently -07), which had previously
> completed WGLC when a few concerns were raised. The document currently:
> > 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
> > 2. Updates the preferred cipher-suite with a stronger cipher suite
> > 3. Updates RFC 4572.
> >
> > Item 1 seems to be generally agreeable, whereas items 2 and 3 are not.
> The chairs are hereby soliciting WG feedback on how to proceed based on the
> following choices:
> >
> > a) Proceed with publication of 4572-update-07 in its current form (i.e.
> covering all 3 items above)
> >
> > b) Remove item 2 from 4572-update, i.e. do not update the preferred
> cipher-suite
> >
> > c) Remove item 3 from 4572-update, i.e. do not indicate that this
> document constitutes an update to RFC 4572.
> >
> >
> > Note that choice a) is mutually exclusive with b) and c), but b) and c)
> are not mutually exclusive.
> >
> > Please let us know your preference wrt to the above no later than Friday
> October 14th.
> >
> >
> > Thanks
> >
> >       Flemming & Bo (MMUSIC chairs)
> >
> > _______________________________________________
> > 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
>

--001a113fe12e79b5a1053eb63648
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">I do build products as well. I would be happy to get on the =
call. Can you at least give us a hint what product is affected or at least =
what is the exact problem you are trying to prevent?</p>
<p dir=3D"ltr">Roman Shpount</p>
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Oct 12, 2016 1=
0:37 PM, &quot;Cullen Jennings&quot; &lt;<a href=3D"mailto:fluffy@iii.ca">f=
luffy@iii.ca</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><br>
I really object to this. I think there is a much better option than any of =
these three options and I have asked us to have a phone call to discuss it.=
 I&#39;d like a chance to actually consider the issue here before we take a=
 consensus call where we hear from a bunch of people that aren&#39;t buildi=
ng=C2=A0 products that do the current 4572.<br>
<br>
Once again, can we please have a phone call to discuss this.<br>
<br>
<br>
&gt; On Oct 12, 2016, at 4:23 PM, Flemming Andreasen &lt;<a href=3D"mailto:=
fandreas@cisco.com">fandreas@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Greetings<br>
&gt;<br>
&gt; There has been quite a bit of discussion on draft-ietf-mmusic-4572-upd=
ate (currently -07), which had previously completed WGLC when a few concern=
s were raised. The document currently:<br>
&gt; 1. Clarifies the usage of multiple SDP &#39;fingerprint&#39; attribute=
s<br>
&gt; 2. Updates the preferred cipher-suite with a stronger cipher suite<br>
&gt; 3. Updates RFC 4572.<br>
&gt;<br>
&gt; Item 1 seems to be generally agreeable, whereas items 2 and 3 are not.=
 The chairs are hereby soliciting WG feedback on how to proceed based on th=
e following choices:<br>
&gt;<br>
&gt; a) Proceed with publication of 4572-update-07 in its current form (i.e=
. covering all 3 items above)<br>
&gt;<br>
&gt; b) Remove item 2 from 4572-update, i.e. do not update the preferred ci=
pher-suite<br>
&gt;<br>
&gt; c) Remove item 3 from 4572-update, i.e. do not indicate that this docu=
ment constitutes an update to RFC 4572.<br>
&gt;<br>
&gt;<br>
&gt; Note that choice a) is mutually exclusive with b) and c), but b) and c=
) are not mutually exclusive.<br>
&gt;<br>
&gt; Please let us know your preference wrt to the above no later than Frid=
ay October 14th.<br>
&gt;<br>
&gt;<br>
&gt; Thanks<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Flemming &amp; Bo (MMUSIC chairs)<br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; mmusic mailing list<br>
&gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"norefe=
rrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</=
a><br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
</blockquote></div></div>

--001a113fe12e79b5a1053eb63648--


From nobody Wed Oct 12 20:04:01 2016
Return-Path: <fluffy@iii.ca>
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 EA5B01296A1 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 20:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SQeIVppoeeUX for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 20:03:58 -0700 (PDT)
Received: from smtp122.iad3a.emailsrvr.com (smtp122.iad3a.emailsrvr.com [173.203.187.122]) (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 3334B129642 for <mmusic@ietf.org>; Wed, 12 Oct 2016 20:03:58 -0700 (PDT)
Received: from smtp8.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp8.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 4749FC025D; Wed, 12 Oct 2016 23:03:57 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp8.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id D7F3DC025B;  Wed, 12 Oct 2016 23:03:56 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [192.168.4.100] ([UNAVAILABLE]. [128.107.241.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:465 (trex/5.7.7); Wed, 12 Oct 2016 23:03:57 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CAD5OKxtHQ6PRszm13vAKdR3VZB1LP5Uffq8YWHTT=_i4P4h+aA@mail.gmail.com>
Date: Wed, 12 Oct 2016 21:03:55 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <445CBF55-8999-4F08-9FE4-AC4B88760FB8@iii.ca>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca> <CAD5OKxtHQ6PRszm13vAKdR3VZB1LP5Uffq8YWHTT=_i4P4h+aA@mail.gmail.com>
To: Roman Shpount <rshpount@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/QeSc_BBwpxKOGvooiSxnOed6z3U>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 03:04:00 -0000

I'm fine with an RFC that updates 4572 to clarify that you can have =
multiple fingerprints. Given I believe that 4572 already allows that I =
prefer it written as a clarification rather than a change. Call it RFC-A

I'm fine with an RFC that is an extension to RFC-A that mandates the use =
of SHA-256 as well fingerprints from RFC-A. Call RFC-B. I think it sill =
needs to require a fingerprint from the hash used in the cert signature =
to be backwards compatible with 4572. I don't think it needs to be an =
update to RFC-A.=20

This allows things that want to do SHA-256 to reference RFC-B. WebRTC =
for example.

However for people that are have shipping 4572 stuff, it makes it very =
clear that their implementations still follow the advice in 4572, all =
updates to it, and any errata. It also make is clear for people building =
stuff that they want to interop with things that do 4572 that they can't =
assume it has SHA-256. Changing 4572 at this point just make it easier =
for all the people that would rather do SDES to just keep saying well, =
perhaps we will do DTLS-SRTP with fingerprint once it stabilizes but =
that has clearly not happened yet so lets wait.=20

I'm happy to explain in more detail the issue on a call but I've tried =
in email before and seem to fail to communicate them so I'd like to have =
a call to discuss.=20

> On Oct 12, 2016, at 8:47 PM, Roman Shpount <rshpount@gmail.com> wrote:
>=20
> I do build products as well. I would be happy to get on the call. Can =
you at least give us a hint what product is affected or at least what is =
the exact problem you are trying to prevent?
>=20
> Roman Shpount
>=20
>=20
> On Oct 12, 2016 10:37 PM, "Cullen Jennings" <fluffy@iii.ca> wrote:
>=20
> I really object to this. I think there is a much better option than =
any of these three options and I have asked us to have a phone call to =
discuss it. I'd like a chance to actually consider the issue here before =
we take a consensus call where we hear from a bunch of people that =
aren't building  products that do the current 4572.
>=20
> Once again, can we please have a phone call to discuss this.
>=20
>=20
> > On Oct 12, 2016, at 4:23 PM, Flemming Andreasen <fandreas@cisco.com> =
wrote:
> >
> > Greetings
> >
> > There has been quite a bit of discussion on =
draft-ietf-mmusic-4572-update (currently -07), which had previously =
completed WGLC when a few concerns were raised. The document currently:
> > 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
> > 2. Updates the preferred cipher-suite with a stronger cipher suite
> > 3. Updates RFC 4572.
> >
> > Item 1 seems to be generally agreeable, whereas items 2 and 3 are =
not. The chairs are hereby soliciting WG feedback on how to proceed =
based on the following choices:
> >
> > a) Proceed with publication of 4572-update-07 in its current form =
(i.e. covering all 3 items above)
> >
> > b) Remove item 2 from 4572-update, i.e. do not update the preferred =
cipher-suite
> >
> > c) Remove item 3 from 4572-update, i.e. do not indicate that this =
document constitutes an update to RFC 4572.
> >
> >
> > Note that choice a) is mutually exclusive with b) and c), but b) and =
c) are not mutually exclusive.
> >
> > Please let us know your preference wrt to the above no later than =
Friday October 14th.
> >
> >
> > Thanks
> >
> >       Flemming & Bo (MMUSIC chairs)
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www.ietf.org/mailman/listinfo/mmusic
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Wed Oct 12 22:50:44 2016
Return-Path: <bernard.aboba@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20272129409 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 22:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 qQ5DNVDQZWsK for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 22:50:40 -0700 (PDT)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (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 8D8EF126FDC for <mmusic@ietf.org>; Wed, 12 Oct 2016 22:50:40 -0700 (PDT)
Received: by mail-vk0-x232.google.com with SMTP id b186so67032126vkb.1 for <mmusic@ietf.org>; Wed, 12 Oct 2016 22:50:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=izT8xwdWLEIVFFAzqbFrvfDefdJa5ehWoLEEMZh5Ymc=; b=XPSDBIVv6kxtFXEI/EUYbWQGiaV7YmCEagBkcUKB36QcLoKwX1ENjPVwjI3VF7PoDB 2naX7jscvXwy5huejJtRdB1hXhid7f2J+M3cB5v7cj+WlHGz/wEdCM2rwZrXQOFSASPx POLuB+QW+2AjJz6a4CIWiet/K2nkGAeK1Uh6bFDoYbXFgzbA1jE1VHXX/Vk2VJ3dnV2B wHfbgFOan3Kr7mCZ4zGUxP0neQFiHEX3KqQ1BL7ygN+AjXacHI6Ak5m7JVCT2z8Q7p0B mSZxD5+1fdlUdugjUAK903ufz6t+44B3HKK9aTt/xWjqlW6UYhz+08/sW5tRzYTUaVMQ L43A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=izT8xwdWLEIVFFAzqbFrvfDefdJa5ehWoLEEMZh5Ymc=; b=mZytix/f1gt6Jj1YvOftBXBMmnLy09YJL0bT/QDq6z4FfE6t7z2L/9AqLjxoG4dvWn b0IAyZaMlFkwqQ5W3G8eM61skG/xSj+r3ln9ZVCX/W27HNXaqXr/Y2WM6nCwqt48dakf 2uGvHnVRVrjyIio/Z8PnBAB85Oim6Cneuckt9RXFxnZxQnPYDT1DC0Qu/6ngyGu2xw8R aOfthgYgOn+lobCyUTg3rjMu6fx9dt/5P0yAkf/W0/X2L4Qj4WsmwvcYToq5c8tYznAk n/9gDWF2AtJXwJjoKaqWL48aGXWSINds+jrInOr6lC+NKatLsqlOLX3pIBpUFEXLu2Hp 1Q/A==
X-Gm-Message-State: AA6/9RkV+fPdDxkBmrA+e0D2zHItaoed2rHurCyBBXbK/lcMAB9jH05giAGT4qZVGBgnSd86icsOqH5eAzDUzQ==
X-Received: by 10.31.134.3 with SMTP id i3mr3350626vkd.57.1476337839595; Wed, 12 Oct 2016 22:50:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.7.101 with HTTP; Wed, 12 Oct 2016 22:50:19 -0700 (PDT)
In-Reply-To: <CAD5OKxuRBD=EifwFMXRGSG5ajEsaNLqi0mTt7HSp6aJ-2ZEEbQ@mail.gmail.com>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <CAD5OKxuRBD=EifwFMXRGSG5ajEsaNLqi0mTt7HSp6aJ-2ZEEbQ@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Wed, 12 Oct 2016 22:50:19 -0700
Message-ID: <CAOW+2dvD+=9piEZABAdELdW2Bt3qoBoMnE0QBBidBHEK_Cx=sQ@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: multipart/alternative; boundary=001a11441afc7f6b7f053eb8b0d3
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/QFb9mWtm29B_UQIORRhkixq7hkM>
Cc: Flemming Andreasen <fandreas@cisco.com>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 05:50:43 -0000

--001a11441afc7f6b7f053eb8b0d3
Content-Type: text/plain; charset=UTF-8

I would also prefer "a".  Edge, Chrome and Firefox already do SHA-256 so
this is just recognizing reality. Updating RFC 4572 is not an issue to me.

On Wed, Oct 12, 2016 at 3:32 PM, Roman Shpount <roman@telurix.com> wrote:

> Hi All,
>
> I would prefer *a* -- proceed with publication in its current form and
> update 4572. Chrome and Firefox already do SHA-256 and that seems to cause
> no issues. Multiple fingerprint language is required to create 4572
> implementations which are compatible with each other. The current language
> in 4572 is ambiguous enough so that you can create two implementations
> which would supposedly be compatible with 4572 (establish connection when
> getting SDP with multiple fingerprints or failing to do so), but will not
> work with each other. Because of this I think 4572 needs to be updated.
>
> Regards,
>
> _____________
> Roman Shpount
>
> On Wed, Oct 12, 2016 at 6:23 PM, Flemming Andreasen <fandreas@cisco.com>
> wrote:
>
>> Greetings
>>
>> There has been quite a bit of discussion on draft-ietf-mmusic-4572-update
>> (currently -07), which had previously completed WGLC when a few concerns
>> were raised. The document currently:
>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
>> 2. Updates the preferred cipher-suite with a stronger cipher suite
>> 3. Updates RFC 4572.
>>
>> Item 1 seems to be generally agreeable, whereas items 2 and 3 are not.
>> The chairs are hereby soliciting WG feedback on how to proceed based on the
>> following choices:
>>
>> a) Proceed with publication of 4572-update-07 in its current form (i.e.
>> covering all 3 items above)
>>
>> b) Remove item 2 from 4572-update, i.e. do not update the preferred
>> cipher-suite
>>
>> c) Remove item 3 from 4572-update, i.e. do not indicate that this
>> document constitutes an update to RFC 4572.
>>
>>
>> Note that choice a) is mutually exclusive with b) and c), but b) and c)
>> are not mutually exclusive.
>>
>> Please let us know your preference wrt to the above no later than Friday
>> October 14th.
>>
>>
>> Thanks
>>
>>        Flemming & Bo (MMUSIC chairs)
>>
>> _______________________________________________
>> 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
>
>

--001a11441afc7f6b7f053eb8b0d3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I would also prefer &quot;a&quot;.=C2=A0 Edge, Chrome and =
Firefox already do SHA-256 so this is just recognizing reality. Updating RF=
C 4572 is not an issue to me.=C2=A0</div><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Wed, Oct 12, 2016 at 3:32 PM, Roman Shpount <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:roman@telurix.com" target=3D"_blank">ro=
man@telurix.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><di=
v dir=3D"ltr"><div>Hi All,</div><div><br></div>I would prefer *a* -- procee=
d with publication in its current form and update 4572. Chrome and Firefox =
already do SHA-256 and that seems to cause no issues. Multiple fingerprint =
language is required to create 4572 implementations which are compatible wi=
th each other. The current language in 4572 is ambiguous enough so that you=
 can create two implementations which would supposedly be compatible with 4=
572 (establish connection when getting SDP with multiple fingerprints or fa=
iling to do so), but will not work with each other. Because of this I think=
 4572 needs to be updated.<div><br></div><div>Regards,</div></div><div clas=
s=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"m_166451979294441418=
6gmail_signature" data-smartmail=3D"gmail_signature">_____________<span cla=
ss=3D"HOEnZb"><font color=3D"#888888"><br>Roman Shpount</font></span></div>=
</div><div><div class=3D"h5">
<br><div class=3D"gmail_quote">On Wed, Oct 12, 2016 at 6:23 PM, Flemming An=
dreasen <span dir=3D"ltr">&lt;<a href=3D"mailto:fandreas@cisco.com" target=
=3D"_blank">fandreas@cisco.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Greetings<br>
<br>
There has been quite a bit of discussion on draft-ietf-mmusic-4572-update (=
currently -07), which had previously completed WGLC when a few concerns wer=
e raised. The document currently:<br>
1. Clarifies the usage of multiple SDP &#39;fingerprint&#39; attributes<br>
2. Updates the preferred cipher-suite with a stronger cipher suite<br>
3. Updates RFC 4572.<br>
<br>
Item 1 seems to be generally agreeable, whereas items 2 and 3 are not. The =
chairs are hereby soliciting WG feedback on how to proceed based on the fol=
lowing choices:<br>
<br>
a) Proceed with publication of 4572-update-07 in its current form (i.e. cov=
ering all 3 items above)<br>
<br>
b) Remove item 2 from 4572-update, i.e. do not update the preferred cipher-=
suite<br>
<br>
c) Remove item 3 from 4572-update, i.e. do not indicate that this document =
constitutes an update to RFC 4572.<br>
<br>
<br>
Note that choice a) is mutually exclusive with b) and c), but b) and c) are=
 not mutually exclusive.<br>
<br>
Please let us know your preference wrt to the above no later than Friday Oc=
tober 14th.<br>
<br>
<br>
Thanks<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Flemming &amp; Bo (MMUSIC chairs)<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote></div><br></div></div></div>
<br>______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
<br></blockquote></div><br></div>

--001a11441afc7f6b7f053eb8b0d3--


From nobody Wed Oct 12 23:07:01 2016
Return-Path: <bernard.aboba@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBA3D1294B8 for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 23:06:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 5D2t9-SU-qUj for <mmusic@ietfa.amsl.com>; Wed, 12 Oct 2016 23:06:57 -0700 (PDT)
Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (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 2065B128B37 for <mmusic@ietf.org>; Wed, 12 Oct 2016 23:06:57 -0700 (PDT)
Received: by mail-vk0-x22d.google.com with SMTP id b186so67306001vkb.1 for <mmusic@ietf.org>; Wed, 12 Oct 2016 23:06:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HP8Y2ufC0OAR3anGiTVxVdz6KNO2B+Xoj07ACnWMQD0=; b=JuQEG2+poWamVqMmz0dY4bhBz7WO31cw7aZzxPrTvT4rZRDhk2UGRSmdGW7rMijp2d heqJm0VBj6k5ukm3CSA478tweEZ24EuKQysqxMK+eZp6/V/mge7BuaMfYzVonRmDh7FH xUAMLZfH3QPdhaR14OVCY2gx/wtQm8OUdK/K+7gsJWqdvExKAD/KcdDrzlEN2FPPqQvW Wq96s3s7YZEm8VzizRUZl6gQxQFfM8Y21Fn9GnUajYs1viHySFqMzPzUSwBVMqjIsSTq YNzWk/5kpD7vMQ0jysNuge2Rp8xJsw7ORFW6UttpR0QW4hfno+r6GYVlJarJUOfYurl7 4ztQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HP8Y2ufC0OAR3anGiTVxVdz6KNO2B+Xoj07ACnWMQD0=; b=gwr4xpXVtrxsd0rWy5cck554Gq2NDBTV3SrIyOVj5W0vmGao4kC5vFAxLOrQlJ8SRS BiPCPFL2thzl6B4qFBLKeWnYMnrq7wD5A/0gYkwdYWZVUzFvwHBaruADwWif9TJkC7kD Yyjypl+JJyVhO5OsAvUae0HcdDUeTA70EoCGhxm7lCJS2VFSao21Pt66o4MtuFSOW/Jr MJxixCbmFwiHUZ61OGZX3so4d6/lJYTsGltv1f/RjzIa//POTVQtIcf7/M6bqH8+BtRI 2Qwu4kCbdsO616exB0jXq82MuHNM+Q58yI7Lo1E6vZScOv24LKWNoZEIC2/EPIWiP9Wg 0V6g==
X-Gm-Message-State: AA6/9RlsPU5R9Elet/ukMNlMc/bzmxLT3PbL/M9v1zXij6xRuYwPsGlR87vRNgw1SnU0qE5gxsKqzbAAqKKylw==
X-Received: by 10.31.220.195 with SMTP id t186mr3382784vkg.143.1476338816137;  Wed, 12 Oct 2016 23:06:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.7.101 with HTTP; Wed, 12 Oct 2016 23:06:35 -0700 (PDT)
In-Reply-To: <445CBF55-8999-4F08-9FE4-AC4B88760FB8@iii.ca>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca> <CAD5OKxtHQ6PRszm13vAKdR3VZB1LP5Uffq8YWHTT=_i4P4h+aA@mail.gmail.com> <445CBF55-8999-4F08-9FE4-AC4B88760FB8@iii.ca>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Wed, 12 Oct 2016 23:06:35 -0700
Message-ID: <CAOW+2dt4UasTQhe-+3-cZKF6fPTHKaj051oYGrCZfcFDnJgPnw@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: multipart/alternative; boundary=94eb2c07c964b44151053eb8eae6
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wT7vqNAzAoy7rg3JWwwubesCnfU>
Cc: Roman Shpount <rshpount@gmail.com>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 06:07:00 -0000

--94eb2c07c964b44151053eb8eae6
Content-Type: text/plain; charset=UTF-8

Cullen said:

"I think it still needs to require a fingerprint from the hash used in the
cert signature to be backwards compatible with 4572."

[BA] Definitely.  I haven't heard any objection to that requirement so far.

Cullen also said:

"Changing 4572 at this point just make it easier for all the people that
would rather do SDES to just keep saying well, perhaps we will do DTLS-SRTP
with fingerprint once it stabilizes"

[BA] Given all the ongoing changes in DTLS versions (e.g. update to 1.2 and
after that, 1.3), ciphersuites and certs (e.g. ECDSA), PFS, APIs (e.g.
certificate management API), this RFC 4572 update is small potatoes,
particularly if the backward compatibility issues are addressed. So if an
potential implementer can maintain their serenity in the face of all the
other DTLS changes, it seems unlikely they will be pushed over the edge by
this proposed Update (though they might well decide it is not worth
implementing).

On Wed, Oct 12, 2016 at 8:03 PM, Cullen Jennings <fluffy@iii.ca> wrote:

>
> I'm fine with an RFC that updates 4572 to clarify that you can have
> multiple fingerprints. Given I believe that 4572 already allows that I
> prefer it written as a clarification rather than a change. Call it RFC-A
>
> I'm fine with an RFC that is an extension to RFC-A that mandates the use
> of SHA-256 as well fingerprints from RFC-A. Call RFC-B. I think it sill
> needs to require a fingerprint from the hash used in the cert signature to
> be backwards compatible with 4572. I don't think it needs to be an update
> to RFC-A.
>
> This allows things that want to do SHA-256 to reference RFC-B. WebRTC for
> example.
>
> However for people that are have shipping 4572 stuff, it makes it very
> clear that their implementations still follow the advice in 4572, all
> updates to it, and any errata. It also make is clear for people building
> stuff that they want to interop with things that do 4572 that they can't
> assume it has SHA-256. Changing 4572 at this point just make it easier for
> all the people that would rather do SDES to just keep saying well, perhaps
> we will do DTLS-SRTP with fingerprint once it stabilizes but that has
> clearly not happened yet so lets wait.
>
> I'm happy to explain in more detail the issue on a call but I've tried in
> email before and seem to fail to communicate them so I'd like to have a
> call to discuss.
>
> > On Oct 12, 2016, at 8:47 PM, Roman Shpount <rshpount@gmail.com> wrote:
> >
> > I do build products as well. I would be happy to get on the call. Can
> you at least give us a hint what product is affected or at least what is
> the exact problem you are trying to prevent?
> >
> > Roman Shpount
> >
> >
> > On Oct 12, 2016 10:37 PM, "Cullen Jennings" <fluffy@iii.ca> wrote:
> >
> > I really object to this. I think there is a much better option than any
> of these three options and I have asked us to have a phone call to discuss
> it. I'd like a chance to actually consider the issue here before we take a
> consensus call where we hear from a bunch of people that aren't building
> products that do the current 4572.
> >
> > Once again, can we please have a phone call to discuss this.
> >
> >
> > > On Oct 12, 2016, at 4:23 PM, Flemming Andreasen <fandreas@cisco.com>
> wrote:
> > >
> > > Greetings
> > >
> > > There has been quite a bit of discussion on
> draft-ietf-mmusic-4572-update (currently -07), which had previously
> completed WGLC when a few concerns were raised. The document currently:
> > > 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
> > > 2. Updates the preferred cipher-suite with a stronger cipher suite
> > > 3. Updates RFC 4572.
> > >
> > > Item 1 seems to be generally agreeable, whereas items 2 and 3 are not.
> The chairs are hereby soliciting WG feedback on how to proceed based on the
> following choices:
> > >
> > > a) Proceed with publication of 4572-update-07 in its current form
> (i.e. covering all 3 items above)
> > >
> > > b) Remove item 2 from 4572-update, i.e. do not update the preferred
> cipher-suite
> > >
> > > c) Remove item 3 from 4572-update, i.e. do not indicate that this
> document constitutes an update to RFC 4572.
> > >
> > >
> > > Note that choice a) is mutually exclusive with b) and c), but b) and
> c) are not mutually exclusive.
> > >
> > > Please let us know your preference wrt to the above no later than
> Friday October 14th.
> > >
> > >
> > > Thanks
> > >
> > >       Flemming & Bo (MMUSIC chairs)
> > >
> > > _______________________________________________
> > > 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
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--94eb2c07c964b44151053eb8eae6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Cullen said:=C2=A0<div><br></div><div>&quot;<span style=3D=
"font-size:12.8px">I think it still needs to require a fingerprint from the=
 hash used in the cert signature to be backwards compatible with 4572.</spa=
n>&quot;</div><div><br></div><div>[BA] Definitely.=C2=A0 I haven&#39;t hear=
d any objection to that requirement so far.=C2=A0</div><div><br></div><div>=
Cullen also said:=C2=A0</div><div><br></div><div>&quot;<span style=3D"font-=
size:12.8px">Changing 4572 at this point just make it easier for all the pe=
ople that would rather do SDES to just keep saying well, perhaps we will do=
 DTLS-SRTP with fingerprint once it stabilizes</span>&quot;</div><div><br><=
/div><div>[BA] Given all the ongoing changes in DTLS versions (e.g. update =
to 1.2 and after that, 1.3), ciphersuites and certs (e.g. ECDSA), PFS, APIs=
 (e.g. certificate management API), this RFC 4572 update is small potatoes,=
 particularly if the backward compatibility issues are addressed. So if an =
potential implementer can maintain their serenity in the face of all the ot=
her DTLS changes, it seems unlikely they will be pushed over the edge by th=
is proposed Update (though they might well decide it is not worth implement=
ing).=C2=A0</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_q=
uote">On Wed, Oct 12, 2016 at 8:03 PM, Cullen Jennings <span dir=3D"ltr">&l=
t;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank">fluffy@iii.ca</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><br>
I&#39;m fine with an RFC that updates 4572 to clarify that you can have mul=
tiple fingerprints. Given I believe that 4572 already allows that I prefer =
it written as a clarification rather than a change. Call it RFC-A<br>
<br>
I&#39;m fine with an RFC that is an extension to RFC-A that mandates the us=
e of SHA-256 as well fingerprints from RFC-A. Call RFC-B. I think it sill n=
eeds to require a fingerprint from the hash used in the cert signature to b=
e backwards compatible with 4572. I don&#39;t think it needs to be an updat=
e to RFC-A.<br>
<br>
This allows things that want to do SHA-256 to reference RFC-B. WebRTC for e=
xample.<br>
<br>
However for people that are have shipping 4572 stuff, it makes it very clea=
r that their implementations still follow the advice in 4572, all updates t=
o it, and any errata. It also make is clear for people building stuff that =
they want to interop with things that do 4572 that they can&#39;t assume it=
 has SHA-256. Changing 4572 at this point just make it easier for all the p=
eople that would rather do SDES to just keep saying well, perhaps we will d=
o DTLS-SRTP with fingerprint once it stabilizes but that has clearly not ha=
ppened yet so lets wait.<br>
<br>
I&#39;m happy to explain in more detail the issue on a call but I&#39;ve tr=
ied in email before and seem to fail to communicate them so I&#39;d like to=
 have a call to discuss.<br>
<span class=3D"im HOEnZb"><br>
&gt; On Oct 12, 2016, at 8:47 PM, Roman Shpount &lt;<a href=3D"mailto:rshpo=
unt@gmail.com">rshpount@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; I do build products as well. I would be happy to get on the call. Can =
you at least give us a hint what product is affected or at least what is th=
e exact problem you are trying to prevent?<br>
&gt;<br>
&gt; Roman Shpount<br>
&gt;<br>
&gt;<br>
&gt; On Oct 12, 2016 10:37 PM, &quot;Cullen Jennings&quot; &lt;<a href=3D"m=
ailto:fluffy@iii.ca">fluffy@iii.ca</a>&gt; wrote:<br>
&gt;<br>
</span><div class=3D"HOEnZb"><div class=3D"h5">&gt; I really object to this=
. I think there is a much better option than any of these three options and=
 I have asked us to have a phone call to discuss it. I&#39;d like a chance =
to actually consider the issue here before we take a consensus call where w=
e hear from a bunch of people that aren&#39;t building=C2=A0 products that =
do the current 4572.<br>
&gt;<br>
&gt; Once again, can we please have a phone call to discuss this.<br>
&gt;<br>
&gt;<br>
&gt; &gt; On Oct 12, 2016, at 4:23 PM, Flemming Andreasen &lt;<a href=3D"ma=
ilto:fandreas@cisco.com">fandreas@cisco.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; Greetings<br>
&gt; &gt;<br>
&gt; &gt; There has been quite a bit of discussion on draft-ietf-mmusic-457=
2-update (currently -07), which had previously completed WGLC when a few co=
ncerns were raised. The document currently:<br>
&gt; &gt; 1. Clarifies the usage of multiple SDP &#39;fingerprint&#39; attr=
ibutes<br>
&gt; &gt; 2. Updates the preferred cipher-suite with a stronger cipher suit=
e<br>
&gt; &gt; 3. Updates RFC 4572.<br>
&gt; &gt;<br>
&gt; &gt; Item 1 seems to be generally agreeable, whereas items 2 and 3 are=
 not. The chairs are hereby soliciting WG feedback on how to proceed based =
on the following choices:<br>
&gt; &gt;<br>
&gt; &gt; a) Proceed with publication of 4572-update-07 in its current form=
 (i.e. covering all 3 items above)<br>
&gt; &gt;<br>
&gt; &gt; b) Remove item 2 from 4572-update, i.e. do not update the preferr=
ed cipher-suite<br>
&gt; &gt;<br>
&gt; &gt; c) Remove item 3 from 4572-update, i.e. do not indicate that this=
 document constitutes an update to RFC 4572.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Note that choice a) is mutually exclusive with b) and c), but b) =
and c) are not mutually exclusive.<br>
&gt; &gt;<br>
&gt; &gt; Please let us know your preference wrt to the above no later than=
 Friday October 14th.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Thanks<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Flemming &amp; Bo (MMUSIC chairs)<br>
&gt; &gt;<br>
&gt; &gt; ______________________________<wbr>_________________<br>
&gt; &gt; mmusic mailing list<br>
&gt; &gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmu=
sic</a><br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; mmusic mailing list<br>
&gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"norefe=
rrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</=
a><br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div>

--94eb2c07c964b44151053eb8eae6--


From nobody Thu Oct 13 00:07:27 2016
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 CC9311298A8 for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 00:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 QCbOyoihR7lc for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 00:07:24 -0700 (PDT)
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 4C5311298A7 for <mmusic@ietf.org>; Thu, 13 Oct 2016 00:07:24 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-d5-57ff32aa05c6
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by  (Symantec Mail Security) with SMTP id EA.70.02551.AA23FF75; Thu, 13 Oct 2016 09:07:22 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0319.002; Thu, 13 Oct 2016 09:07:21 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Cullen Jennings <fluffy@iii.ca>, Roman Shpount <rshpount@gmail.com>
Thread-Topic: [MMUSIC] 4572-update: Consensus call on how to move forward
Thread-Index: AQHSJNdEtWk4xt51MEuwAe7K/vKCE6ClihwAgAApINCAAEOSUA==
Date: Thu, 13 Oct 2016 07:07:20 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD67769@ESESSMB209.ericsson.se>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca> <CAD5OKxtHQ6PRszm13vAKdR3VZB1LP5Uffq8YWHTT=_i4P4h+aA@mail.gmail.com> <445CBF55-8999-4F08-9FE4-AC4B88760FB8@iii.ca>
In-Reply-To: <445CBF55-8999-4F08-9FE4-AC4B88760FB8@iii.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphkeLIzCtJLcpLzFFi42KZGbHdUneV0f9wg9eL9C0+rP/BaDF1+WMW i55z69kdmD12zrrL7rFkyU8mj8vnPzIGMEdx2aSk5mSWpRbp2yVwZXxefoWl4AlzxZqPT1gb GL8xdTFyckgImEgcX/SZvYuRi0NIYD2jxLr321khnCWMEvfub2HsYuTgYBOwkOj+pw3SICLg LrHm0T9WEJtZQEZixtlGJpASYQEPibOzdEBMEQFPifdv7CGqnSQuLboCVs0ioCqx/dkjZhCb V8BX4ljDfhaITY8ZJXa+/MMK0sspYCXxvA2shlFATOL7qTVMEJvEJW49mQ91soDEkj3nmSFs UYmXjyGukRBQkmhc8gTqMh2JBbs/sUHY2hLLFr6G2isocXLmE5YJjKKzkIydhaRlFpKWWUha FjCyrGIULU4tLs5NNzLWSy3KTC4uzs/Ty0st2cQIjJuDW37r7mBc/drxEKMAB6MSD69C1b9w IdbEsuLK3EOMEhzMSiK8Err/w4V4UxIrq1KL8uOLSnNSiw8xSnOwKInzmq28Hy4kkJ5Ykpqd mlqQWgSTZeLglGpg7Oq+dc6oM9rS9eNBDgGr/aVHpdwi4zPKOnqk5XV8Fxifd35w8hRvf/y8 gwJSS3q+68+YxHeVscDis+Ab7SquM71aRx0Sph86tv2jryzDh7uSJXe3ZbsZyDqJhU2pP623 f1fOG67TshsO+eQ1MVxS+K6z8tvtV8znVSeZs3s2//K8fIHBubFTiaU4I9FQi7moOBEAadKZ 95cCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/HToXECEiTPbHcTqCvAKkPZNPfEI>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 07:07:26 -0000

Hi,

>I think it still needs to require a fingerprint from the hash used in the =
cert signature to be >backwards compatible with 4572.

Version -07 contains the following text - which was added based on your com=
ments:

    "An endpoint MUST, as a minimum, calculate a fingerprint using both the=
 'SHA-256'
    hash function algorithm and the hash function used to generate the
    signature on the certificate for each possible certificate."

Regards,

Christer


From nobody Thu Oct 13 02:09:18 2016
Return-Path: <magnus.westerlund@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 BDB5C1296DF for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 02:09:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 NudgaLCkt5RS for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 02:09:14 -0700 (PDT)
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 9A79A1293F2 for <mmusic@ietf.org>; Thu, 13 Oct 2016 02:09:14 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-df-57ff4f38bc63
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by  (Symantec Mail Security) with SMTP id 6D.AC.02458.83F4FF75; Thu, 13 Oct 2016 11:09:13 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.86) with Microsoft SMTP Server id 14.3.301.0; Thu, 13 Oct 2016 11:09:11 +0200
To: Eric Rescorla <ekr@rtfm.com>, Christer Holmberg <christer.holmberg@ericsson.com>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com> <D423DEE7.1101D%christer.holmberg@ericsson.com> <D423FEEE.11074%christer.holmberg@ericsson.com> <CABcZeBO7b3XGRTCzN4-Z-6=8sTD3nrr8HtgN1q9np-hZ3tqbMQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD668D1@ESESSMB209.ericsson.se> <CABcZeBNDpt5F_HZeHC9tavPUKzq-Dw3u2SroKcH4U-k-hWNmyg@mail.gmail.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <4a000249-91d9-f6b3-5b01-4833e6d359fc@ericsson.com>
Date: Thu, 13 Oct 2016 11:09:07 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBNDpt5F_HZeHC9tavPUKzq-Dw3u2SroKcH4U-k-hWNmyg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKLMWRmVeSWpSXmKPExsUyM2J7iK6l//9wg4MJFiten2O3+LD+B6PF 1OWPWSxWbDjA6sDi8ff9ByaPJUt+MnlcPv+R0WPy4zbmAJYoLpuU1JzMstQifbsEroz3e08w FuySrNhwfDNjA+MOkS5GTg4JAROJzm1nWbsYuTiEBNYzSvT9f8EGkhASWM4osX1LbRcjB4ew QL7E9Cl1IKaIQJjE2rP8EOW9LBLTNt1nBClnFiiQeH5yKwuIzSZgIXHzRyPYGF4Be4kb3ftY QXpZBFQlVhz1BQmLCsRIXH/2CKpEUOLkzCdgrZwCgRLPf/5ighhpITFz/nmo8fISzVtnM0Nc pi3R0NTBOoFRYBaS9llIWmYhaVnAyLyKUbQ4tbg4N93ISC+1KDO5uDg/Ty8vtWQTIzBwD275 bbWD8eBzx0OMAhyMSjy8ClX/woVYE8uKK3MPMUpwMCuJ8Ar5/Q8X4k1JrKxKLcqPLyrNSS0+ xCjNwaIkzmu28n64kEB6YklqdmpqQWoRTJaJg1OqgbFv0vPAxZO2PTW/uq9hyeltaVd8pdTX vCyOumv0Z+mzgLV/hdRvuF8VytowbXefI+v5nmQ//3oex0ydmSbzNy59rfnZ7efyNH2Z3li1 2+93bP8SxmFkIs5T56c3LzBpY3LViRksd69MSOOpecjH3L/9S0U9i+qxrl3Tj4T7s4ScrjD4 mL1O3leJpTgj0VCLuag4EQBzA7haWAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/mKvPFWjdmf9rnAFiafbMDRN7SSg>
Cc: Cullen Jennings <fluffy@iii.ca>, "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 09:09:17 -0000

Den 2016-10-13 kl. 02:51, skrev Eric Rescorla:
>
>
> On Wed, Oct 12, 2016 at 12:54 PM, Christer Holmberg
> <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>>
> wrote:
>
>     Hi,____
>
>     __ __
>
>     My intention was not to claim we have consensus. I just wanted to
>     put forward some text to see whether itâ€™s something we can work on.____
>
>     __ __
>
>     Or, would you prefer to not saying anything?
>
>
> I don't think we need to say anything normative.
>

Can you please be a bit more constructive here?

I hope you are not disagreeing with a RECOMMEND for source 
authentication at least? Having third party attackers being able to 
change the MID on path that is a quite serious attack, so integrity and 
source authentication I think is well motivated.

Regarding the aspects regarding privacy and information leakage. You 
previously indicated that you agree that we should at least avoid 
structured MIDs to avoid that implementation specifics or hardware 
addresses of source devices leaks this way. This would mean that BUNDLE 
should contain guidance on how to construct them so this is avoided. 
This is currently not included. I have no problem with including such 
recommendations. Do you have a proposal for how to construct them?

When we come to the last aspect regarding confidentiality protection of 
the MID identifiers I can understand the hesitance over this. For some 
use cases I agree the information leakage is in principal zero, as the 
fact that the streams are there are present through SSRCs, PTs etc. 
However, especially for multiple  streams originating from a endpoint, 
rather than a conference mixer, this do exposes information. Here the 
above discussed recommendations do matters for what information can be 
leaked. For example if we would sequentially assign identifers, then we 
exposes the potential sub-selection of streams the signalling agrees on 
at the RTP layer. If we use random values this exposure can be avoid.

I proposed encryption as method that would ensure that we had random 
identifiers of good properties. But, what is your proposal for how these 
identifiers should be construct to minimize the exposure of information?

I also asked the question if there was issues with encrypting this from 
a functional perspective? Unless I receive an answer I will assume not, 
and that it is primarily a hesitant to start using RFC6904.

 From my perspective, lets settle the guidance for construction, then we 
can document what the potential remaining risks are in the security 
consideration. I personally think it is more important to document the 
risks than absolutely have the RFC2119 recommendation here.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Oct 13 05:13:25 2016
Return-Path: <ekr@rtfm.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 E5C64129567 for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 05:13:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4px2LdgNKYRp for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 05:13:22 -0700 (PDT)
Received: from mail-yb0-x22f.google.com (mail-yb0-x22f.google.com [IPv6:2607:f8b0:4002:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23F641294BE for <mmusic@ietf.org>; Thu, 13 Oct 2016 05:13:20 -0700 (PDT)
Received: by mail-yb0-x22f.google.com with SMTP id o189so4458212yba.1 for <mmusic@ietf.org>; Thu, 13 Oct 2016 05:13:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xAOUDPyQkxhCvV2x2PV7uyT+F6/5ywgEsxMFTpkckEQ=; b=eXmQ550fbnUW/MQRRcUMQtmpoJElyPVNjpkZDXcNl2ZFLAI7GrweLvAktA7CLIh41I ICW4EWYpcMLqvHkwpVocyLXvteP6ZHDGMJumzOOQxVFgPATozEZWUDQE5ySOy9vvrwvG a3cvcr37U8AY52wgqdaLIBmAEYiAwOy7oceIiy2ogsvatYVHRByUq46oDHR02mrF2vTT Mzcy1Xj5RHT3/V2AJTD5J/74fcY4oGtudEcPjbPizT+A4aFusLcFXbjKHFA2WGtAGEtQ lE1QsAkIH+xkSbo2xITk+w8WbfB5lklyc+Cn9brjHrIbEkNxRLtWKqTkf4b3UlUjbdi8 GgQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xAOUDPyQkxhCvV2x2PV7uyT+F6/5ywgEsxMFTpkckEQ=; b=MIyO5Gm/qdSd2kU+SMkLeceNN/SPDJmnWkBxBHMTSrR+eXWB6pZXBaVWYZB6fsPPrw TQK60ncRE4VoOmmPnuth0XO9M7DpY9fJyAHxruwQYanrEJTHZGZ3JQytdIOl+iH+V9R0 0VwL+PqKvypm7PkhNA9U+sQC5EJ0NBETy2szMZjYMEByiQ5jcWvxZpeGaqzxUchOZvHk P74bHf1lsvgtR33wM5dIPmzLx69pd8flSNyQbWXej4qcusHkVKHn3MyOZt2GmaZm0co1 VXC8eO/3Uyz5roZ0nsF0wIwDtNzbU/QyziTxVJZHJ7cEndknpferERyjCfWV2y2c1Bjl mO0g==
X-Gm-Message-State: AA6/9RnLlcdSviY7KZq2+TJwxRPSJpUSu3lRYhy2YesxZPDIwoYiZN7KLkZ6J4KnHhWTzh2au+Nudlk3Z2D/tA==
X-Received: by 10.37.80.12 with SMTP id e12mr5246065ybb.105.1476360799311; Thu, 13 Oct 2016 05:13:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.75.212 with HTTP; Thu, 13 Oct 2016 05:12:38 -0700 (PDT)
In-Reply-To: <4a000249-91d9-f6b3-5b01-4833e6d359fc@ericsson.com>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com> <D423DEE7.1101D%christer.holmberg@ericsson.com> <D423FEEE.11074%christer.holmberg@ericsson.com> <CABcZeBO7b3XGRTCzN4-Z-6=8sTD3nrr8HtgN1q9np-hZ3tqbMQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD668D1@ESESSMB209.ericsson.se> <CABcZeBNDpt5F_HZeHC9tavPUKzq-Dw3u2SroKcH4U-k-hWNmyg@mail.gmail.com> <4a000249-91d9-f6b3-5b01-4833e6d359fc@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 13 Oct 2016 05:12:38 -0700
Message-ID: <CABcZeBNwbWWZPcjothhZEv2L8uSpW=stg5-eyxS_nOYUjNwp8A@mail.gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: multipart/alternative; boundary=001a113e86cc0108e7053ebe09de
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/vcBbkYM-gIdNRGYdmX-TSS6iQ18>
Cc: Cullen Jennings <fluffy@iii.ca>, "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 12:13:24 -0000

--001a113e86cc0108e7053ebe09de
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 13, 2016 at 2:09 AM, Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> Den 2016-10-13 kl. 02:51, skrev Eric Rescorla:
>
>>
>>
>> On Wed, Oct 12, 2016 at 12:54 PM, Christer Holmberg
>> <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>>
>> wrote:
>>
>>     Hi,____
>>
>>     __ __
>>
>>     My intention was not to claim we have consensus. I just wanted to
>>     put forward some text to see whether it=E2=80=99s something we can w=
ork
>> on.____
>>
>>     __ __
>>
>>     Or, would you prefer to not saying anything?
>>
>>
>> I don't think we need to say anything normative.
>>
>>
> Can you please be a bit more constructive here?
>

I think I am being constructive. I'm trying to get the draft finished, and
this seems to be poorly motivated.


I hope you are not disagreeing with a RECOMMEND for source authentication
> at least? Having third party attackers being able to change the MID on pa=
th
> that is a quite serious attack, so integrity and source authentication I
> think is well motivated.
>

There seem to be two cases:

1. You're using SRTP (and this should also include SRTCP).
2. You're not using SRTP.

In case #1, then the MID should be integrity protected because it's part of
the packet. If not, then I don't think a partial solution helps.


Regarding the aspects regarding privacy and information leakage. You
> previously indicated that you agree that we should at least avoid
> structured MIDs to avoid that implementation specifics or hardware
> addresses of source devices leaks this way.


No, that's not what I said. Rather, I said:

"The first of these seems addressable by guidance about how to construct
these IDs. I note that we
have only very limited guidance on how to construct ICE ufrag/passwords....=
"

If you think this kind of identifier-generation tracking is an issue, I
would suggest doing a broader survey
first, rather than focusing on this case.

-Ekr

This would mean that BUNDLE should contain guidance on how to construct
> them so this is avoided. This is currently not included. I have no proble=
m
> with including such recommendations. Do you have a proposal for how to
> construct them?
>
> When we come to the last aspect regarding confidentiality protection of
> the MID identifiers I can understand the hesitance over this. For some us=
e
> cases I agree the information leakage is in principal zero, as the fact
> that the streams are there are present through SSRCs, PTs etc. However,
> especially for multiple  streams originating from a endpoint, rather than=
 a
> conference mixer, this do exposes information. Here the above discussed
> recommendations do matters for what information can be leaked. For exampl=
e
> if we would sequentially assign identifers, then we exposes the potential
> sub-selection of streams the signalling agrees on at the RTP layer. If we
> use random values this exposure can be avoid.
>
> I proposed encryption as method that would ensure that we had random
> identifiers of good properties. But, what is your proposal for how these
> identifiers should be construct to minimize the exposure of information?
>
> I also asked the question if there was issues with encrypting this from a
> functional perspective? Unless I receive an answer I will assume not, and
> that it is primarily a hesitant to start using RFC6904.
>
> From my perspective, lets settle the guidance for construction, then we
> can document what the potential remaining risks are in the security
> consideration. I personally think it is more important to document the
> risks than absolutely have the RFC2119 recommendation here.
>
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=C3=A4r=C3=B6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>

--001a113e86cc0108e7053ebe09de
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Oct 13, 2016 at 2:09 AM, Magnus Westerlund <span dir=3D"ltr">&l=
t;<a href=3D"mailto:magnus.westerlund@ericsson.com" target=3D"_blank">magnu=
s.westerlund@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex"><span class=3D"gmail-">Den 2016-10-13 kl. 02:51, =
skrev Eric Rescorla:<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gma=
il-">
<br>
<br>
On Wed, Oct 12, 2016 at 12:54 PM, Christer Holmberg<br></span>
&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chr=
ister.holmberg@ericsson.co<wbr>m</a> &lt;mailto:<a href=3D"mailto:christer.=
holmberg@ericsson.com" target=3D"_blank">christer.holmberg@eric<wbr>sson.co=
m</a>&gt;&gt;<br>
wrote:<br>
<br>
=C2=A0 =C2=A0 Hi,____<br>
<br>
=C2=A0 =C2=A0 __ __<span class=3D"gmail-"><br>
<br>
=C2=A0 =C2=A0 My intention was not to claim we have consensus. I just wante=
d to<br></span>
=C2=A0 =C2=A0 put forward some text to see whether it=E2=80=99s something w=
e can work on.____<br>
<br>
=C2=A0 =C2=A0 __ __<span class=3D"gmail-"><br>
<br>
=C2=A0 =C2=A0 Or, would you prefer to not saying anything?<br>
<br>
<br>
I don&#39;t think we need to say anything normative.<br>
<br>
</span></blockquote>
<br>
Can you please be a bit more constructive here?<br></blockquote><div><br></=
div><div>I think I am being constructive. I&#39;m trying to get the draft f=
inished, and this seems to be poorly motivated.</div><div><br></div><div><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">
I hope you are not disagreeing with a RECOMMEND for source authentication a=
t least? Having third party attackers being able to change the MID on path =
that is a quite serious attack, so integrity and source authentication I th=
ink is well motivated.<br></blockquote><div><br></div><div>There seem to be=
 two cases:</div><div><br></div><div>1. You&#39;re using SRTP (and this sho=
uld also include SRTCP).</div><div>2. You&#39;re not using SRTP.</div><div>=
<br></div><div>In case #1, then the MID should be integrity protected becau=
se it&#39;s part of the packet. If not, then I don&#39;t think a partial so=
lution helps.</div><div><br></div><div><br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">
Regarding the aspects regarding privacy and information leakage. You previo=
usly indicated that you agree that we should at least avoid structured MIDs=
 to avoid that implementation specifics or hardware addresses of source dev=
ices leaks this way.</blockquote><div><br></div><div>No, that&#39;s not wha=
t I said. Rather, I said:</div><div><br></div><div>&quot;<span style=3D"fon=
t-size:12.8px">The first of these seems addressable by guidance about how t=
o construct these IDs. I note that we</span></div><div style=3D"font-size:1=
2.8px">have only very limited guidance on how to construct ICE ufrag/passwo=
rds....&quot;</div><div style=3D"font-size:12.8px"><br></div><div style=3D"=
font-size:12.8px">If you think this kind of identifier-generation tracking =
is an issue, I would suggest doing a broader survey</div><div style=3D"font=
-size:12.8px">first, rather than focusing on this case.</div><div style=3D"=
font-size:12.8px"><br></div><div>-Ekr</div><div><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"> This would mean that BUNDLE should contai=
n guidance on how to construct them so this is avoided. This is currently n=
ot included. I have no problem with including such recommendations. Do you =
have a proposal for how to construct them?<br>
<br>
When we come to the last aspect regarding confidentiality protection of the=
 MID identifiers I can understand the hesitance over this. For some use cas=
es I agree the information leakage is in principal zero, as the fact that t=
he streams are there are present through SSRCs, PTs etc. However, especiall=
y for multiple=C2=A0 streams originating from a endpoint, rather than a con=
ference mixer, this do exposes information. Here the above discussed recomm=
endations do matters for what information can be leaked. For example if we =
would sequentially assign identifers, then we exposes the potential sub-sel=
ection of streams the signalling agrees on at the RTP layer. If we use rand=
om values this exposure can be avoid.<br>
<br>
I proposed encryption as method that would ensure that we had random identi=
fiers of good properties. But, what is your proposal for how these identifi=
ers should be construct to minimize the exposure of information?<br>
<br>
I also asked the question if there was issues with encrypting this from a f=
unctional perspective? Unless I receive an answer I will assume not, and th=
at it is primarily a hesitant to start using RFC6904.<br>
<br>
>From my perspective, lets settle the guidance for construction, then we can=
 document what the potential remaining risks are in the security considerat=
ion. I personally think it is more important to document the risks than abs=
olutely have the RFC2119 recommendation here.<div class=3D"gmail-HOEnZb"><d=
iv class=3D"gmail-h5"><br>
<br>
Cheers<br>
<br>
Magnus Westerlund<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
Services, Media and Network features, Ericsson Research EAB/TXM<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
Ericsson AB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =
Phone=C2=A0 <a href=3D"tel:%2B46%2010%207148287" value=3D"+46107148287" tar=
get=3D"_blank">+46 10 7148287</a><br>
F=C3=A4r=C3=B6gatan 6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0| Mobile <a href=3D"tel:%2B46%2073%200949079" value=3D"+467309490=
79" target=3D"_blank">+46 73 0949079</a><br>
SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@e=
ricsson.com" target=3D"_blank">magnus.westerlund@ericsson.com</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
</div></div></blockquote></div><br></div></div>

--001a113e86cc0108e7053ebe09de--


From nobody Thu Oct 13 06:18:16 2016
Return-Path: <magnus.westerlund@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 C08061294F8 for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 06:18:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 zoz0UJW36nPX for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 06:18:13 -0700 (PDT)
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 B5CF0129454 for <mmusic@ietf.org>; Thu, 13 Oct 2016 06:18:12 -0700 (PDT)
X-AuditID: c1b4fb25-15fff7000000793b-17-57ff899098b8
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by  (Symantec Mail Security) with SMTP id 94.3B.31035.0998FF75; Thu, 13 Oct 2016 15:18:11 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.65) with Microsoft SMTP Server id 14.3.319.2; Thu, 13 Oct 2016 15:18:08 +0200
To: Eric Rescorla <ekr@rtfm.com>
References: <D41C238A.1095B%christer.holmberg@ericsson.com> <71419d1f-af1d-46e9-401d-81c5df73fc49@ericsson.com> <58510E68-A045-4312-B3B3-3468E83C8EB7@iii.ca> <243c777f-46f9-4053-1588-7e6b58a06c8c@ericsson.com> <D423DEE7.1101D%christer.holmberg@ericsson.com> <D423FEEE.11074%christer.holmberg@ericsson.com> <CABcZeBO7b3XGRTCzN4-Z-6=8sTD3nrr8HtgN1q9np-hZ3tqbMQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD668D1@ESESSMB209.ericsson.se> <CABcZeBNDpt5F_HZeHC9tavPUKzq-Dw3u2SroKcH4U-k-hWNmyg@mail.gmail.com> <4a000249-91d9-f6b3-5b01-4833e6d359fc@ericsson.com> <CABcZeBNwbWWZPcjothhZEv2L8uSpW=stg5-eyxS_nOYUjNwp8A@mail.gmail.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <53d2e50d-25a5-11da-0062-3bd6dc14fd3b@ericsson.com>
Date: Thu, 13 Oct 2016 15:18:06 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBNwbWWZPcjothhZEv2L8uSpW=stg5-eyxS_nOYUjNwp8A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFLMWRmVeSWpSXmKPExsUyM2K7ve7kzv/hBh3t3BYrXp9jt/iw/gej xdTlj1ksVmw4wOrA4vH3/QcmjyVLfjJ5XD7/kdFj8uM25gCWKC6blNSczLLUIn27BK6MK/+P sBR806g4uWMbawPjNYUuRk4OCQETielLm1m7GLk4hATWM0pc79vNBOEsZ5T4fX4fUIaDQ1gg X2L6lDqQBhEBBYlff06wQNR0sUo0rmxnBnGYBZYxSkyYuIkNpIpNwELi5o9GMJtXwF5i0aKZ TCA2i4CqxJEv3SwgtqhAjMT1Z4+gagQlTs58AhbnFAiUaL35ACzODDRn5vzzjBC2vETz1tnM ILaQgLZEQ1MH6wRGgVlI2mchaZmFpGUBI/MqRtHi1OKk3HQjY73Uoszk4uL8PL281JJNjMAQ Prjlt+oOxstvHA8xCnAwKvHwKlT9CxdiTSwrrsw9xCjBwawkwju97X+4EG9KYmVValF+fFFp TmrxIUZpDhYlcV6zlffDhQTSE0tSs1NTC1KLYLJMHJxSDYwdB/Pl9tveeeDz5j3TpsP71eMm bBHS2iyut3vaxrOeaX6V5mK1Dzd2tXR8uvSkdUOsmWfnBK8Yg0nyMy2Wninhzaq+enTKVyae XVlP/zqc9jiUY13H9Vjk1z7vjecnXpzkecdwB6Ov1gSPI96V26U0AxcU+6e4v+Off+/lwrit R23TT3P521QosRRnJBpqMRcVJwIATsSW+10CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/VTubMuo-1gN0PD8Pj-IvSC0Wbv8>
Cc: Cullen Jennings <fluffy@iii.ca>, "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 13:18:15 -0000

Den 2016-10-13 kl. 14:12, skrev Eric Rescorla:

> On Thu, Oct 13, 2016 at 2:09 AM, Magnus Westerlund
> <magnus.westerlund@ericsson.com <mailto:magnus.westerlund@ericsson.com>>
> wrote:
>
>     Den 2016-10-13 kl. 02:51, skrev Eric Rescorla:
>
>
> I think I am being constructive. I'm trying to get the draft finished,
> and this seems to be poorly motivated.
>

Yes, I am also trying to get it finished by ensuring that we actually 
have a security consideration section that discuss the potential issues.

>
>     I hope you are not disagreeing with a RECOMMEND for source
>     authentication at least? Having third party attackers being able to
>     change the MID on path that is a quite serious attack, so integrity
>     and source authentication I think is well motivated.
>
>
> There seem to be two cases:
>
> 1. You're using SRTP (and this should also include SRTCP).
> 2. You're not using SRTP.
>
> In case #1, then the MID should be integrity protected because it's part
> of the packet. If not, then I don't think a partial solution helps.
>

Yes, I agree that if you are using the SRTP/SRTCP then this is not an 
issue. But, as we clearly point out in RFC 7201 SRTP is not the only 
solution. Thus, I at least try to ensure that any security 
considerations around RTP do discuss the requirements rather than 
mandating a single solution.

Do you have a problem with actually saying that source authentication is 
something that one really should do?

>
>     Regarding the aspects regarding privacy and information leakage. You
>     previously indicated that you agree that we should at least avoid
>     structured MIDs to avoid that implementation specifics or hardware
>     addresses of source devices leaks this way.
>
>
> No, that's not what I said. Rather, I said:
>
> "The first of these seems addressable by guidance about how to construct
> these IDs. I note that we
> have only very limited guidance on how to construct ICE ufrag/passwords...."
>
> If you think this kind of identifier-generation tracking is an issue, I
> would suggest doing a broader survey
> first, rather than focusing on this case.
>

Okay, then I misunderstood your intention with bringing up ICE.

As that broader survey is quite a significant work and something that 
likely spans at least from the transport flow structure, across the RTP 
streams up to the signaling this is quite an undertaking if one want to 
investigate what possibilities exist just for the media protocol part of 
a WebRTC system. No something I will promise to do. I will once more 
remark that our steps from single media streams to multi-stream, 
multi-party setups has changed what we exposes at the different layers.

But, I can agree that BUNDLE is likely not the most appropriate point to 
tackle the fingerprinting issue. So unless someone else is of the 
opinion that is needs to be tackled in BUNDLE i will drop this for now.

However, that doesn't remove the need for an updated MID related 
security consideration. The MID security part in current version is the 
following:

    The identification-tag MUST NOT
    contain any user information, and applications SHALL avoid generating
    the identification-tag using a pattern that enables application
    identification.

This completely ignores the issues with on path modifications. That at 
least needs to be added.

Okay, dropping the fingerprint, I still think the security consideration 
should say something like this:


The identfication-tag when included in the RTP MID SDES item, 
independent of transport, RTCP SDES packet or RTP header extension, can 
expose the value to parties beyond the signaling chain. Therefore, the 
identification-tag MUST NOT contain any user related information for 
privacy reasons nor hardware based identifiers that would enable 
tracking of the sending end point.

The identification-tag is used to route the media stream to the right 
application functionality, thus is important that the value received is 
the one intended by the sender. Malicious modifications can result in 
that a media stream is wrongly attributed or fails to be played. Thus, 
integrity and the authenticity of the source are RECOMMENDED to the 
attacks on the application. Note, that the SDES RTP header extensions 
[RFC7941] requires encryption of the header extension in cases when the 
RTCP encrypts the SDES item. Security mechanisms for RTP/RTCP are 
discussed in Options for Securing RTP Sessions [RFC7201], for example 
SRTP [RFC3711] with SRTCP encryption enabled combined with [RFC6904] can 
provide the necessary security functions.


Is the above more acceptable?

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Oct 13 08:04:03 2016
Return-Path: <fluffy@iii.ca>
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 21FE912946E for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 08:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qiRFhGGSPzEw for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 08:03:56 -0700 (PDT)
Received: from smtp90.iad3a.emailsrvr.com (smtp90.iad3a.emailsrvr.com [173.203.187.90]) (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 AEB581294D5 for <mmusic@ietf.org>; Thu, 13 Oct 2016 08:03:56 -0700 (PDT)
Received: from smtp4.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp4.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id EF56EC07A8; Thu, 13 Oct 2016 11:03:51 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp4.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 23073C0769;  Thu, 13 Oct 2016 11:03:51 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.24.127.141] ([UNAVAILABLE]. [128.107.241.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.7); Thu, 13 Oct 2016 11:03:51 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_858AE8D9-7DCE-403F-BD36-3598A290CBB4"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <D423EDCF.1102F%christer.holmberg@ericsson.com>
Date: Thu, 13 Oct 2016 09:03:49 -0600
Message-Id: <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/SWSCZWQDPnKPK-QQAa4-B9iz6nw>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 15:04:01 -0000

--Apple-Mail=_858AE8D9-7DCE-403F-BD36-3598A290CBB4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


That looks about right for RTP but I think it is still missing stuff for =
RTCP handling. Here is the current text we did for JSEP. I prefer the =
style in which you described it compared to the algorithm style below =
but I think this might help figure out what to write for RTCP.=20



When an RTP packet is received by a transport and passes SRTP =
authentication, that packet needs to be routed to the correct =
RtpReceiver. For each transport, the following steps MUST be followed to =
prepare to route packets:
Construct a table mapping MID to RtpReceiver for each RtpReceiver =
configured to receive from this transport.
Construct a table mapping incoming SSRC to RtpReceiver for each =
RtpReceiver configured to receive from this transport and for each SSRC =
that RtpReceiver is configured to receive. Some of the SSRCs may be =
present in the m=3D section corresponding to that RtpReceiver in the =
remote description.
Construct a table mapping outgoing SSRC to RtpSender for each RtpSender =
configured to transmit from this transport and for each SSRC that =
RtpSender is configured to use when sending.
Construct a table mapping payload type to RtpReceiver for each =
RtpReceiver configured to receive from this transport and for each =
payload type that RtpReceiver is configured to receive. The payload =
types of a given RtpReceiver are found in the m=3D section corresponding =
to that RtpReceiver in the local description. If any payload type could =
map to more than one RtpReceiver, map to the RtpReceiver whose m=3D =
section appears earliest in the local description.
As RtpTransceivers (and, thus, RtpReceivers) are added, removed, =
stopped, or reconfigured, the tables above must also be updated.
For each RTP packet received, the following steps MUST be followed to =
route the packet:
If the packet has a MID and that MID is not in the table mapping MID to =
RtpReceiver, drop the packet and stop.
If the packet has a MID and that MID is in the table mapping MID to =
RtpReceiver, update the incoming SSRC mapping table to include an entry =
that maps the packet's SSRC to the RtpReceiver for that MID.
If the packet's SSRC is in the incoming SSRC mapping table, deliver the =
packet to the associated RtpReceiver and stop.
If the packet's payload type is in the payload type table, update the =
the incoming SSRC mapping table to include an entry that maps the =
packet's SSRC to the RtpReceiver for that payload type. In addition, =
deliver the packet to the associated RtpReceiver and stop.
Otherwise, drop the packet.
For each RTCP packet received (including each RTCP packet that is part =
of a compound RTCP packet), the following type-specific handling MUST be =
performed to route the packet:
If the packet is of type SR, and the sender SSRC for the packet is found =
in the incoming SSRC table, deliver a copy of the packet to the =
RtpReceiver associated with that SSRC. In addition, for each report =
block in the report whose SSRC is found in the outgoing SSRC table, =
deliver a copy of the RTCP packet to the RtpSender associated with that =
SSRC.
If the packet is of type RR, for each report block in the packet whose =
SSRC is found in the outgoing SSRC table, deliver a copy of the RTCP =
packet to the RtpSender associated with that SSRC.
If the packet is of type SDES, and the sender SSRC for the packet is =
found in the incoming SSRC table, deliver the packet to the RtpReceiver =
associated with that SSRC. In addition, for each chunk in the packet =
that contains a MID that is in the table mapping MID to RtpReceiver, =
update the incoming SSRC mapping table to include an entry that maps the =
SSRC for that chunk to the RtpReceiver associated with that MID. (This =
case can occur when RTCP for a source is received before any RTP =
packets.)
If the packet is of type BYE, for each SSRC indicated in the packet that =
is found in the incoming SSRC table, deliver a copy of the packet to the =
RtpReceiver associated with that SSRC.
If the packet is of type RTPFB or PSFB, as defined in [RFC4585] =
<http://rtcweb-wg.github.io/jsep/#RFC4585>, and the media source SSRC =
for the packet is found in the outgoing SSRC table, deliver the packet =
to the RtpSender associated with that SSRC.
After packets are routed to the RtpReceiver, further processing of the =
RTP packets is done at the RtpReceiver level. This includes using =
[I-D.ietf-mmusic-rid] =
<http://rtcweb-wg.github.io/jsep/#I-D.ietf-mmusic-rid> to distinguish =
between multiple Encoded Streams, as well as determine which Source RTP =
stream should be repaired by a given Redundancy RTP stream. If the RTP =
packet's PT does not match any codec in use by the RtpReceiver, the =
packet will be dropped.



> On Oct 12, 2016, at 4:37 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> I=C4=85ve created a pull request with additional text regarding =
associating
> RTP/RTCP packets with the correct =C5=82m=3D=C5=82 line.
>=20
> https://github.com/cdh4u/draft-sdp-bundle/pull/10
>=20
>=20
> Regards,
>=20
> Christer
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


--Apple-Mail=_858AE8D9-7DCE-403F-BD36-3598A290CBB4
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; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D""><br class=3D""></div>That looks about right =
for RTP but I think it is still missing stuff for RTCP handling. Here is =
the current text we did for JSEP. I prefer the style in which you =
described it compared to the algorithm style below but I think this =
might help figure out what to write for RTCP.&nbsp;<div class=3D""><br =
class=3D""></div><div class=3D""><span style=3D"color: rgb(51, 51, 51); =
font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: =
15px; orphans: 2; widows: 2;" class=3D""><br class=3D""></span></div><div =
class=3D""><span style=3D"color: rgb(51, 51, 51); font-family: =
'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 15px; =
orphans: 2; widows: 2;" class=3D""><br class=3D""></span></div><div =
class=3D""><span style=3D"color: rgb(51, 51, 51); font-family: =
'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 15px; =
orphans: 2; widows: 2;" class=3D"">When an RTP packet is received by a =
transport and passes SRTP authentication, that packet needs to be routed =
to the correct RtpReceiver. For each transport, the following steps MUST =
be followed to prepare to route packets:</span></div><div class=3D""><p =
style=3D"padding: 0px; margin: 0.5em 0px; color: rgb(51, 51, 51); =
font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: =
15px; font-variant-ligatures: normal; orphans: 2; widows: 2;" =
class=3D""></p><ul class=3D"empty" style=3D"padding: 0px; margin: 0.5em =
0px 0.5em 2em; list-style-type: none; color: rgb(51, 51, 51); =
font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: =
15px; font-variant-ligatures: normal; orphans: 2; widows: 2;"><li =
style=3D"padding: 0px; margin: 0.5em 0px;" class=3D"">Construct a table =
mapping MID to RtpReceiver for each RtpReceiver configured to receive =
from this transport.</li><li style=3D"padding: 0px; margin: 0.5em 0px;" =
class=3D"">Construct a table mapping incoming SSRC to RtpReceiver for =
each RtpReceiver configured to receive from this transport and for each =
SSRC that RtpReceiver is configured to receive. Some of the SSRCs may be =
present in the m=3D section corresponding to that RtpReceiver in the =
remote description.</li><li style=3D"padding: 0px; margin: 0.5em 0px;" =
class=3D"">Construct a table mapping outgoing SSRC to RtpSender for each =
RtpSender configured to transmit from this transport and for each SSRC =
that RtpSender is configured to use when sending.</li><li =
style=3D"padding: 0px; margin: 0.5em 0px;" class=3D"">Construct a table =
mapping payload type to RtpReceiver for each RtpReceiver configured to =
receive from this transport and for each payload type that RtpReceiver =
is configured to receive. The payload types of a given RtpReceiver are =
found in the m=3D section corresponding to that RtpReceiver in the local =
description. If any payload type could map to more than one RtpReceiver, =
map to the RtpReceiver whose m=3D section appears earliest in the local =
description.</li></ul><p style=3D"padding: 0px; margin: 0.5em 0px; =
color: rgb(51, 51, 51); font-family: 'Helvetica Neue', Helvetica, Arial, =
sans-serif; font-size: 15px; font-variant-ligatures: normal; orphans: 2; =
widows: 2;" class=3D""></p><div style=3D"padding: 0px; margin: 0.5em =
0px; color: rgb(51, 51, 51); font-family: 'Helvetica Neue', Helvetica, =
Arial, sans-serif; font-size: 15px; font-variant-ligatures: normal; =
orphans: 2; widows: 2;" class=3D"">As RtpTransceivers (and, thus, =
RtpReceivers) are added, removed, stopped, or reconfigured, the tables =
above must also be updated.</div><div style=3D"padding: 0px; margin: =
0.5em 0px; color: rgb(51, 51, 51); font-family: 'Helvetica Neue', =
Helvetica, Arial, sans-serif; font-size: 15px; font-variant-ligatures: =
normal; orphans: 2; widows: 2;" class=3D"">For each RTP packet received, =
the following steps MUST be followed to route the packet:</div><p =
style=3D"padding: 0px; margin: 0.5em 0px; color: rgb(51, 51, 51); =
font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: =
15px; font-variant-ligatures: normal; orphans: 2; widows: 2;" =
class=3D""></p><ul class=3D"empty" style=3D"padding: 0px; margin: 0.5em =
0px 0.5em 2em; list-style-type: none; color: rgb(51, 51, 51); =
font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: =
15px; font-variant-ligatures: normal; orphans: 2; widows: 2;"><li =
style=3D"padding: 0px; margin: 0.5em 0px;" class=3D"">If the packet has =
a MID and that MID is not in the table mapping MID to RtpReceiver, drop =
the packet and stop.</li><li style=3D"padding: 0px; margin: 0.5em 0px;" =
class=3D"">If the packet has a MID and that MID is in the table mapping =
MID to RtpReceiver, update the incoming SSRC mapping table to include an =
entry that maps the packet's SSRC to the RtpReceiver for that =
MID.</li><li style=3D"padding: 0px; margin: 0.5em 0px;" class=3D"">If =
the packet's SSRC is in the incoming SSRC mapping table, deliver the =
packet to the associated RtpReceiver and stop.</li><li style=3D"padding: =
0px; margin: 0.5em 0px;" class=3D"">If the packet's payload type is in =
the payload type table, update the the incoming SSRC mapping table to =
include an entry that maps the packet's SSRC to the RtpReceiver for that =
payload type. In addition, deliver the packet to the associated =
RtpReceiver and stop.</li><li style=3D"padding: 0px; margin: 0.5em 0px;" =
class=3D"">Otherwise, drop the packet.</li></ul><p style=3D"padding: =
0px; margin: 0.5em 0px; color: rgb(51, 51, 51); font-family: 'Helvetica =
Neue', Helvetica, Arial, sans-serif; font-size: 15px; =
font-variant-ligatures: normal; orphans: 2; widows: 2;" =
class=3D""></p><div style=3D"padding: 0px; margin: 0.5em 0px; color: =
rgb(51, 51, 51); font-family: 'Helvetica Neue', Helvetica, Arial, =
sans-serif; font-size: 15px; font-variant-ligatures: normal; orphans: 2; =
widows: 2;" class=3D"">For each RTCP packet received (including each =
RTCP packet that is part of a compound RTCP packet), the following =
type-specific handling MUST be performed to route the packet:</div><p =
style=3D"padding: 0px; margin: 0.5em 0px; color: rgb(51, 51, 51); =
font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: =
15px; font-variant-ligatures: normal; orphans: 2; widows: 2;" =
class=3D""></p><ul class=3D"empty" style=3D"padding: 0px; margin: 0.5em =
0px 0.5em 2em; list-style-type: none; color: rgb(51, 51, 51); =
font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: =
15px; font-variant-ligatures: normal; orphans: 2; widows: 2;"><li =
style=3D"padding: 0px; margin: 0.5em 0px;" class=3D"">If the packet is =
of type SR, and the sender SSRC for the packet is found in the incoming =
SSRC table, deliver a copy of the packet to the RtpReceiver associated =
with that SSRC. In addition, for each report block in the report whose =
SSRC is found in the outgoing SSRC table, deliver a copy of the RTCP =
packet to the RtpSender associated with that SSRC.</li><li =
style=3D"padding: 0px; margin: 0.5em 0px;" class=3D"">If the packet is =
of type RR, for each report block in the packet whose SSRC is found in =
the outgoing SSRC table, deliver a copy of the RTCP packet to the =
RtpSender associated with that SSRC.</li><li style=3D"padding: 0px; =
margin: 0.5em 0px;" class=3D"">If the packet is of type SDES, and the =
sender SSRC for the packet is found in the incoming SSRC table, deliver =
the packet to the RtpReceiver associated with that SSRC. In addition, =
for each chunk in the packet that contains a MID that is in the table =
mapping MID to RtpReceiver, update the incoming SSRC mapping table to =
include an entry that maps the SSRC for that chunk to the RtpReceiver =
associated with that MID. (This case can occur when RTCP for a source is =
received before any RTP packets.)</li><li style=3D"padding: 0px; margin: =
0.5em 0px;" class=3D"">If the packet is of type BYE, for each SSRC =
indicated in the packet that is found in the incoming SSRC table, =
deliver a copy of the packet to the RtpReceiver associated with that =
SSRC.</li><li style=3D"padding: 0px; margin: 0.5em 0px;" class=3D"">If =
the packet is of type RTPFB or PSFB, as defined in&nbsp;<a =
href=3D"http://rtcweb-wg.github.io/jsep/#RFC4585" =
style=3D"text-decoration: none; color: rgb(42, 100, 150);" =
class=3D"">[RFC4585]</a>, and the media source SSRC for the packet is =
found in the outgoing SSRC table, deliver the packet to the RtpSender =
associated with that SSRC.</li></ul><p style=3D"padding: 0px; margin: =
0.5em 0px; color: rgb(51, 51, 51); font-family: 'Helvetica Neue', =
Helvetica, Arial, sans-serif; font-size: 15px; font-variant-ligatures: =
normal; orphans: 2; widows: 2;" class=3D""></p><div style=3D"padding: =
0px; margin: 0.5em 0px; color: rgb(51, 51, 51); font-family: 'Helvetica =
Neue', Helvetica, Arial, sans-serif; font-size: 15px; =
font-variant-ligatures: normal; orphans: 2; widows: 2;" class=3D"">After =
packets are routed to the RtpReceiver, further processing of the RTP =
packets is done at the RtpReceiver level. This includes using&nbsp;<a =
href=3D"http://rtcweb-wg.github.io/jsep/#I-D.ietf-mmusic-rid" =
style=3D"text-decoration: none; color: rgb(42, 100, 150);" =
class=3D"">[I-D.ietf-mmusic-rid]</a>&nbsp;to distinguish between =
multiple Encoded Streams, as well as determine which Source RTP stream =
should be repaired by a given Redundancy RTP stream. If the RTP packet's =
PT does not match any codec in use by the RtpReceiver, the packet will =
be dropped.</div><h1 id=3D"rfc.section.7" style=3D"font-family: =
'Helvetica Neue', Helvetica, Arial, sans-serif; font-weight: 500; color: =
rgb(51, 51, 51); line-height: 30px; margin: 0.8em 0px 0.3em; font-size: =
30px; font-variant-ligatures: normal; orphans: 2; widows: 2;" =
class=3D""></h1><div style=3D"padding: 0px; margin: 0.5em 0px; color: =
rgb(51, 51, 51); font-family: 'Helvetica Neue', Helvetica, Arial, =
sans-serif; font-size: 15px; font-variant-ligatures: normal; orphans: 2; =
widows: 2;" class=3D""><br class=3D""></div></div><div style=3D"padding: =
0px; margin: 0.5em 0px; color: rgb(51, 51, 51); font-family: 'Helvetica =
Neue', Helvetica, Arial, sans-serif; font-size: 15px; =
font-variant-ligatures: normal; orphans: 2; widows: 2;" class=3D""><br =
class=3D""></div><div style=3D"padding: 0px; margin: 0.5em 0px; color: =
rgb(51, 51, 51); font-family: 'Helvetica Neue', Helvetica, Arial, =
sans-serif; font-size: 15px; font-variant-ligatures: normal; orphans: 2; =
widows: 2;" class=3D""><br class=3D""></div><div><blockquote type=3D"cite"=
 class=3D""><div class=3D"">On Oct 12, 2016, at 4:37 AM, Christer =
Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com" =
class=3D"">christer.holmberg@ericsson.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">Hi,<br=
 class=3D""><br class=3D"">I=C4=85ve created a pull request with =
additional text regarding associating<br class=3D"">RTP/RTCP packets =
with the correct =C5=82m=3D=C5=82 line.<br class=3D""><br class=3D""><a =
href=3D"https://github.com/cdh4u/draft-sdp-bundle/pull/10" =
class=3D"">https://github.com/cdh4u/draft-sdp-bundle/pull/10</a><br =
class=3D""><br class=3D""><br class=3D"">Regards,<br class=3D""><br =
class=3D"">Christer<br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">mmusic mailing list<br class=3D"">mmusic@ietf.org<br =
class=3D"">https://www.ietf.org/mailman/listinfo/mmusic<br =
class=3D""></div></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_858AE8D9-7DCE-403F-BD36-3598A290CBB4--


From nobody Thu Oct 13 08:40:27 2016
Return-Path: <fluffy@iii.ca>
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 E9B47129564 for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 08:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, 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 mb0aa7ihZRUT for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 08:40:24 -0700 (PDT)
Received: from smtp146.dfw.emailsrvr.com (smtp146.dfw.emailsrvr.com [67.192.241.146]) (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 5554212954B for <mmusic@ietf.org>; Thu, 13 Oct 2016 08:40:24 -0700 (PDT)
Received: from smtp27.relay.dfw1a.emailsrvr.com (localhost [127.0.0.1]) by smtp27.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id BF267A0328; Thu, 13 Oct 2016 11:40:23 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp27.relay.dfw1a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 4CF88A02D6;  Thu, 13 Oct 2016 11:40:23 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.24.127.141] ([UNAVAILABLE]. [128.107.241.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.7); Thu, 13 Oct 2016 11:40:23 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD67769@ESESSMB209.ericsson.se>
Date: Thu, 13 Oct 2016 09:40:21 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <44BB624B-BDAF-45B8-94ED-432B56D0589F@iii.ca>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca> <CAD5OKxtHQ6PRszm13vAKdR3VZB1LP5Uffq8YWHTT=_i4P4h+aA@mail.gmail.com> <445CBF55-8999-4F08-9FE4-AC4B88760FB8@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD67769@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MGkELWz7qpvbcV67Y3odFFSeaSs>
Cc: Roman Shpount <rshpount@gmail.com>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 15:40:26 -0000

> On Oct 13, 2016, at 1:07 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
>> I think it still needs to require a fingerprint from the hash used in =
the cert signature to be >backwards compatible with 4572.
>=20
> Version -07 contains the following text - which was added based on =
your comments:
>=20
>    "An endpoint MUST, as a minimum, calculate a fingerprint using both =
the 'SHA-256'
>    hash function algorithm and the hash function used to generate the
>    signature on the certificate for each possible certificate."
>=20
>=20

Yah, I think that is the right text for RFC-B.=20



From nobody Thu Oct 13 09:01:36 2016
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 B327D12953F for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 09:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 s1BLufug_sYD for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 09:01:31 -0700 (PDT)
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 E5D1D129519 for <mmusic@ietf.org>; Thu, 13 Oct 2016 09:01:30 -0700 (PDT)
X-AuditID: c1b4fb30-b87ff70000000cb2-5a-57ffafd6d650
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by  (Symantec Mail Security) with SMTP id DD.B7.03250.6DFAFF75; Thu, 13 Oct 2016 18:01:29 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0319.002; Thu, 13 Oct 2016 18:01:26 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Cullen Jennings <fluffy@iii.ca>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
Thread-Index: AQHSJHSivk5Ucbs2BE2kFscuEARQNKCmW5CAgAAxTzA=
Date: Thu, 13 Oct 2016 16:01:25 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca>
In-Reply-To: <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BD6861AESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCIsWRmVeSWpSXmKPExsUyM2K7qO7N9f/DDf7fEbT4sP4Ho8XU5Y9Z HJg8liz5yeRx+fxHxgCmKC6blNSczLLUIn27BK6MHS/usRTcuMVUsfrWRfYGxgsXmboYOTkk BEwkNu7qZe5i5OIQEljPKLFsyh8mCGcJo8SNto8sXYwcHGwCFhLd/7RBGkQElCXO7bjLDGIz C8RK7Dg6jRHEFhbIkJg/eRtYuYhApsSKlX4Q5VYS1ye+ANvFIqAq8fDlUbBWXgFfickf34C1 CglkS6zadIgNxOYEqr+1uQ2snlFATOL7qTVMEKvEJW49mQ91s4DEkj3nmSFsUYmXj/+xQthK Eo1LnrBC1OdLnN6ynw1il6DEyZlPWCYwisxCMmoWkrJZSMpmAX3ALKApsX6XPkSJosSU7ofs ELaGROucuezI4gsY2VcxihanFiflphsZ6aUWZSYXF+fn6eWllmxiBMbVwS2/DXYwvnzueIhR gINRiYdXoepfuBBrYllxZe4hRgkOZiUR3pw1/8OFeFMSK6tSi/Lji0pzUosPMUpzsCiJ85qt vB8uJJCeWJKanZpakFoEk2Xi4JRqYIxufHpU9iPzacUrvrfnVWqsODjz9b7kiOk/uTYfEGo4 9r1szemnl+asP7xtRnPIrr7JVw4/cv/yVr2Wr/HBpYuBMy1S1BgqM9fO9bL8PyOk88Fquehl TBc2Touu3uUyL0yfeYPe5CL2240HloRbfvMOEfbTPBy+6dI9iSiujTNdZwawFVz71eCtxFKc kWioxVxUnAgAyAT/A6cCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/VRm-ihcxFT9bYurYqDZRD61dXXw>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 16:01:35 -0000

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

SGksDQoNClJUQ1AgcGFja2V0cyBjYW4gYmUgYXNzb2NpYXRlZCB3aXRoIG0tIGxpbmVzIGluIHRo
ZSBzYW1lIHdheSBhcyBSVFAgcGFja2V0cy4NCg0KSG93ZXZlciwgTWFnbnVzIHRvbGQgbWUgaXTi
gJlzIG5vdCBuZWVkZWQsIHNvIEnigJlkIGxpa2UgdG8gZ2V0IHNvbWUgaW5wdXQgZnJvbSBoaW0u
DQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCkZyb206IEN1bGxlbiBKZW5uaW5ncyBbbWFpbHRv
OmZsdWZmeUBpaWkuY2FdDQpTZW50OiAxMyBPY3RvYmVyIDIwMTYgMTg6MDQNClRvOiBDaHJpc3Rl
ciBIb2xtYmVyZyA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPg0KQ2M6IG1tdXNpY0Bp
ZXRmLm9yZzsgTWFnbnVzIFdlc3Rlcmx1bmQgPG1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNv
bT4NClN1YmplY3Q6IFJlOiBbTU1VU0lDXSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1tbXVzaWMtc2Rw
LWJ1bmRsZS1uZWdvdGlhdGlvbi0zMiAtIFJUUCBkZW11eCAtIFB1bGwgUmVxdWVzdA0KDQoNClRo
YXQgbG9va3MgYWJvdXQgcmlnaHQgZm9yIFJUUCBidXQgSSB0aGluayBpdCBpcyBzdGlsbCBtaXNz
aW5nIHN0dWZmIGZvciBSVENQIGhhbmRsaW5nLiBIZXJlIGlzIHRoZSBjdXJyZW50IHRleHQgd2Ug
ZGlkIGZvciBKU0VQLiBJIHByZWZlciB0aGUgc3R5bGUgaW4gd2hpY2ggeW91IGRlc2NyaWJlZCBp
dCBjb21wYXJlZCB0byB0aGUgYWxnb3JpdGhtIHN0eWxlIGJlbG93IGJ1dCBJIHRoaW5rIHRoaXMg
bWlnaHQgaGVscCBmaWd1cmUgb3V0IHdoYXQgdG8gd3JpdGUgZm9yIFJUQ1AuDQoNCg0KDQoNCg0K
V2hlbiBhbiBSVFAgcGFja2V0IGlzIHJlY2VpdmVkIGJ5IGEgdHJhbnNwb3J0IGFuZCBwYXNzZXMg
U1JUUCBhdXRoZW50aWNhdGlvbiwgdGhhdCBwYWNrZXQgbmVlZHMgdG8gYmUgcm91dGVkIHRvIHRo
ZSBjb3JyZWN0IFJ0cFJlY2VpdmVyLiBGb3IgZWFjaCB0cmFuc3BvcnQsIHRoZSBmb2xsb3dpbmcg
c3RlcHMgTVVTVCBiZSBmb2xsb3dlZCB0byBwcmVwYXJlIHRvIHJvdXRlIHBhY2tldHM6DQrCtyAg
ICAgICBDb25zdHJ1Y3QgYSB0YWJsZSBtYXBwaW5nIE1JRCB0byBSdHBSZWNlaXZlciBmb3IgZWFj
aCBSdHBSZWNlaXZlciBjb25maWd1cmVkIHRvIHJlY2VpdmUgZnJvbSB0aGlzIHRyYW5zcG9ydC4N
CsK3ICAgICAgIENvbnN0cnVjdCBhIHRhYmxlIG1hcHBpbmcgaW5jb21pbmcgU1NSQyB0byBSdHBS
ZWNlaXZlciBmb3IgZWFjaCBSdHBSZWNlaXZlciBjb25maWd1cmVkIHRvIHJlY2VpdmUgZnJvbSB0
aGlzIHRyYW5zcG9ydCBhbmQgZm9yIGVhY2ggU1NSQyB0aGF0IFJ0cFJlY2VpdmVyIGlzIGNvbmZp
Z3VyZWQgdG8gcmVjZWl2ZS4gU29tZSBvZiB0aGUgU1NSQ3MgbWF5IGJlIHByZXNlbnQgaW4gdGhl
IG09IHNlY3Rpb24gY29ycmVzcG9uZGluZyB0byB0aGF0IFJ0cFJlY2VpdmVyIGluIHRoZSByZW1v
dGUgZGVzY3JpcHRpb24uDQrCtyAgICAgICBDb25zdHJ1Y3QgYSB0YWJsZSBtYXBwaW5nIG91dGdv
aW5nIFNTUkMgdG8gUnRwU2VuZGVyIGZvciBlYWNoIFJ0cFNlbmRlciBjb25maWd1cmVkIHRvIHRy
YW5zbWl0IGZyb20gdGhpcyB0cmFuc3BvcnQgYW5kIGZvciBlYWNoIFNTUkMgdGhhdCBSdHBTZW5k
ZXIgaXMgY29uZmlndXJlZCB0byB1c2Ugd2hlbiBzZW5kaW5nLg0KwrcgICAgICAgQ29uc3RydWN0
IGEgdGFibGUgbWFwcGluZyBwYXlsb2FkIHR5cGUgdG8gUnRwUmVjZWl2ZXIgZm9yIGVhY2ggUnRw
UmVjZWl2ZXIgY29uZmlndXJlZCB0byByZWNlaXZlIGZyb20gdGhpcyB0cmFuc3BvcnQgYW5kIGZv
ciBlYWNoIHBheWxvYWQgdHlwZSB0aGF0IFJ0cFJlY2VpdmVyIGlzIGNvbmZpZ3VyZWQgdG8gcmVj
ZWl2ZS4gVGhlIHBheWxvYWQgdHlwZXMgb2YgYSBnaXZlbiBSdHBSZWNlaXZlciBhcmUgZm91bmQg
aW4gdGhlIG09IHNlY3Rpb24gY29ycmVzcG9uZGluZyB0byB0aGF0IFJ0cFJlY2VpdmVyIGluIHRo
ZSBsb2NhbCBkZXNjcmlwdGlvbi4gSWYgYW55IHBheWxvYWQgdHlwZSBjb3VsZCBtYXAgdG8gbW9y
ZSB0aGFuIG9uZSBSdHBSZWNlaXZlciwgbWFwIHRvIHRoZSBSdHBSZWNlaXZlciB3aG9zZSBtPSBz
ZWN0aW9uIGFwcGVhcnMgZWFybGllc3QgaW4gdGhlIGxvY2FsIGRlc2NyaXB0aW9uLg0KQXMgUnRw
VHJhbnNjZWl2ZXJzIChhbmQsIHRodXMsIFJ0cFJlY2VpdmVycykgYXJlIGFkZGVkLCByZW1vdmVk
LCBzdG9wcGVkLCBvciByZWNvbmZpZ3VyZWQsIHRoZSB0YWJsZXMgYWJvdmUgbXVzdCBhbHNvIGJl
IHVwZGF0ZWQuDQpGb3IgZWFjaCBSVFAgcGFja2V0IHJlY2VpdmVkLCB0aGUgZm9sbG93aW5nIHN0
ZXBzIE1VU1QgYmUgZm9sbG93ZWQgdG8gcm91dGUgdGhlIHBhY2tldDoNCsK3ICAgICAgIElmIHRo
ZSBwYWNrZXQgaGFzIGEgTUlEIGFuZCB0aGF0IE1JRCBpcyBub3QgaW4gdGhlIHRhYmxlIG1hcHBp
bmcgTUlEIHRvIFJ0cFJlY2VpdmVyLCBkcm9wIHRoZSBwYWNrZXQgYW5kIHN0b3AuDQrCtyAgICAg
ICBJZiB0aGUgcGFja2V0IGhhcyBhIE1JRCBhbmQgdGhhdCBNSUQgaXMgaW4gdGhlIHRhYmxlIG1h
cHBpbmcgTUlEIHRvIFJ0cFJlY2VpdmVyLCB1cGRhdGUgdGhlIGluY29taW5nIFNTUkMgbWFwcGlu
ZyB0YWJsZSB0byBpbmNsdWRlIGFuIGVudHJ5IHRoYXQgbWFwcyB0aGUgcGFja2V0J3MgU1NSQyB0
byB0aGUgUnRwUmVjZWl2ZXIgZm9yIHRoYXQgTUlELg0KwrcgICAgICAgSWYgdGhlIHBhY2tldCdz
IFNTUkMgaXMgaW4gdGhlIGluY29taW5nIFNTUkMgbWFwcGluZyB0YWJsZSwgZGVsaXZlciB0aGUg
cGFja2V0IHRvIHRoZSBhc3NvY2lhdGVkIFJ0cFJlY2VpdmVyIGFuZCBzdG9wLg0KwrcgICAgICAg
SWYgdGhlIHBhY2tldCdzIHBheWxvYWQgdHlwZSBpcyBpbiB0aGUgcGF5bG9hZCB0eXBlIHRhYmxl
LCB1cGRhdGUgdGhlIHRoZSBpbmNvbWluZyBTU1JDIG1hcHBpbmcgdGFibGUgdG8gaW5jbHVkZSBh
biBlbnRyeSB0aGF0IG1hcHMgdGhlIHBhY2tldCdzIFNTUkMgdG8gdGhlIFJ0cFJlY2VpdmVyIGZv
ciB0aGF0IHBheWxvYWQgdHlwZS4gSW4gYWRkaXRpb24sIGRlbGl2ZXIgdGhlIHBhY2tldCB0byB0
aGUgYXNzb2NpYXRlZCBSdHBSZWNlaXZlciBhbmQgc3RvcC4NCsK3ICAgICAgIE90aGVyd2lzZSwg
ZHJvcCB0aGUgcGFja2V0Lg0KRm9yIGVhY2ggUlRDUCBwYWNrZXQgcmVjZWl2ZWQgKGluY2x1ZGlu
ZyBlYWNoIFJUQ1AgcGFja2V0IHRoYXQgaXMgcGFydCBvZiBhIGNvbXBvdW5kIFJUQ1AgcGFja2V0
KSwgdGhlIGZvbGxvd2luZyB0eXBlLXNwZWNpZmljIGhhbmRsaW5nIE1VU1QgYmUgcGVyZm9ybWVk
IHRvIHJvdXRlIHRoZSBwYWNrZXQ6DQrCtyAgICAgICBJZiB0aGUgcGFja2V0IGlzIG9mIHR5cGUg
U1IsIGFuZCB0aGUgc2VuZGVyIFNTUkMgZm9yIHRoZSBwYWNrZXQgaXMgZm91bmQgaW4gdGhlIGlu
Y29taW5nIFNTUkMgdGFibGUsIGRlbGl2ZXIgYSBjb3B5IG9mIHRoZSBwYWNrZXQgdG8gdGhlIFJ0
cFJlY2VpdmVyIGFzc29jaWF0ZWQgd2l0aCB0aGF0IFNTUkMuIEluIGFkZGl0aW9uLCBmb3IgZWFj
aCByZXBvcnQgYmxvY2sgaW4gdGhlIHJlcG9ydCB3aG9zZSBTU1JDIGlzIGZvdW5kIGluIHRoZSBv
dXRnb2luZyBTU1JDIHRhYmxlLCBkZWxpdmVyIGEgY29weSBvZiB0aGUgUlRDUCBwYWNrZXQgdG8g
dGhlIFJ0cFNlbmRlciBhc3NvY2lhdGVkIHdpdGggdGhhdCBTU1JDLg0KwrcgICAgICAgSWYgdGhl
IHBhY2tldCBpcyBvZiB0eXBlIFJSLCBmb3IgZWFjaCByZXBvcnQgYmxvY2sgaW4gdGhlIHBhY2tl
dCB3aG9zZSBTU1JDIGlzIGZvdW5kIGluIHRoZSBvdXRnb2luZyBTU1JDIHRhYmxlLCBkZWxpdmVy
IGEgY29weSBvZiB0aGUgUlRDUCBwYWNrZXQgdG8gdGhlIFJ0cFNlbmRlciBhc3NvY2lhdGVkIHdp
dGggdGhhdCBTU1JDLg0KwrcgICAgICAgSWYgdGhlIHBhY2tldCBpcyBvZiB0eXBlIFNERVMsIGFu
ZCB0aGUgc2VuZGVyIFNTUkMgZm9yIHRoZSBwYWNrZXQgaXMgZm91bmQgaW4gdGhlIGluY29taW5n
IFNTUkMgdGFibGUsIGRlbGl2ZXIgdGhlIHBhY2tldCB0byB0aGUgUnRwUmVjZWl2ZXIgYXNzb2Np
YXRlZCB3aXRoIHRoYXQgU1NSQy4gSW4gYWRkaXRpb24sIGZvciBlYWNoIGNodW5rIGluIHRoZSBw
YWNrZXQgdGhhdCBjb250YWlucyBhIE1JRCB0aGF0IGlzIGluIHRoZSB0YWJsZSBtYXBwaW5nIE1J
RCB0byBSdHBSZWNlaXZlciwgdXBkYXRlIHRoZSBpbmNvbWluZyBTU1JDIG1hcHBpbmcgdGFibGUg
dG8gaW5jbHVkZSBhbiBlbnRyeSB0aGF0IG1hcHMgdGhlIFNTUkMgZm9yIHRoYXQgY2h1bmsgdG8g
dGhlIFJ0cFJlY2VpdmVyIGFzc29jaWF0ZWQgd2l0aCB0aGF0IE1JRC4gKFRoaXMgY2FzZSBjYW4g
b2NjdXIgd2hlbiBSVENQIGZvciBhIHNvdXJjZSBpcyByZWNlaXZlZCBiZWZvcmUgYW55IFJUUCBw
YWNrZXRzLikNCsK3ICAgICAgIElmIHRoZSBwYWNrZXQgaXMgb2YgdHlwZSBCWUUsIGZvciBlYWNo
IFNTUkMgaW5kaWNhdGVkIGluIHRoZSBwYWNrZXQgdGhhdCBpcyBmb3VuZCBpbiB0aGUgaW5jb21p
bmcgU1NSQyB0YWJsZSwgZGVsaXZlciBhIGNvcHkgb2YgdGhlIHBhY2tldCB0byB0aGUgUnRwUmVj
ZWl2ZXIgYXNzb2NpYXRlZCB3aXRoIHRoYXQgU1NSQy4NCsK3ICAgICAgIElmIHRoZSBwYWNrZXQg
aXMgb2YgdHlwZSBSVFBGQiBvciBQU0ZCLCBhcyBkZWZpbmVkIGluIFtSRkM0NTg1XTxodHRwOi8v
cnRjd2ViLXdnLmdpdGh1Yi5pby9qc2VwLyNSRkM0NTg1PiwgYW5kIHRoZSBtZWRpYSBzb3VyY2Ug
U1NSQyBmb3IgdGhlIHBhY2tldCBpcyBmb3VuZCBpbiB0aGUgb3V0Z29pbmcgU1NSQyB0YWJsZSwg
ZGVsaXZlciB0aGUgcGFja2V0IHRvIHRoZSBSdHBTZW5kZXIgYXNzb2NpYXRlZCB3aXRoIHRoYXQg
U1NSQy4NCkFmdGVyIHBhY2tldHMgYXJlIHJvdXRlZCB0byB0aGUgUnRwUmVjZWl2ZXIsIGZ1cnRo
ZXIgcHJvY2Vzc2luZyBvZiB0aGUgUlRQIHBhY2tldHMgaXMgZG9uZSBhdCB0aGUgUnRwUmVjZWl2
ZXIgbGV2ZWwuIFRoaXMgaW5jbHVkZXMgdXNpbmcgW0ktRC5pZXRmLW1tdXNpYy1yaWRdPGh0dHA6
Ly9ydGN3ZWItd2cuZ2l0aHViLmlvL2pzZXAvI0ktRC5pZXRmLW1tdXNpYy1yaWQ+IHRvIGRpc3Rp
bmd1aXNoIGJldHdlZW4gbXVsdGlwbGUgRW5jb2RlZCBTdHJlYW1zLCBhcyB3ZWxsIGFzIGRldGVy
bWluZSB3aGljaCBTb3VyY2UgUlRQIHN0cmVhbSBzaG91bGQgYmUgcmVwYWlyZWQgYnkgYSBnaXZl
biBSZWR1bmRhbmN5IFJUUCBzdHJlYW0uIElmIHRoZSBSVFAgcGFja2V0J3MgUFQgZG9lcyBub3Qg
bWF0Y2ggYW55IGNvZGVjIGluIHVzZSBieSB0aGUgUnRwUmVjZWl2ZXIsIHRoZSBwYWNrZXQgd2ls
bCBiZSBkcm9wcGVkLg0KDQoNCg0KT24gT2N0IDEyLCAyMDE2LCBhdCA0OjM3IEFNLCBDaHJpc3Rl
ciBIb2xtYmVyZyA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPG1haWx0bzpjaHJpc3Rl
ci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+PiB3cm90ZToNCg0KSGksDQoNCknEhXZlIGNyZWF0ZWQg
YSBwdWxsIHJlcXVlc3Qgd2l0aCBhZGRpdGlvbmFsIHRleHQgcmVnYXJkaW5nIGFzc29jaWF0aW5n
DQpSVFAvUlRDUCBwYWNrZXRzIHdpdGggdGhlIGNvcnJlY3QgxYJtPcWCIGxpbmUuDQoNCmh0dHBz
Oi8vZ2l0aHViLmNvbS9jZGg0dS9kcmFmdC1zZHAtYnVuZGxlL3B1bGwvMTANCg0KDQpSZWdhcmRz
LA0KDQpDaHJpc3Rlcg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KbW11c2ljIG1haWxpbmcgbGlzdA0KbW11c2ljQGlldGYub3JnPG1haWx0bzptbXVz
aWNAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNp
Yw0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7
fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToy
IDQgNSAzIDUgNCA2IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsN
CglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAq
Lw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNt
Ow0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFt
aWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCmgxDQoJe21zby1zdHlsZS1wcmlvcml0eTo5
Ow0KCW1zby1zdHlsZS1saW5rOiJIZWFkaW5nIDEgQ2hhciI7DQoJbXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBjbTsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsN
CgltYXJnaW4tbGVmdDowY207DQoJZm9udC1zaXplOjI0LjBwdDsNCglmb250LWZhbWlseToiVGlt
ZXMgTmV3IFJvbWFuIixzZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxp
bmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1w
cmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9
DQpzcGFuLkhlYWRpbmcxQ2hhcg0KCXttc28tc3R5bGUtbmFtZToiSGVhZGluZyAxIENoYXIiOw0K
CW1zby1zdHlsZS1wcmlvcml0eTo5Ow0KCW1zby1zdHlsZS1saW5rOiJIZWFkaW5nIDEiOw0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIExpZ2h0IixzYW5zLXNlcmlmOw0KCWNvbG9yOiMyRTc0QjU7fQ0K
c3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9u
dC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hw
RGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0
O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46
NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpX
b3JkU2VjdGlvbjE7fQ0KLyogTGlzdCBEZWZpbml0aW9ucyAqLw0KQGxpc3QgbDANCgl7bXNvLWxp
c3QtaWQ6MTIzMTc3NDQzOTsNCgltc28tbGlzdC10ZW1wbGF0ZS1pZHM6LTI4NTMyNjI3ODt9DQpA
bGlzdCBsMDpsZXZlbDENCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1s
ZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MzYuMHB0Ow0KCW1zby1sZXZlbC1u
dW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCW1zby1hbnNpLWZv
bnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxldmVsMg0K
CXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCglt
c28tbGV2ZWwtdGFiLXN0b3A6NzIuMHB0Ow0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJ
Zm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCgltc28tYmlkaS1mb250LWZhbWlseToiVGltZXMg
TmV3IFJvbWFuIjt9DQpAbGlzdCBsMDpsZXZlbDMNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6
YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MTA4LjBw
dDsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBw
dDsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9
DQpAbGlzdCBsMDpsZXZlbDQNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1z
by1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MTQ0LjBwdDsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCgltc28tYW5z
aS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDps
ZXZlbDUNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0
Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MTgwLjBwdDsNCgltc28tbGV2ZWwtbnVtYmVyLXBv
c2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCgltc28tYW5zaS1mb250LXNpemU6
MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNv
LWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28t
bGV2ZWwtdGFiLXN0b3A6MjE2LjBwdDsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7
DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZv
bnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDcNCgl7bXNvLWxldmVsLW51bWJl
ci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0
b3A6MjUyLjBwdDsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRl
bnQ6LTE4LjBwdDsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5Oldp
bmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVs
bGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6Mjg4LjBwdDsN
Cgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsN
Cgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpA
bGlzdCBsMDpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1s
ZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MzI0LjBwdDsNCgltc28tbGV2ZWwt
bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCgltc28tYW5zaS1m
b250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMQ0KCXtt
c28tbGlzdC1pZDoxNTg0OTk3NDQ1Ow0KCW1zby1saXN0LXRlbXBsYXRlLWlkczoxNzEzNjg4Njg0
O30NCkBsaXN0IGwxOmxldmVsMQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJ
bXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDozNi4wcHQ7DQoJbXNvLWxl
dmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFu
c2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6bGV2
ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpv
Ow0KCW1zby1sZXZlbC10YWItc3RvcDo3Mi4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlv
bjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBw
dDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciOw0KCW1zby1iaWRpLWZvbnQtZmFtaWx5OiJU
aW1lcyBOZXcgUm9tYW4iO30NCkBsaXN0IGwxOmxldmVsMw0KCXttc28tbGV2ZWwtbnVtYmVyLWZv
cm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDox
MDguMHB0Ow0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDot
MTguMHB0Ow0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2Rp
bmdzO30NCkBsaXN0IGwxOmxldmVsNA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7
DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDoxNDQuMHB0Ow0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCW1z
by1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0
IGwxOmxldmVsNQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVs
LXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDoxODAuMHB0Ow0KCW1zby1sZXZlbC1udW1i
ZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCW1zby1hbnNpLWZvbnQt
c2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxOmxldmVsNg0K
CXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0K
CW1zby1sZXZlbC10YWItc3RvcDoyMTYuMHB0Ow0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246
bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7
DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxOmxldmVsNw0KCXttc28tbGV2ZWwt
bnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10
YWItc3RvcDoyNTIuMHB0Ow0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0
LWluZGVudDotMTguMHB0Ow0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1p
bHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxOmxldmVsOA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1h
dDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDoyODgu
MHB0Ow0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTgu
MHB0Ow0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2Rpbmdz
O30NCkBsaXN0IGwxOmxldmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJ
bXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDozMjQuMHB0Ow0KCW1zby1s
ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCW1zby1h
bnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwy
DQoJe21zby1saXN0LWlkOjE3MDQzNTc1MjE7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOjMzNjc1
NTI2MDt9DQpAbGlzdCBsMjpsZXZlbDENCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0
Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MzYuMHB0Ow0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCW1z
by1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwy
OmxldmVsMg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRl
eHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6NzIuMHB0Ow0KCW1zby1sZXZlbC1udW1iZXItcG9z
aXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCW1zby1hbnNpLWZvbnQtc2l6ZTox
MC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCgltc28tYmlkaS1mb250LWZhbWls
eToiVGltZXMgTmV3IFJvbWFuIjt9DQpAbGlzdCBsMjpsZXZlbDMNCgl7bXNvLWxldmVsLW51bWJl
ci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0
b3A6MTA4LjBwdDsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRl
bnQ6LTE4LjBwdDsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5Oldp
bmdkaW5nczt9DQpAbGlzdCBsMjpsZXZlbDQNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVs
bGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MTQ0LjBwdDsN
Cgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsN
Cgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpA
bGlzdCBsMjpsZXZlbDUNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1s
ZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MTgwLjBwdDsNCgltc28tbGV2ZWwt
bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCgltc28tYW5zaS1m
b250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMjpsZXZl
bDYNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+C
pzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MjE2LjBwdDsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0
aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCgltc28tYW5zaS1mb250LXNpemU6MTAu
MHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMjpsZXZlbDcNCgl7bXNvLWxl
dmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2
ZWwtdGFiLXN0b3A6MjUyLjBwdDsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJ
dGV4dC1pbmRlbnQ6LTE4LjBwdDsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQt
ZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMjpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1m
b3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6
Mjg4LjBwdDsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6
LTE4LjBwdDsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5Oldpbmdk
aW5nczt9DQpAbGlzdCBsMjpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0
Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MzI0LjBwdDsNCglt
c28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglt
c28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpvbA0K
CXttYXJnaW4tYm90dG9tOjBjbTt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBjbTt9DQotLT48L3N0
eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRp
dCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5
XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVk
aXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hl
YWQ+DQo8Ym9keSBsYW5nPSJFTi1HQiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2
IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkhpLDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFG
NDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+UlRDUCBwYWNrZXRzIGNhbiBiZSBhc3Nv
Y2lhdGVkIHdpdGggbS0gbGluZXMgaW4gdGhlIHNhbWUgd2F5IGFzIFJUUCBwYWNrZXRzLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+SG93ZXZlciwgTWFnbnVzIHRvbGQg
bWUgaXTigJlzIG5vdCBuZWVkZWQsIHNvIEnigJlkIGxpa2UgdG8gZ2V0IHNvbWUgaW5wdXQgZnJv
bSBoaW0uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5SZWdhcmRzLDxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+Q2hyaXN0ZXI8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YSBuYW1lPSJfTWFpbEVuZENvbXBv
c2UiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVO
LVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2E+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9
ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0
IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWYiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
Ij4gQ3VsbGVuIEplbm5pbmdzIFttYWlsdG86Zmx1ZmZ5QGlpaS5jYV0NCjxicj4NCjxiPlNlbnQ6
PC9iPiAxMyBPY3RvYmVyIDIwMTYgMTg6MDQ8YnI+DQo8Yj5Ubzo8L2I+IENocmlzdGVyIEhvbG1i
ZXJnICZsdDtjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9i
PiBtbXVzaWNAaWV0Zi5vcmc7IE1hZ251cyBXZXN0ZXJsdW5kICZsdDttYWdudXMud2VzdGVybHVu
ZEBlcmljc3Nvbi5jb20mZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbTU1VU0lDXSBSZXZp
ZXcgb2YgZHJhZnQtaWV0Zi1tbXVzaWMtc2RwLWJ1bmRsZS1uZWdvdGlhdGlvbi0zMiAtIFJUUCBk
ZW11eCAtIFB1bGwgUmVxdWVzdDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+VGhhdCBsb29rcyBhYm91dCByaWdodCBmb3IgUlRQIGJ1dCBJIHRoaW5rIGl0
IGlzIHN0aWxsIG1pc3Npbmcgc3R1ZmYgZm9yIFJUQ1AgaGFuZGxpbmcuIEhlcmUgaXMgdGhlIGN1
cnJlbnQgdGV4dCB3ZSBkaWQgZm9yIEpTRVAuIEkgcHJlZmVyIHRoZSBzdHlsZSBpbiB3aGljaCB5
b3UgZGVzY3JpYmVkIGl0IGNvbXBhcmVkIHRvIHRoZSBhbGdvcml0aG0gc3R5bGUgYmVsb3cgYnV0
IEkgdGhpbmsgdGhpcyBtaWdodA0KIGhlbHAgZmlndXJlIG91dCB3aGF0IHRvIHdyaXRlIGZvciBS
VENQLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNh
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzMzMzMzMyI+PGJyPg0KPGJyPg0KPC9zcGFuPjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6IzMzMzMzMyI+PGJyPg0KPGJyPg0KPC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzMzMzMzMyI+V2hlbiBhbiBSVFAgcGFja2V0IGlzIHJlY2VpdmVkIGJ5IGEgdHJhbnNw
b3J0IGFuZCBwYXNzZXMgU1JUUCBhdXRoZW50aWNhdGlvbiwgdGhhdCBwYWNrZXQgbmVlZHMgdG8g
YmUgcm91dGVkIHRvIHRoZSBjb3JyZWN0IFJ0cFJlY2VpdmVyLiBGb3IgZWFjaCB0cmFuc3BvcnQs
DQogdGhlIGZvbGxvd2luZyBzdGVwcyBNVVNUIGJlIGZvbGxvd2VkIHRvIHByZXBhcmUgdG8gcm91
dGUgcGFja2V0czo8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjYuMHB0O21hcmdpbi1yaWdo
dDowY207bWFyZ2luLWJvdHRvbTo2LjBwdDttYXJnaW4tbGVmdDoyNC4wcHQ7dGV4dC1pbmRlbnQ6
LTE4LjBwdDttc28tbGlzdDpsMiBsZXZlbDEgbGZvMTtmb250LXZhcmlhbnQtbGlnYXR1cmVzOiBu
b3JtYWw7b3JwaGFuczogMjt3aWRvd3M6IDIiPg0KPCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6U3ltYm9sO2NvbG9yOiMzMzMzMzMi
PjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPsK3PHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQg
JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjVwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMzMzMzMzIj5Db25zdHJ1Y3QgYSB0YWJsZSBtYXBwaW5nIE1JRCB0byBSdHBSZWNl
aXZlciBmb3IgZWFjaCBSdHBSZWNlaXZlciBjb25maWd1cmVkIHRvIHJlY2VpdmUgZnJvbSB0aGlz
IHRyYW5zcG9ydC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjYuMHB0O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJv
dHRvbTo2LjBwdDttYXJnaW4tbGVmdDoyNC4wcHQ7dGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlz
dDpsMiBsZXZlbDEgbGZvMSI+DQo8IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpTeW1ib2w7Y29sb3I6IzMzMzMzMyI+PHNwYW4gc3R5
bGU9Im1zby1saXN0Oklnbm9yZSI+wrc8c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1l
cyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0K
PC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMz
MzMzMzMiPkNvbnN0cnVjdCBhIHRhYmxlIG1hcHBpbmcgaW5jb21pbmcgU1NSQyB0byBSdHBSZWNl
aXZlciBmb3IgZWFjaCBSdHBSZWNlaXZlciBjb25maWd1cmVkIHRvIHJlY2VpdmUgZnJvbSB0aGlz
IHRyYW5zcG9ydCBhbmQgZm9yIGVhY2ggU1NSQyB0aGF0IFJ0cFJlY2VpdmVyDQogaXMgY29uZmln
dXJlZCB0byByZWNlaXZlLiBTb21lIG9mIHRoZSBTU1JDcyBtYXkgYmUgcHJlc2VudCBpbiB0aGUg
bT0gc2VjdGlvbiBjb3JyZXNwb25kaW5nIHRvIHRoYXQgUnRwUmVjZWl2ZXIgaW4gdGhlIHJlbW90
ZSBkZXNjcmlwdGlvbi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjYuMHB0O21hcmdpbi1yaWdodDowY207bWFyZ2lu
LWJvdHRvbTo2LjBwdDttYXJnaW4tbGVmdDoyNC4wcHQ7dGV4dC1pbmRlbnQ6LTE4LjBwdDttc28t
bGlzdDpsMiBsZXZlbDEgbGZvMSI+DQo8IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpTeW1ib2w7Y29sb3I6IzMzMzMzMyI+PHNwYW4g
c3R5bGU9Im1zby1saXN0Oklnbm9yZSI+wrc8c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtU
aW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
Ow0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OiMzMzMzMzMiPkNvbnN0cnVjdCBhIHRhYmxlIG1hcHBpbmcgb3V0Z29pbmcgU1NSQyB0byBSdHBT
ZW5kZXIgZm9yIGVhY2ggUnRwU2VuZGVyIGNvbmZpZ3VyZWQgdG8gdHJhbnNtaXQgZnJvbSB0aGlz
IHRyYW5zcG9ydCBhbmQgZm9yIGVhY2ggU1NSQyB0aGF0IFJ0cFNlbmRlcg0KIGlzIGNvbmZpZ3Vy
ZWQgdG8gdXNlIHdoZW4gc2VuZGluZy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjYuMHB0O21hcmdpbi1yaWdodDow
Y207bWFyZ2luLWJvdHRvbTo2LjBwdDttYXJnaW4tbGVmdDoyNC4wcHQ7dGV4dC1pbmRlbnQ6LTE4
LjBwdDttc28tbGlzdDpsMiBsZXZlbDEgbGZvMSI+DQo8IVtpZiAhc3VwcG9ydExpc3RzXT48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpTeW1ib2w7Y29sb3I6IzMzMzMz
MyI+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+wrc8c3BhbiBzdHlsZT0iZm9udDo3LjBw
dCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMzMzMzMzMiPkNvbnN0cnVjdCBhIHRhYmxlIG1hcHBpbmcgcGF5bG9hZCB0eXBl
IHRvIFJ0cFJlY2VpdmVyIGZvciBlYWNoIFJ0cFJlY2VpdmVyIGNvbmZpZ3VyZWQgdG8gcmVjZWl2
ZSBmcm9tIHRoaXMgdHJhbnNwb3J0IGFuZCBmb3IgZWFjaCBwYXlsb2FkIHR5cGUgdGhhdA0KIFJ0
cFJlY2VpdmVyIGlzIGNvbmZpZ3VyZWQgdG8gcmVjZWl2ZS4gVGhlIHBheWxvYWQgdHlwZXMgb2Yg
YSBnaXZlbiBSdHBSZWNlaXZlciBhcmUgZm91bmQgaW4gdGhlIG09IHNlY3Rpb24gY29ycmVzcG9u
ZGluZyB0byB0aGF0IFJ0cFJlY2VpdmVyIGluIHRoZSBsb2NhbCBkZXNjcmlwdGlvbi4gSWYgYW55
IHBheWxvYWQgdHlwZSBjb3VsZCBtYXAgdG8gbW9yZSB0aGFuIG9uZSBSdHBSZWNlaXZlciwgbWFw
IHRvIHRoZSBSdHBSZWNlaXZlciB3aG9zZQ0KIG09IHNlY3Rpb24gYXBwZWFycyBlYXJsaWVzdCBp
biB0aGUgbG9jYWwgZGVzY3JpcHRpb24uPG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHls
ZT0ibWFyZ2luLXRvcDo2LjBwdDttYXJnaW4tYm90dG9tOjYuMHB0O2ZvbnQtdmFyaWFudC1saWdh
dHVyZXM6IG5vcm1hbDtvcnBoYW5zOiAyO3dpZG93czogMiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjVwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRp
Y2EmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMzMzMzMzIj5BcyBSdHBUcmFuc2NlaXZlcnMgKGFu
ZCwgdGh1cywgUnRwUmVjZWl2ZXJzKSBhcmUgYWRkZWQsIHJlbW92ZWQsIHN0b3BwZWQsIG9yIHJl
Y29uZmlndXJlZCwgdGhlIHRhYmxlcyBhYm92ZSBtdXN0IGFsc28gYmUgdXBkYXRlZC48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbi10b3A6Ni4wcHQ7bWFy
Z2luLWJvdHRvbTo2LjBwdDtmb250LXZhcmlhbnQtbGlnYXR1cmVzOiBub3JtYWw7b3JwaGFuczog
Mjt3aWRvd3M6IDIiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6IzMzMzMzMyI+Rm9yIGVhY2ggUlRQIHBhY2tldCByZWNlaXZlZCwgdGhlIGZvbGxvd2luZyBz
dGVwcyBNVVNUIGJlIGZvbGxvd2VkIHRvIHJvdXRlIHRoZSBwYWNrZXQ6PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OjYuMHB0O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTo2LjBwdDttYXJnaW4t
bGVmdDoyNC4wcHQ7dGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEgbGZvMjtm
b250LXZhcmlhbnQtbGlnYXR1cmVzOiBub3JtYWw7b3JwaGFuczogMjt3aWRvd3M6IDIiPg0KPCFb
aWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6U3ltYm9sO2NvbG9yOiMzMzMzMzMiPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPsK3
PHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PC9zcGFuPjwh
W2VuZGlmXT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjVwdDtmb250LWZhbWlseTomcXVvdDtI
ZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMzMzMzMzIj5JZiB0aGUgcGFja2V0IGhh
cyBhIE1JRCBhbmQgdGhhdCBNSUQgaXMgbm90IGluIHRoZSB0YWJsZSBtYXBwaW5nIE1JRCB0byBS
dHBSZWNlaXZlciwgZHJvcCB0aGUgcGFja2V0IGFuZCBzdG9wLjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6Ni4wcHQ7
bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjYuMHB0O21hcmdpbi1sZWZ0OjI0LjBwdDt0
ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0OmwwIGxldmVsMSBsZm8yIj4NCjwhW2lmICFzdXBw
b3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OlN5bWJv
bDtjb2xvcjojMzMzMzMzIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj7CtzxzcGFuIHN0
eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNh
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzMzMzMzMyI+SWYgdGhlIHBhY2tldCBoYXMgYSBNSUQg
YW5kIHRoYXQgTUlEIGlzIGluIHRoZSB0YWJsZSBtYXBwaW5nIE1JRCB0byBSdHBSZWNlaXZlciwg
dXBkYXRlIHRoZSBpbmNvbWluZyBTU1JDIG1hcHBpbmcgdGFibGUgdG8gaW5jbHVkZSBhbiBlbnRy
eSB0aGF0IG1hcHMNCiB0aGUgcGFja2V0J3MgU1NSQyB0byB0aGUgUnRwUmVjZWl2ZXIgZm9yIHRo
YXQgTUlELjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6Ni4wcHQ7bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9t
OjYuMHB0O21hcmdpbi1sZWZ0OjI0LjBwdDt0ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0Omww
IGxldmVsMSBsZm8yIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OlN5bWJvbDtjb2xvcjojMzMzMzMzIj48c3BhbiBzdHlsZT0i
bXNvLWxpc3Q6SWdub3JlIj7CtzxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5l
dyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3Nw
YW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS41cHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzMzMzMz
MyI+SWYgdGhlIHBhY2tldCdzIFNTUkMgaXMgaW4gdGhlIGluY29taW5nIFNTUkMgbWFwcGluZyB0
YWJsZSwgZGVsaXZlciB0aGUgcGFja2V0IHRvIHRoZSBhc3NvY2lhdGVkIFJ0cFJlY2VpdmVyIGFu
ZCBzdG9wLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6Ni4wcHQ7bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9t
OjYuMHB0O21hcmdpbi1sZWZ0OjI0LjBwdDt0ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0Omww
IGxldmVsMSBsZm8yIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OlN5bWJvbDtjb2xvcjojMzMzMzMzIj48c3BhbiBzdHlsZT0i
bXNvLWxpc3Q6SWdub3JlIj7CtzxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5l
dyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3Nw
YW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS41cHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzMzMzMz
MyI+SWYgdGhlIHBhY2tldCdzIHBheWxvYWQgdHlwZSBpcyBpbiB0aGUgcGF5bG9hZCB0eXBlIHRh
YmxlLCB1cGRhdGUgdGhlIHRoZSBpbmNvbWluZyBTU1JDIG1hcHBpbmcgdGFibGUgdG8gaW5jbHVk
ZSBhbiBlbnRyeSB0aGF0IG1hcHMgdGhlIHBhY2tldCdzIFNTUkMNCiB0byB0aGUgUnRwUmVjZWl2
ZXIgZm9yIHRoYXQgcGF5bG9hZCB0eXBlLiBJbiBhZGRpdGlvbiwgZGVsaXZlciB0aGUgcGFja2V0
IHRvIHRoZSBhc3NvY2lhdGVkIFJ0cFJlY2VpdmVyIGFuZCBzdG9wLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6Ni4w
cHQ7bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjYuMHB0O21hcmdpbi1sZWZ0OjI0LjBw
dDt0ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0OmwwIGxldmVsMSBsZm8yIj4NCjwhW2lmICFz
dXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OlN5
bWJvbDtjb2xvcjojMzMzMzMzIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj7CtzxzcGFu
IHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRp
Zl0+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0
aWNhJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzMzMzMzMyI+T3RoZXJ3aXNlLCBkcm9wIHRoZSBw
YWNrZXQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0ibWFyZ2luLXRvcDo2LjBw
dDttYXJnaW4tYm90dG9tOjYuMHB0O2ZvbnQtdmFyaWFudC1saWdhdHVyZXM6IG5vcm1hbDtvcnBo
YW5zOiAyO3dpZG93czogMiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjVwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMzMzMzMzIj5Gb3IgZWFjaCBSVENQIHBhY2tldCByZWNlaXZlZCAoaW5jbHVkaW5n
IGVhY2ggUlRDUCBwYWNrZXQgdGhhdCBpcyBwYXJ0IG9mIGEgY29tcG91bmQgUlRDUCBwYWNrZXQp
LCB0aGUgZm9sbG93aW5nIHR5cGUtc3BlY2lmaWMgaGFuZGxpbmcgTVVTVCBiZSBwZXJmb3JtZWQg
dG8NCiByb3V0ZSB0aGUgcGFja2V0OjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDo2LjBwdDttYXJnaW4t
cmlnaHQ6MGNtO21hcmdpbi1ib3R0b206Ni4wcHQ7bWFyZ2luLWxlZnQ6MjQuMHB0O3RleHQtaW5k
ZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDEgbGV2ZWwxIGxmbzM7Zm9udC12YXJpYW50LWxpZ2F0dXJl
czogbm9ybWFsO29ycGhhbnM6IDI7d2lkb3dzOiAyIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNdPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OlN5bWJvbDtjb2xvcjojMzMz
MzMzIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj7CtzxzcGFuIHN0eWxlPSJmb250Ojcu
MHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMt
c2VyaWY7Y29sb3I6IzMzMzMzMyI+SWYgdGhlIHBhY2tldCBpcyBvZiB0eXBlIFNSLCBhbmQgdGhl
IHNlbmRlciBTU1JDIGZvciB0aGUgcGFja2V0IGlzIGZvdW5kIGluIHRoZSBpbmNvbWluZyBTU1JD
IHRhYmxlLCBkZWxpdmVyIGEgY29weSBvZiB0aGUgcGFja2V0IHRvIHRoZSBSdHBSZWNlaXZlcg0K
IGFzc29jaWF0ZWQgd2l0aCB0aGF0IFNTUkMuIEluIGFkZGl0aW9uLCBmb3IgZWFjaCByZXBvcnQg
YmxvY2sgaW4gdGhlIHJlcG9ydCB3aG9zZSBTU1JDIGlzIGZvdW5kIGluIHRoZSBvdXRnb2luZyBT
U1JDIHRhYmxlLCBkZWxpdmVyIGEgY29weSBvZiB0aGUgUlRDUCBwYWNrZXQgdG8gdGhlIFJ0cFNl
bmRlciBhc3NvY2lhdGVkIHdpdGggdGhhdCBTU1JDLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6Ni4wcHQ7bWFyZ2lu
LXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjYuMHB0O21hcmdpbi1sZWZ0OjI0LjBwdDt0ZXh0LWlu
ZGVudDotMTguMHB0O21zby1saXN0OmwxIGxldmVsMSBsZm8zIj4NCjwhW2lmICFzdXBwb3J0TGlz
dHNdPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OlN5bWJvbDtjb2xv
cjojMzMzMzMzIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj7CtzxzcGFuIHN0eWxlPSJm
b250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzMzMzMzMyI+SWYgdGhlIHBhY2tldCBpcyBvZiB0eXBlIFJSLCBm
b3IgZWFjaCByZXBvcnQgYmxvY2sgaW4gdGhlIHBhY2tldCB3aG9zZSBTU1JDIGlzIGZvdW5kIGlu
IHRoZSBvdXRnb2luZyBTU1JDIHRhYmxlLCBkZWxpdmVyIGEgY29weSBvZiB0aGUgUlRDUCBwYWNr
ZXQNCiB0byB0aGUgUnRwU2VuZGVyIGFzc29jaWF0ZWQgd2l0aCB0aGF0IFNTUkMuPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDo2LjBwdDttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0b206Ni4wcHQ7bWFyZ2luLWxl
ZnQ6MjQuMHB0O3RleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDEgbGV2ZWwxIGxmbzMiPg0K
PCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6U3ltYm9sO2NvbG9yOiMzMzMzMzMiPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUi
PsK3PHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4m
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PC9zcGFu
PjwhW2VuZGlmXT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjVwdDtmb250LWZhbWlseTomcXVv
dDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMzMzMzMzIj5JZiB0aGUgcGFja2V0
IGlzIG9mIHR5cGUgU0RFUywgYW5kIHRoZSBzZW5kZXIgU1NSQyBmb3IgdGhlIHBhY2tldCBpcyBm
b3VuZCBpbiB0aGUgaW5jb21pbmcgU1NSQyB0YWJsZSwgZGVsaXZlciB0aGUgcGFja2V0IHRvIHRo
ZSBSdHBSZWNlaXZlciBhc3NvY2lhdGVkDQogd2l0aCB0aGF0IFNTUkMuIEluIGFkZGl0aW9uLCBm
b3IgZWFjaCBjaHVuayBpbiB0aGUgcGFja2V0IHRoYXQgY29udGFpbnMgYSBNSUQgdGhhdCBpcyBp
biB0aGUgdGFibGUgbWFwcGluZyBNSUQgdG8gUnRwUmVjZWl2ZXIsIHVwZGF0ZSB0aGUgaW5jb21p
bmcgU1NSQyBtYXBwaW5nIHRhYmxlIHRvIGluY2x1ZGUgYW4gZW50cnkgdGhhdCBtYXBzIHRoZSBT
U1JDIGZvciB0aGF0IGNodW5rIHRvIHRoZSBSdHBSZWNlaXZlciBhc3NvY2lhdGVkIHdpdGggdGhh
dA0KIE1JRC4gKFRoaXMgY2FzZSBjYW4gb2NjdXIgd2hlbiBSVENQIGZvciBhIHNvdXJjZSBpcyBy
ZWNlaXZlZCBiZWZvcmUgYW55IFJUUCBwYWNrZXRzLik8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjYuMHB0O21hcmdp
bi1yaWdodDowY207bWFyZ2luLWJvdHRvbTo2LjBwdDttYXJnaW4tbGVmdDoyNC4wcHQ7dGV4dC1p
bmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMSBsZXZlbDEgbGZvMyI+DQo8IVtpZiAhc3VwcG9ydExp
c3RzXT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpTeW1ib2w7Y29s
b3I6IzMzMzMzMyI+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+wrc8c3BhbiBzdHlsZT0i
Zm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMzMzMzMzMiPklmIHRoZSBwYWNrZXQgaXMgb2YgdHlwZSBCWUUs
IGZvciBlYWNoIFNTUkMgaW5kaWNhdGVkIGluIHRoZSBwYWNrZXQgdGhhdCBpcyBmb3VuZCBpbiB0
aGUgaW5jb21pbmcgU1NSQyB0YWJsZSwgZGVsaXZlciBhIGNvcHkgb2YgdGhlIHBhY2tldCB0byB0
aGUNCiBSdHBSZWNlaXZlciBhc3NvY2lhdGVkIHdpdGggdGhhdCBTU1JDLjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
Ni4wcHQ7bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjYuMHB0O21hcmdpbi1sZWZ0OjI0
LjBwdDt0ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0OmwxIGxldmVsMSBsZm8zIj4NCjwhW2lm
ICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OlN5bWJvbDtjb2xvcjojMzMzMzMzIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj7Ctzxz
cGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtl
bmRpZl0+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVs
dmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzMzMzMzMyI+SWYgdGhlIHBhY2tldCBpcyBv
ZiB0eXBlIFJUUEZCIG9yIFBTRkIsIGFzIGRlZmluZWQgaW4mbmJzcDs8YSBocmVmPSJodHRwOi8v
cnRjd2ViLXdnLmdpdGh1Yi5pby9qc2VwLyNSRkM0NTg1Ij48c3BhbiBzdHlsZT0iY29sb3I6IzJB
NjQ5Njt0ZXh0LWRlY29yYXRpb246bm9uZSI+W1JGQzQ1ODVdPC9zcGFuPjwvYT4sDQogYW5kIHRo
ZSBtZWRpYSBzb3VyY2UgU1NSQyBmb3IgdGhlIHBhY2tldCBpcyBmb3VuZCBpbiB0aGUgb3V0Z29p
bmcgU1NSQyB0YWJsZSwgZGVsaXZlciB0aGUgcGFja2V0IHRvIHRoZSBSdHBTZW5kZXIgYXNzb2Np
YXRlZCB3aXRoIHRoYXQgU1NSQy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJt
YXJnaW4tdG9wOjYuMHB0O21hcmdpbi1ib3R0b206Ni4wcHQ7Zm9udC12YXJpYW50LWxpZ2F0dXJl
czogbm9ybWFsO29ycGhhbnM6IDI7d2lkb3dzOiAyIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMzMzMzMzMiPkFmdGVyIHBhY2tldHMgYXJlIHJvdXRlZCB0
byB0aGUgUnRwUmVjZWl2ZXIsIGZ1cnRoZXIgcHJvY2Vzc2luZyBvZiB0aGUgUlRQIHBhY2tldHMg
aXMgZG9uZSBhdCB0aGUgUnRwUmVjZWl2ZXIgbGV2ZWwuIFRoaXMgaW5jbHVkZXMgdXNpbmcmbmJz
cDs8YSBocmVmPSJodHRwOi8vcnRjd2ViLXdnLmdpdGh1Yi5pby9qc2VwLyNJLUQuaWV0Zi1tbXVz
aWMtcmlkIj48c3BhbiBzdHlsZT0iY29sb3I6IzJBNjQ5Njt0ZXh0LWRlY29yYXRpb246bm9uZSI+
W0ktRC5pZXRmLW1tdXNpYy1yaWRdPC9zcGFuPjwvYT4mbmJzcDt0bw0KIGRpc3Rpbmd1aXNoIGJl
dHdlZW4gbXVsdGlwbGUgRW5jb2RlZCBTdHJlYW1zLCBhcyB3ZWxsIGFzIGRldGVybWluZSB3aGlj
aCBTb3VyY2UgUlRQIHN0cmVhbSBzaG91bGQgYmUgcmVwYWlyZWQgYnkgYSBnaXZlbiBSZWR1bmRh
bmN5IFJUUCBzdHJlYW0uIElmIHRoZSBSVFAgcGFja2V0J3MgUFQgZG9lcyBub3QgbWF0Y2ggYW55
IGNvZGVjIGluIHVzZSBieSB0aGUgUnRwUmVjZWl2ZXIsIHRoZSBwYWNrZXQgd2lsbCBiZSBkcm9w
cGVkLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luLXRv
cDo2LjBwdDttYXJnaW4tYm90dG9tOjYuMHB0O2ZvbnQtdmFyaWFudC1saWdhdHVyZXM6IG5vcm1h
bDtvcnBoYW5zOiAyO3dpZG93czogMiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjVwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojMzMzMzMzIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luLXRvcDo2LjBwdDttYXJnaW4tYm90dG9tOjYu
MHB0O2ZvbnQtdmFyaWFudC1saWdhdHVyZXM6IG5vcm1hbDtvcnBoYW5zOiAyO3dpZG93czogMiI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjVwdDtmb250
LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMzMzMzMzIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbi10
b3A6Ni4wcHQ7bWFyZ2luLWJvdHRvbTo2LjBwdDtmb250LXZhcmlhbnQtbGlnYXR1cmVzOiBub3Jt
YWw7b3JwaGFuczogMjt3aWRvd3M6IDIiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6IzMzMzMzMyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJv
dHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gT2N0IDEyLCAyMDE2
LCBhdCA0OjM3IEFNLCBDaHJpc3RlciBIb2xtYmVyZyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmNocmlz
dGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSI+Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29t
PC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5IaSw8YnI+DQo8YnI+DQpJxIV2ZSBjcmVhdGVkIGEgcHVsbCByZXF1ZXN0IHdpdGggYWRk
aXRpb25hbCB0ZXh0IHJlZ2FyZGluZyBhc3NvY2lhdGluZzxicj4NClJUUC9SVENQIHBhY2tldHMg
d2l0aCB0aGUgY29ycmVjdCDFgm09xYIgbGluZS48YnI+DQo8YnI+DQo8YSBocmVmPSJodHRwczov
L2dpdGh1Yi5jb20vY2RoNHUvZHJhZnQtc2RwLWJ1bmRsZS9wdWxsLzEwIj5odHRwczovL2dpdGh1
Yi5jb20vY2RoNHUvZHJhZnQtc2RwLWJ1bmRsZS9wdWxsLzEwPC9hPjxicj4NCjxicj4NCjxicj4N
ClJlZ2FyZHMsPGJyPg0KPGJyPg0KQ2hyaXN0ZXI8YnI+DQo8YnI+DQpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCm1tdXNpYyBtYWlsaW5nIGxpc3Q8
YnI+DQo8YSBocmVmPSJtYWlsdG86bW11c2ljQGlldGYub3JnIj5tbXVzaWNAaWV0Zi5vcmc8L2E+
PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVz
aWMiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljPC9hPjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvYm9keT4NCjwv
aHRtbD4NCg==

--_000_7594FB04B1934943A5C02806D1A2204B4BD6861AESESSMB209erics_--


From nobody Thu Oct 13 13:15:05 2016
Return-Path: <fluffy@iii.ca>
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 E38DD129640 for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 13:15:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GThldz4OcJz8 for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 13:15:03 -0700 (PDT)
Received: from smtp98.iad3a.emailsrvr.com (smtp98.iad3a.emailsrvr.com [173.203.187.98]) (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 BD0791295DC for <mmusic@ietf.org>; Thu, 13 Oct 2016 13:15:02 -0700 (PDT)
Received: from smtp13.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp13.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id AC7B3C0532; Thu, 13 Oct 2016 16:14:59 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp13.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 4393DC0415;  Thu, 13 Oct 2016 16:14:59 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.24.127.141] ([UNAVAILABLE]. [128.107.241.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.7); Thu, 13 Oct 2016 16:14:59 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CAD5OKxta5Mk22PEbWcfyFHS5bv5W4dwnLf8bgZ2K-eZ1yqEDzA@mail.gmail.com>
Date: Thu, 13 Oct 2016 14:14:57 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <52B83055-41E7-4095-8B70-23BD2CC79460@iii.ca>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca> <CAD5OKxtHQ6PRszm13vAKdR3VZB1LP5Uffq8YWHTT=_i4P4h+aA@mail.gmail.com> <445CBF55-8999-4F08-9FE4-AC4B88760FB8@iii.ca> <CAD5OKxta5Mk22PEbWcfyFHS5bv5W4dwnLf8bgZ2K-eZ1yqEDzA@mail.gmail.com>
To: Roman Shpount <rshpount@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/HUPHRvuImzgynhWsMtM72MI9cPk>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 20:15:04 -0000

> On Oct 13, 2016, at 11:13 AM, Roman Shpount <rshpount@gmail.com> =
wrote:
>=20
> Cullen,
>=20
> Just to clarify, you want to avoid making SHA-256 a MUST. Why is this =
a problem? I cannot think of a single library that implements DTLS but =
does not implement SHA-256. Can you point me to any 4572 implementations =
that do not support SHA-256?
>=20

note there is an difference between MTI and MTU and lots of TLS things =
implement ciphers that may not be configured for use but to get to your =
questions.=20

Yes.=20

4572 was published in 2006 and there were multiple implementation before =
it was published with some of them (including Cisco's) based on openssl. =
SHA256 was added to be default in openssl in 2010. Cisco's version of =
openssl lags the main branch due to security review and getting it to be =
FIPS approved. There is plenty of 4572 stuff that does not do SHA256.=20

And don't get me wrong, I want to add a RFC that has SHA256 but I do not =
see the point in gratuitously demanding that everything support it. Thus =
my argument for an RFC that adds SHA256 that is merely an extension to =
4572.=20



From nobody Thu Oct 13 13:33:29 2016
Return-Path: <bernard.aboba@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B71E12948D for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 13:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 qAmFXPj8ehXB for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 13:33:25 -0700 (PDT)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (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 E9DA912946B for <mmusic@ietf.org>; Thu, 13 Oct 2016 13:33:24 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id 2so92632042vkb.3 for <mmusic@ietf.org>; Thu, 13 Oct 2016 13:33:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AwlTd5Epw6tlzk5ZfLJun0G4uiAwo65/x7gpv/Shl6Q=; b=flj76eRQHWjxUG0Rwb4yrflo4cXgbOYTLoMGKbZ62nzBHQGdN9BaeZFXJLTXj+Z5Tf /alhIwqm6G6jsNzWlw2dB/BFLCXh9JdVHw11Qxiswx/2Jz+Qv8C1TZfk4U4NmFc+zFDt GqBx15qJbPkcCOZq0cnDi3DeEjOusXCi8AQZfj47lEEYFxojVI6F6obP0X28I95SR2bz iX6pVg3BFv9bjW2iwuuyZysYWHm/07IF6RQwOuMicIf6NCktRLIMXFUVi2HcrRlj2pgX e7/5wSvHnH/j8sgwqM2xEN2TvXl9YQVYTjHHPcfkAm6/Lg2WAbM/k4rPZIcLc22ynJdy EYLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AwlTd5Epw6tlzk5ZfLJun0G4uiAwo65/x7gpv/Shl6Q=; b=Rjx7yGSTNRHcObON6Cs9YgAB1lqMnH8XBVJ5o13N25c7/GUNiUeY16unA2dvdw0J+p hRB5q+OeBbhAjcigpCC4VH/oGfHnqYu/F08lt5ax3wPtfMhrRckS9f8VhTaaxbzR7Rhz Fk17B9f+KTbd90C1BT+uYJTz5mfhW3jg/T0HX49J2HHdcqTEYjFMckKlvv5nnSaajo7U 2kTU/n55yHR37EghtVTUyK3iXfaB4UMYHPFd3th7MZkS61xdNW7sO6XmIMeWtnnyfmMu SQG2leUvglZxodWIGju+QAmQjHi6wufFJGI2gRj06A6nd1C0Y1e2an6viy6M2zGqlHrm PZaQ==
X-Gm-Message-State: AA6/9RmMJirF+XKIn+no31C6NSbKlIY8zuuc54LJLF/NOEyY+Lgr8GdGsJvknYAzrPQ9rbqQ8NaOcFgkeIhniQ==
X-Received: by 10.31.223.1 with SMTP id w1mr6202946vkg.34.1476390803900; Thu, 13 Oct 2016 13:33:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.7.101 with HTTP; Thu, 13 Oct 2016 13:33:03 -0700 (PDT)
In-Reply-To: <52B83055-41E7-4095-8B70-23BD2CC79460@iii.ca>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca> <CAD5OKxtHQ6PRszm13vAKdR3VZB1LP5Uffq8YWHTT=_i4P4h+aA@mail.gmail.com> <445CBF55-8999-4F08-9FE4-AC4B88760FB8@iii.ca> <CAD5OKxta5Mk22PEbWcfyFHS5bv5W4dwnLf8bgZ2K-eZ1yqEDzA@mail.gmail.com> <52B83055-41E7-4095-8B70-23BD2CC79460@iii.ca>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Thu, 13 Oct 2016 13:33:03 -0700
Message-ID: <CAOW+2duEtsj9dhSfNkk44tba25tCGF-gDqToA9jO26qPk=T6Xg@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: multipart/alternative; boundary=94eb2c07ab386a92be053ec50547
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/4GwsU5BrocSCfdam4IOo6Os9qNM>
Cc: Roman Shpount <rshpount@gmail.com>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 20:33:28 -0000

--94eb2c07ab386a92be053ec50547
Content-Type: text/plain; charset=UTF-8

Cullen said:

"And don't get me wrong, I want to add an RFC that has SHA256 but I do not
see the point in gratuitously demanding that everything support it."

[BA] I can see an argument for new implementations being able to verify old
digital signatures and hashes created with SHA-1.  However, the use of
SHA-1 to generate digital signatures is being deprecated, so new
implementations do need to move to alternatives, such as SHA-256.  For
example, here is the NIST policy on hash functions as of August 5, 2015:
http://csrc.nist.gov/groups/ST/hash/policy.html

*SHA-1*: Federal agencies *should* stop using SHA-1 for generating digital
signatures, generating time stamps and for other applications that require
collision resistance. Federal agencies may use SHA-1 for the following
applications: verifying old digital signatures and time stamps, generating
and verifying hash-based message authentication codes (HMACs), key
derivation functions (KDFs), and random bit/number generation. Further
guidance on the use of SHA-1 is provided in SP 800-131A.

*SHA-2 (i.e., SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224 and
SHA-512/256)*: Federal agencies may use these hash functions for all
applications that employ secure hash algorithms. NIST encourages
application and protocol designers to implement SHA-256 at a minimum for
any applications of hash functions requiring interoperability. Further
guidance on the use of SHA-2 is provided in SP 800-57 Part 1, section 5.6.2
and SP 800-131A.

On Thu, Oct 13, 2016 at 1:14 PM, Cullen Jennings <fluffy@iii.ca> wrote:

>
> > On Oct 13, 2016, at 11:13 AM, Roman Shpount <rshpount@gmail.com> wrote:
> >
> > Cullen,
> >
> > Just to clarify, you want to avoid making SHA-256 a MUST. Why is this a
> problem? I cannot think of a single library that implements DTLS but does
> not implement SHA-256. Can you point me to any 4572 implementations that do
> not support SHA-256?
> >
>
> note there is an difference between MTI and MTU and lots of TLS things
> implement ciphers that may not be configured for use but to get to your
> questions.
>
> Yes.
>
> 4572 was published in 2006 and there were multiple implementation before
> it was published with some of them (including Cisco's) based on openssl.
> SHA256 was added to be default in openssl in 2010. Cisco's version of
> openssl lags the main branch due to security review and getting it to be
> FIPS approved. There is plenty of 4572 stuff that does not do SHA256.
>
> And don't get me wrong, I want to add a RFC that has SHA256 but I do not
> see the point in gratuitously demanding that everything support it. Thus my
> argument for an RFC that adds SHA256 that is merely an extension to 4572.
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--94eb2c07ab386a92be053ec50547
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Cullen said:=C2=A0<div><br></div><div>&quot;<span style=3D=
"font-size:12.8px">And don&#39;t get me wrong, I want to add an RFC that ha=
s SHA256 but I do not see the point in gratuitously demanding that everythi=
ng support it.</span>&quot;</div><div><br></div><div>[BA] I can see an argu=
ment for new implementations being able to verify old digital signatures an=
d hashes created with SHA-1.=C2=A0 However, the use of SHA-1 to generate di=
gital signatures is being deprecated, so new implementations do need to mov=
e to alternatives, such as SHA-256.=C2=A0 For example, here is the NIST pol=
icy on hash functions as of August 5, 2015:=C2=A0</div><div><a href=3D"http=
://csrc.nist.gov/groups/ST/hash/policy.html">http://csrc.nist.gov/groups/ST=
/hash/policy.html</a><br></div><div><br></div><div><strong style=3D"font-st=
yle:italic;color:rgb(0,0,0);font-family:arial,helvetica,san-serif">SHA-1</s=
trong><span style=3D"color:rgb(0,0,0);font-family:arial,helvetica,san-serif=
">: Federal agencies=C2=A0</span><strong style=3D"font-style:italic;color:r=
gb(0,0,0);font-family:arial,helvetica,san-serif">should</strong><span style=
=3D"color:rgb(0,0,0);font-family:arial,helvetica,san-serif">=C2=A0stop usin=
g SHA-1 for generating digital signatures, generating time stamps and for o=
ther applications that require collision resistance. Federal agencies may u=
se SHA-1 for the following applications: verifying old digital signatures a=
nd time stamps, generating and verifying hash-based message authentication =
codes (HMACs), key derivation functions (KDFs), and random bit/number gener=
ation. Further guidance on the use of SHA-1 is provided in SP 800-131A.</sp=
an><br></div><div><span style=3D"color:rgb(0,0,0);font-family:arial,helveti=
ca,san-serif"><br></span></div><div><strong style=3D"font-style:italic;colo=
r:rgb(0,0,0);font-family:arial,helvetica,san-serif">SHA-2 (i.e., SHA-224, S=
HA-256, SHA-384, SHA-512, SHA-512/224 and SHA-512/256)</strong><span style=
=3D"color:rgb(0,0,0);font-family:arial,helvetica,san-serif">: Federal agenc=
ies may use these hash functions for all applications that employ secure ha=
sh algorithms. NIST encourages application and protocol designers to implem=
ent SHA-256 at a minimum for any applications of hash functions requiring i=
nteroperability. Further guidance on the use of SHA-2 is provided in SP 800=
-57 Part 1, section 5.6.2 and SP 800-131A.</span><span style=3D"color:rgb(0=
,0,0);font-family:arial,helvetica,san-serif"><br></span></div></div><div cl=
ass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Oct 13, 2016 at =
1:14 PM, Cullen Jennings <span dir=3D"ltr">&lt;<a href=3D"mailto:fluffy@iii=
.ca" target=3D"_blank">fluffy@iii.ca</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><br>
&gt; On Oct 13, 2016, at 11:13 AM, Roman Shpount &lt;<a href=3D"mailto:rshp=
ount@gmail.com">rshpount@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Cullen,<br>
&gt;<br>
&gt; Just to clarify, you want to avoid making SHA-256 a MUST. Why is this =
a problem? I cannot think of a single library that implements DTLS but does=
 not implement SHA-256. Can you point me to any 4572 implementations that d=
o not support SHA-256?<br>
&gt;<br>
<br>
note there is an difference between MTI and MTU and lots of TLS things impl=
ement ciphers that may not be configured for use but to get to your questio=
ns.<br>
<br>
Yes.<br>
<br>
4572 was published in 2006 and there were multiple implementation before it=
 was published with some of them (including Cisco&#39;s) based on openssl. =
SHA256 was added to be default in openssl in 2010. Cisco&#39;s version of o=
penssl lags the main branch due to security review and getting it to be FIP=
S approved. There is plenty of 4572 stuff that does not do SHA256.<br>
<br>
And don&#39;t get me wrong, I want to add a RFC that has SHA256 but I do no=
t see the point in gratuitously demanding that everything support it. Thus =
my argument for an RFC that adds SHA256 that is merely an extension to 4572=
.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div>

--94eb2c07ab386a92be053ec50547--


From nobody Thu Oct 13 15:06:43 2016
Return-Path: <ekr@rtfm.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 58A57129651 for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 15:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MipwKe17Vu5q for <mmusic@ietfa.amsl.com>; Thu, 13 Oct 2016 15:06:39 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (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 BDF7A12956E for <mmusic@ietf.org>; Thu, 13 Oct 2016 15:06:38 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id u124so63726630ywg.3 for <mmusic@ietf.org>; Thu, 13 Oct 2016 15:06:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=i+31B0XKLBh1U/K6KrInouVTeKsKvqzgOPsVfFj6nfo=; b=ARXzeKKfp35loUrtAemy4NKEfjhYATii78jXhj8x3ERxBArG2x4/vuWmHhogaaopH1 kRFnX6+UXYdEDZaXPSZjNM4jdw1u4cRAG8vzGi0pMlUMd6Nn28+Puyf5SKOO+HVIhC2V PGnTTnAa7s3E0Ty90BQzNBnHqMOMMYq90zQhzFMAIDMF2kd2wOJnTRlS7ndkuIxL+ys1 +K7nxE4a0nMVvM7pKYFj90zVdDTANWm2MIRnDaKoxe+bWrNtweEaVGE2JGYZ0TSfbVtq K1ZcSpcdalKkYdjt4MoVqN139eS6151EO2/Pag+vliSOKiw40nj1D5hHKC6asQtmbjQJ 4Qiw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=i+31B0XKLBh1U/K6KrInouVTeKsKvqzgOPsVfFj6nfo=; b=hsZ+usab2KYBn5Oi1Ze5oqYYvV4Un+33lbhvPX04/ium7jpCBvGEYN/f0h633/f2Rg cZwk8/FVfZyesDvgJcm7QyeDeJc7BJKWCy5D3UxDUAUvWrHnuFpZWUSuKhciBjo3ltP7 PGXDxAvBQOUZYo2AgMwuEh3QTwDobdwTG4Lz6KuPLfl/flZbQbhWYgfZhj6BBtTE2EQ5 kxSk4lFixtxJvfoXXYJOh0p8V+/8tTC2S2muI9FfptTAKVF2mEWgsPjPxAsXwTOgkvIL YTYlPiOaIfu0mg0ipJ0NNzvMQgmQZkq6IieOPW5TqyHy/FyLvqxq/pJjta9ROQMQ7Gg2 Szdw==
X-Gm-Message-State: AA6/9RmH14I2aW0Yg4wmfhyw/XbBLd218AtSMa7rX+wBGKtwmaf2/vYvQrDHQtaKANQUYDWB1/0HrG7b2fwslQ==
X-Received: by 10.129.81.21 with SMTP id f21mr7830616ywb.149.1476396397917; Thu, 13 Oct 2016 15:06:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.75.212 with HTTP; Thu, 13 Oct 2016 15:05:57 -0700 (PDT)
In-Reply-To: <CAOW+2duEtsj9dhSfNkk44tba25tCGF-gDqToA9jO26qPk=T6Xg@mail.gmail.com>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <978C3B13-18D7-423B-B7B3-3921461D8650@iii.ca> <CAD5OKxtHQ6PRszm13vAKdR3VZB1LP5Uffq8YWHTT=_i4P4h+aA@mail.gmail.com> <445CBF55-8999-4F08-9FE4-AC4B88760FB8@iii.ca> <CAD5OKxta5Mk22PEbWcfyFHS5bv5W4dwnLf8bgZ2K-eZ1yqEDzA@mail.gmail.com> <52B83055-41E7-4095-8B70-23BD2CC79460@iii.ca> <CAOW+2duEtsj9dhSfNkk44tba25tCGF-gDqToA9jO26qPk=T6Xg@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 13 Oct 2016 15:05:57 -0700
Message-ID: <CABcZeBPKsD06USHKtjbazU0KiFmZwJhQgBEhhQitd6BvM40ryg@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Content-Type: multipart/alternative; boundary=001a11461104d8ae07053ec65204
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/KJJwimfTyU_oEAfw01gw2XiGRXM>
Cc: Roman Shpount <rshpount@gmail.com>, mmusic <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Oct 2016 22:06:41 -0000

--001a11461104d8ae07053ec65204
Content-Type: text/plain; charset=UTF-8

A few notes in no particular order on the technical side:

0. We clearly want to clean up the situation re: multiple fingerprints.
1. I think it's clear we do want to move to SHA-256.
2. It's not clear that the current attacks actually implicate the use of
SHA-1 in this setting. The reason is that those attacks are targeted at
collisions but I believe that to mount a successful attack here you would
need a preimage, though I could be wrong on this point.
3. On the compat side, it seems inevitable that allowing multiple
fingerprints is going to have the effect of breaking any agent which read
4572 as only allowing one. Not sure what we can do about that.

I take the concern Cullen to be raising that "Updates 4572" somehow
retroactively makes implementations which only supported SHA-1 to be
noncompliant?

I'm pretty much indifferent to what appears in this field. The bottom line
is that going forward we would like people to comply with this draft (RFC
XXX) and that people who don't do so are going to have a bad day, no matter
what appears in the Updates field. If it makes people more comfortable not,
I am fine with that. Would "Obsoletes" be better?

-Ekr







On Thu, Oct 13, 2016 at 1:33 PM, Bernard Aboba <bernard.aboba@gmail.com>
wrote:

> Cullen said:
>
> "And don't get me wrong, I want to add an RFC that has SHA256 but I do
> not see the point in gratuitously demanding that everything support it."
>
> [BA] I can see an argument for new implementations being able to verify
> old digital signatures and hashes created with SHA-1.  However, the use of
> SHA-1 to generate digital signatures is being deprecated, so new
> implementations do need to move to alternatives, such as SHA-256.  For
> example, here is the NIST policy on hash functions as of August 5, 2015:
> http://csrc.nist.gov/groups/ST/hash/policy.html
>
> *SHA-1*: Federal agencies *should* stop using SHA-1 for generating
> digital signatures, generating time stamps and for other applications that
> require collision resistance. Federal agencies may use SHA-1 for the
> following applications: verifying old digital signatures and time stamps,
> generating and verifying hash-based message authentication codes (HMACs),
> key derivation functions (KDFs), and random bit/number generation. Further
> guidance on the use of SHA-1 is provided in SP 800-131A.
>
> *SHA-2 (i.e., SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224 and
> SHA-512/256)*: Federal agencies may use these hash functions for all
> applications that employ secure hash algorithms. NIST encourages
> application and protocol designers to implement SHA-256 at a minimum for
> any applications of hash functions requiring interoperability. Further
> guidance on the use of SHA-2 is provided in SP 800-57 Part 1, section 5.6.2
> and SP 800-131A.
>
> On Thu, Oct 13, 2016 at 1:14 PM, Cullen Jennings <fluffy@iii.ca> wrote:
>
>>
>> > On Oct 13, 2016, at 11:13 AM, Roman Shpount <rshpount@gmail.com> wrote:
>> >
>> > Cullen,
>> >
>> > Just to clarify, you want to avoid making SHA-256 a MUST. Why is this a
>> problem? I cannot think of a single library that implements DTLS but does
>> not implement SHA-256. Can you point me to any 4572 implementations that do
>> not support SHA-256?
>> >
>>
>> note there is an difference between MTI and MTU and lots of TLS things
>> implement ciphers that may not be configured for use but to get to your
>> questions.
>>
>> Yes.
>>
>> 4572 was published in 2006 and there were multiple implementation before
>> it was published with some of them (including Cisco's) based on openssl.
>> SHA256 was added to be default in openssl in 2010. Cisco's version of
>> openssl lags the main branch due to security review and getting it to be
>> FIPS approved. There is plenty of 4572 stuff that does not do SHA256.
>>
>> And don't get me wrong, I want to add a RFC that has SHA256 but I do not
>> see the point in gratuitously demanding that everything support it. Thus my
>> argument for an RFC that adds SHA256 that is merely an extension to 4572.
>>
>>
>> _______________________________________________
>> 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
>
>

--001a11461104d8ae07053ec65204
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>A few notes in no particular order on the technical s=
ide:</div><div><br></div><div>0. We clearly want to clean up the situation =
re: multiple fingerprints.</div><div>1. I think it&#39;s clear we do want t=
o move to SHA-256.</div><div>2. It&#39;s not clear that the current attacks=
 actually implicate the use of SHA-1 in this setting. The reason is that th=
ose attacks are targeted at collisions but I believe that to mount a succes=
sful attack here you would need a preimage, though I could be wrong on this=
 point.</div><div>3. On the compat side, it seems inevitable that allowing =
multiple fingerprints is going to have the effect of breaking any agent whi=
ch read 4572 as only allowing one. Not sure what we can do about that.=C2=
=A0</div><div><br></div><div>I take the concern Cullen to be raising that &=
quot;Updates 4572&quot; somehow retroactively makes implementations which o=
nly supported SHA-1 to be noncompliant?</div><div><br></div><div>I&#39;m pr=
etty much indifferent to what appears in this field. The bottom line is tha=
t going forward we would like people to comply with this draft (RFC XXX) an=
d that people who don&#39;t do so are going to have a bad day, no matter wh=
at appears in the Updates field. If it makes people more comfortable not, I=
 am fine with that. Would &quot;Obsoletes&quot; be better?</div><div><br></=
div><div>-Ekr</div><div><br></div><div><br></div><div><br></div><div><br></=
div><div><br></div><div><br></div></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">On Thu, Oct 13, 2016 at 1:33 PM, Bernard Aboba <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:bernard.aboba@gmail.com" target=3D"_blan=
k">bernard.aboba@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div dir=3D"ltr">Cullen said:=C2=A0<div><br></div><div>&quot;<span =
style=3D"font-size:12.8px">And don&#39;t get me wrong, I want to add an RFC=
 that has SHA256 but I do not see the point in gratuitously demanding that =
everything support it.</span>&quot;</div><div><br></div><div>[BA] I can see=
 an argument for new implementations being able to verify old digital signa=
tures and hashes created with SHA-1.=C2=A0 However, the use of SHA-1 to gen=
erate digital signatures is being deprecated, so new implementations do nee=
d to move to alternatives, such as SHA-256.=C2=A0 For example, here is the =
NIST policy on hash functions as of August 5, 2015:=C2=A0</div><div><a href=
=3D"http://csrc.nist.gov/groups/ST/hash/policy.html" target=3D"_blank">http=
://csrc.nist.gov/groups/<wbr>ST/hash/policy.html</a><br></div><div><br></di=
v><div><strong style=3D"font-style:italic;color:rgb(0,0,0);font-family:aria=
l,helvetica,san-serif">SHA-1</strong><span style=3D"color:rgb(0,0,0);font-f=
amily:arial,helvetica,san-serif">: Federal agencies=C2=A0</span><strong sty=
le=3D"font-style:italic;color:rgb(0,0,0);font-family:arial,helvetica,san-se=
rif">should</strong><span style=3D"color:rgb(0,0,0);font-family:arial,helve=
tica,san-serif">=C2=A0stop using SHA-1 for generating digital signatures, g=
enerating time stamps and for other applications that require collision res=
istance. Federal agencies may use SHA-1 for the following applications: ver=
ifying old digital signatures and time stamps, generating and verifying has=
h-based message authentication codes (HMACs), key derivation functions (KDF=
s), and random bit/number generation. Further guidance on the use of SHA-1 =
is provided in SP 800-131A.</span><br></div><div><span style=3D"color:rgb(0=
,0,0);font-family:arial,helvetica,san-serif"><br></span></div><div><strong =
style=3D"font-style:italic;color:rgb(0,0,0);font-family:arial,helvetica,san=
-serif">SHA-2 (i.e., SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224 and SH=
A-512/256)</strong><span style=3D"color:rgb(0,0,0);font-family:arial,helvet=
ica,san-serif">: Federal agencies may use these hash functions for all appl=
ications that employ secure hash algorithms. NIST encourages application an=
d protocol designers to implement SHA-256 at a minimum for any applications=
 of hash functions requiring interoperability. Further guidance on the use =
of SHA-2 is provided in SP 800-57 Part 1, section 5.6.2 and SP 800-131A.</s=
pan><span style=3D"color:rgb(0,0,0);font-family:arial,helvetica,san-serif">=
<br></span></div></div><div class=3D"HOEnZb"><div class=3D"h5"><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Oct 13, 2016 at 1:1=
4 PM, Cullen Jennings <span dir=3D"ltr">&lt;<a href=3D"mailto:fluffy@iii.ca=
" target=3D"_blank">fluffy@iii.ca</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><br>
&gt; On Oct 13, 2016, at 11:13 AM, Roman Shpount &lt;<a href=3D"mailto:rshp=
ount@gmail.com" target=3D"_blank">rshpount@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Cullen,<br>
&gt;<br>
&gt; Just to clarify, you want to avoid making SHA-256 a MUST. Why is this =
a problem? I cannot think of a single library that implements DTLS but does=
 not implement SHA-256. Can you point me to any 4572 implementations that d=
o not support SHA-256?<br>
&gt;<br>
<br>
note there is an difference between MTI and MTU and lots of TLS things impl=
ement ciphers that may not be configured for use but to get to your questio=
ns.<br>
<br>
Yes.<br>
<br>
4572 was published in 2006 and there were multiple implementation before it=
 was published with some of them (including Cisco&#39;s) based on openssl. =
SHA256 was added to be default in openssl in 2010. Cisco&#39;s version of o=
penssl lags the main branch due to security review and getting it to be FIP=
S approved. There is plenty of 4572 stuff that does not do SHA256.<br>
<br>
And don&#39;t get me wrong, I want to add a RFC that has SHA256 but I do no=
t see the point in gratuitously demanding that everything support it. Thus =
my argument for an RFC that adds SHA256 that is merely an extension to 4572=
.<br>
<div class=3D"m_7639219063908107102HOEnZb"><div class=3D"m_7639219063908107=
102h5"><br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
<br></blockquote></div><br></div>

--001a11461104d8ae07053ec65204--


From nobody Fri Oct 14 00:55:25 2016
Return-Path: <magnus.westerlund@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 71C7D1295E6 for <mmusic@ietfa.amsl.com>; Fri, 14 Oct 2016 00:55:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 RXtOUomcG6CI for <mmusic@ietfa.amsl.com>; Fri, 14 Oct 2016 00:55:22 -0700 (PDT)
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 23EA112940C for <mmusic@ietf.org>; Fri, 14 Oct 2016 00:55:21 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-b5-58008f687aff
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by  (Symantec Mail Security) with SMTP id 77.84.02551.86F80085; Fri, 14 Oct 2016 09:55:20 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.50) with Microsoft SMTP Server id 14.3.319.2; Fri, 14 Oct 2016 09:54:18 +0200
To: Christer Holmberg <christer.holmberg@ericsson.com>, Cullen Jennings <fluffy@iii.ca>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com>
Date: Fri, 14 Oct 2016 09:54:15 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM2K7gW5GP0OEwb9OZYsP638wWkxd/pjF gcljyZKfTB6Xz39kDGCK4rJJSc3JLEst0rdL4MqYdWUVY8EcuYonM8+wNDBulOhi5OSQEDCR OPm1iw3EFhJYzyhx/KJQFyMXkL2cUaKl4RMjSEJYIEOi5WUXmC0iEClx5ewpZogioIZ7i9ex dzFycDALqEtcXRwEUsMmYCFx80cj2FBeAXuJva8usILYLAKqEjOXzmEHsUUFYiSuP3sEVSMo cXLmExaQMZwCfhIvnkSChJmBxsycf54RwpaXaN46mxniTm2JhqYO1gmMArOQdM9C0jILScsC RuZVjKLFqcXFuelGxnqpRZnJxcX5eXp5qSWbGIFBeXDLb90djKtfOx5iFOBgVOLhXXD6f7gQ a2JZcWXuIUYJDmYlEV7uPoYIId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rxmK++HCwmkJ5akZqem FqQWwWSZODilGhhrgufs+8R7TVI4auftKd8DPtw7o2Ut9HWmsejqI/Mn3318c/rciMU7NfRf ro36Yfbr6pfSNo++NTdOB8xPet+49/jiF9e+Hyrc/yqqnV3qxbdfjyU5khn3iyzQWLJlk7b6 feGXh1e5ZUsxVHGsEkzNvjvZM3I93/YjG2qLJBofCG87H3F07smTD5RYijMSDbWYi4oTAdEc A/pGAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/N1ZCDjwBzqIL9a51LKLRfsprTcw>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 14 Oct 2016 07:55:24 -0000

Den 2016-10-13 kl. 18:01, skrev Christer Holmberg:
> However, Magnus told me itâ€™s not needed, so Iâ€™d like to get some input
> from him.
>
> *From:*Cullen Jennings [mailto:fluffy@iii.ca]
> That looks about right for RTP but I think it is still missing stuff for
> RTCP handling. Here is the current text we did for JSEP. I prefer the
> style in which you described it compared to the algorithm style below
> but I think this might help figure out what to write for RTCP.
>

I dislike the algorithmic description JSEP has because it inserts itself 
at position in the stack where I would not myself implement the binding 
handling. The implementations of RTP stacks I have made have never let 
the full RTCP packets be available to the application layer. It has only 
implemented event and request based interface to provide the triggers 
and data associated with the differnet RTCP packets. Thus, from my 
perspective the routing of the RTCP packets becomes a question if the 
SSRC is bound to the right m=. Then handel the received RTCP packets in 
that context.

So what might be a suitable RTCP clarification regarding RTCP would be 
the following.

Simply add RTCP in the following sentence:

"Later, when an offerer or answerer receives an RTP packet that does not 
carry the identification-tag, it can associate the packet with the
correct "m=" line using the SSRC value."

so that it reads:

"Later, when an offerer or answerer receives an RTP or RTCP packet that 
does not carry the identification-tag, it can associate the packet with 
the correct "m=" line using the SSRC value."

Regarding the second paragraph. If the association has been done 
according to this part then also the RTCP packets has an association. If 
an RTCP packet arrives with a non associated SSRC, then many RTCP 
packets type can still be processed and the information stored in the 
SSRC related information table. Some that are application interaction 
related, like some of the feedback messages can of course not be handled.

One very important aspect here is that the basic RTCP processing do need 
to occur for also non-associated SSRCs. This to ensure that the sender 
get the RTCP feedback information for congestion control purposes. We 
want the transport layer functions to continue function, even if the 
application can't consume the packets.

Thus, I would consider that the "the packet SHOULD be dropped." needs an 
addition that says after having been processed as received by the RTCP 
layer. If we don't report them as received we skew the congestion 
control information, and it will make any coupled congestion controller 
that looks at the set of RTP streams being emitted take the wrong 
decision. I also assumes that a lack of association is in most cases a 
temporary issue that will be resolved by the regular transmissions.

A long term lack of association is from my perspective indicates an 
error on the signalling plane, so that a renegotation is needed. I do 
see the downside that the sending sides RTP/RTCP stack is lacking the 
information that the packet is being dropped after reception. This could 
be solved if one implemented the RTCP XR packet type Discard Count 
Metric Reporting (https://datatracker.ietf.org/doc/rfc7002/).
I would use the 01 "Packet to early" for this case.


Cheers


Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Fri Oct 14 12:13:07 2016
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 ECBC9129898 for <mmusic@ietfa.amsl.com>; Fri, 14 Oct 2016 12:13:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.197
X-Spam-Level: 
X-Spam-Status: No, score=-7.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.996, 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 fUoYhEMs0usy for <mmusic@ietfa.amsl.com>; Fri, 14 Oct 2016 12:13:05 -0700 (PDT)
Received: from alum-mailsec-scanner-2.mit.edu (alum-mailsec-scanner-2.mit.edu [18.7.68.13]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8D312961B for <mmusic@ietf.org>; Fri, 14 Oct 2016 12:13:05 -0700 (PDT)
X-AuditID: 1207440d-4c5ff700000009a7-8e-58012e3fab61
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id 04.43.02471.F3E21085; Fri, 14 Oct 2016 15:13:03 -0400 (EDT)
Received: from [192.168.1.110] (c-73-186-127-100.hsd1.ma.comcast.net [73.186.127.100]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id u9EJD258026314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Fri, 14 Oct 2016 15:13:03 -0400
To: mmusic@ietf.org
References: <19028e81-8f2e-090f-7cdf-5d942382d393@cisco.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <f39c7bad-4c2a-f400-4b5c-2828bc143a17@alum.mit.edu>
Date: Fri, 14 Oct 2016 15:13:02 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <19028e81-8f2e-090f-7cdf-5d942382d393@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNIsWRmVeSWpSXmKPExsUixO6iqGuvxxhh8G+FhcXU5Y9ZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVced2B2PBQ7OK3g9vWBsY72p2MXJySAiYSHR1LWPuYuTiEBK4 zCix+W4TI4Tzlknice8JNpAqYQFriSM/FoPZIgLCEjPe/gWzhQRsJLbs+MkKYrMJaEnMOfSf BcTmFbCX2PLsMiOIzSKgKvH4wDUwW1QgTWL7ut3MEDWCEidnPgGr5xSwlbi8+gxYnBnIvjN3 N5QtL7H97RzmCYx8s5C0zEJSNgtJ2QJG5lWMcok5pbm6uYmZOcWpybrFyYl5ealFukZ6uZkl eqkppZsYIWHGu4Px/zqZQ4wCHIxKPLwzPjBECLEmlhVX5h5ilORgUhLltfkKFOJLyk+pzEgs zogvKs1JLT7EKMHBrCTC6yHGGCHEm5JYWZValA+TkuZgURLnVVui7ickkJ5YkpqdmlqQWgST leHgUJLgbZUEahQsSk1PrUjLzClBSDNxcIIM5wEavgCkhre4IDG3ODMdIn+KUVFKnFcXJCEA ksgozYPrhaWBV4ziQK8I8x4GqeIBphC47ldAg5mABn9oYwAZXJKIkJJqYGybzSuu+MiTI2bS h60PTk9UX6hdYvlGe6mTVzZ7n5Dm8rnHLRQqWszFnPWs2+uyHx/hz+S7cbj7oqTirEtXdp5u XOtVYN921+Vf3sV5a9w/XKx71SimI36aV21hzcXU1dnrg5tf3zXfWRMiwbDD6Z1l4WVPvikc c9av2Snib3v8dsDE0JVPpJRYijMSDbWYi4oTAcUP3wfeAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/PPIgeGtI4xG58NmrS2GLWuhGGjc>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 14 Oct 2016 19:13:07 -0000

I tried to do a reasonably thorough review of this document. I did find 
a bunch of stuff that needs some work. Most of it is editorial.

* Section 1:

The following is present twice:

    The Stream Control Transmission Protocol (SCTP) [RFC4960] is a
    transport protocol used to establish associations between two
    endpoints.

I don't understand the point of including the following:

    NOTE: TLS is designed to run on top of a byte-stream oriented
    transport protocol providing a reliable, in-sequence delivery like
    TCP.  [RFC6083] presents serious limitations with transporting TLS on
    top of SCTP.  Therefore, defining a mechanism to negotiate media
    streams transported using TLS on top of SCTP, i.e., 'SCTP/TLS', is
    outside the scope of this specification.  In addition, defining a
    mechanism to negotiate non-protected SCTP associations is also
    outside the scope of this specification.

This document doesn't discuss running *anything* in particular over 
SCTP, so why single out TLS over SCTP? There is something similar that 
would make sense to mention: that running SCTP over TCP presents serious 
limitation, since it forces ordering and reliability even on SCTP 
streams that don't want that. So it would be good to mention that 
TCP/DTLS/SCTP is only intended as a fallback for use in situations where 
UDP is blocked.

OTOH, the following sentence:

                                              In addition, defining a
    mechanism to negotiate non-protected SCTP associations is also
    outside the scope of this specification.

Is worth saying, though it needs rewording after removing the rest.

* Section 4.3:

    NOTE: A mechanism on how to describe, and manage, individual SCTP
    streams within an SCTP association, is outside the scope of this
    specification.

I think it would be helpful to make an informational reference to 
draft-ietf-mmusic-data-channel-sdpneg, since that is well along toward 
completion.

* Section 4.4:

IMO it is very unwise to restate the syntax of the m- line here. That is 
defined in 4566/4566bis, and this doesn't change that.

Instead, I think this section should restrict itself to defining the 
values that may be used for the fields <media> <port> <proto> <fmt> 
defined in 4566. In particular:

<media>: "application"

<proto>: "UDP/DTLS/SCTP" or "TCP/DTLS/SCTP"

<port>: UDP port number (for "UDP/DTLS/SCTP"), or
         TCP port number (for ""UDP/DTLS/SCTP")

<fmt>: a string denoting the association-usage, limited to the syntax
        of a 'token' as defined in RFC4566.

* Section 5.2:

Rather than restate the general syntax of an attribute, please just 
define the parts that are unique to this attribute, in the style 
introduced in RFC4566bis. E.g.,

    Name: sctp-port

    Value: sctp-port-value

    Usage Level: media

    Charset Dependent: no

    Mux Category: SPECIAL

    Syntax:

          sctp-port-value = 1*5<DIGIT defined in RFC4566>

          The SCTP port range is between 0 and 65535 (both included).
          Leading zeroes MUST NOT be used.

    Example:

          a=sctp-port:5000

* Section 5.3:

The qualification in the first paragraph is now redundant since the 
draft is now so qualified.

* Section 6.2:

Rather than restate the general syntax of an attribute, please just 
define the parts that are unique to this attribute, in the style 
introduced in RFC4566bis. E.g.,

    Name: max-message-size

    Value: max-message-size-value

    Usage Level: media

    Charset Dependent: no

    Mux Category: SPECIAL

    Syntax:

          max-message-size-value = 1*40<DIGIT defined in RFC4566>
          *** Did you really want *40* here? ***

          Leading zeroes MUST NOT be used.

    Example:

          a=max-message-size:100000

* Section 6.3:

See comments on 5.3.

* Section 9.1:

The following is redundant and can be removed: "In case of UDP/DTLS/SCTP 
and TCP/DTLS/SCTP".

Using "association/connection" invites confusion. Does the "/" mean OR?

I suggest:

    The SCTP association, DTLS association and TCP connection are
    managed independently of each other.  Each can be re-established
    without impacting others.

* Section 9.2:

I suggest s/discarded/ignored/

* Section 9.3:

After reading this I remain confused about what triggers 
re-establishment. I *think* it is intended that this only be triggered 
by an O/A where one side or the other has changed the port value. I'd 
like to see this stated more explicitly.

The following:

    As both SCTP endpoints take the 'active' role, this specification
    does not define usage of the SDP 'setup' attribute [RFC4145] for
    SCTP.

may be confusing because 'setup' is used for the m-line. I suggest:

    As both SCTP endpoints take the 'active' role, the SDP 'setup'
    attribute [RFC4145] does not apply to SCTP association
    establishment. However the 'setup' attribute does apply to
    establishment of underlying DTLS associations and TCP connections.
    (See below.)

A similar change is appropriate for the 'connection' attribute.

The text "NOTE: In case of SCTP-over-DTLS" is redundant and can be removed.

The following wording is confusing (it seems circular):

    When such SCTP association is re-established the
    SCTP endpoints MUST use the procedures in this section for
    establishing an SCTP association.

I think this would be better stated:

    The procedures in this section MUST be followed to re-establish the
    SCTP association. This requires a new offer/answer exchange.

* Section 10.2:

Some offerers may not be capable of using 'actpass' because they aren't 
able to receive incoming connection requests. While this might be 
resolved by using STUN or TURN I don't think this draft should assume 
that those are required. I see no particular reason to prevent use of 
"active" or "passive", though it might be good to encourage use of 
"actpass" when possible.

* Section 10.3:

    Once the answerer has sent the answer the answerer MUST, if an SCTP
    association has yet not been established, or if an existing SCTP
    association is to be re-established, initiate the establishment of
    the SCTP association.

    The answerer follows the procedures in [I-D.ietf-mmusic-dtls-sdp]
    regarding the establishment/re-establishment of the DTLS association.

    In the case of TCP/DTLS/SCTP, the answerer follows the procedures in
    [RFC4145] regarding the establishment/re-establishment of the TCP
    connection association.

I think the order of presentation here is backward. It needs to be 
carried out bottom to top, so I propose the order of these paragraphs be 
flipped. (Some wording tweaks will also be required to handle the 
transitions properly.)

* Section 10.4:

Again the ordering seems wrong.

	Thanks,
	Paul


From nobody Sat Oct 15 14:18:41 2016
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 F34DA129488 for <mmusic@ietfa.amsl.com>; Sat, 15 Oct 2016 14:18:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 owLIgC7k_KGb for <mmusic@ietfa.amsl.com>; Sat, 15 Oct 2016 14:18:38 -0700 (PDT)
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 17F3F1293DF for <mmusic@ietf.org>; Sat, 15 Oct 2016 14:18:37 -0700 (PDT)
X-AuditID: c1b4fb2d-1c7ff700000009f7-c0-58029d2aef47
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by  (Symantec Mail Security) with SMTP id C7.88.02551.A2D92085; Sat, 15 Oct 2016 23:18:36 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0319.002; Sat, 15 Oct 2016 23:18:34 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Paul's review
Thread-Index: AdImVRUqaKFns7OmSde3fBN3KRdtxQ==
Date: Sat, 15 Oct 2016 21:18:33 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD93F95@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBLMWRmVeSWpSXmKPExsUyM2K7t67OXKYIg6nvWCymLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugStj0aK/rAWn7CumXj7M3sB4zqCLkZNDQsBE 4s+XM8xdjFwcQgLrGSW+LO1mgnAWM0ps7brL0sXIwcEmYCHR/U8bpEFEwFfi2ePbbCC2sIC3 xJHrBxkh4j4Sx+csYYWw9SRuLF3PBGKzCKhKzP58jgXE5gXqPfRsF1icUUBM4vupNWA2s4C4 xK0n85kgDhKQWLLnPDOELSrx8vE/VghbSWLR7c9Q9ToSC3Z/YoOwtSWWLXzNDDFfUOLkzCcs ExiFZiEZOwtJyywkLbOQtCxgZFnFKFqcWlycm25krJdalJlcXJyfp5eXWrKJERjeB7f81t3B uPq14yFGAQ5GJR5eBVnGCCHWxLLiytxDjBIczEoivJYzmCKEeFMSK6tSi/Lji0pzUosPMUpz sCiJ85qtvB8uJJCeWJKanZpakFoEk2Xi4JRqYGQ0WS+59vS+dfG12n2yHQ1bHPPeLl+Xt01W vmG/cIbfi4f9ybs0p9VWCf/z3a2htLvOz+m+f/t38+++f9JVPsn0z3T/E+BsHtvx7NRjJb75 7/vO/jumtyXli9mNXtbLZg8/TFA4OHW16uuWmvQnVWevhEvNnRF39bc9n/E3qVWNKzvml87M MlRiKc5INNRiLipOBABKMne6awIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/iZ9aKXR62dt7yhjbhkvQt7I3DRo>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Paul's review
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Oct 2016 21:18:40 -0000

Hi Paul,

Thanks for your review! Please see inline.

* Section 1:

> The following is present twice:
>
>    The Stream Control Transmission Protocol (SCTP) [RFC4960] is a
>    transport protocol used to establish associations between two
>    endpoints.
>
> I don't understand the point of including the following:
>
>    NOTE: TLS is designed to run on top of a byte-stream oriented
>    transport protocol providing a reliable, in-sequence delivery like
>    TCP.  [RFC6083] presents serious limitations with transporting TLS on
>    top of SCTP.  Therefore, defining a mechanism to negotiate media
>    streams transported using TLS on top of SCTP, i.e., 'SCTP/TLS', is
>    outside the scope of this specification.  In addition, defining a
>    mechanism to negotiate non-protected SCTP associations is also
>    outside the scope of this specification.
>
> This document doesn't discuss running *anything* in particular over SCTP,=
 so why single out TLS over SCTP?=20

The text seems to be a leftover from when the draft defined the O/A procedu=
res DTLS-over-SCTP. I will remove it (except for the last sentence - see mo=
re below).

> There is something similar that would make sense to mention: that running=
 SCTP over TCP presents serious limitation, since
> it forces ordering and reliability even on SCTP streams that don't want t=
hat. So it would be good to mention that TCP/DTLS/SCTP=20
> is only intended as a fallback for use in situations where UDP is blocked=
.

I'll think of some text.

>OTOH, the following sentence:
>
>  In addition, defining a mechanism to negotiate non-protected SCTP associ=
ations is also
>    outside the scope of this specification.
>
> Is worth saying, though it needs rewording after removing the rest.

I'll think of something.

------

* Section 4.3:

>    NOTE: A mechanism on how to describe, and manage, individual SCTP
>    streams within an SCTP association, is outside the scope of this
>    specification.
>
> I think it would be helpful to make an informational reference to draft-i=
etf-mmusic-data-channel-sdpneg, since that is well along toward completion.

I can do that.

------

* Section 4.4:

> IMO it is very unwise to restate the syntax of the m- line here. That is =
defined in 4566/4566bis, and this doesn't change that.
>
> Instead, I think this section should restrict itself to defining the valu=
es that may be used for the fields <media> <port> <proto> <fmt> defined in =
4566. In particular:
>
> <media>: "application"
>
> <proto>: "UDP/DTLS/SCTP" or "TCP/DTLS/SCTP"
>
> <port>: UDP port number (for "UDP/DTLS/SCTP"), or
>         TCP port number (for ""UDP/DTLS/SCTP")
>
> <fmt>: a string denoting the association-usage, limited to the syntax
>       of a 'token' as defined in RFC4566.

Will do as suggested.

------

* Section 5.2:

> Rather than restate the general syntax of an attribute, please just defin=
e the parts that are unique to this attribute, in the style introduced in R=
FC4566bis. E.g.,
>
>    Name: sctp-port
>
>    Value: sctp-port-value
>
>    Usage Level: media
>
>    Charset Dependent: no
>
>    Mux Category: SPECIAL
>
>    Syntax:
>
>          sctp-port-value =3D 1*5<DIGIT defined in RFC4566>
>
>          The SCTP port range is between 0 and 65535 (both included).
>          Leading zeroes MUST NOT be used.
>
>    Example:
>
>          a=3Dsctp-port:5000

Will do as suggested.

------

* Section 5.3:

> The qualification in the first paragraph is now redundant since the draft=
 is now so qualified.

Just to verify that I understood the comment,  are you saying the first par=
agraph can be removed?

------

* Section 6.2:

> Rather than restate the general syntax of an attribute, please just defin=
e the parts that are unique to this attribute, in the style introduced in R=
FC4566bis. E.g.,
>
>    Name: max-message-size
>
>    Value: max-message-size-value
>
>    Usage Level: media
>
>    Charset Dependent: no
>
>    Mux Category: SPECIAL
>
>    Syntax:
>
>          max-message-size-value =3D 1*40<DIGIT defined in RFC4566>
>          *** Did you really want *40* here? ***

I don't remember where the number came from.

Any suggestion would be a reasonable number? Do we need to set a limit? As =
far as I remember, the standard does not define a max size.

>          Leading zeroes MUST NOT be used.
>
>    Example:
>
>          a=3Dmax-message-size:100000

Will do as suggested.

------

* Section 6.3:

> See comments on 5.3.

See reply above.

------

* Section 9.1:

> The following is redundant and can be removed: "In case of UDP/DTLS/SCTP =
and TCP/DTLS/SCTP".

Correct. I will remove it.

> Using "association/connection" invites confusion. Does the "/" mean OR?
>
> I suggest:
>
>    The SCTP association, DTLS association and TCP connection are
>    managed independently of each other.  Each can be re-established
>    without impacting others.

Looks good. I'll change as suggested.

------

* Section 9.2:

> I suggest s/discarded/ignored/

I'll change as suggested.

------

* Section 9.3:

> After reading this I remain confused about what triggers re-establishment=
. I *think* it is intended that this only be triggered=20
> by an O/A where one side or the other has changed the port value. I'd lik=
e to see this stated more explicitly.

I'll take a look.

> The following:
>
>    As both SCTP endpoints take the 'active' role, this specification
>    does not define usage of the SDP 'setup' attribute [RFC4145] for
>    SCTP.
>
> may be confusing because 'setup' is used for the m-line. I suggest:
>
>    As both SCTP endpoints take the 'active' role, the SDP 'setup'
>    attribute [RFC4145] does not apply to SCTP association
>    establishment. However the 'setup' attribute does apply to
>    establishment of underlying DTLS associations and TCP connections.
>    (See below.)
>
> A similar change is appropriate for the 'connection' attribute.

I'll think of some text.

> The text "NOTE: In case of SCTP-over-DTLS" is redundant and can be remove=
d.

Ok.

> The following wording is confusing (it seems circular):
>
>    When such SCTP association is re-established the
>    SCTP endpoints MUST use the procedures in this section for
>    establishing an SCTP association.
>
> I think this would be better stated:
>
>    The procedures in this section MUST be followed to re-establish the
>    SCTP association. This requires a new offer/answer exchange.

Ok.

------

* Section 10.2:

> Some offerers may not be capable of using 'actpass' because they aren't a=
ble to receive incoming connection=20
> requests. While this might be resolved by using STUN or TURN I don't thin=
k this draft should assume that those=20
> are required. I see no particular reason to prevent use of "active" or "p=
assive", though it might be good to encourage=20
> use of "actpass" when possible.

I agree. I'll change as suggested.=20

------

* Section 10.3:

>    Once the answerer has sent the answer the answerer MUST, if an SCTP
>    association has yet not been established, or if an existing SCTP
>    association is to be re-established, initiate the establishment of
>    the SCTP association.
>
>    The answerer follows the procedures in [I-D.ietf-mmusic-dtls-sdp]
>    regarding the establishment/re-establishment of the DTLS association.
>
>    In the case of TCP/DTLS/SCTP, the answerer follows the procedures in
>    [RFC4145] regarding the establishment/re-establishment of the TCP
>    connection association.
>
> I think the order of presentation here is backward. It needs to be carrie=
d out bottom=20
> to top, so I propose the order of these paragraphs be flipped. (Some word=
ing tweaks=20
> will also be required to handle the transitions properly.)

I'll look at it.

------

* Section 10.4:

>Again the ordering seems wrong.

I'll look at it.

------

Thanks!

Regards,

Christer


From nobody Sun Oct 16 06:56:07 2016
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 A5AE2129497 for <mmusic@ietfa.amsl.com>; Sun, 16 Oct 2016 06:56:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 f_k_8WwaNONx for <mmusic@ietfa.amsl.com>; Sun, 16 Oct 2016 06:56:03 -0700 (PDT)
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 86029127A91 for <mmusic@ietf.org>; Sun, 16 Oct 2016 06:56:02 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-79-580386f05fef
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by  (Symantec Mail Security) with SMTP id BF.76.02458.0F683085; Sun, 16 Oct 2016 15:56:01 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0319.002; Sun, 16 Oct 2016 15:56:00 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Paul's review
Thread-Index: AdImVRUqaKFns7OmSde3fBN3KRdtxQBX9o1g
Date: Sun, 16 Oct 2016 13:55:59 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BD98642@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B4BD93F95@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD93F95@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDLMWRmVeSWpSXmKPExsUyM2J7uO7HNuYIg+ZNbBZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJWxfu8yxoL1LhXzti5ma2B8YNLFyMkhIWAi cef6JyYQW0hgPaPEhy8REPZiRolnawK7GDk42AQsJLr/aXcxcnGICDQzSlw7v5wFpEZYwFvi yPWDjCC2iICPxPE5S1hB6kUEjCRa73uBhFkEVCXuP77CCmLzCvhKfHi0mxGkRAjIvroiGcTk FPCT2NFXBlLBKCAm8f3UGrBjmAXEJW49mc8EcaSAxJI955khbFGJl4//sULYShKLbn+GqteR WLD7ExuErS2xbOFrZoitghInZz5hmcAoMgvJ2FlIWmYhaZmFpGUBI8sqRtHi1OLi3HQjI73U oszk4uL8PL281JJNjMA4OLjlt9UOxoPPHQ8xCnAwKvHwPljGFCHEmlhWXJl7iFGCg1lJhLev mTlCiDclsbIqtSg/vqg0J7X4EKM0B4uSOK/ZyvvhQgLpiSWp2ampBalFMFkmDk6pBsbe8J4J 698d2eRuoKZ77lz9nJjnfNyvG3wjck1a2wqWm5/VrI/WnughM4P1bkGoTXpfM/eVvfeebrfh T9RdVmXPy1F62k/2sU3A68s8qU5/2H2/vTZRvn5nb3e1wLk5XY51qozzDedPntEy50hk1o75 h+uEllwVYfIK2RCSYRChtF5o2aOmQCWW4oxEQy3mouJEADKQVfV/AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9OFiVftwiuQmlM4aUZBDsjNUl18>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Paul's review
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Oct 2016 13:56:05 -0000

Hi,

I've created a pull request for the WGLC comments. The current changes are =
based on Paul's WGLC comments.

https://github.com/cdh4u/draft-sctp-sdp/pull/7

Regards,

Christer

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: 16 October 2016 00:19
To: Paul Kyzivat <pkyzivat@alum.mit.edu>; mmusic@ietf.org
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Paul's review

Hi Paul,

Thanks for your review! Please see inline.

* Section 1:

> The following is present twice:
>
>    The Stream Control Transmission Protocol (SCTP) [RFC4960] is a
>    transport protocol used to establish associations between two
>    endpoints.
>
> I don't understand the point of including the following:
>
>    NOTE: TLS is designed to run on top of a byte-stream oriented
>    transport protocol providing a reliable, in-sequence delivery like
>    TCP.  [RFC6083] presents serious limitations with transporting TLS on
>    top of SCTP.  Therefore, defining a mechanism to negotiate media
>    streams transported using TLS on top of SCTP, i.e., 'SCTP/TLS', is
>    outside the scope of this specification.  In addition, defining a
>    mechanism to negotiate non-protected SCTP associations is also
>    outside the scope of this specification.
>
> This document doesn't discuss running *anything* in particular over SCTP,=
 so why single out TLS over SCTP?=20

The text seems to be a leftover from when the draft defined the O/A procedu=
res DTLS-over-SCTP. I will remove it (except for the last sentence - see mo=
re below).

> There is something similar that would make sense to mention: that=20
> running SCTP over TCP presents serious limitation, since it forces=20
> ordering and reliability even on SCTP streams that don't want that. So it=
 would be good to mention that TCP/DTLS/SCTP is only intended as a fallback=
 for use in situations where UDP is blocked.

I'll think of some text.

>OTOH, the following sentence:
>
>  In addition, defining a mechanism to negotiate non-protected SCTP associ=
ations is also
>    outside the scope of this specification.
>
> Is worth saying, though it needs rewording after removing the rest.

I'll think of something.

------

* Section 4.3:

>    NOTE: A mechanism on how to describe, and manage, individual SCTP
>    streams within an SCTP association, is outside the scope of this
>    specification.
>
> I think it would be helpful to make an informational reference to draft-i=
etf-mmusic-data-channel-sdpneg, since that is well along toward completion.

I can do that.

------

* Section 4.4:

> IMO it is very unwise to restate the syntax of the m- line here. That is =
defined in 4566/4566bis, and this doesn't change that.
>
> Instead, I think this section should restrict itself to defining the valu=
es that may be used for the fields <media> <port> <proto> <fmt> defined in =
4566. In particular:
>
> <media>: "application"
>
> <proto>: "UDP/DTLS/SCTP" or "TCP/DTLS/SCTP"
>
> <port>: UDP port number (for "UDP/DTLS/SCTP"), or
>         TCP port number (for ""UDP/DTLS/SCTP")
>
> <fmt>: a string denoting the association-usage, limited to the syntax
>       of a 'token' as defined in RFC4566.

Will do as suggested.

------

* Section 5.2:

> Rather than restate the general syntax of an attribute, please just=20
> define the parts that are unique to this attribute, in the style=20
> introduced in RFC4566bis. E.g.,
>
>    Name: sctp-port
>
>    Value: sctp-port-value
>
>    Usage Level: media
>
>    Charset Dependent: no
>
>    Mux Category: SPECIAL
>
>    Syntax:
>
>          sctp-port-value =3D 1*5<DIGIT defined in RFC4566>
>
>          The SCTP port range is between 0 and 65535 (both included).
>          Leading zeroes MUST NOT be used.
>
>    Example:
>
>          a=3Dsctp-port:5000

Will do as suggested.

------

* Section 5.3:

> The qualification in the first paragraph is now redundant since the draft=
 is now so qualified.

Just to verify that I understood the comment,  are you saying the first par=
agraph can be removed?

------

* Section 6.2:

> Rather than restate the general syntax of an attribute, please just=20
> define the parts that are unique to this attribute, in the style=20
> introduced in RFC4566bis. E.g.,
>
>    Name: max-message-size
>
>    Value: max-message-size-value
>
>    Usage Level: media
>
>    Charset Dependent: no
>
>    Mux Category: SPECIAL
>
>    Syntax:
>
>          max-message-size-value =3D 1*40<DIGIT defined in RFC4566>
>          *** Did you really want *40* here? ***

I don't remember where the number came from.

Any suggestion would be a reasonable number? Do we need to set a limit? As =
far as I remember, the standard does not define a max size.

>          Leading zeroes MUST NOT be used.
>
>    Example:
>
>          a=3Dmax-message-size:100000

Will do as suggested.

------

* Section 6.3:

> See comments on 5.3.

See reply above.

------

* Section 9.1:

> The following is redundant and can be removed: "In case of UDP/DTLS/SCTP =
and TCP/DTLS/SCTP".

Correct. I will remove it.

> Using "association/connection" invites confusion. Does the "/" mean OR?
>
> I suggest:
>
>    The SCTP association, DTLS association and TCP connection are
>    managed independently of each other.  Each can be re-established
>    without impacting others.

Looks good. I'll change as suggested.

------

* Section 9.2:

> I suggest s/discarded/ignored/

I'll change as suggested.

------

* Section 9.3:

> After reading this I remain confused about what triggers=20
> re-establishment. I *think* it is intended that this only be triggered by=
 an O/A where one side or the other has changed the port value. I'd like to=
 see this stated more explicitly.

I'll take a look.

> The following:
>
>    As both SCTP endpoints take the 'active' role, this specification
>    does not define usage of the SDP 'setup' attribute [RFC4145] for
>    SCTP.
>
> may be confusing because 'setup' is used for the m-line. I suggest:
>
>    As both SCTP endpoints take the 'active' role, the SDP 'setup'
>    attribute [RFC4145] does not apply to SCTP association
>    establishment. However the 'setup' attribute does apply to
>    establishment of underlying DTLS associations and TCP connections.
>    (See below.)
>
> A similar change is appropriate for the 'connection' attribute.

I'll think of some text.

> The text "NOTE: In case of SCTP-over-DTLS" is redundant and can be remove=
d.

Ok.

> The following wording is confusing (it seems circular):
>
>    When such SCTP association is re-established the
>    SCTP endpoints MUST use the procedures in this section for
>    establishing an SCTP association.
>
> I think this would be better stated:
>
>    The procedures in this section MUST be followed to re-establish the
>    SCTP association. This requires a new offer/answer exchange.

Ok.

------

* Section 10.2:

> Some offerers may not be capable of using 'actpass' because they=20
> aren't able to receive incoming connection requests. While this might=20
> be resolved by using STUN or TURN I don't think this draft should=20
> assume that those are required. I see no particular reason to prevent use=
 of "active" or "passive", though it might be good to encourage use of "act=
pass" when possible.

I agree. I'll change as suggested.=20

------

* Section 10.3:

>    Once the answerer has sent the answer the answerer MUST, if an SCTP
>    association has yet not been established, or if an existing SCTP
>    association is to be re-established, initiate the establishment of
>    the SCTP association.
>
>    The answerer follows the procedures in [I-D.ietf-mmusic-dtls-sdp]
>    regarding the establishment/re-establishment of the DTLS association.
>
>    In the case of TCP/DTLS/SCTP, the answerer follows the procedures in
>    [RFC4145] regarding the establishment/re-establishment of the TCP
>    connection association.
>
> I think the order of presentation here is backward. It needs to be=20
> carried out bottom to top, so I propose the order of these paragraphs=20
> be flipped. (Some wording tweaks will also be required to handle the=20
> transitions properly.)

I'll look at it.

------

* Section 10.4:

>Again the ordering seems wrong.

I'll look at it.

------

Thanks!

Regards,

Christer

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


From nobody Mon Oct 17 01:41:42 2016
Return-Path: <thomass.stach@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 9B19F1295C1 for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 01:41:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 72cCnlS0dsyI for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 01:41:39 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 2CF3F1294C7 for <mmusic@ietf.org>; Mon, 17 Oct 2016 01:41:39 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id b81so273943587lfe.1 for <mmusic@ietf.org>; Mon, 17 Oct 2016 01:41:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=2tUuCCdd/ra74daar1TeZzh/PT9mLxBEhMJ12TWxD04=; b=JaIyR0wLZYizOcuqKydg5BVvk8iCwIsqRCNI4KuE4ExP0as3HfZ046z4DVdqY3h1dk iwykYQwMMUUvLazoMrt1+lllkmwDcnf6CW8p66ZxjVCcjTVEBjpy9sWr6SSJUli5S9zs TooL36JiPXS8k6G7wPq7tIfs4j6RF1wDv4l5iDoLEa6bwt7tkO4KV4YnjcaRqB6gvsre P+OJHEEH+BHrVqBdpk4mOsO5PmS+I+SzJvFHMh7G5Nlc/KYQvMON4fRcXwyqP/3OxBR3 CSPuUNwCio3NHvoNq9O95mvEeLX2vkD1+9XW0GAqCYa7lxesv51GXqkpcp9rUoth12jw /skg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=2tUuCCdd/ra74daar1TeZzh/PT9mLxBEhMJ12TWxD04=; b=P2vKvzHNQ5qbNvFNodWhBXjzR7Olq5H0nV+K1TU187Vad6yDGSZqkyIwNOvclJR0k+ vcTslxl1kx1fOHyMyno2e463/WjCFACFXpeivXJH6Q4CwIqrFOly671IA83e6Pdz0H+e UceO+aW+A6y+GveS4NOA4Gg9v7yuJ8gfcvT7cDqkQAPLHOfQuu/2DljRuqLPh7vZQO7b 8jxnuxdX4j9XdhqSSRa/v9/4cg+scM9EDVewSysLtntgW37wnN06A77aHYwXh5jvFSbX NoAu0zptZm0OdbPPwZkwuUpVJezZ55pDrdaq1ujSXw7enG6fm2XsM+bAZilcGiHC9X6n E1Mg==
X-Gm-Message-State: AA6/9RmbIC/dvOTBPbsSqRv6nNPO8VMqpmNoKvuQjEbpZYc6KDE0AoKw+JJOCjnMIuPcYg==
X-Received: by 10.25.27.207 with SMTP id b198mr11619766lfb.18.1476693697121; Mon, 17 Oct 2016 01:41:37 -0700 (PDT)
Received: from [192.168.2.111] (d91-130-252-149.cust.tele2.at. [91.130.252.149]) by smtp.googlemail.com with ESMTPSA id g5sm7339694lfe.14.2016.10.17.01.41.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Oct 2016 01:41:36 -0700 (PDT)
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <D41AC393.10727%christer.holmberg@ericsson.com> <bc713d1a-acdb-af95-5391-b3e244e1126d@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1B3B2@ESESSMB209.ericsson.se> <e44e62ff-1b0d-9180-2872-b98c84cbb6f6@gmail.com> <D4226F4E.10D4F%christer.holmberg@ericsson.com> <7c516d72-ef2a-e928-dc4a-ee77298ebb22@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD668A9@ESESSMB209.ericsson.se>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <e22f8a1a-00f6-8c87-5a4e-8c1e6dfa75b2@gmail.com>
Date: Mon, 17 Oct 2016 10:41:35 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD668A9@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/hiwdkKuqNJ4LZVvpYgbKwTCZXak>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2016 08:41:41 -0000

Christer,

sorry for the delay i was busy with other stuff.

more inline


On 2016-10-12 21:51, Christer Holmberg wrote:
> Hi,
>
>>>>>>>> It has been suggested that removal of candidates should not be
>>>>>>>> part of trickle, but rather be defined in a separate future extension draft.
>>>>>>>> The comments below are based on that such "extension" may exist at
>>>>>>>> some point.
>>>>>>>>
>>>>>>>> The text in section 4.2 says:
>>>>>>>>        "In every INFO request agents MUST include all local
>>>>>>>>        candidates they have signaled previously.  This is necessary in order to
>>>>>>>>        more easily avoid problems that would arise from unreliable transports.  Mis-
>>>>>>>>        ordering can be detected through the CSeq: header field in the INFO
>>>>>>>>        request.  As a consequence candidates cannot be removed unless an ICE
>>>>>>>>        restart is performed.  Note that extension might be specified in the
>>>>>>>>        future that enable such removal without a restart."
>>>>>>>> Q1: Assuming someone does define an extension which allows removal
>>>>>>>> of candidates without a restart, do such candidates still have to
>>>>>>>> be included in the INFO, as they have been "previously signalled"?
>>>>>>> This would have to clarified in that future extension document
>>>>>>> together with corresponding backward compatibility issues and/or
>>>>>>> indication of support for such an extension. I don't want to do
>>>>>>> design here, but a=ice-options might be something to look at.
>>>>>> How you indicate support of such extension is outside the scope of
>>>>>> this thread. I want to clarify the exact semantics of a candidate in an INFO.
>>>> Again, I agree that how candidates are removed is outside the scope.
>>>> But, that doesn¹t change the fact that trickle needs to define exactly
>>>> what the semantic of the signalled candidates. I do NOT want a future
>>>> extension to change that semantic.
>> I don't how you want to preclude an arbitrary future extension to do such a change,
>> but in case of a "candidate removal" extension I don't see a problem with the current >concept.
>> The current concept is (as I understand it):
>> - An INFO always carries all candidates that belong to the currently valid ufrag/pwd.
> But that is not what the text is saying. "That belong" is not the same as "Previously signalled". "That belong" means they are still valid/active - at least in my ears.
Taking into account that draft-ice-trickle does not provide  any 
mechanism for removal in my ears both sound the same -  currently that is.
Would then changing  "... Previously signalled ..." to "That belong" in 
the body of draft-mmusic-trickle-ice-sdp be fine then?
>
>> - We have the restriction that in subsequent INFOs the number of these candidates can
>>   only increase or remain constant until end-of-candidates is signalled.
> I think we should remove that restriction.
Taking into account that draft-ice-trickle does not provide  any 
mechanism for removal in my ears such a restriction is implied - 
currently that is again.
However I would be fine with not explicitly mentioning this in 
draft-mmusic-trickle-ice-sdp.

>
> Even if we don't have a defined mechanism for removing candidates, they can disappear anyway. The TURN server may crash, etc.
Would that be detected via the failed connectivity checks?
> Why should we keep signalling such candidates?
I doesn't do any harm. Section 4.2 specifies that only new candidates 
are relayed to the ICE agent.
> We could of course do an ICE re-start whenever a candidate is removed (one way or another), but I don't think we want to do that...
Probably not, but that is the way that Trickle-ICE inherited from 5245.
> But, again, by ONLY signalling the added candidates we don't have the issue with removed candidates to begin with.
There  will certainly be other issues.
>> If someone wants to define a "candidate removal" extension, he/she can keep the semantics of the first item, i.e.
>> - An INFO always carries all candidates that belong to the currently valid ufrag/pwd.
> Again, I don't think that is what "previously signalled" means.
>
>>   and would have to do the following
>> - modify the constraint to something like  "In subsequent INFOs the number of these candidates can increase, _decrease_ or remain constant "
> I see no reason to have that constraint to begin with.
>
>> - define how support for the "candidate removal" extension is negotiated  and how backward compatibility is achieved
>> -  define how candidates are actually removed
> I agree the negotiation and mechanism should be defined elsewhere.
>
> But, again again, I'd like to hear whether people would be ok to only signal the added candidates in INFO.
>
> <snip/>
>>>>> Also, an "extension" could have removed candidiates since the
>>>>> ufrag/pwd was signalled. So, you cannot simply say "since current
>>>>> ufrag/pwd was signalled". You also need to say something like "and
>>>>> are still active/in use", or something like that.
>>>> Why would I have to?
>>> Because I assume we only want to signal candidates that are still in use.
>>>
>>> That is what I meant by the semantic comment earlier. I don¹t want the
>>> semantic of a signalled candidate to be ³It was signalled at some
>>> point with the current ufrag/pwd, but it may no longer be in use². I
>>> want it to be ³It was signalled at some point with the current
>>> ufrag/pwd, and it is still in use².
>> Does my answer from above work for you?
> Partly. But, again, I don't think what you are saying is what is written in the draft :)
>
>>>>>>> Q2: What if an INFO does NOT contain a local candidate that has
>>>>>>> previously been signaled? Do we assume it has been removed using
>>>>>>> some "extension"? Do we assume it's still there?
>>>>>> We could either treat this case as an error and ignore the content
>>>>>> of that INFO.
>>>>>> Probably not the best idea, e.g. in case that a=end-of-candidates
>>>>>> was included.
>>>>>> Or we can assume (in absence of any "removal extension") that it is
>>>>>> still there. That would allow to still make use of any newly
>>>>>> trickled candidates in such an INFO. This makes more sense to me.
>>>>>> If this is agreable I would be happy to put corresponding text into
>>>>>> section 4.2.
>>>>> ...or, we could go back to my previous proposal, and say that we
>>>>> *ONLY* signal the new candidates, and that the INFO has no impact on
>>>>> any other candidates :)
>>>> Well, there is consensus since  2013 that the INFO carries all candidates.
>>>> It was one outcome of the thread that started here
>>>> https://mailarchive.ietf.org/arch/search/?email_list=mmusic&gbt=1&ind
>>>> ex=T7R18RumQQJrmtHRh1lmcf9wcqs
>>>>
>>>> I can't remember that this consensus was not challenged since then,
>>>> but I guess that all implementations will expect all candidates in the INFO.
>>> We didn¹t discuss removal of candidates back in 2013, so I think we
>>> shall re-ask the community.
>> I still think that the current concept works, so will you want to ask that then?
> I am asking as we speak. Anyone who does not agree with the suggestion should speak up :)
Nicely replied :)
However, it certainly takes more than silence to change the current 
procedure in the document.
There needs to be explicit support for such a change from a larger 
number of participants.
I also believe that we first need to see some elaborated text that deals 
with issues like reordering and other corner cases.

The current concept is mature and I also showed a path how it could be 
extended to deal with candidate removal.
So, I don't see a need to change, especially considering that we were 
asked to get things finished rather quickly.

Regards
Thomas
>
> Regards,
>
> Christer
>
>


From nobody Mon Oct 17 02:17:56 2016
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 4B0E21295C6 for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 02:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 dieR5ILAOhO7 for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 02:17:53 -0700 (PDT)
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 3A2C912956D for <mmusic@ietf.org>; Mon, 17 Oct 2016 02:17:53 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-45-5804973fea78
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by  (Symantec Mail Security) with SMTP id 4F.BA.02458.F3794085; Mon, 17 Oct 2016 11:17:51 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0319.002; Mon, 17 Oct 2016 11:17:50 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Thomas Stach <thomass.stach@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
Thread-Index: AQHSHxIL5dxB//uBWky8GjwyA0+P66CZ76sAgAjKcACAAD99AIABlqsAgACw0bCABwPJgIAAPlIA
Date: Mon, 17 Oct 2016 09:17:50 +0000
Message-ID: <D42A7012.1139C%christer.holmberg@ericsson.com>
References: <D41AC393.10727%christer.holmberg@ericsson.com> <bc713d1a-acdb-af95-5391-b3e244e1126d@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1B3B2@ESESSMB209.ericsson.se> <e44e62ff-1b0d-9180-2872-b98c84cbb6f6@gmail.com> <D4226F4E.10D4F%christer.holmberg@ericsson.com> <7c516d72-ef2a-e928-dc4a-ee77298ebb22@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD668A9@ESESSMB209.ericsson.se> <e22f8a1a-00f6-8c87-5a4e-8c1e6dfa75b2@gmail.com>
In-Reply-To: <e22f8a1a-00f6-8c87-5a4e-8c1e6dfa75b2@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <BF7AA8F1C9DFE746BD8D3A2398A18228@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCIsWRmVeSWpSXmKPExsUyM2K7pa79dJYIg/bNGhZTlz9msfh0YiuT A5PHzll32T2WLPnJFMAUxWWTkpqTWZZapG+XwJVx7fR+toJHphV3W5tZGxg3mHQxcnJICJhI NG5ZxdzFyMUhJLCeUWLe0iWMEM5iRolLKw+xdDFycLAJWEh0/9MGaRARCJT4fOY4E0iNsMBU Ronrp/tYIRLTGCWeLrWCsKMkHl9dyAxiswioSuxbtJsdxOYVsJbY9ukcO8SCg8wS8z+uBGvm FLCVOPJyHxOIzSggJvH91Bowm1lAXOLWk/lMEKcKSCzZc54ZwhaVePn4HyvIcaICehJr7oeB mBICShLTtqZBdGpJfPmxjw3CtpaYtO8yM4StKDGl+yHUOYISJ2c+YZnAKDYLybJZSNpnIWmf haR9FpL2BYysqxhFi1OLi3PTjYz0Uosyk4uL8/P08lJLNjEC4+rglt9WOxgPPnc8xCjAwajE w/tgGVOEEGtiWXFl7iFGCQ5mJRHeuiksEUK8KYmVValF+fFFpTmpxYcYpTlYlMR5zVbeDxcS SE8sSc1OTS1ILYLJMnFwSjUwqlV1HM7jyylpCg8XEN+b87c1fuq8kKW6PTf/d50ufRJW22b8 rz3hRt9pkeXh8wPdxE4vNtr1leFGwUvdk7HdtTs25Tht0chVbkj4VX1sjvr9uD2LFt3hVgs7 4e/gECgwfW60v8R3E+4Ja4pPb85w3vNNf+o17jDX7xL3+1SWBe+2dPnw7KyBEktxRqKhFnNR cSIAGwwctKcCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/X_uafiBcOm70rnF0tDn9LNLV_4A>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2016 09:17:55 -0000

SGksDQoNCj4+Pj4+Pj4+Pkl0IGhhcyBiZWVuIHN1Z2dlc3RlZCB0aGF0IHJlbW92YWwgb2YgY2Fu
ZGlkYXRlcyBzaG91bGQgbm90IGJlDQo+Pj4+Pj4+Pj4gcGFydCBvZiB0cmlja2xlLCBidXQgcmF0
aGVyIGJlIGRlZmluZWQgaW4gYSBzZXBhcmF0ZSBmdXR1cmUNCj4+Pj4+Pj4+PmV4dGVuc2lvbiBk
cmFmdC4NCj4+Pj4+Pj4+PiBUaGUgY29tbWVudHMgYmVsb3cgYXJlIGJhc2VkIG9uIHRoYXQgc3Vj
aCAiZXh0ZW5zaW9uIiBtYXkgZXhpc3QNCj4+Pj4+Pj4+PmF0DQo+Pj4+Pj4+Pj4gc29tZSBwb2lu
dC4NCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+IFRoZSB0ZXh0IGluIHNlY3Rpb24gNC4yIHNheXM6DQo+
Pj4+Pj4+Pj4gICAgICAgICJJbiBldmVyeSBJTkZPIHJlcXVlc3QgYWdlbnRzIE1VU1QgaW5jbHVk
ZSBhbGwgbG9jYWwNCj4+Pj4+Pj4+PiAgICAgICAgY2FuZGlkYXRlcyB0aGV5IGhhdmUgc2lnbmFs
ZWQgcHJldmlvdXNseS4gIFRoaXMgaXMNCj4+Pj4+Pj4+Pm5lY2Vzc2FyeSBpbiBvcmRlciB0bw0K
Pj4+Pj4+Pj4+ICAgICAgICBtb3JlIGVhc2lseSBhdm9pZCBwcm9ibGVtcyB0aGF0IHdvdWxkIGFy
aXNlIGZyb20NCj4+Pj4+Pj4+PnVucmVsaWFibGUgdHJhbnNwb3J0cy4gIE1pcy0NCj4+Pj4+Pj4+
PiAgICAgICAgb3JkZXJpbmcgY2FuIGJlIGRldGVjdGVkIHRocm91Z2ggdGhlIENTZXE6IGhlYWRl
ciBmaWVsZA0KPj4+Pj4+Pj4+aW4gdGhlIElORk8NCj4+Pj4+Pj4+PiAgICAgICAgcmVxdWVzdC4g
IEFzIGEgY29uc2VxdWVuY2UgY2FuZGlkYXRlcyBjYW5ub3QgYmUgcmVtb3ZlZA0KPj4+Pj4+Pj4+
dW5sZXNzIGFuIElDRQ0KPj4+Pj4+Pj4+ICAgICAgICByZXN0YXJ0IGlzIHBlcmZvcm1lZC4gIE5v
dGUgdGhhdCBleHRlbnNpb24gbWlnaHQgYmUNCj4+Pj4+Pj4+PnNwZWNpZmllZCBpbiB0aGUNCj4+
Pj4+Pj4+PiAgICAgICAgZnV0dXJlIHRoYXQgZW5hYmxlIHN1Y2ggcmVtb3ZhbCB3aXRob3V0IGEg
cmVzdGFydC4iDQo+Pj4+Pj4+Pj4gUTE6IEFzc3VtaW5nIHNvbWVvbmUgZG9lcyBkZWZpbmUgYW4g
ZXh0ZW5zaW9uIHdoaWNoIGFsbG93cw0KPj4+Pj4+Pj4+cmVtb3ZhbA0KPj4+Pj4+Pj4+IG9mIGNh
bmRpZGF0ZXMgd2l0aG91dCBhIHJlc3RhcnQsIGRvIHN1Y2ggY2FuZGlkYXRlcyBzdGlsbCBoYXZl
IHRvDQo+Pj4+Pj4+Pj4gYmUgaW5jbHVkZWQgaW4gdGhlIElORk8sIGFzIHRoZXkgaGF2ZSBiZWVu
ICJwcmV2aW91c2x5DQo+Pj4+Pj4+Pj5zaWduYWxsZWQiPw0KPj4+Pj4+Pj4gVGhpcyB3b3VsZCBo
YXZlIHRvIGNsYXJpZmllZCBpbiB0aGF0IGZ1dHVyZSBleHRlbnNpb24gZG9jdW1lbnQNCj4+Pj4+
Pj4+IHRvZ2V0aGVyIHdpdGggY29ycmVzcG9uZGluZyBiYWNrd2FyZCBjb21wYXRpYmlsaXR5IGlz
c3VlcyBhbmQvb3INCj4+Pj4+Pj4+IGluZGljYXRpb24gb2Ygc3VwcG9ydCBmb3Igc3VjaCBhbiBl
eHRlbnNpb24uIEkgZG9uJ3Qgd2FudCB0byBkbw0KPj4+Pj4+Pj4gZGVzaWduIGhlcmUsIGJ1dCBh
PWljZS1vcHRpb25zIG1pZ2h0IGJlIHNvbWV0aGluZyB0byBsb29rIGF0Lg0KPj4+Pj4+PiBIb3cg
eW91IGluZGljYXRlIHN1cHBvcnQgb2Ygc3VjaCBleHRlbnNpb24gaXMgb3V0c2lkZSB0aGUgc2Nv
cGUgb2YNCj4+Pj4+Pj4gdGhpcyB0aHJlYWQuIEkgd2FudCB0byBjbGFyaWZ5IHRoZSBleGFjdCBz
ZW1hbnRpY3Mgb2YgYSBjYW5kaWRhdGUNCj4+Pj4+Pj5pbiBhbiBJTkZPLg0KPj4+Pj4gQWdhaW4s
IEkgYWdyZWUgdGhhdCBob3cgY2FuZGlkYXRlcyBhcmUgcmVtb3ZlZCBpcyBvdXRzaWRlIHRoZSBz
Y29wZS4NCj4+Pj4+IEJ1dCwgdGhhdCBkb2Vzbqn2dCBjaGFuZ2UgdGhlIGZhY3QgdGhhdCB0cmlj
a2xlIG5lZWRzIHRvIGRlZmluZQ0KPj4+Pj5leGFjdGx5DQo+Pj4+PiB3aGF0IHRoZSBzZW1hbnRp
YyBvZiB0aGUgc2lnbmFsbGVkIGNhbmRpZGF0ZXMuIEkgZG8gTk9UIHdhbnQgYSBmdXR1cmUNCj4+
Pj4+IGV4dGVuc2lvbiB0byBjaGFuZ2UgdGhhdCBzZW1hbnRpYy4NCj4+PiBJIGRvbid0IGhvdyB5
b3Ugd2FudCB0byBwcmVjbHVkZSBhbiBhcmJpdHJhcnkgZnV0dXJlIGV4dGVuc2lvbiB0byBkbw0K
Pj4+c3VjaCBhIGNoYW5nZSwNCj4+PiBidXQgaW4gY2FzZSBvZiBhICJjYW5kaWRhdGUgcmVtb3Zh
bCIgZXh0ZW5zaW9uIEkgZG9uJ3Qgc2VlIGEgcHJvYmxlbQ0KPj4+d2l0aCB0aGUgY3VycmVudCA+
Y29uY2VwdC4NCj4+PiBUaGUgY3VycmVudCBjb25jZXB0IGlzIChhcyBJIHVuZGVyc3RhbmQgaXQp
Og0KPj4+IC0gQW4gSU5GTyBhbHdheXMgY2FycmllcyBhbGwgY2FuZGlkYXRlcyB0aGF0IGJlbG9u
ZyB0byB0aGUgY3VycmVudGx5DQo+Pj52YWxpZCB1ZnJhZy9wd2QuDQo+PiBCdXQgdGhhdCBpcyBu
b3Qgd2hhdCB0aGUgdGV4dCBpcyBzYXlpbmcuICJUaGF0IGJlbG9uZyIgaXMgbm90IHRoZSBzYW1l
DQo+PmFzICJQcmV2aW91c2x5IHNpZ25hbGxlZCIuICJUaGF0IGJlbG9uZyIgbWVhbnMgdGhleSBh
cmUgc3RpbGwNCj4+dmFsaWQvYWN0aXZlIC0gYXQgbGVhc3QgaW4gbXkgZWFycy4NCj5UYWtpbmcg
aW50byBhY2NvdW50IHRoYXQgZHJhZnQtaWNlLXRyaWNrbGUgZG9lcyBub3QgcHJvdmlkZSAgYW55
DQo+bWVjaGFuaXNtIGZvciByZW1vdmFsIGluIG15IGVhcnMgYm90aCBzb3VuZCB0aGUgc2FtZSAt
ICBjdXJyZW50bHkgdGhhdCBpcy4NCj5Xb3VsZCB0aGVuIGNoYW5naW5nICAiLi4uIFByZXZpb3Vz
bHkgc2lnbmFsbGVkIC4uLiIgdG8gIlRoYXQgYmVsb25nIiBpbg0KPnRoZSBib2R5IG9mIGRyYWZ0
LW1tdXNpYy10cmlja2xlLWljZS1zZHAgYmUgZmluZSB0aGVuPw0KDQpMZXShr3MgdGFsayBhYm91
dCBhIG1lY2hhbmlzbSB0aGF0IERPRVMgZXhpc3Q6IGNvbnRpbm91cyBjb25zZW50Lg0KDQpBY2Nv
cmRpbmcgdG8gUkZDIDc2NzUsIGlmIGNvbnNlbnQgaXMgbG9zdCBmb3Igc3BlY2lmaWMgY2FuZGlk
YXRlcyBhbiBJQ0UNCnJlLXN0YXJ0IGlzIHJlcXVpcmVkIGluIG9yZGVyIHRvIHVzZSB0aGUgY2Fu
ZGlkYXRlIHBhaXIuDQoNClNvLCBiZWZvcmUgc3VjaCBJQ0UgcmUtc3RhcnQgb2NjdXIsIHdoeSBz
aG91bGQgd2Uga2VlcCBzaWduYWxsaW5nIHN1Y2gNCmNhbmRpZGF0ZXMgaW4gSU5GT3M/DQoNCkFs
c28gbm90ZSB0aGF0IDc2NzUgZGVmaW5lcyBhIG1lY2hhbmlzbSB0byBleHBsaWNpdGx5IHNpZ25h
bCB0aGF0IGNvbnNlbnQNCmhhcyBiZWVuIHJlbW92ZWQuIFdoZXRoZXIgd2UgY2FsbCB0aGF0IKGw
cmVtb3ZhbCBvZiBjYW5kaWRhdGWhsSBvciBub3QgY2FuDQpiZSBkaXNjdXNzZWQsIGJ1dCB3aHkg
c2hvdWxkIHN1Y2ggY2FuZGlkYXRlcyBjb250aW51ZSB0byBiZSBzaWduYWxsZWQ/DQoNCg0KLi4u
DQoNCg0KPj5FdmVuIGlmIHdlIGRvbid0IGhhdmUgYSBkZWZpbmVkIG1lY2hhbmlzbSBmb3IgcmVt
b3ZpbmcgY2FuZGlkYXRlcywgdGhleQ0KPj5jYW4gZGlzYXBwZWFyIGFueXdheS4gVGhlIFRVUk4g
c2VydmVyIG1heSBjcmFzaCwgZXRjLg0KPldvdWxkIHRoYXQgYmUgZGV0ZWN0ZWQgdmlhIHRoZSBm
YWlsZWQgY29ubmVjdGl2aXR5IGNoZWNrcz8NCg0KWWVzLiBPciwgaWYgY29uaW5vdXMgY29uc2Vu
dCBpcyB1c2VkLCB3aGVuIGNvbnNlbnQgZXhwaXJlcy4NCg0KDQo+PiBXaHkgc2hvdWxkIHdlIGtl
ZXAgc2lnbmFsbGluZyBzdWNoIGNhbmRpZGF0ZXM/DQo+SSBkb2Vzbid0IGRvIGFueSBoYXJtLiBT
ZWN0aW9uIDQuMiBzcGVjaWZpZXMgdGhhdCBvbmx5IG5ldyBjYW5kaWRhdGVzDQo+YXJlIHJlbGF5
ZWQgdG8gdGhlIElDRSBhZ2VudC4NCj4+IFdlIGNvdWxkIG9mIGNvdXJzZSBkbyBhbiBJQ0UgcmUt
c3RhcnQgd2hlbmV2ZXIgYSBjYW5kaWRhdGUgaXMgcmVtb3ZlZA0KPj4ob25lIHdheSBvciBhbm90
aGVyKSwgYnV0IEkgZG9uJ3QgdGhpbmsgd2Ugd2FudCB0byBkbyB0aGF0Li4uDQo+UHJvYmFibHkg
bm90LCBidXQgdGhhdCBpcyB0aGUgd2F5IHRoYXQgVHJpY2tsZS1JQ0UgaW5oZXJpdGVkIGZyb20g
NTI0NS4NCj4+IEJ1dCwgYWdhaW4sIGJ5IE9OTFkgc2lnbmFsbGluZyB0aGUgYWRkZWQgY2FuZGlk
YXRlcyB3ZSBkb24ndCBoYXZlIHRoZQ0KPj5pc3N1ZSB3aXRoIHJlbW92ZWQgY2FuZGlkYXRlcyB0
byBiZWdpbiB3aXRoLg0KPlRoZXJlICB3aWxsIGNlcnRhaW5seSBiZSBvdGhlciBpc3N1ZXMuDQoN
ClBsZWFzZSBwcmVzZW50IHRob3NlIGlzc3VlcyBzbyB3ZSBjYW4gZGlzY3VzcyB0aGVtLg0KDQou
Li4NCg0KPj4+IEkgc3RpbGwgdGhpbmsgdGhhdCB0aGUgY3VycmVudCBjb25jZXB0IHdvcmtzLCBz
byB3aWxsIHlvdSB3YW50IHRvIGFzaw0KPj4+dGhhdCB0aGVuPw0KPj4gSSBhbSBhc2tpbmcgYXMg
d2Ugc3BlYWsuIEFueW9uZSB3aG8gZG9lcyBub3QgYWdyZWUgd2l0aCB0aGUgc3VnZ2VzdGlvbg0K
Pj5zaG91bGQgc3BlYWsgdXAgOikNCj5OaWNlbHkgcmVwbGllZCA6KQ0KPkhvd2V2ZXIsIGl0IGNl
cnRhaW5seSB0YWtlcyBtb3JlIHRoYW4gc2lsZW5jZSB0byBjaGFuZ2UgdGhlIGN1cnJlbnQNCj5w
cm9jZWR1cmUgaW4gdGhlIGRvY3VtZW50Lg0KPlRoZXJlIG5lZWRzIHRvIGJlIGV4cGxpY2l0IHN1
cHBvcnQgZm9yIHN1Y2ggYSBjaGFuZ2UgZnJvbSBhIGxhcmdlcg0KPm51bWJlciBvZiBwYXJ0aWNp
cGFudHMuDQo+SSBhbHNvIGJlbGlldmUgdGhhdCB3ZSBmaXJzdCBuZWVkIHRvIHNlZSBzb21lIGVs
YWJvcmF0ZWQgdGV4dCB0aGF0IGRlYWxzDQo+d2l0aCBpc3N1ZXMgbGlrZSByZW9yZGVyaW5nIGFu
ZCBvdGhlciBjb3JuZXIgY2FzZXMuDQo+DQo+VGhlIGN1cnJlbnQgY29uY2VwdCBpcyBtYXR1cmUg
YW5kIEkgYWxzbyBzaG93ZWQgYSBwYXRoIGhvdyBpdCBjb3VsZCBiZQ0KPmV4dGVuZGVkIHRvIGRl
YWwgd2l0aCBjYW5kaWRhdGUgcmVtb3ZhbC4NCj5TbywgSSBkb24ndCBzZWUgYSBuZWVkIHRvIGNo
YW5nZSwgZXNwZWNpYWxseSBjb25zaWRlcmluZyB0aGF0IHdlIHdlcmUNCj5hc2tlZCB0byBnZXQg
dGhpbmdzIGZpbmlzaGVkIHJhdGhlciBxdWlja2x5Lg0KDQoNCkkgYXNzdW1lIHdlIGFyZSBhbHNv
IGFza2VkIHRvIGdldCB0aGluZ3MgZmluaXNoZWQgcHJvcGVybHkgOikNCg0KUmVnYXJkcywNCg0K
Q2hyaXN0ZXINCg0K


From nobody Mon Oct 17 02:38:01 2016
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 CDA531295BF for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 02:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 rzOWeOaoLkVC for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 02:37:57 -0700 (PDT)
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 3E70D128B37 for <mmusic@ietf.org>; Mon, 17 Oct 2016 02:37:57 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-df-58049bf39faf
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by  (Symantec Mail Security) with SMTP id 1B.F1.02551.3FB94085; Mon, 17 Oct 2016 11:37:55 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0319.002; Mon, 17 Oct 2016 11:37:40 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
Thread-Index: AQHSKFoabubXRq8c+EawmGSRTGgMMw==
Date: Mon, 17 Oct 2016 09:37:40 +0000
Message-ID: <D42A7728.113D4%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_D42A7728113D4christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyM2K7pe7n2SwRBpd+allMXf6YxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGbtvvGIuuGJU8fXxf5YGxvdaXYycHBICJhLHDm9m7GLk4hAS WM8ocePobzYIZzGjxL7GA0xdjBwcbAIWEt3/tEEaRATUJb7u7WEGsYUFfCWWXjvICBEPkTj7 dSU7hK0n0X7+EVicRUBV4s+cc0wgNq+AtcSv3WfAbEYBMYnvp9aA2cwC4hK3nsxngjhIQGLJ nvPMELaoxMvH/1hBThAFmrnmfhhEWEnix4ZLLBCtCRIr+5awQIwXlDg58wnLBEahWUimzkJS NgtJGUTcQOL9ufnMELa2xLKFr6FsfYmNX84yQtjWEk/PrWdEVrOAkWMVo2hxanFxbrqRsV5q UWZycXF+nl5easkmRmCkHNzyW3cH4+rXjocYBTgYlXh4HyxjihBiTSwrrsw9xCjBwawkwls3 hSVCiDclsbIqtSg/vqg0J7X4EKM0B4uSOK/ZyvvhQgLpiSWp2ampBalFMFkmDk6pBkaNPE9F K7Mrb/dsufZ0NiMXu+JqrVt7D+mcer7k8K076532s5rxSXAc5EoVlF6v46srt1Dz68f/CU2C troH3fZpHvopurJTjqtnZ/i2qSdnWy0q6go+/W6jTemfV0v///iYf1phdttt9+CPjjazfS+H u/z96ZLioKl3KmZvVGqqjEzU1sIH93iVWIozEg21mIuKEwEXllZ9kAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/THu9XOHlFVXT3UUuu9EVde83Luw>
Subject: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2016 09:38:00 -0000

--_000_D42A7728113D4christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

The issue in this e-mail has came up during ICE discussions related to BFCP=
 and SCTP.

Section 4.1.1.2 of draft-ietf-mmusic-ice-sip-sdp-10 says:

   "The default candidates are added to the SDP as the default
   destination for media.  For streams based on RTP, this is done by
   placing the IP address and port of the RTP candidate into the "c=3D"
   and "m=3D" lines, respectively.=94

=85and:

   "The transport addresses that will be the default destination for
   media when communicating with non-ICE peers MUST also be present as
   candidates in one or more a=3Dcandidate lines."

Assume the offerer sends an offer. The default candidate is TCP-based, whic=
h will be reflected in the m- line (e.g., TCP/DTLS/SCTP). The offer also co=
ntains UDP-based candidates.

Now, assume the default candidate of the answerer is UDP-based (perhaps the=
 answerer doesn=92t even support TCP). However, according to the O/A rules,=
 the answerer cannot change the m- line proto in the answer (e.g., UDP/DTLS=
/SCTP). So, if I understand correctly, it means that the answerer must reje=
ct the m- line =96 even if there are UDP-based candidates that the answerer=
 would support.

A solution to this would be to NOT mandate the m- line to match the default=
 candidate in the answer. So, in the example above, the answerer could incl=
ude (TCP/DTLS/SCTP) in the m- line, but ONLY provide UDP candidates.

Another solution would to always mandate support of one or more specific tr=
ansports, and specify that the default candidate MUST use that transport.

Regards,

Christer



--_000_D42A7728113D4christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <6E392EB46D3D1D4892E188838CC939A5@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>Hi,</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>The issue in this e-mail has came up during ICE discussions related to BFC=
P and SCTP.</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>Section 4.1.1.2 of draft-ietf-mmusic-ice-sip-sdp-10 says:</font></div>
<div>
<pre style=3D"color: rgb(0, 0, 0); font-size: 14px; font-variant-ligatures:=
 normal; orphans: 2; widows: 2; word-wrap: break-word; white-space: pre-wra=
p;"><font face=3D"Calibri">   &quot;The default candidates are added to the=
 SDP as the default
   destination for media.  For streams based on RTP, this is done by
   placing the IP address and port of the RTP candidate into the &quot;c=3D=
&quot;
   and &quot;m=3D&quot; lines, respectively.=94</font></pre>
<pre style=3D"color: rgb(0, 0, 0); font-size: 14px; font-variant-ligatures:=
 normal; orphans: 2; widows: 2; word-wrap: break-word; white-space: pre-wra=
p;"><font face=3D"Calibri">=85and:</font></pre>
<pre style=3D"color: rgb(0, 0, 0); font-size: 14px; font-variant-ligatures:=
 normal; orphans: 2; widows: 2; word-wrap: break-word; white-space: pre-wra=
p;"><pre style=3D"font-variant-ligatures: normal; word-wrap: break-word; wh=
ite-space: pre-wrap;"><font face=3D"Calibri">   &quot;The transport address=
es that will be the default destination for
   media when communicating with non-ICE peers MUST also be present as
   candidates in one or more a=3Dcandidate lines.&quot;</font></pre></pre>
</div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>Assume the offerer sends an offer. The default c</font><span style=3D"font=
-family: Calibri;">andidate is TCP-based, which will be reflected in the m-=
 line (e.g., TCP/DTLS/SCTP). The offer
 also contains UDP-based candidates.</span></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>Now, assume the default candidate of the answerer is UDP-based (perhaps th=
e answerer doesn=92t even support TCP). However, according to the O/A rules=
, the answerer cannot change the m- line
 proto in the answer (e.g., UDP/DTLS/SCTP).&nbsp;</font><span style=3D"font=
-family: Calibri;">So, if I understand correctly, it means that the answere=
r must reject the m- line =96 even if there are UDP-based candidates that t=
he answerer would support.</span></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>A solution to this would be to NOT mandate the m- line to match the defaul=
t candidate in the answer. So, in the example above, the answerer could inc=
lude (TCP/DTLS/SCTP) in the m- line,
 but ONLY provide UDP candidates.</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;">Another solution would=
 to always mandate support of one or more specific transports, and specify =
that the default candidate MUST use that transport.</div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>Regards,</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>Christer</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
</body>
</html>

--_000_D42A7728113D4christerholmbergericssoncom_--


From nobody Mon Oct 17 02:51:09 2016
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 181241295D8 for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 02:51:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 MQnfH5c2LPDL for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 02:51:06 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 783A81295C4 for <mmusic@ietf.org>; Mon, 17 Oct 2016 02:51:06 -0700 (PDT)
Received: from [130.209.247.112] (port=65068 helo=mangole.dcs.gla.ac.uk) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1bw4ZS-00027U-RN; Mon, 17 Oct 2016 10:51:04 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com>
Date: Mon, 17 Oct 2016 10:50:50 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/qtqYqTbaMXPKhp9SCQCG1R-YaT8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2016 09:51:08 -0000

> On 14 Oct 2016, at 08:54, Magnus Westerlund =
<magnus.westerlund@ericsson.com> wrote:
>=20
> Den 2016-10-13 kl. 18:01, skrev Christer Holmberg:
>> However, Magnus told me it=E2=80=99s not needed, so I=E2=80=99d like =
to get some input
>> from him.
>>=20
>> *From:*Cullen Jennings [mailto:fluffy@iii.ca]
>> That looks about right for RTP but I think it is still missing stuff =
for
>> RTCP handling. Here is the current text we did for JSEP. I prefer the
>> style in which you described it compared to the algorithm style below
>> but I think this might help figure out what to write for RTCP.
>>=20
>=20
> I dislike the algorithmic description JSEP has because it inserts =
itself at position in the stack where I would not myself implement the =
binding handling. The implementations of RTP stacks I have made have =
never let the full RTCP packets be available to the application layer. =
It has only implemented event and request based interface to provide the =
triggers and data associated with the differnet RTCP packets. Thus, from =
my perspective the routing of the RTCP packets becomes a question if the =
SSRC is bound to the right m=3D. Then handel the received RTCP packets =
in that context.
>=20
> So what might be a suitable RTCP clarification regarding RTCP would be =
the following.
>=20
> Simply add RTCP in the following sentence:
>=20
> "Later, when an offerer or answerer receives an RTP packet that does =
not carry the identification-tag, it can associate the packet with the
> correct "m=3D" line using the SSRC value."
>=20
> so that it reads:
>=20
> "Later, when an offerer or answerer receives an RTP or RTCP packet =
that does not carry the identification-tag, it can associate the packet =
with the correct "m=3D" line using the SSRC value."
>=20
> Regarding the second paragraph. If the association has been done =
according to this part then also the RTCP packets has an association. If =
an RTCP packet arrives with a non associated SSRC, then many RTCP =
packets type can still be processed and the information stored in the =
SSRC related information table. Some that are application interaction =
related, like some of the feedback messages can of course not be =
handled.
>=20
> One very important aspect here is that the basic RTCP processing do =
need to occur for also non-associated SSRCs. This to ensure that the =
sender get the RTCP feedback information for congestion control =
purposes. We want the transport layer functions to continue function, =
even if the application can't consume the packets.
>=20
> Thus, I would consider that the "the packet SHOULD be dropped." needs =
an addition that says after having been processed as received by the =
RTCP layer. If we don't report them as received we skew the congestion =
control information, and it will make any coupled congestion controller =
that looks at the set of RTP streams being emitted take the wrong =
decision. I also assumes that a lack of association is in most cases a =
temporary issue that will be resolved by the regular transmissions.

I agree with all of this. The mapping shouldn=E2=80=99t be from RTP or =
RTCP packets onto RtpRecivers. The RTP protocol requires RTP and RTCP =
packets be associated to an SSRC, and the mapping is to determine =
what=E2=80=99s the role of that SSRC (i.e., to map from SSRC to =
RtpReceiver).


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





From nobody Mon Oct 17 05:36:35 2016
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 61CA3129489 for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 05:36:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 tElqmzAXWY01 for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 05:36:32 -0700 (PDT)
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 2A4521293E1 for <mmusic@ietf.org>; Mon, 17 Oct 2016 05:36:32 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-54-5804c5ce771a
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by  (Symantec Mail Security) with SMTP id 8A.4D.02551.EC5C4085; Mon, 17 Oct 2016 14:36:30 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0319.002; Mon, 17 Oct 2016 14:36:29 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
Thread-Index: AQHSJHSivk5Ucbs2BE2kFscuEARQNKCmW5CAgAAxTzCAAOkBgIAE15EAgABieAA=
Date: Mon, 17 Oct 2016 12:36:28 +0000
Message-ID: <D42AA198.11408%christer.holmberg@ericsson.com>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org>
In-Reply-To: <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <6C422418E8DAFA44AD9AFC73CFE7898F@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOIsWRmVeSWpSXmKPExsUyM2K7uu65oywRBkv7RSyWvzzBaPFh/Q9G i6nLH7M4MHtMu3+fzWPJkp9MHpfPf2QMYI7isklJzcksSy3St0vgytjScJmlYL5cxYWD75ga GI9LdDFyckgImEi8XHWABcQWEljPKNH6z6iLkQvIXswo0X50EmsXIwcHm4CFRPc/bZAaEYFo iVU/zrOB2MwCHhLfP09jBrGFBTIkPh9dxgRSLiKQKbFipR+E6Sfx6Ks5SAWLgKrE9YsLwTp5 Bawlrr6/xwqxaQ6TxO93LWAJTgFHidUzZrCC2IwCYhLfT61hglglLnHryXwmiJMFJJbsOc8M YYtKvHz8D+xKUQE9iTX3wyDCihIfX+1jhGjVk7gxdQrUxdYS39+tY4ewtSWWLXzNDHGPoMTJ mU9YJjCKz0KybRaS9llI2mchaZ+FpH0BI+sqRtHi1OLi3HQjY73Uoszk4uL8PL281JJNjMDo O7jlt+4OxtWvHQ8xCnAwKvHwPljGFCHEmlhWXJl7iFGCg1lJhHfqYZYIId6UxMqq1KL8+KLS nNTiQ4zSHCxK4rxmK++HCwmkJ5akZqemFqQWwWSZODilGhiZcz4Wfvv48fi9JRudLnJ4LGZ5 365y/GrtnneV1Rej5bYdTN7tI3xIyvjzI585KQ3r4ngmeXBayL45rXX+4NKgikNKZT8PF8Zm Nze8EvwZJ/Zli2OH9ZsuqTv2Ok9qdKc+4n+2vSOYc9rb4F/uRYfempyfab7EZPriQxsSDNjY LcrPPreLZDikxFKckWioxVxUnAgAoF7ryLoCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Q5wJu69b6ZcDa8vSqy9S8pV3oss>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2016 12:36:34 -0000

Hi,

Would the following work:

- BUNDLE defines how to associate received RTP packets with an m- line
- JSET defines how to associate m- lines with RtpReceivers

In that case, BUNDLE would define the generic associate-with-m-line rules,
while JSEP defines the WebRTC specifics.

Regards,

Christer


On 17/10/16 12:50, "Colin Perkins" <csp@csperkins.org> wrote:

>> On 14 Oct 2016, at 08:54, Magnus Westerlund
>><magnus.westerlund@ericsson.com> wrote:
>>=20
>> Den 2016-10-13 kl. 18:01, skrev Christer Holmberg:
>>> However, Magnus told me it=B9s not needed, so I=B9d like to get some in=
put
>>> from him.
>>>=20
>>> *From:*Cullen Jennings [mailto:fluffy@iii.ca]
>>> That looks about right for RTP but I think it is still missing stuff
>>>for
>>> RTCP handling. Here is the current text we did for JSEP. I prefer the
>>> style in which you described it compared to the algorithm style below
>>> but I think this might help figure out what to write for RTCP.
>>>=20
>>=20
>> I dislike the algorithmic description JSEP has because it inserts
>>itself at position in the stack where I would not myself implement the
>>binding handling. The implementations of RTP stacks I have made have
>>never let the full RTCP packets be available to the application layer.
>>It has only implemented event and request based interface to provide the
>>triggers and data associated with the differnet RTCP packets. Thus, from
>>my perspective the routing of the RTCP packets becomes a question if the
>>SSRC is bound to the right m=3D. Then handel the received RTCP packets in
>>that context.
>>=20
>> So what might be a suitable RTCP clarification regarding RTCP would be
>>the following.
>>=20
>> Simply add RTCP in the following sentence:
>>=20
>> "Later, when an offerer or answerer receives an RTP packet that does
>>not carry the identification-tag, it can associate the packet with the
>> correct "m=3D" line using the SSRC value."
>>=20
>> so that it reads:
>>=20
>> "Later, when an offerer or answerer receives an RTP or RTCP packet that
>>does not carry the identification-tag, it can associate the packet with
>>the correct "m=3D" line using the SSRC value."
>>=20
>> Regarding the second paragraph. If the association has been done
>>according to this part then also the RTCP packets has an association. If
>>an RTCP packet arrives with a non associated SSRC, then many RTCP
>>packets type can still be processed and the information stored in the
>>SSRC related information table. Some that are application interaction
>>related, like some of the feedback messages can of course not be handled.
>>=20
>> One very important aspect here is that the basic RTCP processing do
>>need to occur for also non-associated SSRCs. This to ensure that the
>>sender get the RTCP feedback information for congestion control
>>purposes. We want the transport layer functions to continue function,
>>even if the application can't consume the packets.
>>=20
>> Thus, I would consider that the "the packet SHOULD be dropped." needs
>>an addition that says after having been processed as received by the
>>RTCP layer. If we don't report them as received we skew the congestion
>>control information, and it will make any coupled congestion controller
>>that looks at the set of RTP streams being emitted take the wrong
>>decision. I also assumes that a lack of association is in most cases a
>>temporary issue that will be resolved by the regular transmissions.
>
>I agree with all of this. The mapping shouldn=B9t be from RTP or RTCP
>packets onto RtpRecivers. The RTP protocol requires RTP and RTCP packets
>be associated to an SSRC, and the mapping is to determine what=B9s the rol=
e
>of that SSRC (i.e., to map from SSRC to RtpReceiver).
>
>
>--=20
>Colin Perkins
>https://csperkins.org/
>
>
>
>


From nobody Mon Oct 17 06:49:35 2016
Return-Path: <thomass.stach@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 2BF3812967F for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 06:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 SpFUgtvwu4B2 for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 06:49:32 -0700 (PDT)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (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 075B912967D for <mmusic@ietf.org>; Mon, 17 Oct 2016 06:49:31 -0700 (PDT)
Received: by mail-lf0-x22e.google.com with SMTP id x79so295978658lff.0 for <mmusic@ietf.org>; Mon, 17 Oct 2016 06:49:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=gNoyOgGeCu9+sV20DJvlhiLS93b0ozFhTJmJPkHr6TQ=; b=RcsGFLqUoIGKBe8h+H7sW2EdUjfqN67r/HzyB6o/yTC9tOlMMjOCQdjf8/i5h3/Ijh +KNwNV0ZAx7mraFdtYnsJpv19z//PH7mK2G3fQPEdMXDwHquFbJepwZkjEg52lNu1FZR VofMhWvcXiP8FNYwGlvitYszzuZ1tQnpv4NOIDYZ/cGsgKEvsX8gVFnUbGmIyVOIgr4m KZ7nobU71DLA0cttUFHmcNQWpXZXOVAwUCpIbdDDBkdnRPdv4Is5uBE8UHYm/7Ctv1n9 pQrJaVWhxXlY0sLu95J8H9LBev2PlE56RqD8rF+rz4absUs7S4j87g+67FO6pacni7Rn 17Ew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=gNoyOgGeCu9+sV20DJvlhiLS93b0ozFhTJmJPkHr6TQ=; b=b7OeDdKP5+6PwnRB9aoJkrZG1ACmamG29glC4UzjBPSoNz7yMpuD6UixcfwjaxBg2E OvqegmOZeOoYKrSzBS9k5v7GgF3fZsbsCNMvXb70cw/1d2VeJxWlvY1sj8zfA0YaxIUR Ek1T6MYUbwy1Ju5VmEEk85IDg/lb1ik2wJBLHBRd3HVRh1Nhy9DyUkbXzCJHRmdoBEug wxDcJZ+vvyAmp0FEW7uKFgIKl6EpKZPry9ESHr96q0bRxFSeLUynfxj2jxHuaGbBRacj N5SE2hnath+2Qum6wNhNulK6vb9e0F6UgJR6M+l4hr8EjDy3eGyjg+YYe3N2uc0V7AFN WiRA==
X-Gm-Message-State: AA6/9RmsvGkFjErSt45yC6K/QX12Qf++GQUqi/PVrL8UWavu0yl/4kgXts5M2OP5wAPMsg==
X-Received: by 10.25.217.209 with SMTP id s78mr12707655lfi.8.1476712168959; Mon, 17 Oct 2016 06:49:28 -0700 (PDT)
Received: from [192.168.2.111] (d91-130-252-149.cust.tele2.at. [91.130.252.149]) by smtp.googlemail.com with ESMTPSA id f27sm7830745lji.24.2016.10.17.06.49.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Oct 2016 06:49:28 -0700 (PDT)
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <D41AC393.10727%christer.holmberg@ericsson.com> <bc713d1a-acdb-af95-5391-b3e244e1126d@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1B3B2@ESESSMB209.ericsson.se> <e44e62ff-1b0d-9180-2872-b98c84cbb6f6@gmail.com> <D4226F4E.10D4F%christer.holmberg@ericsson.com> <7c516d72-ef2a-e928-dc4a-ee77298ebb22@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD668A9@ESESSMB209.ericsson.se> <e22f8a1a-00f6-8c87-5a4e-8c1e6dfa75b2@gmail.com> <D42A7012.1139C%christer.holmberg@ericsson.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <7f03bb7b-f896-5238-a869-8ec16bd77f4a@gmail.com>
Date: Mon, 17 Oct 2016 15:49:27 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <D42A7012.1139C%christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/oh2MhLAeUNu-uiKr4z6BF9mMp_o>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2016 13:49:34 -0000

inline


On 2016-10-17 11:17, Christer Holmberg wrote:
> Hi,
>
>>>>>>>>>> It has been suggested that removal of candidates should not be
>>>>>>>>>> part of trickle, but rather be defined in a separate future
>>>>>>>>>> extension draft.
>>>>>>>>>> The comments below are based on that such "extension" may exist
>>>>>>>>>> at
>>>>>>>>>> some point.
>>>>>>>>>>
>>>>>>>>>> The text in section 4.2 says:
>>>>>>>>>>         "In every INFO request agents MUST include all local
>>>>>>>>>>         candidates they have signaled previously.  This is
>>>>>>>>>> necessary in order to
>>>>>>>>>>         more easily avoid problems that would arise from
>>>>>>>>>> unreliable transports.  Mis-
>>>>>>>>>>         ordering can be detected through the CSeq: header field
>>>>>>>>>> in the INFO
>>>>>>>>>>         request.  As a consequence candidates cannot be removed
>>>>>>>>>> unless an ICE
>>>>>>>>>>         restart is performed.  Note that extension might be
>>>>>>>>>> specified in the
>>>>>>>>>>         future that enable such removal without a restart."
>>>>>>>>>> Q1: Assuming someone does define an extension which allows
>>>>>>>>>> removal
>>>>>>>>>> of candidates without a restart, do such candidates still have to
>>>>>>>>>> be included in the INFO, as they have been "previously
>>>>>>>>>> signalled"?
>>>>>>>>> This would have to clarified in that future extension document
>>>>>>>>> together with corresponding backward compatibility issues and/or
>>>>>>>>> indication of support for such an extension. I don't want to do
>>>>>>>>> design here, but a=ice-options might be something to look at.
>>>>>>>> How you indicate support of such extension is outside the scope of
>>>>>>>> this thread. I want to clarify the exact semantics of a candidate
>>>>>>>> in an INFO.
>>>>>> Again, I agree that how candidates are removed is outside the scope.
>>>>>> But, that doesnÂ¹t change the fact that trickle needs to define
>>>>>> exactly
>>>>>> what the semantic of the signalled candidates. I do NOT want a future
>>>>>> extension to change that semantic.
>>>> I don't how you want to preclude an arbitrary future extension to do
>>>> such a change,
>>>> but in case of a "candidate removal" extension I don't see a problem
>>>> with the current >concept.
>>>> The current concept is (as I understand it):
>>>> - An INFO always carries all candidates that belong to the currently
>>>> valid ufrag/pwd.
>>> But that is not what the text is saying. "That belong" is not the same
>>> as "Previously signalled". "That belong" means they are still
>>> valid/active - at least in my ears.
>> Taking into account that draft-ice-trickle does not provide  any
>> mechanism for removal in my ears both sound the same -  currently that is.
>> Would then changing  "... Previously signalled ..." to "That belong" in
>> the body of draft-mmusic-trickle-ice-sdp be fine then?
> Letâ€™s talk about a mechanism that DOES exist: continous consent.
>
> According to RFC 7675, if consent is lost for specific candidates an ICE
> re-start is required in order to use the candidate pair.
>
> So, before such ICE re-start occur, why should we keep signalling such
> candidates in INFOs?
Now I'm lost.
Can you please explain what 7675 has to do with the INFO messages from 
Trickle-ICE?
These INFOs are used during the early dialog phase of the session in 
order to get the candidates exchanged until end-of-candidates is received.
7675 comes into the game  after a candidate pair is nominated and the 
dialog is confirmed.
> Also note that 7675 defines a mechanism to explicitly signal that consent
> has been removed. Whether we call that â€œremoval of candidateâ€� or not can
> be discussed, but why should such candidates continue to be signalled?
The signalling of candidates has long finished at that point.
> ...
>
>
>>> Even if we don't have a defined mechanism for removing candidates, they
>>> can disappear anyway. The TURN server may crash, etc.
>> Would that be detected via the failed connectivity checks?
> Yes. Or, if coninous consent is used, when consent expires.
>
>
>>> Why should we keep signalling such candidates?
>> I doesn't do any harm. Section 4.2 specifies that only new candidates
>> are relayed to the ICE agent.
>>> We could of course do an ICE re-start whenever a candidate is removed
>>> (one way or another), but I don't think we want to do that...
>> Probably not, but that is the way that Trickle-ICE inherited from 5245.
>>> But, again, by ONLY signalling the added candidates we don't have the
>>> issue with removed candidates to begin with.
>> There  will certainly be other issues.
> Please present those issues so we can discuss them.
I'd rather wait until some elaborated text for your proposal appears and 
then start from there.
>>>> I still think that the current concept works, so will you want to ask
>>>> that then?
>>> I am asking as we speak. Anyone who does not agree with the suggestion
>>> should speak up :)
>> Nicely replied :)
>> However, it certainly takes more than silence to change the current
>> procedure in the document.
>> There needs to be explicit support for such a change from a larger
>> number of participants.
>> I also believe that we first need to see some elaborated text that deals
>> with issues like reordering and other corner cases.
>>
>> The current concept is mature and I also showed a path how it could be
>> extended to deal with candidate removal.
>> So, I don't see a need to change, especially considering that we were
>> asked to get things finished rather quickly.
>
> I assume we are also asked to get things finished properly :)
Which we certainly will do.

Regards
Thomas
>
> Regards,
>
> Christer
>


From nobody Mon Oct 17 07:34:45 2016
Return-Path: <juergen.stoetzer-bradler@nokia.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 0AF191297A7 for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 07:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level: 
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ZjSCJVUXC8TS for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 07:34:39 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 0537C1297A5 for <mmusic@ietf.org>; Mon, 17 Oct 2016 07:34:38 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id BC8FB9E61F86B for <mmusic@ietf.org>; Mon, 17 Oct 2016 14:34:33 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u9HEYZPL000339 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <mmusic@ietf.org>; Mon, 17 Oct 2016 14:34:36 GMT
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u9HEYU34024763 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mmusic@ietf.org>; Mon, 17 Oct 2016 16:34:35 +0200
Received: from [135.224.211.131] (135.239.27.38) by FR711WXCHHUB02.zeu.alcatel-lucent.com (135.239.2.112) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 17 Oct 2016 16:34:33 +0200
To: <mmusic@ietf.org>
References: <19028e81-8f2e-090f-7cdf-5d942382d393@cisco.com>
From: Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@nokia.com>
Message-ID: <61de1624-08ed-8d64-55d2-3b385c7d4eca@nokia.com>
Date: Mon, 17 Oct 2016 16:34:32 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <19028e81-8f2e-090f-7cdf-5d942382d393@cisco.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms010408090104080004090906"
X-Originating-IP: [135.239.27.38]
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xXEbgzSfv0-kaJrGN0USmbJ7gok>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2016 14:34:42 -0000

--------------ms010408090104080004090906
Content-Type: multipart/alternative;
 boundary="------------37F62CA6FE3B0CB6766B6D6F"

This is a multi-part message in MIME format.
--------------37F62CA6FE3B0CB6766B6D6F
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Hello,

Have re-read the whole text and would have some comments as follows.

Thanks,
Juergen

* Section 3, terminology: The "SCTP transport address" is mentioned. Woul=
d this still be needed in=20
the draft, given that SCTP-over-IP is now out of scope?

* Sec 4.1: The paragraph right after the "m=3D" line mentions the 'UDP' a=
nd 'TCP' proto values. As far=20
as I see the UDP related proto value is IANA registered only with lower c=
ase letters, 'udp'. Would=20
therefore propose to replace 'UDP' with 'udp'.

* Sec 5.1: The last sentence specifies: "Usage of the SDP 'sctp-port' att=
ribute with other proto=20
values is not specified, and MUST be discarded if received." On the other=
 hand, section 6.1 (within=20
the note) mentions for the "max-message-size" attribute that "Usage of th=
e attribute with other=20
proto values needs to be defined in a separate specification." In section=
 5.1, should this draft=20
actually require the "sctp-port" attribute being discarded if associated =
with m-line with proto=20
values other than UDP/DTLS/SCTP or TCP/DTLS/SCTP? As per my understanding=
 it would actually be up to=20
the (other) document(s), which specify such other proto values. (Especial=
ly as SCTP-over-IP is not=20
within the scope anymore.)

* Sec 6.1: This section introduces the "max-message-size" attribute and s=
pecifies: "The attribute=20
can be associated with an m- line to indicate the maximum message size (i=
ndicated in bytes) that an=20
SCTP endpoint is willing to receive on the SCTP association associated wi=
th the m-line."
Would propose to explicitly add "... to indicate the maximum SCTP user me=
ssage size ...".=20
Admittedly, it seems pretty clear in the given context that "message size=
" refers to the "SCTP user=20
message size". However, explicitly adding "SCTP user" might help to unamb=
iguously differentiate this=20
message size  from e.g. the maximum DTLS payload size, or from applicatio=
n level protocol message=20
sizes (like e.g. MSRP message sizes or MSRP message chunk sizes). Similar=
ly, Would propose to extend=20
the first sentence of the second paragraph like "... must assume that lar=
ger SCTP user messages ...".

  * Sections 9 and 10: I am still struggling with the usages of "re-estab=
lishment" / "re-establish"=20
/ "re-established".
These terms are used several times in sections 9 and 10.
For me in (almost) all cases these usages seem to refer to a situation, w=
here a _new_ SCTP=20
association (or DTLS association or TCP connection) is (to be) establishe=
d either _after_ a previous=20
corresponding association or connection had been closed, or which is mean=
t to replace a previously=20
established and still existing association or connection. In a way I am q=
uite generally unsure what=20
exactly the notion of "re-establishment" means in such situations. For me=
 a "re-establishment" e.g.=20
of an SCTP association would be a concept where an SCTP association is es=
tablished, where it then=20
fails, and where it is then established again with the same transport add=
ress (or here SCTP port)=20
values. However, even in this case, strictly speaking, a new SCTP associa=
tion is actually=20
established, which replaces the old one. But at least in case where new t=
ransport protocol=20
parameters (like new SCTP ports) are used, I cannot really think of a "re=
-establishment". For me=20
this would always be an "establishment of a new" association.
Given that I'd actually like to propose avoiding the term "re-establishme=
nt" (and its various=20
grammatical derivatives) as much a possible.

* Sec 15.3: This creates the new IANA registry of the "fmt" values for th=
e UDP/DTLS/SCTP and=20
TCP/DTLS/SCTP proto values. And it introduces the "fmt" value "webrtc-dat=
achannel". In the table the=20
reference to draft-ietf-rtcweb-data-protocol is given. But that draft doe=
sn't introduce any SDP=20
information elements, especially not this "fmt" value. As per my understa=
nding the present=20
draft-ietf-mmusic-sctp-sdp itself introduces the "fmt" value "webrtc-data=
channel". Would therefore=20
propose to replace "draft-ietf-rtcweb-data-protocol" with "draft-ietf-mmu=
sic-sctp-sdp".



On 11.10.2016 20:53, Flemming Andreasen wrote:
> Greetings MMUSIC
>
> This is to announce a 2 week WGLC on the draft:
>
>     https://www.ietf.org/id/draft-ietf-mmusic-sctp-sdp-18.txt
>
> as Proposed Standard. Please review and provide any comments you may ha=
ve on the document by=20
> Tuesday, October 25, 2016. Comments should be sent to the document auth=
ors and the MMUSIC WG list.=20
> 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


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

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    Hello,<br>
    <br>
    Have re-read the whole text and would have some comments as follows.<=
br>
    <br>
    Thanks,<br>
    Juergen<br>
    <br>
    * Section 3, terminology: The "SCTP transport address" is mentioned.
    Would this still be needed in the draft, given that SCTP-over-IP is
    now out of scope?<br>
    <br>
    * Sec 4.1: The paragraph right after the "m=3D" line mentions the
    'UDP' and 'TCP' proto values. As far as I see the UDP related proto
    value is IANA registered only with lower case letters, 'udp'. Would
    therefore propose to replace 'UDP' with 'udp'.<br>
    <br>
    * Sec 5.1: The last sentence specifies: "Usage of the SDP
    'sctp-port' attribute with other proto values is not specified, and
    MUST be discarded if received." On the other hand, section 6.1
    (within the note) mentions for the "max-message-size" attribute that
    "Usage of the attribute with other proto values needs to be defined
    in a separate specification." In section 5.1, should this draft
    actually require the "sctp-port" attribute being discarded if
    associated with m-line with proto values other than UDP/DTLS/SCTP or
    TCP/DTLS/SCTP? As per my understanding it would actually be up to
    the (other) document(s), which specify such other proto values.
    (Especially as SCTP-over-IP is not within the scope anymore.)<br>
    <br>
    * Sec 6.1: This section introduces the "max-message-size" attribute
    and specifies: "The attribute can be associated with an m- line to
    indicate the maximum message size (indicated in bytes) that an SCTP
    endpoint is willing to receive on the SCTP association associated
    with the m-line."<br>
    Would propose to explicitly add "... to indicate the maximum SCTP
    user message size ...". Admittedly, it seems pretty clear in the
    given context that "message size" refers to the "SCTP user message
    size". However, explicitly adding "SCTP user" might help to
    unambiguously differentiate this message size=C2=A0 from e.g. the max=
imum
    DTLS payload size, or from application level protocol message sizes
    (like e.g. MSRP message sizes or MSRP message chunk sizes).
    Similarly, Would propose to extend the first sentence of the second
    paragraph like "... must assume that larger SCTP user messages ...".<=
br>
    <br>
    =C2=A0* Sections 9 and 10: I am still struggling with the usages of
    "re-establishment" / "re-establish" / "re-established".<br>
    These terms are used several times in sections 9 and 10.<br>
    For me in (almost) all cases these usages seem to refer to a
    situation, where a _new_ SCTP association (or DTLS association or
    TCP connection) is (to be) established either _after_ a previous
    corresponding association or connection had been closed, or which is
    meant to replace a previously established and still existing
    association or connection. In a way I am quite generally unsure what
    exactly the notion of "re-establishment" means in such situations.
    For me a "re-establishment" e.g. of an SCTP association would be a
    concept where an SCTP association is established, where it then
    fails, and where it is then established again with the same
    transport address (or here SCTP port) values. However, even in this
    case, strictly speaking, a new SCTP association is actually
    established, which replaces the old one. But at least in case where
    new transport protocol parameters (like new SCTP ports) are used, I
    cannot really think of a "re-establishment". For me this would
    always be an "establishment of a new" association.<br>
    Given that I'd actually like to propose avoiding the term
    "re-establishment" (and its various grammatical derivatives) as much
    a possible. <br>
    <br>
    * Sec 15.3: This creates the new IANA registry of the "fmt" values
    for the UDP/DTLS/SCTP and TCP/DTLS/SCTP proto values. And it
    introduces the "fmt" value "webrtc-datachannel". In the table the
    reference to draft-ietf-rtcweb-data-protocol is given. But that
    draft doesn't introduce any SDP information elements, especially not
    this "fmt" value. As per my understanding the present
    draft-ietf-mmusic-sctp-sdp itself introduces the "fmt" value
    "webrtc-datachannel". Would therefore propose to replace
    "draft-ietf-rtcweb-data-protocol" with "draft-ietf-mmusic-sctp-sdp".<=
br>
    <br>
    <br>
    <div class=3D"moz-cite-prefix">On 11.10.2016 20:53, Flemming Andrease=
n
      wrote:<br>
    </div>
    <blockquote
      cite=3D"mid:%3C19028e81-8f2e-090f-7cdf-5d942382d393@cisco.com%3E"
      type=3D"cite">Greetings MMUSIC
      <br>
      <br>
      This is to announce a 2 week WGLC on the draft:
      <br>
      <br>
      =C2=A0=C2=A0=C2=A0 <a class=3D"moz-txt-link-freetext" href=3D"https=
://www.ietf.org/id/draft-ietf-mmusic-sctp-sdp-18.txt">https://www.ietf.or=
g/id/draft-ietf-mmusic-sctp-sdp-18.txt</a>
      <br>
      <br>
      as Proposed Standard. Please review and provide any comments you
      may have on the document by Tuesday, October 25, 2016. 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>
      _______________________________________________
      <br>
      mmusic mailing list
      <br>
      <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:mmusic@ietf.or=
g">mmusic@ietf.org</a>
      <br>
      <a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mai=
lman/listinfo/mmusic">https://www.ietf.org/mailman/listinfo/mmusic</a>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------37F62CA6FE3B0CB6766B6D6F--

--------------ms010408090104080004090906
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
DF8wggTdMIIDxaADAgECAgoanQrOAAAAAAAGMA0GCSqGSIb3DQEBBQUAMEMxFzAVBgNVBAoT
DkFsY2F0ZWwgTHVjZW50MSgwJgYDVQQDEx9BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBSb290
IENBMB4XDTA4MTEyMTIxNTcyOFoXDTE4MTEyMTIyMDcyOFowgYUxEzARBgoJkiaJk/IsZAEZ
FgNjb20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcw
FQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJu
YWwgU3ViIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2Ocmcli3LbVU6TRh
+JLMtquBr5/grS+gzfN5YL/lauFCHmDlF7kNQvxtDWqwNpOkzb97CwWcVsdfkyWAiGzVWeRI
rYGhK/xNPFRYXOKYXLGqxFWkltZkYpSRudHzjTneUC4EVdMXnREMu8FTC0CM38VbxMvQ+ygj
Eyicg2QT9lZHWkKP9kCI1818P+AmS7905t6kXR9Q2m1GjcCa0KqARPGX/xe2toQS+VdiUwDa
ry1Enk8j19KFmvFg1bhY2mNSHgzN2AWnhsOi/EID1SalzBwHylByB/UbbEv2dZUsAdMuOtYt
Z/8dM1axS0d3fW7q7mAYV5uM42mYX9o1B/RzjwIDAQABo4IBjjCCAYowDwYDVR0TAQH/BAUw
AwEB/zAdBgNVHQ4EFgQU2exrvZZYIvfYpnfN/k2B77qXvRIwCwYDVR0PBAQDAgHGMBAGCSsG
AQQBgjcVAQQDAgEAMBkGCSsGAQQBgjcUAgQMHgoAUwB1AGIAQwBBMB8GA1UdIwQYMBaAFAes
slr2YYl8XHzr4pcnKWkMih/wMHgGA1UdHwRxMG8wbaBroGmGOWh0dHA6Ly9zZXJ2aWNlcy5z
dXBwb3J0LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kvcm9vdENBLmNybIYsaHR0cDovL3d3dy5h
bGNhdGVsLWx1Y2VudC5jb20vUEtJL3Jvb3RDQS5jcmwwgYIGCCsGAQUFBwEBBHYwdDA4Bggr
BgEFBQcwAoYsaHR0cDovL3d3dy5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3Jvb3RDQS5jcnQw
OAYIKwYBBQUHMAKGLGh0dHA6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9yb290Q0Eu
Y3J0MA0GCSqGSIb3DQEBBQUAA4IBAQClGxDp5Z1IDjIEz8VaTEWa8Q1OWUbXwsszdoNg5Gg3
F1a2VFFVegmsrpt4axbESlgE6AT/rkUUiyjbEhcUgY2OHdeKN5Gc7VOGh9D7SER9peARwSwx
4NYRrsIaRXDrUswWAM6T6ilDUogjKYk3uK2zZ6Vy7z3JewxVlhpeSsNPQSMoyNibKkYLRoh6
rvz94vB0mvcT0uVx7xowPNoTOjjGRAk4J/MBaNOupvwfRfPmwRetdnD6NC5x8aRkhr4ZNBjv
YxFT8IJaeLk8piQYMPRDlzi7dlb9d6C5WuC0LRpomk2r3bd6/XpNOx2FyG18axeeASWtENgP
vqEirM5MjwkCMIIHejCCBmKgAwIBAgIKYWH+JwAAAAFWdjANBgkqhkiG9w0BAQUFADCBhTET
MBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBmx1Y2VudDEUMBIGCgmSJomT
8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MScwJQYDVQQDEx5BbGNhdGVs
IEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0EwHhcNMTUwNTE4MTMwNzI0WhcNMTcwNTE3MTMwNzI0
WjBOMRAwDgYDVQQDEwdsaTYwNzYwMTowOAYJKoZIhvcNAQkBFitqdWVyZ2VuLnN0b2V0emVy
LWJyYWRsZXJAYWxjYXRlbC1sdWNlbnQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEA3SjiDDt1yolL0cBi5MS+Bea3hhVDSdcJ/xtfzEbTtkxo05xnMgeRTy/kNJZuR4oY
j/2TE+raQenSEgROQtLgxKjxtLh9/fGEuLCyFclz9SIeIYIkZBB1NSwZKmGlJHRU5jjqSinT
Hmux9chaP+TUoidoDYbfdz/uFGdPW7RP21Gxjzg9v/VC+tfc0u0idNF9Vwnkh3VgdisMf1Jf
JZNINpw0ZapFKRhLEhgtXVS7tkdxxTL0uc9XtviOTSSfxgBt2MPsj0qfhsNFFO4zUO1pJiBz
SBPnLt7af96oS2ZHI4Xz7zNHShDoSMMIr+7l9xgopb5qN/KMCMP9BSxxNEfphwIDAQABo4IE
IDCCBBwwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIhb3FWYPjsTmHpYEqhr/DQoWUmBmB
C/nmTIT9tVoCAWQCAQUwHwYDVR0lBBgwFgYKKwYBBAGCNwoDBAYIKwYBBQUHAwQwCwYDVR0P
BAQDAgWgMCkGCSsGAQQBgjcVCgQcMBowDAYKKwYBBAGCNwoDBDAKBggrBgEFBQcDBDBEBgkq
hkiG9w0BCQ8ENzA1MA4GCCqGSIb3DQMCAgIAgDAOBggqhkiG9w0DBAICAIAwBwYFKw4DAgcw
CgYIKoZIhvcNAwcwHQYDVR0OBBYEFEVmlcJSxtK5Cu7FZb5XUWWuKktKMB8GA1UdIwQYMBaA
FNnsa72WWCL32KZ3zf5Nge+6l70SMIIBXQYDVR0fBIIBVDCCAVAwggFMoIIBSKCCAUSGgdls
ZGFwOi8vL0NOPUFsY2F0ZWwlMjBMdWNlbnQlMjBJbnRlcm5hbCUyMFN1YiUyMENBLENOPXVz
bmF2c3BraTAzcCxDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2Vydmlj
ZXMsQ049Q29uZmlndXJhdGlvbixEQz1sdWFkLERDPWx1Y2VudCxEQz1jb20/Y2VydGlmaWNh
dGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNSTERpc3RyaWJ1dGlvblBvaW50
hixodHRwczovL3d3dy5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3N1YkNBLmNybIY4aHR0cDov
L3NlcnZpY2VzLnN1cHBvcnQuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9zdWJDQS5jcmwwggFh
BggrBgEFBQcBAQSCAVMwggFPMIHMBggrBgEFBQcwAoaBv2xkYXA6Ly8vQ049QWxjYXRlbCUy
MEx1Y2VudCUyMEludGVybmFsJTIwU3ViJTIwQ0EsQ049QUlBLENOPVB1YmxpYyUyMEtleSUy
MFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9bHVhZCxEQz1sdWNl
bnQsREM9Y29tP2NBQ2VydGlmaWNhdGU/YmFzZT9vYmplY3RDbGFzcz1jZXJ0aWZpY2F0aW9u
QXV0aG9yaXR5MDgGCCsGAQUFBzAChixodHRwczovL3d3dy5hbGNhdGVsLWx1Y2VudC5jb20v
UEtJL3N1YkNBLmNydDBEBggrBgEFBQcwAoY4aHR0cDovL3NlcnZpY2VzLnN1cHBvcnQuYWxj
YXRlbC1sdWNlbnQuY29tL1BLSS9zdWJDQS5jcnQwNgYDVR0RBC8wLYEranVlcmdlbi5zdG9l
dHplci1icmFkbGVyQGFsY2F0ZWwtbHVjZW50LmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAMrtX
ZAqm6NqOAYttJjvC6pL04tEKUusax1Dr6p6NfxVfUuW8ZoFXKoxHEDaYKQR9ldfnuILHN+x7
KdLeKg+NPUs7GFGwpBmJb7PRmxnIarFJbGHzpqZ9+Fhsde1uxi+y2VJcIOVaEh/JoRdHvSUQ
nwT4+FcBmS6uRv68rnCkh+KeUm6A7+6dDo/9l/Zh2Hu1+HVWw5kEH/xmO170v9Xef7efxzxv
BeQ644kvErDNG26LJDUtOqaKTdz9KKZXngw+2cAV/4Kc7C9xdT29Ugm8oOK/ecqBliMhBUen
WphsEDjIbKJCd40RJLKb+v49EN/IJogNDd81vtehOxDw5Lus4zGCA+0wggPpAgEBMIGUMIGF
MRMwEQYKCZImiZPyLGQBGRYDY29tMRYwFAYKCZImiZPyLGQBGRYGbHVjZW50MRQwEgYKCZIm
iZPyLGQBGRYEbmEwMjEXMBUGA1UEChMOQWxjYXRlbCBMdWNlbnQxJzAlBgNVBAMTHkFsY2F0
ZWwgTHVjZW50IEludGVybmFsIFN1YiBDQQIKYWH+JwAAAAFWdjANBglghkgBZQMEAgEFAKCC
AikwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTYxMDE3MTQz
NDMyWjAvBgkqhkiG9w0BCQQxIgQgpfWXCwxnqyypu868WzXjIgnLCQxyGksP7gHWAAsq/SQw
bAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMH
MA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIB
KDCBpQYJKwYBBAGCNxAEMYGXMIGUMIGFMRMwEQYKCZImiZPyLGQBGRYDY29tMRYwFAYKCZIm
iZPyLGQBGRYGbHVjZW50MRQwEgYKCZImiZPyLGQBGRYEbmEwMjEXMBUGA1UEChMOQWxjYXRl
bCBMdWNlbnQxJzAlBgNVBAMTHkFsY2F0ZWwgTHVjZW50IEludGVybmFsIFN1YiBDQQIKYWH+
JwAAAAFWdjCBpwYLKoZIhvcNAQkQAgsxgZeggZQwgYUxEzARBgoJkiaJk/IsZAEZFgNjb20x
FjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQK
Ew5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgU3Vi
IENBAgphYf4nAAAAAVZ2MA0GCSqGSIb3DQEBAQUABIIBAKQDCIFRfItc976Yfnp/JJfwIbvb
a5mexPlGoZABjyatcEvemXOa3liBlhUyzqJGb97IJf2EiA6dRs0XM9Zr4RMSSGIqO8mlfPz9
2YPTEn6GtjG8zcC1OqancBRj5FjVB8Pkmoe8dOdBUnCUzWCsuhVFopreE9HbF33V2BIHnkAM
tc18fJrAULtSSzPNoB74/hPlf9jkhuyLbJJHBt/hK48sq1W23Qzqk6CKSiaK2yLcN9BGpCuH
QmR3qVWKQKmiWlYHYSAscuw41baaKeV4doG0XdGFlZjgvf2fy1Yaq6sAbl8bbn/PIG6FUuXY
lbwg/AeG1obKj2lae4yaCz458jgAAAAAAAA=
--------------ms010408090104080004090906--


From nobody Mon Oct 17 10:04:23 2016
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 3E689129967 for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 10:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZNldN7ED8wIQ for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 10:04:21 -0700 (PDT)
Received: from resqmta-po-03v.sys.comcast.net (resqmta-po-03v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:162]) (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 4B4351298C3 for <mmusic@ietf.org>; Mon, 17 Oct 2016 10:04:21 -0700 (PDT)
Received: from resomta-po-04v.sys.comcast.net ([96.114.154.228]) by resqmta-po-03v.sys.comcast.net with SMTP id wBJSb46wnzd8UwBKlb8bJG; Mon, 17 Oct 2016 17:04:19 +0000
Received: from [192.168.1.110] ([73.186.127.100]) by resomta-po-04v.sys.comcast.net with SMTP id wBKkbCbRo872EwBKlbMsaj; Mon, 17 Oct 2016 17:04:19 +0000
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B4BD93F95@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <c72ee559-73f8-ad08-cf40-ff9acd7dabb6@alum.mit.edu>
Date: Mon, 17 Oct 2016 13:04:18 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD93F95@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfA4Ovppr5MNiJBI3+UNN3/vG7oc3MUuHhhI2QBZyYgQhnpbEaeQC8UVUbGeprYl0Q2PXRpCs1pNSRaQqayT/sZ7i8YJoGdbUQ8WBJvVOUotWtHDb2Kmj EIVmTU40eIv80H7IZqjl3d6cd+i9Zjx25/oID1dWFdG1afwWA62cbpaMKNOci41p3mO6cwvI1eg2kw+UTy9rUD5qSUOFERKIGURQ3EbgOV8r2qsFMRtffWUS
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MNo5hcZfrVF7BMPFW_Vzy_5WMNc>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Paul's review
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2016 17:04:22 -0000

Sounds good. You had one question:

On 10/15/16 5:18 PM, Christer Holmberg wrote:

> * Section 6.2:
>
>> Rather than restate the general syntax of an attribute, please just define the parts that are unique to this attribute, in the style introduced in RFC4566bis. E.g.,
>>
>>    Name: max-message-size
>>
>>    Value: max-message-size-value
>>
>>    Usage Level: media
>>
>>    Charset Dependent: no
>>
>>    Mux Category: SPECIAL
>>
>>    Syntax:
>>
>>          max-message-size-value = 1*40<DIGIT defined in RFC4566>
>>          *** Did you really want *40* here? ***
>
> I don't remember where the number came from.
>
> Any suggestion would be a reasonable number? Do we need to set a limit? As far as I remember, the standard does not define a max size.

I was thinking that this value is negotiable in DCEP, and if so that 
would have a field size that would limit this. But I can't find that in 
DCEP. So I guess it probably is fundamentally an SCTP issue. Somebody 
must know.

(I see that you went with simply '1*' in your update. That works 
syntactically, but I think it is worthwhile to resolve what the range of 
values is.

	Thanks,
	Paul


From nobody Mon Oct 17 10:27:36 2016
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 49709129973 for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 10:27:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 HUfFNdQK6Q5C for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 10:27:35 -0700 (PDT)
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 A685D129680 for <mmusic@ietf.org>; Mon, 17 Oct 2016 10:27:34 -0700 (PDT)
X-AuditID: c1b4fb25-14bff7000000793b-c1-58050a03498c
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by  (Symantec Mail Security) with SMTP id 01.F4.31035.30A05085; Mon, 17 Oct 2016 19:27:32 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0319.002; Mon, 17 Oct 2016 19:27:31 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Paul's review
Thread-Index: AdImVRUqaKFns7OmSde3fBN3KRdtxQCMqZoAAATwRXA=
Date: Mon, 17 Oct 2016 17:27:30 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BDAB581@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B4BD93F95@ESESSMB209.ericsson.se> <c72ee559-73f8-ad08-cf40-ff9acd7dabb6@alum.mit.edu>
In-Reply-To: <c72ee559-73f8-ad08-cf40-ff9acd7dabb6@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM2J7uC4LF2uEwbwVNhZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJXx6oZhwRf2in9Te5kbGH+zdjFyckgImEjs P7OIBcQWEljPKNE+SaKLkQvIXswo8fJ3B1ARBwebgIVE9z9tkBoRAV+JZ49vs4HYwgLeEkeu H2SEiPtIHJ+zhBXCtpJYd/0CmM0ioCpx4e8jsHpeoN5r798xQ8xvZpT4sXcpO0iCU8BB4tOr r2A2o4CYxPdTa5hAbGYBcYlbT+YzQRwqILFkz3lmCFtU4uXjf1APKEk0LnnCClGvI7Fg9yc2 CFtbYtnC18wQiwUlTs58wjKBUWQWkrGzkLTMQtIyC0nLAkaWVYyixanFSbnpRsZ6qUWZycXF +Xl6eaklmxiB0XBwy2/VHYyX3zgeYhTgYFTi4U24yRIhxJpYVlyZe4hRgoNZSYSX/w9QiDcl sbIqtSg/vqg0J7X4EKM0B4uSOK/ZyvvhQgLpiSWp2ampBalFMFkmDk6pBkZWWa3UZZu6vePb gnTD27XenWfoXRR/9/uO8MgwpVv/3z89wSb0O0yjafnM94tmm6RGZOpm66meeLJn/zb5rdUm r3q+SAZsu9a2NfTXdq4bjYtars9gVtpbscHPOF3xtdjDOuXDYgUOPrsc1/TkFnYfN17tuiNp 9s2c8K9f/6Z9qA2ue7dt3WElluKMREMt5qLiRAA5HQdyggIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/X4rXsXkyZ94lU4m6XCTDyzWP2XI>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Paul's review
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2016 17:27:36 -0000

Hi,

...

>>>    Syntax:
>>>
>>>          max-message-size-value =3D 1*40<DIGIT defined in RFC4566>
>>>          *** Did you really want *40* here? ***
>>
>> I don't remember where the number came from.
>>
>> Any suggestion would be a reasonable number? Do we need to set a limit? =
As far as I remember, the standard does not define a max size.
>
> I was thinking that this value is negotiable in DCEP, and if so that woul=
d have a field size that would limit this. But
> I can't find that in DCEP. So I guess it probably is fundamentally an SCT=
P issue. Somebody must know.
>
> (I see that you went with simply '1*' in your update. That works syntacti=
cally, but I think it is worthwhile to resolve what the range of values is.

I was googling around a little, and as far as I know the SCTP standard does=
 not define a max size. There may of course be other factors that limit the=
 max size - which is why we define a way to indicate it to begin with :)

Regards,

Christer


From nobody Mon Oct 17 11:20:59 2016
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 09AF9129457 for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 11:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 PjdpIXII_Qm5 for <mmusic@ietfa.amsl.com>; Mon, 17 Oct 2016 11:20:56 -0700 (PDT)
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 3FAE212943B for <mmusic@ietf.org>; Mon, 17 Oct 2016 11:20:56 -0700 (PDT)
X-AuditID: c1b4fb30-b87ff70000000cb2-b0-58051686cd3f
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by  (Symantec Mail Security) with SMTP id 32.23.03250.68615085; Mon, 17 Oct 2016 20:20:54 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0319.002; Mon, 17 Oct 2016 20:20:53 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@nokia.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Juergen's comments
Thread-Index: AdIon9o9oFJtOTTCTq+gCP2Z1PlXow==
Date: Mon, 17 Oct 2016 18:20:52 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BDAB88D@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUyM2K7pW6bGGuEQfMyLYuzT1YwWkxd/pjF gcljyZKfTB53b11iCmCK4rJJSc3JLEst0rdL4Mpo/9HLWHDPuGLOm9MsDYxbjLoYOTkkBEwk Pqy9yNjFyMUhJLCeUeLElB3MEM5iRokdc2azdTFycLAJWEh0/9MGaRARyJDYc/8wM4gtLBAk sWbmd0aIeLDEutU72CFsPYkZU5aC1bAIqEocOPwIrIZXwFfifvt9VhCbUUBM4vupNUwgNrOA uMStJ/OZIA4SkFiy5zwzhC0q8fLxP1YIW0micckTVpBzmAU0Jdbv0odoVZSY0v2QHWK8oMTJ mU9YJjAKzUIydRZCxywkHbOQdCxgZFnFKFqcWpyUm25kpJdalJlcXJyfp5eXWrKJERjaB7f8 NtjB+PK54yFGAQ5GJR7ehJssEUKsiWXFlbmHGCU4mJVEeAuFWSOEeFMSK6tSi/Lji0pzUosP MUpzsCiJ85qtvB8uJJCeWJKanZpakFoEk2Xi4JRqYPR+vma9/uIlsfevH1Iy2zehVvxXhALH siUZXMpry34usYjVinz8//oNzsdmZesnOTP+WyKhOX3Vo3vnwwU/f528vOGtUbyDc/1OsWMm Z47OnvdVbNqEcnPJ09JFXjc3GpbociayMKsHv/udYHb7g71VjPyGT2dZFA9adTzSedjoLr9+ acqHOWVKLMUZiYZazEXFiQCL7Cx4aQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wnGOvwqOsvIvJi8P5Fjz_GGQHQw>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Juergen's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2016 18:20:58 -0000

SGkgSnVlcmdlbiwNCg0KVGhhbmtzIGZvciB5b3VyIGNvbW1lbnRzISBQbGVhc2Ugc2VlIGlubGlu
ZS4NCg0KPiogU2VjdGlvbiAzLCB0ZXJtaW5vbG9neTogVGhlICJTQ1RQIHRyYW5zcG9ydCBhZGRy
ZXNzIiBpcyBtZW50aW9uZWQuIFdvdWxkIHRoaXMgc3RpbGwgYmUgDQo+IG5lZWRlZCBpbiB0aGUg
ZHJhZnQsIGdpdmVuIHRoYXQgU0NUUC1vdmVyLUlQIGlzIG5vdyBvdXQgb2Ygc2NvcGU/DQoNCkkg
dGhpbmsgd2UgY2FuIHJlbW92ZSBpdC4NCg0KDQo+KiBTZWMgNC4xOiBUaGUgcGFyYWdyYXBoIHJp
Z2h0IGFmdGVyIHRoZSAibT0iIGxpbmUgbWVudGlvbnMgdGhlICdVRFAnIGFuZCAnVENQJyBwcm90
byB2YWx1ZXMuIA0KPkFzIGZhciBhcyBJIHNlZSB0aGUgVURQIHJlbGF0ZWQgcHJvdG8gdmFsdWUg
aXMgSUFOQSByZWdpc3RlcmVkIG9ubHkgd2l0aCBsb3dlciBjYXNlIGxldHRlcnMsICd1ZHAnLiAN
Cj5Xb3VsZCB0aGVyZWZvcmUgcHJvcG9zZSB0byByZXBsYWNlICdVRFAnIHdpdGggJ3VkcCcuDQoN
Ck5vdGUgdGhhdCBkcmFmdC1pZXRmLWJmY3BiaXMtcmZjNDU4M2Jpcy0xNi50eHQgZGVmaW5lcyBz
aW1pbGFyIHZhbHVlcyBmb3IgQkZDUCwgd2l0aCB1cHBlciBjYXNlIGxldHRlcnMuDQoNCkknZCBw
cmVmZXIgdG8ga2VlcCB0aGUgdXBwZXIgY2FzZS4gSXQgbG9va3MgYmV0dGVyIHRoYXQgd2F5Lg0K
DQoNCj4gKiBTZWMgNS4xOiBUaGUgbGFzdCBzZW50ZW5jZSBzcGVjaWZpZXM6ICJVc2FnZSBvZiB0
aGUgU0RQICdzY3RwLXBvcnQnIGF0dHJpYnV0ZSB3aXRoIG90aGVyIHByb3RvIHZhbHVlcw0KPiBp
cyBub3Qgc3BlY2lmaWVkLCBhbmQgTVVTVCBiZSBkaXNjYXJkZWQgaWYgcmVjZWl2ZWQuIiBPbiB0
aGUgb3RoZXIgaGFuZCwgc2VjdGlvbiA2LjEgKHdpdGhpbiB0aGUgbm90ZSkgDQo+IG1lbnRpb25z
IGZvciB0aGUgIm1heC1tZXNzYWdlLXNpemUiIGF0dHJpYnV0ZSB0aGF0ICJVc2FnZSBvZiB0aGUg
YXR0cmlidXRlIHdpdGggb3RoZXIgcHJvdG8gdmFsdWVzIA0KPiBuZWVkcyB0byBiZSBkZWZpbmVk
IGluIGEgc2VwYXJhdGUgc3BlY2lmaWNhdGlvbi4iIEluIHNlY3Rpb24gNS4xLCBzaG91bGQgdGhp
cyBkcmFmdCBhY3R1YWxseSByZXF1aXJlIHRoZSANCj4gInNjdHAtcG9ydCIgYXR0cmlidXRlIGJl
aW5nIGRpc2NhcmRlZCBpZiBhc3NvY2lhdGVkIHdpdGggbS1saW5lIHdpdGggcHJvdG8gdmFsdWVz
IG90aGVyIHRoYW4gDQo+IFVEUC9EVExTL1NDVFAgb3IgVENQL0RUTFMvU0NUUD8gQXMgcGVyIG15
IHVuZGVyc3RhbmRpbmcgaXQgd291bGQgYWN0dWFsbHkgYmUgdXAgdG8gdGhlIChvdGhlcikgDQo+
IGRvY3VtZW50KHMpLCB3aGljaCBzcGVjaWZ5IHN1Y2ggb3RoZXIgcHJvdG8gdmFsdWVzLiAoRXNw
ZWNpYWxseSBhcyBTQ1RQLW92ZXItSVAgaXMgbm90IHdpdGhpbiB0aGUgc2NvcGUgYW55bW9yZS4p
DQoNCkkgZ3Vlc3MgSSBjb3VsZCByZXBsYWNlIHRoZSB0ZXh0IGluIHNlY3Rpb24gNS4xIHdpdGgg
YSBzaW1pbGFyIG5vdGUuDQoNCg0KPiogU2VjIDYuMTogVGhpcyBzZWN0aW9uIGludHJvZHVjZXMg
dGhlICJtYXgtbWVzc2FnZS1zaXplIiBhdHRyaWJ1dGUgYW5kIHNwZWNpZmllczogIlRoZSBhdHRy
aWJ1dGUgY2FuIGJlIGFzc29jaWF0ZWQNCj4gd2l0aCBhbiBtLSBsaW5lIHRvIGluZGljYXRlIHRo
ZSBtYXhpbXVtIG1lc3NhZ2Ugc2l6ZSAoaW5kaWNhdGVkIGluIGJ5dGVzKSB0aGF0IGFuIFNDVFAg
ZW5kcG9pbnQgaXMgd2lsbGluZyB0byByZWNlaXZlDQo+IG9uIHRoZSBTQ1RQIGFzc29jaWF0aW9u
IGFzc29jaWF0ZWQgd2l0aCB0aGUgbS1saW5lLiINCj4gV291bGQgcHJvcG9zZSB0byBleHBsaWNp
dGx5IGFkZCAiLi4uIHRvIGluZGljYXRlIHRoZSBtYXhpbXVtIFNDVFAgdXNlciBtZXNzYWdlIHNp
emUgLi4uIi4gQWRtaXR0ZWRseSwgaXQgc2VlbXMgcHJldHR5IA0KPiBjbGVhciBpbiB0aGUgZ2l2
ZW4gY29udGV4dCB0aGF0ICJtZXNzYWdlIHNpemUiIHJlZmVycyB0byB0aGUgIlNDVFAgdXNlciBt
ZXNzYWdlIHNpemUiLiBIb3dldmVyLCBleHBsaWNpdGx5IGFkZGluZyAiU0NUUCB1c2VyIiANCj4g
bWlnaHQgaGVscCB0byB1bmFtYmlndW91c2x5IGRpZmZlcmVudGlhdGUgdGhpcyBtZXNzYWdlIHNp
emXCoCBmcm9tIGUuZy4gdGhlIG1heGltdW0gRFRMUyBwYXlsb2FkIHNpemUsIG9yIGZyb20gYXBw
bGljYXRpb24gDQo+IGxldmVsIHByb3RvY29sIG1lc3NhZ2Ugc2l6ZXMgKGxpa2UgZS5nLiBNU1JQ
IG1lc3NhZ2Ugc2l6ZXMgb3IgTVNSUCBtZXNzYWdlIGNodW5rIHNpemVzKS4gU2ltaWxhcmx5LCBX
b3VsZCBwcm9wb3NlIHRvIGV4dGVuZA0KPiB0aGUgZmlyc3Qgc2VudGVuY2Ugb2YgdGhlIHNlY29u
ZCBwYXJhZ3JhcGggbGlrZSAiLi4uIG11c3QgYXNzdW1lIHRoYXQgbGFyZ2VyIFNDVFAgdXNlciBt
ZXNzYWdlcyAuLi4iLg0KDQpJJ2xsIG1vZGlmeSBhcyBzdWdnZXN0ZWQsIGJ5IGFkZGluZyAidXNl
ciIuDQoNCj7CoCogU2VjdGlvbnMgOSBhbmQgMTA6IEkgYW0gc3RpbGwgc3RydWdnbGluZyB3aXRo
IHRoZSB1c2FnZXMgb2YgInJlLWVzdGFibGlzaG1lbnQiIC8gInJlLWVzdGFibGlzaCIgLyAicmUt
ZXN0YWJsaXNoZWQiLg0KPlRoZXNlIHRlcm1zIGFyZSB1c2VkIHNldmVyYWwgdGltZXMgaW4gc2Vj
dGlvbnMgOSBhbmQgMTAuDQoNCldoaWxlIGl0IG1heSBub3QgYmUgcmVsYXRlZCB0byB5b3VyIGlz
c3VlLCBwbGVhc2Ugbm90ZSB0aGUgcHVsbCByZXF1ZXN0IHdoaWNoIG1vZGlmaWVzIHNlY3Rpb25z
IDkgYW5kIDEwIHF1aXRlIGEgYml0Lg0KDQo+Rm9yIG1lIGluIChhbG1vc3QpIGFsbCBjYXNlcyB0
aGVzZSB1c2FnZXMgc2VlbSB0byByZWZlciB0byBhIHNpdHVhdGlvbiwgd2hlcmUgYSBfbmV3XyBT
Q1RQIGFzc29jaWF0aW9uDQo+IChvciBEVExTIGFzc29jaWF0aW9uIG9yIFRDUCBjb25uZWN0aW9u
KSBpcyAodG8gYmUpIGVzdGFibGlzaGVkIGVpdGhlciBfYWZ0ZXJfIGEgcHJldmlvdXMgY29ycmVz
cG9uZGluZyANCj4gYXNzb2NpYXRpb24gb3IgY29ubmVjdGlvbiBoYWQgYmVlbiBjbG9zZWQsIG9y
IHdoaWNoIGlzIG1lYW50IHRvIHJlcGxhY2UgYSBwcmV2aW91c2x5IGVzdGFibGlzaGVkIGFuZCAN
Cj4gc3RpbGwgZXhpc3RpbmcgYXNzb2NpYXRpb24gb3IgY29ubmVjdGlvbi4gSW4gYSB3YXkgSSBh
bSBxdWl0ZSBnZW5lcmFsbHkgdW5zdXJlIHdoYXQgZXhhY3RseSB0aGUgbm90aW9uIA0KPiBvZiAi
cmUtZXN0YWJsaXNobWVudCIgbWVhbnMgaW4gc3VjaCBzaXR1YXRpb25zLiBGb3IgbWUgYSAicmUt
ZXN0YWJsaXNobWVudCIgZS5nLiBvZiBhbiBTQ1RQIGFzc29jaWF0aW9uIA0KPiB3b3VsZCBiZSBh
IGNvbmNlcHQgd2hlcmUgYW4gU0NUUCBhc3NvY2lhdGlvbiBpcyBlc3RhYmxpc2hlZCwgd2hlcmUg
aXQgdGhlbiBmYWlscywgYW5kIHdoZXJlIGl0IGlzIHRoZW4gDQo+IGVzdGFibGlzaGVkIGFnYWlu
IHdpdGggdGhlIHNhbWUgdHJhbnNwb3J0IGFkZHJlc3MgKG9yIGhlcmUgU0NUUCBwb3J0KSB2YWx1
ZXMuIEhvd2V2ZXIsIGV2ZW4gaW4gdGhpcyANCj4gY2FzZSwgc3RyaWN0bHkgc3BlYWtpbmcsIGEg
bmV3IFNDVFAgYXNzb2NpYXRpb24gaXMgYWN0dWFsbHkgZXN0YWJsaXNoZWQsIHdoaWNoIHJlcGxh
Y2VzIHRoZSBvbGQgb25lLiANCj4gQnV0IGF0IGxlYXN0IGluIGNhc2Ugd2hlcmUgbmV3IHRyYW5z
cG9ydCBwcm90b2NvbCBwYXJhbWV0ZXJzIChsaWtlIG5ldyBTQ1RQIHBvcnRzKSBhcmUgdXNlZCwg
SSBjYW5ub3QgDQo+IHJlYWxseSB0aGluayBvZiBhICJyZS1lc3RhYmxpc2htZW50Ii4gRm9yIG1l
IHRoaXMgd291bGQgYWx3YXlzIGJlIGFuICJlc3RhYmxpc2htZW50IG9mIGEgbmV3IiBhc3NvY2lh
dGlvbi4NCj4gR2l2ZW4gdGhhdCBJJ2QgYWN0dWFsbHkgbGlrZSB0byBwcm9wb3NlIGF2b2lkaW5n
IHRoZSB0ZXJtICJyZS1lc3RhYmxpc2htZW50IiAoYW5kIGl0cyB2YXJpb3VzIGdyYW1tYXRpY2Fs
IA0KPiBkZXJpdmF0aXZlcykgYXMgbXVjaCBhIHBvc3NpYmxlLiANCg0KSSBoZWFyIHdoYXQgeW91
IGFyZSBzYXlpbmcsIGFuZCBJJ2xsIHNlZSB3aGF0IEkgY2FuIGRvLg0KDQoNCj4qIFNlYyAxNS4z
OiBUaGlzIGNyZWF0ZXMgdGhlIG5ldyBJQU5BIHJlZ2lzdHJ5IG9mIHRoZSAiZm10IiB2YWx1ZXMg
Zm9yIHRoZSBVRFAvRFRMUy9TQ1RQIGFuZCBUQ1AvRFRMUy9TQ1RQIHByb3RvIA0KPiB2YWx1ZXMu
IEFuZCBpdCBpbnRyb2R1Y2VzIHRoZSAiZm10IiB2YWx1ZSAid2VicnRjLWRhdGFjaGFubmVsIi4g
SW4gdGhlIHRhYmxlIHRoZSByZWZlcmVuY2UgdG8gZHJhZnQtaWV0Zi1ydGN3ZWItZGF0YS1wcm90
b2NvbCANCj4gaXMgZ2l2ZW4uIEJ1dCB0aGF0IGRyYWZ0IGRvZXNuJ3QgaW50cm9kdWNlIGFueSBT
RFAgaW5mb3JtYXRpb24gZWxlbWVudHMsIGVzcGVjaWFsbHkgbm90IHRoaXMgImZtdCIgdmFsdWUu
IEFzIHBlciBteSANCj4gdW5kZXJzdGFuZGluZyB0aGUgcHJlc2VudCBkcmFmdC1pZXRmLW1tdXNp
Yy1zY3RwLXNkcCBpdHNlbGYgaW50cm9kdWNlcyB0aGUgImZtdCIgdmFsdWUgIndlYnJ0Yy1kYXRh
Y2hhbm5lbCIuIFdvdWxkIA0KPiB0aGVyZWZvcmUgcHJvcG9zZSB0byByZXBsYWNlICJkcmFmdC1p
ZXRmLXJ0Y3dlYi1kYXRhLXByb3RvY29sIiB3aXRoICJkcmFmdC1pZXRmLW1tdXNpYy1zY3RwLXNk
cCIuDQoNCkkgaGVhciB3aGF0IHlvdSBhcmUgc2F5aW5nLg0KDQpCdXQsIEkgdGhpbmsgd2Ugc29t
ZXdoZXJlIG5lZWQgdG8gaGF2ZSBhIHJlZmVyZW5jZSB0byBkcmFmdC1pZXRmLXJ0Y3dlYi1kYXRh
LXByb3RvY29sLCBiZWNhdXNlIG90aGVyd2lzZSByZWFkZXJzIGhhdmUgbm8gY2x1ZSB3aGF0IHRo
ZSB2YWx1ZSBpcyB1c2VkIGZvci4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQo=


From nobody Tue Oct 18 01:41:03 2016
Return-Path: <juergen.stoetzer-bradler@nokia.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 A92BA129997 for <mmusic@ietfa.amsl.com>; Tue, 18 Oct 2016 01:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level: 
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 4ceODi0VyBVy for <mmusic@ietfa.amsl.com>; Tue, 18 Oct 2016 01:40:57 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 26C551299C4 for <mmusic@ietf.org>; Tue, 18 Oct 2016 01:40:57 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id E09CB92EB63A0; Tue, 18 Oct 2016 08:40:53 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u9I8etI0028830 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 18 Oct 2016 08:40:55 GMT
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u9I8enXO005024 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Oct 2016 10:40:54 +0200
Received: from [135.224.206.149] (135.239.27.39) by FR711WXCHHUB02.zeu.alcatel-lucent.com (135.239.2.112) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 18 Oct 2016 10:40:46 +0200
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B4BDAB88D@ESESSMB209.ericsson.se>
From: Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@nokia.com>
Message-ID: <9f4d2ce6-b3c5-aba8-0fb6-91b118152dcc@nokia.com>
Date: Tue, 18 Oct 2016 10:40:44 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BDAB88D@ESESSMB209.ericsson.se>
Content-Type: multipart/alternative; boundary="------------C6E8A80C4266B11A33E56D1A"
X-Originating-IP: [135.239.27.39]
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/aNP_ekF1efO5r7Xir9yDuXK3hvY>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Juergen's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Oct 2016 08:41:00 -0000

--------------C6E8A80C4266B11A33E56D1A
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi Christer,

Thanks for your feedback.
I've added some additional remarks below.

Best regards,
Juergen


On 17.10.2016 20:20, Christer Holmberg wrote:
>
>> * Sec 4.1: The paragraph right after the "m=3D" line mentions the 'UDP=
' and 'TCP' proto values.
>> As far as I see the UDP related proto value is IANA registered only wi=
th lower case letters, 'udp'.
>> Would therefore propose to replace 'UDP' with 'udp'.
> Note that draft-ietf-bfcpbis-rfc4583bis-16.txt defines similar values f=
or BFCP, with upper case letters.
>
> I'd prefer to keep the upper case. It looks better that way.
[Juergen] Ok. I see your point.

>
>>   * Sections 9 and 10: I am still struggling with the usages of "re-es=
tablishment" / "re-establish" / "re-established".
>> These terms are used several times in sections 9 and 10.
> While it may not be related to your issue, please note the pull request=
 which modifies sections 9 and 10 quite a bit.
>
>> For me in (almost) all cases these usages seem to refer to a situation=
, where a _new_ SCTP association
>> (or DTLS association or TCP connection) is (to be) established either =
_after_ a previous corresponding
>> association or connection had been closed, or which is meant to replac=
e a previously established and
>> still existing association or connection. In a way I am quite generall=
y unsure what exactly the notion
>> of "re-establishment" means in such situations. For me a "re-establish=
ment" e.g. of an SCTP association
>> would be a concept where an SCTP association is established, where it =
then fails, and where it is then
>> established again with the same transport address (or here SCTP port) =
values. However, even in this
>> case, strictly speaking, a new SCTP association is actually establishe=
d, which replaces the old one.
>> But at least in case where new transport protocol parameters (like new=
 SCTP ports) are used, I cannot
>> really think of a "re-establishment". For me this would always be an "=
establishment of a new" association.
>> Given that I'd actually like to propose avoiding the term "re-establis=
hment" (and its various grammatical
>> derivatives) as much a possible.
> I hear what you are saying, and I'll see what I can do.
[Juergen] Just had a look at sections 9 and 10 of your pull request. The =
changes look fine to me.
Regarding the usage of "re-establishment", I am not native English speake=
r. Thus I realize that I=20
better be careful here.
It is just that this term so far for me has always been associated with t=
he concept of "restoration=20
of something or some state, which previously had already been there and w=
hich then had vanished at=20
some point in the past".

>
>> * Sec 15.3: This creates the new IANA registry of the "fmt" values for=
 the UDP/DTLS/SCTP and TCP/DTLS/SCTP proto
>> values. And it introduces the "fmt" value "webrtc-datachannel". In the=
 table the reference to draft-ietf-rtcweb-data-protocol
>> is given. But that draft doesn't introduce any SDP information element=
s, especially not this "fmt" value. As per my
>> understanding the present draft-ietf-mmusic-sctp-sdp itself introduces=
 the "fmt" value "webrtc-datachannel". Would
>> therefore propose to replace "draft-ietf-rtcweb-data-protocol" with "d=
raft-ietf-mmusic-sctp-sdp".
> I hear what you are saying.
>
> But, I think we somewhere need to have a reference to draft-ietf-rtcweb=
-data-protocol, because otherwise readers have no clue what the value is =
used for.
[Juergen] I see your point and quite agree that draft-ietf-rtcweb-data-pr=
otocol should also be=20
referenced. Would it be acceptable to reference both drafts?
(draft-ietf-rtcweb-data-protocol defining the protocol stack and procedur=
es to be used on the media=20
plane and "webrtc-datachannel" being the associated SDP <fmt> value to be=
 used in related SDP=20
m-lines as introduced in draft-ietf-mmusic-sctp-sdp.)


--------------C6E8A80C4266B11A33E56D1A
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Christer,<br>
    <br>
    Thanks for your feedback.<br>
    I've added some additional remarks below.<br>
    <br>
    Best regards,<br>
    Juergen<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 17.10.2016 20:20, Christer Holmberg
      wrote:<br>
    </div>
    <blockquote
cite="mid:7594FB04B1934943A5C02806D1A2204B4BDAB88D@ESESSMB209.ericsson.se"
      type="cite"><br>
      <blockquote type="cite">
        <pre wrap="">* Sec 4.1: The paragraph right after the "m=" line mentions the 'UDP' and 'TCP' proto values. 
As far as I see the UDP related proto value is IANA registered only with lower case letters, 'udp'. 
Would therefore propose to replace 'UDP' with 'udp'.
</pre>
      </blockquote>
      <pre wrap="">
Note that draft-ietf-bfcpbis-rfc4583bis-16.txt defines similar values for BFCP, with upper case letters.

I'd prefer to keep the upper case. It looks better that way.</pre>
    </blockquote>
    [Juergen] Ok. I see your point.<br>
    <br>
    <blockquote
cite="mid:7594FB04B1934943A5C02806D1A2204B4BDAB88D@ESESSMB209.ericsson.se"
      type="cite"><br>
      <blockquote type="cite">
        <pre wrap="">Â * Sections 9 and 10: I am still struggling with the usages of "re-establishment" / "re-establish" / "re-established".
These terms are used several times in sections 9 and 10.
</pre>
      </blockquote>
      <pre wrap="">
While it may not be related to your issue, please note the pull request which modifies sections 9 and 10 quite a bit.

</pre>
      <blockquote type="cite">
        <pre wrap="">For me in (almost) all cases these usages seem to refer to a situation, where a _new_ SCTP association
(or DTLS association or TCP connection) is (to be) established either _after_ a previous corresponding 
association or connection had been closed, or which is meant to replace a previously established and 
still existing association or connection. In a way I am quite generally unsure what exactly the notion 
of "re-establishment" means in such situations. For me a "re-establishment" e.g. of an SCTP association 
would be a concept where an SCTP association is established, where it then fails, and where it is then 
established again with the same transport address (or here SCTP port) values. However, even in this 
case, strictly speaking, a new SCTP association is actually established, which replaces the old one. 
But at least in case where new transport protocol parameters (like new SCTP ports) are used, I cannot 
really think of a "re-establishment". For me this would always be an "establishment of a new" association.
Given that I'd actually like to propose avoiding the term "re-establishment" (and its various grammatical 
derivatives) as much a possible. 
</pre>
      </blockquote>
      <pre wrap="">
I hear what you are saying, and I'll see what I can do.</pre>
    </blockquote>
    [Juergen] Just had a look at sections 9 and 10 of your pull request.
    The changes look fine to me.<br>
    Regarding the usage of "re-establishment", I am not native English
    speaker. Thus I realize that I better be careful here.<br>
    It is just that this term so far for me has always been associated
    with the concept of "restoration of something or some state, which
    previously had already been there and which then had vanished at
    some point in the past". <br>
    <br>
    <blockquote
cite="mid:7594FB04B1934943A5C02806D1A2204B4BDAB88D@ESESSMB209.ericsson.se"
      type="cite"><br>
      <blockquote type="cite">
        <pre wrap="">* Sec 15.3: This creates the new IANA registry of the "fmt" values for the UDP/DTLS/SCTP and TCP/DTLS/SCTP proto 
values. And it introduces the "fmt" value "webrtc-datachannel". In the table the reference to draft-ietf-rtcweb-data-protocol 
is given. But that draft doesn't introduce any SDP information elements, especially not this "fmt" value. As per my 
understanding the present draft-ietf-mmusic-sctp-sdp itself introduces the "fmt" value "webrtc-datachannel". Would 
therefore propose to replace "draft-ietf-rtcweb-data-protocol" with "draft-ietf-mmusic-sctp-sdp".
</pre>
      </blockquote>
      <pre wrap="">
I hear what you are saying.

But, I think we somewhere need to have a reference to draft-ietf-rtcweb-data-protocol, because otherwise readers have no clue what the value is used for.</pre>
    </blockquote>
    [Juergen] I see your point and quite agree that
    draft-ietf-rtcweb-data-protocol should also be referenced. Would it
    be acceptable to reference both drafts? <br>
    (draft-ietf-rtcweb-data-protocol defining the protocol stack and
    procedures to be used on the media plane and "webrtc-datachannel"
    being the associated SDP &lt;fmt&gt; value to be used in related SDP
    m-lines as introduced in draft-ietf-mmusic-sctp-sdp.)<br>
    <br>
  </body>
</html>

--------------C6E8A80C4266B11A33E56D1A--


From nobody Tue Oct 18 02:19:14 2016
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 423F71299CB for <mmusic@ietfa.amsl.com>; Tue, 18 Oct 2016 02:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 Hs9HwCXD9-fB for <mmusic@ietfa.amsl.com>; Tue, 18 Oct 2016 02:19:12 -0700 (PDT)
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 CBAC1129991 for <mmusic@ietf.org>; Tue, 18 Oct 2016 02:19:11 -0700 (PDT)
X-AuditID: c1b4fb30-b73ff70000000cb2-e8-5805e90c808d
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by  (Symantec Mail Security) with SMTP id A0.E3.03250.C09E5085; Tue, 18 Oct 2016 11:19:10 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0319.002; Tue, 18 Oct 2016 11:19:08 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@nokia.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Juergen's comments
Thread-Index: AdIon9o9oFJtOTTCTq+gCP2Z1PlXowAarLMAAAfeCwA=
Date: Tue, 18 Oct 2016 09:19:08 +0000
Message-ID: <D42BC513.11488%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B4BDAB88D@ESESSMB209.ericsson.se> <9f4d2ce6-b3c5-aba8-0fb6-91b118152dcc@nokia.com>
In-Reply-To: <9f4d2ce6-b3c5-aba8-0fb6-91b118152dcc@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_D42BC51311488christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprPIsWRmVeSWpSXmKPExsUyM2J7lC7fS9YIg4+fBCzOPlnBaDF1+WMW ByaPJUt+MnncvXWJKYApissmJTUnsyy1SN8ugStj5tqHjAW35Sq2zZjN2sA4XaqLkZNDQsBE Ytb/naxdjFwcQgLrGSX2nJjHBpIQEljMKDHht3IXIwcHm4CFRPc/bZCwiECGxJ77h5lBbGGB IInmBY2sEPFgiXWrd7BD2FYS09a9YwKxWQRUJU6ufAdWwytgLXFx71UWiF0NjBLXTx0Ea+AU sJXomrsYrIhRQEzi+6k1YM3MAuISt57MZ4I4VEBiyZ7zzBC2qMTLx/9YQW4TFdCTWHM/DCKs KLHzbDszRGuCxKpbK5gg9gpKnJz5hGUCo8gsJFNnISmbhaQMIm4g8f7cfGYIW1ti2cLXULa+ xMYvZxkhbGuJFZPfo6hZwMixilG0OLU4KTfdyEgvtSgzubg4P08vL7VkEyMw2g5u+W2wg/Hl c8dDjAIcjEo8vAk3WSKEWBPLiitzDzFKcDArifDmP2eNEOJNSaysSi3Kjy8qzUktPsQozcGi JM5rtvJ+uJBAemJJanZqakFqEUyWiYNTqoHRz7xW/7DHIq2W/KNh3t5bdJR8T7FqT3CbZCVj fXfGJrnFavP0176Mlzk9/XDzheUJvuGa90TmGPv1bp/C+nHilK/+j1ducTjf3l3uyxBoZ1eZ 4dr8/vTL9AMSTZs+XWE1WlPMu7Jt0u1AScWmyfvnvHbpO6Daln5R+qeP5tzifON7y56rFDkq sRRnJBpqMRcVJwIAc4KUW7ICAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/e6zRoXSuHsKHR_olmqNialCSDFw>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Juergen's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Oct 2016 09:19:13 -0000

--_000_D42BC51311488christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

=85


* Sec 15.3: This creates the new IANA registry of the "fmt" values for the =
UDP/DTLS/SCTP and TCP/DTLS/SCTP proto
values. And it introduces the "fmt" value "webrtc-datachannel". In the tabl=
e the reference to draft-ietf-rtcweb-data-protocol
is given. But that draft doesn't introduce any SDP information elements, es=
pecially not this "fmt" value. As per my
understanding the present draft-ietf-mmusic-sctp-sdp itself introduces the =
"fmt" value "webrtc-datachannel". Would
therefore propose to replace "draft-ietf-rtcweb-data-protocol" with "draft-=
ietf-mmusic-sctp-sdp".


I hear what you are saying.

But, I think we somewhere need to have a reference to draft-ietf-rtcweb-dat=
a-protocol, because otherwise readers have no clue what the value is used f=
or.

[Juergen] I see your point and quite agree that draft-ietf-rtcweb-data-prot=
ocol should also be referenced. Would it be acceptable to reference both dr=
afts?
(draft-ietf-rtcweb-data-protocol defining the protocol stack and procedures=
 to be used on the media plane and "webrtc-datachannel" being the associate=
d SDP <fmt> value to be used in related SDP m-lines as introduced in draft-=
ietf-mmusic-sctp-sdp.)


In the pull request both drafts are now referenced.

Regards,

Christer



--_000_D42BC51311488christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <D6F7969349E8E4429211A9323C55B9E6@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>=85</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
<div><br>
</div>
<blockquote type=3D"cite">
<pre wrap=3D"">* Sec 15.3: This creates the new IANA registry of the &quot;=
fmt&quot; values for the UDP/DTLS/SCTP and TCP/DTLS/SCTP proto=20
values. And it introduces the &quot;fmt&quot; value &quot;webrtc-datachanne=
l&quot;. In the table the reference to draft-ietf-rtcweb-data-protocol=20
is given. But that draft doesn't introduce any SDP information elements, es=
pecially not this &quot;fmt&quot; value. As per my=20
understanding the present draft-ietf-mmusic-sctp-sdp itself introduces the =
&quot;fmt&quot; value &quot;webrtc-datachannel&quot;. Would=20
therefore propose to replace &quot;draft-ietf-rtcweb-data-protocol&quot; wi=
th &quot;draft-ietf-mmusic-sctp-sdp&quot;.
</pre>
</blockquote>
<div>
<pre wrap=3D"">I hear what you are saying.

But, I think we somewhere need to have a reference to draft-ietf-rtcweb-dat=
a-protocol, because otherwise readers have no clue what the value is used f=
or.</pre>
</div>
[Juergen] I see your point and quite agree that draft-ietf-rtcweb-data-prot=
ocol should also be referenced. Would it be acceptable to reference both dr=
afts?
<br>
(draft-ietf-rtcweb-data-protocol defining the protocol stack and procedures=
 to be used on the media plane and &quot;webrtc-datachannel&quot; being the=
 associated SDP &lt;fmt&gt; value to be used in related SDP m-lines as intr=
oduced in draft-ietf-mmusic-sctp-sdp.)</div>
</div>
</span>
<div><br>
</div>
<div><br>
</div>
<div>In the pull request both drafts are now referenced.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div bgcolor=3D"#FFFFFF" text=3D"#000000"><br>
<br>
</div>
</div>
</span>
</body>
</html>

--_000_D42BC51311488christerholmbergericssoncom_--


From nobody Tue Oct 18 02:24:53 2016
Return-Path: <juergen.stoetzer-bradler@nokia.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 92025129991 for <mmusic@ietfa.amsl.com>; Tue, 18 Oct 2016 02:24:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level: 
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 hAXF1BHA_WLJ for <mmusic@ietfa.amsl.com>; Tue, 18 Oct 2016 02:24:50 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 C25CE129591 for <mmusic@ietf.org>; Tue, 18 Oct 2016 02:24:49 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 1E4DBDE2D8A52; Tue, 18 Oct 2016 09:24:46 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u9I9OlHd029899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 18 Oct 2016 09:24:47 GMT
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u9I9NxcF009913 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Oct 2016 11:24:46 +0200
Received: from [135.224.206.149] (135.239.27.39) by FR711WXCHHUB01.zeu.alcatel-lucent.com (135.239.2.111) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 18 Oct 2016 11:24:37 +0200
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B4BDAB88D@ESESSMB209.ericsson.se> <9f4d2ce6-b3c5-aba8-0fb6-91b118152dcc@nokia.com> <D42BC513.11488%christer.holmberg@ericsson.com>
From: Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@nokia.com>
Message-ID: <e8e76f20-1cc6-bf07-022e-b57fb40bde19@nokia.com>
Date: Tue, 18 Oct 2016 11:24:35 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <D42BC513.11488%christer.holmberg@ericsson.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms090405090509070500070700"
X-Originating-IP: [135.239.27.39]
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/kuwf6g5aBp_Z1rM5QfuK1b4g04k>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-sctp-sdp-18 - Juergen's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Oct 2016 09:24:52 -0000

--------------ms090405090509070500070700
Content-Type: multipart/alternative;
 boundary="------------294D803FB06642EB354BE2EB"

This is a multi-part message in MIME format.
--------------294D803FB06642EB354BE2EB
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi Christer,

Thanks! The updates in your today's pull request look all good to me.

Best regards,
Juergen

On 18.10.2016 11:19, Christer Holmberg wrote:
> Hi,
>
> =E2=80=A6
>
>> * Sec 15.3: This creates the new IANA registry of the "fmt" values for=
 the UDP/DTLS/SCTP and TCP/DTLS/SCTP proto
>> values. And it introduces the "fmt" value "webrtc-datachannel". In the=
 table the reference to draft-ietf-rtcweb-data-protocol
>> is given. But that draft doesn't introduce any SDP information element=
s, especially not this "fmt" value. As per my
>> understanding the present draft-ietf-mmusic-sctp-sdp itself introduces=
 the "fmt" value "webrtc-datachannel". Would
>> therefore propose to replace "draft-ietf-rtcweb-data-protocol" with "d=
raft-ietf-mmusic-sctp-sdp".
> I hear what you are saying.
>
> But, I think we somewhere need to have a reference to draft-ietf-rtcweb=
-data-protocol, because otherwise readers have no clue what the value is =
used for.
> [Juergen] I see your point and quite agree that draft-ietf-rtcweb-data-=
protocol should also be=20
> referenced. Would it be acceptable to reference both drafts?
> (draft-ietf-rtcweb-data-protocol defining the protocol stack and proced=
ures to be used on the=20
> media plane and "webrtc-datachannel" being the associated SDP <fmt> val=
ue to be used in related=20
> SDP m-lines as introduced in draft-ietf-mmusic-sctp-sdp.)
>
>
> In the pull request both drafts are now referenced.
>
> Regards,
>
> Christer
>
>


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

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    Hi Christer,<br>
    <br>
    Thanks! The updates in your today's pull request look all good to
    me.<br>
    <br>
    Best regards,<br>
    Juergen<br>
    <br>
    <div class=3D"moz-cite-prefix">On 18.10.2016 11:19, Christer Holmberg=

      wrote:<br>
    </div>
    <blockquote
      cite=3D"mid:D42BC513.11488%25christer.holmberg@ericsson.com"
      type=3D"cite">
      <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Du=
tf-8">
      <div>Hi,</div>
      <div><br>
      </div>
      <div>=E2=80=A6</div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <div>
          <div bgcolor=3D"#FFFFFF" text=3D"#000000">
            <div><br>
            </div>
            <blockquote type=3D"cite">
              <pre wrap=3D"">* Sec 15.3: This creates the new IANA regist=
ry of the "fmt" values for the UDP/DTLS/SCTP and TCP/DTLS/SCTP proto=20
values. And it introduces the "fmt" value "webrtc-datachannel". In the ta=
ble the reference to draft-ietf-rtcweb-data-protocol=20
is given. But that draft doesn't introduce any SDP information elements, =
especially not this "fmt" value. As per my=20
understanding the present draft-ietf-mmusic-sctp-sdp itself introduces th=
e "fmt" value "webrtc-datachannel". Would=20
therefore propose to replace "draft-ietf-rtcweb-data-protocol" with "draf=
t-ietf-mmusic-sctp-sdp".
</pre>
            </blockquote>
            <div>
              <pre wrap=3D"">I hear what you are saying.

But, I think we somewhere need to have a reference to draft-ietf-rtcweb-d=
ata-protocol, because otherwise readers have no clue what the value is us=
ed for.</pre>
            </div>
            [Juergen] I see your point and quite agree that
            draft-ietf-rtcweb-data-protocol should also be referenced.
            Would it be acceptable to reference both drafts?
            <br>
            (draft-ietf-rtcweb-data-protocol defining the protocol stack
            and procedures to be used on the media plane and
            "webrtc-datachannel" being the associated SDP &lt;fmt&gt;
            value to be used in related SDP m-lines as introduced in
            draft-ietf-mmusic-sctp-sdp.)</div>
        </div>
      </span>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>In the pull request both drafts are now referenced.</div>
      <div><br>
      </div>
      <div>Regards,</div>
      <div><br>
      </div>
      <div>Christer</div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <div>
          <div bgcolor=3D"#FFFFFF" text=3D"#000000"><br>
            <br>
          </div>
        </div>
      </span>
    </blockquote>
    <br>
  </body>
</html>

--------------294D803FB06642EB354BE2EB--

--------------ms090405090509070500070700
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
DF8wggTdMIIDxaADAgECAgoanQrOAAAAAAAGMA0GCSqGSIb3DQEBBQUAMEMxFzAVBgNVBAoT
DkFsY2F0ZWwgTHVjZW50MSgwJgYDVQQDEx9BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBSb290
IENBMB4XDTA4MTEyMTIxNTcyOFoXDTE4MTEyMTIyMDcyOFowgYUxEzARBgoJkiaJk/IsZAEZ
FgNjb20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcw
FQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJu
YWwgU3ViIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2Ocmcli3LbVU6TRh
+JLMtquBr5/grS+gzfN5YL/lauFCHmDlF7kNQvxtDWqwNpOkzb97CwWcVsdfkyWAiGzVWeRI
rYGhK/xNPFRYXOKYXLGqxFWkltZkYpSRudHzjTneUC4EVdMXnREMu8FTC0CM38VbxMvQ+ygj
Eyicg2QT9lZHWkKP9kCI1818P+AmS7905t6kXR9Q2m1GjcCa0KqARPGX/xe2toQS+VdiUwDa
ry1Enk8j19KFmvFg1bhY2mNSHgzN2AWnhsOi/EID1SalzBwHylByB/UbbEv2dZUsAdMuOtYt
Z/8dM1axS0d3fW7q7mAYV5uM42mYX9o1B/RzjwIDAQABo4IBjjCCAYowDwYDVR0TAQH/BAUw
AwEB/zAdBgNVHQ4EFgQU2exrvZZYIvfYpnfN/k2B77qXvRIwCwYDVR0PBAQDAgHGMBAGCSsG
AQQBgjcVAQQDAgEAMBkGCSsGAQQBgjcUAgQMHgoAUwB1AGIAQwBBMB8GA1UdIwQYMBaAFAes
slr2YYl8XHzr4pcnKWkMih/wMHgGA1UdHwRxMG8wbaBroGmGOWh0dHA6Ly9zZXJ2aWNlcy5z
dXBwb3J0LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kvcm9vdENBLmNybIYsaHR0cDovL3d3dy5h
bGNhdGVsLWx1Y2VudC5jb20vUEtJL3Jvb3RDQS5jcmwwgYIGCCsGAQUFBwEBBHYwdDA4Bggr
BgEFBQcwAoYsaHR0cDovL3d3dy5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3Jvb3RDQS5jcnQw
OAYIKwYBBQUHMAKGLGh0dHA6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9yb290Q0Eu
Y3J0MA0GCSqGSIb3DQEBBQUAA4IBAQClGxDp5Z1IDjIEz8VaTEWa8Q1OWUbXwsszdoNg5Gg3
F1a2VFFVegmsrpt4axbESlgE6AT/rkUUiyjbEhcUgY2OHdeKN5Gc7VOGh9D7SER9peARwSwx
4NYRrsIaRXDrUswWAM6T6ilDUogjKYk3uK2zZ6Vy7z3JewxVlhpeSsNPQSMoyNibKkYLRoh6
rvz94vB0mvcT0uVx7xowPNoTOjjGRAk4J/MBaNOupvwfRfPmwRetdnD6NC5x8aRkhr4ZNBjv
YxFT8IJaeLk8piQYMPRDlzi7dlb9d6C5WuC0LRpomk2r3bd6/XpNOx2FyG18axeeASWtENgP
vqEirM5MjwkCMIIHejCCBmKgAwIBAgIKYWH+JwAAAAFWdjANBgkqhkiG9w0BAQUFADCBhTET
MBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBmx1Y2VudDEUMBIGCgmSJomT
8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MScwJQYDVQQDEx5BbGNhdGVs
IEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0EwHhcNMTUwNTE4MTMwNzI0WhcNMTcwNTE3MTMwNzI0
WjBOMRAwDgYDVQQDEwdsaTYwNzYwMTowOAYJKoZIhvcNAQkBFitqdWVyZ2VuLnN0b2V0emVy
LWJyYWRsZXJAYWxjYXRlbC1sdWNlbnQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEA3SjiDDt1yolL0cBi5MS+Bea3hhVDSdcJ/xtfzEbTtkxo05xnMgeRTy/kNJZuR4oY
j/2TE+raQenSEgROQtLgxKjxtLh9/fGEuLCyFclz9SIeIYIkZBB1NSwZKmGlJHRU5jjqSinT
Hmux9chaP+TUoidoDYbfdz/uFGdPW7RP21Gxjzg9v/VC+tfc0u0idNF9Vwnkh3VgdisMf1Jf
JZNINpw0ZapFKRhLEhgtXVS7tkdxxTL0uc9XtviOTSSfxgBt2MPsj0qfhsNFFO4zUO1pJiBz
SBPnLt7af96oS2ZHI4Xz7zNHShDoSMMIr+7l9xgopb5qN/KMCMP9BSxxNEfphwIDAQABo4IE
IDCCBBwwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIhb3FWYPjsTmHpYEqhr/DQoWUmBmB
C/nmTIT9tVoCAWQCAQUwHwYDVR0lBBgwFgYKKwYBBAGCNwoDBAYIKwYBBQUHAwQwCwYDVR0P
BAQDAgWgMCkGCSsGAQQBgjcVCgQcMBowDAYKKwYBBAGCNwoDBDAKBggrBgEFBQcDBDBEBgkq
hkiG9w0BCQ8ENzA1MA4GCCqGSIb3DQMCAgIAgDAOBggqhkiG9w0DBAICAIAwBwYFKw4DAgcw
CgYIKoZIhvcNAwcwHQYDVR0OBBYEFEVmlcJSxtK5Cu7FZb5XUWWuKktKMB8GA1UdIwQYMBaA
FNnsa72WWCL32KZ3zf5Nge+6l70SMIIBXQYDVR0fBIIBVDCCAVAwggFMoIIBSKCCAUSGgdls
ZGFwOi8vL0NOPUFsY2F0ZWwlMjBMdWNlbnQlMjBJbnRlcm5hbCUyMFN1YiUyMENBLENOPXVz
bmF2c3BraTAzcCxDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2Vydmlj
ZXMsQ049Q29uZmlndXJhdGlvbixEQz1sdWFkLERDPWx1Y2VudCxEQz1jb20/Y2VydGlmaWNh
dGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNSTERpc3RyaWJ1dGlvblBvaW50
hixodHRwczovL3d3dy5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3N1YkNBLmNybIY4aHR0cDov
L3NlcnZpY2VzLnN1cHBvcnQuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9zdWJDQS5jcmwwggFh
BggrBgEFBQcBAQSCAVMwggFPMIHMBggrBgEFBQcwAoaBv2xkYXA6Ly8vQ049QWxjYXRlbCUy
MEx1Y2VudCUyMEludGVybmFsJTIwU3ViJTIwQ0EsQ049QUlBLENOPVB1YmxpYyUyMEtleSUy
MFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9bHVhZCxEQz1sdWNl
bnQsREM9Y29tP2NBQ2VydGlmaWNhdGU/YmFzZT9vYmplY3RDbGFzcz1jZXJ0aWZpY2F0aW9u
QXV0aG9yaXR5MDgGCCsGAQUFBzAChixodHRwczovL3d3dy5hbGNhdGVsLWx1Y2VudC5jb20v
UEtJL3N1YkNBLmNydDBEBggrBgEFBQcwAoY4aHR0cDovL3NlcnZpY2VzLnN1cHBvcnQuYWxj
YXRlbC1sdWNlbnQuY29tL1BLSS9zdWJDQS5jcnQwNgYDVR0RBC8wLYEranVlcmdlbi5zdG9l
dHplci1icmFkbGVyQGFsY2F0ZWwtbHVjZW50LmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAMrtX
ZAqm6NqOAYttJjvC6pL04tEKUusax1Dr6p6NfxVfUuW8ZoFXKoxHEDaYKQR9ldfnuILHN+x7
KdLeKg+NPUs7GFGwpBmJb7PRmxnIarFJbGHzpqZ9+Fhsde1uxi+y2VJcIOVaEh/JoRdHvSUQ
nwT4+FcBmS6uRv68rnCkh+KeUm6A7+6dDo/9l/Zh2Hu1+HVWw5kEH/xmO170v9Xef7efxzxv
BeQ644kvErDNG26LJDUtOqaKTdz9KKZXngw+2cAV/4Kc7C9xdT29Ugm8oOK/ecqBliMhBUen
WphsEDjIbKJCd40RJLKb+v49EN/IJogNDd81vtehOxDw5Lus4zGCA+0wggPpAgEBMIGUMIGF
MRMwEQYKCZImiZPyLGQBGRYDY29tMRYwFAYKCZImiZPyLGQBGRYGbHVjZW50MRQwEgYKCZIm
iZPyLGQBGRYEbmEwMjEXMBUGA1UEChMOQWxjYXRlbCBMdWNlbnQxJzAlBgNVBAMTHkFsY2F0
ZWwgTHVjZW50IEludGVybmFsIFN1YiBDQQIKYWH+JwAAAAFWdjANBglghkgBZQMEAgEFAKCC
AikwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTYxMDE4MDky
NDM1WjAvBgkqhkiG9w0BCQQxIgQgcUfr68ViUET85I9ClZuZKZkEYmGfKTs39JnZBr6kt9ww
bAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMH
MA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIB
KDCBpQYJKwYBBAGCNxAEMYGXMIGUMIGFMRMwEQYKCZImiZPyLGQBGRYDY29tMRYwFAYKCZIm
iZPyLGQBGRYGbHVjZW50MRQwEgYKCZImiZPyLGQBGRYEbmEwMjEXMBUGA1UEChMOQWxjYXRl
bCBMdWNlbnQxJzAlBgNVBAMTHkFsY2F0ZWwgTHVjZW50IEludGVybmFsIFN1YiBDQQIKYWH+
JwAAAAFWdjCBpwYLKoZIhvcNAQkQAgsxgZeggZQwgYUxEzARBgoJkiaJk/IsZAEZFgNjb20x
FjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQK
Ew5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgU3Vi
IENBAgphYf4nAAAAAVZ2MA0GCSqGSIb3DQEBAQUABIIBAAuBrTCFjOa91BuDU+bNDLRFboRn
N2NYBKgK+MUBNcZX+7prrqz0BhD/HW/VSe8U9G78zmzlhr+GNklqXrV/m3YSDe1gsou2pJdo
E32YXDSNpQdEgJkWHgTgMaSs+59LVyAX3fnA9KG/2+55Lr+oT7scz+m9W4xAC9+2nsXM4wtd
ry40ukfoofwOTu5EX9G/Z/k3xfa/ViLfTNyyrM6McWWuOfsjFI85caejlsn1Kbw1XzKULy7o
eLekll8fdn2j7m96G9t2LI+93EPgd3iQV7nRn0yGVzqdjbZ52SJMRnplv3P90Ef4EFRb3/su
/GZVyW1XNFbTGG3JstfBtA+jVSgAAAAAAAA=
--------------ms090405090509070500070700--


From nobody Tue Oct 18 03:21:03 2016
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 0E802129534 for <mmusic@ietfa.amsl.com>; Tue, 18 Oct 2016 03:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 F-iurEBesekM for <mmusic@ietfa.amsl.com>; Tue, 18 Oct 2016 03:21:00 -0700 (PDT)
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 F043E128B37 for <mmusic@ietf.org>; Tue, 18 Oct 2016 03:20:59 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-49-5805f78a67f2
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by  (Symantec Mail Security) with SMTP id AE.B6.02551.A87F5085; Tue, 18 Oct 2016 12:20:58 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0319.002; Tue, 18 Oct 2016 12:20:56 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Thomas Stach <thomass.stach@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
Thread-Index: AQHSHxIL5dxB//uBWky8GjwyA0+P66CZ76sAgAjKcACAAD99AIABlqsAgACw0bCABwPJgIAAPlIAgAAXs4CAAYxIAA==
Date: Tue, 18 Oct 2016 10:20:56 +0000
Message-ID: <D42BCBE2.1149C%christer.holmberg@ericsson.com>
References: <D41AC393.10727%christer.holmberg@ericsson.com> <bc713d1a-acdb-af95-5391-b3e244e1126d@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1B3B2@ESESSMB209.ericsson.se> <e44e62ff-1b0d-9180-2872-b98c84cbb6f6@gmail.com> <D4226F4E.10D4F%christer.holmberg@ericsson.com> <7c516d72-ef2a-e928-dc4a-ee77298ebb22@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD668A9@ESESSMB209.ericsson.se> <e22f8a1a-00f6-8c87-5a4e-8c1e6dfa75b2@gmail.com> <D42A7012.1139C%christer.holmberg@ericsson.com> <7f03bb7b-f896-5238-a869-8ec16bd77f4a@gmail.com>
In-Reply-To: <7f03bb7b-f896-5238-a869-8ec16bd77f4a@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <9E94F314DBB62A40A9289EBDDA5CDE7A@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCIsWRmVeSWpSXmKPExsUyM2K7q27Xd9YIg41vBC2mLn/MYvHpxFYm ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugStjS9cXxoIf5hU75q5hbmA8YNbFyMkhIWAi Mf/ZbqYuRi4OIYH1jBKXPuxlhXAWM0p0H57B3sXIwcEmYCHR/U8bpEFEIFDi85njYA3CAlMZ Ja6f7mOFSExjlHi61ArCzpJ4unI5O4jNIqAqcaL9NBuIzStgLTF7zmxGiAXLWCRaLv5kBVnA KWAr8f4UWC+jgJjE91NrmEBsZgFxiVtP5jNBXCogsWTPeWYIW1Ti5eN/YK2iAnoSa+6HQYQV JT6+2scI0aol8eXHPjYI21pi/dslULaixJTuh+wQ5whKnJz5hGUCo9gsJNtmIWmfhaR9FpL2 WUjaFzCyrmIULU4tLs5NNzLWSy3KTC4uzs/Ty0st2cQIjKuDW37r7mBc/drxEKMAB6MSD2/C TZYIIdbEsuLK3EOMEhzMSiK8q76yRgjxpiRWVqUW5ccXleakFh9ilOZgURLnNVt5P1xIID2x JDU7NbUgtQgmy8TBKdXAGMSfNmGTb4yULVfOJ7cVZy3PJqz4XikXde2zuN/zabns9Uta53e8 UxRaulVprudL9467mb3Jym1bA50ceqJUiqdnclay9E/K3nn863Q2Q7PpM08UMshufnJtq+Az lTDG1t32S+WeKOr879x7XyKP2+JCWPrUtdVthZl70mzYbirWbfJe3/pWiaU4I9FQi7moOBEA i45or6cCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/AlrHng-5nhqcOe0rqKoLEvVSSaY>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Oct 2016 10:21:02 -0000

SGkgVGhvbWFzLA0KDQo+Pj4+Pj4+Pj4+PiBJdCBoYXMgYmVlbiBzdWdnZXN0ZWQgdGhhdCByZW1v
dmFsIG9mIGNhbmRpZGF0ZXMgc2hvdWxkIG5vdCBiZQ0KPj4+Pj4+Pj4+Pj4gcGFydCBvZiB0cmlj
a2xlLCBidXQgcmF0aGVyIGJlIGRlZmluZWQgaW4gYSBzZXBhcmF0ZSBmdXR1cmUNCj4+Pj4+Pj4+
Pj4+IGV4dGVuc2lvbiBkcmFmdC4NCj4+Pj4+Pj4+Pj4+IFRoZSBjb21tZW50cyBiZWxvdyBhcmUg
YmFzZWQgb24gdGhhdCBzdWNoICJleHRlbnNpb24iIG1heSBleGlzdA0KPj4+Pj4+Pj4+Pj4gYXQN
Cj4+Pj4+Pj4+Pj4+IHNvbWUgcG9pbnQuDQo+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4gVGhlIHRl
eHQgaW4gc2VjdGlvbiA0LjIgc2F5czoNCj4+Pj4+Pj4+Pj4+ICAgICAgICAgIkluIGV2ZXJ5IElO
Rk8gcmVxdWVzdCBhZ2VudHMgTVVTVCBpbmNsdWRlIGFsbCBsb2NhbA0KPj4+Pj4+Pj4+Pj4gICAg
ICAgICBjYW5kaWRhdGVzIHRoZXkgaGF2ZSBzaWduYWxlZCBwcmV2aW91c2x5LiAgVGhpcyBpcw0K
Pj4+Pj4+Pj4+Pj4gbmVjZXNzYXJ5IGluIG9yZGVyIHRvDQo+Pj4+Pj4+Pj4+PiAgICAgICAgIG1v
cmUgZWFzaWx5IGF2b2lkIHByb2JsZW1zIHRoYXQgd291bGQgYXJpc2UgZnJvbQ0KPj4+Pj4+Pj4+
Pj4gdW5yZWxpYWJsZSB0cmFuc3BvcnRzLiAgTWlzLQ0KPj4+Pj4+Pj4+Pj4gICAgICAgICBvcmRl
cmluZyBjYW4gYmUgZGV0ZWN0ZWQgdGhyb3VnaCB0aGUgQ1NlcTogaGVhZGVyIGZpZWxkDQo+Pj4+
Pj4+Pj4+PiBpbiB0aGUgSU5GTw0KPj4+Pj4+Pj4+Pj4gICAgICAgICByZXF1ZXN0LiAgQXMgYSBj
b25zZXF1ZW5jZSBjYW5kaWRhdGVzIGNhbm5vdCBiZSByZW1vdmVkDQo+Pj4+Pj4+Pj4+PiB1bmxl
c3MgYW4gSUNFDQo+Pj4+Pj4+Pj4+PiAgICAgICAgIHJlc3RhcnQgaXMgcGVyZm9ybWVkLiAgTm90
ZSB0aGF0IGV4dGVuc2lvbiBtaWdodCBiZQ0KPj4+Pj4+Pj4+Pj4gc3BlY2lmaWVkIGluIHRoZQ0K
Pj4+Pj4+Pj4+Pj4gICAgICAgICBmdXR1cmUgdGhhdCBlbmFibGUgc3VjaCByZW1vdmFsIHdpdGhv
dXQgYSByZXN0YXJ0LiINCj4+Pj4+Pj4+Pj4+IFExOiBBc3N1bWluZyBzb21lb25lIGRvZXMgZGVm
aW5lIGFuIGV4dGVuc2lvbiB3aGljaCBhbGxvd3MNCj4+Pj4+Pj4+Pj4+IHJlbW92YWwNCj4+Pj4+
Pj4+Pj4+IG9mIGNhbmRpZGF0ZXMgd2l0aG91dCBhIHJlc3RhcnQsIGRvIHN1Y2ggY2FuZGlkYXRl
cyBzdGlsbCBoYXZlDQo+Pj4+Pj4+Pj4+PnRvDQo+Pj4+Pj4+Pj4+PiBiZSBpbmNsdWRlZCBpbiB0
aGUgSU5GTywgYXMgdGhleSBoYXZlIGJlZW4gInByZXZpb3VzbHkNCj4+Pj4+Pj4+Pj4+IHNpZ25h
bGxlZCI/DQo+Pj4+Pj4+Pj4+IFRoaXMgd291bGQgaGF2ZSB0byBjbGFyaWZpZWQgaW4gdGhhdCBm
dXR1cmUgZXh0ZW5zaW9uIGRvY3VtZW50DQo+Pj4+Pj4+Pj4+IHRvZ2V0aGVyIHdpdGggY29ycmVz
cG9uZGluZyBiYWNrd2FyZCBjb21wYXRpYmlsaXR5IGlzc3VlcyBhbmQvb3INCj4+Pj4+Pj4+Pj4g
aW5kaWNhdGlvbiBvZiBzdXBwb3J0IGZvciBzdWNoIGFuIGV4dGVuc2lvbi4gSSBkb24ndCB3YW50
IHRvIGRvDQo+Pj4+Pj4+Pj4+IGRlc2lnbiBoZXJlLCBidXQgYT1pY2Utb3B0aW9ucyBtaWdodCBi
ZSBzb21ldGhpbmcgdG8gbG9vayBhdC4NCj4+Pj4+Pj4+PiBIb3cgeW91IGluZGljYXRlIHN1cHBv
cnQgb2Ygc3VjaCBleHRlbnNpb24gaXMgb3V0c2lkZSB0aGUgc2NvcGUNCj4+Pj4+Pj4+Pm9mDQo+
Pj4+Pj4+Pj4gdGhpcyB0aHJlYWQuIEkgd2FudCB0byBjbGFyaWZ5IHRoZSBleGFjdCBzZW1hbnRp
Y3Mgb2YgYSBjYW5kaWRhdGUNCj4+Pj4+Pj4+PiBpbiBhbiBJTkZPLg0KPj4+Pj4+PiBBZ2Fpbiwg
SSBhZ3JlZSB0aGF0IGhvdyBjYW5kaWRhdGVzIGFyZSByZW1vdmVkIGlzIG91dHNpZGUgdGhlDQo+
Pj4+Pj4+c2NvcGUuDQo+Pj4+Pj4+IEJ1dCwgdGhhdCBkb2Vzbqn2dCBjaGFuZ2UgdGhlIGZhY3Qg
dGhhdCB0cmlja2xlIG5lZWRzIHRvIGRlZmluZQ0KPj4+Pj4+PiBleGFjdGx5DQo+Pj4+Pj4+IHdo
YXQgdGhlIHNlbWFudGljIG9mIHRoZSBzaWduYWxsZWQgY2FuZGlkYXRlcy4gSSBkbyBOT1Qgd2Fu
dCBhDQo+Pj4+Pj4+ZnV0dXJlDQo+Pj4+Pj4+IGV4dGVuc2lvbiB0byBjaGFuZ2UgdGhhdCBzZW1h
bnRpYy4NCj4+Pj4+IEkgZG9uJ3QgaG93IHlvdSB3YW50IHRvIHByZWNsdWRlIGFuIGFyYml0cmFy
eSBmdXR1cmUgZXh0ZW5zaW9uIHRvIGRvDQo+Pj4+PiBzdWNoIGEgY2hhbmdlLA0KPj4+Pj4gYnV0
IGluIGNhc2Ugb2YgYSAiY2FuZGlkYXRlIHJlbW92YWwiIGV4dGVuc2lvbiBJIGRvbid0IHNlZSBh
IHByb2JsZW0NCj4+Pj4+IHdpdGggdGhlIGN1cnJlbnQgPmNvbmNlcHQuDQo+Pj4+PiBUaGUgY3Vy
cmVudCBjb25jZXB0IGlzIChhcyBJIHVuZGVyc3RhbmQgaXQpOg0KPj4+Pj4gLSBBbiBJTkZPIGFs
d2F5cyBjYXJyaWVzIGFsbCBjYW5kaWRhdGVzIHRoYXQgYmVsb25nIHRvIHRoZSBjdXJyZW50bHkN
Cj4+Pj4+IHZhbGlkIHVmcmFnL3B3ZC4NCj4+Pj4gQnV0IHRoYXQgaXMgbm90IHdoYXQgdGhlIHRl
eHQgaXMgc2F5aW5nLiAiVGhhdCBiZWxvbmciIGlzIG5vdCB0aGUgc2FtZQ0KPj4+PiBhcyAiUHJl
dmlvdXNseSBzaWduYWxsZWQiLiAiVGhhdCBiZWxvbmciIG1lYW5zIHRoZXkgYXJlIHN0aWxsDQo+
Pj4+IHZhbGlkL2FjdGl2ZSAtIGF0IGxlYXN0IGluIG15IGVhcnMuDQo+Pj4gVGFraW5nIGludG8g
YWNjb3VudCB0aGF0IGRyYWZ0LWljZS10cmlja2xlIGRvZXMgbm90IHByb3ZpZGUgIGFueQ0KPj4+
IG1lY2hhbmlzbSBmb3IgcmVtb3ZhbCBpbiBteSBlYXJzIGJvdGggc291bmQgdGhlIHNhbWUgLSAg
Y3VycmVudGx5IHRoYXQNCj4+PmlzLg0KPj4+IFdvdWxkIHRoZW4gY2hhbmdpbmcgICIuLi4gUHJl
dmlvdXNseSBzaWduYWxsZWQgLi4uIiB0byAiVGhhdCBiZWxvbmciIGluDQo+Pj4gdGhlIGJvZHkg
b2YgZHJhZnQtbW11c2ljLXRyaWNrbGUtaWNlLXNkcCBiZSBmaW5lIHRoZW4/DQo+PiBMZXShr3Mg
dGFsayBhYm91dCBhIG1lY2hhbmlzbSB0aGF0IERPRVMgZXhpc3Q6IGNvbnRpbm91cyBjb25zZW50
Lg0KPj4NCj4+IEFjY29yZGluZyB0byBSRkMgNzY3NSwgaWYgY29uc2VudCBpcyBsb3N0IGZvciBz
cGVjaWZpYyBjYW5kaWRhdGVzIGFuIElDRQ0KPj4gcmUtc3RhcnQgaXMgcmVxdWlyZWQgaW4gb3Jk
ZXIgdG8gdXNlIHRoZSBjYW5kaWRhdGUgcGFpci4NCj4+DQo+PiBTbywgYmVmb3JlIHN1Y2ggSUNF
IHJlLXN0YXJ0IG9jY3VyLCB3aHkgc2hvdWxkIHdlIGtlZXAgc2lnbmFsbGluZyBzdWNoDQo+PiBj
YW5kaWRhdGVzIGluIElORk9zPw0KPk5vdyBJJ20gbG9zdC4NCj5DYW4geW91IHBsZWFzZSBleHBs
YWluIHdoYXQgNzY3NSBoYXMgdG8gZG8gd2l0aCB0aGUgSU5GTyBtZXNzYWdlcyBmcm9tDQo+VHJp
Y2tsZS1JQ0U/DQo+VGhlc2UgSU5GT3MgYXJlIHVzZWQgZHVyaW5nIHRoZSBlYXJseSBkaWFsb2cg
cGhhc2Ugb2YgdGhlIHNlc3Npb24gaW4NCj5vcmRlciB0byBnZXQgdGhlIGNhbmRpZGF0ZXMgZXhj
aGFuZ2VkIHVudGlsIGVuZC1vZi1jYW5kaWRhdGVzIGlzIHJlY2VpdmVkLg0KPjc2NzUgY29tZXMg
aW50byB0aGUgZ2FtZSAgYWZ0ZXIgYSBjYW5kaWRhdGUgcGFpciBpcyBub21pbmF0ZWQgYW5kIHRo
ZQ0KPmRpYWxvZyBpcyBjb25maXJtZWQuDQoNCg0KWW91IGFyZSByaWdodC4gVGhlIGNvbnRpbnVv
dXMgY29uc2VudCAoQ0MpIGNoZWNrcyBzdGFydCBvbmNlIElDRSBoYXMNCmNvbmNsdWRlZCAoYXQg
bGVhc3QgdGhhdKGvcyBob3cgSSBhbHNvIHJlYWQgNzY3NSkuIFRvIG1lIHRoYXQgc291bmRzDQpz
dHJhbmdlLCBiZWNhdXNlIG1lZGlhIGNhbiBiZSBzZW50IG9uIGNhbmRpZGF0ZXMgYmVmb3JlIElD
RSBpcyBjb25jbHVkZWQuDQpJdCBldmVuIHRoYXQgc29tZW9uZSBjb3VsZCChsGRpc2FibGWhsSBD
QyBzaW1wbHkgYnkgbmV2ZXIgY29uY2x1ZGluZyBJQ0UgdG8NCmJlZ2luIHdpdGguIEJ1dCwgdGhh
dCBkaXNjdXNzaW9uIGJlbG9uZ3MgZWxzZXdoZXJlLg0KDQpBbHNvLCBpZiB3ZSBtb3ZlIGZvcndh
cmQgd2l0aCB0aGUgY29udGludW91cyBub21pbmF0aW9uIChDTikgcHJvcG9zYWwsDQp3aGVyZSBJ
Q0UgaXMgbmV2ZXIgY29uY2x1ZGVkLCBJIGFzc3VtZSB3ZSB3b3VsZCBoYXZlIHRvIG1vZGlmeSBS
RkMgNzY3NSBzbw0KdGhhdCBDQyBjaGVja3MgYmVnaW4gZWFybGllci4gQnV0LCB0aGF0IHdvdWxk
IGFsc28gbWVhbiB0aGF0IENDIGNoZWNrcyBhbmQNCnRyaWNrbGUgY291bGQgYmUgdXNlZCBhdCB0
aGUgc2FtZSB0aW1lLg0KDQoNCi4uLg0KDQo+Pj4+IFdoeSBzaG91bGQgd2Uga2VlcCBzaWduYWxs
aW5nIHN1Y2ggY2FuZGlkYXRlcz8NCj4+PiBJIGRvZXNuJ3QgZG8gYW55IGhhcm0uIFNlY3Rpb24g
NC4yIHNwZWNpZmllcyB0aGF0IG9ubHkgbmV3IGNhbmRpZGF0ZXMNCj4+PiBhcmUgcmVsYXllZCB0
byB0aGUgSUNFIGFnZW50Lg0KPj4+PiBXZSBjb3VsZCBvZiBjb3Vyc2UgZG8gYW4gSUNFIHJlLXN0
YXJ0IHdoZW5ldmVyIGEgY2FuZGlkYXRlIGlzIHJlbW92ZWQNCj4+Pj4gKG9uZSB3YXkgb3IgYW5v
dGhlciksIGJ1dCBJIGRvbid0IHRoaW5rIHdlIHdhbnQgdG8gZG8gdGhhdC4uLg0KPj4+IFByb2Jh
Ymx5IG5vdCwgYnV0IHRoYXQgaXMgdGhlIHdheSB0aGF0IFRyaWNrbGUtSUNFIGluaGVyaXRlZCBm
cm9tIDUyNDUuDQo+Pj4+IEJ1dCwgYWdhaW4sIGJ5IE9OTFkgc2lnbmFsbGluZyB0aGUgYWRkZWQg
Y2FuZGlkYXRlcyB3ZSBkb24ndCBoYXZlIHRoZQ0KPj4+PiBpc3N1ZSB3aXRoIHJlbW92ZWQgY2Fu
ZGlkYXRlcyB0byBiZWdpbiB3aXRoLg0KPj4+IFRoZXJlICB3aWxsIGNlcnRhaW5seSBiZSBvdGhl
ciBpc3N1ZXMuDQo+PiBQbGVhc2UgcHJlc2VudCB0aG9zZSBpc3N1ZXMgc28gd2UgY2FuIGRpc2N1
c3MgdGhlbS4NCj5JJ2QgcmF0aGVyIHdhaXQgdW50aWwgc29tZSBlbGFib3JhdGVkIHRleHQgZm9y
IHlvdXIgcHJvcG9zYWwgYXBwZWFycyBhbmQNCj50aGVuIHN0YXJ0IGZyb20gdGhlcmUuDQoNCk9r
LCBJoa9sbCB3b3JrIG9uIHNvbWUgdGV4dC4NCg0KQnV0LCBJoa9kIHN0aWxsIGxpa2UgdG8ga25v
dyB3aGF0IHRoZSBpc3N1ZXMgd2l0aCBPTkxZIHNpZ25hbGxpbmcgdGhlIGFkZGVkDQpjYW5kaWRh
dGVzIHdlcmUuIElmIHRoZXJlIHdlcmUgc29tZSBpc3N1ZXMsIGl0IHdvdWxkIHByb2JhYmx5IGJl
IGdvb2QgdG8NCmRvY3VtZW50IGluIHRoZSBkcmFmdCwgdG8ganVzdGlmeSB0aGUgc2VuZGluZyBv
ZiBBTEwgY2FuZGlkYXRlcy4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0K


From nobody Tue Oct 18 04:16:55 2016
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 B540A12959A for <mmusic@ietfa.amsl.com>; Tue, 18 Oct 2016 04:16:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 BMVCIFoTPwWZ for <mmusic@ietfa.amsl.com>; Tue, 18 Oct 2016 04:16:51 -0700 (PDT)
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 5DE3012940B for <mmusic@ietf.org>; Tue, 18 Oct 2016 04:16:50 -0700 (PDT)
X-AuditID: c1b4fb30-b87ff70000000cb2-66-580604a06795
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by  (Symantec Mail Security) with SMTP id 17.93.03250.0A406085; Tue, 18 Oct 2016 13:16:49 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0319.002; Tue, 18 Oct 2016 13:16:47 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Cullen Jennings <fluffy@iii.ca>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
Thread-Index: AQHSJHSivk5Ucbs2BE2kFscuEARQNKCmW5CAgAAxTzCAAOkBgIAGtiCA
Date: Tue, 18 Oct 2016 11:16:47 +0000
Message-ID: <D42BE0D9.11504%christer.holmberg@ericsson.com>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com>
In-Reply-To: <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <2024415018409447B2D7662DEF949B17@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNIsWRmVeSWpSXmKPExsUyM2K7je5CFrYIg645shYf1v9gtJi6/DGL A5PHkiU/mTwun//IGMAUxWWTkpqTWZZapG+XwJXxa9ldtoIehYpZNz+zNzDOkupi5OSQEDCR OP32DyuILSSwnlHixl21LkYuIHsxo8Tl/mlACQ4ONgELie5/2iA1IgKREgsnTWACCTMLqEtc XRwEEhYWyJD4fHQZWFhEIFNixUo/CNNN4kK/LUgFi4CqxOw9j9hBbF4Ba4m/e04xQSx9yijx qCkTxOYUcJCYv/IBI4jNKCAm8f3UGrAaZgFxiVtP5jNBHCwgsWTPeWYIW1Ti5eN/YDeKCuhJ rLkfBhFWkvix4RILRKuexI2pU9ggbGuJJXPeskLY2hLLFr5mhjhHUOLkzCcsExjFZyHZNgtJ +ywk7bOQtM9C0r6AkXUVo2hxanFSbrqRkV5qUWZycXF+nl5easkmRmCUHdzy22AH48vnjocY BTgYlXh4E26yRAixJpYVV+YeYpTgYFYS4dVnZosQ4k1JrKxKLcqPLyrNSS0+xCjNwaIkzmu2 8n64kEB6YklqdmpqQWoRTJaJg1OqgZH7WXv53Y0X+da1Snh1rFz999yr48EH5B6+Kw//t80p brrLoq3R4lIM6vkbf/2edCFMt28C38Hlez6mxu2MvSpUOodTfLabX/N2sfrc4BDL6nPpV5vm s66JOaHebXy46m27iJBrgu+/kxoyyZIJL5wuZv4VCH4X+mDL3799J8pqb1quPzubUU2JpTgj 0VCLuag4EQBkswGDrgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/e27WbT3YfrS1SCIP5NStKY_gC5M>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Oct 2016 11:16:54 -0000

Hi,

I=B9ve updated the pull request based on Magnus=B9 suggestion.

Regards,

Christer

On 14/10/16 10:54, "Magnus Westerlund" <magnus.westerlund@ericsson.com>
wrote:

>Den 2016-10-13 kl. 18:01, skrev Christer Holmberg:
>> However, Magnus told me it=B9s not needed, so I=B9d like to get some inp=
ut
>> from him.
>>
>> *From:*Cullen Jennings [mailto:fluffy@iii.ca]
>> That looks about right for RTP but I think it is still missing stuff for
>> RTCP handling. Here is the current text we did for JSEP. I prefer the
>> style in which you described it compared to the algorithm style below
>> but I think this might help figure out what to write for RTCP.
>>
>
>I dislike the algorithmic description JSEP has because it inserts itself
>at position in the stack where I would not myself implement the binding
>handling. The implementations of RTP stacks I have made have never let
>the full RTCP packets be available to the application layer. It has only
>implemented event and request based interface to provide the triggers
>and data associated with the differnet RTCP packets. Thus, from my
>perspective the routing of the RTCP packets becomes a question if the
>SSRC is bound to the right m=3D. Then handel the received RTCP packets in
>that context.
>
>So what might be a suitable RTCP clarification regarding RTCP would be
>the following.
>
>Simply add RTCP in the following sentence:
>
>"Later, when an offerer or answerer receives an RTP packet that does not
>carry the identification-tag, it can associate the packet with the
>correct "m=3D" line using the SSRC value."
>
>so that it reads:
>
>"Later, when an offerer or answerer receives an RTP or RTCP packet that
>does not carry the identification-tag, it can associate the packet with
>the correct "m=3D" line using the SSRC value."
>
>Regarding the second paragraph. If the association has been done
>according to this part then also the RTCP packets has an association. If
>an RTCP packet arrives with a non associated SSRC, then many RTCP
>packets type can still be processed and the information stored in the
>SSRC related information table. Some that are application interaction
>related, like some of the feedback messages can of course not be handled.
>
>One very important aspect here is that the basic RTCP processing do need
>to occur for also non-associated SSRCs. This to ensure that the sender
>get the RTCP feedback information for congestion control purposes. We
>want the transport layer functions to continue function, even if the
>application can't consume the packets.
>
>Thus, I would consider that the "the packet SHOULD be dropped." needs an
>addition that says after having been processed as received by the RTCP
>layer. If we don't report them as received we skew the congestion
>control information, and it will make any coupled congestion controller
>that looks at the set of RTP streams being emitted take the wrong
>decision. I also assumes that a lack of association is in most cases a
>temporary issue that will be resolved by the regular transmissions.
>
>A long term lack of association is from my perspective indicates an
>error on the signalling plane, so that a renegotation is needed. I do
>see the downside that the sending sides RTP/RTCP stack is lacking the
>information that the packet is being dropped after reception. This could
>be solved if one implemented the RTCP XR packet type Discard Count
>Metric Reporting (https://datatracker.ietf.org/doc/rfc7002/).
>I would use the 01 "Packet to early" for this case.
>
>
>Cheers
>
>
>Magnus Westerlund
>
>----------------------------------------------------------------------
>Services, Media and Network features, Ericsson Research EAB/TXM
>----------------------------------------------------------------------
>Ericsson AB                 | Phone  +46 10 7148287
>F=E4r=F6gatan 6                 | Mobile +46 73 0949079
>SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>----------------------------------------------------------------------
>


From nobody Wed Oct 19 00:34:06 2016
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 1EF9C129547 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 00:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 fRlKeZT0bbpK for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 00:34:03 -0700 (PDT)
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 154891294A0 for <mmusic@ietf.org>; Wed, 19 Oct 2016 00:34:02 -0700 (PDT)
X-AuditID: c1b4fb30-b73ff70000000cb2-93-580721e8e1c9
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by  (Symantec Mail Security) with SMTP id A7.3F.03250.8E127085; Wed, 19 Oct 2016 09:34:01 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0319.002; Wed, 19 Oct 2016 09:33:59 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Thomas Stach <thomass.stach@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
Thread-Index: AQHSHxIL5dxB//uBWky8GjwyA0+P66CZ76sAgAjKcACAAD99AIABlqsAgACw0bCABwPJgIAAPlIAgAAXs4CAAYxIAIABY7EA
Date: Wed, 19 Oct 2016 07:33:59 +0000
Message-ID: <D42CFDA3.115F5%christer.holmberg@ericsson.com>
References: <D41AC393.10727%christer.holmberg@ericsson.com> <bc713d1a-acdb-af95-5391-b3e244e1126d@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD1B3B2@ESESSMB209.ericsson.se> <e44e62ff-1b0d-9180-2872-b98c84cbb6f6@gmail.com> <D4226F4E.10D4F%christer.holmberg@ericsson.com> <7c516d72-ef2a-e928-dc4a-ee77298ebb22@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD668A9@ESESSMB209.ericsson.se> <e22f8a1a-00f6-8c87-5a4e-8c1e6dfa75b2@gmail.com> <D42A7012.1139C%christer.holmberg@ericsson.com> <7f03bb7b-f896-5238-a869-8ec16bd77f4a@gmail.com> <D42BCBE2.1149C%christer.holmberg@ericsson.com>
In-Reply-To: <D42BCBE2.1149C%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <B5000A111FB5E04BAC008C730752D768@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCIsWRmVeSWpSXmKPExsUyM2K7h+5LRfYIg8nrZCymLn/MYvHpxFYm ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugStj1uqfzAVvDCuOPbrN1sB4wqCLkZNDQsBE YvK/GaxdjFwcQgLrGSUWvDjNCOEsZpSY3j6FpYuRg4NNwEKi+582SFxEoJVRoq9jD1iHsMBU Ronrp/tYQUaJCExjlHi61AqkQUQgT2LxNgWQMIuAqsSGq98ZQWxeAWuJ/dt3QS24wSKx8Ox/ ZpB6TgEbic/rXUBqGAXEJL6fWsMEYjMLiEvcejKfCeJSAYkle84zQ9iiEi8f/2MFaRUV0JNY cz8MIqwosfNsOzNEq5bElx/72CBsa4l9516yQtiKElO6H7JDnCMocXLmE5YJjGKzkGybhaR9 FpL2WUjaZyFpX8DIuopRtDi1OCk33chIL7UoM7m4OD9PLy+1ZBMjMK4ObvltsIPx5XPHQ4wC HIxKPLwKyWwRQqyJZcWVuYcYJTiYlUR42+XYI4R4UxIrq1KL8uOLSnNSiw8xSnOwKInzmq28 Hy4kkJ5YkpqdmlqQWgSTZeLglGpgjNi3tOfBGvZT/QaS0z4pTfDe/dOAme8N1w7tiKKeK5k+ Jh++mcjOuvHi3u0pb4uE+8Rlzs5fekw33fx0yKq9U+9Oe6ivlb1CLq4pXexI5IOlR2pfcJzc uuI6S/rhYlPlpXcTBa5cvvuGa1V+MXNumNT9e+wFgod+njkXKtsa/3xCucRNzfpjLUosxRmJ hlrMRcWJAKolGS6nAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/DJfVsc3FaUBD9YT3RSlbd57akZU>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-trickle-ice-sip-05 (not draft-ietf-mmusic-ice-sip-sdp) regarding explicit removal of candidites
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 07:34:05 -0000

SGkgVGhvbWFzLA0KDQo+Pj4+Pj4+Pj4+Pj5JdCBoYXMgYmVlbiBzdWdnZXN0ZWQgdGhhdCByZW1v
dmFsIG9mIGNhbmRpZGF0ZXMgc2hvdWxkIG5vdCBiZQ0KPj4+Pj4+Pj4+Pj4+IHBhcnQgb2YgdHJp
Y2tsZSwgYnV0IHJhdGhlciBiZSBkZWZpbmVkIGluIGEgc2VwYXJhdGUgZnV0dXJlDQo+Pj4+Pj4+
Pj4+Pj4gZXh0ZW5zaW9uIGRyYWZ0Lg0KPj4+Pj4+Pj4+Pj4+IFRoZSBjb21tZW50cyBiZWxvdyBh
cmUgYmFzZWQgb24gdGhhdCBzdWNoICJleHRlbnNpb24iIG1heQ0KPj4+Pj4+Pj4+Pj4+ZXhpc3QN
Cj4+Pj4+Pj4+Pj4+PiBhdA0KPj4+Pj4+Pj4+Pj4+IHNvbWUgcG9pbnQuDQo+Pj4+Pj4+Pj4+Pj4N
Cj4+Pj4+Pj4+Pj4+PiBUaGUgdGV4dCBpbiBzZWN0aW9uIDQuMiBzYXlzOg0KPj4+Pj4+Pj4+Pj4+
ICAgICAgICAgIkluIGV2ZXJ5IElORk8gcmVxdWVzdCBhZ2VudHMgTVVTVCBpbmNsdWRlIGFsbCBs
b2NhbA0KPj4+Pj4+Pj4+Pj4+ICAgICAgICAgY2FuZGlkYXRlcyB0aGV5IGhhdmUgc2lnbmFsZWQg
cHJldmlvdXNseS4gIFRoaXMgaXMNCj4+Pj4+Pj4+Pj4+PiBuZWNlc3NhcnkgaW4gb3JkZXIgdG8N
Cj4+Pj4+Pj4+Pj4+PiAgICAgICAgIG1vcmUgZWFzaWx5IGF2b2lkIHByb2JsZW1zIHRoYXQgd291
bGQgYXJpc2UgZnJvbQ0KPj4+Pj4+Pj4+Pj4+IHVucmVsaWFibGUgdHJhbnNwb3J0cy4gIE1pcy0N
Cj4+Pj4+Pj4+Pj4+PiAgICAgICAgIG9yZGVyaW5nIGNhbiBiZSBkZXRlY3RlZCB0aHJvdWdoIHRo
ZSBDU2VxOiBoZWFkZXINCj4+Pj4+Pj4+Pj4+PmZpZWxkDQo+Pj4+Pj4+Pj4+Pj4gaW4gdGhlIElO
Rk8NCj4+Pj4+Pj4+Pj4+PiAgICAgICAgIHJlcXVlc3QuICBBcyBhIGNvbnNlcXVlbmNlIGNhbmRp
ZGF0ZXMgY2Fubm90IGJlDQo+Pj4+Pj4+Pj4+Pj5yZW1vdmVkDQo+Pj4+Pj4+Pj4+Pj4gdW5sZXNz
IGFuIElDRQ0KPj4+Pj4+Pj4+Pj4+ICAgICAgICAgcmVzdGFydCBpcyBwZXJmb3JtZWQuICBOb3Rl
IHRoYXQgZXh0ZW5zaW9uIG1pZ2h0IGJlDQo+Pj4+Pj4+Pj4+Pj4gc3BlY2lmaWVkIGluIHRoZQ0K
Pj4+Pj4+Pj4+Pj4+ICAgICAgICAgZnV0dXJlIHRoYXQgZW5hYmxlIHN1Y2ggcmVtb3ZhbCB3aXRo
b3V0IGEgcmVzdGFydC4iDQo+Pj4+Pj4+Pj4+Pj4gUTE6IEFzc3VtaW5nIHNvbWVvbmUgZG9lcyBk
ZWZpbmUgYW4gZXh0ZW5zaW9uIHdoaWNoIGFsbG93cw0KPj4+Pj4+Pj4+Pj4+IHJlbW92YWwNCj4+
Pj4+Pj4+Pj4+PiBvZiBjYW5kaWRhdGVzIHdpdGhvdXQgYSByZXN0YXJ0LCBkbyBzdWNoIGNhbmRp
ZGF0ZXMgc3RpbGwgaGF2ZQ0KPj4+Pj4+Pj4+Pj4+dG8NCj4+Pj4+Pj4+Pj4+PiBiZSBpbmNsdWRl
ZCBpbiB0aGUgSU5GTywgYXMgdGhleSBoYXZlIGJlZW4gInByZXZpb3VzbHkNCj4+Pj4+Pj4+Pj4+
PiBzaWduYWxsZWQiPw0KPj4+Pj4+Pj4+Pj4gVGhpcyB3b3VsZCBoYXZlIHRvIGNsYXJpZmllZCBp
biB0aGF0IGZ1dHVyZSBleHRlbnNpb24gZG9jdW1lbnQNCj4+Pj4+Pj4+Pj4+IHRvZ2V0aGVyIHdp
dGggY29ycmVzcG9uZGluZyBiYWNrd2FyZCBjb21wYXRpYmlsaXR5IGlzc3Vlcw0KPj4+Pj4+Pj4+
Pj5hbmQvb3INCj4+Pj4+Pj4+Pj4+IGluZGljYXRpb24gb2Ygc3VwcG9ydCBmb3Igc3VjaCBhbiBl
eHRlbnNpb24uIEkgZG9uJ3Qgd2FudCB0byBkbw0KPj4+Pj4+Pj4+Pj4gZGVzaWduIGhlcmUsIGJ1
dCBhPWljZS1vcHRpb25zIG1pZ2h0IGJlIHNvbWV0aGluZyB0byBsb29rIGF0Lg0KPj4+Pj4+Pj4+
PiBIb3cgeW91IGluZGljYXRlIHN1cHBvcnQgb2Ygc3VjaCBleHRlbnNpb24gaXMgb3V0c2lkZSB0
aGUgc2NvcGUNCj4+Pj4+Pj4+Pj5vZg0KPj4+Pj4+Pj4+PiB0aGlzIHRocmVhZC4gSSB3YW50IHRv
IGNsYXJpZnkgdGhlIGV4YWN0IHNlbWFudGljcyBvZiBhDQo+Pj4+Pj4+Pj4+Y2FuZGlkYXRlDQo+
Pj4+Pj4+Pj4+IGluIGFuIElORk8uDQo+Pj4+Pj4+PiBBZ2FpbiwgSSBhZ3JlZSB0aGF0IGhvdyBj
YW5kaWRhdGVzIGFyZSByZW1vdmVkIGlzIG91dHNpZGUgdGhlDQo+Pj4+Pj4+PnNjb3BlLg0KPj4+
Pj4+Pj4gQnV0LCB0aGF0IGRvZXNuqfZ0IGNoYW5nZSB0aGUgZmFjdCB0aGF0IHRyaWNrbGUgbmVl
ZHMgdG8gZGVmaW5lDQo+Pj4+Pj4+PiBleGFjdGx5DQo+Pj4+Pj4+PiB3aGF0IHRoZSBzZW1hbnRp
YyBvZiB0aGUgc2lnbmFsbGVkIGNhbmRpZGF0ZXMuIEkgZG8gTk9UIHdhbnQgYQ0KPj4+Pj4+Pj5m
dXR1cmUNCj4+Pj4+Pj4+IGV4dGVuc2lvbiB0byBjaGFuZ2UgdGhhdCBzZW1hbnRpYy4NCj4+Pj4+
PiBJIGRvbid0IGhvdyB5b3Ugd2FudCB0byBwcmVjbHVkZSBhbiBhcmJpdHJhcnkgZnV0dXJlIGV4
dGVuc2lvbiB0byBkbw0KPj4+Pj4+IHN1Y2ggYSBjaGFuZ2UsDQo+Pj4+Pj4gYnV0IGluIGNhc2Ug
b2YgYSAiY2FuZGlkYXRlIHJlbW92YWwiIGV4dGVuc2lvbiBJIGRvbid0IHNlZSBhIHByb2JsZW0N
Cj4+Pj4+PiB3aXRoIHRoZSBjdXJyZW50ID5jb25jZXB0Lg0KPj4+Pj4+IFRoZSBjdXJyZW50IGNv
bmNlcHQgaXMgKGFzIEkgdW5kZXJzdGFuZCBpdCk6DQo+Pj4+Pj4gLSBBbiBJTkZPIGFsd2F5cyBj
YXJyaWVzIGFsbCBjYW5kaWRhdGVzIHRoYXQgYmVsb25nIHRvIHRoZSBjdXJyZW50bHkNCj4+Pj4+
PiB2YWxpZCB1ZnJhZy9wd2QuDQo+Pj4+PiBCdXQgdGhhdCBpcyBub3Qgd2hhdCB0aGUgdGV4dCBp
cyBzYXlpbmcuICJUaGF0IGJlbG9uZyIgaXMgbm90IHRoZQ0KPj4+Pj5zYW1lDQo+Pj4+PiBhcyAi
UHJldmlvdXNseSBzaWduYWxsZWQiLiAiVGhhdCBiZWxvbmciIG1lYW5zIHRoZXkgYXJlIHN0aWxs
DQo+Pj4+PiB2YWxpZC9hY3RpdmUgLSBhdCBsZWFzdCBpbiBteSBlYXJzLg0KPj4+PiBUYWtpbmcg
aW50byBhY2NvdW50IHRoYXQgZHJhZnQtaWNlLXRyaWNrbGUgZG9lcyBub3QgcHJvdmlkZSAgYW55
DQo+Pj4+IG1lY2hhbmlzbSBmb3IgcmVtb3ZhbCBpbiBteSBlYXJzIGJvdGggc291bmQgdGhlIHNh
bWUgLSAgY3VycmVudGx5IHRoYXQNCj4+Pj5pcy4NCj4+Pj4gV291bGQgdGhlbiBjaGFuZ2luZyAg
Ii4uLiBQcmV2aW91c2x5IHNpZ25hbGxlZCAuLi4iIHRvICJUaGF0IGJlbG9uZyINCj4+Pj5pbg0K
Pj4+PiB0aGUgYm9keSBvZiBkcmFmdC1tbXVzaWMtdHJpY2tsZS1pY2Utc2RwIGJlIGZpbmUgdGhl
bj8NCj4+PiBMZXShr3MgdGFsayBhYm91dCBhIG1lY2hhbmlzbSB0aGF0IERPRVMgZXhpc3Q6IGNv
bnRpbm91cyBjb25zZW50Lg0KPj4+DQo+Pj4gQWNjb3JkaW5nIHRvIFJGQyA3Njc1LCBpZiBjb25z
ZW50IGlzIGxvc3QgZm9yIHNwZWNpZmljIGNhbmRpZGF0ZXMgYW4NCj4+PklDRQ0KPj4+IHJlLXN0
YXJ0IGlzIHJlcXVpcmVkIGluIG9yZGVyIHRvIHVzZSB0aGUgY2FuZGlkYXRlIHBhaXIuDQo+Pj4N
Cj4+PiBTbywgYmVmb3JlIHN1Y2ggSUNFIHJlLXN0YXJ0IG9jY3VyLCB3aHkgc2hvdWxkIHdlIGtl
ZXAgc2lnbmFsbGluZyBzdWNoDQo+Pj4gY2FuZGlkYXRlcyBpbiBJTkZPcz8NCj4+Tm93IEknbSBs
b3N0Lg0KPj5DYW4geW91IHBsZWFzZSBleHBsYWluIHdoYXQgNzY3NSBoYXMgdG8gZG8gd2l0aCB0
aGUgSU5GTyBtZXNzYWdlcyBmcm9tDQo+PlRyaWNrbGUtSUNFPw0KPj5UaGVzZSBJTkZPcyBhcmUg
dXNlZCBkdXJpbmcgdGhlIGVhcmx5IGRpYWxvZyBwaGFzZSBvZiB0aGUgc2Vzc2lvbiBpbg0KPj5v
cmRlciB0byBnZXQgdGhlIGNhbmRpZGF0ZXMgZXhjaGFuZ2VkIHVudGlsIGVuZC1vZi1jYW5kaWRh
dGVzIGlzDQo+PnJlY2VpdmVkLg0KPj43Njc1IGNvbWVzIGludG8gdGhlIGdhbWUgIGFmdGVyIGEg
Y2FuZGlkYXRlIHBhaXIgaXMgbm9taW5hdGVkIGFuZCB0aGUNCj4+ZGlhbG9nIGlzIGNvbmZpcm1l
ZC4NCj4NCj4NCj5Zb3UgYXJlIHJpZ2h0LiBUaGUgY29udGludW91cyBjb25zZW50IChDQykgY2hl
Y2tzIHN0YXJ0IG9uY2UgSUNFIGhhcw0KPmNvbmNsdWRlZCAoYXQgbGVhc3QgdGhhdKGvcyBob3cg
SSBhbHNvIHJlYWQgNzY3NSkuIFRvIG1lIHRoYXQgc291bmRzDQo+c3RyYW5nZSwgYmVjYXVzZSBt
ZWRpYSBjYW4gYmUgc2VudCBvbiBjYW5kaWRhdGVzIGJlZm9yZSBJQ0UgaXMgY29uY2x1ZGVkLg0K
Pkl0IGV2ZW4gdGhhdCBzb21lb25lIGNvdWxkIKGwZGlzYWJsZaGxIENDIHNpbXBseSBieSBuZXZl
ciBjb25jbHVkaW5nIElDRSB0bw0KPmJlZ2luIHdpdGguIEJ1dCwgdGhhdCBkaXNjdXNzaW9uIGJl
bG9uZ3MgZWxzZXdoZXJlLg0KPg0KPkFsc28sIGlmIHdlIG1vdmUgZm9yd2FyZCB3aXRoIHRoZSBj
b250aW51b3VzIG5vbWluYXRpb24gKENOKSBwcm9wb3NhbCwNCj53aGVyZSBJQ0UgaXMgbmV2ZXIg
Y29uY2x1ZGVkLCBJIGFzc3VtZSB3ZSB3b3VsZCBoYXZlIHRvIG1vZGlmeSBSRkMgNzY3NSBzbw0K
PnRoYXQgQ0MgY2hlY2tzIGJlZ2luIGVhcmxpZXIuIEJ1dCwgdGhhdCB3b3VsZCBhbHNvIG1lYW4g
dGhhdCBDQyBjaGVja3MgYW5kDQo+dHJpY2tsZSBjb3VsZCBiZSB1c2VkIGF0IHRoZSBzYW1lIHRp
bWUuDQoNCkkgaGFkIHNvbWUgb2ZmLWxpbmUgZGlzY3Vzc2lvbnMsIGFuZCBpdCBzZWVtcyBsaWtl
IHRoZSBpZGVhIGlzIHRoYXQgQ0MNCmNoZWNrcyBiZWdpbiBvbmNlIGEgcGFpciBoYXMgYmVlbiB2
YWxpZGF0ZWQuIFBlb3BsZSBhZ3JlZSB0aGUgUkZDIHRleHQgaXMNCm5vdCB2ZXJ5IGNsZWFyLg0K
DQpCdXQsIHRoYXQgbWVhbnMgdGhhdCBDQyBjaGVja3MgYW5kIHRyaWNrbGUgQ0FOIGJlIHVzZWQg
YXQgdGhlIHNhbWUgdGltZS4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0K


From nobody Wed Oct 19 02:58:12 2016
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 C5970129465; Wed, 19 Oct 2016 02:58:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.35.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147687108880.8960.11244395540650656354.idtracker@ietfa.amsl.com>
Date: Wed, 19 Oct 2016 02:58:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/GGQ8eutpMl4gKke0ptJQt312TNs>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-bundle-negotiation-34.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 09:58:09 -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 of the IETF.

        Title           : Negotiating Media Multiplexing Using the Session Description Protocol (SDP)
        Authors         : Christer Holmberg
                          Harald Tveit Alvestrand
                          Cullen Jennings
	Filename        : draft-ietf-mmusic-sdp-bundle-negotiation-34.txt
	Pages           : 56
	Date            : 2016-10-19

Abstract:
   This specification defines a new Session Description Protocol (SDP)
   Grouping Framework extension, 'BUNDLE'.  The extension can be used
   with the SDP Offer/Answer mechanism to negotiate the usage of a
   single address:port combination (BUNDLE address) for receiving media,
   referred to as bundled media, specified by multiple SDP media
   descriptions ("m=" lines).

   To assist endpoints in negotiating the use of bundle this
   specification defines a new SDP attribute, 'bundle-only', which can
   be used to request that specific media is only used if bundled.  The
   specification also updates RFC 3264, to allow usage of zero port
   values without meaning that media is rejected.

   There are multiple ways to correlate the bundled RTP packets with the
   appropriate media descriptions.  This specification defines a new
   Real-time Transport Protocol (RTP) source description (SDES) item and
   a new RTP header extension that provides an additional way to do this
   correlation by using them to carry a value that associates the RTP/
   RTCP packets with a specific media description.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation-34

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


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

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


From nobody Wed Oct 19 03:00:50 2016
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 F3EF312959F for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 03:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 U8kMZVEpKOUL for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 03:00:47 -0700 (PDT)
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 86506127078 for <mmusic@ietf.org>; Wed, 19 Oct 2016 03:00:47 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-80-5807444d529e
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by  (Symantec Mail Security) with SMTP id 8B.15.02551.D4447085; Wed, 19 Oct 2016 12:00:45 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0319.002; Wed, 19 Oct 2016 12:00:44 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: BUNDLE-34
Thread-Index: AQHSKe+o3h6+jOE8jESeNotNbKlH4g==
Date: Wed, 19 Oct 2016 10:00:44 +0000
Message-ID: <D42D209A.11629%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.20]
Content-Type: multipart/alternative; boundary="_000_D42D209A11629christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFLMWRmVeSWpSXmKPExsUyM2K7va6vC3uEwZ+9phZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxuXTe5kKzvFUXNn0nbWB8RlXFyMnh4SAicSlxxeYuhi5OIQE 1jNKnPv9gB3CWcwosWn+dNYuRg4ONgELie5/2iANIgLqEl/39jCD2MICqhLN0y8yQ8S1JL6c 2M8GYetJHJ39mAWklQWopu+NBUiYV8Baon3iInYQm1FATOL7qTVMIDazgLjErSfzmSDuEZBY suc8M4QtKvHy8T+wC0SBRq65HwYRVpS4On05E0iYWSBBYsoeFojpghInZz5hmcAoNAvJ0FkI VbOQVEGUGEi8PzefGcLWlli28DWUrS+x8ctZRgjbWuLiuS1MyGoWMHKsYhQtTi0uzk03MtZL LcpMLi7Oz9PLSy3ZxAiMkYNbfuvuYFz92vEQowAHoxIPr0IyW4QQa2JZcWXuIUYJDmYlEd5n VuwRQrwpiZVVqUX58UWlOanFhxilOViUxHnNVt4PFxJITyxJzU5NLUgtgskycXBKNTA239aw /yi0PUluR9O8mukHzOSsGSTqGY0CTj17c/255ALTrA0zFW+FZ1xgP7lwF/+Jd6sipCvOyXtJ +JkLeUR/Pf6G/9resDPM806dtd13zGGNgKTh1wt97d08HWo+iU5sv53aduXrzeEP/Xne6sml vPmqW1wYO7jOePlKRQUXaD2aGjvv3A4lluKMREMt5qLiRABkNqaZjQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/oBeJOsIQLl6k7MlL7x9WAhUBLoA>
Subject: [MMUSIC] Draft new version: BUNDLE-34
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 10:00:49 -0000

--_000_D42D209A11629christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

I=92ve submitted a new version (-34) of BUNDLE.

Changes:

  *   Alignment with JSEP regarding a=3Drtcp/a=3Drtcp-mux usage
  *   Additional text regarding associating RTP/RTCP packets with m- lines
  *   Reference correction

I have NOT done any changes regarding MID security, as there is still no co=
nsensus on what/if to do.

Regards,

Christer

--_000_D42D209A11629christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <2A60935C35645943A41B1AFF2073875A@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>I=92ve submitted a new version (-34) of BUNDLE.</div>
<div><br>
</div>
<div>Changes:</div>
<ul>
<li>Alignment with JSEP regarding a=3Drtcp/a=3Drtcp-mux usage</li><li>Addit=
ional text regarding associating RTP/RTCP packets with m- lines</li><li>Ref=
erence correction</li></ul>
<div>I have NOT done any changes regarding MID security, as there is still =
no consensus on what/if to do.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
</body>
</html>

--_000_D42D209A11629christerholmbergericssoncom_--


From nobody Wed Oct 19 04:41:56 2016
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 D0E2C129435; Wed, 19 Oct 2016 04:41:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.35.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147687731184.8840.15751595572399093873.idtracker@ietfa.amsl.com>
Date: Wed, 19 Oct 2016 04:41:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/QgEz2ZeY2KdvcOy_hlMMsKBY6MM>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-msrp-usage-data-channel-06.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 11:41:52 -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 of the IETF.

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

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


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-msrp-usage-data-channel-06

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


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 Wed Oct 19 04:51:53 2016
Return-Path: <juergen.stoetzer-bradler@nokia.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 8A07D129566 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 04:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.42
X-Spam-Level: 
X-Spam-Status: No, score=-6.42 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, 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 YW5i95_R_qz9 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 04:51:49 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 7846A129421 for <mmusic@ietf.org>; Wed, 19 Oct 2016 04:51:49 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 5F42CAA95D0BA for <mmusic@ietf.org>; Wed, 19 Oct 2016 11:51:45 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u9JBpkOH013817 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <mmusic@ietf.org>; Wed, 19 Oct 2016 11:51:47 GMT
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u9JBphRJ020062 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mmusic@ietf.org>; Wed, 19 Oct 2016 13:51:45 +0200
Received: from [149.204.68.181] (135.239.27.39) by FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 19 Oct 2016 13:51:43 +0200
To: <mmusic@ietf.org>
References: <147687731184.8840.15751595572399093873.idtracker@ietfa.amsl.com>
From: Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@nokia.com>
Message-ID: <1b89f4ef-9e28-f243-d8ab-50b9fef105b3@nokia.com>
Date: Wed, 19 Oct 2016 13:51:42 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <147687731184.8840.15751595572399093873.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms080109040607080300070100"
X-Originating-IP: [135.239.27.39]
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Fjhffs2YzEDN8QjzgBOwhabaaaE>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-msrp-usage-data-channel-06.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 11:51:51 -0000

--------------ms080109040607080300070100
Content-Type: multipart/alternative;
 boundary="------------2E317FCC7287C3DD4236D98F"

This is a multi-part message in MIME format.
--------------2E317FCC7287C3DD4236D98F
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Have just submitted this new version 06.
The only change to version 05 is a modification of my address information=
=2E

Thanks,
Juergen

On 19.10.2016 13:41, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts dire=
ctories.
> This draft is a work item of the Multiparty Multimedia Session Control =
of the IETF.
>
>          Title           : MSRP over Data Channels
>          Authors         : Keith Drage
>                            Maridi R. Makaraju (Raju)
>                            Juergen Stoetzer-Bradler
>                            Richard Ejzak
>                            Jerome Marcon
> 	Filename        : draft-ietf-mmusic-msrp-usage-data-channel-06.txt
> 	Pages           : 17
> 	Date            : 2016-10-19
>
> Abstract:
>     This document specifies how the Message Session Relay Protocol (MSR=
P)
>     can be instantiated as a data channel sub-protocol, using the SDP
>     offer/answer exchange-based generic data channel negotiation
>     framework.  Two network configurations are documented: a WebRTC end=
-
>     to-end configuration (connecting two MSRP over data channel
>     endpoints), and a gateway configuration (connecting an MSRP over da=
ta
>     channel endpoint with an MSRP over TCP endpoint).
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-msrp-usage-data-chan=
nel/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-mmusic-msrp-usage-data-channel-0=
6
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-msrp-usage-data-c=
hannel-06
>
>
> Please note that it may take a couple of minutes from the time of submi=
ssion
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


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

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    Have just submitted this new version 06.<br>
    The only change to version 05 is a modification of my address
    information.<br>
    <br>
    Thanks,<br>
    Juergen<br>
    <br>
    <div class=3D"moz-cite-prefix">On 19.10.2016 13:41,
      <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:internet-draft=
s@ietf.org">internet-drafts@ietf.org</a> wrote:<br>
    </div>
    <blockquote
cite=3D"mid:147687731184.8840.15751595572399093873.idtracker@ietfa.amsl.c=
om"
      type=3D"cite">
      <pre wrap=3D"">
A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
This draft is a work item of the Multiparty Multimedia Session Control of=
 the IETF.

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

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


The IETF datatracker status page for this draft is:
<a class=3D"moz-txt-link-freetext" href=3D"https://datatracker.ietf.org/d=
oc/draft-ietf-mmusic-msrp-usage-data-channel/">https://datatracker.ietf.o=
rg/doc/draft-ietf-mmusic-msrp-usage-data-channel/</a>

There's also a htmlized version available at:
<a class=3D"moz-txt-link-freetext" href=3D"https://tools.ietf.org/html/dr=
aft-ietf-mmusic-msrp-usage-data-channel-06">https://tools.ietf.org/html/d=
raft-ietf-mmusic-msrp-usage-data-channel-06</a>

A diff from the previous version is available at:
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/rfcdiff?u=
rl2=3Ddraft-ietf-mmusic-msrp-usage-data-channel-06">https://www.ietf.org/=
rfcdiff?url2=3Ddraft-ietf-mmusic-msrp-usage-data-channel-06</a>


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

Internet-Drafts are also available by anonymous FTP at:
<a class=3D"moz-txt-link-freetext" href=3D"ftp://ftp.ietf.org/internet-dr=
afts/">ftp://ftp.ietf.org/internet-drafts/</a>

_______________________________________________
mmusic mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:mmusic@ietf.org">mmu=
sic@ietf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/l=
istinfo/mmusic">https://www.ietf.org/mailman/listinfo/mmusic</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------2E317FCC7287C3DD4236D98F--

--------------ms080109040607080300070100
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
DF8wggTdMIIDxaADAgECAgoanQrOAAAAAAAGMA0GCSqGSIb3DQEBBQUAMEMxFzAVBgNVBAoT
DkFsY2F0ZWwgTHVjZW50MSgwJgYDVQQDEx9BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBSb290
IENBMB4XDTA4MTEyMTIxNTcyOFoXDTE4MTEyMTIyMDcyOFowgYUxEzARBgoJkiaJk/IsZAEZ
FgNjb20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcw
FQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJu
YWwgU3ViIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2Ocmcli3LbVU6TRh
+JLMtquBr5/grS+gzfN5YL/lauFCHmDlF7kNQvxtDWqwNpOkzb97CwWcVsdfkyWAiGzVWeRI
rYGhK/xNPFRYXOKYXLGqxFWkltZkYpSRudHzjTneUC4EVdMXnREMu8FTC0CM38VbxMvQ+ygj
Eyicg2QT9lZHWkKP9kCI1818P+AmS7905t6kXR9Q2m1GjcCa0KqARPGX/xe2toQS+VdiUwDa
ry1Enk8j19KFmvFg1bhY2mNSHgzN2AWnhsOi/EID1SalzBwHylByB/UbbEv2dZUsAdMuOtYt
Z/8dM1axS0d3fW7q7mAYV5uM42mYX9o1B/RzjwIDAQABo4IBjjCCAYowDwYDVR0TAQH/BAUw
AwEB/zAdBgNVHQ4EFgQU2exrvZZYIvfYpnfN/k2B77qXvRIwCwYDVR0PBAQDAgHGMBAGCSsG
AQQBgjcVAQQDAgEAMBkGCSsGAQQBgjcUAgQMHgoAUwB1AGIAQwBBMB8GA1UdIwQYMBaAFAes
slr2YYl8XHzr4pcnKWkMih/wMHgGA1UdHwRxMG8wbaBroGmGOWh0dHA6Ly9zZXJ2aWNlcy5z
dXBwb3J0LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kvcm9vdENBLmNybIYsaHR0cDovL3d3dy5h
bGNhdGVsLWx1Y2VudC5jb20vUEtJL3Jvb3RDQS5jcmwwgYIGCCsGAQUFBwEBBHYwdDA4Bggr
BgEFBQcwAoYsaHR0cDovL3d3dy5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3Jvb3RDQS5jcnQw
OAYIKwYBBQUHMAKGLGh0dHA6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9yb290Q0Eu
Y3J0MA0GCSqGSIb3DQEBBQUAA4IBAQClGxDp5Z1IDjIEz8VaTEWa8Q1OWUbXwsszdoNg5Gg3
F1a2VFFVegmsrpt4axbESlgE6AT/rkUUiyjbEhcUgY2OHdeKN5Gc7VOGh9D7SER9peARwSwx
4NYRrsIaRXDrUswWAM6T6ilDUogjKYk3uK2zZ6Vy7z3JewxVlhpeSsNPQSMoyNibKkYLRoh6
rvz94vB0mvcT0uVx7xowPNoTOjjGRAk4J/MBaNOupvwfRfPmwRetdnD6NC5x8aRkhr4ZNBjv
YxFT8IJaeLk8piQYMPRDlzi7dlb9d6C5WuC0LRpomk2r3bd6/XpNOx2FyG18axeeASWtENgP
vqEirM5MjwkCMIIHejCCBmKgAwIBAgIKYWH+JwAAAAFWdjANBgkqhkiG9w0BAQUFADCBhTET
MBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBmx1Y2VudDEUMBIGCgmSJomT
8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MScwJQYDVQQDEx5BbGNhdGVs
IEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0EwHhcNMTUwNTE4MTMwNzI0WhcNMTcwNTE3MTMwNzI0
WjBOMRAwDgYDVQQDEwdsaTYwNzYwMTowOAYJKoZIhvcNAQkBFitqdWVyZ2VuLnN0b2V0emVy
LWJyYWRsZXJAYWxjYXRlbC1sdWNlbnQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEA3SjiDDt1yolL0cBi5MS+Bea3hhVDSdcJ/xtfzEbTtkxo05xnMgeRTy/kNJZuR4oY
j/2TE+raQenSEgROQtLgxKjxtLh9/fGEuLCyFclz9SIeIYIkZBB1NSwZKmGlJHRU5jjqSinT
Hmux9chaP+TUoidoDYbfdz/uFGdPW7RP21Gxjzg9v/VC+tfc0u0idNF9Vwnkh3VgdisMf1Jf
JZNINpw0ZapFKRhLEhgtXVS7tkdxxTL0uc9XtviOTSSfxgBt2MPsj0qfhsNFFO4zUO1pJiBz
SBPnLt7af96oS2ZHI4Xz7zNHShDoSMMIr+7l9xgopb5qN/KMCMP9BSxxNEfphwIDAQABo4IE
IDCCBBwwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIhb3FWYPjsTmHpYEqhr/DQoWUmBmB
C/nmTIT9tVoCAWQCAQUwHwYDVR0lBBgwFgYKKwYBBAGCNwoDBAYIKwYBBQUHAwQwCwYDVR0P
BAQDAgWgMCkGCSsGAQQBgjcVCgQcMBowDAYKKwYBBAGCNwoDBDAKBggrBgEFBQcDBDBEBgkq
hkiG9w0BCQ8ENzA1MA4GCCqGSIb3DQMCAgIAgDAOBggqhkiG9w0DBAICAIAwBwYFKw4DAgcw
CgYIKoZIhvcNAwcwHQYDVR0OBBYEFEVmlcJSxtK5Cu7FZb5XUWWuKktKMB8GA1UdIwQYMBaA
FNnsa72WWCL32KZ3zf5Nge+6l70SMIIBXQYDVR0fBIIBVDCCAVAwggFMoIIBSKCCAUSGgdls
ZGFwOi8vL0NOPUFsY2F0ZWwlMjBMdWNlbnQlMjBJbnRlcm5hbCUyMFN1YiUyMENBLENOPXVz
bmF2c3BraTAzcCxDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2Vydmlj
ZXMsQ049Q29uZmlndXJhdGlvbixEQz1sdWFkLERDPWx1Y2VudCxEQz1jb20/Y2VydGlmaWNh
dGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNSTERpc3RyaWJ1dGlvblBvaW50
hixodHRwczovL3d3dy5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3N1YkNBLmNybIY4aHR0cDov
L3NlcnZpY2VzLnN1cHBvcnQuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9zdWJDQS5jcmwwggFh
BggrBgEFBQcBAQSCAVMwggFPMIHMBggrBgEFBQcwAoaBv2xkYXA6Ly8vQ049QWxjYXRlbCUy
MEx1Y2VudCUyMEludGVybmFsJTIwU3ViJTIwQ0EsQ049QUlBLENOPVB1YmxpYyUyMEtleSUy
MFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9bHVhZCxEQz1sdWNl
bnQsREM9Y29tP2NBQ2VydGlmaWNhdGU/YmFzZT9vYmplY3RDbGFzcz1jZXJ0aWZpY2F0aW9u
QXV0aG9yaXR5MDgGCCsGAQUFBzAChixodHRwczovL3d3dy5hbGNhdGVsLWx1Y2VudC5jb20v
UEtJL3N1YkNBLmNydDBEBggrBgEFBQcwAoY4aHR0cDovL3NlcnZpY2VzLnN1cHBvcnQuYWxj
YXRlbC1sdWNlbnQuY29tL1BLSS9zdWJDQS5jcnQwNgYDVR0RBC8wLYEranVlcmdlbi5zdG9l
dHplci1icmFkbGVyQGFsY2F0ZWwtbHVjZW50LmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAMrtX
ZAqm6NqOAYttJjvC6pL04tEKUusax1Dr6p6NfxVfUuW8ZoFXKoxHEDaYKQR9ldfnuILHN+x7
KdLeKg+NPUs7GFGwpBmJb7PRmxnIarFJbGHzpqZ9+Fhsde1uxi+y2VJcIOVaEh/JoRdHvSUQ
nwT4+FcBmS6uRv68rnCkh+KeUm6A7+6dDo/9l/Zh2Hu1+HVWw5kEH/xmO170v9Xef7efxzxv
BeQ644kvErDNG26LJDUtOqaKTdz9KKZXngw+2cAV/4Kc7C9xdT29Ugm8oOK/ecqBliMhBUen
WphsEDjIbKJCd40RJLKb+v49EN/IJogNDd81vtehOxDw5Lus4zGCA+0wggPpAgEBMIGUMIGF
MRMwEQYKCZImiZPyLGQBGRYDY29tMRYwFAYKCZImiZPyLGQBGRYGbHVjZW50MRQwEgYKCZIm
iZPyLGQBGRYEbmEwMjEXMBUGA1UEChMOQWxjYXRlbCBMdWNlbnQxJzAlBgNVBAMTHkFsY2F0
ZWwgTHVjZW50IEludGVybmFsIFN1YiBDQQIKYWH+JwAAAAFWdjANBglghkgBZQMEAgEFAKCC
AikwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTYxMDE5MTE1
MTQyWjAvBgkqhkiG9w0BCQQxIgQgTHQM1XT6GIPRTsZLlKzi/7nxMTC//k2qQ3c7vKUEhg0w
bAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMH
MA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIB
KDCBpQYJKwYBBAGCNxAEMYGXMIGUMIGFMRMwEQYKCZImiZPyLGQBGRYDY29tMRYwFAYKCZIm
iZPyLGQBGRYGbHVjZW50MRQwEgYKCZImiZPyLGQBGRYEbmEwMjEXMBUGA1UEChMOQWxjYXRl
bCBMdWNlbnQxJzAlBgNVBAMTHkFsY2F0ZWwgTHVjZW50IEludGVybmFsIFN1YiBDQQIKYWH+
JwAAAAFWdjCBpwYLKoZIhvcNAQkQAgsxgZeggZQwgYUxEzARBgoJkiaJk/IsZAEZFgNjb20x
FjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQK
Ew5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgU3Vi
IENBAgphYf4nAAAAAVZ2MA0GCSqGSIb3DQEBAQUABIIBADN7rQTLSztcmRjUMmDFCaSh3xyy
RcjwawjHwreFf2MbKZhAATtMAHkqq7J+hhwip+DyOGYn7yPQ1nLOoBFffqMGLgBddZs/RII7
o3Q5xZHwIe+Y8D65J33fkNXcX/uCWnGIDRlHAwKiv4kwVyGF7fX0eXI2Vf3AtQsg4Ljee+w1
lupnrBBiCulZ3dHji4vEtVjzfEVPDLogzK0v5e6JQwcTVnCpT/zUrGQ2cXhqW3QRGYKxo3VV
wIHLa8/r9kzAauhajcKmb26PxfTYwwD7C6qs0PxzXS/7Zcd1Osfp6DmgO7iPyhU/n8xWUjte
X8MsEAFu5WcclhKZKnozDEpgX/EAAAAAAAA=
--------------ms080109040607080300070100--


From nobody Wed Oct 19 05:19:26 2016
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 16DC61295F9 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 05:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 FyE82j6r11Q3 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 05:19:22 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CD3E129405 for <mmusic@ietf.org>; Wed, 19 Oct 2016 05:19:22 -0700 (PDT)
Received: from [130.209.157.30] (port=55501 helo=glaroam2-128-140.wireless.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1bwppu-00058j-SY; Wed, 19 Oct 2016 13:19:15 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <D42AA198.11408%christer.holmberg@ericsson.com>
Date: Wed, 19 Oct 2016 13:18:39 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A2448DA9-6634-4583-A4B6-040B93371254@csperkins.org>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org> <D42AA198.11408%christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/rqoPpJ8irJVgqdlkTt7OY4JQDpM>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 12:19:24 -0000

Hi,

That split between BUNDLE and JSEP is fine with me. My concern, though, =
is that it=E2=80=99s still phrased in terms of =E2=80=9Cassociate =
received RTP packets with an m=3D line=E2=80=9D, rather than =
=E2=80=9Cassociate SSRC with an m=3D line=E2=80=9D. For the RTP =
processing to work, the RTP and RTCP packets need to be grouped by SSRC, =
since RTCP processing, repairs, etc., are done per SSRC, then that SSRC =
mapped is onto the m=3D line.

Colin



> On 17 Oct 2016, at 13:36, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> Would the following work:
>=20
> - BUNDLE defines how to associate received RTP packets with an m- line
> - JSET defines how to associate m- lines with RtpReceivers
>=20
> In that case, BUNDLE would define the generic associate-with-m-line =
rules,
> while JSEP defines the WebRTC specifics.
>=20
> Regards,
>=20
> Christer
>=20
>=20
> On 17/10/16 12:50, "Colin Perkins" <csp@csperkins.org> wrote:
>=20
>>> On 14 Oct 2016, at 08:54, Magnus Westerlund
>>> <magnus.westerlund@ericsson.com> wrote:
>>>=20
>>> Den 2016-10-13 kl. 18:01, skrev Christer Holmberg:
>>>> However, Magnus told me it=C2=B9s not needed, so I=C2=B9d like to =
get some input
>>>> from him.
>>>>=20
>>>> *From:*Cullen Jennings [mailto:fluffy@iii.ca]
>>>> That looks about right for RTP but I think it is still missing =
stuff
>>>> for
>>>> RTCP handling. Here is the current text we did for JSEP. I prefer =
the
>>>> style in which you described it compared to the algorithm style =
below
>>>> but I think this might help figure out what to write for RTCP.
>>>>=20
>>>=20
>>> I dislike the algorithmic description JSEP has because it inserts
>>> itself at position in the stack where I would not myself implement =
the
>>> binding handling. The implementations of RTP stacks I have made have
>>> never let the full RTCP packets be available to the application =
layer.
>>> It has only implemented event and request based interface to provide =
the
>>> triggers and data associated with the differnet RTCP packets. Thus, =
from
>>> my perspective the routing of the RTCP packets becomes a question if =
the
>>> SSRC is bound to the right m=3D. Then handel the received RTCP =
packets in
>>> that context.
>>>=20
>>> So what might be a suitable RTCP clarification regarding RTCP would =
be
>>> the following.
>>>=20
>>> Simply add RTCP in the following sentence:
>>>=20
>>> "Later, when an offerer or answerer receives an RTP packet that does
>>> not carry the identification-tag, it can associate the packet with =
the
>>> correct "m=3D" line using the SSRC value."
>>>=20
>>> so that it reads:
>>>=20
>>> "Later, when an offerer or answerer receives an RTP or RTCP packet =
that
>>> does not carry the identification-tag, it can associate the packet =
with
>>> the correct "m=3D" line using the SSRC value."
>>>=20
>>> Regarding the second paragraph. If the association has been done
>>> according to this part then also the RTCP packets has an =
association. If
>>> an RTCP packet arrives with a non associated SSRC, then many RTCP
>>> packets type can still be processed and the information stored in =
the
>>> SSRC related information table. Some that are application =
interaction
>>> related, like some of the feedback messages can of course not be =
handled.
>>>=20
>>> One very important aspect here is that the basic RTCP processing do
>>> need to occur for also non-associated SSRCs. This to ensure that the
>>> sender get the RTCP feedback information for congestion control
>>> purposes. We want the transport layer functions to continue =
function,
>>> even if the application can't consume the packets.
>>>=20
>>> Thus, I would consider that the "the packet SHOULD be dropped." =
needs
>>> an addition that says after having been processed as received by the
>>> RTCP layer. If we don't report them as received we skew the =
congestion
>>> control information, and it will make any coupled congestion =
controller
>>> that looks at the set of RTP streams being emitted take the wrong
>>> decision. I also assumes that a lack of association is in most cases =
a
>>> temporary issue that will be resolved by the regular transmissions.
>>=20
>> I agree with all of this. The mapping shouldn=C2=B9t be from RTP or =
RTCP
>> packets onto RtpRecivers. The RTP protocol requires RTP and RTCP =
packets
>> be associated to an SSRC, and the mapping is to determine what=C2=B9s =
the role
>> of that SSRC (i.e., to map from SSRC to RtpReceiver).
>>=20
>>=20
>> --=20
>> Colin Perkins
>> https://csperkins.org/
>>=20
>>=20
>>=20
>>=20
>=20



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





From nobody Wed Oct 19 05:37:29 2016
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 AF7CD129601 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 05:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 KQyPVfx5y-e2 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 05:37:25 -0700 (PDT)
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 C897A1294F7 for <mmusic@ietf.org>; Wed, 19 Oct 2016 05:37:24 -0700 (PDT)
X-AuditID: c1b4fb25-14bff7000000793b-dd-58076902c2bf
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by  (Symantec Mail Security) with SMTP id CD.8F.31035.20967085; Wed, 19 Oct 2016 14:37:23 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0319.002; Wed, 19 Oct 2016 14:37:21 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
Thread-Index: AQHSJHSivk5Ucbs2BE2kFscuEARQNKCmW5CAgAAxTzCAAOkBgIAE15EAgABieACAAut/gIAAOXAA
Date: Wed, 19 Oct 2016 12:37:21 +0000
Message-ID: <D42D44E7.11653%christer.holmberg@ericsson.com>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org> <D42AA198.11408%christer.holmberg@ericsson.com> <A2448DA9-6634-4583-A4B6-040B93371254@csperkins.org>
In-Reply-To: <A2448DA9-6634-4583-A4B6-040B93371254@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <39E4AF93674B7544AAC5DA5418ACDF91@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGIsWRmVeSWpSXmKPExsUyM2J7iC5zJnuEweweAYvlL08wWnxY/4PR YuryxywOzB7T7t9n81iy5CeTx+XzHxkDmKO4bFJSczLLUov07RK4Mmb2fmMteGBWsWv/W8YG xjWmXYycHBICJhLtDfuYuxi5OIQE1jNK7G6YzwLhLGaUODX3DnsXIwcHm4CFRPc/bZAGEQFV iR3H/zGC2MwCdRKXfnaB2cICGRKfjy5jAikXEciUWLHSD6I8SuL2mSvsIDYLUOvW3uesICW8 AtYSqxrBSoQEWpklLrzyBAlzCjhK/L1RDRJmFBCT+H5qDRPEInGJW0/mM0FcLCCxZM95Zghb VOLl439gE0UF9CTW3A+DCCtKtD9tgLpRS+LLj31sELa1xNfjc6FsRYkp3Q/BDuMVEJQ4OfMJ ywRG8VlIts1C0j4LSfssJO2zkLQvYGRdxShanFqclJtuZKyXWpSZXFycn6eXl1qyiREYewe3 /FbdwXj5jeMhRgEORiUeXoVktggh1sSy4srcQ4wSHMxKIrxGqewRQrwpiZVVqUX58UWlOanF hxilOViUxHnNVt4PFxJITyxJzU5NLUgtgskycXBKNTCylmzk06lenL6RYclc95vXOgtV/j8P Xm7o38S0JUSy697ZoBcLih9V2Hh27VOdlxF747uox771Z72cJnuFHu+a2Zj8R8tn3xQdxjWh p4rrrN6xPTySeMHuhNf224L/31cePeJ5U+FvdWRmnpG70dq7XbmSkz5NWjHrmuIFNnPNe7vu zHWL3ZKqxFKckWioxVxUnAgAj5jBgrkCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/sgstz9hTZbNrHRwrcUel1eTuk3c>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 12:37:28 -0000

SGkgQ29saW4sDQoNCkJVTkRMRSBpcyBhYm91dCBncm91cGluZyBtLSBsaW5lcywgYW5kIGFzIGFs
bCBtLSBsaW5lcyBzaGFyZXMgdGhlIHNhbWUNCmFkZHJlc3M6cG9ydCBJIHRoaW5rIHRoZSB0ZXh0
IHNob3VsZCBiZSBob3cgdG8gYXNzb2NpYXRlIFJUUCBwYWNrZXRzIHdpdGgNCm0tIGxpbmVzLCB1
c2luZyBNSUQsIFNTUkMgZXRjLg0KDQpIb3cgUlRQIHBhY2tldHMgYXJlIHRoZW4gZ3JvdXBlZCBh
bmQgcHJvY2Vzc2VkIGV0YyBJIHRoaW5rIGlzIG91dHNpZGUgdGhlDQpzY29wZSBvZiBCVU5ETEUu
DQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg0KT24gMTkvMTAvMTYgMTU6MTgsICJDb2xpbiBQ
ZXJraW5zIiA8Y3NwQGNzcGVya2lucy5vcmc+IHdyb3RlOg0KDQo+SGksDQo+DQo+VGhhdCBzcGxp
dCBiZXR3ZWVuIEJVTkRMRSBhbmQgSlNFUCBpcyBmaW5lIHdpdGggbWUuIE15IGNvbmNlcm4sIHRo
b3VnaCwNCj5pcyB0aGF0IGl0oa9zIHN0aWxsIHBocmFzZWQgaW4gdGVybXMgb2YgobBhc3NvY2lh
dGUgcmVjZWl2ZWQgUlRQIHBhY2tldHMNCj53aXRoIGFuIG09IGxpbmWhsSwgcmF0aGVyIHRoYW4g
obBhc3NvY2lhdGUgU1NSQyB3aXRoIGFuIG09IGxpbmWhsS4gRm9yIHRoZQ0KPlJUUCBwcm9jZXNz
aW5nIHRvIHdvcmssIHRoZSBSVFAgYW5kIFJUQ1AgcGFja2V0cyBuZWVkIHRvIGJlIGdyb3VwZWQg
YnkNCj5TU1JDLCBzaW5jZSBSVENQIHByb2Nlc3NpbmcsIHJlcGFpcnMsIGV0Yy4sIGFyZSBkb25l
IHBlciBTU1JDLCB0aGVuIHRoYXQNCj5TU1JDIG1hcHBlZCBpcyBvbnRvIHRoZSBtPSBsaW5lLg0K
Pg0KPkNvbGluDQo+DQo+DQo+DQo+PiBPbiAxNyBPY3QgMjAxNiwgYXQgMTM6MzYsIENocmlzdGVy
IEhvbG1iZXJnDQo+PjxjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+IHdyb3RlOg0KPj4g
DQo+PiBIaSwNCj4+IA0KPj4gV291bGQgdGhlIGZvbGxvd2luZyB3b3JrOg0KPj4gDQo+PiAtIEJV
TkRMRSBkZWZpbmVzIGhvdyB0byBhc3NvY2lhdGUgcmVjZWl2ZWQgUlRQIHBhY2tldHMgd2l0aCBh
biBtLSBsaW5lDQo+PiAtIEpTRVQgZGVmaW5lcyBob3cgdG8gYXNzb2NpYXRlIG0tIGxpbmVzIHdp
dGggUnRwUmVjZWl2ZXJzDQo+PiANCj4+IEluIHRoYXQgY2FzZSwgQlVORExFIHdvdWxkIGRlZmlu
ZSB0aGUgZ2VuZXJpYyBhc3NvY2lhdGUtd2l0aC1tLWxpbmUNCj4+cnVsZXMsDQo+PiB3aGlsZSBK
U0VQIGRlZmluZXMgdGhlIFdlYlJUQyBzcGVjaWZpY3MuDQo+PiANCj4+IFJlZ2FyZHMsDQo+PiAN
Cj4+IENocmlzdGVyDQo+PiANCj4+IA0KPj4gT24gMTcvMTAvMTYgMTI6NTAsICJDb2xpbiBQZXJr
aW5zIiA8Y3NwQGNzcGVya2lucy5vcmc+IHdyb3RlOg0KPj4gDQo+Pj4+IE9uIDE0IE9jdCAyMDE2
LCBhdCAwODo1NCwgTWFnbnVzIFdlc3Rlcmx1bmQNCj4+Pj4gPG1hZ251cy53ZXN0ZXJsdW5kQGVy
aWNzc29uLmNvbT4gd3JvdGU6DQo+Pj4+IA0KPj4+PiBEZW4gMjAxNi0xMC0xMyBrbC4gMTg6MDEs
IHNrcmV2IENocmlzdGVyIEhvbG1iZXJnOg0KPj4+Pj4gSG93ZXZlciwgTWFnbnVzIHRvbGQgbWUg
aXSp9nMgbm90IG5lZWRlZCwgc28gSan2ZCBsaWtlIHRvIGdldCBzb21lDQo+Pj4+PmlucHV0DQo+
Pj4+PiBmcm9tIGhpbS4NCj4+Pj4+IA0KPj4+Pj4gKkZyb206KkN1bGxlbiBKZW5uaW5ncyBbbWFp
bHRvOmZsdWZmeUBpaWkuY2FdDQo+Pj4+PiBUaGF0IGxvb2tzIGFib3V0IHJpZ2h0IGZvciBSVFAg
YnV0IEkgdGhpbmsgaXQgaXMgc3RpbGwgbWlzc2luZyBzdHVmZg0KPj4+Pj4gZm9yDQo+Pj4+PiBS
VENQIGhhbmRsaW5nLiBIZXJlIGlzIHRoZSBjdXJyZW50IHRleHQgd2UgZGlkIGZvciBKU0VQLiBJ
IHByZWZlciB0aGUNCj4+Pj4+IHN0eWxlIGluIHdoaWNoIHlvdSBkZXNjcmliZWQgaXQgY29tcGFy
ZWQgdG8gdGhlIGFsZ29yaXRobSBzdHlsZSBiZWxvdw0KPj4+Pj4gYnV0IEkgdGhpbmsgdGhpcyBt
aWdodCBoZWxwIGZpZ3VyZSBvdXQgd2hhdCB0byB3cml0ZSBmb3IgUlRDUC4NCj4+Pj4+IA0KPj4+
PiANCj4+Pj4gSSBkaXNsaWtlIHRoZSBhbGdvcml0aG1pYyBkZXNjcmlwdGlvbiBKU0VQIGhhcyBi
ZWNhdXNlIGl0IGluc2VydHMNCj4+Pj4gaXRzZWxmIGF0IHBvc2l0aW9uIGluIHRoZSBzdGFjayB3
aGVyZSBJIHdvdWxkIG5vdCBteXNlbGYgaW1wbGVtZW50IHRoZQ0KPj4+PiBiaW5kaW5nIGhhbmRs
aW5nLiBUaGUgaW1wbGVtZW50YXRpb25zIG9mIFJUUCBzdGFja3MgSSBoYXZlIG1hZGUgaGF2ZQ0K
Pj4+PiBuZXZlciBsZXQgdGhlIGZ1bGwgUlRDUCBwYWNrZXRzIGJlIGF2YWlsYWJsZSB0byB0aGUg
YXBwbGljYXRpb24gbGF5ZXIuDQo+Pj4+IEl0IGhhcyBvbmx5IGltcGxlbWVudGVkIGV2ZW50IGFu
ZCByZXF1ZXN0IGJhc2VkIGludGVyZmFjZSB0byBwcm92aWRlDQo+Pj4+dGhlDQo+Pj4+IHRyaWdn
ZXJzIGFuZCBkYXRhIGFzc29jaWF0ZWQgd2l0aCB0aGUgZGlmZmVybmV0IFJUQ1AgcGFja2V0cy4g
VGh1cywNCj4+Pj5mcm9tDQo+Pj4+IG15IHBlcnNwZWN0aXZlIHRoZSByb3V0aW5nIG9mIHRoZSBS
VENQIHBhY2tldHMgYmVjb21lcyBhIHF1ZXN0aW9uIGlmDQo+Pj4+dGhlDQo+Pj4+IFNTUkMgaXMg
Ym91bmQgdG8gdGhlIHJpZ2h0IG09LiBUaGVuIGhhbmRlbCB0aGUgcmVjZWl2ZWQgUlRDUCBwYWNr
ZXRzDQo+Pj4+aW4NCj4+Pj4gdGhhdCBjb250ZXh0Lg0KPj4+PiANCj4+Pj4gU28gd2hhdCBtaWdo
dCBiZSBhIHN1aXRhYmxlIFJUQ1AgY2xhcmlmaWNhdGlvbiByZWdhcmRpbmcgUlRDUCB3b3VsZCBi
ZQ0KPj4+PiB0aGUgZm9sbG93aW5nLg0KPj4+PiANCj4+Pj4gU2ltcGx5IGFkZCBSVENQIGluIHRo
ZSBmb2xsb3dpbmcgc2VudGVuY2U6DQo+Pj4+IA0KPj4+PiAiTGF0ZXIsIHdoZW4gYW4gb2ZmZXJl
ciBvciBhbnN3ZXJlciByZWNlaXZlcyBhbiBSVFAgcGFja2V0IHRoYXQgZG9lcw0KPj4+PiBub3Qg
Y2FycnkgdGhlIGlkZW50aWZpY2F0aW9uLXRhZywgaXQgY2FuIGFzc29jaWF0ZSB0aGUgcGFja2V0
IHdpdGggdGhlDQo+Pj4+IGNvcnJlY3QgIm09IiBsaW5lIHVzaW5nIHRoZSBTU1JDIHZhbHVlLiIN
Cj4+Pj4gDQo+Pj4+IHNvIHRoYXQgaXQgcmVhZHM6DQo+Pj4+IA0KPj4+PiAiTGF0ZXIsIHdoZW4g
YW4gb2ZmZXJlciBvciBhbnN3ZXJlciByZWNlaXZlcyBhbiBSVFAgb3IgUlRDUCBwYWNrZXQNCj4+
Pj50aGF0DQo+Pj4+IGRvZXMgbm90IGNhcnJ5IHRoZSBpZGVudGlmaWNhdGlvbi10YWcsIGl0IGNh
biBhc3NvY2lhdGUgdGhlIHBhY2tldA0KPj4+PndpdGgNCj4+Pj4gdGhlIGNvcnJlY3QgIm09IiBs
aW5lIHVzaW5nIHRoZSBTU1JDIHZhbHVlLiINCj4+Pj4gDQo+Pj4+IFJlZ2FyZGluZyB0aGUgc2Vj
b25kIHBhcmFncmFwaC4gSWYgdGhlIGFzc29jaWF0aW9uIGhhcyBiZWVuIGRvbmUNCj4+Pj4gYWNj
b3JkaW5nIHRvIHRoaXMgcGFydCB0aGVuIGFsc28gdGhlIFJUQ1AgcGFja2V0cyBoYXMgYW4gYXNz
b2NpYXRpb24uDQo+Pj4+SWYNCj4+Pj4gYW4gUlRDUCBwYWNrZXQgYXJyaXZlcyB3aXRoIGEgbm9u
IGFzc29jaWF0ZWQgU1NSQywgdGhlbiBtYW55IFJUQ1ANCj4+Pj4gcGFja2V0cyB0eXBlIGNhbiBz
dGlsbCBiZSBwcm9jZXNzZWQgYW5kIHRoZSBpbmZvcm1hdGlvbiBzdG9yZWQgaW4gdGhlDQo+Pj4+
IFNTUkMgcmVsYXRlZCBpbmZvcm1hdGlvbiB0YWJsZS4gU29tZSB0aGF0IGFyZSBhcHBsaWNhdGlv
biBpbnRlcmFjdGlvbg0KPj4+PiByZWxhdGVkLCBsaWtlIHNvbWUgb2YgdGhlIGZlZWRiYWNrIG1l
c3NhZ2VzIGNhbiBvZiBjb3Vyc2Ugbm90IGJlDQo+Pj4+aGFuZGxlZC4NCj4+Pj4gDQo+Pj4+IE9u
ZSB2ZXJ5IGltcG9ydGFudCBhc3BlY3QgaGVyZSBpcyB0aGF0IHRoZSBiYXNpYyBSVENQIHByb2Nl
c3NpbmcgZG8NCj4+Pj4gbmVlZCB0byBvY2N1ciBmb3IgYWxzbyBub24tYXNzb2NpYXRlZCBTU1JD
cy4gVGhpcyB0byBlbnN1cmUgdGhhdCB0aGUNCj4+Pj4gc2VuZGVyIGdldCB0aGUgUlRDUCBmZWVk
YmFjayBpbmZvcm1hdGlvbiBmb3IgY29uZ2VzdGlvbiBjb250cm9sDQo+Pj4+IHB1cnBvc2VzLiBX
ZSB3YW50IHRoZSB0cmFuc3BvcnQgbGF5ZXIgZnVuY3Rpb25zIHRvIGNvbnRpbnVlIGZ1bmN0aW9u
LA0KPj4+PiBldmVuIGlmIHRoZSBhcHBsaWNhdGlvbiBjYW4ndCBjb25zdW1lIHRoZSBwYWNrZXRz
Lg0KPj4+PiANCj4+Pj4gVGh1cywgSSB3b3VsZCBjb25zaWRlciB0aGF0IHRoZSAidGhlIHBhY2tl
dCBTSE9VTEQgYmUgZHJvcHBlZC4iIG5lZWRzDQo+Pj4+IGFuIGFkZGl0aW9uIHRoYXQgc2F5cyBh
ZnRlciBoYXZpbmcgYmVlbiBwcm9jZXNzZWQgYXMgcmVjZWl2ZWQgYnkgdGhlDQo+Pj4+IFJUQ1Ag
bGF5ZXIuIElmIHdlIGRvbid0IHJlcG9ydCB0aGVtIGFzIHJlY2VpdmVkIHdlIHNrZXcgdGhlIGNv
bmdlc3Rpb24NCj4+Pj4gY29udHJvbCBpbmZvcm1hdGlvbiwgYW5kIGl0IHdpbGwgbWFrZSBhbnkg
Y291cGxlZCBjb25nZXN0aW9uDQo+Pj4+Y29udHJvbGxlcg0KPj4+PiB0aGF0IGxvb2tzIGF0IHRo
ZSBzZXQgb2YgUlRQIHN0cmVhbXMgYmVpbmcgZW1pdHRlZCB0YWtlIHRoZSB3cm9uZw0KPj4+PiBk
ZWNpc2lvbi4gSSBhbHNvIGFzc3VtZXMgdGhhdCBhIGxhY2sgb2YgYXNzb2NpYXRpb24gaXMgaW4g
bW9zdCBjYXNlcyBhDQo+Pj4+IHRlbXBvcmFyeSBpc3N1ZSB0aGF0IHdpbGwgYmUgcmVzb2x2ZWQg
YnkgdGhlIHJlZ3VsYXIgdHJhbnNtaXNzaW9ucy4NCj4+PiANCj4+PiBJIGFncmVlIHdpdGggYWxs
IG9mIHRoaXMuIFRoZSBtYXBwaW5nIHNob3VsZG6p9nQgYmUgZnJvbSBSVFAgb3IgUlRDUA0KPj4+
IHBhY2tldHMgb250byBSdHBSZWNpdmVycy4gVGhlIFJUUCBwcm90b2NvbCByZXF1aXJlcyBSVFAg
YW5kIFJUQ1ANCj4+PnBhY2tldHMNCj4+PiBiZSBhc3NvY2lhdGVkIHRvIGFuIFNTUkMsIGFuZCB0
aGUgbWFwcGluZyBpcyB0byBkZXRlcm1pbmUgd2hhdKn2cyB0aGUNCj4+PnJvbGUNCj4+PiBvZiB0
aGF0IFNTUkMgKGkuZS4sIHRvIG1hcCBmcm9tIFNTUkMgdG8gUnRwUmVjZWl2ZXIpLg0KPj4+IA0K
Pj4+IA0KPj4+IC0tIA0KPj4+IENvbGluIFBlcmtpbnMNCj4+PiBodHRwczovL2NzcGVya2lucy5v
cmcvDQo+Pj4gDQo+Pj4gDQo+Pj4gDQo+Pj4gDQo+PiANCj4NCj4NCj4NCj4tLSANCj5Db2xpbiBQ
ZXJraW5zDQo+aHR0cHM6Ly9jc3BlcmtpbnMub3JnLw0KPg0KPg0KPg0KPg0KDQo=


From nobody Wed Oct 19 05:43:37 2016
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 73174129605 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 05:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.953
X-Spam-Level: 
X-Spam-Status: No, score=-14.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, 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 wEENcUNSEslM for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 05:43:30 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DBE5129507 for <mmusic@ietf.org>; Wed, 19 Oct 2016 05:43:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2123; q=dns/txt; s=iport; t=1476881010; x=1478090610; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=aRSHLePG9kC7rXPT/qAcr9M+o3F0d60NIjiTvQZ5GcM=; b=QpGq9GQaCRrzjyPRBqHXMumWsJN0jzmkcRzBdZ0J14jRwsvTp/uLCqiL yQqLoC54t8Vy5+i1gc5w+0YWoZwWmqW2m8oGIt2Os/NR0E9oCLUQFpHTH MaK0wcsEi/z8dB3XT6pyMiyytZOmFlnPU1sFC2pXgmBu08dx5GbF8cZtv A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D6AgC2aQdY/4oNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgzwBAQEBAR1XKlKNNJZ7lDqCCBwLhTBKAoISOBQBAgEBAQEBAQFiJ0E?= =?us-ascii?q?OhBMBAQQBAQE1NhsjLicwBg0GAgEBiE4Ow24BAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEXBYY9gX0IjHYBBJoLgTuOT4FuhGmDFIYOhxKJbB42VYM6gVYiNIE3hwYBAQE?=
X-IronPort-AV: E=Sophos;i="5.31,514,1473120000"; d="scan'208";a="165084424"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Oct 2016 12:43:29 +0000
Received: from [10.98.149.200] (bxb-fandreas-8817.cisco.com [10.98.149.200]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u9JChTKG017962 for <mmusic@ietf.org>; Wed, 19 Oct 2016 12:43:29 GMT
To: mmusic <mmusic@ietf.org>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <563ec9e6-15eb-49bf-0527-9c068ab1b329@cisco.com>
Date: Wed, 19 Oct 2016 08:43:29 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2L4dtxZXDjupAzk0bor4A7zCdeA>
Subject: [MMUSIC] Rough concensus: Re: 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 12:43:36 -0000

Hi

Following up on the consensus call, we have received 5 responses in 
favor of option a) below, one neutral, and one objection. Looking at the 
document we have noted that backwards compatibility is handled by the 
current text in the document and it also clearly states that it does not 
make current RFC 4572 implementation non-compliant with RFC 4572. Since 
we have not heard of any technical problems with proposal a), nor seen 
any tangible progress on how to address the objection, we are hereby 
declaring rough consensus on option a). We will proceed with the 
publication request for the current draft while duly noting the 
"roughness" of the consensus based on the pending objection as part of 
this.

Thanks

     Flemming & Bo (MMUSIC chairs)


On 10/12/16 6:23 PM, Flemming Andreasen wrote:
> Greetings
>
> There has been quite a bit of discussion on 
> draft-ietf-mmusic-4572-update (currently -07), which had previously 
> completed WGLC when a few concerns were raised. The document currently:
> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
> 2. Updates the preferred cipher-suite with a stronger cipher suite
> 3. Updates RFC 4572.
>
> Item 1 seems to be generally agreeable, whereas items 2 and 3 are not. 
> The chairs are hereby soliciting WG feedback on how to proceed based 
> on the following choices:
>
> a) Proceed with publication of 4572-update-07 in its current form 
> (i.e. covering all 3 items above)
>
> b) Remove item 2 from 4572-update, i.e. do not update the preferred 
> cipher-suite
>
> c) Remove item 3 from 4572-update, i.e. do not indicate that this 
> document constitutes an update to RFC 4572.
>
>
> Note that choice a) is mutually exclusive with b) and c), but b) and 
> c) are not mutually exclusive.
>
> Please let us know your preference wrt to the above no later than 
> Friday October 14th.
>
>
> Thanks
>
>        Flemming & Bo (MMUSIC chairs)
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> .
>


From nobody Wed Oct 19 06:24:53 2016
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 97A50129629 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 06:24:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CtnmrdJmMfu2 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 06:24:50 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AA0E1295E3 for <mmusic@ietf.org>; Wed, 19 Oct 2016 06:18:52 -0700 (PDT)
Received: from [130.209.247.112] (port=56674 helo=mangole.dcs.gla.ac.uk) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1bwqlc-0006sr-Mr; Wed, 19 Oct 2016 14:18:49 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <D42D44E7.11653%christer.holmberg@ericsson.com>
Date: Wed, 19 Oct 2016 14:18:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9483F0F1-F651-4471-9AC0-6AA79EA2480D@csperkins.org>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org> <D42AA198.11408%christer.holmberg@ericsson.com> <A2448DA9-6634-4583-A4B6-040B93371254@csperkins.org> <D42D44E7.11653%christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/WSw83kOPb2UcVsMbQjGd8YOF510>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 13:24:51 -0000

Hi,

> On 19 Oct 2016, at 13:37, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> BUNDLE is about grouping m- lines, and as all m- lines shares the same
> address:port I think the text should be how to associate RTP packets =
with
> m- lines, using MID, SSRC etc.

Sorry, but I think this is fundamentally wrong. BUNDLE associates RTP =
_streams_ with =E2=80=9Cm=3D=E2=80=9C lines; it doesn=E2=80=99t =
associate RTP _packets_ with =E2=80=9Cm=3D=E2=80=9C lines. There=E2=80=99s=
 an important semantic difference between these two that=E2=80=99s =
getting missed.

When RTP and RTCP packets are received, they=E2=80=99re associated with =
an RTP stream, based on, and identified by, their SSRC [RFC7656]. This =
is done whether or not BUNDLE is in use.

The goal of BUNDLE is then to associate those received RTP streams with =
m=3D lines. This might be done based on a signalled mapping from SSRC to =
m=3D line (=E2=80=9Ca=3Dssrc:=E2=80=9D), it might be done using MID, or =
some other means. But, the association is from RTP stream to m=3D line, =
not from RTP packets to m=3D line.

> How RTP packets are then grouped and processed etc I think is outside =
the
> scope of BUNDLE.

Yes, but not in the way you suggest. I think what should happen is:

- The grouping of RTP and RTCP packets into RTP streams happens below =
BUNDLE. An RTP stream is always identified by SSRC, and will have other =
metadata associated with it. That metadata can be sent in RTCP, in RTP =
header extensions, or it can be signalled using =E2=80=9Ca=3Dssrc:=E2=80=9D=
 lines. The SSRC might not be signalled in advance, but still identifies =
the RTP stream.

- BUNDLE then associates those RTP streams with m=3D lines. This mapping =
needs to be defined in terms of RTP streams, not RTP packets, since the =
RTP packets have already been grouped into streams before they reach =
BUNDLE. It should describe how to map an RTP stream with a particular =
SSRC onto an =E2=80=9Cm=3D=E2=80=9C line, based on the metadata =
associated with that RTP stream.=20

- How those m=3D lines relate to higher-level semantics is determined by =
a higher-layer protocol, such as JSEP.

Getting the layering right is important, I think, to have something =
that=E2=80=99s both understandable and extensible:

 RTP Layer  : RTP and RTCP packets -> RTP streams
 SDP BUNDLE : RTP streams -> SDP =E2=80=9Cm=3D" lines
 JSEP       : SDP =E2=80=9Cm=3D" lines -> application-level semantics

I don=E2=80=99t think this will need a big text change, but it is a =
semantic change in how the BUNDLE draft describes the mapping.

Colin



> Regards,
>=20
> Christer
>=20
>=20
> On 19/10/16 15:18, "Colin Perkins" <csp@csperkins.org> wrote:
>=20
>> Hi,
>>=20
>> That split between BUNDLE and JSEP is fine with me. My concern, =
though,
>> is that it=E2=80=99s still phrased in terms of =E2=80=9Cassociate =
received RTP packets
>> with an m=3D line=E2=80=9D, rather than =E2=80=9Cassociate SSRC with =
an m=3D line=E2=80=9D. For the
>> RTP processing to work, the RTP and RTCP packets need to be grouped =
by
>> SSRC, since RTCP processing, repairs, etc., are done per SSRC, then =
that
>> SSRC mapped is onto the m=3D line.
>>=20
>> Colin
>>=20
>>=20
>>=20
>>> On 17 Oct 2016, at 13:36, Christer Holmberg
>>> <christer.holmberg@ericsson.com> wrote:
>>>=20
>>> Hi,
>>>=20
>>> Would the following work:
>>>=20
>>> - BUNDLE defines how to associate received RTP packets with an m- =
line
>>> - JSET defines how to associate m- lines with RtpReceivers
>>>=20
>>> In that case, BUNDLE would define the generic associate-with-m-line
>>> rules,
>>> while JSEP defines the WebRTC specifics.
>>>=20
>>> Regards,
>>>=20
>>> Christer
>>>=20
>>>=20
>>> On 17/10/16 12:50, "Colin Perkins" <csp@csperkins.org> wrote:
>>>=20
>>>>> On 14 Oct 2016, at 08:54, Magnus Westerlund
>>>>> <magnus.westerlund@ericsson.com> wrote:
>>>>>=20
>>>>> Den 2016-10-13 kl. 18:01, skrev Christer Holmberg:
>>>>>> However, Magnus told me it=C2=B9s not needed, so I=C2=B9d like to =
get some
>>>>>> input
>>>>>> from him.
>>>>>>=20
>>>>>> *From:*Cullen Jennings [mailto:fluffy@iii.ca]
>>>>>> That looks about right for RTP but I think it is still missing =
stuff
>>>>>> for
>>>>>> RTCP handling. Here is the current text we did for JSEP. I prefer =
the
>>>>>> style in which you described it compared to the algorithm style =
below
>>>>>> but I think this might help figure out what to write for RTCP.
>>>>>>=20
>>>>>=20
>>>>> I dislike the algorithmic description JSEP has because it inserts
>>>>> itself at position in the stack where I would not myself implement =
the
>>>>> binding handling. The implementations of RTP stacks I have made =
have
>>>>> never let the full RTCP packets be available to the application =
layer.
>>>>> It has only implemented event and request based interface to =
provide
>>>>> the
>>>>> triggers and data associated with the differnet RTCP packets. =
Thus,
>>>>> from
>>>>> my perspective the routing of the RTCP packets becomes a question =
if
>>>>> the
>>>>> SSRC is bound to the right m=3D. Then handel the received RTCP =
packets
>>>>> in
>>>>> that context.
>>>>>=20
>>>>> So what might be a suitable RTCP clarification regarding RTCP =
would be
>>>>> the following.
>>>>>=20
>>>>> Simply add RTCP in the following sentence:
>>>>>=20
>>>>> "Later, when an offerer or answerer receives an RTP packet that =
does
>>>>> not carry the identification-tag, it can associate the packet with =
the
>>>>> correct "m=3D" line using the SSRC value."
>>>>>=20
>>>>> so that it reads:
>>>>>=20
>>>>> "Later, when an offerer or answerer receives an RTP or RTCP packet
>>>>> that
>>>>> does not carry the identification-tag, it can associate the packet
>>>>> with
>>>>> the correct "m=3D" line using the SSRC value."
>>>>>=20
>>>>> Regarding the second paragraph. If the association has been done
>>>>> according to this part then also the RTCP packets has an =
association.
>>>>> If
>>>>> an RTCP packet arrives with a non associated SSRC, then many RTCP
>>>>> packets type can still be processed and the information stored in =
the
>>>>> SSRC related information table. Some that are application =
interaction
>>>>> related, like some of the feedback messages can of course not be
>>>>> handled.
>>>>>=20
>>>>> One very important aspect here is that the basic RTCP processing =
do
>>>>> need to occur for also non-associated SSRCs. This to ensure that =
the
>>>>> sender get the RTCP feedback information for congestion control
>>>>> purposes. We want the transport layer functions to continue =
function,
>>>>> even if the application can't consume the packets.
>>>>>=20
>>>>> Thus, I would consider that the "the packet SHOULD be dropped." =
needs
>>>>> an addition that says after having been processed as received by =
the
>>>>> RTCP layer. If we don't report them as received we skew the =
congestion
>>>>> control information, and it will make any coupled congestion
>>>>> controller
>>>>> that looks at the set of RTP streams being emitted take the wrong
>>>>> decision. I also assumes that a lack of association is in most =
cases a
>>>>> temporary issue that will be resolved by the regular =
transmissions.
>>>>=20
>>>> I agree with all of this. The mapping shouldn=C2=B9t be from RTP or =
RTCP
>>>> packets onto RtpRecivers. The RTP protocol requires RTP and RTCP
>>>> packets
>>>> be associated to an SSRC, and the mapping is to determine what=C2=B9s=
 the
>>>> role
>>>> of that SSRC (i.e., to map from SSRC to RtpReceiver).
>>>>=20
>>>>=20
>>>> --=20
>>>> Colin Perkins
>>>> https://csperkins.org/
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>=20
>>=20
>>=20
>>=20
>> --=20
>> Colin Perkins
>> https://csperkins.org/
>>=20
>>=20
>>=20
>>=20
>=20



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





From nobody Wed Oct 19 06:31:51 2016
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 A5D6A12963D for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 06:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 SYeO2jliO28X for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 06:31:46 -0700 (PDT)
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 C67B5129639 for <mmusic@ietf.org>; Wed, 19 Oct 2016 06:31:45 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-44-580775bf6590
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by  (Symantec Mail Security) with SMTP id FB.91.02458.FB577085; Wed, 19 Oct 2016 15:31:43 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0319.002; Wed, 19 Oct 2016 15:31:42 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
Thread-Index: AQHSJHSivk5Ucbs2BE2kFscuEARQNKCmW5CAgAAxTzCAAOkBgIAE15EAgABieACAAut/gIAAOXAA///XUACAACT74A==
Date: Wed, 19 Oct 2016 13:31:42 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BDBA1FF@ESESSMB209.ericsson.se>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org> <D42AA198.11408%christer.holmberg@ericsson.com> <A2448DA9-6634-4583-A4B6-040B93371254@csperkins.org> <D42D44E7.11653%christer.holmberg@ericsson.com> <9483F0F1-F651-4471-9AC0-6AA79EA2480D@csperkins.org>
In-Reply-To: <9483F0F1-F651-4471-9AC0-6AA79EA2480D@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGbHdQ3d/KXuEwcETlhbLX55gtPiw/gej xdTlj1kcmD2m3b/P5rFkyU8mj8vnPzIGMEdx2aSk5mSWpRbp2yVwZZz//JC14FtoxekTc1kb GO8EdzFyckgImEgsXv2YpYuRi0NIYD2jxPljS9kgnMWMEqc+/ANyODjYBCwkuv9pgzSICKhK 7Dj+jxHEZhaok7j0swvMFhbIkJg/eRsLSLmIQKbEipV+EOVZEvf/rQabwgLUOuWJDEiYV8BX ounLciaITe+YJXqvL2IFSXAKOEqsmLaXBcRmFBCT+H5qDRPEKnGJW0/mM0HcLCCxZM95Zghb VOLl43+sELaSROOSJ6wgu5gFNCXW79KHaFWUmNL9kB1ir6DEyZlPWCYwis5CMnUWQscsJB2z kHQsYGRZxShanFpcnJtuZKSXWpSZXFycn6eXl1qyiREYNQe3/LbawXjwueMhRgEORiUeXoVk tggh1sSy4srcQ4wSHMxKIrzhxewRQrwpiZVVqUX58UWlOanFhxilOViUxHnNVt4PFxJITyxJ zU5NLUgtgskycXBKNTBqP7Kbv9Bl+anKSZrnbn/c3SlzZ8IuwUkqUj+XLDx6/Gziis+Nuz8v 2P1I/Ghv6rkLr0uCV+inGmZ6MoudC5RY5jnnG2PK5eRpRlOfxXHcvnnx96amt2cWd3oWRZ7Y m9zs6HuI8aHks+VnV09oUfj3Of3h9sS0Pb8TnpZcSvW7WsxRt0Fxhm6ApRJLcUaioRZzUXEi ANjPF9eWAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/cGQ4BWuFhFn1jSCAvH7w6CaUaGQ>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 13:31:50 -0000

SGkgQ29saW4sDQoNCkknZCByZWFsbHkgYXBwcmVjaWF0ZSBpZiB5b3UgY291bGQgcHJvdmlkZSB0
ZXh0LCBieSBlLW1haWwsIGJ5IGEgcHVsbCByZXF1ZXN0LCBvciBob3dldmVyIHlvdSB3YW50IDop
DQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpG
cm9tOiBDb2xpbiBQZXJraW5zIFttYWlsdG86Y3NwQGNzcGVya2lucy5vcmddIA0KU2VudDogMTkg
T2N0b2JlciAyMDE2IDE2OjE5DQpUbzogQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1i
ZXJnQGVyaWNzc29uLmNvbT4NCkNjOiBNYWdudXMgV2VzdGVybHVuZCA8bWFnbnVzLndlc3Rlcmx1
bmRAZXJpY3Nzb24uY29tPjsgQ3VsbGVuIEplbm5pbmdzIDxmbHVmZnlAaWlpLmNhPjsgbW11c2lj
QGlldGYub3JnDQpTdWJqZWN0OiBSZTogW01NVVNJQ10gUmV2aWV3IG9mIGRyYWZ0LWlldGYtbW11
c2ljLXNkcC1idW5kbGUtbmVnb3RpYXRpb24tMzIgLSBSVFAgZGVtdXggLSBQdWxsIFJlcXVlc3QN
Cg0KSGksDQoNCj4gT24gMTkgT2N0IDIwMTYsIGF0IDEzOjM3LCBDaHJpc3RlciBIb2xtYmVyZyA8
Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPiB3cm90ZToNCj4gDQo+IEJVTkRMRSBpcyBh
Ym91dCBncm91cGluZyBtLSBsaW5lcywgYW5kIGFzIGFsbCBtLSBsaW5lcyBzaGFyZXMgdGhlIHNh
bWUgDQo+IGFkZHJlc3M6cG9ydCBJIHRoaW5rIHRoZSB0ZXh0IHNob3VsZCBiZSBob3cgdG8gYXNz
b2NpYXRlIFJUUCBwYWNrZXRzIA0KPiB3aXRoDQo+IG0tIGxpbmVzLCB1c2luZyBNSUQsIFNTUkMg
ZXRjLg0KDQpTb3JyeSwgYnV0IEkgdGhpbmsgdGhpcyBpcyBmdW5kYW1lbnRhbGx5IHdyb25nLiBC
VU5ETEUgYXNzb2NpYXRlcyBSVFAgX3N0cmVhbXNfIHdpdGgg4oCcbT3igJwgbGluZXM7IGl0IGRv
ZXNu4oCZdCBhc3NvY2lhdGUgUlRQIF9wYWNrZXRzXyB3aXRoIOKAnG094oCcIGxpbmVzLiBUaGVy
ZeKAmXMgYW4gaW1wb3J0YW50IHNlbWFudGljIGRpZmZlcmVuY2UgYmV0d2VlbiB0aGVzZSB0d28g
dGhhdOKAmXMgZ2V0dGluZyBtaXNzZWQuDQoNCldoZW4gUlRQIGFuZCBSVENQIHBhY2tldHMgYXJl
IHJlY2VpdmVkLCB0aGV54oCZcmUgYXNzb2NpYXRlZCB3aXRoIGFuIFJUUCBzdHJlYW0sIGJhc2Vk
IG9uLCBhbmQgaWRlbnRpZmllZCBieSwgdGhlaXIgU1NSQyBbUkZDNzY1Nl0uIFRoaXMgaXMgZG9u
ZSB3aGV0aGVyIG9yIG5vdCBCVU5ETEUgaXMgaW4gdXNlLg0KDQpUaGUgZ29hbCBvZiBCVU5ETEUg
aXMgdGhlbiB0byBhc3NvY2lhdGUgdGhvc2UgcmVjZWl2ZWQgUlRQIHN0cmVhbXMgd2l0aCBtPSBs
aW5lcy4gVGhpcyBtaWdodCBiZSBkb25lIGJhc2VkIG9uIGEgc2lnbmFsbGVkIG1hcHBpbmcgZnJv
bSBTU1JDIHRvIG09IGxpbmUgKOKAnGE9c3NyYzrigJ0pLCBpdCBtaWdodCBiZSBkb25lIHVzaW5n
IE1JRCwgb3Igc29tZSBvdGhlciBtZWFucy4gQnV0LCB0aGUgYXNzb2NpYXRpb24gaXMgZnJvbSBS
VFAgc3RyZWFtIHRvIG09IGxpbmUsIG5vdCBmcm9tIFJUUCBwYWNrZXRzIHRvIG09IGxpbmUuDQoN
Cj4gSG93IFJUUCBwYWNrZXRzIGFyZSB0aGVuIGdyb3VwZWQgYW5kIHByb2Nlc3NlZCBldGMgSSB0
aGluayBpcyBvdXRzaWRlIA0KPiB0aGUgc2NvcGUgb2YgQlVORExFLg0KDQpZZXMsIGJ1dCBub3Qg
aW4gdGhlIHdheSB5b3Ugc3VnZ2VzdC4gSSB0aGluayB3aGF0IHNob3VsZCBoYXBwZW4gaXM6DQoN
Ci0gVGhlIGdyb3VwaW5nIG9mIFJUUCBhbmQgUlRDUCBwYWNrZXRzIGludG8gUlRQIHN0cmVhbXMg
aGFwcGVucyBiZWxvdyBCVU5ETEUuIEFuIFJUUCBzdHJlYW0gaXMgYWx3YXlzIGlkZW50aWZpZWQg
YnkgU1NSQywgYW5kIHdpbGwgaGF2ZSBvdGhlciBtZXRhZGF0YSBhc3NvY2lhdGVkIHdpdGggaXQu
IFRoYXQgbWV0YWRhdGEgY2FuIGJlIHNlbnQgaW4gUlRDUCwgaW4gUlRQIGhlYWRlciBleHRlbnNp
b25zLCBvciBpdCBjYW4gYmUgc2lnbmFsbGVkIHVzaW5nIOKAnGE9c3NyYzrigJ0gbGluZXMuIFRo
ZSBTU1JDIG1pZ2h0IG5vdCBiZSBzaWduYWxsZWQgaW4gYWR2YW5jZSwgYnV0IHN0aWxsIGlkZW50
aWZpZXMgdGhlIFJUUCBzdHJlYW0uDQoNCi0gQlVORExFIHRoZW4gYXNzb2NpYXRlcyB0aG9zZSBS
VFAgc3RyZWFtcyB3aXRoIG09IGxpbmVzLiBUaGlzIG1hcHBpbmcgbmVlZHMgdG8gYmUgZGVmaW5l
ZCBpbiB0ZXJtcyBvZiBSVFAgc3RyZWFtcywgbm90IFJUUCBwYWNrZXRzLCBzaW5jZSB0aGUgUlRQ
IHBhY2tldHMgaGF2ZSBhbHJlYWR5IGJlZW4gZ3JvdXBlZCBpbnRvIHN0cmVhbXMgYmVmb3JlIHRo
ZXkgcmVhY2ggQlVORExFLiBJdCBzaG91bGQgZGVzY3JpYmUgaG93IHRvIG1hcCBhbiBSVFAgc3Ry
ZWFtIHdpdGggYSBwYXJ0aWN1bGFyIFNTUkMgb250byBhbiDigJxtPeKAnCBsaW5lLCBiYXNlZCBv
biB0aGUgbWV0YWRhdGEgYXNzb2NpYXRlZCB3aXRoIHRoYXQgUlRQIHN0cmVhbS4gDQoNCi0gSG93
IHRob3NlIG09IGxpbmVzIHJlbGF0ZSB0byBoaWdoZXItbGV2ZWwgc2VtYW50aWNzIGlzIGRldGVy
bWluZWQgYnkgYSBoaWdoZXItbGF5ZXIgcHJvdG9jb2wsIHN1Y2ggYXMgSlNFUC4NCg0KR2V0dGlu
ZyB0aGUgbGF5ZXJpbmcgcmlnaHQgaXMgaW1wb3J0YW50LCBJIHRoaW5rLCB0byBoYXZlIHNvbWV0
aGluZyB0aGF04oCZcyBib3RoIHVuZGVyc3RhbmRhYmxlIGFuZCBleHRlbnNpYmxlOg0KDQogUlRQ
IExheWVyICA6IFJUUCBhbmQgUlRDUCBwYWNrZXRzIC0+IFJUUCBzdHJlYW1zICBTRFAgQlVORExF
IDogUlRQIHN0cmVhbXMgLT4gU0RQIOKAnG09IiBsaW5lcw0KIEpTRVAgICAgICAgOiBTRFAg4oCc
bT0iIGxpbmVzIC0+IGFwcGxpY2F0aW9uLWxldmVsIHNlbWFudGljcw0KDQpJIGRvbuKAmXQgdGhp
bmsgdGhpcyB3aWxsIG5lZWQgYSBiaWcgdGV4dCBjaGFuZ2UsIGJ1dCBpdCBpcyBhIHNlbWFudGlj
IGNoYW5nZSBpbiBob3cgdGhlIEJVTkRMRSBkcmFmdCBkZXNjcmliZXMgdGhlIG1hcHBpbmcuDQoN
CkNvbGluDQoNCg0KDQo+IFJlZ2FyZHMsDQo+IA0KPiBDaHJpc3Rlcg0KPiANCj4gDQo+IE9uIDE5
LzEwLzE2IDE1OjE4LCAiQ29saW4gUGVya2lucyIgPGNzcEBjc3BlcmtpbnMub3JnPiB3cm90ZToN
Cj4gDQo+PiBIaSwNCj4+IA0KPj4gVGhhdCBzcGxpdCBiZXR3ZWVuIEJVTkRMRSBhbmQgSlNFUCBp
cyBmaW5lIHdpdGggbWUuIE15IGNvbmNlcm4sIA0KPj4gdGhvdWdoLCBpcyB0aGF0IGl04oCZcyBz
dGlsbCBwaHJhc2VkIGluIHRlcm1zIG9mIOKAnGFzc29jaWF0ZSByZWNlaXZlZCANCj4+IFJUUCBw
YWNrZXRzIHdpdGggYW4gbT0gbGluZeKAnSwgcmF0aGVyIHRoYW4g4oCcYXNzb2NpYXRlIFNTUkMg
d2l0aCBhbiBtPSANCj4+IGxpbmXigJ0uIEZvciB0aGUgUlRQIHByb2Nlc3NpbmcgdG8gd29yaywg
dGhlIFJUUCBhbmQgUlRDUCBwYWNrZXRzIG5lZWQgDQo+PiB0byBiZSBncm91cGVkIGJ5IFNTUkMs
IHNpbmNlIFJUQ1AgcHJvY2Vzc2luZywgcmVwYWlycywgZXRjLiwgYXJlIGRvbmUgDQo+PiBwZXIg
U1NSQywgdGhlbiB0aGF0IFNTUkMgbWFwcGVkIGlzIG9udG8gdGhlIG09IGxpbmUuDQo+PiANCj4+
IENvbGluDQo+PiANCj4+IA0KPj4gDQo+Pj4gT24gMTcgT2N0IDIwMTYsIGF0IDEzOjM2LCBDaHJp
c3RlciBIb2xtYmVyZyANCj4+PiA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPiB3cm90
ZToNCj4+PiANCj4+PiBIaSwNCj4+PiANCj4+PiBXb3VsZCB0aGUgZm9sbG93aW5nIHdvcms6DQo+
Pj4gDQo+Pj4gLSBCVU5ETEUgZGVmaW5lcyBob3cgdG8gYXNzb2NpYXRlIHJlY2VpdmVkIFJUUCBw
YWNrZXRzIHdpdGggYW4gbS0gDQo+Pj4gbGluZQ0KPj4+IC0gSlNFVCBkZWZpbmVzIGhvdyB0byBh
c3NvY2lhdGUgbS0gbGluZXMgd2l0aCBSdHBSZWNlaXZlcnMNCj4+PiANCj4+PiBJbiB0aGF0IGNh
c2UsIEJVTkRMRSB3b3VsZCBkZWZpbmUgdGhlIGdlbmVyaWMgYXNzb2NpYXRlLXdpdGgtbS1saW5l
IA0KPj4+IHJ1bGVzLCB3aGlsZSBKU0VQIGRlZmluZXMgdGhlIFdlYlJUQyBzcGVjaWZpY3MuDQo+
Pj4gDQo+Pj4gUmVnYXJkcywNCj4+PiANCj4+PiBDaHJpc3Rlcg0KPj4+IA0KPj4+IA0KPj4+IE9u
IDE3LzEwLzE2IDEyOjUwLCAiQ29saW4gUGVya2lucyIgPGNzcEBjc3BlcmtpbnMub3JnPiB3cm90
ZToNCj4+PiANCj4+Pj4+IE9uIDE0IE9jdCAyMDE2LCBhdCAwODo1NCwgTWFnbnVzIFdlc3Rlcmx1
bmQgDQo+Pj4+PiA8bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPiB3cm90ZToNCj4+Pj4+
IA0KPj4+Pj4gRGVuIDIwMTYtMTAtMTMga2wuIDE4OjAxLCBza3JldiBDaHJpc3RlciBIb2xtYmVy
ZzoNCj4+Pj4+PiBIb3dldmVyLCBNYWdudXMgdG9sZCBtZSBpdMK5cyBub3QgbmVlZGVkLCBzbyBJ
wrlkIGxpa2UgdG8gZ2V0IHNvbWUgDQo+Pj4+Pj4gaW5wdXQgZnJvbSBoaW0uDQo+Pj4+Pj4gDQo+
Pj4+Pj4gKkZyb206KkN1bGxlbiBKZW5uaW5ncyBbbWFpbHRvOmZsdWZmeUBpaWkuY2FdIFRoYXQg
bG9va3MgYWJvdXQgDQo+Pj4+Pj4gcmlnaHQgZm9yIFJUUCBidXQgSSB0aGluayBpdCBpcyBzdGls
bCBtaXNzaW5nIHN0dWZmIGZvciBSVENQIA0KPj4+Pj4+IGhhbmRsaW5nLiBIZXJlIGlzIHRoZSBj
dXJyZW50IHRleHQgd2UgZGlkIGZvciBKU0VQLiBJIHByZWZlciB0aGUgDQo+Pj4+Pj4gc3R5bGUg
aW4gd2hpY2ggeW91IGRlc2NyaWJlZCBpdCBjb21wYXJlZCB0byB0aGUgYWxnb3JpdGhtIHN0eWxl
IA0KPj4+Pj4+IGJlbG93IGJ1dCBJIHRoaW5rIHRoaXMgbWlnaHQgaGVscCBmaWd1cmUgb3V0IHdo
YXQgdG8gd3JpdGUgZm9yIFJUQ1AuDQo+Pj4+Pj4gDQo+Pj4+PiANCj4+Pj4+IEkgZGlzbGlrZSB0
aGUgYWxnb3JpdGhtaWMgZGVzY3JpcHRpb24gSlNFUCBoYXMgYmVjYXVzZSBpdCBpbnNlcnRzIA0K
Pj4+Pj4gaXRzZWxmIGF0IHBvc2l0aW9uIGluIHRoZSBzdGFjayB3aGVyZSBJIHdvdWxkIG5vdCBt
eXNlbGYgaW1wbGVtZW50IA0KPj4+Pj4gdGhlIGJpbmRpbmcgaGFuZGxpbmcuIFRoZSBpbXBsZW1l
bnRhdGlvbnMgb2YgUlRQIHN0YWNrcyBJIGhhdmUgDQo+Pj4+PiBtYWRlIGhhdmUgbmV2ZXIgbGV0
IHRoZSBmdWxsIFJUQ1AgcGFja2V0cyBiZSBhdmFpbGFibGUgdG8gdGhlIGFwcGxpY2F0aW9uIGxh
eWVyLg0KPj4+Pj4gSXQgaGFzIG9ubHkgaW1wbGVtZW50ZWQgZXZlbnQgYW5kIHJlcXVlc3QgYmFz
ZWQgaW50ZXJmYWNlIHRvIA0KPj4+Pj4gcHJvdmlkZSB0aGUgdHJpZ2dlcnMgYW5kIGRhdGEgYXNz
b2NpYXRlZCB3aXRoIHRoZSBkaWZmZXJuZXQgUlRDUCANCj4+Pj4+IHBhY2tldHMuIFRodXMsIGZy
b20gbXkgcGVyc3BlY3RpdmUgdGhlIHJvdXRpbmcgb2YgdGhlIFJUQ1AgcGFja2V0cyANCj4+Pj4+
IGJlY29tZXMgYSBxdWVzdGlvbiBpZiB0aGUgU1NSQyBpcyBib3VuZCB0byB0aGUgcmlnaHQgbT0u
IFRoZW4gDQo+Pj4+PiBoYW5kZWwgdGhlIHJlY2VpdmVkIFJUQ1AgcGFja2V0cyBpbiB0aGF0IGNv
bnRleHQuDQo+Pj4+PiANCj4+Pj4+IFNvIHdoYXQgbWlnaHQgYmUgYSBzdWl0YWJsZSBSVENQIGNs
YXJpZmljYXRpb24gcmVnYXJkaW5nIFJUQ1AgDQo+Pj4+PiB3b3VsZCBiZSB0aGUgZm9sbG93aW5n
Lg0KPj4+Pj4gDQo+Pj4+PiBTaW1wbHkgYWRkIFJUQ1AgaW4gdGhlIGZvbGxvd2luZyBzZW50ZW5j
ZToNCj4+Pj4+IA0KPj4+Pj4gIkxhdGVyLCB3aGVuIGFuIG9mZmVyZXIgb3IgYW5zd2VyZXIgcmVj
ZWl2ZXMgYW4gUlRQIHBhY2tldCB0aGF0IA0KPj4+Pj4gZG9lcyBub3QgY2FycnkgdGhlIGlkZW50
aWZpY2F0aW9uLXRhZywgaXQgY2FuIGFzc29jaWF0ZSB0aGUgcGFja2V0IA0KPj4+Pj4gd2l0aCB0
aGUgY29ycmVjdCAibT0iIGxpbmUgdXNpbmcgdGhlIFNTUkMgdmFsdWUuIg0KPj4+Pj4gDQo+Pj4+
PiBzbyB0aGF0IGl0IHJlYWRzOg0KPj4+Pj4gDQo+Pj4+PiAiTGF0ZXIsIHdoZW4gYW4gb2ZmZXJl
ciBvciBhbnN3ZXJlciByZWNlaXZlcyBhbiBSVFAgb3IgUlRDUCBwYWNrZXQgDQo+Pj4+PiB0aGF0
IGRvZXMgbm90IGNhcnJ5IHRoZSBpZGVudGlmaWNhdGlvbi10YWcsIGl0IGNhbiBhc3NvY2lhdGUg
dGhlIA0KPj4+Pj4gcGFja2V0IHdpdGggdGhlIGNvcnJlY3QgIm09IiBsaW5lIHVzaW5nIHRoZSBT
U1JDIHZhbHVlLiINCj4+Pj4+IA0KPj4+Pj4gUmVnYXJkaW5nIHRoZSBzZWNvbmQgcGFyYWdyYXBo
LiBJZiB0aGUgYXNzb2NpYXRpb24gaGFzIGJlZW4gZG9uZSANCj4+Pj4+IGFjY29yZGluZyB0byB0
aGlzIHBhcnQgdGhlbiBhbHNvIHRoZSBSVENQIHBhY2tldHMgaGFzIGFuIGFzc29jaWF0aW9uLg0K
Pj4+Pj4gSWYNCj4+Pj4+IGFuIFJUQ1AgcGFja2V0IGFycml2ZXMgd2l0aCBhIG5vbiBhc3NvY2lh
dGVkIFNTUkMsIHRoZW4gbWFueSBSVENQIA0KPj4+Pj4gcGFja2V0cyB0eXBlIGNhbiBzdGlsbCBi
ZSBwcm9jZXNzZWQgYW5kIHRoZSBpbmZvcm1hdGlvbiBzdG9yZWQgaW4gDQo+Pj4+PiB0aGUgU1NS
QyByZWxhdGVkIGluZm9ybWF0aW9uIHRhYmxlLiBTb21lIHRoYXQgYXJlIGFwcGxpY2F0aW9uIA0K
Pj4+Pj4gaW50ZXJhY3Rpb24gcmVsYXRlZCwgbGlrZSBzb21lIG9mIHRoZSBmZWVkYmFjayBtZXNz
YWdlcyBjYW4gb2YgDQo+Pj4+PiBjb3Vyc2Ugbm90IGJlIGhhbmRsZWQuDQo+Pj4+PiANCj4+Pj4+
IE9uZSB2ZXJ5IGltcG9ydGFudCBhc3BlY3QgaGVyZSBpcyB0aGF0IHRoZSBiYXNpYyBSVENQIHBy
b2Nlc3NpbmcgDQo+Pj4+PiBkbyBuZWVkIHRvIG9jY3VyIGZvciBhbHNvIG5vbi1hc3NvY2lhdGVk
IFNTUkNzLiBUaGlzIHRvIGVuc3VyZSANCj4+Pj4+IHRoYXQgdGhlIHNlbmRlciBnZXQgdGhlIFJU
Q1AgZmVlZGJhY2sgaW5mb3JtYXRpb24gZm9yIGNvbmdlc3Rpb24gDQo+Pj4+PiBjb250cm9sIHB1
cnBvc2VzLiBXZSB3YW50IHRoZSB0cmFuc3BvcnQgbGF5ZXIgZnVuY3Rpb25zIHRvIA0KPj4+Pj4g
Y29udGludWUgZnVuY3Rpb24sIGV2ZW4gaWYgdGhlIGFwcGxpY2F0aW9uIGNhbid0IGNvbnN1bWUg
dGhlIHBhY2tldHMuDQo+Pj4+PiANCj4+Pj4+IFRodXMsIEkgd291bGQgY29uc2lkZXIgdGhhdCB0
aGUgInRoZSBwYWNrZXQgU0hPVUxEIGJlIGRyb3BwZWQuIiANCj4+Pj4+IG5lZWRzIGFuIGFkZGl0
aW9uIHRoYXQgc2F5cyBhZnRlciBoYXZpbmcgYmVlbiBwcm9jZXNzZWQgYXMgDQo+Pj4+PiByZWNl
aXZlZCBieSB0aGUgUlRDUCBsYXllci4gSWYgd2UgZG9uJ3QgcmVwb3J0IHRoZW0gYXMgcmVjZWl2
ZWQgd2UgDQo+Pj4+PiBza2V3IHRoZSBjb25nZXN0aW9uIGNvbnRyb2wgaW5mb3JtYXRpb24sIGFu
ZCBpdCB3aWxsIG1ha2UgYW55IA0KPj4+Pj4gY291cGxlZCBjb25nZXN0aW9uIGNvbnRyb2xsZXIg
dGhhdCBsb29rcyBhdCB0aGUgc2V0IG9mIFJUUCBzdHJlYW1zIA0KPj4+Pj4gYmVpbmcgZW1pdHRl
ZCB0YWtlIHRoZSB3cm9uZyBkZWNpc2lvbi4gSSBhbHNvIGFzc3VtZXMgdGhhdCBhIGxhY2sgDQo+
Pj4+PiBvZiBhc3NvY2lhdGlvbiBpcyBpbiBtb3N0IGNhc2VzIGEgdGVtcG9yYXJ5IGlzc3VlIHRo
YXQgd2lsbCBiZSANCj4+Pj4+IHJlc29sdmVkIGJ5IHRoZSByZWd1bGFyIHRyYW5zbWlzc2lvbnMu
DQo+Pj4+IA0KPj4+PiBJIGFncmVlIHdpdGggYWxsIG9mIHRoaXMuIFRoZSBtYXBwaW5nIHNob3Vs
ZG7CuXQgYmUgZnJvbSBSVFAgb3IgUlRDUCANCj4+Pj4gcGFja2V0cyBvbnRvIFJ0cFJlY2l2ZXJz
LiBUaGUgUlRQIHByb3RvY29sIHJlcXVpcmVzIFJUUCBhbmQgUlRDUCANCj4+Pj4gcGFja2V0cyBi
ZSBhc3NvY2lhdGVkIHRvIGFuIFNTUkMsIGFuZCB0aGUgbWFwcGluZyBpcyB0byBkZXRlcm1pbmUg
DQo+Pj4+IHdoYXTCuXMgdGhlIHJvbGUgb2YgdGhhdCBTU1JDIChpLmUuLCB0byBtYXAgZnJvbSBT
U1JDIHRvIA0KPj4+PiBSdHBSZWNlaXZlcikuDQo+Pj4+IA0KPj4+PiANCj4+Pj4gLS0NCj4+Pj4g
Q29saW4gUGVya2lucw0KPj4+PiBodHRwczovL2NzcGVya2lucy5vcmcvDQo+Pj4+IA0KPj4+PiAN
Cj4+Pj4gDQo+Pj4+IA0KPj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gLS0NCj4+IENvbGluIFBlcmtp
bnMNCj4+IGh0dHBzOi8vY3NwZXJraW5zLm9yZy8NCj4+IA0KPj4gDQo+PiANCj4+IA0KPiANCg0K
DQoNCi0tDQpDb2xpbiBQZXJraW5zDQpodHRwczovL2NzcGVya2lucy5vcmcvDQoNCg0KDQoNCg==


From nobody Wed Oct 19 06:37:09 2016
Return-Path: <magnus.westerlund@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 E932C12973E for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 06:37:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 C-tCVNfborC8 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 06:37:06 -0700 (PDT)
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 A7F0C1295CF for <mmusic@ietf.org>; Wed, 19 Oct 2016 06:37:05 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-98-580776ffc214
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by  (Symantec Mail Security) with SMTP id 68.E2.02458.FF677085; Wed, 19 Oct 2016 15:37:04 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.59) with Microsoft SMTP Server id 14.3.319.2; Wed, 19 Oct 2016 15:36:55 +0200
To: Colin Perkins <csp@csperkins.org>, Christer Holmberg <christer.holmberg@ericsson.com>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org> <D42AA198.11408%christer.holmberg@ericsson.com> <A2448DA9-6634-4583-A4B6-040B93371254@csperkins.org> <D42D44E7.11653%christer.holmberg@ericsson.com> <9483F0F1-F651-4471-9AC0-6AA79EA2480D@csperkins.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <35f4d9dd-7abb-ea0a-7a22-a6eb9d1b1e7a@ericsson.com>
Date: Wed, 19 Oct 2016 15:36:54 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <9483F0F1-F651-4471-9AC0-6AA79EA2480D@csperkins.org>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHLMWRmVeSWpSXmKPExsUyM2K7pS5DOXuEQecedovlL08wWnxY/4PR YuryxywOzB7T7t9n81iy5CeTx+XzHxkDmKO4bFJSczLLUov07RK4Ml6uvM5ScNShouHuUrYG xikmXYwcHBICJhKrj2p3MXJxCAmsZ5S4OmETO4SznFHi+MO/LF2MnBzCAhkSLS+7GEFsEYFo iTtvrrNAFL1jlui9vogVJMEs4CHx/fM0ZhCbTcBC4uaPRjaQDbwC9hInGrNBwiwCqhINUzaw gdiiAjES1589ArN5BQQlTs58AraLU8BRYsW0vSwQIy0kZs4/zwhhy0s0b50NNl5IQFuioamD dQKjwCwk7bOQtMxC0rKAkXkVo2hxanFxbrqRkV5qUWZycXF+nl5easkmRmCoHtzy22oH48Hn jocYBTgYlXh4FZLZIoRYE8uKK3MPMUpwMCuJ8C4qZY8Q4k1JrKxKLcqPLyrNSS0+xCjNwaIk zmu28n64kEB6YklqdmpqQWoRTJaJg1OqgZHJvzlsxzqPDzKRvNt+XDy+8/O+vX8e8z05FVjz 4fqNBY9N1s4SPLOkY0HXzK9RC6xaC/ZtsqpjyqszX+fBtsrKbV72w9fvbnctYniyirdY1OSt VX2QedzfNtGDlj3OaafNzMvYl+4O2SZfE7uKnde99R+/wz7X0Iu/uZUVV2dvVEq+7HhJMF6J pTgj0VCLuag4EQApTHccUQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FlVOxbCaATLNk5wp9WvWiIPLouY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 13:37:08 -0000

Hi,

I just want to say that I support what Colin expresses below.

Cheers

Magnus


Den 2016-10-19 kl. 15:18, skrev Colin Perkins:
> Hi,
>
>> On 19 Oct 2016, at 13:37, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
>>
>> BUNDLE is about grouping m- lines, and as all m- lines shares the same
>> address:port I think the text should be how to associate RTP packets with
>> m- lines, using MID, SSRC etc.
>
> Sorry, but I think this is fundamentally wrong. BUNDLE associates RTP _streams_ with â€œm=â€œ lines; it doesnâ€™t associate RTP _packets_ with â€œm=â€œ lines. Thereâ€™s an important semantic difference between these two thatâ€™s getting missed.
>
> When RTP and RTCP packets are received, theyâ€™re associated with an RTP stream, based on, and identified by, their SSRC [RFC7656]. This is done whether or not BUNDLE is in use.
>
> The goal of BUNDLE is then to associate those received RTP streams with m= lines. This might be done based on a signalled mapping from SSRC to m= line (â€œa=ssrc:â€�), it might be done using MID, or some other means. But, the association is from RTP stream to m= line, not from RTP packets to m= line.
>
>> How RTP packets are then grouped and processed etc I think is outside the
>> scope of BUNDLE.
>
> Yes, but not in the way you suggest. I think what should happen is:
>
> - The grouping of RTP and RTCP packets into RTP streams happens below BUNDLE. An RTP stream is always identified by SSRC, and will have other metadata associated with it. That metadata can be sent in RTCP, in RTP header extensions, or it can be signalled using â€œa=ssrc:â€� lines. The SSRC might not be signalled in advance, but still identifies the RTP stream.
>
> - BUNDLE then associates those RTP streams with m= lines. This mapping needs to be defined in terms of RTP streams, not RTP packets, since the RTP packets have already been grouped into streams before they reach BUNDLE. It should describe how to map an RTP stream with a particular SSRC onto an â€œm=â€œ line, based on the metadata associated with that RTP stream.
>
> - How those m= lines relate to higher-level semantics is determined by a higher-layer protocol, such as JSEP.
>
> Getting the layering right is important, I think, to have something thatâ€™s both understandable and extensible:
>
>  RTP Layer  : RTP and RTCP packets -> RTP streams
>  SDP BUNDLE : RTP streams -> SDP â€œm=" lines
>  JSEP       : SDP â€œm=" lines -> application-level semantics
>
> I donâ€™t think this will need a big text change, but it is a semantic change in how the BUNDLE draft describes the mapping.
>
> Colin
>
>
>
>> Regards,
>>
>> Christer
>>
>>
>> On 19/10/16 15:18, "Colin Perkins" <csp@csperkins.org> wrote:
>>
>>> Hi,
>>>
>>> That split between BUNDLE and JSEP is fine with me. My concern, though,
>>> is that itâ€™s still phrased in terms of â€œassociate received RTP packets
>>> with an m= lineâ€�, rather than â€œassociate SSRC with an m= lineâ€�. For the
>>> RTP processing to work, the RTP and RTCP packets need to be grouped by
>>> SSRC, since RTCP processing, repairs, etc., are done per SSRC, then that
>>> SSRC mapped is onto the m= line.
>>>
>>> Colin
>>>
>>>
>>>
>>>> On 17 Oct 2016, at 13:36, Christer Holmberg
>>>> <christer.holmberg@ericsson.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Would the following work:
>>>>
>>>> - BUNDLE defines how to associate received RTP packets with an m- line
>>>> - JSET defines how to associate m- lines with RtpReceivers
>>>>
>>>> In that case, BUNDLE would define the generic associate-with-m-line
>>>> rules,
>>>> while JSEP defines the WebRTC specifics.
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>>
>>>> On 17/10/16 12:50, "Colin Perkins" <csp@csperkins.org> wrote:
>>>>
>>>>>> On 14 Oct 2016, at 08:54, Magnus Westerlund
>>>>>> <magnus.westerlund@ericsson.com> wrote:
>>>>>>
>>>>>> Den 2016-10-13 kl. 18:01, skrev Christer Holmberg:
>>>>>>> However, Magnus told me itÂ¹s not needed, so IÂ¹d like to get some
>>>>>>> input
>>>>>>> from him.
>>>>>>>
>>>>>>> *From:*Cullen Jennings [mailto:fluffy@iii.ca]
>>>>>>> That looks about right for RTP but I think it is still missing stuff
>>>>>>> for
>>>>>>> RTCP handling. Here is the current text we did for JSEP. I prefer the
>>>>>>> style in which you described it compared to the algorithm style below
>>>>>>> but I think this might help figure out what to write for RTCP.
>>>>>>>
>>>>>>
>>>>>> I dislike the algorithmic description JSEP has because it inserts
>>>>>> itself at position in the stack where I would not myself implement the
>>>>>> binding handling. The implementations of RTP stacks I have made have
>>>>>> never let the full RTCP packets be available to the application layer.
>>>>>> It has only implemented event and request based interface to provide
>>>>>> the
>>>>>> triggers and data associated with the differnet RTCP packets. Thus,
>>>>>> from
>>>>>> my perspective the routing of the RTCP packets becomes a question if
>>>>>> the
>>>>>> SSRC is bound to the right m=. Then handel the received RTCP packets
>>>>>> in
>>>>>> that context.
>>>>>>
>>>>>> So what might be a suitable RTCP clarification regarding RTCP would be
>>>>>> the following.
>>>>>>
>>>>>> Simply add RTCP in the following sentence:
>>>>>>
>>>>>> "Later, when an offerer or answerer receives an RTP packet that does
>>>>>> not carry the identification-tag, it can associate the packet with the
>>>>>> correct "m=" line using the SSRC value."
>>>>>>
>>>>>> so that it reads:
>>>>>>
>>>>>> "Later, when an offerer or answerer receives an RTP or RTCP packet
>>>>>> that
>>>>>> does not carry the identification-tag, it can associate the packet
>>>>>> with
>>>>>> the correct "m=" line using the SSRC value."
>>>>>>
>>>>>> Regarding the second paragraph. If the association has been done
>>>>>> according to this part then also the RTCP packets has an association.
>>>>>> If
>>>>>> an RTCP packet arrives with a non associated SSRC, then many RTCP
>>>>>> packets type can still be processed and the information stored in the
>>>>>> SSRC related information table. Some that are application interaction
>>>>>> related, like some of the feedback messages can of course not be
>>>>>> handled.
>>>>>>
>>>>>> One very important aspect here is that the basic RTCP processing do
>>>>>> need to occur for also non-associated SSRCs. This to ensure that the
>>>>>> sender get the RTCP feedback information for congestion control
>>>>>> purposes. We want the transport layer functions to continue function,
>>>>>> even if the application can't consume the packets.
>>>>>>
>>>>>> Thus, I would consider that the "the packet SHOULD be dropped." needs
>>>>>> an addition that says after having been processed as received by the
>>>>>> RTCP layer. If we don't report them as received we skew the congestion
>>>>>> control information, and it will make any coupled congestion
>>>>>> controller
>>>>>> that looks at the set of RTP streams being emitted take the wrong
>>>>>> decision. I also assumes that a lack of association is in most cases a
>>>>>> temporary issue that will be resolved by the regular transmissions.
>>>>>
>>>>> I agree with all of this. The mapping shouldnÂ¹t be from RTP or RTCP
>>>>> packets onto RtpRecivers. The RTP protocol requires RTP and RTCP
>>>>> packets
>>>>> be associated to an SSRC, and the mapping is to determine whatÂ¹s the
>>>>> role
>>>>> of that SSRC (i.e., to map from SSRC to RtpReceiver).
>>>>>
>>>>>
>>>>> --
>>>>> Colin Perkins
>>>>> https://csperkins.org/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Colin Perkins
>>> https://csperkins.org/
>>>
>>>
>>>
>>>
>>
>
>
>


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Wed Oct 19 06:48:09 2016
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 7FDF9129984 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 06:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 z4Eq51u6hYxe for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 06:48:05 -0700 (PDT)
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 EF961129952 for <mmusic@ietf.org>; Wed, 19 Oct 2016 06:48:04 -0700 (PDT)
X-AuditID: c1b4fb3a-aa3ff7000000099a-0a-58077993ab41
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by  (Symantec Mail Security) with SMTP id 77.C5.02458.39977085; Wed, 19 Oct 2016 15:48:03 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0319.002; Wed, 19 Oct 2016 15:48:01 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
Thread-Index: AQHSJHSivk5Ucbs2BE2kFscuEARQNKCmW5CAgAAxTzCAAOkBgIAE15EAgABieACAAut/gIAAOXAA///XUACAAAUdAIAAJIXA
Date: Wed, 19 Oct 2016 13:48:01 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BDBA235@ESESSMB209.ericsson.se>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org> <D42AA198.11408%christer.holmberg@ericsson.com> <A2448DA9-6634-4583-A4B6-040B93371254@csperkins.org> <D42D44E7.11653%christer.holmberg@ericsson.com> <9483F0F1-F651-4471-9AC0-6AA79EA2480D@csperkins.org> <35f4d9dd-7abb-ea0a-7a22-a6eb9d1b1e7a@ericsson.com>
In-Reply-To: <35f4d9dd-7abb-ea0a-7a22-a6eb9d1b1e7a@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphkeLIzCtJLcpLzFFi42KZGbHdSXdyJXuEwdMOKYvlL08wWnxY/4PR YuryxywOzB7T7t9n81iy5CeTx+XzHxkDmKO4bFJSczLLUov07RK4Mp5OXs5U0BdZMenoR8YG xhdhXYycHBICJhIvd81m72Lk4hASWM8oMfP2LWYIZzGjxKzbj4AcDg42AQuJ7n/aIA0iAtES 0ybsZgaxmQU8JL5/ngZmCwtkSMyfvI0FpFxEIFNixUo/iPI8idO3+thAbBYBVYnfU06A2bwC vhIt+w+wQqxawiLxseElE0iCU8BB4uDRh6wgNqOAmMT3U2uYIHaJS9x6Mp8J4mgBiSV7zjND 2KISLx//Y4WwlSQalzxhBbmBWUBTYv0ufYhWRYkp3Q/ZIfYKSpyc+YRlAqPoLCRTZyF0zELS MQtJxwJGllWMosWpxcW56UZGeqlFmcnFxfl5enmpJZsYgXFzcMtvqx2MB587HmIU4GBU4uFV SGaLEGJNLCuuzD3EKMHBrCTCy1nBHiHEm5JYWZValB9fVJqTWnyIUZqDRUmc12zl/XAhgfTE ktTs1NSC1CKYLBMHp1QDY2W6x9tZAkvfLqmRXX+dcdFPluf3v4uuv+Sg45de+ntD9TV5uY+y Cp4uCW+qpx3XZiytKH8503eT7nYxcavX/Fxtn18WHJp8M7zrpmNwQ7LgE4nWtdO5vpZ0xjZP 0pw18Wzl2fISu0efSmQu8Iqk2NUW5Odusd8c/iW/8cy2G2kityQfXEiqV2Ipzkg01GIuKk4E AA3vo+GXAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/JwD7QmyJgRtwG2Hwe0WqFisxNOA>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 13:48:07 -0000

SGksDQoNCj5JIGp1c3Qgd2FudCB0byBzYXkgdGhhdCBJIHN1cHBvcnQgd2hhdCBDb2xpbiBleHBy
ZXNzZXMgYmVsb3cuDQoNCkF3ZXNvbWUgLSBmZWVsIGZyZWUgdG8gaGVscCBDb2xpbiBwdXR0aW5n
IHRvZ2V0aGVyIHRoZSBwdWxsIHJlcXVlc3QgOikNCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0K
DQoNCkRlbiAyMDE2LTEwLTE5IGtsLiAxNToxOCwgc2tyZXYgQ29saW4gUGVya2luczoNCj4gSGks
DQo+DQo+PiBPbiAxOSBPY3QgMjAxNiwgYXQgMTM6MzcsIENocmlzdGVyIEhvbG1iZXJnIDxjaHJp
c3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+IHdyb3RlOg0KPj4NCj4+IEJVTkRMRSBpcyBhYm91
dCBncm91cGluZyBtLSBsaW5lcywgYW5kIGFzIGFsbCBtLSBsaW5lcyBzaGFyZXMgdGhlIA0KPj4g
c2FtZSBhZGRyZXNzOnBvcnQgSSB0aGluayB0aGUgdGV4dCBzaG91bGQgYmUgaG93IHRvIGFzc29j
aWF0ZSBSVFAgDQo+PiBwYWNrZXRzIHdpdGgNCj4+IG0tIGxpbmVzLCB1c2luZyBNSUQsIFNTUkMg
ZXRjLg0KPg0KPiBTb3JyeSwgYnV0IEkgdGhpbmsgdGhpcyBpcyBmdW5kYW1lbnRhbGx5IHdyb25n
LiBCVU5ETEUgYXNzb2NpYXRlcyBSVFAgX3N0cmVhbXNfIHdpdGgg4oCcbT3igJwgbGluZXM7IGl0
IGRvZXNu4oCZdCBhc3NvY2lhdGUgUlRQIF9wYWNrZXRzXyB3aXRoIOKAnG094oCcIGxpbmVzLiBU
aGVyZeKAmXMgYW4gaW1wb3J0YW50IHNlbWFudGljIGRpZmZlcmVuY2UgYmV0d2VlbiB0aGVzZSB0
d28gdGhhdOKAmXMgZ2V0dGluZyBtaXNzZWQuDQo+DQo+IFdoZW4gUlRQIGFuZCBSVENQIHBhY2tl
dHMgYXJlIHJlY2VpdmVkLCB0aGV54oCZcmUgYXNzb2NpYXRlZCB3aXRoIGFuIFJUUCBzdHJlYW0s
IGJhc2VkIG9uLCBhbmQgaWRlbnRpZmllZCBieSwgdGhlaXIgU1NSQyBbUkZDNzY1Nl0uIFRoaXMg
aXMgZG9uZSB3aGV0aGVyIG9yIG5vdCBCVU5ETEUgaXMgaW4gdXNlLg0KPg0KPiBUaGUgZ29hbCBv
ZiBCVU5ETEUgaXMgdGhlbiB0byBhc3NvY2lhdGUgdGhvc2UgcmVjZWl2ZWQgUlRQIHN0cmVhbXMg
d2l0aCBtPSBsaW5lcy4gVGhpcyBtaWdodCBiZSBkb25lIGJhc2VkIG9uIGEgc2lnbmFsbGVkIG1h
cHBpbmcgZnJvbSBTU1JDIHRvIG09IGxpbmUgKOKAnGE9c3NyYzrigJ0pLCBpdCBtaWdodCBiZSBk
b25lIHVzaW5nIE1JRCwgb3Igc29tZSBvdGhlciBtZWFucy4gQnV0LCB0aGUgYXNzb2NpYXRpb24g
aXMgZnJvbSBSVFAgc3RyZWFtIHRvIG09IGxpbmUsIG5vdCBmcm9tIFJUUCBwYWNrZXRzIHRvIG09
IGxpbmUuDQo+DQo+PiBIb3cgUlRQIHBhY2tldHMgYXJlIHRoZW4gZ3JvdXBlZCBhbmQgcHJvY2Vz
c2VkIGV0YyBJIHRoaW5rIGlzIG91dHNpZGUgDQo+PiB0aGUgc2NvcGUgb2YgQlVORExFLg0KPg0K
PiBZZXMsIGJ1dCBub3QgaW4gdGhlIHdheSB5b3Ugc3VnZ2VzdC4gSSB0aGluayB3aGF0IHNob3Vs
ZCBoYXBwZW4gaXM6DQo+DQo+IC0gVGhlIGdyb3VwaW5nIG9mIFJUUCBhbmQgUlRDUCBwYWNrZXRz
IGludG8gUlRQIHN0cmVhbXMgaGFwcGVucyBiZWxvdyBCVU5ETEUuIEFuIFJUUCBzdHJlYW0gaXMg
YWx3YXlzIGlkZW50aWZpZWQgYnkgU1NSQywgYW5kIHdpbGwgaGF2ZSBvdGhlciBtZXRhZGF0YSBh
c3NvY2lhdGVkIHdpdGggaXQuIFRoYXQgbWV0YWRhdGEgY2FuIGJlIHNlbnQgaW4gUlRDUCwgaW4g
UlRQIGhlYWRlciBleHRlbnNpb25zLCBvciBpdCBjYW4gYmUgc2lnbmFsbGVkIHVzaW5nIOKAnGE9
c3NyYzrigJ0gbGluZXMuIFRoZSBTU1JDIG1pZ2h0IG5vdCBiZSBzaWduYWxsZWQgaW4gYWR2YW5j
ZSwgYnV0IHN0aWxsIGlkZW50aWZpZXMgdGhlIFJUUCBzdHJlYW0uDQo+DQo+IC0gQlVORExFIHRo
ZW4gYXNzb2NpYXRlcyB0aG9zZSBSVFAgc3RyZWFtcyB3aXRoIG09IGxpbmVzLiBUaGlzIG1hcHBp
bmcgbmVlZHMgdG8gYmUgZGVmaW5lZCBpbiB0ZXJtcyBvZiBSVFAgc3RyZWFtcywgbm90IFJUUCBw
YWNrZXRzLCBzaW5jZSB0aGUgUlRQIHBhY2tldHMgaGF2ZSBhbHJlYWR5IGJlZW4gZ3JvdXBlZCBp
bnRvIHN0cmVhbXMgYmVmb3JlIHRoZXkgcmVhY2ggQlVORExFLiBJdCBzaG91bGQgZGVzY3JpYmUg
aG93IHRvIG1hcCBhbiBSVFAgc3RyZWFtIHdpdGggYSBwYXJ0aWN1bGFyIFNTUkMgb250byBhbiDi
gJxtPeKAnCBsaW5lLCBiYXNlZCBvbiB0aGUgbWV0YWRhdGEgYXNzb2NpYXRlZCB3aXRoIHRoYXQg
UlRQIHN0cmVhbS4NCj4NCj4gLSBIb3cgdGhvc2UgbT0gbGluZXMgcmVsYXRlIHRvIGhpZ2hlci1s
ZXZlbCBzZW1hbnRpY3MgaXMgZGV0ZXJtaW5lZCBieSBhIGhpZ2hlci1sYXllciBwcm90b2NvbCwg
c3VjaCBhcyBKU0VQLg0KPg0KPiBHZXR0aW5nIHRoZSBsYXllcmluZyByaWdodCBpcyBpbXBvcnRh
bnQsIEkgdGhpbmssIHRvIGhhdmUgc29tZXRoaW5nIHRoYXTigJlzIGJvdGggdW5kZXJzdGFuZGFi
bGUgYW5kIGV4dGVuc2libGU6DQo+DQo+ICBSVFAgTGF5ZXIgIDogUlRQIGFuZCBSVENQIHBhY2tl
dHMgLT4gUlRQIHN0cmVhbXMgIFNEUCBCVU5ETEUgOiBSVFAgDQo+IHN0cmVhbXMgLT4gU0RQIOKA
nG09IiBsaW5lcw0KPiAgSlNFUCAgICAgICA6IFNEUCDigJxtPSIgbGluZXMgLT4gYXBwbGljYXRp
b24tbGV2ZWwgc2VtYW50aWNzDQo+DQo+IEkgZG9u4oCZdCB0aGluayB0aGlzIHdpbGwgbmVlZCBh
IGJpZyB0ZXh0IGNoYW5nZSwgYnV0IGl0IGlzIGEgc2VtYW50aWMgY2hhbmdlIGluIGhvdyB0aGUg
QlVORExFIGRyYWZ0IGRlc2NyaWJlcyB0aGUgbWFwcGluZy4NCj4NCj4gQ29saW4NCj4NCj4NCj4N
Cj4+IFJlZ2FyZHMsDQo+Pg0KPj4gQ2hyaXN0ZXINCj4+DQo+Pg0KPj4gT24gMTkvMTAvMTYgMTU6
MTgsICJDb2xpbiBQZXJraW5zIiA8Y3NwQGNzcGVya2lucy5vcmc+IHdyb3RlOg0KPj4NCj4+PiBI
aSwNCj4+Pg0KPj4+IFRoYXQgc3BsaXQgYmV0d2VlbiBCVU5ETEUgYW5kIEpTRVAgaXMgZmluZSB3
aXRoIG1lLiBNeSBjb25jZXJuLCANCj4+PiB0aG91Z2gsIGlzIHRoYXQgaXTigJlzIHN0aWxsIHBo
cmFzZWQgaW4gdGVybXMgb2Yg4oCcYXNzb2NpYXRlIHJlY2VpdmVkIA0KPj4+IFJUUCBwYWNrZXRz
IHdpdGggYW4gbT0gbGluZeKAnSwgcmF0aGVyIHRoYW4g4oCcYXNzb2NpYXRlIFNTUkMgd2l0aCBh
biBtPSANCj4+PiBsaW5l4oCdLiBGb3IgdGhlIFJUUCBwcm9jZXNzaW5nIHRvIHdvcmssIHRoZSBS
VFAgYW5kIFJUQ1AgcGFja2V0cyBuZWVkIA0KPj4+IHRvIGJlIGdyb3VwZWQgYnkgU1NSQywgc2lu
Y2UgUlRDUCBwcm9jZXNzaW5nLCByZXBhaXJzLCBldGMuLCBhcmUgDQo+Pj4gZG9uZSBwZXIgU1NS
QywgdGhlbiB0aGF0IFNTUkMgbWFwcGVkIGlzIG9udG8gdGhlIG09IGxpbmUuDQo+Pj4NCj4+PiBD
b2xpbg0KPj4+DQo+Pj4NCj4+Pg0KPj4+PiBPbiAxNyBPY3QgMjAxNiwgYXQgMTM6MzYsIENocmlz
dGVyIEhvbG1iZXJnIA0KPj4+PiA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPiB3cm90
ZToNCj4+Pj4NCj4+Pj4gSGksDQo+Pj4+DQo+Pj4+IFdvdWxkIHRoZSBmb2xsb3dpbmcgd29yazoN
Cj4+Pj4NCj4+Pj4gLSBCVU5ETEUgZGVmaW5lcyBob3cgdG8gYXNzb2NpYXRlIHJlY2VpdmVkIFJU
UCBwYWNrZXRzIHdpdGggYW4gbS0gDQo+Pj4+IGxpbmUNCj4+Pj4gLSBKU0VUIGRlZmluZXMgaG93
IHRvIGFzc29jaWF0ZSBtLSBsaW5lcyB3aXRoIFJ0cFJlY2VpdmVycw0KPj4+Pg0KPj4+PiBJbiB0
aGF0IGNhc2UsIEJVTkRMRSB3b3VsZCBkZWZpbmUgdGhlIGdlbmVyaWMgYXNzb2NpYXRlLXdpdGgt
bS1saW5lIA0KPj4+PiBydWxlcywgd2hpbGUgSlNFUCBkZWZpbmVzIHRoZSBXZWJSVEMgc3BlY2lm
aWNzLg0KPj4+Pg0KPj4+PiBSZWdhcmRzLA0KPj4+Pg0KPj4+PiBDaHJpc3Rlcg0KPj4+Pg0KPj4+
Pg0KPj4+PiBPbiAxNy8xMC8xNiAxMjo1MCwgIkNvbGluIFBlcmtpbnMiIDxjc3BAY3NwZXJraW5z
Lm9yZz4gd3JvdGU6DQo+Pj4+DQo+Pj4+Pj4gT24gMTQgT2N0IDIwMTYsIGF0IDA4OjU0LCBNYWdu
dXMgV2VzdGVybHVuZCANCj4+Pj4+PiA8bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPiB3
cm90ZToNCj4+Pj4+Pg0KPj4+Pj4+IERlbiAyMDE2LTEwLTEzIGtsLiAxODowMSwgc2tyZXYgQ2hy
aXN0ZXIgSG9sbWJlcmc6DQo+Pj4+Pj4+IEhvd2V2ZXIsIE1hZ251cyB0b2xkIG1lIGl0wrlzIG5v
dCBuZWVkZWQsIHNvIEnCuWQgbGlrZSB0byBnZXQgc29tZSANCj4+Pj4+Pj4gaW5wdXQgZnJvbSBo
aW0uDQo+Pj4+Pj4+DQo+Pj4+Pj4+ICpGcm9tOipDdWxsZW4gSmVubmluZ3MgW21haWx0bzpmbHVm
ZnlAaWlpLmNhXSBUaGF0IGxvb2tzIGFib3V0IA0KPj4+Pj4+PiByaWdodCBmb3IgUlRQIGJ1dCBJ
IHRoaW5rIGl0IGlzIHN0aWxsIG1pc3Npbmcgc3R1ZmYgZm9yIFJUQ1AgDQo+Pj4+Pj4+IGhhbmRs
aW5nLiBIZXJlIGlzIHRoZSBjdXJyZW50IHRleHQgd2UgZGlkIGZvciBKU0VQLiBJIHByZWZlciB0
aGUgDQo+Pj4+Pj4+IHN0eWxlIGluIHdoaWNoIHlvdSBkZXNjcmliZWQgaXQgY29tcGFyZWQgdG8g
dGhlIGFsZ29yaXRobSBzdHlsZSANCj4+Pj4+Pj4gYmVsb3cgYnV0IEkgdGhpbmsgdGhpcyBtaWdo
dCBoZWxwIGZpZ3VyZSBvdXQgd2hhdCB0byB3cml0ZSBmb3IgUlRDUC4NCj4+Pj4+Pj4NCj4+Pj4+
Pg0KPj4+Pj4+IEkgZGlzbGlrZSB0aGUgYWxnb3JpdGhtaWMgZGVzY3JpcHRpb24gSlNFUCBoYXMg
YmVjYXVzZSBpdCBpbnNlcnRzIA0KPj4+Pj4+IGl0c2VsZiBhdCBwb3NpdGlvbiBpbiB0aGUgc3Rh
Y2sgd2hlcmUgSSB3b3VsZCBub3QgbXlzZWxmIA0KPj4+Pj4+IGltcGxlbWVudCB0aGUgYmluZGlu
ZyBoYW5kbGluZy4gVGhlIGltcGxlbWVudGF0aW9ucyBvZiBSVFAgc3RhY2tzIA0KPj4+Pj4+IEkg
aGF2ZSBtYWRlIGhhdmUgbmV2ZXIgbGV0IHRoZSBmdWxsIFJUQ1AgcGFja2V0cyBiZSBhdmFpbGFi
bGUgdG8gdGhlIGFwcGxpY2F0aW9uIGxheWVyLg0KPj4+Pj4+IEl0IGhhcyBvbmx5IGltcGxlbWVu
dGVkIGV2ZW50IGFuZCByZXF1ZXN0IGJhc2VkIGludGVyZmFjZSB0byANCj4+Pj4+PiBwcm92aWRl
IHRoZSB0cmlnZ2VycyBhbmQgZGF0YSBhc3NvY2lhdGVkIHdpdGggdGhlIGRpZmZlcm5ldCBSVENQ
IA0KPj4+Pj4+IHBhY2tldHMuIFRodXMsIGZyb20gbXkgcGVyc3BlY3RpdmUgdGhlIHJvdXRpbmcg
b2YgdGhlIFJUQ1AgDQo+Pj4+Pj4gcGFja2V0cyBiZWNvbWVzIGEgcXVlc3Rpb24gaWYgdGhlIFNT
UkMgaXMgYm91bmQgdG8gdGhlIHJpZ2h0IG09LiANCj4+Pj4+PiBUaGVuIGhhbmRlbCB0aGUgcmVj
ZWl2ZWQgUlRDUCBwYWNrZXRzIGluIHRoYXQgY29udGV4dC4NCj4+Pj4+Pg0KPj4+Pj4+IFNvIHdo
YXQgbWlnaHQgYmUgYSBzdWl0YWJsZSBSVENQIGNsYXJpZmljYXRpb24gcmVnYXJkaW5nIFJUQ1Ag
DQo+Pj4+Pj4gd291bGQgYmUgdGhlIGZvbGxvd2luZy4NCj4+Pj4+Pg0KPj4+Pj4+IFNpbXBseSBh
ZGQgUlRDUCBpbiB0aGUgZm9sbG93aW5nIHNlbnRlbmNlOg0KPj4+Pj4+DQo+Pj4+Pj4gIkxhdGVy
LCB3aGVuIGFuIG9mZmVyZXIgb3IgYW5zd2VyZXIgcmVjZWl2ZXMgYW4gUlRQIHBhY2tldCB0aGF0
IA0KPj4+Pj4+IGRvZXMgbm90IGNhcnJ5IHRoZSBpZGVudGlmaWNhdGlvbi10YWcsIGl0IGNhbiBh
c3NvY2lhdGUgdGhlIA0KPj4+Pj4+IHBhY2tldCB3aXRoIHRoZSBjb3JyZWN0ICJtPSIgbGluZSB1
c2luZyB0aGUgU1NSQyB2YWx1ZS4iDQo+Pj4+Pj4NCj4+Pj4+PiBzbyB0aGF0IGl0IHJlYWRzOg0K
Pj4+Pj4+DQo+Pj4+Pj4gIkxhdGVyLCB3aGVuIGFuIG9mZmVyZXIgb3IgYW5zd2VyZXIgcmVjZWl2
ZXMgYW4gUlRQIG9yIFJUQ1AgDQo+Pj4+Pj4gcGFja2V0IHRoYXQgZG9lcyBub3QgY2FycnkgdGhl
IGlkZW50aWZpY2F0aW9uLXRhZywgaXQgY2FuIA0KPj4+Pj4+IGFzc29jaWF0ZSB0aGUgcGFja2V0
IHdpdGggdGhlIGNvcnJlY3QgIm09IiBsaW5lIHVzaW5nIHRoZSBTU1JDIA0KPj4+Pj4+IHZhbHVl
LiINCj4+Pj4+Pg0KPj4+Pj4+IFJlZ2FyZGluZyB0aGUgc2Vjb25kIHBhcmFncmFwaC4gSWYgdGhl
IGFzc29jaWF0aW9uIGhhcyBiZWVuIGRvbmUgDQo+Pj4+Pj4gYWNjb3JkaW5nIHRvIHRoaXMgcGFy
dCB0aGVuIGFsc28gdGhlIFJUQ1AgcGFja2V0cyBoYXMgYW4gYXNzb2NpYXRpb24uDQo+Pj4+Pj4g
SWYNCj4+Pj4+PiBhbiBSVENQIHBhY2tldCBhcnJpdmVzIHdpdGggYSBub24gYXNzb2NpYXRlZCBT
U1JDLCB0aGVuIG1hbnkgUlRDUCANCj4+Pj4+PiBwYWNrZXRzIHR5cGUgY2FuIHN0aWxsIGJlIHBy
b2Nlc3NlZCBhbmQgdGhlIGluZm9ybWF0aW9uIHN0b3JlZCBpbiANCj4+Pj4+PiB0aGUgU1NSQyBy
ZWxhdGVkIGluZm9ybWF0aW9uIHRhYmxlLiBTb21lIHRoYXQgYXJlIGFwcGxpY2F0aW9uIA0KPj4+
Pj4+IGludGVyYWN0aW9uIHJlbGF0ZWQsIGxpa2Ugc29tZSBvZiB0aGUgZmVlZGJhY2sgbWVzc2Fn
ZXMgY2FuIG9mIA0KPj4+Pj4+IGNvdXJzZSBub3QgYmUgaGFuZGxlZC4NCj4+Pj4+Pg0KPj4+Pj4+
IE9uZSB2ZXJ5IGltcG9ydGFudCBhc3BlY3QgaGVyZSBpcyB0aGF0IHRoZSBiYXNpYyBSVENQIHBy
b2Nlc3NpbmcgDQo+Pj4+Pj4gZG8gbmVlZCB0byBvY2N1ciBmb3IgYWxzbyBub24tYXNzb2NpYXRl
ZCBTU1JDcy4gVGhpcyB0byBlbnN1cmUgDQo+Pj4+Pj4gdGhhdCB0aGUgc2VuZGVyIGdldCB0aGUg
UlRDUCBmZWVkYmFjayBpbmZvcm1hdGlvbiBmb3IgY29uZ2VzdGlvbiANCj4+Pj4+PiBjb250cm9s
IHB1cnBvc2VzLiBXZSB3YW50IHRoZSB0cmFuc3BvcnQgbGF5ZXIgZnVuY3Rpb25zIHRvIA0KPj4+
Pj4+IGNvbnRpbnVlIGZ1bmN0aW9uLCBldmVuIGlmIHRoZSBhcHBsaWNhdGlvbiBjYW4ndCBjb25z
dW1lIHRoZSBwYWNrZXRzLg0KPj4+Pj4+DQo+Pj4+Pj4gVGh1cywgSSB3b3VsZCBjb25zaWRlciB0
aGF0IHRoZSAidGhlIHBhY2tldCBTSE9VTEQgYmUgZHJvcHBlZC4iIA0KPj4+Pj4+IG5lZWRzIGFu
IGFkZGl0aW9uIHRoYXQgc2F5cyBhZnRlciBoYXZpbmcgYmVlbiBwcm9jZXNzZWQgYXMgDQo+Pj4+
Pj4gcmVjZWl2ZWQgYnkgdGhlIFJUQ1AgbGF5ZXIuIElmIHdlIGRvbid0IHJlcG9ydCB0aGVtIGFz
IHJlY2VpdmVkIA0KPj4+Pj4+IHdlIHNrZXcgdGhlIGNvbmdlc3Rpb24gY29udHJvbCBpbmZvcm1h
dGlvbiwgYW5kIGl0IHdpbGwgbWFrZSBhbnkgDQo+Pj4+Pj4gY291cGxlZCBjb25nZXN0aW9uIGNv
bnRyb2xsZXIgdGhhdCBsb29rcyBhdCB0aGUgc2V0IG9mIFJUUCANCj4+Pj4+PiBzdHJlYW1zIGJl
aW5nIGVtaXR0ZWQgdGFrZSB0aGUgd3JvbmcgZGVjaXNpb24uIEkgYWxzbyBhc3N1bWVzIA0KPj4+
Pj4+IHRoYXQgYSBsYWNrIG9mIGFzc29jaWF0aW9uIGlzIGluIG1vc3QgY2FzZXMgYSB0ZW1wb3Jh
cnkgaXNzdWUgDQo+Pj4+Pj4gdGhhdCB3aWxsIGJlIHJlc29sdmVkIGJ5IHRoZSByZWd1bGFyIHRy
YW5zbWlzc2lvbnMuDQo+Pj4+Pg0KPj4+Pj4gSSBhZ3JlZSB3aXRoIGFsbCBvZiB0aGlzLiBUaGUg
bWFwcGluZyBzaG91bGRuwrl0IGJlIGZyb20gUlRQIG9yIA0KPj4+Pj4gUlRDUCBwYWNrZXRzIG9u
dG8gUnRwUmVjaXZlcnMuIFRoZSBSVFAgcHJvdG9jb2wgcmVxdWlyZXMgUlRQIGFuZCANCj4+Pj4+
IFJUQ1AgcGFja2V0cyBiZSBhc3NvY2lhdGVkIHRvIGFuIFNTUkMsIGFuZCB0aGUgbWFwcGluZyBp
cyB0byANCj4+Pj4+IGRldGVybWluZSB3aGF0wrlzIHRoZSByb2xlIG9mIHRoYXQgU1NSQyAoaS5l
LiwgdG8gbWFwIGZyb20gU1NSQyB0byANCj4+Pj4+IFJ0cFJlY2VpdmVyKS4NCj4+Pj4+DQo+Pj4+
Pg0KPj4+Pj4gLS0NCj4+Pj4+IENvbGluIFBlcmtpbnMNCj4+Pj4+IGh0dHBzOi8vY3NwZXJraW5z
Lm9yZy8NCj4+Pj4+DQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+DQo+Pj4+DQo+Pj4NCj4+Pg0KPj4+DQo+
Pj4gLS0NCj4+PiBDb2xpbiBQZXJraW5zDQo+Pj4gaHR0cHM6Ly9jc3BlcmtpbnMub3JnLw0KPj4+
DQo+Pj4NCj4+Pg0KPj4+DQo+Pg0KPg0KPg0KPg0KDQoNCi0tIA0KDQpNYWdudXMgV2VzdGVybHVu
ZA0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tDQpTZXJ2aWNlcywgTWVkaWEgYW5kIE5ldHdvcmsgZmVhdHVyZXMs
IEVyaWNzc29uIFJlc2VhcmNoIEVBQi9UWE0NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkVyaWNzc29uIEFCICAg
ICAgICAgICAgICAgICB8IFBob25lICArNDYgMTAgNzE0ODI4Nw0KRsOkcsO2Z2F0YW4gNiAgICAg
ICAgICAgICAgICAgfCBNb2JpbGUgKzQ2IDczIDA5NDkwNzkNClNFLTE2NCA4MCBTdG9ja2hvbG0s
IFN3ZWRlbiB8IG1haWx0bzogbWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tDQotLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQoNCg==


From nobody Wed Oct 19 08:25:00 2016
Return-Path: <eckelcu@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 C8F0D12966F; Wed, 19 Oct 2016 08:24:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.951
X-Spam-Level: 
X-Spam-Status: No, score=-14.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 6AiA9c8w7co7; Wed, 19 Oct 2016 08:24:58 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DC9D1299C8; Wed, 19 Oct 2016 08:24:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9154; q=dns/txt; s=iport; t=1476890698; x=1478100298; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=EOf7R3ccITiR985IhBAri3fDGBlkBsbFnrF0nMBKegE=; b=OyA+Y8N3d4Dg+EJgKAxJNNZA5vqkNkfztqPdw4JylFmIs2WHVZijmRbV 77iRhBJDeSWgkqeVW2iIyt7gAJVEUEnedV2mUJhH7YcWVw0a7I+YPEIAZ 25zy8burbsvMSPhP3SoNFETyV/l2Wa8EbWrd/0iBzaHSCFOzZPMdxFtcj M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DjAQDmjwdY/5RdJa1cDgwBAQEBAgEBA?= =?us-ascii?q?QEIAQEBAYMINgEBAQEBHVd9B40tpiGFFYIIhiECGoFePxQBAgEBAQEBAQFiKIR?= =?us-ascii?q?jAQEEI1YQAgEIDjEDAgICMBQRAgQBDQWIUrZ0jQgBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEciDoIglCEGREBgyAsgi8FjkWLSAGJLoZbT48qkH0BHjYdOIQ5O3KGHYE?= =?us-ascii?q?ggQABAQE?=
X-IronPort-AV: E=Sophos;i="5.31,514,1473120000";  d="scan'208,217";a="159697908"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Oct 2016 15:24:54 +0000
Received: from XCH-RCD-017.cisco.com (xch-rcd-017.cisco.com [173.37.102.27]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u9JFOsT1003110 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 19 Oct 2016 15:24:54 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-RCD-017.cisco.com (173.37.102.27) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 19 Oct 2016 10:24:53 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Wed, 19 Oct 2016 10:24:53 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: James Swan <jmswan@iol.unh.edu>, "hackathon@ietf.org" <hackathon@ietf.org>
Thread-Topic: [hackathon] IPv6 Transition and NAT traversal network setup
Thread-Index: AQHSI9QnsZKJF5Lvj0Ow+NQhW1UK86Cv0LAA
Date: Wed, 19 Oct 2016 15:24:53 +0000
Message-ID: <54AF05DE-827C-4776-8F58-7A4D6FC21BBA@cisco.com>
References: <CAKp+0qG+_O6G3hPNT5Q7ubXrw2T2G4OaMmrec9C4WdPv0mziag@mail.gmail.com>
In-Reply-To: <CAKp+0qG+_O6G3hPNT5Q7ubXrw2T2G4OaMmrec9C4WdPv0mziag@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1b.0.161010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.182.35]
Content-Type: multipart/alternative; boundary="_000_54AF05DE827C47768F587A4D6FC21BBAciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/X124eTosJDMT4_KuLXwcZNk-2Q0>
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] [hackathon] IPv6 Transition and NAT traversal network setup
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 15:25:00 -0000

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

SGkgSmFtZXMsDQoNClRoYW5rcyBmb3IgeW91ciBlbWFpbCBhbmQgc29ycnkgZm9yIHRoZSBkZWxh
eSBpbiByZXNwb25kaW5nLiBJIGhhZCBhbiBpc3N1ZSB3aXRoIGZpbHRlcnMgb24gbXkgZW1haWwg
Y2xpZW50IHRoYXQgSSByZWFsaXplZCBhbmQgZml4ZWQgb25seSB0b2RheS4gSSB0aGluayB0aGlz
IHNldHVwIHdvdWxkIGJlIGV4dHJlbWVseSB2YWx1YWJsZSBhdCB0aGUgaGFja2F0aG9uLCBlc3Bl
Y2lhbGx5IGluIGxpZ2h0IG9mIGFsbCB0aGUgcmVjZW50IGRpc2N1c3Npb25zIGFuZCBmaW5kaW5n
cyB3aXRoIElDRSByZWNlbnRseSBpbiB0aGUgbW11c2ljIGFuZCBiZmNwYmlzIGxpc3RzIChib3Ro
IGNj4oCZZCkuIE9mIGNvdXJzZSwgdGhlIHNldHVwIGlzIHVzZWZ1bCBvbmx5IGlmIG90aGVycyBj
b21lIHRvIHVzZSBpdCwgc28gaG9wZWZ1bGx5IG90aGVycyBjYW4gZm9yd2FyZCB0byBpbnRlcmVz
dGVkIHBhcnRpZXMgYW5kIGNoaW1lIGluIHN0YXRpbmcgdGhlaXIgaW50ZXJlc3QgaW4gcGFydGlj
aXBhdGluZy4NCg0KQ2hlZXJzLA0KQ2hhcmxlcw0KDQoNCk9uIDEwLzExLzE2LCA4OjI3IEFNLCAi
aGFja2F0aG9uIG9uIGJlaGFsZiBvZiBKYW1lcyBTd2FuIiA8aGFja2F0aG9uLWJvdW5jZXNAaWV0
Zi5vcmc8bWFpbHRvOmhhY2thdGhvbi1ib3VuY2VzQGlldGYub3JnPiBvbiBiZWhhbGYgb2Ygam1z
d2FuQGlvbC51bmguZWR1PG1haWx0bzpqbXN3YW5AaW9sLnVuaC5lZHU+PiB3cm90ZToNCg0KSGks
DQoNCk15IG5hbWUgaXMgSmFtZXMgU3dhbiBhbmQgd29yayBhdCB0aGUgVW5pdmVyc2l0eSBvZiBO
ZXcgSGFtcHNoaXJlIEludGVyT3BlcmFiaWxpdHkgTGFib3JhdG9yeSAoVU5ILUlPTCkuICBBdCB0
aGUgU0lQaXQgMzIgZXZlbnQgcmVjZW50bHkgaGVsZCBhdCBvdXIgZmFjaWxpdHkgd2UgdXRpbGl6
ZWQgYSBudW1iZXIgb2YgZGlmZmVyZW50IG5ldHdvcmtzIGluIG9yZGVyIHRvIHRlc3QgU0lQIGlt
cGxlbWVudGF0aW9ucyBhYmlsaXR5IHRvIHVzZSBTVFVOL1RVUk4vSUNFIGluIG9yZGVyIHRvIG1h
a2UgY29ubmVjdGlvbnMgaW4gdmFyaW91cyB0dWZmIG5ldHdvcmsgc2NlbmFyaW9zLiAgU29tZSBl
eGFtcGxlcyBhcmUgYW4gSVB2NiBvbmx5IG5ldHdvcmssIE5BVCdkIG5ldHdvcmtzIGluIHRoZSBz
YW1lIGFkZHJlc3MgcmFuZ2UsIG11bHRpbGF5ZXJlZCBOQVRzLCBhbmQgd2hhdCB3ZSBjYWxsZWQg
YW4gJ2V2aWwnIGhvdGVsIG5ldHdvcmsgdGhhdCBvbmx5IGFsbG93cyBETlMgYW5kIFRDUCBwb3J0
cyA4MCBhbmQgNDQzIChhcyBtYW55IHNlY3VyaXR5IGNvbnN0cmFpbmVkIG5ldHdvcmtzIHByb3Zp
ZGUpLiAgVGhlcmUgd2FzIHNvbWUgZGlzY3Vzc2lvbiBhdCBTSVBpdCBvbiB0aGlzIGJlaW5nIHVz
ZWZ1bCBkdXJpbmcgdGhlIElFVEYgaGFja2F0aG9uIHRvIHByb3ZpZGUgYWRkaXRpb25hbCB0b29s
cyBmb3IgdGVzdGluZyBpbXBsZW1lbnRhdGlvbnMgb2Ygb3RoZXIgcHJvdG9jb2xzIHRoYXQgbWF5
IGJlIGRlcGxveWVkIGluIHRoZXNlIHZhcmlvdXMgc2NlbmFyaW9zLiAgV291bGQgdGhpcyB0eXBl
IG9mIHNldHVwIGJlIG9mIGludGVyZXN0IHRvIHRoZSBJRVRGIGZvciB0aGUgaGFja2F0aG9uIG9y
IG90aGVyIGV2ZW50cyBoZWxkIGR1cmluZyB0aGUgd2Vlaz8NCg0KQmVzdCBSZWdhcmRzLA0KSmFt
ZXMNCg0K

--_000_54AF05DE827C47768F587A4D6FC21BBAciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <0A85CC98D46DAA4F8E60D27D09E417F7@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpDb25zb2xhczsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBE
ZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0K
CXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0
Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO30NCmE6bGluaywgc3Bhbi5Nc29IeXBl
cmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNv
cmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRp
b246dW5kZXJsaW5lO30NCnNwYW4uYXBwbGUtc3R5bGUtc3Bhbg0KCXttc28tc3R5bGUtbmFtZTph
cHBsZS1zdHlsZS1zcGFuO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBl
cnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OkNhbGlicmk7DQoJY29sb3I6d2luZG93dGV4dDt9
DQpzcGFuLm1zb0lucw0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCgltc28tc3R5bGUt
bmFtZToiIjsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lOw0KCWNvbG9yOnRlYWw7fQ0KLk1z
b0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEw
LjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2lu
OjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3Jk
U2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT4NCjwvaGVhZD4NCjxib2R5IGJnY29sb3I9IndoaXRlIiBs
YW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3Jk
U2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OkNhbGlicmkiPkhpIEphbWVzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6Q2FsaWJyaSI+VGhhbmtzIGZvciB5b3VyIGVtYWlsIGFuZCBzb3JyeSBmb3IgdGhlIGRlbGF5
IGluIHJlc3BvbmRpbmcuIEkgaGFkIGFuIGlzc3VlIHdpdGggZmlsdGVycyBvbiBteSBlbWFpbCBj
bGllbnQgdGhhdCBJIHJlYWxpemVkIGFuZCBmaXhlZCBvbmx5IHRvZGF5LiBJIHRoaW5rIHRoaXMg
c2V0dXAgd291bGQgYmUgZXh0cmVtZWx5IHZhbHVhYmxlIGF0IHRoZSBoYWNrYXRob24sDQogZXNw
ZWNpYWxseSBpbiBsaWdodCBvZiBhbGwgdGhlIHJlY2VudCBkaXNjdXNzaW9ucyBhbmQgZmluZGlu
Z3Mgd2l0aCBJQ0UgcmVjZW50bHkgaW4gdGhlIG1tdXNpYyBhbmQgYmZjcGJpcyBsaXN0cyAoYm90
aCBjY+KAmWQpLiBPZiBjb3Vyc2UsIHRoZSBzZXR1cCBpcyB1c2VmdWwgb25seSBpZiBvdGhlcnMg
Y29tZSB0byB1c2UgaXQsIHNvIGhvcGVmdWxseSBvdGhlcnMgY2FuIGZvcndhcmQgdG8gaW50ZXJl
c3RlZCBwYXJ0aWVzIGFuZCBjaGltZSBpbiBzdGF0aW5nDQogdGhlaXIgaW50ZXJlc3QgaW4gcGFy
dGljaXBhdGluZy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGli
cmkiPkNoZWVycyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaSI+Q2hhcmxlczxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxp
YnJpIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDYWxpYnJpIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLWxlZnQ6c29saWQgI0I1QzRERiA0LjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0O21h
cmdpbi1sZWZ0OjMuNzVwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj5PbiAxMC8xMS8xNiwgODoyNyBBTSwgJnF1b3Q7
aGFja2F0aG9uIG9uIGJlaGFsZiBvZiBKYW1lcyBTd2FuJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWls
dG86aGFja2F0aG9uLWJvdW5jZXNAaWV0Zi5vcmciPmhhY2thdGhvbi1ib3VuY2VzQGlldGYub3Jn
PC9hPiBvbiBiZWhhbGYgb2YNCjxhIGhyZWY9Im1haWx0bzpqbXN3YW5AaW9sLnVuaC5lZHUiPmpt
c3dhbkBpb2wudW5oLmVkdTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpLCA8
bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk15IG5hbWUgaXMg
SmFtZXMgU3dhbiBhbmQgd29yayBhdCB0aGUgVW5pdmVyc2l0eSBvZiBOZXcgSGFtcHNoaXJlIElu
dGVyT3BlcmFiaWxpdHkgTGFib3JhdG9yeSAoVU5ILUlPTCkuJm5ic3A7IEF0IHRoZSBTSVBpdCAz
MiBldmVudCByZWNlbnRseSBoZWxkIGF0IG91ciBmYWNpbGl0eSB3ZSB1dGlsaXplZCBhIG51bWJl
ciBvZiBkaWZmZXJlbnQgbmV0d29ya3MgaW4gb3JkZXIgdG8gdGVzdCBTSVAgaW1wbGVtZW50YXRp
b25zDQogYWJpbGl0eSB0byB1c2UgU1RVTi9UVVJOL0lDRSBpbiBvcmRlciB0byBtYWtlIGNvbm5l
Y3Rpb25zIGluIHZhcmlvdXMgdHVmZiBuZXR3b3JrIHNjZW5hcmlvcy4mbmJzcDsgU29tZSBleGFt
cGxlcyBhcmUgYW4gSVB2NiBvbmx5IG5ldHdvcmssIE5BVCdkIG5ldHdvcmtzIGluIHRoZSBzYW1l
IGFkZHJlc3MgcmFuZ2UsIG11bHRpbGF5ZXJlZCBOQVRzLCBhbmQgd2hhdCB3ZSBjYWxsZWQgYW4g
J2V2aWwnIGhvdGVsIG5ldHdvcmsgdGhhdCBvbmx5IGFsbG93cyBETlMNCiBhbmQgVENQIHBvcnRz
IDgwIGFuZCA0NDMgKGFzIG1hbnkgc2VjdXJpdHkgY29uc3RyYWluZWQgbmV0d29ya3MgcHJvdmlk
ZSkuJm5ic3A7IFRoZXJlIHdhcyBzb21lIGRpc2N1c3Npb24gYXQgU0lQaXQgb24gdGhpcyBiZWlu
ZyB1c2VmdWwgZHVyaW5nIHRoZSBJRVRGIGhhY2thdGhvbiB0byBwcm92aWRlIGFkZGl0aW9uYWwg
dG9vbHMgZm9yIHRlc3RpbmcgaW1wbGVtZW50YXRpb25zIG9mIG90aGVyIHByb3RvY29scyB0aGF0
IG1heSBiZSBkZXBsb3llZCBpbg0KIHRoZXNlIHZhcmlvdXMgc2NlbmFyaW9zLiZuYnNwOyBXb3Vs
ZCB0aGlzIHR5cGUgb2Ygc2V0dXAgYmUgb2YgaW50ZXJlc3QgdG8gdGhlIElFVEYgZm9yIHRoZSBo
YWNrYXRob24gb3Igb3RoZXIgZXZlbnRzIGhlbGQgZHVyaW5nIHRoZSB3ZWVrPzxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CZXN0IFJlZ2FyZHMs
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5KYW1l
czxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+
DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_54AF05DE827C47768F587A4D6FC21BBAciscocom_--


From nobody Wed Oct 19 13:20:32 2016
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 9FDB51295D0 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 13:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.632
X-Spam-Level: 
X-Spam-Status: No, score=-4.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.431, 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 3XnnLkzFVwKM for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 13:20:28 -0700 (PDT)
Received: from alum-mailsec-scanner-7.mit.edu (alum-mailsec-scanner-7.mit.edu [18.7.68.19]) by ietfa.amsl.com (Postfix) with ESMTP id BB6AA12969D for <mmusic@ietf.org>; Wed, 19 Oct 2016 13:20:28 -0700 (PDT)
X-AuditID: 12074413-9a9ff70000000a14-e8-5807d58a173e
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id 5B.62.02580.A85D7085; Wed, 19 Oct 2016 16:20:27 -0400 (EDT)
Received: from [192.168.1.110] (c-73-186-127-100.hsd1.ma.comcast.net [73.186.127.100]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id u9JKKPTD007117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Wed, 19 Oct 2016 16:20:26 -0400
To: mmusic@ietf.org
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org> <D42AA198.11408%christer.holmberg@ericsson.com> <A2448DA9-6634-4583-A4B6-040B93371254@csperkins.org> <D42D44E7.11653%christer.holmberg@ericsson.com> <9483F0F1-F651-4471-9AC0-6AA79EA2480D@csperkins.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <0b0a5e0b-a038-a230-cd18-05d1b759064e@alum.mit.edu>
Date: Wed, 19 Oct 2016 16:20:25 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <9483F0F1-F651-4471-9AC0-6AA79EA2480D@csperkins.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNIsWRmVeSWpSXmKPExsUixO6iqNt9lT3CYNsBboupyx+zODB6LFny kymAMYrLJiU1J7MstUjfLoEro3P2BcaCBeoVDz+7NDDule9i5OSQEDCRODbrF0sXIxeHkMBl RokPp+czQjhvmSRWT77PAlIlLJAh0fKyixHEFhEQlpjx9i8bRNE7Zone64tYQRJsAloScw79 B2vgFbCXWH0JoplFQFXixZy3bCC2qECaxPZ1u5khagQlTs58AlbDKeAosWLaXjCbWcBMYt7m h8wQtrxE89bZzBMY+WYhaZmFpGwWkrIFjMyrGOUSc0pzdXMTM3OKU5N1i5MT8/JSi3TN9XIz S/RSU0o3MULCTHgH466TcocYBTgYlXh4M8+xRwixJpYVV+YeYpTkYFIS5eXpAwrxJeWnVGYk FmfEF5XmpBYfYpTgYFYS4T19BijHm5JYWZValA+TkuZgURLnVVui7ickkJ5YkpqdmlqQWgST leHgUJLgzbgC1ChYlJqeWpGWmVOCkGbi4AQZzgM0PAykhre4IDG3ODMdIn+KUVFKnHfyZaCE AEgiozQPrheWBl4xigO9Isz7F6SKB5hC4LpfAQ1mAhp8Lo8FZHBJIkJKqoGxhPU9n7SEjaeB ySFt9xuT/06fvUJxA197j9u+jdM51Bbo74m7mWxgWp3rFGr3xPrXi/t8qz9Hh8hkyx7/zN35 ZpnUan2FYLFj8Z9D226f2/fsiOMnkfJgrg9y7JIXNm+MVu45E114TfmemuL+mfn22+2KVsQd Xz19+W4rK153LrdkrXlNysuUWIozEg21mIuKEwEUwOtu3gIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ay65iOFVurBs9mNTij-4gT5vn50>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 20:20:30 -0000

On 10/19/16 9:18 AM, Colin Perkins wrote:
> Hi,
>
>> On 19 Oct 2016, at 13:37, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
>>
>> BUNDLE is about grouping m- lines, and as all m- lines shares the same
>> address:port I think the text should be how to associate RTP packets with
>> m- lines, using MID, SSRC etc.
>
> Sorry, but I think this is fundamentally wrong. BUNDLE associates RTP _streams_ with â€œm=â€œ lines; it doesnâ€™t associate RTP _packets_ with â€œm=â€œ lines. Thereâ€™s an important semantic difference between these two thatâ€™s getting missed.
>
> When RTP and RTCP packets are received, theyâ€™re associated with an RTP stream, based on, and identified by, their SSRC [RFC7656]. This is done whether or not BUNDLE is in use.
>
> The goal of BUNDLE is then to associate those received RTP streams with m= lines. This might be done based on a signalled mapping from SSRC to m= line (â€œa=ssrc:â€�), it might be done using MID, or some other means. But, the association is from RTP stream to m= line, not from RTP packets to m= line.
>
>> How RTP packets are then grouped and processed etc I think is outside the
>> scope of BUNDLE.
>
> Yes, but not in the way you suggest. I think what should happen is:
>
> - The grouping of RTP and RTCP packets into RTP streams happens below BUNDLE. An RTP stream is always identified by SSRC, and will have other metadata associated with it. That metadata can be sent in RTCP, in RTP header extensions, or it can be signalled using â€œa=ssrc:â€� lines. The SSRC might not be signalled in advance, but still identifies the RTP stream.
>
> - BUNDLE then associates those RTP streams with m= lines. This mapping needs to be defined in terms of RTP streams, not RTP packets, since the RTP packets have already been grouped into streams before they reach BUNDLE. It should describe how to map an RTP stream with a particular SSRC onto an â€œm=â€œ line, based on the metadata associated with that RTP stream.
>
> - How those m= lines relate to higher-level semantics is determined by a higher-layer protocol, such as JSEP.
>
> Getting the layering right is important, I think, to have something thatâ€™s both understandable and extensible:
>
>  RTP Layer  : RTP and RTCP packets -> RTP streams
>  SDP BUNDLE : RTP streams -> SDP â€œm=" lines
>  JSEP       : SDP â€œm=" lines -> application-level semantics
>
> I donâ€™t think this will need a big text change, but it is a semantic change in how the BUNDLE draft describes the mapping.

ISTM this isn't fundamentally about BUNDLE. It is about the relationship 
of SDP and RTP. My impression is that this was never *right*, and the 
introduction of BUNDLE has brought it to a head.

For the most part SDP rarely mentions SSRCs. (It *can* using a=SSRC, but 
that is a rarely used construct.)

SDP is a container for multiple "Media Descriptions". Syntactically it 
does this by:

- grouping multiple SDP lines into multiple media descriptions
   delineated by m-lines
- associating a 3-tuple with each media description based on the
   c-line and info in the m-line
- associating two SDPs (offer and answer), pairing the media
   descriptions in each in order to merge properties. This merges
   two 3-tuples into a 5-tuple

The code that interprets this stuff then (in the case of RTP) associates 
each media description with (possibly multiple) RTP streams. In non-rtp 
cases the interpretation is different.

Historically (pre-bundle) that code was able to associate network 
packets with media descriptions based on the 5-tuple. This was partially 
done by the OS (sockets) and partially the application.

The introduction of BUNDLE is with the intent using a single 5-tuple for 
multiple media descriptions. That means that the 5-tuple is insufficient 
to associate packets with media descriptions, so some additional 
algorithm is required to do that.

When Christer is talking about an m-line he is generally using that as 
shorthand language for the media description delineated by the m-line. 
With that in mind, his wording "associate received RTP packets wth an m= 
line [media description]" seems right to me.

In the case of RTP, it remains the job of the RTP implementation to 
associate those incoming RTP packets with a media description. *Then* it 
can use the other properties of that media description to help in 
figuring out what RTP stream they are associated with.

That is only for RTP. In the case of non-RTP media that is is the bundle 
some different algorithm is needed to make the association. We have only 
defined a limited case for non-RTP media in a bundle, so the task is 
easier. But we just put that off. In principle more things could be 
bundled. For instance, we *could* have allowed multiple UDP/DTLS/SCTP 
media descriptions in the bundle as long as they had differing 
SCTP-ports. That would bind corresponding packets to one or the other of 
the media descriptions.

	Thanks,
	Paul




From nobody Wed Oct 19 13:34:46 2016
Return-Path: <bernard.aboba@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD5CD1294BB for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 13:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 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, HTML_OBFUSCATE_05_10=0.26, 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=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 h0lUr4FCkzCq for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 13:34:42 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (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 F073012947E for <mmusic@ietf.org>; Wed, 19 Oct 2016 13:34:41 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id 83so43160438vkd.0 for <mmusic@ietf.org>; Wed, 19 Oct 2016 13:34:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=obiaN7kpbjY2GsTYvOykPq5nsIhRYvnP0cx4uYMDlmM=; b=p6zP8y57K+lp+eW2lHlPsJHKk58WLi4npDfDSQ3AsiNdfgCB0L54Kp2561Da1LBfE2 uQD6XO5agbhplUSZA6W7wpaY849OE2DHv1Q1LxOhfZZWiHb2xzeTWtn0NqKpcO6znIvN 5LeAOZlOJ/3GsBL5scxoMlOnDpGT/p0QfO41pa38SjrcM4jcYwCZ1ftC68LorGsCV/v0 s6KqE69Epd0sH9Ox8rheM0mE7LBPMub0S1knPvmRN2QILRq2HHJHPrNlGoCejqmN31LR zv6vP5QtbGVyFoA8Vt+GfsmOCDKou5KPRsBgXhlnVbfP2T3Fbr2Er8oONH9jdS4eRkuV mlyg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=obiaN7kpbjY2GsTYvOykPq5nsIhRYvnP0cx4uYMDlmM=; b=Rk4S/P7E4pqjvcStGad+qpoOUpvld+ZQB8xGEHAa70XQZ4MKQ20wA4Jwj9rLc7f6el q6nirDiUlQEuWUBAlV5kCUTQ9t/i74aig7Jr0hkfu13R49KYbo/JqkDR7Rysf2H+8VxW WNCZJdGpMYz8ALOOP34gYPI1FA4MVxLfB7fXOMrYzZI5+/mMaM8T1r0lf+HeBI3LrF6M Y0jupot4qpHPiMZku8jE4WziIcAP24cMwoZ8aO6+PxltVT0mHWS0Edwne0SIsSk1H17u WmVPYwpygp2la/lthtU+vpn6xTZDX1DVnuEbbyi8l868AL2TVVSmPUoLZNZFkA8XFMSs xTCg==
X-Gm-Message-State: AA6/9RnoEXLdNljkiviO7MV1XY+GOZvJbE8+4asPfE7Myro6STjRlGCFvpgq982K9IMWqVnAFNBrS7Qf4vKZqw==
X-Received: by 10.31.74.4 with SMTP id x4mr6173532vka.58.1476909279801; Wed, 19 Oct 2016 13:34:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.7.101 with HTTP; Wed, 19 Oct 2016 13:34:19 -0700 (PDT)
In-Reply-To: <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Wed, 19 Oct 2016 15:34:19 -0500
Message-ID: <CAOW+2dtMj-i_Q-Y69jxEqRU9Z1N_y6oxQ2nR5tZWy-+zE71PDA@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: multipart/alternative; boundary=001a114daaacfcf59b053f3dbc2c
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/5EBksHdatBm24eW5N-HfDUtPkJg>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 20:34:45 -0000

--001a114daaacfcf59b053f3dbc2c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

RTCP packets can contain information relevant to more than one RtpReceiver
or RtpSender.  As a result, the ORTC specification contains the (admittedly
somewhat vague) text below.  We omitted the RTCP "app" message (Section 6.7
of RFC 3550) since support for that is not required in WebRTC.

"RTCP packets arriving on an RTCDtlsTransport
<http://draft.ortc.org/#dom-rtcdtlstransport> are decrypted and a
notification is sent to all RTCRtpSender
<http://draft.ortc.org/#dom-rtcrtpsender> andRTCRtpReceiver
<http://draft.ortc.org/#dom-rtcrtpreceiver> objects utilizing that
transport. RTCRtpSender <http://draft.ortc.org/#dom-rtcrtpsender> and
RTCRtpReceiver <http://draft.ortc.org/#dom-rtcrtpreceiver> objects then
examine the RTCP packets to determine the information relevant to their
operation and the statistics maintained by them.

RTCP packets should be queued for 30 seconds and all RTCRtpSender
<http://draft.ortc.org/#dom-rtcrtpsender> and RTCRtpReceiver
<http://draft.ortc.org/#dom-rtcrtpreceiver> objects on the related
RTCDTlsTransport <http://draft.ortc.org/#dom-rtcdtlstransport> have access
to those packets until the packet is removed from the queue, should the
RTCRtpSender <http://draft.ortc.org/#dom-rtcrtpsender> or RTCRtpReceiver
<http://draft.ortc.org/#dom-rtcrtpreceiver> objects need to examine them.

Relevant SSRC fields within selected RTCP packets are summarized within [
RFC3550 <http://draft.ortc.org/#bib-RFC3550>] Section 6.4.1 (Sender
Report), Section 6.4.2 (Receiver Report), Section 6.5 (SDES), Section 6.6
(BYE), [RFC4585 <http://draft.ortc.org/#bib-RFC4585>] Section 6.1 (Feedback
Messages), and [RFC3611 <http://draft.ortc.org/#bib-RFC3611>] Section 2
(Extended Reports)."




On Thu, Oct 13, 2016 at 10:03 AM, Cullen Jennings <fluffy@iii.ca> wrote:

>
> That looks about right for RTP but I think it is still missing stuff for
> RTCP handling. Here is the current text we did for JSEP. I prefer the sty=
le
> in which you described it compared to the algorithm style below but I thi=
nk
> this might help figure out what to write for RTCP.
>
>
>
> When an RTP packet is received by a transport and passes SRTP
> authentication, that packet needs to be routed to the correct RtpReceiver=
.
> For each transport, the following steps MUST be followed to prepare to
> route packets:
>
>
>    - Construct a table mapping MID to RtpReceiver for each RtpReceiver
>    configured to receive from this transport.
>    - Construct a table mapping incoming SSRC to RtpReceiver for each
>    RtpReceiver configured to receive from this transport and for each SSR=
C
>    that RtpReceiver is configured to receive. Some of the SSRCs may be pr=
esent
>    in the m=3D section corresponding to that RtpReceiver in the remote
>    description.
>    - Construct a table mapping outgoing SSRC to RtpSender for each
>    RtpSender configured to transmit from this transport and for each SSRC=
 that
>    RtpSender is configured to use when sending.
>    - Construct a table mapping payload type to RtpReceiver for each
>    RtpReceiver configured to receive from this transport and for each pay=
load
>    type that RtpReceiver is configured to receive. The payload types of a
>    given RtpReceiver are found in the m=3D section corresponding to that
>    RtpReceiver in the local description. If any payload type could map to=
 more
>    than one RtpReceiver, map to the RtpReceiver whose m=3D section appear=
s
>    earliest in the local description.
>
> As RtpTransceivers (and, thus, RtpReceivers) are added, removed, stopped,
> or reconfigured, the tables above must also be updated.
> For each RTP packet received, the following steps MUST be followed to
> route the packet:
>
>
>    - If the packet has a MID and that MID is not in the table mapping MID
>    to RtpReceiver, drop the packet and stop.
>    - If the packet has a MID and that MID is in the table mapping MID to
>    RtpReceiver, update the incoming SSRC mapping table to include an entr=
y
>    that maps the packet's SSRC to the RtpReceiver for that MID.
>    - If the packet's SSRC is in the incoming SSRC mapping table, deliver
>    the packet to the associated RtpReceiver and stop.
>    - If the packet's payload type is in the payload type table, update
>    the the incoming SSRC mapping table to include an entry that maps the
>    packet's SSRC to the RtpReceiver for that payload type. In addition,
>    deliver the packet to the associated RtpReceiver and stop.
>    - Otherwise, drop the packet.
>
> For each RTCP packet received (including each RTCP packet that is part of
> a compound RTCP packet), the following type-specific handling MUST be
> performed to route the packet:
>
>
>    - If the packet is of type SR, and the sender SSRC for the packet is
>    found in the incoming SSRC table, deliver a copy of the packet to the
>    RtpReceiver associated with that SSRC. In addition, for each report bl=
ock
>    in the report whose SSRC is found in the outgoing SSRC table, deliver =
a
>    copy of the RTCP packet to the RtpSender associated with that SSRC.
>    - If the packet is of type RR, for each report block in the packet
>    whose SSRC is found in the outgoing SSRC table, deliver a copy of the =
RTCP
>    packet to the RtpSender associated with that SSRC.
>    - If the packet is of type SDES, and the sender SSRC for the packet is
>    found in the incoming SSRC table, deliver the packet to the RtpReceive=
r
>    associated with that SSRC. In addition, for each chunk in the packet t=
hat
>    contains a MID that is in the table mapping MID to RtpReceiver, update=
 the
>    incoming SSRC mapping table to include an entry that maps the SSRC for=
 that
>    chunk to the RtpReceiver associated with that MID. (This case can occu=
r
>    when RTCP for a source is received before any RTP packets.)
>    - If the packet is of type BYE, for each SSRC indicated in the packet
>    that is found in the incoming SSRC table, deliver a copy of the packet=
 to
>    the RtpReceiver associated with that SSRC.
>    - If the packet is of type RTPFB or PSFB, as defined in [RFC4585]
>    <http://rtcweb-wg.github.io/jsep/#RFC4585>, and the media source SSRC
>    for the packet is found in the outgoing SSRC table, deliver the packet=
 to
>    the RtpSender associated with that SSRC.
>
> After packets are routed to the RtpReceiver, further processing of the RT=
P
> packets is done at the RtpReceiver level. This includes using
> [I-D.ietf-mmusic-rid]
> <http://rtcweb-wg.github.io/jsep/#I-D.ietf-mmusic-rid> to distinguish
> between multiple Encoded Streams, as well as determine which Source RTP
> stream should be repaired by a given Redundancy RTP stream. If the RTP
> packet's PT does not match any codec in use by the RtpReceiver, the packe=
t
> will be dropped.
>
>
>
> On Oct 12, 2016, at 4:37 AM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
> Hi,
>
> I=C4=85ve created a pull request with additional text regarding associati=
ng
> RTP/RTCP packets with the correct =C5=82m=3D=C5=82 line.
>
> https://github.com/cdh4u/draft-sdp-bundle/pull/10
>
>
> Regards,
>
> Christer
>
> _______________________________________________
> 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
>
>

--001a114daaacfcf59b053f3dbc2c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">RTCP packets can contain information relevant to more than=
 one RtpReceiver or RtpSender.=C2=A0 As a result, the ORTC specification co=
ntains the (admittedly somewhat vague) text below.=C2=A0 We omitted the RTC=
P &quot;app&quot; message (Section 6.7 of RFC 3550) since support for that =
is not required in WebRTC.=C2=A0<div><div><br></div><div><p style=3D"margin=
:1em 0px;color:rgb(0,0,0);font-family:sans-serif;font-size:medium">&quot;RT=
CP packets arriving on an=C2=A0<code style=3D"color:rgb(200,53,0);font-fami=
ly:menlo,consolas,&quot;dejavu sans mono&quot;,monaco,monospace;font-size:0=
.9em"><a href=3D"http://draft.ortc.org/#dom-rtcdtlstransport" class=3D"gmai=
l-internalDFN" style=3D"color:rgb(3,69,117);border-bottom:1px solid rgb(187=
,187,187);text-decoration:none;padding:0px 1px"><code style=3D"color:rgb(20=
0,53,0);font-family:menlo,consolas,&quot;dejavu sans mono&quot;,monaco,mono=
space;font-size:14.4px">RTCDtlsTransport</code></a></code>=C2=A0are decrypt=
ed and a notification is sent to all=C2=A0<code style=3D"color:rgb(200,53,0=
);font-family:menlo,consolas,&quot;dejavu sans mono&quot;,monaco,monospace;=
font-size:0.9em"><a href=3D"http://draft.ortc.org/#dom-rtcrtpsender" class=
=3D"gmail-internalDFN" style=3D"color:rgb(3,69,117);border-bottom:1px solid=
 rgb(187,187,187);text-decoration:none;padding:0px 1px"><code style=3D"colo=
r:rgb(200,53,0);font-family:menlo,consolas,&quot;dejavu sans mono&quot;,mon=
aco,monospace;font-size:14.4px">RTCRtpSender</code></a></code>=C2=A0and<cod=
e style=3D"color:rgb(200,53,0);font-family:menlo,consolas,&quot;dejavu sans=
 mono&quot;,monaco,monospace;font-size:0.9em"><a href=3D"http://draft.ortc.=
org/#dom-rtcrtpreceiver" class=3D"gmail-internalDFN" style=3D"color:rgb(3,6=
9,117);border-bottom:1px solid rgb(187,187,187);text-decoration:none;paddin=
g:0px 1px"><code style=3D"color:rgb(200,53,0);font-family:menlo,consolas,&q=
uot;dejavu sans mono&quot;,monaco,monospace;font-size:14.4px">RTCRtpReceive=
r</code></a></code>=C2=A0objects utilizing that transport.=C2=A0<code style=
=3D"color:rgb(200,53,0);font-family:menlo,consolas,&quot;dejavu sans mono&q=
uot;,monaco,monospace;font-size:0.9em"><a href=3D"http://draft.ortc.org/#do=
m-rtcrtpsender" class=3D"gmail-internalDFN" style=3D"color:rgb(3,69,117);bo=
rder-bottom:1px solid rgb(187,187,187);text-decoration:none;padding:0px 1px=
"><code style=3D"color:rgb(200,53,0);font-family:menlo,consolas,&quot;dejav=
u sans mono&quot;,monaco,monospace;font-size:14.4px">RTCRtpSender</code></a=
></code>=C2=A0and=C2=A0<code style=3D"color:rgb(200,53,0);font-family:menlo=
,consolas,&quot;dejavu sans mono&quot;,monaco,monospace;font-size:0.9em"><a=
 href=3D"http://draft.ortc.org/#dom-rtcrtpreceiver" class=3D"gmail-internal=
DFN" style=3D"color:rgb(3,69,117);border-bottom:1px solid rgb(187,187,187);=
text-decoration:none;padding:0px 1px"><code style=3D"color:rgb(200,53,0);fo=
nt-family:menlo,consolas,&quot;dejavu sans mono&quot;,monaco,monospace;font=
-size:14.4px">RTCRtpReceiver</code></a></code>=C2=A0objects then examine th=
e RTCP packets to determine the information relevant to their operation and=
 the statistics maintained by them.</p><p style=3D"margin:1em 0px;color:rgb=
(0,0,0);font-family:sans-serif;font-size:medium">RTCP packets should be que=
ued for 30 seconds and all=C2=A0<code style=3D"color:rgb(200,53,0);font-fam=
ily:menlo,consolas,&quot;dejavu sans mono&quot;,monaco,monospace;font-size:=
0.9em"><a href=3D"http://draft.ortc.org/#dom-rtcrtpsender" class=3D"gmail-i=
nternalDFN" style=3D"color:rgb(3,69,117);border-bottom:1px solid rgb(187,18=
7,187);text-decoration:none;padding:0px 1px"><code style=3D"color:rgb(200,5=
3,0);font-family:menlo,consolas,&quot;dejavu sans mono&quot;,monaco,monospa=
ce;font-size:14.4px">RTCRtpSender</code></a></code>=C2=A0and=C2=A0<code sty=
le=3D"color:rgb(200,53,0);font-family:menlo,consolas,&quot;dejavu sans mono=
&quot;,monaco,monospace;font-size:0.9em"><a href=3D"http://draft.ortc.org/#=
dom-rtcrtpreceiver" class=3D"gmail-internalDFN" style=3D"color:rgb(3,69,117=
);border-bottom:1px solid rgb(187,187,187);text-decoration:none;padding:0px=
 1px"><code style=3D"color:rgb(200,53,0);font-family:menlo,consolas,&quot;d=
ejavu sans mono&quot;,monaco,monospace;font-size:14.4px">RTCRtpReceiver</co=
de></a></code>=C2=A0objects on the related<code style=3D"color:rgb(200,53,0=
);font-family:menlo,consolas,&quot;dejavu sans mono&quot;,monaco,monospace;=
font-size:0.9em"><a href=3D"http://draft.ortc.org/#dom-rtcdtlstransport" cl=
ass=3D"gmail-internalDFN" style=3D"color:rgb(3,69,117);border-bottom:1px so=
lid rgb(187,187,187);text-decoration:none;padding:0px 1px"><code style=3D"c=
olor:rgb(200,53,0);font-family:menlo,consolas,&quot;dejavu sans mono&quot;,=
monaco,monospace;font-size:14.4px">RTCDTlsTransport</code></a></code>=C2=A0=
have access to those packets until the packet is removed from the queue, sh=
ould the<code style=3D"color:rgb(200,53,0);font-family:menlo,consolas,&quot=
;dejavu sans mono&quot;,monaco,monospace;font-size:0.9em"><a href=3D"http:/=
/draft.ortc.org/#dom-rtcrtpsender" class=3D"gmail-internalDFN" style=3D"col=
or:rgb(3,69,117);border-bottom:1px solid rgb(187,187,187);text-decoration:n=
one;padding:0px 1px"><code style=3D"color:rgb(200,53,0);font-family:menlo,c=
onsolas,&quot;dejavu sans mono&quot;,monaco,monospace;font-size:14.4px">RTC=
RtpSender</code></a></code>=C2=A0or=C2=A0<code style=3D"color:rgb(200,53,0)=
;font-family:menlo,consolas,&quot;dejavu sans mono&quot;,monaco,monospace;f=
ont-size:0.9em"><a href=3D"http://draft.ortc.org/#dom-rtcrtpreceiver" class=
=3D"gmail-internalDFN" style=3D"color:rgb(3,69,117);border-bottom:1px solid=
 rgb(187,187,187);text-decoration:none;padding:0px 1px"><code style=3D"colo=
r:rgb(200,53,0);font-family:menlo,consolas,&quot;dejavu sans mono&quot;,mon=
aco,monospace;font-size:14.4px">RTCRtpReceiver</code></a></code>=C2=A0objec=
ts need to examine them.</p><p style=3D"margin:1em 0px;color:rgb(0,0,0);fon=
t-family:sans-serif;font-size:medium">Relevant SSRC fields within selected =
RTCP packets are summarized within [<cite><a class=3D"gmail-bibref" href=3D=
"http://draft.ortc.org/#bib-RFC3550" style=3D"text-decoration:none;font-sty=
le:normal;color:rgb(3,69,117);border-bottom:1px solid rgb(187,187,187);padd=
ing:0px 1px">RFC3550</a></cite>] Section 6.4.1 (Sender Report), Section 6.4=
.2 (Receiver Report), Section 6.5 (SDES), Section 6.6 (BYE), [<cite><a clas=
s=3D"gmail-bibref" href=3D"http://draft.ortc.org/#bib-RFC4585" style=3D"tex=
t-decoration:none;font-style:normal;color:rgb(3,69,117);border-bottom:1px s=
olid rgb(187,187,187);padding:0px 1px">RFC4585</a></cite>] Section 6.1 (Fee=
dback Messages), and [<cite><a class=3D"gmail-bibref" href=3D"http://draft.=
ortc.org/#bib-RFC3611" style=3D"text-decoration:none;font-style:normal;colo=
r:rgb(3,69,117);border-bottom:1px solid rgb(187,187,187);padding:0px 1px">R=
FC3611</a></cite>] Section 2 (Extended Reports).&quot;</p><div><br></div><d=
iv><br></div><div><br></div></div></div></div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Thu, Oct 13, 2016 at 10:03 AM, Cullen Jenni=
ngs <span dir=3D"ltr">&lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank=
">fluffy@iii.ca</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><di=
v style=3D"word-wrap:break-word"><div><br></div>That looks about right for =
RTP but I think it is still missing stuff for RTCP handling. Here is the cu=
rrent text we did for JSEP. I prefer the style in which you described it co=
mpared to the algorithm style below but I think this might help figure out =
what to write for RTCP.=C2=A0<div><br></div><div><span style=3D"color:rgb(5=
1,51,51);font-family:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-serif;fo=
nt-size:15px"><br></span></div><div><span style=3D"color:rgb(51,51,51);font=
-family:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-serif;font-size:15px"=
><br></span></div><div><span style=3D"color:rgb(51,51,51);font-family:&#39;=
Helvetica Neue&#39;,Helvetica,Arial,sans-serif;font-size:15px">When an RTP =
packet is received by a transport and passes SRTP authentication, that pack=
et needs to be routed to the correct RtpReceiver. For each transport, the f=
ollowing steps MUST be followed to prepare to route packets:</span></div><d=
iv><p style=3D"padding:0px;margin:0.5em 0px;color:rgb(51,51,51);font-family=
:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-serif;font-size:15px;font-va=
riant-ligatures:normal"></p><ul class=3D"m_6788252280181015495empty" style=
=3D"padding:0px;margin:0.5em 0px 0.5em 2em;list-style-type:none;color:rgb(5=
1,51,51);font-family:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-serif;fo=
nt-size:15px;font-variant-ligatures:normal"><li style=3D"padding:0px;margin=
:0.5em 0px">Construct a table mapping MID to RtpReceiver for each RtpReceiv=
er configured to receive from this transport.</li><li style=3D"padding:0px;=
margin:0.5em 0px">Construct a table mapping incoming SSRC to RtpReceiver fo=
r each RtpReceiver configured to receive from this transport and for each S=
SRC that RtpReceiver is configured to receive. Some of the SSRCs may be pre=
sent in the m=3D section corresponding to that RtpReceiver in the remote de=
scription.</li><li style=3D"padding:0px;margin:0.5em 0px">Construct a table=
 mapping outgoing SSRC to RtpSender for each RtpSender configured to transm=
it from this transport and for each SSRC that RtpSender is configured to us=
e when sending.</li><li style=3D"padding:0px;margin:0.5em 0px">Construct a =
table mapping payload type to RtpReceiver for each RtpReceiver configured t=
o receive from this transport and for each payload type that RtpReceiver is=
 configured to receive. The payload types of a given RtpReceiver are found =
in the m=3D section corresponding to that RtpReceiver in the local descript=
ion. If any payload type could map to more than one RtpReceiver, map to the=
 RtpReceiver whose m=3D section appears earliest in the local description.<=
/li></ul><p style=3D"padding:0px;margin:0.5em 0px;color:rgb(51,51,51);font-=
family:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-serif;font-size:15px;f=
ont-variant-ligatures:normal"></p><div style=3D"padding:0px;margin:0.5em 0p=
x;color:rgb(51,51,51);font-family:&#39;Helvetica Neue&#39;,Helvetica,Arial,=
sans-serif;font-size:15px;font-variant-ligatures:normal">As RtpTransceivers=
 (and, thus, RtpReceivers) are added, removed, stopped, or reconfigured, th=
e tables above must also be updated.</div><div style=3D"padding:0px;margin:=
0.5em 0px;color:rgb(51,51,51);font-family:&#39;Helvetica Neue&#39;,Helvetic=
a,Arial,sans-serif;font-size:15px;font-variant-ligatures:normal">For each R=
TP packet received, the following steps MUST be followed to route the packe=
t:</div><p style=3D"padding:0px;margin:0.5em 0px;color:rgb(51,51,51);font-f=
amily:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-serif;font-size:15px;fo=
nt-variant-ligatures:normal"></p><ul class=3D"m_6788252280181015495empty" s=
tyle=3D"padding:0px;margin:0.5em 0px 0.5em 2em;list-style-type:none;color:r=
gb(51,51,51);font-family:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-seri=
f;font-size:15px;font-variant-ligatures:normal"><li style=3D"padding:0px;ma=
rgin:0.5em 0px">If the packet has a MID and that MID is not in the table ma=
pping MID to RtpReceiver, drop the packet and stop.</li><li style=3D"paddin=
g:0px;margin:0.5em 0px">If the packet has a MID and that MID is in the tabl=
e mapping MID to RtpReceiver, update the incoming SSRC mapping table to inc=
lude an entry that maps the packet&#39;s SSRC to the RtpReceiver for that M=
ID.</li><li style=3D"padding:0px;margin:0.5em 0px">If the packet&#39;s SSRC=
 is in the incoming SSRC mapping table, deliver the packet to the associate=
d RtpReceiver and stop.</li><li style=3D"padding:0px;margin:0.5em 0px">If t=
he packet&#39;s payload type is in the payload type table, update the the i=
ncoming SSRC mapping table to include an entry that maps the packet&#39;s S=
SRC to the RtpReceiver for that payload type. In addition, deliver the pack=
et to the associated RtpReceiver and stop.</li><li style=3D"padding:0px;mar=
gin:0.5em 0px">Otherwise, drop the packet.</li></ul><p style=3D"padding:0px=
;margin:0.5em 0px;color:rgb(51,51,51);font-family:&#39;Helvetica Neue&#39;,=
Helvetica,Arial,sans-serif;font-size:15px;font-variant-ligatures:normal"></=
p><div style=3D"padding:0px;margin:0.5em 0px;color:rgb(51,51,51);font-famil=
y:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-serif;font-size:15px;font-v=
ariant-ligatures:normal">For each RTCP packet received (including each RTCP=
 packet that is part of a compound RTCP packet), the following type-specifi=
c handling MUST be performed to route the packet:</div><p style=3D"padding:=
0px;margin:0.5em 0px;color:rgb(51,51,51);font-family:&#39;Helvetica Neue&#3=
9;,Helvetica,Arial,sans-serif;font-size:15px;font-variant-ligatures:normal"=
></p><ul class=3D"m_6788252280181015495empty" style=3D"padding:0px;margin:0=
.5em 0px 0.5em 2em;list-style-type:none;color:rgb(51,51,51);font-family:&#3=
9;Helvetica Neue&#39;,Helvetica,Arial,sans-serif;font-size:15px;font-varian=
t-ligatures:normal"><li style=3D"padding:0px;margin:0.5em 0px">If the packe=
t is of type SR, and the sender SSRC for the packet is found in the incomin=
g SSRC table, deliver a copy of the packet to the RtpReceiver associated wi=
th that SSRC. In addition, for each report block in the report whose SSRC i=
s found in the outgoing SSRC table, deliver a copy of the RTCP packet to th=
e RtpSender associated with that SSRC.</li><li style=3D"padding:0px;margin:=
0.5em 0px">If the packet is of type RR, for each report block in the packet=
 whose SSRC is found in the outgoing SSRC table, deliver a copy of the RTCP=
 packet to the RtpSender associated with that SSRC.</li><li style=3D"paddin=
g:0px;margin:0.5em 0px">If the packet is of type SDES, and the sender SSRC =
for the packet is found in the incoming SSRC table, deliver the packet to t=
he RtpReceiver associated with that SSRC. In addition, for each chunk in th=
e packet that contains a MID that is in the table mapping MID to RtpReceive=
r, update the incoming SSRC mapping table to include an entry that maps the=
 SSRC for that chunk to the RtpReceiver associated with that MID. (This cas=
e can occur when RTCP for a source is received before any RTP packets.)</li=
><li style=3D"padding:0px;margin:0.5em 0px">If the packet is of type BYE, f=
or each SSRC indicated in the packet that is found in the incoming SSRC tab=
le, deliver a copy of the packet to the RtpReceiver associated with that SS=
RC.</li><li style=3D"padding:0px;margin:0.5em 0px">If the packet is of type=
 RTPFB or PSFB, as defined in=C2=A0<a href=3D"http://rtcweb-wg.github.io/js=
ep/#RFC4585" style=3D"text-decoration:none;color:rgb(42,100,150)" target=3D=
"_blank">[RFC4585]</a>, and the media source SSRC for the packet is found i=
n the outgoing SSRC table, deliver the packet to the RtpSender associated w=
ith that SSRC.</li></ul><p style=3D"padding:0px;margin:0.5em 0px;color:rgb(=
51,51,51);font-family:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-serif;f=
ont-size:15px;font-variant-ligatures:normal"></p><div style=3D"padding:0px;=
margin:0.5em 0px;color:rgb(51,51,51);font-family:&#39;Helvetica Neue&#39;,H=
elvetica,Arial,sans-serif;font-size:15px;font-variant-ligatures:normal">Aft=
er packets are routed to the RtpReceiver, further processing of the RTP pac=
kets is done at the RtpReceiver level. This includes using=C2=A0<a href=3D"=
http://rtcweb-wg.github.io/jsep/#I-D.ietf-mmusic-rid" style=3D"text-decorat=
ion:none;color:rgb(42,100,150)" target=3D"_blank">[I-D.ietf-mmusic-rid]</a>=
=C2=A0to distinguish between multiple Encoded Streams, as well as determine=
 which Source RTP stream should be repaired by a given Redundancy RTP strea=
m. If the RTP packet&#39;s PT does not match any codec in use by the RtpRec=
eiver, the packet will be dropped.</div><h1 id=3D"m_6788252280181015495rfc.=
section.7" style=3D"font-family:&#39;Helvetica Neue&#39;,Helvetica,Arial,sa=
ns-serif;font-weight:500;color:rgb(51,51,51);line-height:30px;margin:0.8em =
0px 0.3em;font-size:30px;font-variant-ligatures:normal"></h1><div style=3D"=
padding:0px;margin:0.5em 0px;color:rgb(51,51,51);font-family:&#39;Helvetica=
 Neue&#39;,Helvetica,Arial,sans-serif;font-size:15px;font-variant-ligatures=
:normal"><br></div></div><div style=3D"padding:0px;margin:0.5em 0px;color:r=
gb(51,51,51);font-family:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-seri=
f;font-size:15px;font-variant-ligatures:normal"><br></div><div style=3D"pad=
ding:0px;margin:0.5em 0px;color:rgb(51,51,51);font-family:&#39;Helvetica Ne=
ue&#39;,Helvetica,Arial,sans-serif;font-size:15px;font-variant-ligatures:no=
rmal"><br></div><div><blockquote type=3D"cite"><div>On Oct 12, 2016, at 4:3=
7 AM, Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.co=
m" target=3D"_blank">christer.holmberg@ericsson.<wbr>com</a>&gt; wrote:</di=
v><br class=3D"m_6788252280181015495Apple-interchange-newline"><div><div>Hi=
,<br><br>I=C4=85ve created a pull request with additional text regarding as=
sociating<br>RTP/RTCP packets with the correct =C5=82m=3D=C5=82 line.<br><b=
r><a href=3D"https://github.com/cdh4u/draft-sdp-bundle/pull/10" target=3D"_=
blank">https://github.com/cdh4u/<wbr>draft-sdp-bundle/pull/10</a><br><br><b=
r>Regards,<br><br>Christer<br><br><span class=3D"">________________________=
______<wbr>_________________<br>mmusic mailing list<br><a href=3D"mailto:mm=
usic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br><a href=3D"https://=
www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">https://www.ietf.or=
g/mailman/<wbr>listinfo/mmusic</a><br></span></div></div></blockquote></div=
><br></div><br>______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
<br></blockquote></div><br></div>

--001a114daaacfcf59b053f3dbc2c--


From nobody Wed Oct 19 13:44:27 2016
Return-Path: <bernard.aboba@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05E1D1294C5 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 13:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 bvcXfvKKVlHy for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 13:44:23 -0700 (PDT)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (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 0ACA9129579 for <mmusic@ietf.org>; Wed, 19 Oct 2016 13:44:23 -0700 (PDT)
Received: by mail-vk0-x232.google.com with SMTP id b186so43949438vkb.1 for <mmusic@ietf.org>; Wed, 19 Oct 2016 13:44:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+QmKzb9wVSFhwiMifYzX0dJ6E/wPlV8YjdtHEystTyU=; b=NBx8IbZ2fOyB97hoPMbkQW+9EQ1JbOBk1CMyIXOs8nWb+6Em0TcFQsdzH4WdUMsE9m 7z5qaXcsTc6g08mUjaHrChWLy6oDz6pZVwiMuYsSCsxIr9GoG9n+zh06e7gvc/0zgNQL 1B+lVGLprgvIFDkqzB4VKzVl19kD5+tBYaYXcI03YhAfeiWLMVsRrp/S6vmrhb5VV2HM LgKdwdhInpKxJ9vUHiWN36MysW2baepsiMRjlSze3SSSaXbDdoh4OZQ6SXlhh9Utj9r3 ih81Ws6J3MmAgGo5WKsLR/on0Gw1kV31a3wn6tnfb1qYdSbIXpL6aTYgu4lcNpRHr/Je gBaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+QmKzb9wVSFhwiMifYzX0dJ6E/wPlV8YjdtHEystTyU=; b=MoF3y6qFu9D5NTJ78aA+yTe+agBehGMjiHxykNK9YkxOfIAlUAsAGKFpfcu/EotGG8 QtTWWYXmrkBzv5AV2FJFT08v4ADhN5Bfz76DWXVAMC/wuFd2tgSDAziVpIqlaTJruAWo fkdAWpdPUa1hC3uZ+bdjvIVdGEC6ExTzorILzh9FLPAVeyUxc+vhkcud0Vpp5nM2pz4C cQ27sO3ti9F7uRWXfkN0T/2CXhsP8EilOwKKcYrTToz9hRiiUhNqq22jxqd7x7ORQ9L7 nKCoF8FkjloTV+ldqrNcIcGdXQBsLz89aKpc5BryLN1On2Evtv9xlJa7amRfRqRaHlE+ Vunw==
X-Gm-Message-State: AA6/9RmbhQ7rRCX88iMWM+BJxm6MPZYWMHWzbBbI22mu6PI2BN9TjC9iDJkOwKpKm2mMXcUClR0rNqpQYgAL6A==
X-Received: by 10.31.200.71 with SMTP id y68mr7421564vkf.126.1476909861905; Wed, 19 Oct 2016 13:44:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.7.101 with HTTP; Wed, 19 Oct 2016 13:44:01 -0700 (PDT)
In-Reply-To: <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Wed, 19 Oct 2016 15:44:01 -0500
Message-ID: <CAOW+2dsUfU8fP_UsvgqYqL0TCxF-ds_nkYYH33nRWZn0ZKhCVQ@mail.gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: multipart/alternative; boundary=001a114dc658af2bea053f3ddf51
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FKYp2CngZkQrsaYv2EFlHTu3TIY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 20:44:26 -0000

--001a114dc658af2bea053f3ddf51
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Magnus --

Applying RTP routing rules to RTCP packets does not work in general.
Consider below an RTCP SR packet (from RFC 3550 Section 6.4.1).

This RTCP SR can contain several report blocks, corresponding to multiple
sources.  Therefore it is conceivable that the first report block will
match one RtpReceiver (based on consulting the ssrc_table), and another
report block will match a different RtpReceiver (consulting that
RtpReceiver's ssrc_table).  So portions of the packet would be relevant to
different RtpReceiver objects.

As a result, you cannot use the RTP routing rules to deliver RTCP packets.

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
header |V=3D2|P|    RC   |   PT=3DSR=3D200   |             length          =
  |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                         SSRC of sender                        |
       +=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
sender |              NTP timestamp, most significant word             |
info   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |             NTP timestamp, least significant word             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                         RTP timestamp                         |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     sender's packet count                     |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                      sender's octet count                     |
       +=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
report |                 SSRC_1 (SSRC of first source)                 |
block  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  1    | fraction lost |       cumulative number of packets lost       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |           extended highest sequence number received           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                      interarrival jitter                      |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                         last SR (LSR)                         |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                   delay since last SR (DLSR)                  |
       +=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
report |                 SSRC_2 (SSRC of second source)                |
block  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  2    :                               ...                             :
       +=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
       |                  profile-specific extensions                  |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


On Fri, Oct 14, 2016 at 2:54 AM, Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> Den 2016-10-13 kl. 18:01, skrev Christer Holmberg:
>
>> However, Magnus told me it=E2=80=99s not needed, so I=E2=80=99d like to =
get some input
>> from him.
>>
>> *From:*Cullen Jennings [mailto:fluffy@iii.ca]
>> That looks about right for RTP but I think it is still missing stuff for
>> RTCP handling. Here is the current text we did for JSEP. I prefer the
>> style in which you described it compared to the algorithm style below
>> but I think this might help figure out what to write for RTCP.
>>
>>
> I dislike the algorithmic description JSEP has because it inserts itself
> at position in the stack where I would not myself implement the binding
> handling. The implementations of RTP stacks I have made have never let th=
e
> full RTCP packets be available to the application layer. It has only
> implemented event and request based interface to provide the triggers and
> data associated with the differnet RTCP packets. Thus, from my perspectiv=
e
> the routing of the RTCP packets becomes a question if the SSRC is bound t=
o
> the right m=3D. Then handel the received RTCP packets in that context.
>
> So what might be a suitable RTCP clarification regarding RTCP would be th=
e
> following.
>
> Simply add RTCP in the following sentence:
>
> "Later, when an offerer or answerer receives an RTP packet that does not
> carry the identification-tag, it can associate the packet with the
> correct "m=3D" line using the SSRC value."
>
> so that it reads:
>
> "Later, when an offerer or answerer receives an RTP or RTCP packet that
> does not carry the identification-tag, it can associate the packet with t=
he
> correct "m=3D" line using the SSRC value."
>
> Regarding the second paragraph. If the association has been done accordin=
g
> to this part then also the RTCP packets has an association. If an RTCP
> packet arrives with a non associated SSRC, then many RTCP packets type ca=
n
> still be processed and the information stored in the SSRC related
> information table. Some that are application interaction related, like so=
me
> of the feedback messages can of course not be handled.
>
> One very important aspect here is that the basic RTCP processing do need
> to occur for also non-associated SSRCs. This to ensure that the sender ge=
t
> the RTCP feedback information for congestion control purposes. We want th=
e
> transport layer functions to continue function, even if the application
> can't consume the packets.
>
> Thus, I would consider that the "the packet SHOULD be dropped." needs an
> addition that says after having been processed as received by the RTCP
> layer. If we don't report them as received we skew the congestion control
> information, and it will make any coupled congestion controller that look=
s
> at the set of RTP streams being emitted take the wrong decision. I also
> assumes that a lack of association is in most cases a temporary issue tha=
t
> will be resolved by the regular transmissions.
>
> A long term lack of association is from my perspective indicates an error
> on the signalling plane, so that a renegotation is needed. I do see the
> downside that the sending sides RTP/RTCP stack is lacking the information
> that the packet is being dropped after reception. This could be solved if
> one implemented the RTCP XR packet type Discard Count Metric Reporting (
> https://datatracker.ietf.org/doc/rfc7002/).
> I would use the 01 "Packet to early" for this case.
>
>
> Cheers
>
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=C3=A4r=C3=B6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--001a114dc658af2bea053f3ddf51
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Magnus --<div><br></div><div>Applying RTP routing rules to=
 RTCP packets does not work in general.=C2=A0 Consider below an RTCP SR pac=
ket (from RFC 3550 Section 6.4.1).=C2=A0</div><div><br></div><div>This RTCP=
 SR can contain several report blocks, corresponding to multiple sources.=
=C2=A0 Therefore it is conceivable that the first report block will match o=
ne RtpReceiver (based on consulting the ssrc_table), and another report blo=
ck will match a different RtpReceiver (consulting that RtpReceiver&#39;s ss=
rc_table).=C2=A0 So portions of the packet would be relevant to different R=
tpReceiver objects.=C2=A0</div><div><br></div><div>As a result, you cannot =
use the RTP routing rules to deliver RTCP packets.=C2=A0</div><div><br></di=
v><div><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top=
:0px;margin-bottom:0px;color:rgb(0,0,0)">        0                   1     =
              2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
header |V=3D2|P|    RC   |   PT=3DSR=3D200   |             length          =
  |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                         SSRC of sender                        |
       +=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
sender |              NTP timestamp, most significant word             |
info   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |             NTP timestamp, least significant word             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                         RTP timestamp                         |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     sender&#39;s packet count                     =
|
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                      sender&#39;s octet count                     =
|
       +=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
report |                 SSRC_1 (SSRC of first source)                 |
block  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  1    | fraction lost |       cumulative number of packets lost       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |           extended highest sequence number received           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                      interarrival jitter                      |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                         last SR (LSR)                         |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                   delay since last SR (DLSR)                  |
       +=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
report |                 SSRC_2 (SSRC of second source)                |
block  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  2    :                               ...                             :
       +=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
       |                  profile-specific extensions                  |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</p=
re></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On=
 Fri, Oct 14, 2016 at 2:54 AM, Magnus Westerlund <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:magnus.westerlund@ericsson.com" target=3D"_blank">magnus.west=
erlund@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><span class=3D"">Den 2016-10-13 kl. 18:01, skrev Christer Holmberg:<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><span class=3D"">
However, Magnus told me it=E2=80=99s not needed, so I=E2=80=99d like to get=
 some input<br>
from him.<br>
<br></span>
*From:*Cullen Jennings [mailto:<a href=3D"mailto:fluffy@iii.ca" target=3D"_=
blank">fluffy@iii.ca</a>]<span class=3D""><br>
That looks about right for RTP but I think it is still missing stuff for<br=
>
RTCP handling. Here is the current text we did for JSEP. I prefer the<br>
style in which you described it compared to the algorithm style below<br>
but I think this might help figure out what to write for RTCP.<br>
<br>
</span></blockquote>
<br>
I dislike the algorithmic description JSEP has because it inserts itself at=
 position in the stack where I would not myself implement the binding handl=
ing. The implementations of RTP stacks I have made have never let the full =
RTCP packets be available to the application layer. It has only implemented=
 event and request based interface to provide the triggers and data associa=
ted with the differnet RTCP packets. Thus, from my perspective the routing =
of the RTCP packets becomes a question if the SSRC is bound to the right m=
=3D. Then handel the received RTCP packets in that context.<br>
<br>
So what might be a suitable RTCP clarification regarding RTCP would be the =
following.<br>
<br>
Simply add RTCP in the following sentence:<br>
<br>
&quot;Later, when an offerer or answerer receives an RTP packet that does n=
ot carry the identification-tag, it can associate the packet with the<br>
correct &quot;m=3D&quot; line using the SSRC value.&quot;<br>
<br>
so that it reads:<br>
<br>
&quot;Later, when an offerer or answerer receives an RTP or RTCP packet tha=
t does not carry the identification-tag, it can associate the packet with t=
he correct &quot;m=3D&quot; line using the SSRC value.&quot;<br>
<br>
Regarding the second paragraph. If the association has been done according =
to this part then also the RTCP packets has an association. If an RTCP pack=
et arrives with a non associated SSRC, then many RTCP packets type can stil=
l be processed and the information stored in the SSRC related information t=
able. Some that are application interaction related, like some of the feedb=
ack messages can of course not be handled.<br>
<br>
One very important aspect here is that the basic RTCP processing do need to=
 occur for also non-associated SSRCs. This to ensure that the sender get th=
e RTCP feedback information for congestion control purposes. We want the tr=
ansport layer functions to continue function, even if the application can&#=
39;t consume the packets.<br>
<br>
Thus, I would consider that the &quot;the packet SHOULD be dropped.&quot; n=
eeds an addition that says after having been processed as received by the R=
TCP layer. If we don&#39;t report them as received we skew the congestion c=
ontrol information, and it will make any coupled congestion controller that=
 looks at the set of RTP streams being emitted take the wrong decision. I a=
lso assumes that a lack of association is in most cases a temporary issue t=
hat will be resolved by the regular transmissions.<br>
<br>
A long term lack of association is from my perspective indicates an error o=
n the signalling plane, so that a renegotation is needed. I do see the down=
side that the sending sides RTP/RTCP stack is lacking the information that =
the packet is being dropped after reception. This could be solved if one im=
plemented the RTCP XR packet type Discard Count Metric Reporting (<a href=
=3D"https://datatracker.ietf.org/doc/rfc7002/" rel=3D"noreferrer" target=3D=
"_blank">https://datatracker.ietf.org/<wbr>doc/rfc7002/</a>).<br>
I would use the 01 &quot;Packet to early&quot; for this case.<br>
<br>
<br>
Cheers<br>
<br>
<br>
Magnus Westerlund<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
Services, Media and Network features, Ericsson Research EAB/TXM<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
Ericsson AB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =
Phone=C2=A0 <a href=3D"tel:%2B46%2010%207148287" value=3D"+46107148287" tar=
get=3D"_blank">+46 10 7148287</a><br>
F=C3=A4r=C3=B6gatan 6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0| Mobile <a href=3D"tel:%2B46%2073%200949079" value=3D"+467309490=
79" target=3D"_blank">+46 73 0949079</a><br>
SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@e=
ricsson.com" target=3D"_blank">magnus.westerlund@ericsson.com</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div>

--001a114dc658af2bea053f3ddf51--


From nobody Wed Oct 19 16:12:37 2016
Return-Path: <adam@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2690E12969D for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 16:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.331
X-Spam-Level: 
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] 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 gzczTFx12Af1 for <mmusic@ietfa.amsl.com>; Wed, 19 Oct 2016 16:12:34 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEA6D129510 for <mmusic@ietf.org>; Wed, 19 Oct 2016 16:12:33 -0700 (PDT)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u9JNCSWS056892 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 19 Oct 2016 18:12:29 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110] claimed to be Orochi.local
To: Flemming Andreasen <fandreas@cisco.com>, mmusic <mmusic@ietf.org>
References: <105f1c1e-63b0-e250-663f-b8981bad960e@cisco.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <70816640-d76a-c84d-e0f8-9baf820d943b@nostrum.com>
Date: Wed, 19 Oct 2016 18:12:28 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <105f1c1e-63b0-e250-663f-b8981bad960e@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/g8Buv2onPOpT3y9zD--BCOgUfSw>
Subject: Re: [MMUSIC] Simulcast draft review needed
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 23:12:36 -0000

On 9/22/16 18:44, Flemming Andreasen wrote:
> Please note that we also have the simulcast draft
>
> https://www.ietf.org/id/draft-ietf-mmusic-sdp-simulcast-05.txt
>
> to go along with this, and we really need some reviews of that one 
> too. If you have some time to review it, please do so and send your 
> comments to the list (incl. "looks good"). 

I'm one of the dedicated volunteers who agreed to review this document. 
I apologize for the delay in providing feedback.

In general, this document looks to be in really good shape. I have a 
handful of comments, some editorial, and some minor technical. I don't 
see any major technical issues. The largest issue I have is that one of 
the examples contravenes the recommendations in avtext-rid, and is 
consequently likely to cause interop failures.


Technical:

Section 4, REQ-1.2 -- it's not clear to me how this requirement is met. 
The current mechanism does not allow implementations to determine which 
streams are part of a single simulcast media source by looking at the 
RTP/RTCP in isolation. The SDP must be used in concert with the RTP/RTCP 
information. This requirement needs to be either removed or clarified.

Section 6.3.2, paragraph 3, states: "The answerer MUST NOT add any 
alternative SCID that were not present in the offer." This seems like an 
odd restriction on SCID in the send direction. It is not reasonable for 
the offerer to know how many Simulcast Formats a single Simulcast Stream 
that the other end can send might be expressed in. Functionally, this is 
the same as saying that the offerer gets to choose how many PTs the 
answer is allowed to contain, which is a new (and presumably 
unnecessary) restriction. The minimal change to fix this issue would be 
to add "in the receive direction" to the sentence I quote.

I'm sure the conversation happened after -05 was published, but to make 
sure it doesn't get lost: we're not supporting declarative use, so 
section 6.4 should be removed.

The most complicated SDP example (Figure 6, on page 20) uses 
nonoverlapping RIDs for the two different video media sections. This 
implies that the RID space is globally unique in some way. In practice, 
RIDs are scoped to be unique only within a single media section. 
Implementors are likely to incorrectly infer from this example that RIDs 
need to be unique even between media sections, which can lead to interop 
failures. Please adjust the example so that the RIDs in the second media 
section start over at 1 rather than resuming where the first video 
section left off.


Editorial:

In the terminology section, the second sentence of the definition of 
Simulcast Streams (starting "Decoding a dependent stream...") is 
difficult to parse and difficult to understand. Assuming I did 
eventually understand what it's saying, I don't think it necessary or 
helpful, and can probably be removed rather than fixed.

The first comma in the definition of Simulcast Format should be a colon.

Section 3 should also mention the use case in which the media switch 
does not have access to the media contents, as in the type of 
conferences that PERC is being designed for.

Section 3.2 should contain commas around the phrase "for example" in the 
second sentence of the first paragraph.

The prose in section 6.1 seems to suffer from the lack of a formal term 
for the construct that the ABNF calls "sc-alt-list." For example, the 
third paragraph says "each SCID is separated by a semicolon." That's 
inaccurate and confusing: the syntax clearly indicates that SCIDs are 
indicated by commas, and the "sc-alt-list" construct is separated by 
semicolons. I think the smallest change we can make to fix this is to 
say "each _stream_ is separated by as semicolon", but that's a bit 
unsatisfying. I think it would be better to define an English term for 
this "sc-alt-list" thing and use it where appropriate.

This missing terminology shows up again in the fourth paragraph of 
section 6.2: the construct "The number of (non-alternative, see above) 
SCID..." is awkward and hard to follow. If we define a term that means 
this "sc-alt-list" thing, it should be used here. If we don't, then I 
again suggest using the term "stream" rather than "(non-alternative, see 
above) SCID".

In the seventh paragraph of section 6.2 (starting "A simulcast 
stream..."), the sentence "...such 'related' formats MUST NOT be defined 
as SCID and listed..." needs to have something like "having their own" 
inserted, to read: "...such 'related' formats MUST NOT be defined as 
having their own SCID and listed..."

The following paragraph contains a sentence fragment that can be turned 
into a sentence by changing "...each of which can be individually 
prefixed..." to "...each can be individually prefixed..."

The final paragraph of section 6.3.2 contains a comma preceded by a 
space. This comma should be removed.

Section 8 should clearly indicate that the technique described in the 
third paragraph is out of scope for this document, and that additional 
specification would be necessary to implement simulcast in a multicast 
context.

/a



From nobody Thu Oct 20 00:18:43 2016
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 34C041294E5 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 00:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 pmy0ne1DUDzU for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 00:18:37 -0700 (PDT)
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 EF0191294A8 for <mmusic@ietf.org>; Thu, 20 Oct 2016 00:18:36 -0700 (PDT)
X-AuditID: c1b4fb30-b73ff70000000cb2-8d-58086fca6894
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by  (Symantec Mail Security) with SMTP id E7.FE.03250.ACF68085; Thu, 20 Oct 2016 09:18:35 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0319.002; Thu, 20 Oct 2016 09:18:34 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Bernard Aboba <bernard.aboba@gmail.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
Thread-Index: AQHSJHSivk5Ucbs2BE2kFscuEARQNKCmW5CAgAAxTzCAAOkBgIAIsrqAgADlhQA=
Date: Thu, 20 Oct 2016 07:18:34 +0000
Message-ID: <D42E46F4.116F1%christer.holmberg@ericsson.com>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <CAOW+2dsUfU8fP_UsvgqYqL0TCxF-ds_nkYYH33nRWZn0ZKhCVQ@mail.gmail.com>
In-Reply-To: <CAOW+2dsUfU8fP_UsvgqYqL0TCxF-ds_nkYYH33nRWZn0ZKhCVQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_D42E46F4116F1christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOIsWRmVeSWpSXmKPExsUyM2K7q+7pfI4Ig8cLuC027PvPbPFh/Q9G i6nLH7M4MHvsnHWX3WPJkp9MHpfPf2QMYI7isklJzcksSy3St0vgynh38wt7wYmNjBW3P65m aWA82c/YxcjJISFgIvF6SR9TFyMXh5DAekaJFTPmQTmLgZy5K9i7GDk42AQsJLr/aYM0iAgk SjT+OAXWzCzgIfH98zRmEFtYIEPi89FlTCDlIgKZEitW+kGU+0ns2TibFcRmEVCVmLp+K5jN K2At8XjyXHaIVWuYJI5sWskCkuAUCJT4//gS2ExGATGJ76fWMEHsEpe49WQ+E8TRAhJL9pxn hrBFJV4+/scKsldUQE9izf0wiLCixMdX+6DOTJA4M6URaq+gxMmZT1gmMIrOQjJ1FpKyWUjK IOIGEu/PzWeGsLUlli18DWXrS2z8cpYRwraWeNt3mhVZzQJGjlWMosWpxUm56UZGeqlFmcnF xfl5enmpJZsYgdF5cMtvgx2ML587HmIU4GBU4uF98IY9Qog1say4MvcQowQHs5II77Ecjggh 3pTEyqrUovz4otKc1OJDjNIcLErivGYr74cLCaQnlqRmp6YWpBbBZJk4OKUaGDslU2v7WmZ1 n/S//NllcvK0yupl9xfuPvmh7WzUspivT2uF9ON7Ku0OupyrZ8o2OnXB3jCuos3F7XjdIZad a6d7nhaTrvue+IODV5ar79bFgCO71tR927vu2SaLw05rVU8/cTRbHKa8PfyGSO7DXr55hw0U F19U1KqWWl/9xO66hvf37MKNq5RYijMSDbWYi4oTAdbPg+jKAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/NJSB4Dx-9_HchNF-SB61InaqyiU>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 07:18:40 -0000

--_000_D42E46F4116F1christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

In BUNDLE, can=92t we just say that an RTCP packet can be associated with m=
ultiple SSRCs, and therefore possibly with m- lines?

Regards,

Christer

From: Bernard Aboba <bernard.aboba@gmail.com<mailto:bernard.aboba@gmail.com=
>>
Date: Wednesday 19 October 2016 at 23:44
To: Magnus Westerlund <magnus.westerlund@ericsson.com<mailto:magnus.westerl=
und@ericsson.com>>
Cc: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmb=
erg@ericsson.com>>, Cullen Jennings <fluffy@iii.ca<mailto:fluffy@iii.ca>>, =
"mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusic@ie=
tf.org>>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32=
 - RTP demux - Pull Request

Magnus --

Applying RTP routing rules to RTCP packets does not work in general.  Consi=
der below an RTCP SR packet (from RFC 3550 Section 6.4.1).

This RTCP SR can contain several report blocks, corresponding to multiple s=
ources.  Therefore it is conceivable that the first report block will match=
 one RtpReceiver (based on consulting the ssrc_table), and another report b=
lock will match a different RtpReceiver (consulting that RtpReceiver's ssrc=
_table).  So portions of the packet would be relevant to different RtpRecei=
ver objects.

As a result, you cannot use the RTP routing rules to deliver RTCP packets.


        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
header |V=3D2|P|    RC   |   PT=3DSR=3D200   |             length          =
  |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                         SSRC of sender                        |
       +=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
sender |              NTP timestamp, most significant word             |
info   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |             NTP timestamp, least significant word             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                         RTP timestamp                         |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     sender's packet count                     |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                      sender's octet count                     |
       +=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
report |                 SSRC_1 (SSRC of first source)                 |
block  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  1    | fraction lost |       cumulative number of packets lost       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |           extended highest sequence number received           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                      interarrival jitter                      |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                         last SR (LSR)                         |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                   delay since last SR (DLSR)                  |
       +=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
report |                 SSRC_2 (SSRC of second source)                |
block  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  2    :                               ...                             :
       +=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D=
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
       |                  profile-specific extensions                  |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

On Fri, Oct 14, 2016 at 2:54 AM, Magnus Westerlund <magnus.westerlund@erics=
son.com<mailto:magnus.westerlund@ericsson.com>> wrote:
Den 2016-10-13 kl. 18:01, skrev Christer Holmberg:
However, Magnus told me it=92s not needed, so I=92d like to get some input
from him.

*From:*Cullen Jennings [mailto:fluffy@iii.ca<mailto:fluffy@iii.ca>]
That looks about right for RTP but I think it is still missing stuff for
RTCP handling. Here is the current text we did for JSEP. I prefer the
style in which you described it compared to the algorithm style below
but I think this might help figure out what to write for RTCP.


I dislike the algorithmic description JSEP has because it inserts itself at=
 position in the stack where I would not myself implement the binding handl=
ing. The implementations of RTP stacks I have made have never let the full =
RTCP packets be available to the application layer. It has only implemented=
 event and request based interface to provide the triggers and data associa=
ted with the differnet RTCP packets. Thus, from my perspective the routing =
of the RTCP packets becomes a question if the SSRC is bound to the right m=
=3D. Then handel the received RTCP packets in that context.

So what might be a suitable RTCP clarification regarding RTCP would be the =
following.

Simply add RTCP in the following sentence:

"Later, when an offerer or answerer receives an RTP packet that does not ca=
rry the identification-tag, it can associate the packet with the
correct "m=3D" line using the SSRC value."

so that it reads:

"Later, when an offerer or answerer receives an RTP or RTCP packet that doe=
s not carry the identification-tag, it can associate the packet with the co=
rrect "m=3D" line using the SSRC value."

Regarding the second paragraph. If the association has been done according =
to this part then also the RTCP packets has an association. If an RTCP pack=
et arrives with a non associated SSRC, then many RTCP packets type can stil=
l be processed and the information stored in the SSRC related information t=
able. Some that are application interaction related, like some of the feedb=
ack messages can of course not be handled.

One very important aspect here is that the basic RTCP processing do need to=
 occur for also non-associated SSRCs. This to ensure that the sender get th=
e RTCP feedback information for congestion control purposes. We want the tr=
ansport layer functions to continue function, even if the application can't=
 consume the packets.

Thus, I would consider that the "the packet SHOULD be dropped." needs an ad=
dition that says after having been processed as received by the RTCP layer.=
 If we don't report them as received we skew the congestion control informa=
tion, and it will make any coupled congestion controller that looks at the =
set of RTP streams being emitted take the wrong decision. I also assumes th=
at a lack of association is in most cases a temporary issue that will be re=
solved by the regular transmissions.

A long term lack of association is from my perspective indicates an error o=
n the signalling plane, so that a renegotation is needed. I do see the down=
side that the sending sides RTP/RTCP stack is lacking the information that =
the packet is being dropped after reception. This could be solved if one im=
plemented the RTCP XR packet type Discard Count Metric Reporting (https://d=
atatracker.ietf.org/doc/rfc7002/).
I would use the 01 "Packet to early" for this case.


Cheers


Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287<tel:%2B46%2010%20714828=
7>
F=E4r=F6gatan 6                 | Mobile +46 73 0949079<tel:%2B46%2073%2009=
49079>
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com<mailto=
:magnus.westerlund@ericsson.com>
----------------------------------------------------------------------


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


--_000_D42E46F4116F1christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <9466D5C814A91942A87CD0F55C80FF2E@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>In BUNDLE, can=92t we just say that an RTCP packet can be associated w=
ith multiple SSRCs, and therefore possibly with m- lines?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Bernard Aboba &lt;<a href=3D"=
mailto:bernard.aboba@gmail.com">bernard.aboba@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday 19 October 2016 at =
23:44<br>
<span style=3D"font-weight:bold">To: </span>Magnus Westerlund &lt;<a href=
=3D"mailto:magnus.westerlund@ericsson.com">magnus.westerlund@ericsson.com</=
a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>Christer Holmberg &lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com</=
a>&gt;, Cullen Jennings &lt;<a href=3D"mailto:fluffy@iii.ca">fluffy@iii.ca<=
/a>&gt;, &quot;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&quot;
 &lt;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [MMUSIC] Review of dra=
ft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">Magnus --
<div><br>
</div>
<div>Applying RTP routing rules to RTCP packets does not work in general.&n=
bsp; Consider below an RTCP SR packet (from RFC 3550 Section 6.4.1).&nbsp;<=
/div>
<div><br>
</div>
<div>This RTCP SR can contain several report blocks, corresponding to multi=
ple sources.&nbsp; Therefore it is conceivable that the first report block =
will match one RtpReceiver (based on consulting the ssrc_table), and anothe=
r report block will match a different
 RtpReceiver (consulting that RtpReceiver's ssrc_table).&nbsp; So portions =
of the packet would be relevant to different RtpReceiver objects.&nbsp;</di=
v>
<div><br>
</div>
<div>As a result, you cannot use the RTP routing rules to deliver RTCP pack=
ets.&nbsp;</div>
<div><br>
</div>
<div>
<pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;ma=
rgin-bottom:0px;color:rgb(0,0,0)">        0                   1            =
       2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;
header |V=3D2|P|    RC   |   PT=3DSR=3D200   |             length          =
  |
       &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;
       |                         SSRC of sender                        |
       &#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43=
;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=
=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D=
&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;
sender |              NTP timestamp, most significant word             |
info   &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;
       |             NTP timestamp, least significant word             |
       &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;
       |                         RTP timestamp                         |
       &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;
       |                     sender's packet count                     |
       &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;
       |                      sender's octet count                     |
       &#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43=
;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=
=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D=
&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;
report |                 SSRC_1 (SSRC of first source)                 |
block  &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;
  1    | fraction lost |       cumulative number of packets lost       |
       &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;
       |           extended highest sequence number received           |
       &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;
       |                      interarrival jitter                      |
       &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;
       |                         last SR (LSR)                         |
       &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;
       |                   delay since last SR (DLSR)                  |
       &#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43=
;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=
=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D=
&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;
report |                 SSRC_2 (SSRC of second source)                |
block  &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;
  2    :                               ...                             :
       &#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43=
;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=
=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D=
&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;=3D&#43;
       |                  profile-specific extensions                  |
       &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;</pre>
</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Fri, Oct 14, 2016 at 2:54 AM, Magnus Westerlu=
nd <span dir=3D"ltr">
&lt;<a href=3D"mailto:magnus.westerlund@ericsson.com" target=3D"_blank">mag=
nus.westerlund@ericsson.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<span class=3D"">Den 2016-10-13 kl. 18:01, skrev Christer Holmberg:<br>
</span>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<span class=3D"">However, Magnus told me it=92s not needed, so I=92d like t=
o get some input<br>
from him.<br>
<br>
</span>*From:*Cullen Jennings [mailto:<a href=3D"mailto:fluffy@iii.ca" targ=
et=3D"_blank">fluffy@iii.ca</a>]<span class=3D""><br>
That looks about right for RTP but I think it is still missing stuff for<br=
>
RTCP handling. Here is the current text we did for JSEP. I prefer the<br>
style in which you described it compared to the algorithm style below<br>
but I think this might help figure out what to write for RTCP.<br>
<br>
</span></blockquote>
<br>
I dislike the algorithmic description JSEP has because it inserts itself at=
 position in the stack where I would not myself implement the binding handl=
ing. The implementations of RTP stacks I have made have never let the full =
RTCP packets be available to the
 application layer. It has only implemented event and request based interfa=
ce to provide the triggers and data associated with the differnet RTCP pack=
ets. Thus, from my perspective the routing of the RTCP packets becomes a qu=
estion if the SSRC is bound to the
 right m=3D. Then handel the received RTCP packets in that context.<br>
<br>
So what might be a suitable RTCP clarification regarding RTCP would be the =
following.<br>
<br>
Simply add RTCP in the following sentence:<br>
<br>
&quot;Later, when an offerer or answerer receives an RTP packet that does n=
ot carry the identification-tag, it can associate the packet with the<br>
correct &quot;m=3D&quot; line using the SSRC value.&quot;<br>
<br>
so that it reads:<br>
<br>
&quot;Later, when an offerer or answerer receives an RTP or RTCP packet tha=
t does not carry the identification-tag, it can associate the packet with t=
he correct &quot;m=3D&quot; line using the SSRC value.&quot;<br>
<br>
Regarding the second paragraph. If the association has been done according =
to this part then also the RTCP packets has an association. If an RTCP pack=
et arrives with a non associated SSRC, then many RTCP packets type can stil=
l be processed and the information
 stored in the SSRC related information table. Some that are application in=
teraction related, like some of the feedback messages can of course not be =
handled.<br>
<br>
One very important aspect here is that the basic RTCP processing do need to=
 occur for also non-associated SSRCs. This to ensure that the sender get th=
e RTCP feedback information for congestion control purposes. We want the tr=
ansport layer functions to continue
 function, even if the application can't consume the packets.<br>
<br>
Thus, I would consider that the &quot;the packet SHOULD be dropped.&quot; n=
eeds an addition that says after having been processed as received by the R=
TCP layer. If we don't report them as received we skew the congestion contr=
ol information, and it will make any coupled
 congestion controller that looks at the set of RTP streams being emitted t=
ake the wrong decision. I also assumes that a lack of association is in mos=
t cases a temporary issue that will be resolved by the regular transmission=
s.<br>
<br>
A long term lack of association is from my perspective indicates an error o=
n the signalling plane, so that a renegotation is needed. I do see the down=
side that the sending sides RTP/RTCP stack is lacking the information that =
the packet is being dropped after
 reception. This could be solved if one implemented the RTCP XR packet type=
 Discard Count Metric Reporting (<a href=3D"https://datatracker.ietf.org/do=
c/rfc7002/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.o=
rg/<wbr>doc/rfc7002/</a>).<br>
I would use the 01 &quot;Packet to early&quot; for this case.<br>
<br>
<br>
Cheers<br>
<br>
<br>
Magnus Westerlund<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
Services, Media and Network features, Ericsson Research EAB/TXM<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
Ericsson AB&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| =
Phone&nbsp; <a href=3D"tel:%2B46%2010%207148287" value=3D"&#43;46107148287"=
 target=3D"_blank">
&#43;46 10 7148287</a><br>
F=E4r=F6gatan 6&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;| Mobile <a href=3D"tel:%2B46%2073%200949079" value=3D"&#43;46730949079" =
target=3D"_blank">
&#43;46 73 0949079</a><br>
SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@e=
ricsson.com" target=3D"_blank">
magnus.westerlund@ericsson.com</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
-----
<div class=3D"HOEnZb">
<div class=3D"h5"><br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D42E46F4116F1christerholmbergericssoncom_--


From nobody Thu Oct 20 00:46:10 2016
Return-Path: <magnus.westerlund@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 1E5CC1294E5 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 00:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 x-u1oylATfvZ for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 00:46:06 -0700 (PDT)
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 7458B129511 for <mmusic@ietf.org>; Thu, 20 Oct 2016 00:46:06 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-73-5808763c46b6
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by  (Symantec Mail Security) with SMTP id C6.C3.02458.C3678085; Thu, 20 Oct 2016 09:46:04 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.80) with Microsoft SMTP Server id 14.3.319.2; Thu, 20 Oct 2016 09:46:02 +0200
To: Bernard Aboba <bernard.aboba@gmail.com>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <CAOW+2dsUfU8fP_UsvgqYqL0TCxF-ds_nkYYH33nRWZn0ZKhCVQ@mail.gmail.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <d0d6497b-ce6e-226a-08af-011fc037f89e@ericsson.com>
Date: Thu, 20 Oct 2016 09:45:54 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CAOW+2dsUfU8fP_UsvgqYqL0TCxF-ds_nkYYH33nRWZn0ZKhCVQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyM2K7n65NGUeEwcfVehYb9v1ntviw/gej xdTlj1kcmD12zrrL7rFkyU8mj8vnPzIGMEdx2aSk5mSWpRbp2yVwZZyd2MlYcN6jovXHJ5YG xi0mXYycHBICJhIfTjxm7GLk4hASWM8osebNWmYIZzmjRPOM6awgVcICGRItL7sYQWwRAW2J vm/7mCCK1jBJHNm0kgUkwSxQJ3Fq3j82EJtNwELi5o9GMJtXwF5i16457CA2i4CqROvJdUwg tqhAjMT1Z4+gagQlTs58AjaHUyBQ4v/jS8wQMy0kZs4/zwhhy0s0b50NFhcCOqKhqYN1AqPA LCTts5C0zELSsoCReRWjaHFqcXFuupGRXmpRZnJxcX6eXl5qySZGYLge3PLbagfjweeOhxgF OBiVeHgfvGGPEGJNLCuuzD3EKMHBrCTCO6WQI0KINyWxsiq1KD++qDQntfgQozQHi5I4r9nK ++FCAumJJanZqakFqUUwWSYOTqkGxpALBdseFzm5ODw90XX7WY9HoPiigvNrL168Ec/cr935 O/9t1oTJF2+Zfl2U5HNwZvq5la6+wYGHXz+7ciUip+XN4WWpsnIWj/ubjt0rsT3QKWDYI9g1 UdNrduLiMBt74cqTlTdbSs2nrZ0foWL/Q+FKa65S2f2X8cm6FcmHlvPJ26qfVi7+q8RSnJFo qMVcVJwIAIuGrRZTAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/eduheecchvMBudwjnc25avIE2Xg>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 07:46:09 -0000

Hi,

Not disagreeing. I was not well formulated what I wrote, it was not 
conveying what it needed to say. Colin also pointed out that talking 
about packets is misleading. Something that is especially true for RTCP, 
where all information is associated with SSRCs, and as you correctly 
point out a single RTCP packet can contain multiple information elements 
related to different RTP streams.

So, yes we need to change the text. I think we first have to ensure that 
there are not anything hiding in the discussion Paul raised.

Cheers

Magnus


Den 2016-10-19 kl. 22:44, skrev Bernard Aboba:
> Magnus --
>
> Applying RTP routing rules to RTCP packets does not work in general.
> Consider below an RTCP SR packet (from RFC 3550 Section 6.4.1).
>
> This RTCP SR can contain several report blocks, corresponding to
> multiple sources.  Therefore it is conceivable that the first report
> block will match one RtpReceiver (based on consulting the ssrc_table),
> and another report block will match a different RtpReceiver (consulting
> that RtpReceiver's ssrc_table).  So portions of the packet would be
> relevant to different RtpReceiver objects.
>
> As a result, you cannot use the RTP routing rules to deliver RTCP packets.
>
>         0                   1                   2                   3
>         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> header |V=2|P|    RC   |   PT=SR=200   |             length            |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                         SSRC of sender                        |
>        +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
> sender |              NTP timestamp, most significant word             |
> info   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |             NTP timestamp, least significant word             |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                         RTP timestamp                         |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                     sender's packet count                     |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                      sender's octet count                     |
>        +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
> report |                 SSRC_1 (SSRC of first source)                 |
> block  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   1    | fraction lost |       cumulative number of packets lost       |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |           extended highest sequence number received           |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                      interarrival jitter                      |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                         last SR (LSR)                         |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        |                   delay since last SR (DLSR)                  |
>        +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
> report |                 SSRC_2 (SSRC of second source)                |
> block  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   2    :                               ...                             :
>        +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
>        |                  profile-specific extensions                  |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
> On Fri, Oct 14, 2016 at 2:54 AM, Magnus Westerlund
> <magnus.westerlund@ericsson.com <mailto:magnus.westerlund@ericsson.com>>
> wrote:
>
>     Den 2016-10-13 kl. 18:01, skrev Christer Holmberg:
>
>         However, Magnus told me itâ€™s not needed, so Iâ€™d like to get some
>         input
>         from him.
>
>         *From:*Cullen Jennings [mailto:fluffy@iii.ca <mailto:fluffy@iii.ca>]
>         That looks about right for RTP but I think it is still missing
>         stuff for
>         RTCP handling. Here is the current text we did for JSEP. I
>         prefer the
>         style in which you described it compared to the algorithm style
>         below
>         but I think this might help figure out what to write for RTCP.
>
>
>     I dislike the algorithmic description JSEP has because it inserts
>     itself at position in the stack where I would not myself implement
>     the binding handling. The implementations of RTP stacks I have made
>     have never let the full RTCP packets be available to the application
>     layer. It has only implemented event and request based interface to
>     provide the triggers and data associated with the differnet RTCP
>     packets. Thus, from my perspective the routing of the RTCP packets
>     becomes a question if the SSRC is bound to the right m=. Then handel
>     the received RTCP packets in that context.
>
>     So what might be a suitable RTCP clarification regarding RTCP would
>     be the following.
>
>     Simply add RTCP in the following sentence:
>
>     "Later, when an offerer or answerer receives an RTP packet that does
>     not carry the identification-tag, it can associate the packet with the
>     correct "m=" line using the SSRC value."
>
>     so that it reads:
>
>     "Later, when an offerer or answerer receives an RTP or RTCP packet
>     that does not carry the identification-tag, it can associate the
>     packet with the correct "m=" line using the SSRC value."
>
>     Regarding the second paragraph. If the association has been done
>     according to this part then also the RTCP packets has an
>     association. If an RTCP packet arrives with a non associated SSRC,
>     then many RTCP packets type can still be processed and the
>     information stored in the SSRC related information table. Some that
>     are application interaction related, like some of the feedback
>     messages can of course not be handled.
>
>     One very important aspect here is that the basic RTCP processing do
>     need to occur for also non-associated SSRCs. This to ensure that the
>     sender get the RTCP feedback information for congestion control
>     purposes. We want the transport layer functions to continue
>     function, even if the application can't consume the packets.
>
>     Thus, I would consider that the "the packet SHOULD be dropped."
>     needs an addition that says after having been processed as received
>     by the RTCP layer. If we don't report them as received we skew the
>     congestion control information, and it will make any coupled
>     congestion controller that looks at the set of RTP streams being
>     emitted take the wrong decision. I also assumes that a lack of
>     association is in most cases a temporary issue that will be resolved
>     by the regular transmissions.
>
>     A long term lack of association is from my perspective indicates an
>     error on the signalling plane, so that a renegotation is needed. I
>     do see the downside that the sending sides RTP/RTCP stack is lacking
>     the information that the packet is being dropped after reception.
>     This could be solved if one implemented the RTCP XR packet type
>     Discard Count Metric Reporting
>     (https://datatracker.ietf.org/doc/rfc7002/
>     <https://datatracker.ietf.org/doc/rfc7002/>).
>     I would use the 01 "Packet to early" for this case.
>
>
>     Cheers
>
>
>     Magnus Westerlund
>
>     ----------------------------------------------------------------------
>     Services, Media and Network features, Ericsson Research EAB/TXM
>     ----------------------------------------------------------------------
>     Ericsson AB                 | Phone  +46 10 7148287
>     <tel:%2B46%2010%207148287>
>     FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
>     <tel:%2B46%2073%200949079>
>     SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>     <mailto:magnus.westerlund@ericsson.com>
>     ----------------------------------------------------------------------
>
>
>     _______________________________________________
>     mmusic mailing list
>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>     https://www.ietf.org/mailman/listinfo/mmusic
>     <https://www.ietf.org/mailman/listinfo/mmusic>
>
>


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Oct 20 01:51:29 2016
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 827EF129532 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 01:51:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 OWfrAYuDaxCs for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 01:51:26 -0700 (PDT)
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 7F9211294A8 for <mmusic@ietf.org>; Thu, 20 Oct 2016 01:51:26 -0700 (PDT)
X-AuditID: c1b4fb3a-e95069800000099a-ef-5808858c49a9
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by  (Symantec Mail Security) with SMTP id E7.74.02458.C8588085; Thu, 20 Oct 2016 10:51:24 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0319.002; Thu, 20 Oct 2016 10:51:23 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
Thread-Index: AQHSKq8ixsJ53smzZ0iYfg1cr+NRBw==
Date: Thu, 20 Oct 2016 08:51:22 +0000
Message-ID: <D42E61A0.11767%christer.holmberg@ericsson.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com>
In-Reply-To: <D42A7728.113D4%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_D42E61A011767christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsUyM2K7n25PK0eEwc6vBhZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxsJjO9gLpjpXrGp9z9rAuNiyi5GTQ0LARGLf5kbmLkYuDiGB 9YwSH1fOZYVwFjNKfHowiamLkYODTcBCovufNkiDiECsxNd175lAbGGBGIlbK/+ww8SvnnnP CmHrSbRM62QFaWURUJVYtJ8RJMwrYC0xdWkrWKsQkH394mmwVk4BG4nu9TfAWhkFxCS+n1oD VsMsIC5x68l8Jog7BSSW7DnPDGGLSrx8/A9svCjQqjX3w0BMCQFFieX9chCdCRKfrx1igdgq KHFy5hOWCYwis5AMnYWkbBaSMoi4gcT7c/OZIWxtiWULX0PZ+hIbv5xlhLCtJa5OPcuErGYB I8cqRtHi1OLi3HQjI73Uoszk4uL8PL281JJNjMCoOrjlt9UOxoPPHQ8xCnAwKvHwPnjDHiHE mlhWXJl7iFGCg1lJhDe9hSNCiDclsbIqtSg/vqg0J7X4EKM0B4uSOK/ZyvvhQgLpiSWp2amp BalFMFkmDk6pBkbz2LCTojdldy9lDuBhav/Aa5AxN5wrqLly3sTwyRWuW6yEnd76B59zmpju H8BgWmkqP/ntrqvr4qa+VSrtlwgxjOPs+saV0aUyn22lQcPjiwkztrG6b2bK49ufcKeSq6rz smnsPr91dY7aD3/lpW36+26PkjIvk2D2SvUnSttXv+5c83B2nhJLcUaioRZzUXEiAHEoCG2m AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FETizMixQ3VCGvvvGMTW8C2cSFM>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 08:51:28 -0000

--_000_D42E61A011767christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Anyone having an opinion on this?

It may impact a couple of drafts which are about to be finalised, so it wou=
ld be good to hear what people think.

Regards,

Christer

From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on b=
ehalf of Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.=
holmberg@ericsson.com>>
Date: Monday 17 October 2016 at 12:37
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>
Subject: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in =
SDP answer?

Hi,

The issue in this e-mail has came up during ICE discussions related to BFCP=
 and SCTP.

Section 4.1.1.2 of draft-ietf-mmusic-ice-sip-sdp-10 says:

   "The default candidates are added to the SDP as the default
   destination for media.  For streams based on RTP, this is done by
   placing the IP address and port of the RTP candidate into the "c=3D"
   and "m=3D" lines, respectively.=94

=85and:

   "The transport addresses that will be the default destination for
   media when communicating with non-ICE peers MUST also be present as
   candidates in one or more a=3Dcandidate lines."

Assume the offerer sends an offer. The default candidate is TCP-based, whic=
h will be reflected in the m- line (e.g., TCP/DTLS/SCTP). The offer also co=
ntains UDP-based candidates.

Now, assume the default candidate of the answerer is UDP-based (perhaps the=
 answerer doesn=92t even support TCP). However, according to the O/A rules,=
 the answerer cannot change the m- line proto in the answer (e.g., UDP/DTLS=
/SCTP). So, if I understand correctly, it means that the answerer must reje=
ct the m- line =96 even if there are UDP-based candidates that the answerer=
 would support.

A solution to this would be to NOT mandate the m- line to match the default=
 candidate in the answer. So, in the example above, the answerer could incl=
ude (TCP/DTLS/SCTP) in the m- line, but ONLY provide UDP candidates.

Another solution would to always mandate support of one or more specific tr=
ansports, and specify that the default candidate MUST use that transport.

Regards,

Christer



--_000_D42E61A011767christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <11E99D62EA283B4FA6C2075E7F3409B5@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Anyone having an opinion on this?</div>
<div><br>
</div>
<div>It may impact a couple of drafts which are about to be finalised, so i=
t would be good to hear what people think.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>mmusic &lt;<a href=3D"mailto:=
mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a>&gt; on behalf of Chris=
ter Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">christer=
.holmberg@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Monday 17 October 2016 at 12:=
37<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:mmusic@=
ietf.org">mmusic@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org">=
mmusic@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[MMUSIC] draft-ice-sip-sdp=
: m- line matching default candidate in SDP answer?<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;">
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>Hi,</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>The issue in this e-mail has came up during ICE discussions related to BFC=
P and SCTP.</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>Section 4.1.1.2 of draft-ietf-mmusic-ice-sip-sdp-10 says:</font></div>
<div>
<pre style=3D"color: rgb(0, 0, 0); font-size: 14px; font-variant-ligatures:=
 normal; orphans: 2; widows: 2; word-wrap: break-word; white-space: pre-wra=
p;"><font face=3D"Calibri">   &quot;The default candidates are added to the=
 SDP as the default
   destination for media.  For streams based on RTP, this is done by
   placing the IP address and port of the RTP candidate into the &quot;c=3D=
&quot;
   and &quot;m=3D&quot; lines, respectively.=94</font></pre>
<pre style=3D"color: rgb(0, 0, 0); font-size: 14px; font-variant-ligatures:=
 normal; orphans: 2; widows: 2; word-wrap: break-word; white-space: pre-wra=
p;"><font face=3D"Calibri">=85and:</font></pre>
<pre style=3D"color: rgb(0, 0, 0); font-size: 14px; font-variant-ligatures:=
 normal; orphans: 2; widows: 2; word-wrap: break-word; white-space: pre-wra=
p;"><pre style=3D"font-variant-ligatures: normal; word-wrap: break-word; wh=
ite-space: pre-wrap;"><font face=3D"Calibri">   &quot;The transport address=
es that will be the default destination for
   media when communicating with non-ICE peers MUST also be present as
   candidates in one or more a=3Dcandidate lines.&quot;</font></pre></pre>
</div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>Assume the offerer sends an offer. The default c</font><span style=3D"font=
-family: Calibri;">andidate is TCP-based, which will be reflected in the m-=
 line (e.g., TCP/DTLS/SCTP). The offer
 also contains UDP-based candidates.</span></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>Now, assume the default candidate of the answerer is UDP-based (perhaps th=
e answerer doesn=92t even support TCP). However, according to the O/A rules=
, the answerer cannot change the m- line
 proto in the answer (e.g., UDP/DTLS/SCTP).&nbsp;</font><span style=3D"font=
-family: Calibri;">So, if I understand correctly, it means that the answere=
r must reject the m- line =96 even if there are UDP-based candidates that t=
he answerer would support.</span></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>A solution to this would be to NOT mandate the m- line to match the defaul=
t candidate in the answer. So, in the example above, the answerer could inc=
lude (TCP/DTLS/SCTP) in the m- line,
 but ONLY provide UDP candidates.</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;">Another solution would=
 to always mandate support of one or more specific transports, and specify =
that the default candidate MUST use that transport.</div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>Regards,</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
>Christer</font></div>
<div style=3D"color: rgb(0, 0, 0); font-size: 14px;"><font face=3D"Calibri"=
><br>
</font></div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D42E61A011767christerholmbergericssoncom_--


From nobody Thu Oct 20 04:42:51 2016
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 CAE041298C4 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 04:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 P7Gtmf6r_6yE for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 04:42:49 -0700 (PDT)
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 182451298C3 for <mmusic@ietf.org>; Thu, 20 Oct 2016 04:42:48 -0700 (PDT)
X-AuditID: c1b4fb30-f60a598000000cb2-fb-5808adb785bf
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by  (Symantec Mail Security) with SMTP id B6.2F.03250.7BDA8085; Thu, 20 Oct 2016 13:42:47 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0319.002; Thu, 20 Oct 2016 13:42:45 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Bernard Aboba <bernard.aboba@gmail.com>, Colin Perkins <csp@csperkins.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - A new text proposal
Thread-Index: AQHSKscT92/SVBv2Fki1JZy9c0JmkQ==
Date: Thu, 20 Oct 2016 11:42:45 +0000
Message-ID: <D42E898E.11797%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <F528AC6A77AD624FAA5D1D13F7206380@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42KZGbHdQ3f7Wo4IgzcvJSw27PvPbLH85QlG i6nLH7M4MHtMu3+fzWPnrLvsHkuW/GQKYI7isklJzcksSy3St0vgylg3bR5LwRXpihMnf7M2 MB4W7WLk5JAQMJH4/+I3SxcjF4eQwHpGifWnjjNDOIsZJT42bGXtYuTgYBOwkOj+pw0SFxFY zShxe/NBFpBuYYF8iReP7zKC2CICBRJdbe+YIWw9ic49F9lAbBYBVYlnP/6wgti8AtYSj0/1 gtUzCohJfD+1hgnEZhYQl7j1ZD4TxEUCEkv2nGeGsEUlXj7+B3aDKNDMNffDIMKKElenL4dq 1ZO4MXUKG4RtLXFo/h0oW1ti2cLXzBBrBSVOznzCMoFRZBaSbbOQtM9C0j4LSfssJO0LGFlX MYoWpxYn5aYbGemlFmUmFxfn5+nlpZZsYgTGzsEtvw12ML587niIUYCDUYmH98Eb9ggh1sSy 4srcQ4wSHMxKIrwCqzgihHhTEiurUovy44tKc1KLDzFKc7AoifOarbwfLiSQnliSmp2aWpBa BJNl4uCUamCc9P6328ePcSf2fj8e0XdEZtaLDWYZc6ezMmwOtSu/cEJnXkBju0gTn4x9w6tf nELvF4fIVa+YOPXNkp6N0xcJJiX4JrI3iD/w/vH/UaSGWvSKJddP3MyXK9z0OH7XF7MmV6XE WfP5RecaL3q0ZHdm6bepPLuTbi+7LBIZ9Ge14hcbwd72ovOMSizFGYmGWsxFxYkAEgLqfpkC AAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/BgZ-P4ba03tjjJOa0dhs6QrYhXI>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - A new text proposal
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 11:42:51 -0000

Hi,

Based on comments, I=B9ve modified the text. It now talks about associating
RTP STREAMS with m- lines.

------

10.2.  Associating RTP/RTCP Streams With Correct SDP Media Description

   As described in [RFC3550], RTP/RTCP packets are associated with RTP
   streams.  Each RTP stream is identified by an SSRC value, and each
   RTP/RTCP packet carries an SSRC value that is used to associate the
   packet with the correct RTP stream (an RTCP packet can carry multiple
   SSRC values, and might therefore be associated with multiple RTP
   streams).

   In order to be able to process received RTP/RTCP packets correctly it
   must be possible to associate an RTP stream with the correct "m=3D"
   line, as the "m=3D" line and SDP attributes associated with the "m=3D"
   line contain information needed to process the packets.

   As all RTP streams associated with a BUNDLE group are using the same
   address:port combination for sending and receiving RTP/RTCP packets,
   the local address:port combination cannot be used to associate an RTP
   stream with the correct "m=3D" line.  In addition, multiple RTP streams
   might be associated with the same "m=3D" line.

   Also, as described in [Section 10.1.1], the same payload type value
   might be used by multiple RTP streams, in which case the payload type
   value cannot be used to associate an RTP stream with the correct "m=3D"
   line.

   An offerer and answerer can inform each other which SSRC values they
   will use for an RTP stream by using the SDP 'ssrc' attribute
   [RFC5576].  However, an offerer will not know which SSRC values the
   answerer will use until the offerer has received the answer providing
   that information.  Due to this, before the offerer has received the
   answer, the offerer will not be able to associate an RTP stream with
   the correct "m=3D" line using the SSRC value associated with the RTP
   stream.  In addition, the offerer and answerer may start using new
   SSRC values mid-session, without informing each other using the SDP
   'ssrc' attribute.

   In order for an offerer and answerer to always be able to associate
   an RTP stream with the correct "m=3D" line, the offerer and answerer
   using the BUNDLE extension MUST support the mechanism defined in
   Section 14, where the offerer and answerer insert the identification-
   tag (provided by the remote peer) associated with an "m=3D" line in RTP
   and RTCP packets associated with a BUNDLE group.

   Once an offerer or answerer recieve an RTP/RTCP packet carrying an
   identification-tag and an SSRC value (an RTCP packet might carry
   multiple identification-tags and SSRC values), it creates a mapping
   between the SSRC value and the identification-tag, in order to
   associate the RTP stream with the "m=3D" line associated with the
   identification-tag.  Note that the mapping might change mid-session
   if, for a given SSRC value, a different identification-tag is
   provided in an RTP/RTCP packet.

   If an offerer and answerer is not able to associate an RTP stream
   with an "m=3D" line (using the mechanisms described in this section, or
   using other appropriate mechanism), it SHOULD drop the RTP/RTCP
   packets associated with the RTP stream, once non-stream specific
   processing (e.g., related to congestion control) of the packets have
   occurred.  Note that RTCP packets might be associated with multiple
   RTP streams.

------

Regards,


Christer





From nobody Thu Oct 20 04:43:12 2016
Return-Path: <magnus.westerlund@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 0E2DF1298C6 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 04:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 UHz4dewXrvC8 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 04:43:10 -0700 (PDT)
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 45C6D1298C8 for <mmusic@ietf.org>; Thu, 20 Oct 2016 04:43:10 -0700 (PDT)
X-AuditID: c1b4fb30-f60a598000000cb2-82-5808adccee66
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.183.54]) by  (Symantec Mail Security) with SMTP id 4A.3F.03250.CCDA8085; Thu, 20 Oct 2016 13:43:08 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.3.319.2; Thu, 20 Oct 2016 13:43:07 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, <mmusic@ietf.org>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org> <D42AA198.11408%christer.holmberg@ericsson.com> <A2448DA9-6634-4583-A4B6-040B93371254@csperkins.org> <D42D44E7.11653%christer.holmberg@ericsson.com> <9483F0F1-F651-4471-9AC0-6AA79EA2480D@csperkins.org> <0b0a5e0b-a038-a230-cd18-05d1b759064e@alum.mit.edu>
Message-ID: <c0b01f60-7a68-59e6-fcb5-2a5e7e852974@ericsson.com>
Date: Thu, 20 Oct 2016 13:43:05 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <0b0a5e0b-a038-a230-cd18-05d1b759064e@alum.mit.edu>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrJLMWRmVeSWpSXmKPExsUyM2K7me6ZtRwRBgsu6VhMXf6YxWLFhgOs Dkwef99/YPJYsuQnUwBTFJdNSmpOZllqkb5dAlfGxJur2Qt69SuOrNrD1MB4VrWLkZNDQsBE 4vHp5yxdjFwcQgLrGSVWTNwH5SxnlLhzcTEjSBWbgIXEzR+NbCC2sECGRMvLLrC4iIC1xMsV p6AalrBITF64FCzBK2AvMWP1eqYuRg4OFgFViVOT1UDCogIxEtefPWKDKBGUODnzCQuIzSng IPF74k6wVmagXTPnn4ey5SWat85mBrGFBLQlGpo6WCcw8s9C0j4LScssJC0LGJlXMYoWpxYn 5aYbGemlFmUmFxfn5+nlpZZsYgQG4MEtvw12ML587niIUYCDUYmH98Eb9ggh1sSy4srcQ4wS HMxKIrwCqzgihHhTEiurUovy44tKc1KLDzFKc7AoifOarbwfLiSQnliSmp2aWpBaBJNl4uCU amA0O++Q/+LIze6rH18m3Ehfe67/dn8b6y+9eq7yGdcutivJPLzwQ2GhjY9059WwYzturbW5 sMBU9O/TkKZtZjzFaVfcOCZaH14xNSlz5oPgpKTQhvwHUj1namTUEnZpJW6q8b6/rWeKVO39 XQ+EMj/tnhRyqOpHxNOmMC62ig056qfr288EMykpsRRnJBpqMRcVJwIAUWW5+DwCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/7xIIk7rlNdczdcG06_cNsYHPtM4>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 11:43:12 -0000

Hi,

Yes, there are history here, we also have made decision on what we 
wanted the m= line to mean. Yes, the path we chose it is not the one 
that results in the cleanest configuration for RTP.

I am also try my best to keep in mind that how you implemented your RTP 
stack can significantly impact how you consider these issues.

So comments inline.

Attempt to conclude at the bottom.


Den 2016-10-19 kl. 22:20, skrev Paul Kyzivat:
> On 10/19/16 9:18 AM, Colin Perkins wrote:
>> Getting the layering right is important, I think, to have something
>> thatâ€™s both understandable and extensible:
>>
>>  RTP Layer  : RTP and RTCP packets -> RTP streams
>>  SDP BUNDLE : RTP streams -> SDP â€œm=" lines
>>  JSEP       : SDP â€œm=" lines -> application-level semantics
>>
>> I donâ€™t think this will need a big text change, but it is a semantic
>> change in how the BUNDLE draft describes the mapping.
>
> ISTM this isn't fundamentally about BUNDLE. It is about the relationship
> of SDP and RTP. My impression is that this was never *right*, and the
> introduction of BUNDLE has brought it to a head.

Agreed, the usage of SAP wiht SDP for configuring RAT/VIC MBONE tools 
actually worked on an RTP session level (with an assumption of sending 
one but receiving many streams per RTP session and media type). Then SIP 
O/A came along and introduced a media stream centric definition. Which I 
think is part of where it went in a direction that contributes to 
today's issues.

>
> For the most part SDP rarely mentions SSRCs. (It *can* using a=SSRC, but
> that is a rarely used construct.)
>
> SDP is a container for multiple "Media Descriptions". Syntactically it
> does this by:
>
> - grouping multiple SDP lines into multiple media descriptions
>   delineated by m-lines
> - associating a 3-tuple with each media description based on the
>   c-line and info in the m-line
> - associating two SDPs (offer and answer), pairing the media
>   descriptions in each in order to merge properties. This merges
>   two 3-tuples into a 5-tuple
>
> The code that interprets this stuff then (in the case of RTP) associates
> each media description with (possibly multiple) RTP streams. In non-rtp
> cases the interpretation is different.
>
> Historically (pre-bundle) that code was able to associate network
> packets with media descriptions based on the 5-tuple. This was partially
> done by the OS (sockets) and partially the application.

Yes, part of this tangle is that parameters that in reality are RTP 
session related parameters are tangled up with the media source you 
would like to receive and send.

And from my perspective, the OS (Sockets) selectors for incoming data 
are really associated first of all with the RTP session. Only a possible 
second usage for identifying a particular incoming RTP stream as being 
from a particular end-point and application context.

And the O/A design introduced an artificial limitation for RTP. As the 
3-tupe or 5-tuple are not at all related to how many RTP streams can 
flow between these end-points.

> The introduction of BUNDLE is with the intent using a single 5-tuple for
> multiple media descriptions. That means that the 5-tuple is insufficient
> to associate packets with media descriptions, so some additional
> algorithm is required to do that.
>
> When Christer is talking about an m-line he is generally using that as
> shorthand language for the media description delineated by the m-line.
> With that in mind, his wording "associate received RTP packets wth an m=
> line [media description]" seems right to me.
>
> In the case of RTP, it remains the job of the RTP implementation to
> associate those incoming RTP packets with a media description. *Then* it
> can use the other properties of that media description to help in
> figuring out what RTP stream they are associated with.
>
> That is only for RTP. In the case of non-RTP media that is is the bundle
> some different algorithm is needed to make the association. We have only
> defined a limited case for non-RTP media in a bundle, so the task is
> easier. But we just put that off. In principle more things could be
> bundled. For instance, we *could* have allowed multiple UDP/DTLS/SCTP
> media descriptions in the bundle as long as they had differing
> SCTP-ports. That would bind corresponding packets to one or the other of
> the media descriptions.

Yes, but also in the case for SCTP, one doesn't need to talk about SCTP 
packets, one should talk about the different SCTP association, which is 
what the SCTP ports identify. Yes, on the lowest level it might be easy 
to just abstract it to be packets from the other protocol. But, in most 
cases I think you can easily put another label on the flow(s) of 
packets, uni or bi-directional depending on the protocol. When defining 
an SDP configuration of a transport mechanism one have to consider what 
protocol elements that needs to be configured.


I currently fail to see that the above discussion changes what needs to 
be done. Yes, SDP's description of RTP is not optimally structured, but 
that we can't change. We also have the agreement that one m= should 
describe one Media Source, thus we simply have to describe how this is 
accomplished, despite the fact that one needs to consider both RTP 
session and the set of RTP streams associated with a media source that 
on sends as well as the RTP streams one is willing to receive.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Oct 20 05:12:41 2016
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 55BC8129929 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 05:12:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 7aDiyf4l-C5Z for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 05:12:36 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5CF71295F0 for <mmusic@ietf.org>; Thu, 20 Oct 2016 05:12:36 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id f128so86685858qkb.1 for <mmusic@ietf.org>; Thu, 20 Oct 2016 05:12:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=aXQCAxlH+TgSD+Zt8Z6XOgKxD61F/HkjWq5l0ldC0JE=; b=D/Gfs+UBy9Li5QnLzSJ2xc03gPBvBdx2PdmllMGfHmjBwQZg2hEn2MLSTN1UfIPVlm SES/Zc152qQ5zYRxef0QjbHzDo8qv2ZE5nK6NxmKT5TBRFgqE5xbXIoEm3gD6OshDf63 m1UGRwUBvAPJeJmES9TnVke/hMqIWmyKi2Ompqi2W9/Cx8mkyZYGvNrDlL6qLcKiXoTY WxxjFizigGCP3twxi9ERTwzIISZ75Scra8WlhEg+/amJzp1fcMb3WLili/QYNzkvYDz5 IkJAWRimMZlSKTbCjvJXSfGy0240IMw6CWoSYpqZgsAL7yUOcvwChlGCI/BXQUwo7qYV deUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=aXQCAxlH+TgSD+Zt8Z6XOgKxD61F/HkjWq5l0ldC0JE=; b=in3Pso8uuhSeaNJfHxYl6x9gEONml8Cl29O8LWGv1rKfji045ZylB2k0HECZahfDMy GWPUrjpGnktse28Baqse7lpX75xO7DgIcI7hexwtO+mjLhm0zt9RAS+MIPdJ2OA1NRdH 0BNRz5iZfsWaw1WzYTBEXKzZFnMLE1JzNxxfKoLQ62Zmb4rGlG99tL+GwL5kMzoVbgdh A5xl1HSu3o5BMrl46PQdE9t01jbl2EI/fDRLbwLnvPzFT9Czg6uPmqeQ/fJLmBbmpqzK 5u7BQnR73yeO2dJF09rL0afTxfLXMPY0qJ5aOEp4d25+k2JaXgcw0Wae4fuO/JhIDLRG Y9ZA==
X-Gm-Message-State: AA6/9RmSNP1hcUrlGxHA//o7fOg/dKroDGei6CuKTKqx2yxiRGWyEulDLAuG7lxbmj7KFw==
X-Received: by 10.195.13.107 with SMTP id ex11mr201698wjd.99.1476965555649; Thu, 20 Oct 2016 05:12:35 -0700 (PDT)
Received: from alans-mbp.lan ([37.152.254.14]) by smtp.gmail.com with ESMTPSA id r1sm78389393wjc.43.2016.10.20.05.12.34 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 20 Oct 2016 05:12:34 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_0FBF3104-A0D3-44CA-835E-A1801B0E0E35"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <D42E61A0.11767%christer.holmberg@ericsson.com>
Date: Thu, 20 Oct 2016 13:12:33 +0100
Message-Id: <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/cGo_CeDcHcB3A-nhrDRPEcSY0Eo>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 12:12:40 -0000

--Apple-Mail=_0FBF3104-A0D3-44CA-835E-A1801B0E0E35
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi Christer,

It=92s definitely something that would enhance the usefulness of ICE in =
transport-agnostic protocols such as BFCP where there=92s no guarantee =
one end implements both UDP and TCP transports (for example).

I don=92t see a problem with a change in text to make that second =
requirement of 4.1.1.2 apply only to the offerer (not the answerer) - =
any endpoints implementing this should be fine with this. I would be a =
little more concerned, however, about proxies that may make some wrong =
assumptions in these scenarios.

Regards,
Alan

> On 20 Oct 2016, at 09:51, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Anyone having an opinion on this?
>=20
> It may impact a couple of drafts which are about to be finalised, so =
it would be good to hear what people think.
>=20
> Regards,
>=20
> Christer
>=20
> From: mmusic <mmusic-bounces@ietf.org =
<mailto:mmusic-bounces@ietf.org>> on behalf of Christer Holmberg =
<christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>>
> Date: Monday 17 October 2016 at 12:37
> To: "mmusic@ietf.org <mailto:mmusic@ietf.org>" <mmusic@ietf.org =
<mailto:mmusic@ietf.org>>
> Subject: [MMUSIC] draft-ice-sip-sdp: m- line matching default =
candidate in SDP answer?
>=20
> Hi,
>=20
> The issue in this e-mail has came up during ICE discussions related to =
BFCP and SCTP.
>=20
> Section 4.1.1.2 of draft-ietf-mmusic-ice-sip-sdp-10 says:
>    "The default candidates are added to the SDP as the default
>    destination for media.  For streams based on RTP, this is done by
>    placing the IP address and port of the RTP candidate into the "c=3D"
>    and "m=3D" lines, respectively.=94
> =85and:
>    "The transport addresses that will be the default destination for
>    media when communicating with non-ICE peers MUST also be present as
>    candidates in one or more a=3Dcandidate lines."
>=20
> Assume the offerer sends an offer. The default candidate is TCP-based, =
which will be reflected in the m- line (e.g., TCP/DTLS/SCTP). The offer =
also contains UDP-based candidates.
>=20
> Now, assume the default candidate of the answerer is UDP-based =
(perhaps the answerer doesn=92t even support TCP). However, according to =
the O/A rules, the answerer cannot change the m- line proto in the =
answer (e.g., UDP/DTLS/SCTP). So, if I understand correctly, it means =
that the answerer must reject the m- line =96 even if there are =
UDP-based candidates that the answerer would support.
>=20
> A solution to this would be to NOT mandate the m- line to match the =
default candidate in the answer. So, in the example above, the answerer =
could include (TCP/DTLS/SCTP) in the m- line, but ONLY provide UDP =
candidates.
>=20
> Another solution would to always mandate support of one or more =
specific transports, and specify that the default candidate MUST use =
that transport.
>=20
> Regards,
>=20
> Christer
>=20
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


--Apple-Mail=_0FBF3104-A0D3-44CA-835E-A1801B0E0E35
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi Christer,<div class=3D""><br class=3D""></div><div =
class=3D"">It=92s definitely something that would enhance the usefulness =
of ICE in transport-agnostic protocols such as BFCP where there=92s no =
guarantee one end implements both UDP and TCP transports (for =
example).</div><div class=3D""><br class=3D""></div><div class=3D"">I =
don=92t see a problem with a change in text to make that second =
requirement of 4.1.1.2 apply only to the offerer (not the answerer) - =
any endpoints implementing this should be fine with this. I would be a =
little more concerned, however, about proxies that may make some wrong =
assumptions in these scenarios.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Regards,</div><div =
class=3D"">Alan</div><div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On 20 Oct 2016, at 09:51, =
Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com" =
class=3D"">christer.holmberg@ericsson.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DWindows-1252" class=3D"">

<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; font-size: 14px; font-family: =
Calibri, sans-serif;" class=3D"">
<div class=3D"">Anyone having an opinion on this?</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">It may impact a couple of drafts which are about to be =
finalised, so it would be good to hear what people think.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Regards,</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Christer</div>
<div class=3D""><br class=3D"">
</div>
<span id=3D"OLK_SRC_BODY_SECTION" class=3D"">
<div style=3D"font-family: Calibri; font-size: 11pt; text-align: left; =
border-width: 1pt medium medium; border-style: solid none none; padding: =
3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class=3D"">
<span style=3D"font-weight:bold" class=3D"">From: </span>mmusic &lt;<a =
href=3D"mailto:mmusic-bounces@ietf.org" =
class=3D"">mmusic-bounces@ietf.org</a>&gt; on behalf of Christer =
Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com" =
class=3D"">christer.holmberg@ericsson.com</a>&gt;<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">Date: </span>Monday 17 =
October 2016 at 12:37<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">To: </span>"<a =
href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a>" &lt;<a =
href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a>&gt;<br =
class=3D"">
<span style=3D"font-weight:bold" class=3D"">Subject: </span>[MMUSIC] =
draft-ice-sip-sdp: m- line matching default candidate in SDP answer?<br =
class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D"">
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">Hi,</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">The issue in this e-mail has came up during ICE discussions =
related to BFCP and SCTP.</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">Section 4.1.1.2 of draft-ietf-mmusic-ice-sip-sdp-10 =
says:</font></div>
<div class=3D"">
<pre style=3D"font-size: 14px; font-variant-ligatures: normal; orphans: =
2; widows: 2; word-wrap: break-word; white-space: pre-wrap;" =
class=3D""><font face=3D"Calibri" class=3D"">   "The default candidates =
are added to the SDP as the default
   destination for media.  For streams based on RTP, this is done by
   placing the IP address and port of the RTP candidate into the "c=3D"
   and "m=3D" lines, respectively.=94</font></pre>
<pre style=3D"font-size: 14px; font-variant-ligatures: normal; orphans: =
2; widows: 2; word-wrap: break-word; white-space: pre-wrap;" =
class=3D""><font face=3D"Calibri" class=3D"">=85and:</font></pre>
<pre style=3D"font-size: 14px; font-variant-ligatures: normal; orphans: =
2; widows: 2; word-wrap: break-word; white-space: pre-wrap;" =
class=3D""><pre style=3D"font-variant-ligatures: normal; word-wrap: =
break-word; white-space: pre-wrap;" class=3D""><font face=3D"Calibri" =
class=3D"">   "The transport addresses that will be the default =
destination for
   media when communicating with non-ICE peers MUST also be present as
   candidates in one or more a=3Dcandidate lines."</font></pre></pre>
</div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">Assume the offerer sends an offer. The default c</font><span =
style=3D"font-family: Calibri;" class=3D"">andidate is TCP-based, which =
will be reflected in the m- line (e.g., TCP/DTLS/SCTP). The offer
 also contains UDP-based candidates.</span></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">Now, assume the default candidate of the answerer is =
UDP-based (perhaps the answerer doesn=92t even support TCP). However, =
according to the O/A rules, the answerer cannot change the m- line
 proto in the answer (e.g., UDP/DTLS/SCTP).&nbsp;</font><span =
style=3D"font-family: Calibri;" class=3D"">So, if I understand =
correctly, it means that the answerer must reject the m- line =96 even =
if there are UDP-based candidates that the answerer would =
support.</span></div>
<div style=3D"font-size: 14px;" class=3D""><br class=3D"">
</div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">A solution to this would be to NOT mandate the m- line to =
match the default candidate in the answer. So, in the example above, the =
answerer could include (TCP/DTLS/SCTP) in the m- line,
 but ONLY provide UDP candidates.</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D"">Another solution would to =
always mandate support of one or more specific transports, and specify =
that the default candidate MUST use that transport.</div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">Regards,</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">Christer</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;" =
class=3D"">
<br class=3D"">
</div>
</div>
</div>
</span>
</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=_0FBF3104-A0D3-44CA-835E-A1801B0E0E35--


From nobody Thu Oct 20 05:42:56 2016
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 E44F61294FA for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 05:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 mfDMlTmWMz0h for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 05:42:53 -0700 (PDT)
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 EFB9F129421 for <mmusic@ietf.org>; Thu, 20 Oct 2016 05:42:52 -0700 (PDT)
X-AuditID: c1b4fb25-15fff7000000793b-be-5808bbcaee6a
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.183.42]) by  (Symantec Mail Security) with SMTP id 3E.98.31035.ACBB8085; Thu, 20 Oct 2016 14:42:51 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.03.0319.002; Thu, 20 Oct 2016 14:42:49 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Alan Ford <alan.ford@gmail.com>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
Thread-Index: AQHSKq8ixsJ53smzZ0iYfg1cr+NRB6CxH5OAgAA8sIA=
Date: Thu, 20 Oct 2016 12:42:49 +0000
Message-ID: <D42E97C0.117A6%christer.holmberg@ericsson.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com> <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com>
In-Reply-To: <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_D42E97C0117A6christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrJIsWRmVeSWpSXmKPExsUyM2K7lu7p3RwRBr/ei1msPLeC2WLq8scs DkweO2fdZfdYsuQnUwBTFJdNSmpOZllqkb5dAlfGzzvvmQqWJFac+pTVwHgyuIuRk0NCwETi 4cNjrF2MXBxCAusZJXpWnmaEcBYzSszatx7I4eBgE7CQ6P6nDWKKCChLLJ/FCmIyC6hLXF0c BDJGWCBG4tbKP+wgtohArMTVM+9ZIWwribvNe8DiLAKqEr8+/wOzeQWsJT53L4XatIBRYkPz UbAEp4CtxPbP21hAbEYBMYnvp9YwgdjMAuISt57MZ4K4WUBiyZ7zzBC2qMTLx//A7hEV0JNY cz8MIqwo8fHVPkaI1gSJU09fMEHsFZQ4OfMJywRG0VlIps5CUjYLSRlE3EDi/bn5zBC2tsSy ha+hbH2JjV/OMkLY1hInDzxkR1azgJFjFaNocWpxUm66kbFealFmcnFxfp5eXmrJJkZgBB7c 8lt1B+PlN46HGAU4GJV4eB+8YY8QYk0sK67MPcQowcGsJMKrvYMjQog3JbGyKrUoP76oNCe1 +BCjNAeLkjiv2cr74UIC6YklqdmpqQWpRTBZJg5OqQbG2hbf+wnzea6mmv4pfhbNVnomcTGL xMzjPS8uMKid5XmlZuv14Uyd0pe9cn2a4tM2FHlUl944lDcrvTXQ0ibZPD9GvWjRFOeM3Cn7 Nmn399yeFWFT0zt//wvO6XMdlM5x9zczxwUYr9mU3XRi08L5Gb8YG/a3fHyamMPlVRVVr7rz Yni+aIASS3FGoqEWc1FxIgDoSYu7vAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/QPFV5B2aFWmAYJAF3ljrWxRkoCw>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 12:42:55 -0000

--_000_D42E97C0117A6christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Alan,

>It=92s definitely something that would enhance the usefulness of ICE in tr=
ansport-agnostic protocols such as BFCP where there=92s no guarantee one en=
d implements both UDP and TCP transports (for example).
>
>I don=92t see a problem with a change in text to make that second requirem=
ent of 4.1.1.2 apply only to the offerer (not the answerer) - any endpoints=
 implementing this should be fine with this. I would be a little more conce=
rned, however, about proxies that may make some wrong assumptions in these =
scenarios.

Not sure I understand the proxy question. Even if you DO support the transp=
ort you indicate in the m- line, it still doesn=92t guarantee that you will=
 end up using that transport.

Regards,

Christer

On 20 Oct 2016, at 09:51, Christer Holmberg <christer.holmberg@ericsson.com=
<mailto:christer.holmberg@ericsson.com>> wrote:

Anyone having an opinion on this?

It may impact a couple of drafts which are about to be finalised, so it wou=
ld be good to hear what people think.

Regards,

Christer

From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on b=
ehalf of Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.=
holmberg@ericsson.com>>
Date: Monday 17 October 2016 at 12:37
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>
Subject: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in =
SDP answer?

Hi,

The issue in this e-mail has came up during ICE discussions related to BFCP=
 and SCTP.

Section 4.1.1.2 of draft-ietf-mmusic-ice-sip-sdp-10 says:

   "The default candidates are added to the SDP as the default
   destination for media.  For streams based on RTP, this is done by
   placing the IP address and port of the RTP candidate into the "c=3D"
   and "m=3D" lines, respectively.=94

=85and:

   "The transport addresses that will be the default destination for
   media when communicating with non-ICE peers MUST also be present as
   candidates in one or more a=3Dcandidate lines."

Assume the offerer sends an offer. The default candidate is TCP-based, whic=
h will be reflected in the m- line (e.g., TCP/DTLS/SCTP). The offer also co=
ntains UDP-based candidates.

Now, assume the default candidate of the answerer is UDP-based (perhaps the=
 answerer doesn=92t even support TCP). However, according to the O/A rules,=
 the answerer cannot change the m- line proto in the answer (e.g., UDP/DTLS=
/SCTP). So, if I understand correctly, it means that the answerer must reje=
ct the m- line =96 even if there are UDP-based candidates that the answerer=
 would support.

A solution to this would be to NOT mandate the m- line to match the default=
 candidate in the answer. So, in the example above, the answerer could incl=
ude (TCP/DTLS/SCTP) in the m- line, but ONLY provide UDP candidates.

Another solution would to always mandate support of one or more specific tr=
ansports, and specify that the default candidate MUST use that transport.

Regards,

Christer


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


--_000_D42E97C0117A6christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <BD99A344EE97D04FB426F54F2752304E@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi Alan,</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;" class=3D"">
<div class=3D"">&gt;It=92s definitely something that would enhance the usef=
ulness of ICE in transport-agnostic protocols such as BFCP where there=92s =
no guarantee one end implements both UDP and TCP transports (for example).<=
/div>
<div class=3D"">&gt;</div>
<div class=3D"">&gt;I don=92t see a problem with a change in text to make t=
hat second requirement of 4.1.1.2 apply only to the offerer (not the answer=
er) - any endpoints implementing this should be fine with this. I would be =
a little more concerned, however, about
 proxies that may make some wrong assumptions in these scenarios.</div>
</div>
</div>
</span>
<div><br>
</div>
<div>Not sure I understand the proxy question. Even if you DO support the t=
ransport you indicate in the m- line, it still doesn=92t guarantee that you=
 will end up using that transport.</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;" class=3D"">
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Regards,</div>
</div>
</div>
</span>
<div><br>
</div>
<div>Christer</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;" class=3D"">
<div class=3D""><br class=3D"">
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On 20 Oct 2016, at 09:51, Christer Holmberg &lt;<a href=3D"=
mailto:christer.holmberg@ericsson.com" class=3D"">christer.holmberg@ericsso=
n.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; font-size: 14px; font-family: Calibri, sans-seri=
f;" class=3D"">
<div class=3D"">Anyone having an opinion on this?</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">It may impact a couple of drafts which are about to be fina=
lised, so it would be good to hear what people think.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Regards,</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Christer</div>
<div class=3D""><br class=3D"">
</div>
<span id=3D"OLK_SRC_BODY_SECTION" class=3D"">
<div style=3D"font-family: Calibri; font-size: 11pt; text-align: left; bord=
er-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0i=
n 0in; border-top-color: rgb(181, 196, 223);" class=3D"">
<span style=3D"font-weight:bold" class=3D"">From: </span>mmusic &lt;<a href=
=3D"mailto:mmusic-bounces@ietf.org" class=3D"">mmusic-bounces@ietf.org</a>&=
gt; on behalf of Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@=
ericsson.com" class=3D"">christer.holmberg@ericsson.com</a>&gt;<br class=3D=
"">
<span style=3D"font-weight:bold" class=3D"">Date: </span>Monday 17 October =
2016 at 12:37<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">To: </span>&quot;<a href=3D"mai=
lto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a>&quot; &lt;<a href=3D"ma=
ilto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a>&gt;<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">Subject: </span>[MMUSIC] draft-=
ice-sip-sdp: m- line matching default candidate in SDP answer?<br class=3D"=
">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;" class=3D"">
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
">Hi,</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
"><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
">The issue in this e-mail has came up during ICE discussions related to BF=
CP and SCTP.</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
"><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
">Section 4.1.1.2 of draft-ietf-mmusic-ice-sip-sdp-10 says:</font></div>
<div class=3D"">
<pre style=3D"font-size: 14px; font-variant-ligatures: normal; orphans: 2; =
widows: 2; word-wrap: break-word; white-space: pre-wrap;" class=3D""><font =
face=3D"Calibri" class=3D"">   &quot;The default candidates are added to th=
e SDP as the default
   destination for media.  For streams based on RTP, this is done by
   placing the IP address and port of the RTP candidate into the &quot;c=3D=
&quot;
   and &quot;m=3D&quot; lines, respectively.=94</font></pre>
<pre style=3D"font-size: 14px; font-variant-ligatures: normal; orphans: 2; =
widows: 2; word-wrap: break-word; white-space: pre-wrap;" class=3D""><font =
face=3D"Calibri" class=3D"">=85and:</font></pre>
<pre style=3D"font-size: 14px; font-variant-ligatures: normal; orphans: 2; =
widows: 2; word-wrap: break-word; white-space: pre-wrap;" class=3D""><pre s=
tyle=3D"font-variant-ligatures: normal; word-wrap: break-word; white-space:=
 pre-wrap;" class=3D""><font face=3D"Calibri" class=3D"">   &quot;The trans=
port addresses that will be the default destination for
   media when communicating with non-ICE peers MUST also be present as
   candidates in one or more a=3Dcandidate lines.&quot;</font></pre></pre>
</div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
"><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
">Assume the offerer sends an offer. The default c</font><span style=3D"fon=
t-family: Calibri;" class=3D"">andidate is TCP-based, which will be reflect=
ed in the m- line (e.g., TCP/DTLS/SCTP). The
 offer also contains UDP-based candidates.</span></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
"><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
">Now, assume the default candidate of the answerer is UDP-based (perhaps t=
he answerer doesn=92t even support TCP). However, according to the O/A rule=
s, the answerer cannot change the m- line
 proto in the answer (e.g., UDP/DTLS/SCTP).&nbsp;</font><span style=3D"font=
-family: Calibri;" class=3D"">So, if I understand correctly, it means that =
the answerer must reject the m- line =96 even if there are UDP-based candid=
ates that the answerer would support.</span></div>
<div style=3D"font-size: 14px;" class=3D""><br class=3D"">
</div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
">A solution to this would be to NOT mandate the m- line to match the defau=
lt candidate in the answer. So, in the example above, the answerer could in=
clude (TCP/DTLS/SCTP) in the m- line, but
 ONLY provide UDP candidates.</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
"><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D"">Another solution would to always=
 mandate support of one or more specific transports, and specify that the d=
efault candidate MUST use that transport.</div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
"><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
">Regards,</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
"><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
">Christer</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" class=3D"=
"><br class=3D"">
</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;" class=3D"=
"><br class=3D"">
</div>
</div>
</div>
</span></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"">
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.o=
rg/mailman/listinfo/mmusic</a><br class=3D"">
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</div>
</span>
</body>
</html>

--_000_D42E97C0117A6christerholmbergericssoncom_--


From nobody Thu Oct 20 06:02:26 2016
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 A341C1295DF for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 06:02:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 oFCch38LVbko for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 06:02:16 -0700 (PDT)
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 6E59A1295DA for <mmusic@ietf.org>; Thu, 20 Oct 2016 06:02:16 -0700 (PDT)
X-AuditID: c1b4fb25-5405a9800000793b-46-5808c0565c17
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by  (Symantec Mail Security) with SMTP id D2.BD.31035.650C8085; Thu, 20 Oct 2016 15:02:14 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0319.002; Thu, 20 Oct 2016 15:02:14 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, Bernard Aboba <bernard.aboba@gmail.com>, Colin Perkins <csp@csperkins.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - A new text proposal
Thread-Index: AQHSKscT92/SVBv2Fki1JZy9c0JmkaCxYYAA
Date: Thu, 20 Oct 2016 13:02:13 +0000
Message-ID: <D42E9C94.117BB%christer.holmberg@ericsson.com>
References: <D42E898E.11797%christer.holmberg@ericsson.com>
In-Reply-To: <D42E898E.11797%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <357F466254B99F4F8E17B916905F7E36@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHIsWRmVeSWpSXmKPExsUyM2J7uG7YAY4Ig88dZhYb9v1ntlj+8gSj xdTlj1kcmD2m3b/P5rFz1l12jyVLfjIFMEdx2aSk5mSWpRbp2yVwZXyf85G14IBWxce+++wN jFs0uxg5OSQETCQaH+1l7WLk4hASWM8oMWvDPnYIZzGjxJOfF4AyHBxsAhYS3f+0QeIiAvcZ Jc5vfcEC0i0skC/x4vFdRhBbRKBAoqvtHTOEbSSx7MVZsBoWAVWJuZeWsYPYvALWEs9Xz2UF sYWA7OPzO8BqOAVsJBa93Q3WyyggJvH91BomEJtZQFzi1pP5TBCXCkgs2XOeGcIWlXj5+B/Y baICehJr7odBhJUkfmy4xALRqiXx5cc+NgjbWuJO814oW1FiSvdDqHMEJU7OfMIygVFsFpJt s5C0z0LSPgtJ+ywk7QsYWVcxihanFiflphsZ66UWZSYXF+fn6eWllmxiBMbawS2/VXcwXn7j eIhRgINRiYf3wRv2CCHWxLLiytxDjBIczEoivI/3cEQI8aYkVlalFuXHF5XmpBYfYpTmYFES 5zVbeT9cSCA9sSQ1OzW1ILUIJsvEwSnVwKhxVz9Tbu4Ujf2l4Syr2tsSz7ptOyQb9fIOb9QS 9xSbtfP6eqs0Pfw0bz3gE5zx8f3r4wLaHyIy5/M/M3zNOenkw422hdvMDNs2NreW8750mbj6 +KwpfPsPnJlqb+tvLt4mMq3PnnuapckVDY6H9dMYf4cX6erZ6CzbJd9/Xjil/vVH/7RAcyWW 4oxEQy3mouJEAHyFJxWxAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/r_vVylLkJ8p-p0HxQwaQRSUyxi8>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - A new text proposal
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 13:02:25 -0000

U2FtZSBpbiBHaXRIdWI6DQoNCmh0dHBzOi8vZ2l0aHViLmNvbS9jZGg0dS9kcmFmdC1zZHAtYnVu
ZGxlL3B1bGwvMTMNCg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQpPbiAyMC8xMC8xNiAxNDo0
MiwgIm1tdXNpYyBvbiBiZWhhbGYgb2YgQ2hyaXN0ZXIgSG9sbWJlcmciDQo8bW11c2ljLWJvdW5j
ZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4N
Cndyb3RlOg0KDQo+DQo+SGksDQo+DQo+QmFzZWQgb24gY29tbWVudHMsIEmp9nZlIG1vZGlmaWVk
IHRoZSB0ZXh0LiBJdCBub3cgdGFsa3MgYWJvdXQgYXNzb2NpYXRpbmcNCj5SVFAgU1RSRUFNUyB3
aXRoIG0tIGxpbmVzLg0KPg0KPi0tLS0tLQ0KPg0KPjEwLjIuICBBc3NvY2lhdGluZyBSVFAvUlRD
UCBTdHJlYW1zIFdpdGggQ29ycmVjdCBTRFAgTWVkaWEgRGVzY3JpcHRpb24NCj4NCj4gICBBcyBk
ZXNjcmliZWQgaW4gW1JGQzM1NTBdLCBSVFAvUlRDUCBwYWNrZXRzIGFyZSBhc3NvY2lhdGVkIHdp
dGggUlRQDQo+ICAgc3RyZWFtcy4gIEVhY2ggUlRQIHN0cmVhbSBpcyBpZGVudGlmaWVkIGJ5IGFu
IFNTUkMgdmFsdWUsIGFuZCBlYWNoDQo+ICAgUlRQL1JUQ1AgcGFja2V0IGNhcnJpZXMgYW4gU1NS
QyB2YWx1ZSB0aGF0IGlzIHVzZWQgdG8gYXNzb2NpYXRlIHRoZQ0KPiAgIHBhY2tldCB3aXRoIHRo
ZSBjb3JyZWN0IFJUUCBzdHJlYW0gKGFuIFJUQ1AgcGFja2V0IGNhbiBjYXJyeSBtdWx0aXBsZQ0K
PiAgIFNTUkMgdmFsdWVzLCBhbmQgbWlnaHQgdGhlcmVmb3JlIGJlIGFzc29jaWF0ZWQgd2l0aCBt
dWx0aXBsZSBSVFANCj4gICBzdHJlYW1zKS4NCj4NCj4gICBJbiBvcmRlciB0byBiZSBhYmxlIHRv
IHByb2Nlc3MgcmVjZWl2ZWQgUlRQL1JUQ1AgcGFja2V0cyBjb3JyZWN0bHkgaXQNCj4gICBtdXN0
IGJlIHBvc3NpYmxlIHRvIGFzc29jaWF0ZSBhbiBSVFAgc3RyZWFtIHdpdGggdGhlIGNvcnJlY3Qg
Im09Ig0KPiAgIGxpbmUsIGFzIHRoZSAibT0iIGxpbmUgYW5kIFNEUCBhdHRyaWJ1dGVzIGFzc29j
aWF0ZWQgd2l0aCB0aGUgIm09Ig0KPiAgIGxpbmUgY29udGFpbiBpbmZvcm1hdGlvbiBuZWVkZWQg
dG8gcHJvY2VzcyB0aGUgcGFja2V0cy4NCj4NCj4gICBBcyBhbGwgUlRQIHN0cmVhbXMgYXNzb2Np
YXRlZCB3aXRoIGEgQlVORExFIGdyb3VwIGFyZSB1c2luZyB0aGUgc2FtZQ0KPiAgIGFkZHJlc3M6
cG9ydCBjb21iaW5hdGlvbiBmb3Igc2VuZGluZyBhbmQgcmVjZWl2aW5nIFJUUC9SVENQIHBhY2tl
dHMsDQo+ICAgdGhlIGxvY2FsIGFkZHJlc3M6cG9ydCBjb21iaW5hdGlvbiBjYW5ub3QgYmUgdXNl
ZCB0byBhc3NvY2lhdGUgYW4gUlRQDQo+ICAgc3RyZWFtIHdpdGggdGhlIGNvcnJlY3QgIm09IiBs
aW5lLiAgSW4gYWRkaXRpb24sIG11bHRpcGxlIFJUUCBzdHJlYW1zDQo+ICAgbWlnaHQgYmUgYXNz
b2NpYXRlZCB3aXRoIHRoZSBzYW1lICJtPSIgbGluZS4NCj4NCj4gICBBbHNvLCBhcyBkZXNjcmli
ZWQgaW4gW1NlY3Rpb24gMTAuMS4xXSwgdGhlIHNhbWUgcGF5bG9hZCB0eXBlIHZhbHVlDQo+ICAg
bWlnaHQgYmUgdXNlZCBieSBtdWx0aXBsZSBSVFAgc3RyZWFtcywgaW4gd2hpY2ggY2FzZSB0aGUg
cGF5bG9hZCB0eXBlDQo+ICAgdmFsdWUgY2Fubm90IGJlIHVzZWQgdG8gYXNzb2NpYXRlIGFuIFJU
UCBzdHJlYW0gd2l0aCB0aGUgY29ycmVjdCAibT0iDQo+ICAgbGluZS4NCj4NCj4gICBBbiBvZmZl
cmVyIGFuZCBhbnN3ZXJlciBjYW4gaW5mb3JtIGVhY2ggb3RoZXIgd2hpY2ggU1NSQyB2YWx1ZXMg
dGhleQ0KPiAgIHdpbGwgdXNlIGZvciBhbiBSVFAgc3RyZWFtIGJ5IHVzaW5nIHRoZSBTRFAgJ3Nz
cmMnIGF0dHJpYnV0ZQ0KPiAgIFtSRkM1NTc2XS4gIEhvd2V2ZXIsIGFuIG9mZmVyZXIgd2lsbCBu
b3Qga25vdyB3aGljaCBTU1JDIHZhbHVlcyB0aGUNCj4gICBhbnN3ZXJlciB3aWxsIHVzZSB1bnRp
bCB0aGUgb2ZmZXJlciBoYXMgcmVjZWl2ZWQgdGhlIGFuc3dlciBwcm92aWRpbmcNCj4gICB0aGF0
IGluZm9ybWF0aW9uLiAgRHVlIHRvIHRoaXMsIGJlZm9yZSB0aGUgb2ZmZXJlciBoYXMgcmVjZWl2
ZWQgdGhlDQo+ICAgYW5zd2VyLCB0aGUgb2ZmZXJlciB3aWxsIG5vdCBiZSBhYmxlIHRvIGFzc29j
aWF0ZSBhbiBSVFAgc3RyZWFtIHdpdGgNCj4gICB0aGUgY29ycmVjdCAibT0iIGxpbmUgdXNpbmcg
dGhlIFNTUkMgdmFsdWUgYXNzb2NpYXRlZCB3aXRoIHRoZSBSVFANCj4gICBzdHJlYW0uICBJbiBh
ZGRpdGlvbiwgdGhlIG9mZmVyZXIgYW5kIGFuc3dlcmVyIG1heSBzdGFydCB1c2luZyBuZXcNCj4g
ICBTU1JDIHZhbHVlcyBtaWQtc2Vzc2lvbiwgd2l0aG91dCBpbmZvcm1pbmcgZWFjaCBvdGhlciB1
c2luZyB0aGUgU0RQDQo+ICAgJ3NzcmMnIGF0dHJpYnV0ZS4NCj4NCj4gICBJbiBvcmRlciBmb3Ig
YW4gb2ZmZXJlciBhbmQgYW5zd2VyZXIgdG8gYWx3YXlzIGJlIGFibGUgdG8gYXNzb2NpYXRlDQo+
ICAgYW4gUlRQIHN0cmVhbSB3aXRoIHRoZSBjb3JyZWN0ICJtPSIgbGluZSwgdGhlIG9mZmVyZXIg
YW5kIGFuc3dlcmVyDQo+ICAgdXNpbmcgdGhlIEJVTkRMRSBleHRlbnNpb24gTVVTVCBzdXBwb3J0
IHRoZSBtZWNoYW5pc20gZGVmaW5lZCBpbg0KPiAgIFNlY3Rpb24gMTQsIHdoZXJlIHRoZSBvZmZl
cmVyIGFuZCBhbnN3ZXJlciBpbnNlcnQgdGhlIGlkZW50aWZpY2F0aW9uLQ0KPiAgIHRhZyAocHJv
dmlkZWQgYnkgdGhlIHJlbW90ZSBwZWVyKSBhc3NvY2lhdGVkIHdpdGggYW4gIm09IiBsaW5lIGlu
IFJUUA0KPiAgIGFuZCBSVENQIHBhY2tldHMgYXNzb2NpYXRlZCB3aXRoIGEgQlVORExFIGdyb3Vw
Lg0KPg0KPiAgIE9uY2UgYW4gb2ZmZXJlciBvciBhbnN3ZXJlciByZWNpZXZlIGFuIFJUUC9SVENQ
IHBhY2tldCBjYXJyeWluZyBhbg0KPiAgIGlkZW50aWZpY2F0aW9uLXRhZyBhbmQgYW4gU1NSQyB2
YWx1ZSAoYW4gUlRDUCBwYWNrZXQgbWlnaHQgY2FycnkNCj4gICBtdWx0aXBsZSBpZGVudGlmaWNh
dGlvbi10YWdzIGFuZCBTU1JDIHZhbHVlcyksIGl0IGNyZWF0ZXMgYSBtYXBwaW5nDQo+ICAgYmV0
d2VlbiB0aGUgU1NSQyB2YWx1ZSBhbmQgdGhlIGlkZW50aWZpY2F0aW9uLXRhZywgaW4gb3JkZXIg
dG8NCj4gICBhc3NvY2lhdGUgdGhlIFJUUCBzdHJlYW0gd2l0aCB0aGUgIm09IiBsaW5lIGFzc29j
aWF0ZWQgd2l0aCB0aGUNCj4gICBpZGVudGlmaWNhdGlvbi10YWcuICBOb3RlIHRoYXQgdGhlIG1h
cHBpbmcgbWlnaHQgY2hhbmdlIG1pZC1zZXNzaW9uDQo+ICAgaWYsIGZvciBhIGdpdmVuIFNTUkMg
dmFsdWUsIGEgZGlmZmVyZW50IGlkZW50aWZpY2F0aW9uLXRhZyBpcw0KPiAgIHByb3ZpZGVkIGlu
IGFuIFJUUC9SVENQIHBhY2tldC4NCj4NCj4gICBJZiBhbiBvZmZlcmVyIGFuZCBhbnN3ZXJlciBp
cyBub3QgYWJsZSB0byBhc3NvY2lhdGUgYW4gUlRQIHN0cmVhbQ0KPiAgIHdpdGggYW4gIm09IiBs
aW5lICh1c2luZyB0aGUgbWVjaGFuaXNtcyBkZXNjcmliZWQgaW4gdGhpcyBzZWN0aW9uLCBvcg0K
PiAgIHVzaW5nIG90aGVyIGFwcHJvcHJpYXRlIG1lY2hhbmlzbSksIGl0IFNIT1VMRCBkcm9wIHRo
ZSBSVFAvUlRDUA0KPiAgIHBhY2tldHMgYXNzb2NpYXRlZCB3aXRoIHRoZSBSVFAgc3RyZWFtLCBv
bmNlIG5vbi1zdHJlYW0gc3BlY2lmaWMNCj4gICBwcm9jZXNzaW5nIChlLmcuLCByZWxhdGVkIHRv
IGNvbmdlc3Rpb24gY29udHJvbCkgb2YgdGhlIHBhY2tldHMgaGF2ZQ0KPiAgIG9jY3VycmVkLiAg
Tm90ZSB0aGF0IFJUQ1AgcGFja2V0cyBtaWdodCBiZSBhc3NvY2lhdGVkIHdpdGggbXVsdGlwbGUN
Cj4gICBSVFAgc3RyZWFtcy4NCj4NCj4tLS0tLS0NCj4NCj5SZWdhcmRzLA0KPg0KPg0KPkNocmlz
dGVyDQo+DQo+DQo+DQo+DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj5tbXVzaWMgbWFpbGluZyBsaXN0DQo+bW11c2ljQGlldGYub3JnDQo+aHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMNCg0K


From nobody Thu Oct 20 09:40:14 2016
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 5FA8112964F for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 09:40:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZZP0Bpehqmoa for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 09:40:12 -0700 (PDT)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (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 DFDC6129975 for <mmusic@ietf.org>; Thu, 20 Oct 2016 09:40:07 -0700 (PDT)
Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-06v.sys.comcast.net with SMTP id xGMsbyLQW2NhqxGNzblcZq; Thu, 20 Oct 2016 16:40:07 +0000
Received: from [192.168.1.110] ([73.186.127.100]) by resomta-ch2-20v.sys.comcast.net with SMTP id xGNybqUytIwOJxGNybNua4; Thu, 20 Oct 2016 16:40:07 +0000
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, mmusic@ietf.org
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org> <D42AA198.11408%christer.holmberg@ericsson.com> <A2448DA9-6634-4583-A4B6-040B93371254@csperkins.org> <D42D44E7.11653%christer.holmberg@ericsson.com> <9483F0F1-F651-4471-9AC0-6AA79EA2480D@csperkins.org> <0b0a5e0b-a038-a230-cd18-05d1b759064e@alum.mit.edu> <c0b01f60-7a68-59e6-fcb5-2a5e7e852974@ericsson.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <823ebe40-711f-9eac-35dd-d0c332a68166@alum.mit.edu>
Date: Thu, 20 Oct 2016 12:40:06 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <c0b01f60-7a68-59e6-fcb5-2a5e7e852974@ericsson.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfL8KNSwYONZqsXRkwllu/Y5toHM/cJsevC++jhaz2WiIXgLi0w23Rp4Qtdlz0phx0GU9T3RQDeQX0CPRZ+NQx75UbJyaYsEgR7ckrpwPwIekuBYPL1eS MM9JpLOfG45eg+unJWh2ITmtOWjRYJOBecgXRzcnh/7MnCWlpqp+kSJNLpwZ9t5x6xIsmiYcE1HaCdjwazOckjTIExbYk4xXJY0e81TbbR4LHHDb/wRNlv0g
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/hS6cL1NXfKyyiTaeMWQrOxKDAFI>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 16:40:13 -0000

On 10/20/16 7:43 AM, Magnus Westerlund wrote:

> I currently fail to see that the above discussion changes what needs to
> be done. Yes, SDP's description of RTP is not optimally structured, but
> that we can't change. We also have the agreement that one m= should
> describe one Media Source, thus we simply have to describe how this is
> accomplished, despite the fact that one needs to consider both RTP
> session and the set of RTP streams associated with a media source that
> on sends as well as the RTP streams one is willing to receive.

IMO the issue is to sort out different levels of abstraction and layering.

SDP media descriptions are not fundamentally about RTP streams, they are 
about something more general. A whole variety of different sorts of 
connections/associations can be described using media descriptions. Some 
describe a single stream, some describe multiple streams. When they 
describe multiple streams, they have differing nomenclature for talking 
about and denoting those streams. SSRC is meaningful only for RTP. So 
SSRC, or RTP stream, are not terms that ought to be fundamentally 
involved in defining the meaning/function of SDP or BUNDLE. (OTOH, they 
certainly can be considered as part of a discussion of specializing the 
media description for RTP-based media descriptions.)

It might be helpful to conceptualize this in terms of superclasses and 
subclasses. MediaDescription is a base class. A Bundle is a collection 
of MediaDescriptions, but not all MediaDescriptions are bundleable - 
there are some constraints that must be satisfied.

The key feature of a bundle is that all the contained MediaDescriptions 
must share a 5-tuple. The protocol part of the 5-tuple is itself a bit 
tricky, in that we don't require them to have identical m-line <proto> 
fields. Instead, we only require them to share some lower level part of 
the stack of protocols in each of the bundled m-lines. In particular 
DTLS over UDP or DTLS over TCP. (And this is further complicated by ICE, 
but that is a separate discussion.)

The next most significant constraint is that all the data received via 
the 5-tuple must be able to be disambiguated by the receiver regarding 
which MediaDescription(s) it applies to. My attempt to describe that as 
classifying *packets* turns out to be an over-simplification.

The actual classification probably needs to be layered. If the common 
protocol to all the bundled MediaDescriptions is packet-oriented, then 
that is where classification can start. Consider a bundle including RTP, 
RTCP, and SCTP: the first level of classification will be to classify 
the packet as one of those. If there is a single SCTP MediaDescription 
in the bundle then that will be enough to associate SCTP packets with 
that one. If there are multiple RTP MediaDescriptions then RTP and RTCP 
packets need further analysis. The RTCP packets are complicated, as has 
been discussed previously. I still have the sense that RTP packets can 
be classified to a single MediaDescription, but my understanding is 
limited so I am prepared to be wrong about that.

The bottom line is that much of this isn't part of the general bundle 
mechanism. It is specific to the specialization of bundle to RTP. That 
does need to be written down *somewhere*. It could be part of the bundle 
draft, as a subsection specific to RTP. Or it could be in some other 
document.

	Thanks,
	Paul


From nobody Thu Oct 20 10:07:55 2016
Return-Path: <bernard.aboba@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C61A21296FB for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 10:07:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 Vbxgv_j0R7cK for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 10:07:53 -0700 (PDT)
Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::231]) (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 5472F129694 for <mmusic@ietf.org>; Thu, 20 Oct 2016 10:07:53 -0700 (PDT)
Received: by mail-vk0-x231.google.com with SMTP id 83so81218300vkd.0 for <mmusic@ietf.org>; Thu, 20 Oct 2016 10:07:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IonaXBfwqRO33E/NpA4U6vcr6y0woGkiVlhJEa7V5Bw=; b=Itx6i7dDId4ta+mf0arp+pxBDsXojheNEtLyEYm7X4LjQDCwKsP2FNqiZB3H5FLtZj wDUyO94CAEocHqtaULibEhe7guYysBnQLfwpf1iQxTd1dGO3xX7Zv/TwmpJx1vR+FlQw 4KId/Covbg+qwS/J79ghkQwv+sDPcrKIvoc7kkcOZ5870oHYWUWCczvRydKSwTS64Pg6 lQgPOSEqkB8sgHJq5FhGwC4wjjHrPVD78eVXnuY7J+tqBPrW3Ke/T7d6PTmEjxbBgjDi sgulvVXBqYD2ywLDuRRQXcYCKIu2uAjknm9sVOONQfLDLodoLPB0cKcS+7ShLchFjfkX 8s8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IonaXBfwqRO33E/NpA4U6vcr6y0woGkiVlhJEa7V5Bw=; b=CeGortMDqwa6ZCWRrkUIWJRVPD7ne0hYCT2hDHjSbTs/Z9K4huTw+oV3jVIUSb/9Tz yhXNivVgK9NSSxJPFOUCR5XU2ge7HItA9phfGcwLzx425qfxyuTdr+HWZcmbsRHBO4JV 8g29to+xCKE4Ng1RbU+Gh7FkuI+Jfo0KC96JWXfsdFoNwghXJM3dNQoPO2tIwNSKPfMD qC42TKgWrDT9jxGaclt1zBiDHfQgNYhqzal+gkIiyjGvtzZji2tPBRdqxVGZGKbavBdz WtsG8v1mFU6/mJWpMypsqw/ibmKEAuDaE8JNEMl9Zx/KA5XhgcyypZMsLSSip/p8DnC9 FVTw==
X-Gm-Message-State: AA6/9Rkz4dKcINb0Xq3UzNyq6JzXbWPy4fjakLr362rLPpTaLswpB6DRSVDPUYL8r9P0JN10rQKgbJCB64yhnw==
X-Received: by 10.31.200.71 with SMTP id y68mr2579219vkf.126.1476983272233; Thu, 20 Oct 2016 10:07:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.7.101 with HTTP; Thu, 20 Oct 2016 10:07:51 -0700 (PDT)
Received: by 10.176.7.101 with HTTP; Thu, 20 Oct 2016 10:07:51 -0700 (PDT)
In-Reply-To: <CAOW+2dtQXwZk2OeiqJ2QCVP9uzmEPmQ0J=RPs80qTjFzGPfDxw@mail.gmail.com>
References: <CAOW+2duXaBXSq1fwedXj=+rg0s3463GZDqH3Nrg2ss_v8X93dA@mail.gmail.com> <CAOW+2duCa1r0PfObqGPnUDRniG8Gxe3zK=xQwrFhrrYi0wC51A@mail.gmail.com> <CAOW+2ds3oA7_TjCRXJYeZADbuqBqNVtcKBBU5kVVY7H75at47g@mail.gmail.com> <CAOW+2dsxFAj8DUhcM=HHu3reYUsn9A25qGONmBDovc1-FX_RqA@mail.gmail.com> <CAOW+2dtQXwZk2OeiqJ2QCVP9uzmEPmQ0J=RPs80qTjFzGPfDxw@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Thu, 20 Oct 2016 12:07:51 -0500
Message-ID: <CAOW+2dshLX7zgszBgk=pS-w1CVL9WoHy6A43gFzp-XBfn_RP8A@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a114dc658481775053f4ef740
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Dl_QRq-jMg_3t-OCTXKKbOVCK2s>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, mmusic WG <mmusic@ietf.org>, Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] USIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - A new text proposal
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 17:07:55 -0000

--001a114dc658481775053f4ef740
Content-Type: text/plain; charset=UTF-8

I think your proposed text is missing some PT-matching aspects.  Basically,
JSEP matches the MID, then SSRC, then PT.  However, if there are non-unique
PTs, both JSEP as well as ORTC end up routing to one of the RtpReceivers
(though they currently disagree as to which one) rather than dropping the
packet.

   If an offerer and answerer is not able to associate an RTP stream
   with an "m=" line (using the mechanisms described in this section, or
   using other appropriate mechanism), it SHOULD drop the RTP/RTCP
   packets associated with the RTP stream, once non-stream specific
   processing (e.g., related to congestion control) of the packets have
   occurred.  Note that RTCP packets might be associated with multiple
   RTP streams.

--001a114dc658481775053f4ef740
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">I think your proposed text is missing some PT-matching aspec=
ts.=C2=A0 Basically, JSEP matches the MID, then SSRC, then PT.=C2=A0 Howeve=
r, if there are non-unique PTs, both JSEP as well as ORTC end up routing to=
 one of the RtpReceivers (though they currently disagree as to which one) r=
ather than dropping the packet.</p>
<p dir=3D"ltr">=C2=A0=C2=A0 If an offerer and answerer is not able to assoc=
iate an RTP stream<br>
=C2=A0 =C2=A0with an &quot;m=3D&quot; line (using the mechanisms described =
in this section, or<br>
=C2=A0 =C2=A0using other appropriate mechanism), it SHOULD drop the RTP/RTC=
P<br>
=C2=A0 =C2=A0packets associated with the RTP stream, once non-stream specif=
ic<br>
=C2=A0 =C2=A0processing (e.g., related to congestion control) of the packet=
s have<br>
=C2=A0 =C2=A0occurred.=C2=A0 Note that RTCP packets might be associated wit=
h multiple<br>
=C2=A0 =C2=A0RTP streams.</p>

--001a114dc658481775053f4ef740--


From nobody Thu Oct 20 11:09:00 2016
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 A89F212969C for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 11:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 Y4LLXsFyS57Q for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 11:08:57 -0700 (PDT)
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 D8B17129670 for <mmusic@ietf.org>; Thu, 20 Oct 2016 11:08:56 -0700 (PDT)
X-AuditID: c1b4fb3a-aa3ff7000000099a-6b-580908353320
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by  (Symantec Mail Security) with SMTP id 2C.38.02458.53809085; Thu, 20 Oct 2016 20:08:55 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0319.002; Thu, 20 Oct 2016 20:08:53 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Thread-Topic: USIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - A new text proposal
Thread-Index: AQHSKvR+jgXwi9IAI0elxpJAspWLmqCxosjg
Date: Thu, 20 Oct 2016 18:08:52 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BDC0A37@ESESSMB209.ericsson.se>
References: <CAOW+2duXaBXSq1fwedXj=+rg0s3463GZDqH3Nrg2ss_v8X93dA@mail.gmail.com> <CAOW+2duCa1r0PfObqGPnUDRniG8Gxe3zK=xQwrFhrrYi0wC51A@mail.gmail.com> <CAOW+2ds3oA7_TjCRXJYeZADbuqBqNVtcKBBU5kVVY7H75at47g@mail.gmail.com> <CAOW+2dsxFAj8DUhcM=HHu3reYUsn9A25qGONmBDovc1-FX_RqA@mail.gmail.com> <CAOW+2dtQXwZk2OeiqJ2QCVP9uzmEPmQ0J=RPs80qTjFzGPfDxw@mail.gmail.com> <CAOW+2dshLX7zgszBgk=pS-w1CVL9WoHy6A43gFzp-XBfn_RP8A@mail.gmail.com>
In-Reply-To: <CAOW+2dshLX7zgszBgk=pS-w1CVL9WoHy6A43gFzp-XBfn_RP8A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BDC0A37ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHIsWRmVeSWpSXmKPExsUyM2K7tK45B2eEwc3N3BYb9v1ntlj+8gSj xdTlj1kcmD2m3b/P5rFz1l12jyVLfjIFMEdx2aSk5mSWpRbp2yVwZTT/+8Re0KVdcWrZdPYG xheaXYycHBICJhIrvxxn62Lk4hASWM8o8b//KSOEs5hR4s+7O6xdjBwcbAIWEt3/tEEaRAS0 Jfq+7WMCsZkFqiSuLm1jBLGFBXIkTj1cxwRRkyuxeekhNgjbSOL0+/8sIDaLgKrEwmVz2UFs XgFfif9PT7NA7NrMLHH7ylmwZk6BQIkHlxaDFTEKiEl8P7UGapm4xK0n85kgrhaQWLLnPDOE LSrx8vE/VghbSWLt4e0sEPX5Ej0zN0AtE5Q4OfMJywRGkVlIRs1CUjYLSdksoJeZBTQl1u/S hyhRlJjS/ZAdwtaQaJ0zlx1ZfAEj+ypG0eLU4uLcdCMjvdSizOTi4vw8vbzUkk2MwFg7uOW3 1Q7Gg88dDzEKcDAq8fA+eMMeIcSaWFZcmXuIUYKDWUmEN5uZM0KINyWxsiq1KD++qDQntfgQ ozQHi5I4r9nK++FCAumJJanZqakFqUUwWSYOTqkGRm/+2d8Svaf8nZ9mUWZmr7uqfsPTnpk1 2lWrtt3M6D2unyrEf/dJWKz1rgMGXjO7DBofTF8WXb88KH/+HIEZjl/P/NT2eZ/YI5WoYFys WZZ1WTH4tzx/99nAj3uUraZycMl63lq2wLXqnqSyV6rbzXNTjxV9k171r6v7Vt6rT9XzCy94 fJxhq8RSnJFoqMVcVJwIACftmhGxAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/cri832yIhXrhf7HLPJspc2ntcrs>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, mmusic WG <mmusic@ietf.org>, Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] USIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - A new text proposal
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 18:08:59 -0000

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

DQoNCj5JIHRoaW5rIHlvdXIgcHJvcG9zZWQgdGV4dCBpcyBtaXNzaW5nIHNvbWUgUFQtbWF0Y2hp
bmcgYXNwZWN0cy4gQmFzaWNhbGx5LCBKU0VQIG1hdGNoZXMgdGhlIE1JRCwgdGhlbiBTU1JDLCB0
aGVuIFBULg0KDQpJIGNhbiBzYXkg4oCc4oCmb3IgdXNpbmcgb3RoZXIgYXBwcm9wcmlhdGUgbWVj
aGFuaXNtcywgZS5nLCBiYXNlZCBvbiB0aGUgcGF5bG9hZCB0eXBlIHZhbHVlIGlmIGl0IGlzIHVu
aXF1ZSB0byBhIHNpbmdsZSDigJxtPeKAnSBsaW5lKeKAnQ0KDQo+IEhvd2V2ZXIsIGlmIHRoZXJl
IGFyZSBub24tdW5pcXVlIFBUcywgYm90aCBKU0VQIGFzIHdlbGwgYXMgT1JUQyBlbmQgdXAgcm91
dGluZyB0byBvbmUgb2YgdGhlDQo+IFJ0cFJlY2VpdmVycyAodGhvdWdoIHRoZXkgY3VycmVudGx5
IGRpc2FncmVlIGFzIHRvIHdoaWNoIG9uZSkgcmF0aGVyIHRoYW4gZHJvcHBpbmcgdGhlIHBhY2tl
dC4NCg0KSSBjYW4gc2F5IOKAnOKApk1VU1QgZWl0aGVyIGRyb3AgdGhlIFJUUC9SVENQIHBhY2tl
dHMgYXNzb2NpYXRlZCB3aXRoIHRoZSBSVFAgc3RyZWFtLCBvciBwcm9jZXNzIHRoZW0gaW4gc29t
ZSBhcHBsaWNhdGlvbiBzcGVjaWZpYyBtYW5uZXIsIG9uZSBub24tc3RyZWFt4oCm4oCdDQoNClJl
Z2FyZHMsDQoNCkNocmlzdGVyDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29I
eXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4
dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9s
bG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1k
ZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBjbTsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJ
e21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNl
cmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5
cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsN
Cgljb2xvcjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4
cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCW1zby1mYXJl
YXN0LWxhbmd1YWdlOkVOLVVTO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQg
NzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30NCmRpdi5Xb3Jk
U2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBt
c28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYi
IC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBl
bGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0K
PC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0i
RU4tR0IiIGxpbms9IiMwNTYzQzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRT
ZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFG
NDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHA+Jmd0O0kgdGhpbmsgeW91ciBwcm9wb3NlZCB0ZXh0IGlzIG1pc3Npbmcgc29tZSBQ
VC1tYXRjaGluZyBhc3BlY3RzLiZuYnNwO0Jhc2ljYWxseSwgSlNFUCBtYXRjaGVzIHRoZSBNSUQs
IHRoZW4gU1NSQywgdGhlbiBQVC48bzpwPjwvbzpwPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+
SSBjYW4gc2F5IOKAnOKApm9yIHVzaW5nIG90aGVyIGFwcHJvcHJpYXRlIG1lY2hhbmlzbXMsIGUu
ZywgYmFzZWQgb24gdGhlIHBheWxvYWQgdHlwZSB2YWx1ZSBpZiBpdCBpcyB1bmlxdWUgdG8gYSBz
aW5nbGUg4oCcbT3igJ0gbGluZSnigJ08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD4mZ3Q7Jm5i
c3A7SG93ZXZlciwgaWYgdGhlcmUgYXJlIG5vbi11bmlxdWUgUFRzLCBib3RoIEpTRVAgYXMgd2Vs
bCBhcyBPUlRDIGVuZCB1cCByb3V0aW5nIHRvIG9uZSBvZiB0aGU8YnI+DQomZ3Q7IFJ0cFJlY2Vp
dmVycyAodGhvdWdoIHRoZXkgY3VycmVudGx5IGRpc2FncmVlIGFzIHRvIHdoaWNoIG9uZSkgcmF0
aGVyIHRoYW4gZHJvcHBpbmcgdGhlIHBhY2tldC48bzpwPjwvbzpwPjwvcD4NCjxwPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZiI+SSBjYW4gc2F5IOKAnOKApk1VU1QgZWl0aGVyIGRyb3AgdGhlIFJUUC9SVENQIHBh
Y2tldHMgYXNzb2NpYXRlZCB3aXRoIHRoZSBSVFAgc3RyZWFtLCBvciBwcm9jZXNzIHRoZW0gaW4g
c29tZSBhcHBsaWNhdGlvbiBzcGVjaWZpYyBtYW5uZXIsIG9uZSBub24tc3RyZWFt4oCm4oCdPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5SZWdhcmRzLDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Q2hyaXN0ZXI8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_7594FB04B1934943A5C02806D1A2204B4BDC0A37ESESSMB209erics_--


From nobody Thu Oct 20 11:41:37 2016
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 D1817129584 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 11:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 jv3FzK6VA25g for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 11:41:34 -0700 (PDT)
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 B26761296DC for <mmusic@ietf.org>; Thu, 20 Oct 2016 11:41:21 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-cc-58090fcfc083
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by  (Symantec Mail Security) with SMTP id 77.E5.02551.FCF09085; Thu, 20 Oct 2016 20:41:20 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0319.002; Thu, 20 Oct 2016 20:41:18 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
Thread-Index: AQHSJHSivk5Ucbs2BE2kFscuEARQNKCmW5CAgAAxTzCAAOkBgIAE15EAgABieACAAut/gIAAOXAA///XUACAAHXagIABAcuAgABS/ACAAELS4A==
Date: Thu, 20 Oct 2016 18:41:16 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BDC0B43@ESESSMB209.ericsson.se>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org> <D42AA198.11408%christer.holmberg@ericsson.com> <A2448DA9-6634-4583-A4B6-040B93371254@csperkins.org> <D42D44E7.11653%christer.holmberg@ericsson.com> <9483F0F1-F651-4471-9AC0-6AA79EA2480D@csperkins.org> <0b0a5e0b-a038-a230-cd18-05d1b759064e@alum.mit.edu> <c0b01f60-7a68-59e6-fcb5-2a5e7e852974@ericsson.com> <823ebe40-711f-9eac-35dd-d0c332a68166@alum.mit.edu>
In-Reply-To: <823ebe40-711f-9eac-35dd-d0c332a68166@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM2K7t+4Ffs4Ig1UTGS2mLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSujZ/cFtoJ34hVrT6U2MB4U7mLk5JAQMJH4 3rCNtYuRi0NIYD2jxOZXx9kgnMWMEu1/n7F3MXJwsAlYSHT/0waJiwg0M0qse93PCtItLJAh MX/yNhaQGhGBTIkVK/0gzDqJU1vCQSpYBFQlVq3tZwOxeQV8JS6sewO1awKrxMHlqxlBEpwC DhKvph9iB7EZBcQkvp9awwRiMwuIS9x6Mp8J4lABiSV7zjND2KISLx//Y4WwlSTWHt7OAlGv I7Fg9yc2CFtbYtnC18wQiwUlTs58wjKBUWQWkrGzkLTMQtIyC0nLAkaWVYyixanFxbnpRsZ6 qUWZycXF+Xl6eaklmxiB0XBwy2/dHYyrXzseYhTgYFTi4X3whj1CiDWxrLgy9xCjBAezkgjv DR7OCCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8ZivvhwsJpCeWpGanphakFsFkmTg4pRoY6wVD ZmZM5sz/zezif37nOek/F7Yoz82Ind27/+1SN7VrFml5e8yzhT/0lJzUirO+0hccM7f2v+st 2Y3Cb23LvGbW2Gv0PJGurNZ2j3ka4H/3wvXitkMW85ds3bbIasXLdysyQlzuP9vwPD/rEb9e 8VlvuWsLX0ybfHN3aFNjs8oWpme+zfxblViKMxINtZiLihMBD8gDDYICAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/izgMeNMBKtLTO8CxwHYEAtZyy20>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 18:41:36 -0000

>IMO the issue is to sort out different levels of abstraction and layering.
>
>SDP media descriptions are not fundamentally about RTP streams, they are a=
bout something more general. A whole variety=20
>of different sorts of connections/associations can be described using medi=
a descriptions. Some describe a single stream, some=20
>describe multiple streams. When they describe multiple streams, they have =
differing nomenclature for talking about and=20
>denoting those streams. SSRC is meaningful only for RTP. So SSRC, or RTP s=
tream, are not terms that ought to be=20
>fundamentally involved in defining the meaning/function of SDP or BUNDLE. =
(OTOH, they certainly can be considered=20
>as part of a discussion of specializing the media description for RTP-base=
d media descriptions.)
>
>It might be helpful to conceptualize this in terms of superclasses and sub=
classes. MediaDescription is a base class. A
>Bundle is a collection of MediaDescriptions, but not all MediaDescriptions=
 are bundleable - there are some constraints=20
>that must be satisfied.
>
>The key feature of a bundle is that all the contained MediaDescriptions mu=
st share a 5-tuple. The protocol part of the=20
>5-tuple is itself a bit tricky, in that we don't require them to have iden=
tical m-line <proto> fields. Instead, we only=20
>require them to share some lower level part of the stack of protocols in e=
ach of the bundled m-lines. In particular
>DTLS over UDP or DTLS over TCP. (And this is further complicated by ICE, b=
ut that is a separate discussion.)
>
>The next most significant constraint is that all the data received via the=
 5-tuple must be able to be disambiguated=20
>by the receiver regarding which MediaDescription(s) it applies to. My atte=
mpt to describe that as classifying *packets*=20
>turns out to be an over-simplification.
>
>The actual classification probably needs to be layered. If the common prot=
ocol to all the bundled MediaDescriptions=20
>is packet-oriented, then that is where classification can start. Consider =
a bundle including RTP, RTCP, and SCTP: the=20
>first level of classification will be to classify the packet as one of tho=
se. If there is a single SCTP MediaDescription in=20
>the bundle then that will be enough to associate SCTP packets with that on=
e. If there are multiple RTP MediaDescriptions=20
>then RTP and RTCP packets need further analysis. The RTCP packets are comp=
licated, as has been discussed previously.=20
>I still have the sense that RTP packets can be classified to a single Medi=
aDescription, but my understanding is limited=20
>so I am prepared to be wrong about that.
>
>The bottom line is that much of this isn't part of the general bundle mech=
anism. It is specific to the specialization of=20
>bundle to RTP. That does need to be written down *somewhere*. It could be =
part of the bundle draft, as a subsection=20
>specific to RTP. Or it could be in some other document.

Some other document.

Regards,

Christer


From nobody Thu Oct 20 12:02:18 2016
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 E02301296B0 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 12:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.632
X-Spam-Level: 
X-Spam-Status: No, score=-4.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.431, 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 M-9OdX1Vc2mG for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 12:02:15 -0700 (PDT)
Received: from alum-mailsec-scanner-6.mit.edu (alum-mailsec-scanner-6.mit.edu [18.7.68.18]) by ietfa.amsl.com (Postfix) with ESMTP id 5F75D1294FE for <mmusic@ietf.org>; Thu, 20 Oct 2016 12:02:14 -0700 (PDT)
X-AuditID: 12074412-aa5ff700000008d1-19-580914b56123
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id 19.F4.02257.5B419085; Thu, 20 Oct 2016 15:02:13 -0400 (EDT)
Received: from [192.168.1.110] (c-73-186-127-100.hsd1.ma.comcast.net [73.186.127.100]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id u9KJ2Ccr008555 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Thu, 20 Oct 2016 15:02:12 -0400
To: mmusic@ietf.org
References: <CAOW+2duXaBXSq1fwedXj=+rg0s3463GZDqH3Nrg2ss_v8X93dA@mail.gmail.com> <CAOW+2duCa1r0PfObqGPnUDRniG8Gxe3zK=xQwrFhrrYi0wC51A@mail.gmail.com> <CAOW+2ds3oA7_TjCRXJYeZADbuqBqNVtcKBBU5kVVY7H75at47g@mail.gmail.com> <CAOW+2dsxFAj8DUhcM=HHu3reYUsn9A25qGONmBDovc1-FX_RqA@mail.gmail.com> <CAOW+2dtQXwZk2OeiqJ2QCVP9uzmEPmQ0J=RPs80qTjFzGPfDxw@mail.gmail.com> <CAOW+2dshLX7zgszBgk=pS-w1CVL9WoHy6A43gFzp-XBfn_RP8A@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <7dc410dc-19d3-c6df-1989-a72def108feb@alum.mit.edu>
Date: Thu, 20 Oct 2016 15:02:11 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CAOW+2dshLX7zgszBgk=pS-w1CVL9WoHy6A43gFzp-XBfn_RP8A@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOIsWRmVeSWpSXmKPExsUixO6iqLtVhDPC4OVzeYupyx+zODB6LFny kymAMYrLJiU1J7MstUjfLoErY+bCJSwFV5grrrx/xtTA+IGpi5GTQ0LAROLdvmPsXYxcHEIC lxkldv8/ygThvGWS2Nl7hxGkSligVKLpSA8ziC0iICwx4+1fNoiizcwSt6+cBRvFJqAlMefQ f5YuRg4OXgF7ibPPKkHCLAKqEtdOnmEHsUUF0iS2r9sNNodXQFDi5MwnLCA2p0CgxINLi8Fq mAVsJe7MhahhFpCX2P52DvMERr5ZSFpmISmbhaRsASPzKka5xJzSXN3cxMyc4tRk3eLkxLy8 1CJdM73czBK91JTSTYyQMBPawbj+pNwhRgEORiUe3oxz7BFCrIllxZW5hxglOZiURHnf7OWI EOJLyk+pzEgszogvKs1JLT7EKMHBrCTCe4OHM0KINyWxsiq1KB8mJc3BoiTO+3Oxup+QQHpi SWp2ampBahFMVoaDQ0mCVxoYT0KCRanpqRVpmTklCGkmDk6Q4TxAw78KgwwvLkjMLc5Mh8if YtTlWPDj9lomIZa8/LxUKXFeU5AiAZCijNI8uDmw9PCKURzoLWHeGSBVPMDUAjfpFdASJqAl NWkcIEtKEhFSUg2MZltaT2/uWRy5+Pdaw1233gZ3LhULi9BqqVNyWH/APyFQZ5053/73Ky+f +rDs1bVZT+M/fDdYtXaxCm/6xFKp+Aqt5qK5ex68/WCe4DPvlvzcr8+2G+qrBQpedKsJa9h9 83jDq0uXNUuPrOud39eV/1qpOHOS2/OojT4tdhI1hn7iHhU6DPL2SizFGYmGWsxFxYkAxL3p aeoCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9Rdm0UI7Nbgcolqyf97IszXdXpM>
Subject: Re: [MMUSIC] USIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - A new text proposal
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 19:02:17 -0000

On 10/20/16 1:07 PM, Bernard Aboba wrote:
> I think your proposed text is missing some PT-matching aspects.
> Basically, JSEP matches the MID, then SSRC, then PT.  However, if there
> are non-unique PTs, both JSEP as well as ORTC end up routing to one of
> the RtpReceivers (though they currently disagree as to which one) rather
> than dropping the packet.

IMO this case ought to be considered out of scope and the behavior 
undefined.

	Thanks,
	Paul


From nobody Thu Oct 20 12:49:33 2016
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 2CC251294A9 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 12:49:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 FmomcfdpX7zl for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 12:49:19 -0700 (PDT)
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 672431296A6 for <mmusic@ietf.org>; Thu, 20 Oct 2016 12:49:17 -0700 (PDT)
X-AuditID: c1b4fb3a-aa3ff7000000099a-48-58091fba841f
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by  (Symantec Mail Security) with SMTP id 6A.44.02458.ABF19085; Thu, 20 Oct 2016 21:49:16 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0319.002; Thu, 20 Oct 2016 21:49:14 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] USIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - A new text proposal
Thread-Index: AQHSKvR+jgXwi9IAI0elxpJAspWLmqCxkXyAgAAuasA=
Date: Thu, 20 Oct 2016 19:49:13 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BDC0CBB@ESESSMB209.ericsson.se>
References: <CAOW+2duXaBXSq1fwedXj=+rg0s3463GZDqH3Nrg2ss_v8X93dA@mail.gmail.com> <CAOW+2duCa1r0PfObqGPnUDRniG8Gxe3zK=xQwrFhrrYi0wC51A@mail.gmail.com> <CAOW+2ds3oA7_TjCRXJYeZADbuqBqNVtcKBBU5kVVY7H75at47g@mail.gmail.com> <CAOW+2dsxFAj8DUhcM=HHu3reYUsn9A25qGONmBDovc1-FX_RqA@mail.gmail.com> <CAOW+2dtQXwZk2OeiqJ2QCVP9uzmEPmQ0J=RPs80qTjFzGPfDxw@mail.gmail.com> <CAOW+2dshLX7zgszBgk=pS-w1CVL9WoHy6A43gFzp-XBfn_RP8A@mail.gmail.com> <7dc410dc-19d3-c6df-1989-a72def108feb@alum.mit.edu>
In-Reply-To: <7dc410dc-19d3-c6df-1989-a72def108feb@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrALMWRmVeSWpSXmKPExsUyM2K7hO4eec4Ig45mXoupyx+zWKzYcIDV gcnj7/sPTB5LlvxkCmCK4rJJSc3JLEst0rdL4Mp41r2IteA0S8Xid1PYGhgvMXcxcnJICJhI HDgyi7GLkYtDSGA9o8S0T69YQBJCAosZJR7MdOpi5OBgE7CQ6P6nDRIWEfCVePb4NhuILSxQ KjF99j8miHiZxP37rVC2lcT16/cZQWwWAVWJZ40zWUFsXqDe9t87mSF2vWSWON48BSzBKeAg sXL5fDCbUUBM4vupNWCDmAXEJW49mc8EcaiAxJI956GOFpV4+fgfK4StJLH28HYWiHodiQW7 P7FB2NoSyxa+ZoZYLChxcuYTlgmMIrOQjJ2FpGUWkpZZSFoWMLKsYhQtTi0uzk03MtJLLcpM Li7Oz9PLSy3ZxAiMh4NbflvtYDz43PEQowAHoxIP74M37BFCrIllxZW5hxglOJiVRHjfSnFG CPGmJFZWpRblxxeV5qQWH2KU5mBREuc1W3k/XEggPbEkNTs1tSC1CCbLxMEp1cCo0fNkscmm Du+eSc39a/zvunPs8Sk/s8Pn0IwWrQPnXrVtP9xg9fR1yLL+J9sfyh4Q1D7CounjZ6p3tVFa +bwe17nEjV/371Sr7TuzNfTrg7hf9X6HrN+GrJt6VdihjLVa7OaM7f/Y3X6eemBxLm3PjQa2 yVYhKzmvt4U+bzKOjK26t5Zz+i1LJZbijERDLeai4kQA/jUXcoMCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/lAG2pVsUa1tXBMuDhPyWfczimRc>
Subject: Re: [MMUSIC] USIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - A new text proposal
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 19:49:22 -0000

Hi,

>> I think your proposed text is missing some PT-matching aspects.
>> Basically, JSEP matches the MID, then SSRC, then PT.  However, if=20
>> there are non-unique PTs, both JSEP as well as ORTC end up routing to=20
>> one of the RtpReceivers (though they currently disagree as to which=20
>> one) rather than dropping the packet.
>
> IMO this case ought to be considered out of scope and the behaviour undef=
ined.

I agree, and I suggest that we say that packets can be dropped, or processe=
d based on whatever application specific behaviour.

Regards,

Christer


From nobody Thu Oct 20 15:33:56 2016
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 C25491294E1 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 15:33:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 JOQMK7dW9kDm for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 15:33:48 -0700 (PDT)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (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 75A261296AD for <mmusic@ietf.org>; Thu, 20 Oct 2016 15:33:47 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id b81so104019161lfe.1 for <mmusic@ietf.org>; Thu, 20 Oct 2016 15:33:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=gXM11di0bgLZFENe4icfJSw/MDQwRYAvEvtwKO9ln+U=; b=TvuF+06V5P4sTCCM9T6TOimA4HpG48P29bIoVKt2w1rzVolKDQ1Y8W5Z4DB8OuEcEa uWUlAzrQ3XYzH7jYAvF/Fj6iLApWZa/UMmv+DOgaPiDWC//UjRmVewdN+BJ1k/qsFaBL VOFhXXDHlXr1ZwgaebBVCXvMh2bp0Q3OL/Ha92laW7835aqSqo6TIke5yMThEYpvbrc5 ekWLIwlKLSlha4+uuaskb2H43KvcW1NWIkn3Bn/NeEVNOpqnqdqST0EW5Fon70FDg8rW IvB7u9+1670oXPJgfqFj/OsXeYfRzKx1L+kUrcfeBcF6e63XY6iXURtCdoEd2RpVajAK rEhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=gXM11di0bgLZFENe4icfJSw/MDQwRYAvEvtwKO9ln+U=; b=ZX1YprvuLyPQHWtcNaH5sYrkY/Wh0yYzWTzMIRaJz3spwYjsP1n4Vx2zNfIQdVC45B eZvN4qZz90D9YEyWakp2G4ahT7GafZ8I37blJ3RaPxlQ8GHb3RdOIJ4TjacIMr6oGI2L XYxu5boIrShqwgWpkdQZ+/odfuxylTdo5+QWndHCx6+Wr9lzKhfrTAS1IQ5w4A4DIEoN IPhYZkAc8mk8iMFSP2/edDCQxhTGZNa/QsaLYzYwzzaG6293otrkO/8coobiE0CWFNKK 1EP1hqw1aFRhSPLk6dWJ7kMCu+4k9Vz6/rizS/tI294x3tIPsrAnKOhoybOSMrBt0Jd0 K3qw==
X-Gm-Message-State: AA6/9RmvL7C4/5S55eCDjYcSy/PRzTgxKlM1G7dk2FsRZ480cg8GudZ37kBk5pbx9OxL+w==
X-Received: by 10.28.196.5 with SMTP id u5mr310645wmf.23.1477002824573; Thu, 20 Oct 2016 15:33:44 -0700 (PDT)
Received: from alans-mbp.lan ([37.152.254.14]) by smtp.gmail.com with ESMTPSA id ma5sm81794556wjb.47.2016.10.20.15.33.43 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 20 Oct 2016 15:33:43 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_09E7A741-4D30-46CB-AB03-C93DD904A901"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <D42E97C0.117A6%christer.holmberg@ericsson.com>
Date: Thu, 20 Oct 2016 23:33:43 +0100
Message-Id: <AAE65171-77D6-4100-BED6-70DCFF98798D@gmail.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com> <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com> <D42E97C0.117A6%christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MhhKU8TpzENjyOIwFsxWFMj6_Wg>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 22:33:56 -0000

--Apple-Mail=_09E7A741-4D30-46CB-AB03-C93DD904A901
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi Christer,

Upon further thought, yes, you=92re right - any proxy would have to =
support the concept of ICE candidates in the first place, so it really =
doesn=92t matter whether it=92s the m-line transport or not.

So yes, given the issue recently raised in bfcpbis, and the potential =
impact also on SCTP, I=92d be in favour of this clarification in the =
text - that the requirement on the transport line matching a candidate =
is only required for the offerer, not the answerer.

Regards,
Alan

> On 20 Oct 2016, at 13:42, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi Alan,
>=20
> >It=92s definitely something that would enhance the usefulness of ICE =
in transport-agnostic protocols such as BFCP where there=92s no =
guarantee one end implements both UDP and TCP transports (for example).
> >
> >I don=92t see a problem with a change in text to make that second =
requirement of 4.1.1.2 apply only to the offerer (not the answerer) - =
any endpoints implementing this should be fine with this. I would be a =
little more concerned, however, about proxies that may make some wrong =
assumptions in these scenarios.
>=20
> Not sure I understand the proxy question. Even if you DO support the =
transport you indicate in the m- line, it still doesn=92t guarantee that =
you will end up using that transport.
>=20
> Regards,
>=20
> Christer
>=20
>> On 20 Oct 2016, at 09:51, Christer Holmberg =
<christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>> =
wrote:
>>=20
>> Anyone having an opinion on this?
>>=20
>> It may impact a couple of drafts which are about to be finalised, so =
it would be good to hear what people think.
>>=20
>> Regards,
>>=20
>> Christer
>>=20
>> From: mmusic <mmusic-bounces@ietf.org =
<mailto:mmusic-bounces@ietf.org>> on behalf of Christer Holmberg =
<christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>>
>> Date: Monday 17 October 2016 at 12:37
>> To: "mmusic@ietf.org <mailto:mmusic@ietf.org>" <mmusic@ietf.org =
<mailto:mmusic@ietf.org>>
>> Subject: [MMUSIC] draft-ice-sip-sdp: m- line matching default =
candidate in SDP answer?
>>=20
>> Hi,
>>=20
>> The issue in this e-mail has came up during ICE discussions related =
to BFCP and SCTP.
>>=20
>> Section 4.1.1.2 of draft-ietf-mmusic-ice-sip-sdp-10 says:
>>    "The default candidates are added to the SDP as the default
>>    destination for media.  For streams based on RTP, this is done by
>>    placing the IP address and port of the RTP candidate into the "c=3D"=

>>    and "m=3D" lines, respectively.=94
>> =85and:
>>    "The transport addresses that will be the default destination for
>>    media when communicating with non-ICE peers MUST also be present =
as
>>    candidates in one or more a=3Dcandidate lines."
>>=20
>> Assume the offerer sends an offer. The default candidate is =
TCP-based, which will be reflected in the m- line (e.g., TCP/DTLS/SCTP). =
The offer also contains UDP-based candidates.
>>=20
>> Now, assume the default candidate of the answerer is UDP-based =
(perhaps the answerer doesn=92t even support TCP). However, according to =
the O/A rules, the answerer cannot change the m- line proto in the =
answer (e.g., UDP/DTLS/SCTP). So, if I understand correctly, it means =
that the answerer must reject the m- line =96 even if there are =
UDP-based candidates that the answerer would support.
>>=20
>> A solution to this would be to NOT mandate the m- line to match the =
default candidate in the answer. So, in the example above, the answerer =
could include (TCP/DTLS/SCTP) in the m- line, but ONLY provide UDP =
candidates.
>>=20
>> Another solution would to always mandate support of one or more =
specific transports, and specify that the default candidate MUST use =
that transport.
>>=20
>> Regards,
>>=20
>> Christer
>>=20
>>=20
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org <mailto:mmusic@ietf.org>
>> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
>=20


--Apple-Mail=_09E7A741-4D30-46CB-AB03-C93DD904A901
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi Christer,<div class=3D""><br class=3D""></div><div =
class=3D"">Upon further thought, yes, you=92re right - any proxy would =
have to support the concept of ICE candidates in the first place, so it =
really doesn=92t matter whether it=92s the m-line transport or =
not.</div><div class=3D""><br class=3D""></div><div class=3D"">So yes, =
given the issue recently raised in bfcpbis, and the potential impact =
also on SCTP, I=92d be in favour of this clarification in the text - =
that the requirement on the transport line matching a candidate is only =
required for the offerer, not the answerer.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Regards,</div><div =
class=3D"">Alan</div><div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On 20 Oct 2016, at 13:42, =
Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com" =
class=3D"">christer.holmberg@ericsson.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DWindows-1252" class=3D"">

<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; font-size: 14px; font-family: =
Calibri, sans-serif;" class=3D"">
<div class=3D"">Hi Alan,</div>
<div class=3D""><br class=3D"">
</div>
<span id=3D"OLK_SRC_BODY_SECTION" class=3D"">
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D"">
<div class=3D"">&gt;It=92s definitely something that would enhance the =
usefulness of ICE in transport-agnostic protocols such as BFCP where =
there=92s no guarantee one end implements both UDP and TCP transports =
(for example).</div>
<div class=3D"">&gt;</div>
<div class=3D"">&gt;I don=92t see a problem with a change in text to =
make that second requirement of 4.1.1.2 apply only to the offerer (not =
the answerer) - any endpoints implementing this should be fine with =
this. I would be a little more concerned, however, about
 proxies that may make some wrong assumptions in these scenarios.</div>
</div>
</div>
</span>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Not sure I understand the proxy question. Even if you DO =
support the transport you indicate in the m- line, it still doesn=92t =
guarantee that you will end up using that transport.</div>
<span id=3D"OLK_SRC_BODY_SECTION" class=3D"">
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D"">
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Regards,</div>
</div>
</div>
</span>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Christer</div>
<span id=3D"OLK_SRC_BODY_SECTION" class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D"">
<div class=3D""><br class=3D"">
<div class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On 20 Oct 2016, at 09:51, Christer Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com" =
class=3D"">christer.holmberg@ericsson.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; font-size: 14px; font-family: =
Calibri, sans-serif;" class=3D"">
<div class=3D"">Anyone having an opinion on this?</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">It may impact a couple of drafts which are about to be =
finalised, so it would be good to hear what people think.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Regards,</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Christer</div>
<div class=3D""><br class=3D"">
</div>
<span id=3D"OLK_SRC_BODY_SECTION" class=3D"">
<div style=3D"font-family: Calibri; font-size: 11pt; text-align: left; =
border-width: 1pt medium medium; border-style: solid none none; padding: =
3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class=3D"">
<span style=3D"font-weight:bold" class=3D"">From: </span>mmusic &lt;<a =
href=3D"mailto:mmusic-bounces@ietf.org" =
class=3D"">mmusic-bounces@ietf.org</a>&gt; on behalf of Christer =
Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com" =
class=3D"">christer.holmberg@ericsson.com</a>&gt;<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">Date: </span>Monday 17 =
October 2016 at 12:37<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">To: </span>"<a =
href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a>" &lt;<a =
href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a>&gt;<br =
class=3D"">
<span style=3D"font-weight:bold" class=3D"">Subject: </span>[MMUSIC] =
draft-ice-sip-sdp: m- line matching default candidate in SDP answer?<br =
class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D"">
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">Hi,</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">The issue in this e-mail has came up during ICE discussions =
related to BFCP and SCTP.</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">Section 4.1.1.2 of draft-ietf-mmusic-ice-sip-sdp-10 =
says:</font></div>
<div class=3D"">
<pre style=3D"font-size: 14px; font-variant-ligatures: normal; orphans: =
2; widows: 2; word-wrap: break-word; white-space: pre-wrap;" =
class=3D""><font face=3D"Calibri" class=3D"">   "The default candidates =
are added to the SDP as the default
   destination for media.  For streams based on RTP, this is done by
   placing the IP address and port of the RTP candidate into the "c=3D"
   and "m=3D" lines, respectively.=94</font></pre>
<pre style=3D"font-size: 14px; font-variant-ligatures: normal; orphans: =
2; widows: 2; word-wrap: break-word; white-space: pre-wrap;" =
class=3D""><font face=3D"Calibri" class=3D"">=85and:</font></pre>
<pre style=3D"font-size: 14px; font-variant-ligatures: normal; orphans: =
2; widows: 2; word-wrap: break-word; white-space: pre-wrap;" =
class=3D""><pre style=3D"font-variant-ligatures: normal; word-wrap: =
break-word; white-space: pre-wrap;" class=3D""><font face=3D"Calibri" =
class=3D"">   "The transport addresses that will be the default =
destination for
   media when communicating with non-ICE peers MUST also be present as
   candidates in one or more a=3Dcandidate lines."</font></pre></pre>
</div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">Assume the offerer sends an offer. The default c</font><span =
style=3D"font-family: Calibri;" class=3D"">andidate is TCP-based, which =
will be reflected in the m- line (e.g., TCP/DTLS/SCTP). The
 offer also contains UDP-based candidates.</span></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">Now, assume the default candidate of the answerer is =
UDP-based (perhaps the answerer doesn=92t even support TCP). However, =
according to the O/A rules, the answerer cannot change the m- line
 proto in the answer (e.g., UDP/DTLS/SCTP).&nbsp;</font><span =
style=3D"font-family: Calibri;" class=3D"">So, if I understand =
correctly, it means that the answerer must reject the m- line =96 even =
if there are UDP-based candidates that the answerer would =
support.</span></div>
<div style=3D"font-size: 14px;" class=3D""><br class=3D"">
</div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">A solution to this would be to NOT mandate the m- line to =
match the default candidate in the answer. So, in the example above, the =
answerer could include (TCP/DTLS/SCTP) in the m- line, but
 ONLY provide UDP candidates.</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D"">Another solution would to =
always mandate support of one or more specific transports, and specify =
that the default candidate MUST use that transport.</div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">Regards,</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D"">Christer</font></div>
<div style=3D"font-size: 14px;" class=3D""><font face=3D"Calibri" =
class=3D""><br class=3D"">
</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;" =
class=3D""><br class=3D"">
</div>
</div>
</div>
</span></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"">
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
class=3D"">https://www.ietf.org/mailman/listinfo/mmusic</a><br class=3D"">=

</div>
</blockquote>
</div>
<br class=3D"">
</div>
</div>
</span>
</div>

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

--Apple-Mail=_09E7A741-4D30-46CB-AB03-C93DD904A901--


From nobody Thu Oct 20 16:09:56 2016
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 208C2127735 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 16:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5] 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 UcMnU1G0-POv for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 16:09:51 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (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 97937129675 for <mmusic@ietf.org>; Thu, 20 Oct 2016 16:09:51 -0700 (PDT)
Received: by mail-qk0-x22d.google.com with SMTP id o68so123625938qkf.3 for <mmusic@ietf.org>; Thu, 20 Oct 2016 16:09:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+ns1vNjSmFso30J3tpLU2A9GK1DhiYm7ymi8oEPD9J8=; b=eW7cJBlmdlZPUfOrTknnBwIv36+TCrjQ2qOpXOlPdCPuGKaXR4qU2PJj00bsUwT6yi HPSGaaftg0WgfH3XQ6ET+KAbmJ54I/Y4qvkAUwJlMOtxeqAm8U9BAbACQrx0vQdG6d7i bvLIvi1/VIJbL8iqniyGMmYB0eVL8gvNShDIlxoBagzSbWLkUWoQHBqPjnbfTlG6kmBA UoDCdkHgTvy0GJKu9E3J1NSrhNJUyKYXaEahR9vjtMUS2J7Imljce8B9eYkDU8P0SW5J XjkxZxsuWgmG5tnw8rUB7gWZUn+a0BrogGgjQb0A8vPsYk6U2JVA0OVHFrjlAtSK49pR N1uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+ns1vNjSmFso30J3tpLU2A9GK1DhiYm7ymi8oEPD9J8=; b=iTUy1/PhBtO5rAOgxQ2ctgAYZR+38X502aSDh7mVqGQsquIMDQuBEfVyfWxd/RcLF7 YddYKYjB2Yhbgxrw1rR8rReR26OZF1erHu4OUq7dO+gUoyjyj359Qll7Dns08ifOdaTZ CJqu7j5hKaLsX1TIkz8btuNFgWl+xkeubeTCrOu0wDtTtMODOJsQjjOiZdRCvxA35hu5 lZJ+0e0DPYxLVZXCAwFwfRtRjlsoWNsfKEhUma9GYJvYkhmYRVU9zfCC+aXGni9RoGNG C9C2+p457tWBYTHBAm+vIU/Ljo4SPm/VHSGKJN1C8nlxmeSdr8AGqVA1RHlA0uRofJDP TPvg==
X-Gm-Message-State: ABUngveQpc7Y+g2ti9cXGE3INJEVxXQ4+1wnxo6U+zFjXJ6unGFfCz8Je0OF5l0pPf0Dxw==
X-Received: by 10.55.217.218 with SMTP id q87mr2633283qkl.285.1477004990596; Thu, 20 Oct 2016 16:09:50 -0700 (PDT)
Received: from mail-qk0-f182.google.com (mail-qk0-f182.google.com. [209.85.220.182]) by smtp.gmail.com with ESMTPSA id k73sm24305463qke.36.2016.10.20.16.09.50 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Oct 2016 16:09:50 -0700 (PDT)
Received: by mail-qk0-f182.google.com with SMTP id o68so123625518qkf.3 for <mmusic@ietf.org>; Thu, 20 Oct 2016 16:09:50 -0700 (PDT)
X-Received: by 10.55.160.17 with SMTP id j17mr2828736qke.167.1477004989914; Thu, 20 Oct 2016 16:09:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.132.161 with HTTP; Thu, 20 Oct 2016 16:09:49 -0700 (PDT)
In-Reply-To: <AAE65171-77D6-4100-BED6-70DCFF98798D@gmail.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com> <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com> <D42E97C0.117A6%christer.holmberg@ericsson.com> <AAE65171-77D6-4100-BED6-70DCFF98798D@gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Thu, 20 Oct 2016 19:09:49 -0400
X-Gmail-Original-Message-ID: <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com>
Message-ID: <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com>
To: Alan Ford <alan.ford@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c0613fec169ae053f540560
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/CaONvv00qoesP9-51Jfn_qCy5pc>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 23:09:54 -0000

--94eb2c0613fec169ae053f540560
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi All,


What do you propose to put in c=3D and m=3D line in the answer? Whatever
information you are going to put there it will need to have the correct
transport (UDP or TCP) in the m=3D line proto in order to be correctly
interpreted?

Another solution (which would correspond to the practical implementations)
is that when initiating or restarting ICE:
a. Implementations MUST support UDP based protocols and MUST include UDP
based candidates
b. Default candidate MUST be UDP based candidate

As a result m=3D line proto in both offer and answer will always be UDP bas=
ed.

Once ICE nomination process is completed and candidate pair is selected,
transport in m=3D line proto MUST correspond to the transport in nominated
ICE candidate pair.

Regards,

_____________
Roman Shpount

On Thu, Oct 20, 2016 at 6:33 PM, Alan Ford <alan.ford@gmail.com> wrote:

> Hi Christer,
>
> Upon further thought, yes, you=E2=80=99re right - any proxy would have to=
 support
> the concept of ICE candidates in the first place, so it really doesn=E2=
=80=99t
> matter whether it=E2=80=99s the m-line transport or not.
>
> So yes, given the issue recently raised in bfcpbis, and the potential
> impact also on SCTP, I=E2=80=99d be in favour of this clarification in th=
e text -
> that the requirement on the transport line matching a candidate is only
> required for the offerer, not the answerer.
>
> Regards,
> Alan
>
> On 20 Oct 2016, at 13:42, Christer Holmberg <christer.holmberg@ericsson.
> com> wrote:
>
> Hi Alan,
>
> >It=E2=80=99s definitely something that would enhance the usefulness of I=
CE in
> transport-agnostic protocols such as BFCP where there=E2=80=99s no guaran=
tee one
> end implements both UDP and TCP transports (for example).
> >
> >I don=E2=80=99t see a problem with a change in text to make that second
> requirement of 4.1.1.2 apply only to the offerer (not the answerer) - any
> endpoints implementing this should be fine with this. I would be a little
> more concerned, however, about proxies that may make some wrong assumptio=
ns
> in these scenarios.
>
> Not sure I understand the proxy question. Even if you DO support the
> transport you indicate in the m- line, it still doesn=E2=80=99t guarantee=
 that you
> will end up using that transport.
>
> Regards,
>
> Christer
>
> On 20 Oct 2016, at 09:51, Christer Holmberg <christer.holmberg@ericsson.
> com> wrote:
>
> Anyone having an opinion on this?
>
> It may impact a couple of drafts which are about to be finalised, so it
> would be good to hear what people think.
>
> Regards,
>
> Christer
>
> From: mmusic <mmusic-bounces@ietf.org> on behalf of Christer Holmberg <
> christer.holmberg@ericsson.com>
> Date: Monday 17 October 2016 at 12:37
> To: "mmusic@ietf.org" <mmusic@ietf.org>
> Subject: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate
> in SDP answer?
>
> Hi,
>
> The issue in this e-mail has came up during ICE discussions related to
> BFCP and SCTP.
>
> Section 4.1.1.2 of draft-ietf-mmusic-ice-sip-sdp-10 says:
>
>    "The default candidates are added to the SDP as the default
>    destination for media.  For streams based on RTP, this is done by
>    placing the IP address and port of the RTP candidate into the "c=3D"
>    and "m=3D" lines, respectively.=E2=80=9D
>
> =E2=80=A6and:
>
>    "The transport addresses that will be the default destination for
>    media when communicating with non-ICE peers MUST also be present as
>    candidates in one or more a=3Dcandidate lines."
>
>
> Assume the offerer sends an offer. The default candidate is TCP-based,
> which will be reflected in the m- line (e.g., TCP/DTLS/SCTP). The offer
> also contains UDP-based candidates.
>
> Now, assume the default candidate of the answerer is UDP-based (perhaps
> the answerer doesn=E2=80=99t even support TCP). However, according to the=
 O/A
> rules, the answerer cannot change the m- line proto in the answer (e.g.,
> UDP/DTLS/SCTP). So, if I understand correctly, it means that the answerer
> must reject the m- line =E2=80=93 even if there are UDP-based candidates =
that the
> answerer would support.
>
> A solution to this would be to NOT mandate the m- line to match the
> default candidate in the answer. So, in the example above, the answerer
> could include (TCP/DTLS/SCTP) in the m- line, but ONLY provide UDP
> candidates.
>
> Another solution would to always mandate support of one or more specific
> transports, and specify that the default candidate MUST use that transpor=
t.
>
> Regards,
>
> Christer
>
>
> _______________________________________________
> 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
>
>

--94eb2c0613fec169ae053f540560
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi All,</div><div><br></div><div><br></div>What do yo=
u propose to put in c=3D and m=3D line in the answer? Whatever information =
you are going to put there it will need to have the correct transport (UDP =
or TCP) in the m=3D line proto in order to be correctly interpreted?<div><b=
r></div><div>Another solution (which would correspond to the practical impl=
ementations) is that when initiating or restarting ICE:</div><div>a. Implem=
entations MUST support UDP based protocols and MUST include UDP based candi=
dates=C2=A0</div><div>b. Default candidate MUST be UDP based candidate</div=
><div><br></div><div>As a result m=3D line proto in both offer and answer w=
ill always be UDP based.</div><div><br></div><div>Once ICE nomination proce=
ss is completed and candidate pair is selected, transport in m=3D line prot=
o MUST correspond to the transport in nominated ICE candidate pair.</div><d=
iv><br></div><div>Regards,</div></div><div class=3D"gmail_extra"><br clear=
=3D"all"><div><div class=3D"gmail_signature" data-smartmail=3D"gmail_signat=
ure">_____________<br>Roman Shpount</div></div>
<br><div class=3D"gmail_quote">On Thu, Oct 20, 2016 at 6:33 PM, Alan Ford <=
span dir=3D"ltr">&lt;<a href=3D"mailto:alan.ford@gmail.com" target=3D"_blan=
k">alan.ford@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div style=3D"word-wrap:break-word">Hi Christer,<div><br></div><div>Upo=
n further thought, yes, you=E2=80=99re right - any proxy would have to supp=
ort the concept of ICE candidates in the first place, so it really doesn=E2=
=80=99t matter whether it=E2=80=99s the m-line transport or not.</div><div>=
<br></div><div>So yes, given the issue recently raised in bfcpbis, and the =
potential impact also on SCTP, I=E2=80=99d be in favour of this clarificati=
on in the text - that the requirement on the transport line matching a cand=
idate is only required for the offerer, not the answerer.</div><div><br></d=
iv><div>Regards,</div><div>Alan</div><div><div class=3D"h5"><div><br><div><=
blockquote type=3D"cite"><div>On 20 Oct 2016, at 13:42, Christer Holmberg &=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.<wbr>com</a>&gt; wrote:</div><br class=3D"m_-6284803=
581245570341Apple-interchange-newline"><div>



<div style=3D"word-wrap:break-word;font-size:14px;font-family:Calibri,sans-=
serif">
<div>Hi Alan,</div>
<div><br>
</div>
<span id=3D"m_-6284803581245570341OLK_SRC_BODY_SECTION">
<div>
<div style=3D"word-wrap:break-word">
<div>&gt;It=E2=80=99s definitely something that would enhance the usefulnes=
s of ICE in transport-agnostic protocols such as BFCP where there=E2=80=99s=
 no guarantee one end implements both UDP and TCP transports (for example).=
</div>
<div>&gt;</div>
<div>&gt;I don=E2=80=99t see a problem with a change in text to make that s=
econd requirement of 4.1.1.2 apply only to the offerer (not the answerer) -=
 any endpoints implementing this should be fine with this. I would be a lit=
tle more concerned, however, about
 proxies that may make some wrong assumptions in these scenarios.</div>
</div>
</div>
</span>
<div><br>
</div>
<div>Not sure I understand the proxy question. Even if you DO support the t=
ransport you indicate in the m- line, it still doesn=E2=80=99t guarantee th=
at you will end up using that transport.</div>
<span id=3D"m_-6284803581245570341OLK_SRC_BODY_SECTION">
<div>
<div style=3D"word-wrap:break-word">
<div><br>
</div>
<div>Regards,</div>
</div>
</div>
</span>
<div><br>
</div>
<div>Christer</div>
<span id=3D"m_-6284803581245570341OLK_SRC_BODY_SECTION">
<div style=3D"word-wrap:break-word">
<div><br>
<div>
<blockquote type=3D"cite">
<div>On 20 Oct 2016, at 09:51, Christer Holmberg &lt;<a href=3D"mailto:chri=
ster.holmberg@ericsson.com" target=3D"_blank">christer.holmberg@ericsson.<w=
br>com</a>&gt; wrote:</div>
<br class=3D"m_-6284803581245570341Apple-interchange-newline">
<div>
<div style=3D"word-wrap:break-word;font-size:14px;font-family:Calibri,sans-=
serif">
<div>Anyone having an opinion on this?</div>
<div><br>
</div>
<div>It may impact a couple of drafts which are about to be finalised, so i=
t would be good to hear what people think.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"m_-6284803581245570341OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri;font-size:11pt;text-align:left;border-wid=
th:1pt medium medium;border-style:solid none none;padding:3pt 0in 0in;borde=
r-top-color:rgb(181,196,223)">
<span style=3D"font-weight:bold">From: </span>mmusic &lt;<a href=3D"mailto:=
mmusic-bounces@ietf.org" target=3D"_blank">mmusic-bounces@ietf.org</a>&gt; =
on behalf of Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@eric=
sson.com" target=3D"_blank">christer.holmberg@ericsson.<wbr>com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Monday 17 October 2016 at 12:=
37<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:mmusic@=
ietf.org" target=3D"_blank">mmusic@ietf.org</a>&quot; &lt;<a href=3D"mailto=
:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[MMUSIC] draft-ice-sip-sdp=
: m- line matching default candidate in SDP answer?<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap:break-word">
<div style=3D"font-size:14px"><font face=3D"Calibri">Hi,</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri">The issue in this e-ma=
il has came up during ICE discussions related to BFCP and SCTP.</font></div=
>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri">Section 4.1.1.2 of dra=
ft-ietf-mmusic-ice-sip-sdp-<wbr>10 says:</font></div>
<div>
<pre style=3D"font-size:14px;font-variant-ligatures:normal;word-wrap:break-=
word;white-space:pre-wrap"><font face=3D"Calibri">   &quot;The default cand=
idates are added to the SDP as the default
   destination for media.  For streams based on RTP, this is done by
   placing the IP address and port of the RTP candidate into the &quot;c=3D=
&quot;
   and &quot;m=3D&quot; lines, respectively.=E2=80=9D</font></pre>
<pre style=3D"font-size:14px;font-variant-ligatures:normal;word-wrap:break-=
word;white-space:pre-wrap"><font face=3D"Calibri">=E2=80=A6and:</font></pre=
>
<pre style=3D"font-size:14px;font-variant-ligatures:normal;word-wrap:break-=
word;white-space:pre-wrap"><pre style=3D"font-variant-ligatures:normal;word=
-wrap:break-word;white-space:pre-wrap"><font face=3D"Calibri">   &quot;The =
transport addresses that will be the default destination for
   media when communicating with non-ICE peers MUST also be present as
   candidates in one or more a=3Dcandidate lines.&quot;</font></pre></pre>
</div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri">Assume the offerer sen=
ds an offer. The default c</font><span style=3D"font-family:Calibri">andida=
te is TCP-based, which will be reflected in the m- line (e.g., TCP/DTLS/SCT=
P). The
 offer also contains UDP-based candidates.</span></div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri">Now, assume the defaul=
t candidate of the answerer is UDP-based (perhaps the answerer doesn=E2=80=
=99t even support TCP). However, according to the O/A rules, the answerer c=
annot change the m- line
 proto in the answer (e.g., UDP/DTLS/SCTP).=C2=A0</font><span style=3D"font=
-family:Calibri">So, if I understand correctly, it means that the answerer =
must reject the m- line =E2=80=93 even if there are UDP-based candidates th=
at the answerer would support.</span></div>
<div style=3D"font-size:14px"><br>
</div>
<div style=3D"font-size:14px"><font face=3D"Calibri">A solution to this wou=
ld be to NOT mandate the m- line to match the default candidate in the answ=
er. So, in the example above, the answerer could include (TCP/DTLS/SCTP) in=
 the m- line, but
 ONLY provide UDP candidates.</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px">Another solution would to always mandate supp=
ort of one or more specific transports, and specify that the default candid=
ate MUST use that transport.</div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri">Regards,</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri">Christer</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
</div>
</div>
</span></div>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</span>
</div>

</div></blockquote></div><br></div></div></div></div><br>__________________=
____________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
<br></blockquote></div><br></div>

--94eb2c0613fec169ae053f540560--


From nobody Thu Oct 20 23:32:37 2016
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 89914129496 for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 23:32:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 7iaFpyBxFGSk for <mmusic@ietfa.amsl.com>; Thu, 20 Oct 2016 23:32:33 -0700 (PDT)
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 C26CB12941D for <mmusic@ietf.org>; Thu, 20 Oct 2016 23:32:32 -0700 (PDT)
X-AuditID: c1b4fb30-f60a598000000cb2-ed-5809b67eeca9
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by  (Symantec Mail Security) with SMTP id 35.EB.03250.E76B9085; Fri, 21 Oct 2016 08:32:30 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0319.002; Fri, 21 Oct 2016 08:32:09 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>, Alan Ford <alan.ford@gmail.com>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
Thread-Index: AQHSKq8ixsJ53smzZ0iYfg1cr+NRB6CxH5OAgAA8sICAAHDegIAAChaAgACv1AA=
Date: Fri, 21 Oct 2016 06:32:09 +0000
Message-ID: <D42F91D8.11807%christer.holmberg@ericsson.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com> <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com> <D42E97C0.117A6%christer.holmberg@ericsson.com> <AAE65171-77D6-4100-BED6-70DCFF98798D@gmail.com> <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com>
In-Reply-To: <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.147]
Content-Type: multipart/alternative; boundary="_000_D42F91D811807christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrAIsWRmVeSWpSXmKPExsUyM2K7t27dNs4Igx0tFhYrz61gtpi6/DGL xYwLU5kdmD12zrrL7rFkyU8mj1tTCgKYo7hsUlJzMstSi/TtErgyjr5+x1awrb7iwN7vjA2M v3K6GDk5JARMJPbsnsfUxcjFISSwnlGic99tFpCEkMBiRok3fzm7GDk42AQsJLr/aYOYIgJu EpP3mIGYzALqElcXB4EUCwvESNxa+YcdxBYRiJW4euY9K4TtJ9Ez4w4biM0ioCpx7NdidpBW XgFrieY5hRBLzzBJrL7XBFbPKRAocaz9ACOIzSggJvH91BomEJtZQFzi1pP5TBAXC0gs2XOe GcIWlXj5+B8ryExRAT2JNffDQEwJASWJaVvTIDoTJPqPfAar5hUQlDg58wnLBEbRWUiGzkJS NgtJGUTcQOL9ufnMELa2xLKFr6FsfYmNX84yQtjWEv9etLEhq1nAyLGKUbQ4tTgpN93ISC+1 KDO5uDg/Ty8vtWQTIzAeD275bbCD8eVzx0OMAhyMSjy8D96wRwixJpYVV+YeYpTgYFYS4d26 hjNCiDclsbIqtSg/vqg0J7X4EKM0B4uSOK/ZyvvhQgLpiSWp2ampBalFMFkmDk6pBkZRZU1Z saS2byWMH61S5qk2dFZWvFvCwnNa0Sez22VysMDyuNmnGTuM30+4uWn/F+Nf20szeZqn2nH9 F7jsd0PFIkv89Yu3YkaNBzJuLtBWCP8mljpnv2xlz/YJbJtupHz+6hN4R2+3et8KzT8q2uUc EhtecewoNE+/YZS5yPHjJjnJ5efvGCmxFGckGmoxFxUnAgBh1u9owwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/LRfd65btC9pLnsb5qRXOBE7LcxY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Oct 2016 06:32:35 -0000

--_000_D42F91D811807christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

>What do you propose to put in c=3D and m=3D line in the answer? Whatever i=
nformation you are going to put there it will need to have the correct tran=
sport (UDP or TCP) in the m=3D line proto in order to be correctly interpre=
ted?
>
>Another solution (which would correspond to the practical implementations)=
 is that when initiating or restarting ICE:
>a. Implementations MUST support UDP based protocols and MUST include UDP b=
ased candidates
>b. Default candidate MUST be UDP based candidate
>
>As a result m=3D line proto in both offer and answer will always be UDP ba=
sed.
>
>Once ICE nomination process is completed and candidate pair is selected, t=
ransport in m=3D line proto MUST correspond to the transport in nominated I=
CE candidate pair.

Mandating UDP would probably work for most protocols (RTP, SCTP-over-DTLS e=
tc), but can we do it for BFCP? We could of course say that, if an BFCP end=
point supports ICE, it MUST also support BFCP-over-UDP.

Regards,

Christer


On Thu, Oct 20, 2016 at 6:33 PM, Alan Ford <alan.ford@gmail.com<mailto:alan=
.ford@gmail.com>> wrote:
Hi Christer,

Upon further thought, yes, you=92re right - any proxy would have to support=
 the concept of ICE candidates in the first place, so it really doesn=92t m=
atter whether it=92s the m-line transport or not.

So yes, given the issue recently raised in bfcpbis, and the potential impac=
t also on SCTP, I=92d be in favour of this clarification in the text - that=
 the requirement on the transport line matching a candidate is only require=
d for the offerer, not the answerer.

Regards,
Alan

On 20 Oct 2016, at 13:42, Christer Holmberg <christer.holmberg@ericsson.com=
<mailto:christer.holmberg@ericsson.com>> wrote:

Hi Alan,

>It=92s definitely something that would enhance the usefulness of ICE in tr=
ansport-agnostic protocols such as BFCP where there=92s no guarantee one en=
d implements both UDP and TCP transports (for example).
>
>I don=92t see a problem with a change in text to make that second requirem=
ent of 4.1.1.2 apply only to the offerer (not the answerer) - any endpoints=
 implementing this should be fine with this. I would be a little more conce=
rned, however, about proxies that may make some wrong assumptions in these =
scenarios.

Not sure I understand the proxy question. Even if you DO support the transp=
ort you indicate in the m- line, it still doesn=92t guarantee that you will=
 end up using that transport.

Regards,

Christer

On 20 Oct 2016, at 09:51, Christer Holmberg <christer.holmberg@ericsson.com=
<mailto:christer.holmberg@ericsson.com>> wrote:

Anyone having an opinion on this?

It may impact a couple of drafts which are about to be finalised, so it wou=
ld be good to hear what people think.

Regards,

Christer

From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on b=
ehalf of Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.=
holmberg@ericsson.com>>
Date: Monday 17 October 2016 at 12:37
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>
Subject: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in =
SDP answer?

Hi,

The issue in this e-mail has came up during ICE discussions related to BFCP=
 and SCTP.

Section 4.1.1.2 of draft-ietf-mmusic-ice-sip-sdp-10 says:

   "The default candidates are added to the SDP as the default
   destination for media.  For streams based on RTP, this is done by
   placing the IP address and port of the RTP candidate into the "c=3D"
   and "m=3D" lines, respectively.=94

=85and:

   "The transport addresses that will be the default destination for
   media when communicating with non-ICE peers MUST also be present as
   candidates in one or more a=3Dcandidate lines."

Assume the offerer sends an offer. The default candidate is TCP-based, whic=
h will be reflected in the m- line (e.g., TCP/DTLS/SCTP). The offer also co=
ntains UDP-based candidates.

Now, assume the default candidate of the answerer is UDP-based (perhaps the=
 answerer doesn=92t even support TCP). However, according to the O/A rules,=
 the answerer cannot change the m- line proto in the answer (e.g., UDP/DTLS=
/SCTP). So, if I understand correctly, it means that the answerer must reje=
ct the m- line =96 even if there are UDP-based candidates that the answerer=
 would support.

A solution to this would be to NOT mandate the m- line to match the default=
 candidate in the answer. So, in the example above, the answerer could incl=
ude (TCP/DTLS/SCTP) in the m- line, but ONLY provide UDP candidates.

Another solution would to always mandate support of one or more specific tr=
ansports, and specify that the default candidate MUST use that transport.

Regards,

Christer


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



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



--_000_D42F91D811807christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <AA43F9B15DD1034E8FFB5F8EA06F51C8@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir=3D"ltr">&gt;What do you propose to put in c=3D and m=3D line in th=
e answer? Whatever information you are going to put there it will need to h=
ave the correct transport (UDP or TCP) in the m=3D line proto in order to b=
e correctly interpreted?</div>
</div>
</div>
</span>
<div>&gt;</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir=3D"ltr">
<div>&gt;Another solution (which would correspond to the practical implemen=
tations) is that when initiating or restarting ICE:</div>
<div>&gt;a. Implementations MUST support UDP based protocols and MUST inclu=
de UDP based candidates&nbsp;</div>
<div>&gt;b. Default candidate MUST be UDP based candidate</div>
<div>&gt;</div>
<div>&gt;As a result m=3D line proto in both offer and answer will always b=
e UDP based.</div>
<div>&gt;</div>
<div>&gt;Once ICE nomination process is completed and candidate pair is sel=
ected, transport in m=3D line proto MUST correspond to the transport in nom=
inated ICE candidate pair.</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div>Mandating UDP would probably work for most protocols (RTP, SCTP-over-D=
TLS etc), but can we do it for BFCP? We could of course say that, if an BFC=
P endpoint supports ICE, it MUST also support BFCP-over-UDP.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">On Thu, Oct 20, 2016 at 6:33 PM, Alan Ford <span=
 dir=3D"ltr">
&lt;<a href=3D"mailto:alan.ford@gmail.com" target=3D"_blank">alan.ford@gmai=
l.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">Hi Christer,
<div><br>
</div>
<div>Upon further thought, yes, you=92re right - any proxy would have to su=
pport the concept of ICE candidates in the first place, so it really doesn=
=92t matter whether it=92s the m-line transport or not.</div>
<div><br>
</div>
<div>So yes, given the issue recently raised in bfcpbis, and the potential =
impact also on SCTP, I=92d be in favour of this clarification in the text -=
 that the requirement on the transport line matching a candidate is only re=
quired for the offerer, not the answerer.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Alan</div>
<div>
<div class=3D"h5">
<div><br>
<div>
<blockquote type=3D"cite">
<div>On 20 Oct 2016, at 13:42, Christer Holmberg &lt;<a href=3D"mailto:chri=
ster.holmberg@ericsson.com" target=3D"_blank">christer.holmberg@ericsson.<w=
br>com</a>&gt; wrote:</div>
<br class=3D"m_-6284803581245570341Apple-interchange-newline">
<div>
<div style=3D"word-wrap:break-word;font-size:14px;font-family:Calibri,sans-=
serif">
<div>Hi Alan,</div>
<div><br>
</div>
<span id=3D"m_-6284803581245570341OLK_SRC_BODY_SECTION">
<div>
<div style=3D"word-wrap:break-word">
<div>&gt;It=92s definitely something that would enhance the usefulness of I=
CE in transport-agnostic protocols such as BFCP where there=92s no guarante=
e one end implements both UDP and TCP transports (for example).</div>
<div>&gt;</div>
<div>&gt;I don=92t see a problem with a change in text to make that second =
requirement of 4.1.1.2 apply only to the offerer (not the answerer) - any e=
ndpoints implementing this should be fine with this. I would be a little mo=
re concerned, however, about proxies
 that may make some wrong assumptions in these scenarios.</div>
</div>
</div>
</span>
<div><br>
</div>
<div>Not sure I understand the proxy question. Even if you DO support the t=
ransport you indicate in the m- line, it still doesn=92t guarantee that you=
 will end up using that transport.</div>
<span id=3D"m_-6284803581245570341OLK_SRC_BODY_SECTION">
<div>
<div style=3D"word-wrap:break-word">
<div><br>
</div>
<div>Regards,</div>
</div>
</div>
</span>
<div><br>
</div>
<div>Christer</div>
<span id=3D"m_-6284803581245570341OLK_SRC_BODY_SECTION">
<div style=3D"word-wrap:break-word">
<div><br>
<div>
<blockquote type=3D"cite">
<div>On 20 Oct 2016, at 09:51, Christer Holmberg &lt;<a href=3D"mailto:chri=
ster.holmberg@ericsson.com" target=3D"_blank">christer.holmberg@ericsson.<w=
br>com</a>&gt; wrote:</div>
<br class=3D"m_-6284803581245570341Apple-interchange-newline">
<div>
<div style=3D"word-wrap:break-word;font-size:14px;font-family:Calibri,sans-=
serif">
<div>Anyone having an opinion on this?</div>
<div><br>
</div>
<div>It may impact a couple of drafts which are about to be finalised, so i=
t would be good to hear what people think.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"m_-6284803581245570341OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri;font-size:11pt;text-align:left;border-wid=
th:1pt medium medium;border-style:solid none none;padding:3pt 0in 0in;borde=
r-top-color:rgb(181,196,223)">
<span style=3D"font-weight:bold">From: </span>mmusic &lt;<a href=3D"mailto:=
mmusic-bounces@ietf.org" target=3D"_blank">mmusic-bounces@ietf.org</a>&gt; =
on behalf of Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@eric=
sson.com" target=3D"_blank">christer.holmberg@ericsson.<wbr>com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Monday 17 October 2016 at 12:=
37<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:mmusic@=
ietf.org" target=3D"_blank">mmusic@ietf.org</a>&quot; &lt;<a href=3D"mailto=
:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[MMUSIC] draft-ice-sip-sdp=
: m- line matching default candidate in SDP answer?<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap:break-word">
<div style=3D"font-size:14px"><font face=3D"Calibri">Hi,</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri">The issue in this e-ma=
il has came up during ICE discussions related to BFCP and SCTP.</font></div=
>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri">Section 4.1.1.2 of dra=
ft-ietf-mmusic-ice-sip-sdp-<wbr>10 says:</font></div>
<div>
<pre style=3D"font-size:14px;font-variant-ligatures:normal;word-wrap:break-=
word;white-space:pre-wrap"><font face=3D"Calibri">   &quot;The default cand=
idates are added to the SDP as the default
   destination for media.  For streams based on RTP, this is done by
   placing the IP address and port of the RTP candidate into the &quot;c=3D=
&quot;
   and &quot;m=3D&quot; lines, respectively.=94</font></pre>
<pre style=3D"font-size:14px;font-variant-ligatures:normal;word-wrap:break-=
word;white-space:pre-wrap"><font face=3D"Calibri">=85and:</font></pre>
<pre style=3D"font-size:14px;font-variant-ligatures:normal;word-wrap:break-=
word;white-space:pre-wrap"><pre style=3D"font-variant-ligatures:normal;word=
-wrap:break-word;white-space:pre-wrap"><font face=3D"Calibri">   &quot;The =
transport addresses that will be the default destination for
   media when communicating with non-ICE peers MUST also be present as
   candidates in one or more a=3Dcandidate lines.&quot;</font></pre></pre>
</div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri">Assume the offerer sen=
ds an offer. The default c</font><span style=3D"font-family:Calibri">andida=
te is TCP-based, which will be reflected in the m- line (e.g., TCP/DTLS/SCT=
P). The offer also contains UDP-based
 candidates.</span></div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri">Now, assume the defaul=
t candidate of the answerer is UDP-based (perhaps the answerer doesn=92t ev=
en support TCP). However, according to the O/A rules, the answerer cannot c=
hange the m- line proto in the answer
 (e.g., UDP/DTLS/SCTP).&nbsp;</font><span style=3D"font-family:Calibri">So,=
 if I understand correctly, it means that the answerer must reject the m- l=
ine =96 even if there are UDP-based candidates that the answerer would supp=
ort.</span></div>
<div style=3D"font-size:14px"><br>
</div>
<div style=3D"font-size:14px"><font face=3D"Calibri">A solution to this wou=
ld be to NOT mandate the m- line to match the default candidate in the answ=
er. So, in the example above, the answerer could include (TCP/DTLS/SCTP) in=
 the m- line, but ONLY provide UDP candidates.</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px">Another solution would to always mandate supp=
ort of one or more specific transports, and specify that the default candid=
ate MUST use that transport.</div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri">Regards,</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri">Christer</font></div>
<div style=3D"font-size:14px"><font face=3D"Calibri"><br>
</font></div>
<div style=3D"font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
</div>
</div>
</span></div>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</span></div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D42F91D811807christerholmbergericssoncom_--


From nobody Fri Oct 21 01:15:31 2016
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 7655312711D for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 01:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 8Wwkc4Akdc0r for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 01:15:28 -0700 (PDT)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 AA51F12949B for <mmusic@ietf.org>; Fri, 21 Oct 2016 01:15:28 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id z190so136745134qkc.2 for <mmusic@ietf.org>; Fri, 21 Oct 2016 01:15:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PSZJS6xI3P70jgHALHsiePv3qRZA84Sjz8g8Dd1HGro=; b=skuzh9x+WtjxAyzUVxKbN4406DwcXnMCRn+rIv4Uq70XyxVKXmocHVXeKwSOLolcoW 4hnMqAPMR3ju5EkpTd9NoCYmdnNWjXaQ6vx9yN3huXs1zO+DU4Zv7D0+oUfWSjez5GUo tF6akkOyG57baoXeHwfYCQNocEk9OGCiRFwj2sMJGTVAcObUxwbbytFW5XBhPgDyB0iQ aZvmeslvL8HBDM45MzWHSzzU110GV+5v+PFo2TYrvIKtTk/bBLVYc9uDCdoW5IhOMuIv rEKsJ0YX5gGB3ytSZtzgcA7rZSw5gfpw559163I8Pa35UoBAnW2nB9qjjdgwUzmxRz/2 Cxqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PSZJS6xI3P70jgHALHsiePv3qRZA84Sjz8g8Dd1HGro=; b=l2+P6B8/hLHIGbzDtvhSyV+VnY+tLc5mWxg2Nbo34pERxrWlg1CpaEhMui4iG3SLbg 1RYz541mFu175t0ntc/suW10vHxoiYmS3Yl/Y362hRJ2On1eyl+8wILrpO1Wy0b0hwzE hqXE/pLadyKlXNXgIjg29faBZSehH4dKgA95zuWLvroHhtZlZ+w8AJMU8kAQ2GRu6XO9 /8eBsnGbua6V0hIcQW0O2GqLmT5ZSghy1a+gy5Pf6pT0MYvjS++sle2vmNWZoJ++9i+z WxdNsm88rcfBVIaSIrEPonyUAdp+j8IjcGRcFkznuqrkWWU527QBAfTE4I3guxr/kF3n z7/Q==
X-Gm-Message-State: ABUngve+jdLM4p7cZ27wCCqtGx15jXmLvTLTRO5Q7+bi4uJ0VNnH1+vusYkUIDOYREt9ug==
X-Received: by 10.194.200.39 with SMTP id jp7mr3107108wjc.64.1477037727732; Fri, 21 Oct 2016 01:15:27 -0700 (PDT)
Received: from alans-mbp.lan ([37.152.254.14]) by smtp.gmail.com with ESMTPSA id c7sm1584389wjk.19.2016.10.21.01.15.23 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 21 Oct 2016 01:15:26 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com>
Date: Fri, 21 Oct 2016 09:15:13 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D55D7C56-4618-4C75-A2A7-F731F4A1142D@gmail.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com> <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com> <D42E97C0.117A6%christer.holmberg@ericsson.com> <AAE65171-77D6-4100-BED6-70DCFF98798D@gmail.com> <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/DOm_wSH5f4q9JAftA40gRWIFkOc>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Oct 2016 08:15:30 -0000

Hi Roman,

> On 21 Oct 2016, at 00:09, Roman Shpount <roman@telurix.com> wrote:
>=20
> What do you propose to put in c=3D and m=3D line in the answer? =
Whatever information you are going to put there it will need to have the =
correct transport (UDP or TCP) in the m=3D line proto in order to be =
correctly interpreted?

That=E2=80=99s the basis of the question, however. For the answer, is =
there any reason the m-line transport actually does need to match an ICE =
candidate?

Regards,
Alan


From nobody Fri Oct 21 01:45:48 2016
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 41F6E1294E5 for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 01:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 NlvX1h0Jpazl for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 01:45:45 -0700 (PDT)
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 8041F129450 for <mmusic@ietf.org>; Fri, 21 Oct 2016 01:45:45 -0700 (PDT)
X-AuditID: c1b4fb2d-1dbff700000009f7-dd-5809d5b712f8
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by  (Symantec Mail Security) with SMTP id 03.32.02551.7B5D9085; Fri, 21 Oct 2016 10:45:43 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0319.002; Fri, 21 Oct 2016 10:45:42 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Alan Ford <alan.ford@gmail.com>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
Thread-Index: AQHSKq8ixsJ53smzZ0iYfg1cr+NRB6CxH5OAgAA8sICAAHDegIAAChaAgACYYoCAADzBAA==
Date: Fri, 21 Oct 2016 08:45:42 +0000
Message-ID: <D42FB1C3.1184E%christer.holmberg@ericsson.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com> <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com> <D42E97C0.117A6%christer.holmberg@ericsson.com> <AAE65171-77D6-4100-BED6-70DCFF98798D@gmail.com> <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com> <D55D7C56-4618-4C75-A2A7-F731F4A1142D@gmail.com>
In-Reply-To: <D55D7C56-4618-4C75-A2A7-F731F4A1142D@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <539127F408EBBA45AF03F15E7E8FBC11@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOIsWRmVeSWpSXmKPExsUyM2K7ru72q5wRBt9XGVmsPLeC2WLq8scs FjMuTGV2YPbYOesuu8eSJT+ZPG5NKQhgjuKySUnNySxLLdK3S+DK6O26wlqwnbXi8anr7A2M y1i6GDk5JARMJH4d+g9kc3EICaxnlNh8sosRwlnMKHF5wmcgh4ODTcBCovufNkiDiICbxORn fWwgYWYBdYmri4NAwsICMRK3Vv5hhyiJlbh65j0rSImIQJjE6rMRIGEWAVWJ469usoHYvALW Eifmv2OH2PSfSWLGxh1gCU4BW4kJ1y+D2YwCYhLfT61hArGZBcQlbj2ZzwRxs4DEkj3nmSFs UYmXj/+B7RIV0JNYcz8MIqwk8WPDJRaIVj2JG1OnsEHY1hIrdnxjhrC1JZYtfM0McY+gxMmZ T1gmMIrPQrJtFpL2WUjaZyFpn4WkfQEj6ypG0eLU4uLcdCNjvdSizOTi4vw8vbzUkk2MwOg7 uOW37g7G1a8dDzEKcDAq8fA+eMMeIcSaWFZcmXuIUYKDWUmEN+oSZ4QQb0piZVVqUX58UWlO avEhRmkOFiVxXrOV98OFBNITS1KzU1MLUotgskwcnFINjBq2xj6xKz04Q3Qrtid+0787NfTF lccs570ar7CHtVSU5/Nnpd8xnvvVbHr/I26v2D3zmyKtE588C2GPUvjIXSDVaZwmoeWvKv7D Yq6spkyvkXrod95vKtfW/dNdu4FLS/924p8+awN3pbuJ3Es0YgUSXpaWN+wy/htvXaiy7Jzi IbYNd58osRRnJBpqMRcVJwIAoseuILoCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/yIYACZA6RMsZExnaZ-DD0jkb_jk>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Oct 2016 08:45:47 -0000

Hi,

>> On 21 Oct 2016, at 00:09, Roman Shpount <roman@telurix.com> wrote:
>>=20
>> What do you propose to put in c=3D and m=3D line in the answer? Whatever
>>information you are going to put there it will need to have the correct
>>transport (UDP or TCP) in the m=3D line proto in order to be correctly
>>interpreted?
>
>That=B9s the basis of the question, however. For the answer, is there any
>reason the m-line transport actually does need to match an ICE candidate?

It=B9s not only about the m- line transport. The IP address and port in the
c/m- line most likely won=B9t be valid either (if you use different ports
and addresses for UDP and TCP).

Regards,

Christer


From nobody Fri Oct 21 02:34:43 2016
Return-Path: <magnus.westerlund@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 7769A128B44 for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 02:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 frH5p71OeNc9 for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 02:34:40 -0700 (PDT)
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 80BD312954B for <mmusic@ietf.org>; Fri, 21 Oct 2016 02:34:39 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-48-5809e12d6316
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by  (Symantec Mail Security) with SMTP id DF.9E.02551.D21E9085; Fri, 21 Oct 2016 11:34:37 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.74) with Microsoft SMTP Server id 14.3.319.2; Fri, 21 Oct 2016 11:34:36 +0200
To: Bernard Aboba <bernard.aboba@gmail.com>, Christer Holmberg <christer.holmberg@ericsson.com>
References: <CAOW+2duXaBXSq1fwedXj=+rg0s3463GZDqH3Nrg2ss_v8X93dA@mail.gmail.com> <CAOW+2duCa1r0PfObqGPnUDRniG8Gxe3zK=xQwrFhrrYi0wC51A@mail.gmail.com> <CAOW+2ds3oA7_TjCRXJYeZADbuqBqNVtcKBBU5kVVY7H75at47g@mail.gmail.com> <CAOW+2dsxFAj8DUhcM=HHu3reYUsn9A25qGONmBDovc1-FX_RqA@mail.gmail.com> <CAOW+2dtQXwZk2OeiqJ2QCVP9uzmEPmQ0J=RPs80qTjFzGPfDxw@mail.gmail.com> <CAOW+2dshLX7zgszBgk=pS-w1CVL9WoHy6A43gFzp-XBfn_RP8A@mail.gmail.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <279a0668-16fa-609c-2b0c-a3ac2df540d7@ericsson.com>
Date: Fri, 21 Oct 2016 11:34:36 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CAOW+2dshLX7zgszBgk=pS-w1CVL9WoHy6A43gFzp-XBfn_RP8A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPLMWRmVeSWpSXmKPExsUyM2K7h67uQ84Ig//frC027PvPbLH85QlG i6nLH7M4MHtMu3+fzWPnrLvsHkuW/GQKYI7isklJzcksSy3St0vgytj5fTlLwSaeipOzulka GL9xdjFyckgImEhcurOepYuRi0NIYD2jRMuhV6wQznJGiWlT/jKBVAkL5Ej0T9/BAmKLCCRK rJj+gRmiaDOzxO0rZ4GKODiYBZwkpjw1A6lhE7CQuPmjkQ3E5hWwl+i4e4wdxGYRUJVYtOoh M4gtKhAjcf3ZI6gaQYmTM5+AzecUCJR4cGkxWD0z0JyZ888zQtjyEs1bZ4P1CgloSzQ0dbBO YBSYhaR9FpKWWUhaFjAyr2IULU4tLs5NNzLWSy3KTC4uzs/Ty0st2cQIDNaDW37r7mBc/drx EKMAB6MSD++DN+wRQqyJZcWVuYcYJTiYlUR46x5wRgjxpiRWVqUW5ccXleakFh9ilOZgURLn NVt5P1xIID2xJDU7NbUgtQgmy8TBKdXA2Jz0uVsqYN8Dh9g3ZmoHywtjNWeEXTDIddDb1sfp 7qYwjctaasrCuS71HF/LZrtMs/L8f7cswDtBvOdSunnyU61Vl2V4YorEznoxduh4y5ZyxxVY ek/fbCB5KSi+5dgeh8MR3DGlNYcOudyfY9/1zEvnQGb62hVXZrUGay686zH1YK6tt48SS3FG oqEWc1FxIgCBWzOzUgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/qVY3CGbDqDynFEvXpgulGA9HxLg>
Cc: mmusic WG <mmusic@ietf.org>, Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] USIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - A new text proposal
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Oct 2016 09:34:41 -0000

Den 2016-10-20 kl. 19:07, skrev Bernard Aboba:
> I think your proposed text is missing some PT-matching aspects.
> Basically, JSEP matches the MID, then SSRC, then PT.  However, if there
> are non-unique PTs, both JSEP as well as ORTC end up routing to one of
> the RtpReceivers (though they currently disagree as to which one) rather
> than dropping the packet.
>
>    If an offerer and answerer is not able to associate an RTP stream
>    with an "m=" line (using the mechanisms described in this section, or
>    using other appropriate mechanism), it SHOULD drop the RTP/RTCP
>    packets associated with the RTP stream, once non-stream specific
>    processing (e.g., related to congestion control) of the packets have
>    occurred.  Note that RTCP packets might be associated with multiple
>    RTP streams.
>

I think that is unnecessary and agree that this is out of scope. Bundle 
requires one to use MIDs as identifiers. So either use MID and BUNDLE, 
else don't bundle. I don't see the need for describing behavior that is 
not the intended when using BUNDLE.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Fri Oct 21 02:46:26 2016
Return-Path: <magnus.westerlund@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 4087112956F for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 02:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 1EPCgqWAqWwX for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 02:46:23 -0700 (PDT)
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 7224C128B44 for <mmusic@ietf.org>; Fri, 21 Oct 2016 02:46:23 -0700 (PDT)
X-AuditID: c1b4fb25-14bff7000000793b-16-5809e3ed9280
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by  (Symantec Mail Security) with SMTP id 67.38.31035.DE3E9085; Fri, 21 Oct 2016 11:46:21 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.92) with Microsoft SMTP Server id 14.3.319.2; Fri, 21 Oct 2016 11:46:20 +0200
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, <mmusic@ietf.org>
References: <D423EDCF.1102F%christer.holmberg@ericsson.com> <2E473DFD-E9B0-4C8A-B52D-EE456AE487BE@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BD6861A@ESESSMB209.ericsson.se> <36223f41-f534-831d-a045-480ef6a5f601@ericsson.com> <9D9F44AA-E487-4C1A-BA36-D3134347653E@csperkins.org> <D42AA198.11408%christer.holmberg@ericsson.com> <A2448DA9-6634-4583-A4B6-040B93371254@csperkins.org> <D42D44E7.11653%christer.holmberg@ericsson.com> <9483F0F1-F651-4471-9AC0-6AA79EA2480D@csperkins.org> <0b0a5e0b-a038-a230-cd18-05d1b759064e@alum.mit.edu> <c0b01f60-7a68-59e6-fcb5-2a5e7e852974@ericsson.com> <823ebe40-711f-9eac-35dd-d0c332a68166@alum.mit.edu>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <e900c092-38f8-49e8-c803-7efc61c43464@ericsson.com>
Date: Fri, 21 Oct 2016 11:46:19 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <823ebe40-711f-9eac-35dd-d0c332a68166@alum.mit.edu>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFLMWRmVeSWpSXmKPExsUyM2J7lO7bx5wRBq2TzCymLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugStjdf9htoLX2hWtnfOYGhjXK3cxcnJICJhI vD61lKWLkYtDSGA9o8TNPTeZIZzljBKLN95mAakSFsiQaHnZxQhiiwhYS7xccQqqYwKrxMHl q8ESbAIWEjd/NLKB2LwC9hIr9vSDNbMIqEps77sJViMqECNx/dkjqBpBiZMzn4DVcAo4SLya fogdxGYGmjNz/nlGCFteonnrbGYQW0hAW6KhqYN1AiP/LCTts5C0zELSsoCReRWjaHFqcVJu upGxXmpRZnJxcX6eXl5qySZGYAge3PJbdQfj5TeOhxgFOBiVeHgfvGGPEGJNLCuuzD3EKMHB rCTCe/chZ4QQb0piZVVqUX58UWlOavEhRmkOFiVxXrOV98OFBNITS1KzU1MLUotgskwcnFIN jNnzT8RksoV8SNutGahq4porvKz/5VWdHNZHGnn7zR2y7y50ur//yN8JhSINjz6ZuW72czxr tkFnzrUSs/XF14Lzzk+3X/Vax19L9/6KCR8yNrJ8vbD/1KdLocsO7D58adUTptX1jG9rJYW9 Ar8tjY1ZwdCVkeE7b2fpynuMqkce7Hs1J2p1n6YSS3FGoqEWc1FxIgA7zXaqPQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/y7EC8nO6LQYqsh2q8_r-Fjw5xRE>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - RTP demux - Pull Request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Oct 2016 09:46:25 -0000

Den 2016-10-20 kl. 18:40, skrev Paul Kyzivat:
> On 10/20/16 7:43 AM, Magnus Westerlund wrote:
>
>> I currently fail to see that the above discussion changes what needs to
>> be done. Yes, SDP's description of RTP is not optimally structured, but
>> that we can't change. We also have the agreement that one m= should
>> describe one Media Source, thus we simply have to describe how this is
>> accomplished, despite the fact that one needs to consider both RTP
>> session and the set of RTP streams associated with a media source that
>> on sends as well as the RTP streams one is willing to receive.
>
> IMO the issue is to sort out different levels of abstraction and layering.
>
> SDP media descriptions are not fundamentally about RTP streams, they are
> about something more general. A whole variety of different sorts of
> connections/associations can be described using media descriptions. Some
> describe a single stream, some describe multiple streams. When they
> describe multiple streams, they have differing nomenclature for talking
> about and denoting those streams. SSRC is meaningful only for RTP. So
> SSRC, or RTP stream, are not terms that ought to be fundamentally
> involved in defining the meaning/function of SDP or BUNDLE. (OTOH, they
> certainly can be considered as part of a discussion of specializing the
> media description for RTP-based media descriptions.)
>
> It might be helpful to conceptualize this in terms of superclasses and
> subclasses. MediaDescription is a base class. A Bundle is a collection
> of MediaDescriptions, but not all MediaDescriptions are bundleable -
> there are some constraints that must be satisfied.
>
> The key feature of a bundle is that all the contained MediaDescriptions
> must share a 5-tuple. The protocol part of the 5-tuple is itself a bit
> tricky, in that we don't require them to have identical m-line <proto>
> fields. Instead, we only require them to share some lower level part of
> the stack of protocols in each of the bundled m-lines. In particular
> DTLS over UDP or DTLS over TCP. (And this is further complicated by ICE,
> but that is a separate discussion.)
>
> The next most significant constraint is that all the data received via
> the 5-tuple must be able to be disambiguated by the receiver regarding
> which MediaDescription(s) it applies to. My attempt to describe that as
> classifying *packets* turns out to be an over-simplification.
>
> The actual classification probably needs to be layered. If the common
> protocol to all the bundled MediaDescriptions is packet-oriented, then
> that is where classification can start. Consider a bundle including RTP,
> RTCP, and SCTP: the first level of classification will be to classify
> the packet as one of those. If there is a single SCTP MediaDescription
> in the bundle then that will be enough to associate SCTP packets with
> that one. If there are multiple RTP MediaDescriptions then RTP and RTCP
> packets need further analysis. The RTCP packets are complicated, as has
> been discussed previously. I still have the sense that RTP packets can
> be classified to a single MediaDescription, but my understanding is
> limited so I am prepared to be wrong about that.

Yes, you are making it unnecessary complicated because you try to 
interpret RTP packets without considering the RTP stack implementation 
and the work it should do. From my perspective, the SDP needs to be able 
to establish the lower layer filter to be able to dispatch the packets 
to the right RTP stack instance. That is one or more 5-tuples combined 
with a protocol filter, i.e. is this RTP.

Then the RTP stack does it work. And that is particular important to 
consider in the RTCP case. At the end, the RTP stack delivers media data 
associated with RTP streams. It provides meta data, feedback messages 
etc related to that stream. It doesn't need at all to present a raw 
packet, only the information. That higher layer API deliver its data to 
the related application consumer.

>
> The bottom line is that much of this isn't part of the general bundle
> mechanism. It is specific to the specialization of bundle to RTP. That
> does need to be written down *somewhere*. It could be part of the bundle
> draft, as a subsection specific to RTP. Or it could be in some other
> document.

My question to you Paul, what is your view on the latest proposal from 
Christer (yesterday). Is that insufficient, just enough, to detailed, or 
simply not the right thing?

I do think it is good enough.

I promised, and will do an attempt to provide text for the simulcast 
case regarding what type of RTP packet behaviors that is expected to 
occur out from sender, handling in middlebox, and arriving at a 
receiver. Yes, this is not Bundle specific, even if BUNDLE can occur and 
thus needs to be considered. But it is a case which will have multiple 
RTP streams under one SDP media description. Our initial target for this 
text is the MMUSIC simulcast draft. But, I know there is only one more 
week to write it.

cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Fri Oct 21 02:53:02 2016
Return-Path: <magnus.westerlund@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 1CF621295E9 for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 02:53:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 qMKZ5p2D9yrl for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 02:52:59 -0700 (PDT)
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 0489C1295A5 for <mmusic@ietf.org>; Fri, 21 Oct 2016 02:52:58 -0700 (PDT)
X-AuditID: c1b4fb30-b73ff70000000cb2-98-5809e578bc03
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by  (Symantec Mail Security) with SMTP id E0.4A.03250.875E9085; Fri, 21 Oct 2016 11:52:57 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.62) with Microsoft SMTP Server id 14.3.319.2; Fri, 21 Oct 2016 11:52:56 +0200
To: Adam Roach <adam@nostrum.com>, Flemming Andreasen <fandreas@cisco.com>, mmusic <mmusic@ietf.org>
References: <105f1c1e-63b0-e250-663f-b8981bad960e@cisco.com> <70816640-d76a-c84d-e0f8-9baf820d943b@nostrum.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <ed77b9dd-a004-b816-5226-428760cf97e9@ericsson.com>
Date: Fri, 21 Oct 2016 11:52:55 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <70816640-d76a-c84d-e0f8-9baf820d943b@nostrum.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHLMWRmVeSWpSXmKPExsUyM2K7jW7lU84Ig1mXJS32/F3EbvH+gq7F 1OWPWRyYPab83sjqsWTJTyaPWTufsAQwR3HZpKTmZJalFunbJXBlzNl6ka2gy6hi993XLA2M WzS6GDk5JARMJM4c+8gIYgsJrGeU+D6Fr4uRC8hezijRuraLGSQhLGAssWPhVxYQW0QgTeLO +Q0sEA2FEke+fQNrZhOwkLj5o5ENxOYVsJdYcvgwmM0ioCpxYMkxdhBbVCBG4vqzR1A1ghIn Zz4BmsPBwQlUP+dQFIjJDGQ+2FoGUsEsIC/RvHU2M8QmbYmGpg7WCYz8s5A0z0LomIWkYwEj 8ypG0eLU4qTcdCMjvdSizOTi4vw8vbzUkk2MwFA8uOW3wQ7Gl88dDzEKcDAq8fA+eMMeIcSa WFZcmXuIUYKDWUmE1xgYyEK8KYmVValF+fFFpTmpxYcYpTlYlMR5zVbeDxcSSE8sSc1OTS1I LYLJMnFwSjUwahj8N1u2ydRN4ZFJxxTuDDN/ca0LN6a4zOh7KqFw7MGb+T6/PvffUGde+Tft 94qiq5XWe8/ZZ73PusFvdm77oblNJbedasRf5j2fG/vsYJ6WSexTRfvTGfMjjeqdlVsSb+55 w3zxR8Z347ADGwqKhAymPlywwHxlY1VTxE8fv4iA+fNcVry2UmIpzkg01GIuKk4EAL062ulB AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ROrMYo90aKtcabk9O_xxzeIEIL8>
Subject: Re: [MMUSIC] Simulcast draft review needed
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Oct 2016 09:53:01 -0000

Thanks Adam,

We will work on a update to meet the deadline where we will make our 
best to incorporate your feedback. My read through indicates that they 
are reasonable comments. And first after having thought through them and 
attempted implementing them will I know if there some issues with them. 
So a follow up after implementing the changes.

Cheers

Magnus

Den 2016-10-20 kl. 01:12, skrev Adam Roach:
> On 9/22/16 18:44, Flemming Andreasen wrote:
>> Please note that we also have the simulcast draft
>>
>> https://www.ietf.org/id/draft-ietf-mmusic-sdp-simulcast-05.txt
>>
>> to go along with this, and we really need some reviews of that one
>> too. If you have some time to review it, please do so and send your
>> comments to the list (incl. "looks good").
>
> I'm one of the dedicated volunteers who agreed to review this document.
> I apologize for the delay in providing feedback.
>
> In general, this document looks to be in really good shape. I have a
> handful of comments, some editorial, and some minor technical. I don't
> see any major technical issues. The largest issue I have is that one of
> the examples contravenes the recommendations in avtext-rid, and is
> consequently likely to cause interop failures.
>
>
> Technical:
>
> Section 4, REQ-1.2 -- it's not clear to me how this requirement is met.
> The current mechanism does not allow implementations to determine which
> streams are part of a single simulcast media source by looking at the
> RTP/RTCP in isolation. The SDP must be used in concert with the RTP/RTCP
> information. This requirement needs to be either removed or clarified.
>
> Section 6.3.2, paragraph 3, states: "The answerer MUST NOT add any
> alternative SCID that were not present in the offer." This seems like an
> odd restriction on SCID in the send direction. It is not reasonable for
> the offerer to know how many Simulcast Formats a single Simulcast Stream
> that the other end can send might be expressed in. Functionally, this is
> the same as saying that the offerer gets to choose how many PTs the
> answer is allowed to contain, which is a new (and presumably
> unnecessary) restriction. The minimal change to fix this issue would be
> to add "in the receive direction" to the sentence I quote.
>
> I'm sure the conversation happened after -05 was published, but to make
> sure it doesn't get lost: we're not supporting declarative use, so
> section 6.4 should be removed.
>
> The most complicated SDP example (Figure 6, on page 20) uses
> nonoverlapping RIDs for the two different video media sections. This
> implies that the RID space is globally unique in some way. In practice,
> RIDs are scoped to be unique only within a single media section.
> Implementors are likely to incorrectly infer from this example that RIDs
> need to be unique even between media sections, which can lead to interop
> failures. Please adjust the example so that the RIDs in the second media
> section start over at 1 rather than resuming where the first video
> section left off.
>
>
> Editorial:
>
> In the terminology section, the second sentence of the definition of
> Simulcast Streams (starting "Decoding a dependent stream...") is
> difficult to parse and difficult to understand. Assuming I did
> eventually understand what it's saying, I don't think it necessary or
> helpful, and can probably be removed rather than fixed.
>
> The first comma in the definition of Simulcast Format should be a colon.
>
> Section 3 should also mention the use case in which the media switch
> does not have access to the media contents, as in the type of
> conferences that PERC is being designed for.
>
> Section 3.2 should contain commas around the phrase "for example" in the
> second sentence of the first paragraph.
>
> The prose in section 6.1 seems to suffer from the lack of a formal term
> for the construct that the ABNF calls "sc-alt-list." For example, the
> third paragraph says "each SCID is separated by a semicolon." That's
> inaccurate and confusing: the syntax clearly indicates that SCIDs are
> indicated by commas, and the "sc-alt-list" construct is separated by
> semicolons. I think the smallest change we can make to fix this is to
> say "each _stream_ is separated by as semicolon", but that's a bit
> unsatisfying. I think it would be better to define an English term for
> this "sc-alt-list" thing and use it where appropriate.
>
> This missing terminology shows up again in the fourth paragraph of
> section 6.2: the construct "The number of (non-alternative, see above)
> SCID..." is awkward and hard to follow. If we define a term that means
> this "sc-alt-list" thing, it should be used here. If we don't, then I
> again suggest using the term "stream" rather than "(non-alternative, see
> above) SCID".
>
> In the seventh paragraph of section 6.2 (starting "A simulcast
> stream..."), the sentence "...such 'related' formats MUST NOT be defined
> as SCID and listed..." needs to have something like "having their own"
> inserted, to read: "...such 'related' formats MUST NOT be defined as
> having their own SCID and listed..."
>
> The following paragraph contains a sentence fragment that can be turned
> into a sentence by changing "...each of which can be individually
> prefixed..." to "...each can be individually prefixed..."
>
> The final paragraph of section 6.3.2 contains a comma preceded by a
> space. This comma should be removed.
>
> Section 8 should clearly indicate that the technique described in the
> third paragraph is out of scope for this document, and that additional
> specification would be necessary to implement simulcast in a multicast
> context.
>
> /a
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Fri Oct 21 07:54:09 2016
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 305E9129529 for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 07:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RlIOGYUGDNp4 for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 07:54:06 -0700 (PDT)
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 D0C9512943E for <mmusic@ietf.org>; Fri, 21 Oct 2016 07:54:05 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-a6-580a2c0b4ece
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by  (Symantec Mail Security) with SMTP id 75.F1.02551.B0C2A085; Fri, 21 Oct 2016 16:54:04 +0200 (CEST)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.75) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 21 Oct 2016 16:54:03 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=UmAFhfvMgyXHtb1CdmDRh3/rRaUsV/+3iEEb5GRDneM=; b=ITCU3+dKNCa7JsvXw0DaFlqogwgnamOddumqf8NkKTUTsk2dTQjCwTMFNd0Oq2qcMGofXmzsC0//5teO1UkDG+QTARAmALP9SSJwJFDAa5rbqtlIYJ9JUy3A/yfwJGSqTSErzmoVoDLqBjm2zRy5+wRwkF742J4DlcEPQGLAvp4=
Received: from AM5PR0701MB2577.eurprd07.prod.outlook.com (10.173.92.21) by AM5PR0701MB2577.eurprd07.prod.outlook.com (10.173.92.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.679.5; Fri, 21 Oct 2016 14:54:02 +0000
Received: from AM5PR0701MB2577.eurprd07.prod.outlook.com ([10.173.92.21]) by AM5PR0701MB2577.eurprd07.prod.outlook.com ([10.173.92.21]) with mapi id 15.01.0679.006; Fri, 21 Oct 2016 14:54:02 +0000
From: Bo Burman <bo.burman@ericsson.com>
To: "mmusic (mmusic@ietf.org)" <mmusic@ietf.org>
Thread-Topic: Agenda requests for IETF 97
Thread-Index: AdIrqfGh5WqKdM8uQS2lbeNWMYwAgA==
Date: Fri, 21 Oct 2016 14:54:02 +0000
Message-ID: <AM5PR0701MB25777F52531523C2870F0B1A8DD40@AM5PR0701MB2577.eurprd07.prod.outlook.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=bo.burman@ericsson.com; 
x-originating-ip: [83.209.205.79]
x-ms-office365-filtering-correlation-id: c0f5b065-8706-4178-d3d1-08d3f9c21918
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB2577; 7:TG5OCRlvxCx/AndbbRAIDvW0D4Ab7kR3N0es3PVwPHpO2RfQpncUGbqMCSqz+37lHIlgKMwzNkO7U5k1jyGT6Lwo0cElwxHpvlcKssEkC7hniHYCi8wIK9/SEmgmrZZxKp5E3hN9XS9H5kUpA7Yb7cmmN1U/SJGmJf/pe3cKqUGEDTB057rg9xPhlAVtO7Oi7l8tssQhuaL+xegIn7o4At/HoM/m1sB26Pfhwq6akgl5jrCHzBvTu+ro2arx/FvZWh7dHaLBKbG1KrFIp5T1GlTWKQqzS55LXZTPWthsSmrFbkorcfeplClQE1oUTIMkXMNZhMPgCSilSM2tNsimIXVXdpTJCQ8RjPlfbcj5Y3k=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM5PR0701MB2577;
x-microsoft-antispam-prvs: <AM5PR0701MB25778C3E63FF20FB45D3E3358DD40@AM5PR0701MB2577.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046);  SRVR:AM5PR0701MB2577; BCL:0; PCL:0; RULEID:; SRVR:AM5PR0701MB2577; 
x-forefront-prvs: 01026E1310
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(199003)(189002)(5002640100001)(9686002)(76576001)(11100500001)(10400500002)(110136003)(19625215002)(33656002)(106356001)(7696004)(68736007)(7846002)(16236675004)(15975445007)(87936001)(97736004)(5660300001)(19609705001)(86362001)(189998001)(2900100001)(107886002)(101416001)(9326002)(74316002)(558084003)(8936002)(586003)(7736002)(122556002)(450100001)(77096005)(790700001)(19300405004)(105586002)(8676002)(229853001)(2906002)(81156014)(6916009)(81166006)(66066001)(3846002)(3660700001)(6116002)(50986999)(102836003)(92566002)(3280700002)(19580395003)(54356999); DIR:OUT; SFP:1101; SCL:1; SRVR:AM5PR0701MB2577; H:AM5PR0701MB2577.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM5PR0701MB25777F52531523C2870F0B1A8DD40AM5PR0701MB2577_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Oct 2016 14:54:02.8510 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2577
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHKsWRmVeSWpSXmKPExsUyM2K7ty6PDleEwZw3zBZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxqFDpgWbxCr2z/7P2sD4WLiLkZNDQsBEonVBC2MXIxeHkMB6 Rontf1YwQzgnGCUeHJzIBuKwCPQyS+y//IgVIjOdSeLcqQsIZYtnzGEFGcYmoCExf8ddRhBb RMBAYvbKGWC2sICKxP1vf4AaOIDimhKvl+tBlOhJbN/0CayERUBV4tiaq+wgNq9AgsTJt4dZ QGxGATGJ76fWMIHYzALiEreezGeCuFtAYsme88wQtqjEy8f/WCHqIyUmTzzLDhFXlOg6uQOq 3ldi3uYzYDdLCCxilrizcC8rRMJD4uOiZ6wgt0kI5Ev8bHCDCFtJdEw8zgpRv4dRYs2ky1DL ZCR+/p4KlWhik/jZtQrsAyGBVInla1uhHpaSuHulE8qWkXhxB2IZM9CCSzc3sUF8KShxcuYT lgmMarOQPDcLSdksJGUQcR2JBbs/sUHY2hLLFr5mhrHPHHjMhCy+gJF9FaNocWpxcW66kbFe alFmcnFxfp5eXmrJJkZgqjm45bfuDsbVrx0PMQpwMCrx8CbIc0UIsSaWFVfmHmKU4GBWEuGt 1QAK8aYkVlalFuXHF5XmpBYfYpTmYFES5zVbeT9cSCA9sSQ1OzW1ILUIJsvEwSnVwGjLq/TY 0X9jozy/7p6NR0tbNKs2H1rxRuf6tumhor33VOdG/a3USVtskFx9brvhvK+l8wuC7u0u3Z5e OLuh8689m8m/FtezLtlF4V4fSnsWSjw6VdB6g22V2pNHsw5wRHN8l1xzZVcp44e+/t2zM5gT Wcx4uae5R+dm9bIdMVj6YfUltrzmeUosxRmJhlrMRcWJAJUrW0AxAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/6_-DzFQ6DP_XKJf3cGoBESZ6uCw>
Subject: [MMUSIC] Agenda requests for IETF 97
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Oct 2016 14:54:08 -0000

--_000_AM5PR0701MB25777F52531523C2870F0B1A8DD40AM5PR0701MB2577_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

The preliminary agenda deadline is in just over a week and the chairs did n=
ot receive any agenda requests yet.
Please send your requests to the chairs and/or to the list.

Bo & Flemming
MMUSIC chairs


--_000_AM5PR0701MB25777F52531523C2870F0B1A8DD40AM5PR0701MB2577_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"SV">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"SV"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">The preliminary agenda deadline is in just over a we=
ek and the chairs did not receive any agenda requests yet.<o:p></o:p></p>
<p class=3D"MsoNormal">Please send your requests to the chairs and/or to th=
e list.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Bo &amp; Flemming<o:p></o:p></p>
<p class=3D"MsoNormal">MMUSIC chairs<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_AM5PR0701MB25777F52531523C2870F0B1A8DD40AM5PR0701MB2577_--


From nobody Fri Oct 21 08:21:58 2016
Return-Path: <fluffy@iii.ca>
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 7A1DB129611 for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 08:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bbL2kh5xrMPL for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 08:21:56 -0700 (PDT)
Received: from smtp98.iad3a.emailsrvr.com (smtp98.iad3a.emailsrvr.com [173.203.187.98]) (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 08E05129608 for <mmusic@ietf.org>; Fri, 21 Oct 2016 08:21:56 -0700 (PDT)
Received: from smtp5.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp5.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 4C77DE0137; Fri, 21 Oct 2016 11:21:55 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp5.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id F19B5E013A;  Fri, 21 Oct 2016 11:21:54 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.253] (d75-159-45-76.abhsia.telus.net [75.159.45.76]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.7); Fri, 21 Oct 2016 11:21:55 -0400
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <563ec9e6-15eb-49bf-0527-9c068ab1b329@cisco.com>
Date: Fri, 21 Oct 2016 09:21:53 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <E72A6E7D-5B71-4C16-8322-4EFAC9031DBB@iii.ca>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <563ec9e6-15eb-49bf-0527-9c068ab1b329@cisco.com>
To: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Apple Mail (2.3226)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/eR0YTfn10kPwMcjSAAF5755uaGM>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Rough concensus: Re: 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Oct 2016 15:21:57 -0000

I think that is a bad way to run a WG. All I asked for was a phone call =
to discuss this so we could get the issues on the table and discuss what =
is best. The chairs never even replied to my request for a WG call to =
discuss this. The list discussions that ensued from this resulted in =
people other than me sugesting possibilities that were much better than =
any of the three below -  none of which were considered in your =
consensus call.=20

I don=E2=80=99t plan to appeal this but I am considering if it=E2=80=99s =
worth my time to participate in this WG if we are not going to be =
willing to actually spend a short time to discuss possible solutions =
before taking a consensus call.  As input to that decisions, it would be =
really useful to know why you refused to have a phone call on this topic =
and what your policy in general is going to be toward discussions of =
proposed solutions to problems in the future.=20


> On Oct 19, 2016, at 6:43 AM, Flemming Andreasen <fandreas@cisco.com> =
wrote:
>=20
> Hi
>=20
> Following up on the consensus call, we have received 5 responses in =
favor of option a) below, one neutral, and one objection. Looking at the =
document we have noted that backwards compatibility is handled by the =
current text in the document and it also clearly states that it does not =
make current RFC 4572 implementation non-compliant with RFC 4572. Since =
we have not heard of any technical problems with proposal a), nor seen =
any tangible progress on how to address the objection, we are hereby =
declaring rough consensus on option a). We will proceed with the =
publication request for the current draft while duly noting the =
"roughness" of the consensus based on the pending objection as part of =
this.
>=20
> Thanks
>=20
>    Flemming & Bo (MMUSIC chairs)
>=20
>=20
> On 10/12/16 6:23 PM, Flemming Andreasen wrote:
>> Greetings
>>=20
>> There has been quite a bit of discussion on =
draft-ietf-mmusic-4572-update (currently -07), which had previously =
completed WGLC when a few concerns were raised. The document currently:
>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
>> 2. Updates the preferred cipher-suite with a stronger cipher suite
>> 3. Updates RFC 4572.
>>=20
>> Item 1 seems to be generally agreeable, whereas items 2 and 3 are =
not. The chairs are hereby soliciting WG feedback on how to proceed =
based on the following choices:
>>=20
>> a) Proceed with publication of 4572-update-07 in its current form =
(i.e. covering all 3 items above)
>>=20
>> b) Remove item 2 from 4572-update, i.e. do not update the preferred =
cipher-suite
>>=20
>> c) Remove item 3 from 4572-update, i.e. do not indicate that this =
document constitutes an update to RFC 4572.
>>=20
>>=20
>> Note that choice a) is mutually exclusive with b) and c), but b) and =
c) are not mutually exclusive.
>>=20
>> Please let us know your preference wrt to the above no later than =
Friday October 14th.
>>=20
>>=20
>> Thanks
>>=20
>>       Flemming & Bo (MMUSIC chairs)
>>=20
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>> .
>>=20
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Fri Oct 21 08:59:58 2016
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 7E70112940B for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 08:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.952
X-Spam-Level: 
X-Spam-Status: No, score=-14.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 ynpWyRcn00dA for <mmusic@ietfa.amsl.com>; Fri, 21 Oct 2016 08:59:55 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDD90129438 for <mmusic@ietf.org>; Fri, 21 Oct 2016 08:59:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4836; q=dns/txt; s=iport; t=1477065595; x=1478275195; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=KUIAe9mjcz/8JNy6pRKlnLDe1dIytnC46OGrgJdEEUY=; b=kbhG9AsiVBplzVh6Tk0YsZDjuCoEc+AR9pjHPWLhPmiMTiMFC67yxKWw 5irtq/8vOpKFwZI8uqVuzARccwDOgRaO2SH8ObC+f3A/5l6Y067u+xDC/ RYKMKBPinNiA68XY/CWYz36EBimHnfg1lHiCJuHPjESaXm02Dy1vWnNI6 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AkAQCBOgpY/5BdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgz4BAQEBAR1XKlONNJZ9lD6CBxwLhTBKAoFnPxQBAgEBAQEBAQF?= =?us-ascii?q?iKIRiAQEBAwEBAQEgDwEFNgsFCwsOCgICJgICJzAGDQYCAQEXiC8IDrYjjQIBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEaBYEHhTaBfYFTgQWHS4JbBYYlk26MNYNbgW6EbYM?= =?us-ascii?q?WhhCHFIVuhAAeNlmDRYFWIjSISAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.31,377,1473120000"; d="scan'208";a="160172285"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Oct 2016 15:59:54 +0000
Received: from [10.98.149.200] (bxb-fandreas-8817.cisco.com [10.98.149.200]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u9LFxrk8022439; Fri, 21 Oct 2016 15:59:54 GMT
To: Cullen Jennings <fluffy@iii.ca>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <563ec9e6-15eb-49bf-0527-9c068ab1b329@cisco.com> <E72A6E7D-5B71-4C16-8322-4EFAC9031DBB@iii.ca>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <7a195676-67e0-d670-356c-101ef45da49a@cisco.com>
Date: Fri, 21 Oct 2016 11:59:53 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <E72A6E7D-5B71-4C16-8322-4EFAC9031DBB@iii.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/KNPNSF5bNXrVRdLrNWvDEHUk2gE>
Cc: rai-ads <rai-ads@tools.ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Rough concensus: Re: 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Oct 2016 15:59:57 -0000

On 10/21/16 11:21 AM, Cullen Jennings wrote:
> I think that is a bad way to run a WG. All I asked for was a phone call to discuss this so we could get the issues on the table and discuss what is best. The chairs never even replied to my request for a WG call to discuss this.
That is simply not true. You (and Christer) were explicitly asked to 
setup a phone call on 10/6/16 to discuss this issue; a request that 
(like many other others) went unanswered or required extensive prodding 
to get any attention.

> The list discussions that ensued from this resulted in people other than me sugesting possibilities that were much better than any of the three below -  none of which were considered in your consensus call.
I'm not sure what those proposals are, nor were they brought up in 
response to the consensus call.

> I donâ€™t plan to appeal this but I am considering if itâ€™s worth my time to participate in this WG if we are not going to be willing to actually spend a short time to discuss possible solutions before taking a consensus call.  As input to that decisions, it would be really useful to know why you refused to have a phone call on this topic and what your policy in general is going to be toward discussions of proposed solutions to problems in the future.
My position is that we will try our very best to get to not only 
consensus but to satisfy as many concerns as we possibly can. It does 
however require people to engage in a timely manner, and even when they 
don't, we still do what we can, but at some point we need to move 
forward. As for the issue at hand, it has been discussed extensively, 
and several changes were made to the draft to try and accommodate your 
requests.

The one major remaining issue I believe you have is around whether this 
document updates RFC 4572. This has been discussed extensively on the 
wgchairs list; a discussion I initiated to try and help address your 
concern. You may disagree with how that discussion concluded, but again, 
to try and alleviate your concerns, a note was added to 4572-update to 
make it clear that the document does not make existing 4572 
implementations non-compliant with RFC 4572.

I believe the chairs, authors, and the WG at large has done everything 
that can reasonably be done to try and address your concerns, and at 
this point we need to move forward.

Thanks

-- Flemming (as MMUSIC co-chair)



>
>> On Oct 19, 2016, at 6:43 AM, Flemming Andreasen <fandreas@cisco.com> wrote:
>>
>> Hi
>>
>> Following up on the consensus call, we have received 5 responses in favor of option a) below, one neutral, and one objection. Looking at the document we have noted that backwards compatibility is handled by the current text in the document and it also clearly states that it does not make current RFC 4572 implementation non-compliant with RFC 4572. Since we have not heard of any technical problems with proposal a), nor seen any tangible progress on how to address the objection, we are hereby declaring rough consensus on option a). We will proceed with the publication request for the current draft while duly noting the "roughness" of the consensus based on the pending objection as part of this.
>>
>> Thanks
>>
>>     Flemming & Bo (MMUSIC chairs)
>>
>>
>> On 10/12/16 6:23 PM, Flemming Andreasen wrote:
>>> Greetings
>>>
>>> There has been quite a bit of discussion on draft-ietf-mmusic-4572-update (currently -07), which had previously completed WGLC when a few concerns were raised. The document currently:
>>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
>>> 2. Updates the preferred cipher-suite with a stronger cipher suite
>>> 3. Updates RFC 4572.
>>>
>>> Item 1 seems to be generally agreeable, whereas items 2 and 3 are not. The chairs are hereby soliciting WG feedback on how to proceed based on the following choices:
>>>
>>> a) Proceed with publication of 4572-update-07 in its current form (i.e. covering all 3 items above)
>>>
>>> b) Remove item 2 from 4572-update, i.e. do not update the preferred cipher-suite
>>>
>>> c) Remove item 3 from 4572-update, i.e. do not indicate that this document constitutes an update to RFC 4572.
>>>
>>>
>>> Note that choice a) is mutually exclusive with b) and c), but b) and c) are not mutually exclusive.
>>>
>>> Please let us know your preference wrt to the above no later than Friday October 14th.
>>>
>>>
>>> Thanks
>>>
>>>        Flemming & Bo (MMUSIC chairs)
>>>
>>> _______________________________________________
>>> 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 Fri Oct 21 09:05:55 2016
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 3E8D0129667; Fri, 21 Oct 2016 09:05:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.952
X-Spam-Level: 
X-Spam-Status: No, score=-14.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 bhh7cfwfl7ch; Fri, 21 Oct 2016 09:05:53 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 826D312963F; Fri, 21 Oct 2016 09:05:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5356; q=dns/txt; s=iport; t=1477065953; x=1478275553; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=5769v0upJ/L4QT/blZf3ELmM5tPBEfQh5HON7n+s9oA=; b=MRht8ojJa08ajjJl3uad1X4haotmYOrZBubEbjb/d3KV8lW6brfJno4y OyvKfSSb+3KgwRFBlTGuZD0hWY70YZaCx7J63bIm9An4cG4taSgps9TLr YZUbed8zg3pEz4i989N4CH7bi11t26nFL/KN4qjd0Sr/FIN2fqfchogOu I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CCAQB5PApY/40NJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgz4BAQEBAR1XKlONNJZ9lD6CBxwLhTBKAoFnPxQBAgEBAQEBAQFiKIR?= =?us-ascii?q?jAQEEAQEBIA8BBTYLEAsOCgICJgICJzAGDQYCAQEXiDcOtiKNAgEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBARoFgQeFNoF9gVOBBYdLglsBBIYlk26MNYNbgW6EbYMWhhCHFIV?= =?us-ascii?q?uhAAeNlmDRYFWIjSISAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.31,377,1473120000"; d="scan'208";a="162351830"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Oct 2016 16:05:32 +0000
Received: from [10.98.149.200] (bxb-fandreas-8817.cisco.com [10.98.149.200]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u9LG5Vst007254; Fri, 21 Oct 2016 16:05:32 GMT
To: Cullen Jennings <fluffy@iii.ca>
References: <3fcd2bc9-e96a-1269-4418-42be6a16dba8@cisco.com> <563ec9e6-15eb-49bf-0527-9c068ab1b329@cisco.com> <E72A6E7D-5B71-4C16-8322-4EFAC9031DBB@iii.ca> <7a195676-67e0-d670-356c-101ef45da49a@cisco.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <d1304b0f-5efc-fd70-4c4d-f80941e843cd@cisco.com>
Date: Fri, 21 Oct 2016 12:05:31 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <7a195676-67e0-d670-356c-101ef45da49a@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/hofA-h0PqRl3K9sYFC5S0deHnNo>
Cc: ART ADs <art-ads@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Rough concensus: Re: 4572-update: Consensus call on how to move forward
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Oct 2016 16:05:55 -0000

[fixing cc-list]

On 10/21/16 11:59 AM, Flemming Andreasen wrote:
>
>
> On 10/21/16 11:21 AM, Cullen Jennings wrote:
>> I think that is a bad way to run a WG. All I asked for was a phone 
>> call to discuss this so we could get the issues on the table and 
>> discuss what is best. The chairs never even replied to my request for 
>> a WG call to discuss this.
> That is simply not true. You (and Christer) were explicitly asked to 
> setup a phone call on 10/6/16 to discuss this issue; a request that 
> (like many other others) went unanswered or required extensive 
> prodding to get any attention.
>
>> The list discussions that ensued from this resulted in people other 
>> than me sugesting possibilities that were much better than any of the 
>> three below -  none of which were considered in your consensus call.
> I'm not sure what those proposals are, nor were they brought up in 
> response to the consensus call.
>
>> I donâ€™t plan to appeal this but I am considering if itâ€™s worth my 
>> time to participate in this WG if we are not going to be willing to 
>> actually spend a short time to discuss possible solutions before 
>> taking a consensus call.  As input to that decisions, it would be 
>> really useful to know why you refused to have a phone call on this 
>> topic and what your policy in general is going to be toward 
>> discussions of proposed solutions to problems in the future.
> My position is that we will try our very best to get to not only 
> consensus but to satisfy as many concerns as we possibly can. It does 
> however require people to engage in a timely manner, and even when 
> they don't, we still do what we can, but at some point we need to move 
> forward. As for the issue at hand, it has been discussed extensively, 
> and several changes were made to the draft to try and accommodate your 
> requests.
>
> The one major remaining issue I believe you have is around whether 
> this document updates RFC 4572. This has been discussed extensively on 
> the wgchairs list; a discussion I initiated to try and help address 
> your concern. You may disagree with how that discussion concluded, but 
> again, to try and alleviate your concerns, a note was added to 
> 4572-update to make it clear that the document does not make existing 
> 4572 implementations non-compliant with RFC 4572.
>
> I believe the chairs, authors, and the WG at large has done everything 
> that can reasonably be done to try and address your concerns, and at 
> this point we need to move forward.
>
> Thanks
>
> -- Flemming (as MMUSIC co-chair)
>
>
>
>>
>>> On Oct 19, 2016, at 6:43 AM, Flemming Andreasen <fandreas@cisco.com> 
>>> wrote:
>>>
>>> Hi
>>>
>>> Following up on the consensus call, we have received 5 responses in 
>>> favor of option a) below, one neutral, and one objection. Looking at 
>>> the document we have noted that backwards compatibility is handled 
>>> by the current text in the document and it also clearly states that 
>>> it does not make current RFC 4572 implementation non-compliant with 
>>> RFC 4572. Since we have not heard of any technical problems with 
>>> proposal a), nor seen any tangible progress on how to address the 
>>> objection, we are hereby declaring rough consensus on option a). We 
>>> will proceed with the publication request for the current draft 
>>> while duly noting the "roughness" of the consensus based on the 
>>> pending objection as part of this.
>>>
>>> Thanks
>>>
>>>     Flemming & Bo (MMUSIC chairs)
>>>
>>>
>>> On 10/12/16 6:23 PM, Flemming Andreasen wrote:
>>>> Greetings
>>>>
>>>> There has been quite a bit of discussion on 
>>>> draft-ietf-mmusic-4572-update (currently -07), which had previously 
>>>> completed WGLC when a few concerns were raised. The document 
>>>> currently:
>>>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
>>>> 2. Updates the preferred cipher-suite with a stronger cipher suite
>>>> 3. Updates RFC 4572.
>>>>
>>>> Item 1 seems to be generally agreeable, whereas items 2 and 3 are 
>>>> not. The chairs are hereby soliciting WG feedback on how to proceed 
>>>> based on the following choices:
>>>>
>>>> a) Proceed with publication of 4572-update-07 in its current form 
>>>> (i.e. covering all 3 items above)
>>>>
>>>> b) Remove item 2 from 4572-update, i.e. do not update the preferred 
>>>> cipher-suite
>>>>
>>>> c) Remove item 3 from 4572-update, i.e. do not indicate that this 
>>>> document constitutes an update to RFC 4572.
>>>>
>>>>
>>>> Note that choice a) is mutually exclusive with b) and c), but b) 
>>>> and c) are not mutually exclusive.
>>>>
>>>> Please let us know your preference wrt to the above no later than 
>>>> Friday October 14th.
>>>>
>>>>
>>>> Thanks
>>>>
>>>>        Flemming & Bo (MMUSIC chairs)
>>>>
>>>> _______________________________________________
>>>> 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
>> .
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Fri Oct 21 13:50:11 2016
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 BDCBC129855; Fri, 21 Oct 2016 13:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.331
X-Spam-Level: 
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] 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 mInoZk4btNy8; Fri, 21 Oct 2016 13:50:03 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC5AE1296CA; Fri, 21 Oct 2016 13:50:03 -0700 (PDT)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u9LKntLu012404 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 21 Oct 2016 15:49:56 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: "Ben Campbell" <ben@nostrum.com>
To: "Flemming Andreasen" <fandreas@cisco.com>, "Bo Burman" <bo.burman@ericsson.com>, "Cullen Jennings" <fluffy@iii.ca>, "Christer Holmberg" <christer.holmberg@ericsson.com>
Date: Fri, 21 Oct 2016 15:49:55 -0500
Message-ID: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5263)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/kzPdOTIMstKWx0EPk8nNNjOYzOQ>
Cc: ART ADs <art-ads@ietf.org>, mmusic <mmusic@ietf.org>
Subject: [MMUSIC] Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Oct 2016 20:50:05 -0000

Hi Everyone, please accept my apologies for waiting this long to weigh 
in.

I think it's clear that multiple people are not happy with how we got to 
this point. But assigning blame doesn't help us make progress on the 
draft. I propose that we get over that, and instead focus instead on how 
to move forward. Email discussion doesn't seem to be helping. Maybe a 
call will.

Flemming and/or Bo: Can you set up a Doodle poll to get Christer, 
Cullen, and other demonstratively  interested parties on a conference 
call? I will join if at all possible, but don't let scheduling around me 
stop a call from happening.

Thanks!

Ben.

On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:

> [fixing cc-list]
>
> On 10/21/16 11:59 AM, Flemming Andreasen wrote:
>>
>>
>> On 10/21/16 11:21 AM, Cullen Jennings wrote:
>>> I think that is a bad way to run a WG. All I asked for was a phone 
>>> call to discuss this so we could get the issues on the table and 
>>> discuss what is best. The chairs never even replied to my request 
>>> for a WG call to discuss this.
>> That is simply not true. You (and Christer) were explicitly asked to 
>> setup a phone call on 10/6/16 to discuss this issue; a request that 
>> (like many other others) went unanswered or required extensive 
>> prodding to get any attention.
>>
>>> The list discussions that ensued from this resulted in people other 
>>> than me sugesting possibilities that were much better than any of 
>>> the three below -  none of which were considered in your consensus 
>>> call.
>> I'm not sure what those proposals are, nor were they brought up in 
>> response to the consensus call.
>>
>>> I donâ€™t plan to appeal this but I am considering if itâ€™s worth 
>>> my time to participate in this WG if we are not going to be willing 
>>> to actually spend a short time to discuss possible solutions before 
>>> taking a consensus call.  As input to that decisions, it would be 
>>> really useful to know why you refused to have a phone call on this 
>>> topic and what your policy in general is going to be toward 
>>> discussions of proposed solutions to problems in the future.
>> My position is that we will try our very best to get to not only 
>> consensus but to satisfy as many concerns as we possibly can. It does 
>> however require people to engage in a timely manner, and even when 
>> they don't, we still do what we can, but at some point we need to 
>> move forward. As for the issue at hand, it has been discussed 
>> extensively, and several changes were made to the draft to try and 
>> accommodate your requests.
>>
>> The one major remaining issue I believe you have is around whether 
>> this document updates RFC 4572. This has been discussed extensively 
>> on the wgchairs list; a discussion I initiated to try and help 
>> address your concern. You may disagree with how that discussion 
>> concluded, but again, to try and alleviate your concerns, a note was 
>> added to 4572-update to make it clear that the document does not make 
>> existing 4572 implementations non-compliant with RFC 4572.
>>
>> I believe the chairs, authors, and the WG at large has done 
>> everything that can reasonably be done to try and address your 
>> concerns, and at this point we need to move forward.
>>
>> Thanks
>>
>> -- Flemming (as MMUSIC co-chair)
>>
>>
>>
>>>
>>>> On Oct 19, 2016, at 6:43 AM, Flemming Andreasen 
>>>> <fandreas@cisco.com> wrote:
>>>>
>>>> Hi
>>>>
>>>> Following up on the consensus call, we have received 5 responses in 
>>>> favor of option a) below, one neutral, and one objection. Looking 
>>>> at the document we have noted that backwards compatibility is 
>>>> handled by the current text in the document and it also clearly 
>>>> states that it does not make current RFC 4572 implementation 
>>>> non-compliant with RFC 4572. Since we have not heard of any 
>>>> technical problems with proposal a), nor seen any tangible progress 
>>>> on how to address the objection, we are hereby declaring rough 
>>>> consensus on option a). We will proceed with the publication 
>>>> request for the current draft while duly noting the "roughness" of 
>>>> the consensus based on the pending objection as part of this.
>>>>
>>>> Thanks
>>>>
>>>>     Flemming & Bo (MMUSIC chairs)
>>>>
>>>>
>>>> On 10/12/16 6:23 PM, Flemming Andreasen wrote:
>>>>> Greetings
>>>>>
>>>>> There has been quite a bit of discussion on 
>>>>> draft-ietf-mmusic-4572-update (currently -07), which had 
>>>>> previously completed WGLC when a few concerns were raised. The 
>>>>> document currently:
>>>>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
>>>>> 2. Updates the preferred cipher-suite with a stronger cipher suite
>>>>> 3. Updates RFC 4572.
>>>>>
>>>>> Item 1 seems to be generally agreeable, whereas items 2 and 3 are 
>>>>> not. The chairs are hereby soliciting WG feedback on how to 
>>>>> proceed based on the following choices:
>>>>>
>>>>> a) Proceed with publication of 4572-update-07 in its current form 
>>>>> (i.e. covering all 3 items above)
>>>>>
>>>>> b) Remove item 2 from 4572-update, i.e. do not update the 
>>>>> preferred cipher-suite
>>>>>
>>>>> c) Remove item 3 from 4572-update, i.e. do not indicate that this 
>>>>> document constitutes an update to RFC 4572.
>>>>>
>>>>>
>>>>> Note that choice a) is mutually exclusive with b) and c), but b) 
>>>>> and c) are not mutually exclusive.
>>>>>
>>>>> Please let us know your preference wrt to the above no later than 
>>>>> Friday October 14th.
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>        Flemming & Bo (MMUSIC chairs)
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>> .
>>>
>>
>> _______________________________________________
>> 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 Fri Oct 21 16:23:35 2016
Return-Path: <agenda@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 55A70129863; Fri, 21 Oct 2016 16:21:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <mmusic-chairs@ietf.org>, <bo.burman@ericsson.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147709207034.28214.2412414799041124580.idtracker@ietfa.amsl.com>
Date: Fri, 21 Oct 2016 16:21:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/EjQpg3hK1WkEp5jPPIbscwh2k60>
Cc: ben@nostrum.com, mmusic@ietf.org
Subject: [MMUSIC] mmusic - Requested session has been scheduled for IETF 97
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Oct 2016 23:21:10 -0000

Dear Bo Burman,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 

mmusic Session 1 (1:00:00)
    Wednesday, Morning Session II 1110-1210
    Room Name: Studio 4 size: 100
    ---------------------------------------------
    


Request Information:


---------------------------------------------------------
Working Group Name: Multiparty Multimedia Session Control
Area Name: Applications and Real-Time Area
Session Requester: Bo Burman

Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 40
Conflicts to Avoid: 
 First Priority: quic perc tls ice httpbis rtcweb avtcore avtext sipcore dispatch payload core dots sipbrandy
 Second Priority: clue p2psip straw xrblock rmcat stir tram sfc sacm



Special Requests:
  Avoid collision with any QUIC session
---------------------------------------------------------


From nobody Sat Oct 22 06:17:04 2016
Return-Path: <ekr@rtfm.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 197FA1295AF for <mmusic@ietfa.amsl.com>; Sat, 22 Oct 2016 06:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ODJ5pUkqK5vq for <mmusic@ietfa.amsl.com>; Sat, 22 Oct 2016 06:17:01 -0700 (PDT)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 952BE1295B2 for <mmusic@ietf.org>; Sat, 22 Oct 2016 06:17:00 -0700 (PDT)
Received: by mail-yw0-x234.google.com with SMTP id t193so125323496ywc.2 for <mmusic@ietf.org>; Sat, 22 Oct 2016 06:17:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ETxe3ZmJYiVO0GDeRbzvIuMiKtzwtvrISe+Zt7Yi8mI=; b=YDt8JT0hUjQHRHAGOTfyrPIjJPLAo14zv0cUAZF+dUuD0D62JstyMPudtFlflVfvBJ aWBa9Ht5qedCWP9+Q8sa5A6Il8U5ZnWpmPh+w07Q/KNuQIn3KKVv94ozGWpDp0AhifTS q+xP7Tcx7Q9EvsuURBdfnzOh6+yQG7EkXoi2u6t5wD9wsxXogwM1HPLOI+7vLpgT5YtO TPGWz4b/z3m2vDu2xRS3XLyYAtphqjl/YDk5LJK3+z5tmnfKb5uU46LUFoQMBDpeJ/sM NS2/cfMsUHwkvPbjpPFlHrO2bsj4B0zYysUXtz3qd84AIzYElyNsdBJ92hM7UPlk7iZe J7Vg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ETxe3ZmJYiVO0GDeRbzvIuMiKtzwtvrISe+Zt7Yi8mI=; b=IT95vsjBXH5E4O0cWNtaV5erDgXOtsrwwdofcjsOaUD+y2eazb+Wrl1x3vvgBYk/jT 87Mqcko3T0PkVMKp31tgmdrysDA1MEh3jaqUnTO6W5cIOmt+62Wv0tcbBJyHWnTQhm66 aRzJ3yLmq4AmtqsKKL+m3fa7+wI0WqyGzs1czJPkRgg7R1xQleZ51FKq2+JmiwRftFwu dAd1yoIGGlL9lX/FHKeVtUPCzjsEun5W/3SyuypWH/zAhPlcloyKxe5kq8a82vfisX8n QgA/OyJgZzLMxOVS16azYpGUTZFtP/B0XdktuLtwxK94hktlUqI42SLmyRulSOGz5dNo CLEQ==
X-Gm-Message-State: ABUngvco1f471d8nWGk8Ymk8cEc7nOTsSDnadMsjEAHhJmfGIuHeN8/QiU+9g404p8/ZxDlrlo1rfdHf/PwbKg==
X-Received: by 10.129.53.206 with SMTP id c197mr6254048ywa.205.1477142219784;  Sat, 22 Oct 2016 06:16:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.82.210 with HTTP; Sat, 22 Oct 2016 06:16:19 -0700 (PDT)
In-Reply-To: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 22 Oct 2016 06:16:19 -0700
Message-ID: <CABcZeBMkr=WVxY_QGPsBMjbchzwivYFw4S2zukjO27Kn01591w@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=001a11421a264b3496053f73f944
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wDo4c8JrlrvEZEga4M6CjXgC51Y>
Cc: mmusic <mmusic@ietf.org>, ART ADs <art-ads@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Oct 2016 13:17:03 -0000

--001a11421a264b3496053f73f944
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I would be happy to attend such a call.

-Ekr


On Fri, Oct 21, 2016 at 1:49 PM, Ben Campbell <ben@nostrum.com> wrote:

> Hi Everyone, please accept my apologies for waiting this long to weigh in=
.
>
> I think it's clear that multiple people are not happy with how we got to
> this point. But assigning blame doesn't help us make progress on the draf=
t.
> I propose that we get over that, and instead focus instead on how to move
> forward. Email discussion doesn't seem to be helping. Maybe a call will.
>
> Flemming and/or Bo: Can you set up a Doodle poll to get Christer, Cullen,
> and other demonstratively  interested parties on a conference call? I wil=
l
> join if at all possible, but don't let scheduling around me stop a call
> from happening.
>
> Thanks!
>
> Ben.
>
> On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:
>
> [fixing cc-list]
>>
>> On 10/21/16 11:59 AM, Flemming Andreasen wrote:
>>
>>>
>>>
>>> On 10/21/16 11:21 AM, Cullen Jennings wrote:
>>>
>>>> I think that is a bad way to run a WG. All I asked for was a phone cal=
l
>>>> to discuss this so we could get the issues on the table and discuss wh=
at is
>>>> best. The chairs never even replied to my request for a WG call to dis=
cuss
>>>> this.
>>>>
>>> That is simply not true. You (and Christer) were explicitly asked to
>>> setup a phone call on 10/6/16 to discuss this issue; a request that (li=
ke
>>> many other others) went unanswered or required extensive prodding to ge=
t
>>> any attention.
>>>
>>> The list discussions that ensued from this resulted in people other tha=
n
>>>> me sugesting possibilities that were much better than any of the three
>>>> below -  none of which were considered in your consensus call.
>>>>
>>> I'm not sure what those proposals are, nor were they brought up in
>>> response to the consensus call.
>>>
>>> I don=E2=80=99t plan to appeal this but I am considering if it=E2=80=99=
s worth my time
>>>> to participate in this WG if we are not going to be willing to actuall=
y
>>>> spend a short time to discuss possible solutions before taking a conse=
nsus
>>>> call.  As input to that decisions, it would be really useful to know w=
hy
>>>> you refused to have a phone call on this topic and what your policy in
>>>> general is going to be toward discussions of proposed solutions to pro=
blems
>>>> in the future.
>>>>
>>> My position is that we will try our very best to get to not only
>>> consensus but to satisfy as many concerns as we possibly can. It does
>>> however require people to engage in a timely manner, and even when they
>>> don't, we still do what we can, but at some point we need to move forwa=
rd.
>>> As for the issue at hand, it has been discussed extensively, and severa=
l
>>> changes were made to the draft to try and accommodate your requests.
>>>
>>> The one major remaining issue I believe you have is around whether this
>>> document updates RFC 4572. This has been discussed extensively on the
>>> wgchairs list; a discussion I initiated to try and help address your
>>> concern. You may disagree with how that discussion concluded, but again=
, to
>>> try and alleviate your concerns, a note was added to 4572-update to mak=
e it
>>> clear that the document does not make existing 4572 implementations
>>> non-compliant with RFC 4572.
>>>
>>> I believe the chairs, authors, and the WG at large has done everything
>>> that can reasonably be done to try and address your concerns, and at th=
is
>>> point we need to move forward.
>>>
>>> Thanks
>>>
>>> -- Flemming (as MMUSIC co-chair)
>>>
>>>
>>>
>>>
>>>> On Oct 19, 2016, at 6:43 AM, Flemming Andreasen <fandreas@cisco.com>
>>>>> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Following up on the consensus call, we have received 5 responses in
>>>>> favor of option a) below, one neutral, and one objection. Looking at =
the
>>>>> document we have noted that backwards compatibility is handled by the
>>>>> current text in the document and it also clearly states that it does =
not
>>>>> make current RFC 4572 implementation non-compliant with RFC 4572. Sin=
ce we
>>>>> have not heard of any technical problems with proposal a), nor seen a=
ny
>>>>> tangible progress on how to address the objection, we are hereby decl=
aring
>>>>> rough consensus on option a). We will proceed with the publication re=
quest
>>>>> for the current draft while duly noting the "roughness" of the consen=
sus
>>>>> based on the pending objection as part of this.
>>>>>
>>>>> Thanks
>>>>>
>>>>>     Flemming & Bo (MMUSIC chairs)
>>>>>
>>>>>
>>>>> On 10/12/16 6:23 PM, Flemming Andreasen wrote:
>>>>>
>>>>>> Greetings
>>>>>>
>>>>>> There has been quite a bit of discussion on
>>>>>> draft-ietf-mmusic-4572-update (currently -07), which had previously
>>>>>> completed WGLC when a few concerns were raised. The document current=
ly:
>>>>>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
>>>>>> 2. Updates the preferred cipher-suite with a stronger cipher suite
>>>>>> 3. Updates RFC 4572.
>>>>>>
>>>>>> Item 1 seems to be generally agreeable, whereas items 2 and 3 are
>>>>>> not. The chairs are hereby soliciting WG feedback on how to proceed =
based
>>>>>> on the following choices:
>>>>>>
>>>>>> a) Proceed with publication of 4572-update-07 in its current form
>>>>>> (i.e. covering all 3 items above)
>>>>>>
>>>>>> b) Remove item 2 from 4572-update, i.e. do not update the preferred
>>>>>> cipher-suite
>>>>>>
>>>>>> c) Remove item 3 from 4572-update, i.e. do not indicate that this
>>>>>> document constitutes an update to RFC 4572.
>>>>>>
>>>>>>
>>>>>> Note that choice a) is mutually exclusive with b) and c), but b) and
>>>>>> c) are not mutually exclusive.
>>>>>>
>>>>>> Please let us know your preference wrt to the above no later than
>>>>>> Friday October 14th.
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>        Flemming & Bo (MMUSIC chairs)
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>> .
>>>>
>>>>
>>> _______________________________________________
>>> 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
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--001a11421a264b3496053f73f944
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I would be happy to attend such a call.<div><br></div><div=
>-Ekr</div><div><br></div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Fri, Oct 21, 2016 at 1:49 PM, Ben Campbell <span dir=3D=
"ltr">&lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_blank">ben@nostrum.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Everyone, pl=
ease accept my apologies for waiting this long to weigh in.<br>
<br>
I think it&#39;s clear that multiple people are not happy with how we got t=
o this point. But assigning blame doesn&#39;t help us make progress on the =
draft. I propose that we get over that, and instead focus instead on how to=
 move forward. Email discussion doesn&#39;t seem to be helping. Maybe a cal=
l will.<br>
<br>
Flemming and/or Bo: Can you set up a Doodle poll to get Christer, Cullen, a=
nd other demonstratively=C2=A0 interested parties on a conference call? I w=
ill join if at all possible, but don&#39;t let scheduling around me stop a =
call from happening.<br>
<br>
Thanks!<br>
<br>
Ben.<br>
<br>
On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
[fixing cc-list]<br>
<br>
On 10/21/16 11:59 AM, Flemming Andreasen wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
On 10/21/16 11:21 AM, Cullen Jennings wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I think that is a bad way to run a WG. All I asked for was a phone call to =
discuss this so we could get the issues on the table and discuss what is be=
st. The chairs never even replied to my request for a WG call to discuss th=
is.<br>
</blockquote>
That is simply not true. You (and Christer) were explicitly asked to setup =
a phone call on 10/6/16 to discuss this issue; a request that (like many ot=
her others) went unanswered or required extensive prodding to get any atten=
tion.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The list discussions that ensued from this resulted in people other than me=
 sugesting possibilities that were much better than any of the three below =
-=C2=A0 none of which were considered in your consensus call.<br>
</blockquote>
I&#39;m not sure what those proposals are, nor were they brought up in resp=
onse to the consensus call.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I don=E2=80=99t plan to appeal this but I am considering if it=E2=80=99s wo=
rth my time to participate in this WG if we are not going to be willing to =
actually spend a short time to discuss possible solutions before taking a c=
onsensus call.=C2=A0 As input to that decisions, it would be really useful =
to know why you refused to have a phone call on this topic and what your po=
licy in general is going to be toward discussions of proposed solutions to =
problems in the future.<br>
</blockquote>
My position is that we will try our very best to get to not only consensus =
but to satisfy as many concerns as we possibly can. It does however require=
 people to engage in a timely manner, and even when they don&#39;t, we stil=
l do what we can, but at some point we need to move forward. As for the iss=
ue at hand, it has been discussed extensively, and several changes were mad=
e to the draft to try and accommodate your requests.<br>
<br>
The one major remaining issue I believe you have is around whether this doc=
ument updates RFC 4572. This has been discussed extensively on the wgchairs=
 list; a discussion I initiated to try and help address your concern. You m=
ay disagree with how that discussion concluded, but again, to try and allev=
iate your concerns, a note was added to 4572-update to make it clear that t=
he document does not make existing 4572 implementations non-compliant with =
RFC 4572.<br>
<br>
I believe the chairs, authors, and the WG at large has done everything that=
 can reasonably be done to try and address your concerns, and at this point=
 we need to move forward.<br>
<br>
Thanks<br>
<br>
-- Flemming (as MMUSIC co-chair)<br>
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Oct 19, 2016, at 6:43 AM, Flemming Andreasen &lt;<a href=3D"mailto:fandr=
eas@cisco.com" target=3D"_blank">fandreas@cisco.com</a>&gt; wrote:<br>
<br>
Hi<br>
<br>
Following up on the consensus call, we have received 5 responses in favor o=
f option a) below, one neutral, and one objection. Looking at the document =
we have noted that backwards compatibility is handled by the current text i=
n the document and it also clearly states that it does not make current RFC=
 4572 implementation non-compliant with RFC 4572. Since we have not heard o=
f any technical problems with proposal a), nor seen any tangible progress o=
n how to address the objection, we are hereby declaring rough consensus on =
option a). We will proceed with the publication request for the current dra=
ft while duly noting the &quot;roughness&quot; of the consensus based on th=
e pending objection as part of this.<br>
<br>
Thanks<br>
<br>
=C2=A0 =C2=A0 Flemming &amp; Bo (MMUSIC chairs)<br>
<br>
<br>
On 10/12/16 6:23 PM, Flemming Andreasen wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Greetings<br>
<br>
There has been quite a bit of discussion on draft-ietf-mmusic-4572-update (=
currently -07), which had previously completed WGLC when a few concerns wer=
e raised. The document currently:<br>
1. Clarifies the usage of multiple SDP &#39;fingerprint&#39; attributes<br>
2. Updates the preferred cipher-suite with a stronger cipher suite<br>
3. Updates RFC 4572.<br>
<br>
Item 1 seems to be generally agreeable, whereas items 2 and 3 are not. The =
chairs are hereby soliciting WG feedback on how to proceed based on the fol=
lowing choices:<br>
<br>
a) Proceed with publication of 4572-update-07 in its current form (i.e. cov=
ering all 3 items above)<br>
<br>
b) Remove item 2 from 4572-update, i.e. do not update the preferred cipher-=
suite<br>
<br>
c) Remove item 3 from 4572-update, i.e. do not indicate that this document =
constitutes an update to RFC 4572.<br>
<br>
<br>
Note that choice a) is mutually exclusive with b) and c), but b) and c) are=
 not mutually exclusive.<br>
<br>
Please let us know your preference wrt to the above no later than Friday Oc=
tober 14th.<br>
<br>
<br>
Thanks<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Flemming &amp; Bo (MMUSIC chairs)<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
.<br>
<br>
</blockquote>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
.<br>
<br>
</blockquote>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote></div><br></div>

--001a11421a264b3496053f73f944--


From nobody Mon Oct 24 11:44:21 2016
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 4360E1294E2 for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 11:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 LU1MDe-BeSJl for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 11:44:18 -0700 (PDT)
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 A84F71299A1 for <mmusic@ietf.org>; Mon, 24 Oct 2016 11:44:05 -0700 (PDT)
X-AuditID: c1b4fb25-5405a9800000793b-1c-580e56732933
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by  (Symantec Mail Security) with SMTP id 2C.3B.31035.3765E085; Mon, 24 Oct 2016 20:44:04 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0319.002; Mon, 24 Oct 2016 20:44:01 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Alan Ford <alan.ford@gmail.com>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
Thread-Index: AQHSKq8ixsJ53smzZ0iYfg1cr+NRB6CxH5OAgAA8sICAAHDegIAAChaAgACYYoCAADzBAIAFSssA
Date: Mon, 24 Oct 2016 18:44:00 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BDC9F9A@ESESSMB209.ericsson.se>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com> <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com> <D42E97C0.117A6%christer.holmberg@ericsson.com> <AAE65171-77D6-4100-BED6-70DCFF98798D@gmail.com> <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com> <D55D7C56-4618-4C75-A2A7-F731F4A1142D@gmail.com> <D42FB1C3.1184E%christer.holmberg@ericsson.com>
In-Reply-To: <D42FB1C3.1184E%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGbE9ULckjC/CYNcBZouV51YwW0xd/pjF YsaFqcwOzB47Z91l91iy5CeTx60pBQHMUVw2Kak5mWWpRfp2CVwZJ662MBfc4K54sP0mUwPj Mc4uRk4OCQETiZlTpjF3MXJxCAmsZ5T4vPcTO4SzmFFi9bQbbF2MHBxsAhYS3f+0QRpEBGok bk3/wwoSZhZQl7i6OAgkLCwQI7Fz/Rt2iJJYiatn3oOViAhESTzfFw8SZhFQlVjV950NxOYV 8JXYcv0dI4gtJLCRWWLCq2IQm1PARmLJ04VgYxgFxCS+n1rDBGIzC4hL3HoynwniZAGJJXvO M0PYohIvH/9jhbCVJNYe3s4CUa8ncWPqFDYIW1ti2cLXzBB7BSVOznzCMoFRdBaSsbOQtMxC 0jILScsCRpZVjKLFqcVJuelGxnqpRZnJxcX5eXp5qSWbGIFRc3DLb9UdjJffOB5iFOBgVOLh VfDhixBiTSwrrsw9xCjBwawkwrs+BCjEm5JYWZValB9fVJqTWnyIUZqDRUmc12zl/XAhgfTE ktTs1NSC1CKYLBMHp1QDY8qNjRptkq1defdsuSy2zeaKuPwyqWTqps23Urp8/C4f2x1Xr7Zw 3UXHVMGVs64KV2Vuv6lz4u3fzLc3tStud2nK/J9+Iv8Kb/FTnx6Gvz+azXz5PtpbsFmdq/v+ RXbL6ekvOrX7Djs8rgzc9qnZcNoX111/6ryr+2r3+qe6pV8RMt7Tt/9TrBJLcUaioRZzUXEi AHy+iYOWAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/NaO0a_cvdaADFbUuPXmCO63OJto>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 24 Oct 2016 18:44:20 -0000

Hi,

Maybe we, in draft-bfcpbis and draft-sctp-sdp simply could say: "the rules =
in ICE apply regarding when the c/m- lines must match the default candidate=
". =20

Then we'll deal with the issue in draft-ice-sip-sdp, and it won't stop prog=
ress of draft-bfcpbis and draft-sctp-sdp.

Regards,

Christer

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: 21 October 2016 11:46
To: Alan Ford <alan.ford@gmail.com>; Roman Shpount <roman@telurix.com>
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate=
 in SDP answer?

Hi,

>> On 21 Oct 2016, at 00:09, Roman Shpount <roman@telurix.com> wrote:
>>=20
>> What do you propose to put in c=3D and m=3D line in the answer? Whatever=
=20
>>information you are going to put there it will need to have the=20
>>correct transport (UDP or TCP) in the m=3D line proto in order to be=20
>>correctly interpreted?
>
>That=B9s the basis of the question, however. For the answer, is there any=
=20
>reason the m-line transport actually does need to match an ICE candidate?

It=B9s not only about the m- line transport. The IP address and port in the
c/m- line most likely won=B9t be valid either (if you use different ports a=
nd addresses for UDP and TCP).

Regards,

Christer

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


From nobody Mon Oct 24 11:50:47 2016
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 26B4A12999F for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 11:50:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.632
X-Spam-Level: 
X-Spam-Status: No, score=-4.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.431, 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 R-TrDp5GXpyo for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 11:50:44 -0700 (PDT)
Received: from alum-mailsec-scanner-5.mit.edu (alum-mailsec-scanner-5.mit.edu [18.7.68.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1610F129997 for <mmusic@ietf.org>; Mon, 24 Oct 2016 11:50:43 -0700 (PDT)
X-AuditID: 12074411-ff5ff700000008d0-95-580e58020697
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 2F.78.02256.2085E085; Mon, 24 Oct 2016 14:50:43 -0400 (EDT)
Received: from [192.168.1.110] (c-73-186-127-100.hsd1.ma.comcast.net [73.186.127.100]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id u9OIog58003976 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Mon, 24 Oct 2016 14:50:42 -0400
To: mmusic@ietf.org
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com> <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com> <D42E97C0.117A6%christer.holmberg@ericsson.com> <AAE65171-77D6-4100-BED6-70DCFF98798D@gmail.com> <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com> <D55D7C56-4618-4C75-A2A7-F731F4A1142D@gmail.com> <D42FB1C3.1184E%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B4BDC9F9A@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <0b8867ae-3480-3386-2fc1-d505caa1da59@alum.mit.edu>
Date: Mon, 24 Oct 2016 14:50:41 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BDC9F9A@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOIsWRmVeSWpSXmKPExsUixO6iqMscwRdhcGICl8XU5Y9ZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVcbXvBmPBDeaKru9/2BoYfzF1MXJySAiYSJyYdY+li5GLQ0jg MqPEm6a/TBDOWyaJr7P2soFUCQvESBzaOAvMFhEQlpjx9i8bRNFXZonV19rYQRJsAloScw79 BxrFwcErYC+xZFctSJhFQFVi04/nYNtEBdIktq/bzQxi8woISpyc+YQFxOYU8JM4t6sJzGYW sJW4MxeihllAXmL72znMExj5ZiFpmYWkbBaSsgWMzKsY5RJzSnN1cxMzc4pTk3WLkxPz8lKL dE31cjNL9FJTSjcxQsJMcAfjjJNyhxgFOBiVeHgZDPgihFgTy4orcw8xSnIwKYnyngoACvEl 5adUZiQWZ8QXleakFh9ilOBgVhLhlQ8DyvGmJFZWpRblw6SkOViUxHn5lqj7CQmkJ5akZqem FqQWwWRlODiUJHg7QBoFi1LTUyvSMnNKENJMHJwgw3mAhm8LBRleXJCYW5yZDpE/xajLseDH 7bVMQix5+XmpUuK8T0CKBECKMkrz4ObA0sMrRnGgt4R5ZcOBqniAqQVu0iugJUxASwTjeUCW lCQipKQaGKVdYmLz9nyvu/FZpD5aUe37w3LbSCvv85dNzBi/u235Ju9v1p5RtbX08YEj2fM3 1m1czdtdv6/6VkZHze8vM502xpzmnln1yPJqkIth4b3O457WNU6/vKco6gQ+iTz5TejYy4bF 3dyrJfYJXO3nrKi+lXfh9ZMq7skrn9Za3ZK929QXMeuCnBJLcUaioRZzUXEiAFX101DqAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/1trM_rpawyKW5IK7G0NrhJBe74g>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 24 Oct 2016 18:50:45 -0000

On 10/24/16 2:44 PM, Christer Holmberg wrote:
> Hi,
>
> Maybe we, in draft-bfcpbis and draft-sctp-sdp simply could say: "the rules in ICE apply regarding when the c/m- lines must match the default candidate".
>
> Then we'll deal with the issue in draft-ice-sip-sdp, and it won't stop progress of draft-bfcpbis and draft-sctp-sdp.

Seems like that would work. But of course they will still eventually 
block on their dependency to that draft.

	Thanks,
	Paul


From nobody Mon Oct 24 11:55:50 2016
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 B1F5D1299B7 for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 11:55:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 EfKBqPBydoYB for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 11:55:47 -0700 (PDT)
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 164751299B4 for <mmusic@ietf.org>; Mon, 24 Oct 2016 11:55:46 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-7f-580e5930c48a
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by  (Symantec Mail Security) with SMTP id 28.2D.02551.0395E085; Mon, 24 Oct 2016 20:55:45 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0319.002; Mon, 24 Oct 2016 20:55:43 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
Thread-Index: AQHSKq8ixsJ53smzZ0iYfg1cr+NRB6CxH5OAgAA8sICAAHDegIAAChaAgACYYoCAADzBAIAFSssA///g/oCAACK7oA==
Date: Mon, 24 Oct 2016 18:55:42 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BDCA012@ESESSMB209.ericsson.se>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com> <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com> <D42E97C0.117A6%christer.holmberg@ericsson.com> <AAE65171-77D6-4100-BED6-70DCFF98798D@gmail.com> <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com> <D55D7C56-4618-4C75-A2A7-F731F4A1142D@gmail.com> <D42FB1C3.1184E%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B4BDC9F9A@ESESSMB209.ericsson.se> <0b8867ae-3480-3386-2fc1-d505caa1da59@alum.mit.edu>
In-Reply-To: <0b8867ae-3480-3386-2fc1-d505caa1da59@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrALMWRmVeSWpSXmKPExsUyM2K7rq5hJF+EwcxN3BZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJVxcsYktoLpLBVbrh5laWBcwtzFyMEhIWAi cfdfbhcjF4eQwHpGiae3lzBCOIsZJe69PsUIUsQmYCHR/U+7i5GTQ0TAV+LZ49tsILawQIzE zvVv2CHisRJXz7xnhbCzJA78PwUWZxFQlZjWtRoszgvUu2vCUWaI+atZJC6ffcYIkuAUcJBY vnk1M4jNKCAm8f3UGiYQm1lAXOLWk/lgtoSAgMSSPeeZIWxRiZeP/7FC2EoSaw9vZ4Go15FY sPsTG4StLbFs4WtmiMWCEidnPmGZwCgyC8nYWUhaZiFpmYWkZQEjyypG0eLU4uLcdCNjvdSi zOTi4vw8vbzUkk2MwHg4uOW37g7G1a8dDzEKcDAq8fAq+PBFCLEmlhVX5h5ilOBgVhLhNY0A CvGmJFZWpRblxxeV5qQWH2KU5mBREuc1W3k/XEggPbEkNTs1tSC1CCbLxMEp1cDYk7LfI26G 60HtNra9KlVV19xkT+/eyHczzbbwY+Dt1+/WB96WjMjZLMuzbVFUthb74pB9sTYpGV8eutor a17+ZxA2qU1S4bn9bNd+/qnK140cXbfXvww6Kdr8L2pH894s2wLr/+1/2uub6q3ZGK4oZhx5 cW9GVv7pe0cuPtbnUD28On72ZkclluKMREMt5qLiRAC69uzSgwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/XHYczwrXh3hICJdkoVTWmehTXQc>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 24 Oct 2016 18:55:49 -0000

Hi,

>> Maybe we, in draft-bfcpbis and draft-sctp-sdp simply could say: "the rul=
es in ICE apply >>  regarding when the c/m- lines must match the default ca=
ndidate".
>>
>> Then we'll deal with the issue in draft-ice-sip-sdp, and it won't stop p=
rogress of draft->> bfcpbis and draft-sctp-sdp.
>
> Seems like that would work. But of course they will still eventually bloc=
k on their=20
> dependency to that draft.

True. But, at least we'll get the drafts out of the WGs, IESG reviewed etc.

Regards,

Christer


From nobody Mon Oct 24 13:32:59 2016
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 AAE581299C7 for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 13:32:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 VI3pJ10_ZMyS for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 13:32:55 -0700 (PDT)
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 1C919129622 for <mmusic@ietf.org>; Mon, 24 Oct 2016 13:32:54 -0700 (PDT)
X-AuditID: c1b4fb25-14bff7000000793b-11-580e6ff43e2b
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by  (Symantec Mail Security) with SMTP id A4.C5.31035.4FF6E085; Mon, 24 Oct 2016 22:32:53 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0319.002; Mon, 24 Oct 2016 22:32:52 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Bo Burman <bo.burman@ericsson.com>, "mmusic (mmusic@ietf.org)" <mmusic@ietf.org>
Thread-Topic: Agenda requests for IETF 97
Thread-Index: AdIrqfGh5WqKdM8uQS2lbeNWMYwAgACi0aQA
Date: Mon, 24 Oct 2016 20:32:51 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BDCA191@ESESSMB209.ericsson.se>
References: <AM5PR0701MB25777F52531523C2870F0B1A8DD40@AM5PR0701MB2577.eurprd07.prod.outlook.com>
In-Reply-To: <AM5PR0701MB25777F52531523C2870F0B1A8DD40@AM5PR0701MB2577.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BDCA191ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyM2K7ve7XfL4Ig4e35S2mLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujMPbJ7MW7HKtONK0jr2Bca9tFyMnh4SAiUTHyo2MXYxcHEIC 6xklns/tYIVwFjNK7Lr6jL2LkYODTcBCovufNkiDiECYxJWdL9lBbGEBDYnlWz+ClYgIaEq8 Xq4HUWIk8eNQFyOIzSKgKtHSeI0JxOYV8JV4/247K4gtJJAgsfDxDrA4p0CiRMudW8wgNqOA mMT3U2vA4swC4hK3nsxngrhTQGLJnvPMELaoxMvH/1ghbCWJtYe3s0DU50t8bfjICLFLUOLk zCcsExiFZyEZNQtJ2SwkZRBxHYkFuz+xQdjaEssWvmaGsc8ceMyELL6AkX0Vo2hxanFSbrqR sV5qUWZycXF+nl5easkmRmCkHNzyW3UH4+U3jocYBTgYlXh4FXz4IoRYE8uKK3MPMUpwMCuJ 8BYC40yINyWxsiq1KD++qDQntfgQozQHi5I4r9nK++FCAumJJanZqakFqUUwWSYOTqkGRqPO CR9PRS5Iiv63wG+HTVdXwSH1qnLrdMNuWYVDG571n/LL3VZSfD9YL+Wjv9CUP1YzJ19YU5X+ 6LTMhDnvFvbn5WvxJDwWXqs7sW0Cp4DkyvItbheVI81/ht2pfamw339Rm4P6BeH/4VVOL22y Dzs+YTAwUAl3cJpneEve/5aLeLH4kZCFSizFGYmGWsxFxYkAoMFRa5ACAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/gvNHdJ-tqLbPNPNkwesur2jkK10>
Subject: Re: [MMUSIC] Agenda requests for IETF 97
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 24 Oct 2016 20:32:56 -0000

--_000_7594FB04B1934943A5C02806D1A2204B4BDCA191ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

There are a couple of issues that have been raised and discussed on the lis=
t lately, which I think could be discussed face-to-face:


1)      ICE-SIP-SDP: Do we need to mandate the c/m-line transport to match =
the default candidate in an SDP answer (currently mandated by RFC 5245)? Do=
es the answerer even have to support the transport indicated in the c/m-lin=
e of the SDP answer?

2)      TRICKLE-ICE-SIP-SDP: Is there a need to, in addition to the trickle=
d candidates, include all previously signalled candidates in trickle INFOs?=
 What if such previously signalled candidates are no longer valid? What wil=
l break if we only signal the new trickled candidates?

Regards,

Christer


From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Bo Burman
Sent: 21 October 2016 17:54
To: mmusic (mmusic@ietf.org) <mmusic@ietf.org>
Subject: [MMUSIC] Agenda requests for IETF 97

Hi,

The preliminary agenda deadline is in just over a week and the chairs did n=
ot receive any agenda requests yet.
Please send your requests to the chairs and/or to the list.

Bo & Flemming
MMUSIC chairs


--_000_7594FB04B1934943A5C02806D1A2204B4BDCA191ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:92937594;
	mso-list-type:hybrid;
	mso-list-template-ids:837977702 134807569 134807577 134807579 134807567 13=
4807577 134807579 134807567 134807577 134807579;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US">There are a couple of issues that have been raised and discussed on th=
e list lately, which I think could be discussed face-to-face:<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D;mso-fareast-lang=
uage:EN-US"><span style=3D"mso-list:Ignore">1)<span style=3D"font:7.0pt &qu=
ot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D;mso-fareast-lan=
guage:EN-US">ICE-SIP-SDP: Do we need to mandate the c/m-line transport to m=
atch the default candidate in an SDP answer (currently mandated by RFC 5245=
)? Does the answerer even have to
 support the transport indicated in the c/m-line of the SDP answer?<o:p></o=
:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D;mso-fareast-lang=
uage:EN-US"><span style=3D"mso-list:Ignore">2)<span style=3D"font:7.0pt &qu=
ot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D;mso-fareast-lan=
guage:EN-US">TRICKLE-ICE-SIP-SDP: Is there a need to, in addition to the tr=
ickled candidates, include all previously signalled candidates in trickle I=
NFOs? What if such previously signalled
 candidates are no longer valid? What will break if we only signal the new =
trickled candidates?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"color:#1F=
497D;mso-fareast-language:EN-US"><o:p>&nbsp;</o:p></span></a></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US">Christer<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> mmusic [mailto:mmusic-bounces@ietf.org]
<b>On Behalf Of </b>Bo Burman<br>
<b>Sent:</b> 21 October 2016 17:54<br>
<b>To:</b> mmusic (mmusic@ietf.org) &lt;mmusic@ietf.org&gt;<br>
<b>Subject:</b> [MMUSIC] Agenda requests for IETF 97<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"SV">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"SV"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The preliminary agenda deadline=
 is in just over a week and the chairs did not receive any agenda requests =
yet.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Please send your requests to th=
e chairs and/or to the list.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Bo &amp; Flemming<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">MMUSIC chairs<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B4BDCA191ESESSMB209erics_--


From nobody Mon Oct 24 13:45:02 2016
Return-Path: <ibc@aliax.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 42D7A1299C9 for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 13:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aliax-net.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 7ePSVTqJ7iR4 for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 13:45:00 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 1D5051299D2 for <mmusic@ietf.org>; Mon, 24 Oct 2016 13:44:45 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id c78so137368680wme.1 for <mmusic@ietf.org>; Mon, 24 Oct 2016 13:44:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aliax-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=CJoBL2SpAa8ThsZHZbo/RwKmnpluxPavpSHGo7ctD6U=; b=Kpl2y7HGzqQxwDcogl/olasY+4E/17kxZjv7jNSp13CGHKlsrbnS0Bef1VeOFlnMIq 2r5V0lSGa5ncUl5ziGg3o8bIEoopbf+DAb/YpjpeHsRv6s0DqgAx1R85mLLmnp8xbwqz leuL6wM8aEevUxtEoQJd6jHlZrJRjkpf0Wtj9sPnm6e2Di6vOYX5Y3BZmcD95Lube8Ih xQSvkP+BUcnec2B61KRCEf8/ENVNVwN5G3WAtikpzbh/Ss91Z6HEBs08nNutc2uaD9Q2 uevb5kusNpdHzgktcmoPom+ZfaOiWUsjVJLt/iY2ZZlP5KV2NjuonTU4kkFhcm+exYIv NCnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=CJoBL2SpAa8ThsZHZbo/RwKmnpluxPavpSHGo7ctD6U=; b=DydDjH0CbrwANhMkNvEb+YmW/lws0tds8DQM7E+vpfqKEHQh3osIBj9vlFL6mhGIo/ wWw9C4S6anfWZt2KOJF4lNN+0jpFuVf32GUbJzr5+exAVs3upAiQ+UM571oXQbAgKv+4 fndJnS4rIViFBISHY3fmBaf66dCAOKlbU8g4B4yqpkXw1igbctPaNbeMesopzkNDMJF5 q9NCwG5v3+1nNUc6gzJKVzuVLLySKlIhUZB1CgxSFUi5J5LCYoeR4ZeFo0cfrhL+CpBl L5LG6VxgE9Fq1N5jRk+ewFPWRIU3IBD7Vdrclw2bY9pk7xZ9DEp/ymA04Nqg7/wBwjO4 /CrQ==
X-Gm-Message-State: AA6/9RnC2J+n0Fwp0Gd+lvGwlhO8fkE8RQFwk6DjBdAWcrxggULYzTezDra0jGej9+rEzrwWqHJBZTwc3Awoxw==
X-Received: by 10.28.168.86 with SMTP id r83mr24855904wme.16.1477341883588; Mon, 24 Oct 2016 13:44:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.134.25 with HTTP; Mon, 24 Oct 2016 13:44:23 -0700 (PDT)
In-Reply-To: <D42A7728.113D4%christer.holmberg@ericsson.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Mon, 24 Oct 2016 22:44:23 +0200
Message-ID: <CALiegfn2wEnOtJB2XsAckedAOsDVBa-ZN0ht+mVcT+YxgTxzcA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/S1a1qCwh3DcUThqf72avekc1ZgA>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 24 Oct 2016 20:45:01 -0000

2016-10-17 11:37 GMT+02:00 Christer Holmberg <christer.holmberg@ericsson.co=
m>:
> Another solution would to always mandate support of one or more specific
> transports, and specify that the default candidate MUST use that transpor=
t.

Another solution would be to remove the useless address in the c=3D and
m=3D lines because it has zero values when ICE is required (such as in
WebRTC). Or just do as current WebRTC browsers do: put something fake
in there (127.0.0.1 with any port).


--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>


From nobody Mon Oct 24 15:23:17 2016
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 57FF6129ACA for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 15:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5] 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 G08Fd4LnQgFH for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 15:23:14 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (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 9269E129A42 for <mmusic@ietf.org>; Mon, 24 Oct 2016 15:23:14 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id g49so4595140qtc.6 for <mmusic@ietf.org>; Mon, 24 Oct 2016 15:23:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=alx3e9cbf8TdVVA6ZyFYlQbZWX5bsWZtaXnZf/KgSM8=; b=FHjDQdkHlX7qYr/i8k5d8ytd65gzYcgDC7N/Yeazvdds2T/RdzORhoAxmB844iND1H oIwCbpqg9yXQ15aQWelr4oWbvHWdwOZosIFhXaA+H8sIxGqUvii68/yU66atMBKZyC1t VZoTY6b6Qd2R+kN0+I/tRltpkX633uADTZtkeXchy9XU1BoXrtRqou1IR5bA7bfsHsXP StAYMwEuYDhZfM1gDtap/ZI7k5kvLGDN6IrXjFjLmcRSTD4z9qsjSxmpCcC/4TO5ijyQ FBE1L+eJLK/5y4fOAjtgsTfh9vFHEren5tsOsojhKJVImiVnXYKulcCIAn5DDKS8dFrO 7wgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=alx3e9cbf8TdVVA6ZyFYlQbZWX5bsWZtaXnZf/KgSM8=; b=MA00LiqHtnKvfCaGLLW313jyYYUzVtoWoAnFr4VFkdQkI9qCVpiCoiegqkJnD9P0y2 OTZhB27CjuMtDJUql8iJ7yOjXFteOSetSvEMkjHZqvjEeIq4bPykWkhlebbCImHTB6G9 5pbx9qYXZM7nIhDxQ9FNYfsOsBtsoo6n1n9QB61RntWdiaeBOr479skJ7sFHpow7Auhn fl5HhzNKGIYHF/XtA5/uOnsoVpYempMExxw34GlTXE/PH/xhUr+QvdFlmRS5pY1Z0S6P uxt3H53JOozgZnpBZTYq+dpbXv7jMYiZMcggjWx2XAgLNmLdsMgLXEDcAiR2Qyft0R15 Gfyw==
X-Gm-Message-State: ABUngvfvUvYYYAw5Byk3YCx4eIYgxNcLRk+wofxc7/KFrfjy1uArKDlw0VusrMNYFcVcGA==
X-Received: by 10.200.40.91 with SMTP id 27mr16993466qtr.135.1477347793507; Mon, 24 Oct 2016 15:23:13 -0700 (PDT)
Received: from mail-qk0-f173.google.com (mail-qk0-f173.google.com. [209.85.220.173]) by smtp.gmail.com with ESMTPSA id w72sm9523703qkb.33.2016.10.24.15.23.12 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Oct 2016 15:23:13 -0700 (PDT)
Received: by mail-qk0-f173.google.com with SMTP id o68so249487061qkf.3 for <mmusic@ietf.org>; Mon, 24 Oct 2016 15:23:12 -0700 (PDT)
X-Received: by 10.55.160.17 with SMTP id j17mr16518839qke.167.1477347792823; Mon, 24 Oct 2016 15:23:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.132.161 with HTTP; Mon, 24 Oct 2016 15:23:12 -0700 (PDT)
In-Reply-To: <CALiegfn2wEnOtJB2XsAckedAOsDVBa-ZN0ht+mVcT+YxgTxzcA@mail.gmail.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <CALiegfn2wEnOtJB2XsAckedAOsDVBa-ZN0ht+mVcT+YxgTxzcA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Mon, 24 Oct 2016 18:23:12 -0400
X-Gmail-Original-Message-ID: <CAD5OKxte9UhFtgUjExBK_hedTUOWwZiMwzUbJSQxd9nAY+w1dg@mail.gmail.com>
Message-ID: <CAD5OKxte9UhFtgUjExBK_hedTUOWwZiMwzUbJSQxd9nAY+w1dg@mail.gmail.com>
To: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: multipart/alternative; boundary=94eb2c0613fe66aea8053fa3d668
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Be_GosoMM9PGoMJrBFpMiyXm9K8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 24 Oct 2016 22:23:16 -0000

--94eb2c0613fe66aea8053fa3d668
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

My initial solution had two parts:

1. In cases where backwards compatibility with non-ICE endpoints is
required, require that ICE includes UDP candidates and uses UDP candidate
for default candidate. Essentially this considers UDP protocol version and
UDP candidate support required to implement and considers TCP based
protocol version and TCP ICE candidate support optional extensions.

2. In cases where ICE is required and non-ICE answer will not be accepted,
define a new transport tag ICE such as ICE/DTLS/SCPT. In this case no
default candidate should be included. c=3D line should use transport addres=
s
IN IP4 127.0.0.1. m=3D line should use port 7 (discard). In this case no
additional re-INVITE should be sent when ICE nomination process is
completed. This should correspond to the normal use case for WebRTC
browsers.

Regards,
_____________
Roman Shpount

On Mon, Oct 24, 2016 at 4:44 PM, I=C3=B1aki Baz Castillo <ibc@aliax.net> wr=
ote:

> 2016-10-17 11:37 GMT+02:00 Christer Holmberg <christer.holmberg@ericsson.
> com>:
> > Another solution would to always mandate support of one or more specifi=
c
> > transports, and specify that the default candidate MUST use that
> transport.
>
> Another solution would be to remove the useless address in the c=3D and
> m=3D lines because it has zero values when ICE is required (such as in
> WebRTC). Or just do as current WebRTC browsers do: put something fake
> in there (127.0.0.1 with any port).
>
>
> --
> I=C3=B1aki Baz Castillo
> <ibc@aliax.net>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--94eb2c0613fe66aea8053fa3d668
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">My initial solution had two parts:<div><br></div><div>1. I=
n cases where backwards compatibility with non-ICE endpoints is required, r=
equire that ICE includes UDP candidates and uses UDP candidate for default =
candidate. Essentially this considers UDP protocol version and UDP candidat=
e support required to implement and considers TCP based protocol version an=
d TCP ICE candidate support optional extensions.</div><div><br></div><div>2=
. In cases where ICE is required and non-ICE answer will not be accepted, d=
efine a new transport tag ICE such as ICE/DTLS/SCPT. In this case no defaul=
t candidate should be included. c=3D line should use transport address IN I=
P4 127.0.0.1. m=3D line should use port 7 (discard). In this case no additi=
onal re-INVITE should be sent when ICE nomination process is completed. Thi=
s should correspond to the normal use case for WebRTC browsers.<br><div cla=
ss=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Regards,<br clear=
=3D"all"><div><div class=3D"gmail_signature" data-smartmail=3D"gmail_signat=
ure">_____________<br>Roman Shpount</div></div>
<br><div class=3D"gmail_quote">On Mon, Oct 24, 2016 at 4:44 PM, I=C3=B1aki =
Baz Castillo <span dir=3D"ltr">&lt;<a href=3D"mailto:ibc@aliax.net" target=
=3D"_blank">ibc@aliax.net</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><span class=3D"">2016-10-17 11:37 GMT+02:00 Christer Holmberg &lt;<a=
 href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
<wbr>com</a>&gt;:<br>
&gt; Another solution would to always mandate support of one or more specif=
ic<br>
&gt; transports, and specify that the default candidate MUST use that trans=
port.<br>
<br>
</span>Another solution would be to remove the useless address in the c=3D =
and<br>
m=3D lines because it has zero values when ICE is required (such as in<br>
WebRTC). Or just do as current WebRTC browsers do: put something fake<br>
in there (127.0.0.1 with any port).<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
--<br>
I=C3=B1aki Baz Castillo<br>
&lt;<a href=3D"mailto:ibc@aliax.net">ibc@aliax.net</a>&gt;<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div></div></div>

--94eb2c0613fe66aea8053fa3d668--


From nobody Mon Oct 24 18:31:17 2016
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 396841299D8 for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 18:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.632
X-Spam-Level: 
X-Spam-Status: No, score=-4.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.431, 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 4a5ryGXfkdkr for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 18:31:13 -0700 (PDT)
Received: from alum-mailsec-scanner-4.mit.edu (alum-mailsec-scanner-4.mit.edu [18.7.68.15]) by ietfa.amsl.com (Postfix) with ESMTP id 4111C129611 for <mmusic@ietf.org>; Mon, 24 Oct 2016 18:31:13 -0700 (PDT)
X-AuditID: 1207440f-20bff700000009a9-47-580eb5ddf150
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 52.E2.02473.DD5BE085; Mon, 24 Oct 2016 21:31:12 -0400 (EDT)
Received: from [192.168.1.110] (c-73-186-127-100.hsd1.ma.comcast.net [73.186.127.100]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id u9P1V8ng025433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Mon, 24 Oct 2016 21:31:09 -0400
To: mmusic@ietf.org
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <CALiegfn2wEnOtJB2XsAckedAOsDVBa-ZN0ht+mVcT+YxgTxzcA@mail.gmail.com> <CAD5OKxte9UhFtgUjExBK_hedTUOWwZiMwzUbJSQxd9nAY+w1dg@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <fb2a8750-afce-a082-4f47-6ed9c54d9847@alum.mit.edu>
Date: Mon, 24 Oct 2016 21:31:08 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxte9UhFtgUjExBK_hedTUOWwZiMwzUbJSQxd9nAY+w1dg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrDIsWRmVeSWpSXmKPExsUixO6iqPtgK1+EQf9uGYupyx+zODB6LFny kymAMYrLJiU1J7MstUjfLoEr4/XqUywFPzkr5l8/ydrA+Je9i5GTQ0LAROJiy3nGLkYuDiGB y4wSm+Z+YYVw3jJJzDlyHKxKWCBG4tDGWWwgtoiAsMSMt3/ZIIpOMko86F7DDJJgE9CSmHPo PwuIzStgL7H41Q9WEJtFQFXi7PwHYDWiAmkS29ftZoaoEZQ4OfMJWD2nQKBES891RhCbWcBW 4s5ciBpmAXmJ7W/nME9g5JuFpGUWkrJZSMoWMDKvYpRLzCnN1c1NzMwpTk3WLU5OzMtLLdI1 0cvNLNFLTSndxAgJNP4djF3rZQ4xCnAwKvHwMhjwRQixJpYVV+YeYpTkYFIS5Z25CSjEl5Sf UpmRWJwRX1Sak1p8iFGCg1lJhNd3I1CONyWxsiq1KB8mJc3BoiTOq75E3U9IID2xJDU7NbUg tQgmK8PBoSTBe30LUKNgUWp6akVaZk4JQpqJgxNkOA/Q8BsgNbzFBYm5xZnpEPlTjIpS4rwd IAkBkERGaR5cLywRvGIUB3pFmPc9SBUPMInAdb8CGswENFgwngdkcEkiQkqqgVE5SfrQJ7ly 18qSxHqv7ysnTX3b9ppz5rNLHvZOr64eXGtzY1uGclnTfGv1LaplEinnKmt2TV29UPgzq4Zh aPS9OdVWpss3m69bfU7q3O5wk8eMvn0/s/+vyzg+TyqAteuKu4DLTm3NLmP2vYsb/h+w/mzS f9tUIbap/sejmVnbvy91FuC/EaLEUpyRaKjFXFScCADkWHZV3wIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/u_cHPsSFkY1OipKho8H-HPqDZ8k>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 01:31:15 -0000

On 10/24/16 6:23 PM, Roman Shpount wrote:
> My initial solution had two parts:
>
> 1. In cases where backwards compatibility with non-ICE endpoints is
> required, require that ICE includes UDP candidates and uses UDP
> candidate for default candidate. Essentially this considers UDP protocol
> version and UDP candidate support required to implement and considers
> TCP based protocol version and TCP ICE candidate support optional
> extensions.
>
> 2. In cases where ICE is required and non-ICE answer will not be
> accepted, define a new transport tag ICE such as ICE/DTLS/SCPT. In this
> case no default candidate should be included. c= line should use
> transport address IN IP4 127.0.0.1. m= line should use port 7 (discard).
> In this case no additional re-INVITE should be sent when ICE nomination
> process is completed. This should correspond to the normal use case for
> WebRTC browsers.

How about:

C=IN IP4 invalid

'invalid' is a syntactically valid FQDN and so can be used there, and we 
have precedent from anonymous.invalid to use it to signify an unusable 
address.

It also occurs to me that with the expansion of TLDs, maybe somebody 
ought to reserve 'invalid' before somebody else reserves it to use it.

	Thanks,
	Paul


From nobody Mon Oct 24 21:01:28 2016
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 9916A12940E; Mon, 24 Oct 2016 21:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.952
X-Spam-Level: 
X-Spam-Status: No, score=-14.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 QQxVmxBGD74V; Mon, 24 Oct 2016 21:01:25 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9444A12959F; Mon, 24 Oct 2016 21:01:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6709; q=dns/txt; s=iport; t=1477368085; x=1478577685; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=qN3zEDHjn/YVlSNCaFXSiKfeGeQ12QvIpaFd3gxzIuc=; b=Bc4XnOHOLMXlYAiOythKf540azvdh5d+BxcccR2P8VjyaM2/p3+mSnsl CnP5AqrBhwn8Xe50NsD2VMVwzpB5+esqyl+VRqJgmlVb5fo9N408Imwpj DaRq3MambL2L0oEtqQrwMDGlh2y35rto+wH7zj25Qupy7kLjKsZOzFdEy k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DUAQAn2A5Y/5BdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgyoBAQEBAR1YKlONNJZ9lD+CBxwLhTBKAoFsPxQBAgEBAQEBAQF?= =?us-ascii?q?iKIRjAQEEAQEBIA8BBTAGCxALGAICHwcCAicwBgEMBgIBAReINw60W4x2AQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEYBYEHhTaBfYFTgQWEGREBgyCCWwWGJpNujDaDXYF?= =?us-ascii?q?uhG2DF4YQhxeFb4QBHjZeg0iBViI0hTqCIAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.31,544,1473120000"; d="scan'208";a="161214834"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Oct 2016 04:01:24 +0000
Received: from [10.24.117.224] ([10.24.117.224]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u9P41MWC015283; Tue, 25 Oct 2016 04:01:23 GMT
To: Ben Campbell <ben@nostrum.com>, Bo Burman <bo.burman@ericsson.com>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com>
Date: Tue, 25 Oct 2016 00:01:22 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/QL8rNyaVxLH55EjCQLU7FbnVroM>
Cc: ART ADs <art-ads@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 04:01:27 -0000

Hi Ben

We will get a poll setup as soon as we understand any major constraints 
from the key participants.

Thanks

-- Flemming


On 10/21/16 4:49 PM, Ben Campbell wrote:
> Hi Everyone, please accept my apologies for waiting this long to weigh 
> in.
>
> I think it's clear that multiple people are not happy with how we got 
> to this point. But assigning blame doesn't help us make progress on 
> the draft. I propose that we get over that, and instead focus instead 
> on how to move forward. Email discussion doesn't seem to be helping. 
> Maybe a call will.
>
> Flemming and/or Bo: Can you set up a Doodle poll to get Christer, 
> Cullen, and other demonstratively  interested parties on a conference 
> call? I will join if at all possible, but don't let scheduling around 
> me stop a call from happening.
>
> Thanks!
>
> Ben.
>
> On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:
>
>> [fixing cc-list]
>>
>> On 10/21/16 11:59 AM, Flemming Andreasen wrote:
>>>
>>>
>>> On 10/21/16 11:21 AM, Cullen Jennings wrote:
>>>> I think that is a bad way to run a WG. All I asked for was a phone 
>>>> call to discuss this so we could get the issues on the table and 
>>>> discuss what is best. The chairs never even replied to my request 
>>>> for a WG call to discuss this.
>>> That is simply not true. You (and Christer) were explicitly asked to 
>>> setup a phone call on 10/6/16 to discuss this issue; a request that 
>>> (like many other others) went unanswered or required extensive 
>>> prodding to get any attention.
>>>
>>>> The list discussions that ensued from this resulted in people other 
>>>> than me sugesting possibilities that were much better than any of 
>>>> the three below -  none of which were considered in your consensus 
>>>> call.
>>> I'm not sure what those proposals are, nor were they brought up in 
>>> response to the consensus call.
>>>
>>>> I donâ€™t plan to appeal this but I am considering if itâ€™s worth my 
>>>> time to participate in this WG if we are not going to be willing to 
>>>> actually spend a short time to discuss possible solutions before 
>>>> taking a consensus call.  As input to that decisions, it would be 
>>>> really useful to know why you refused to have a phone call on this 
>>>> topic and what your policy in general is going to be toward 
>>>> discussions of proposed solutions to problems in the future.
>>> My position is that we will try our very best to get to not only 
>>> consensus but to satisfy as many concerns as we possibly can. It 
>>> does however require people to engage in a timely manner, and even 
>>> when they don't, we still do what we can, but at some point we need 
>>> to move forward. As for the issue at hand, it has been discussed 
>>> extensively, and several changes were made to the draft to try and 
>>> accommodate your requests.
>>>
>>> The one major remaining issue I believe you have is around whether 
>>> this document updates RFC 4572. This has been discussed extensively 
>>> on the wgchairs list; a discussion I initiated to try and help 
>>> address your concern. You may disagree with how that discussion 
>>> concluded, but again, to try and alleviate your concerns, a note was 
>>> added to 4572-update to make it clear that the document does not 
>>> make existing 4572 implementations non-compliant with RFC 4572.
>>>
>>> I believe the chairs, authors, and the WG at large has done 
>>> everything that can reasonably be done to try and address your 
>>> concerns, and at this point we need to move forward.
>>>
>>> Thanks
>>>
>>> -- Flemming (as MMUSIC co-chair)
>>>
>>>
>>>
>>>>
>>>>> On Oct 19, 2016, at 6:43 AM, Flemming Andreasen 
>>>>> <fandreas@cisco.com> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Following up on the consensus call, we have received 5 responses 
>>>>> in favor of option a) below, one neutral, and one objection. 
>>>>> Looking at the document we have noted that backwards compatibility 
>>>>> is handled by the current text in the document and it also clearly 
>>>>> states that it does not make current RFC 4572 implementation 
>>>>> non-compliant with RFC 4572. Since we have not heard of any 
>>>>> technical problems with proposal a), nor seen any tangible 
>>>>> progress on how to address the objection, we are hereby declaring 
>>>>> rough consensus on option a). We will proceed with the publication 
>>>>> request for the current draft while duly noting the "roughness" of 
>>>>> the consensus based on the pending objection as part of this.
>>>>>
>>>>> Thanks
>>>>>
>>>>>     Flemming & Bo (MMUSIC chairs)
>>>>>
>>>>>
>>>>> On 10/12/16 6:23 PM, Flemming Andreasen wrote:
>>>>>> Greetings
>>>>>>
>>>>>> There has been quite a bit of discussion on 
>>>>>> draft-ietf-mmusic-4572-update (currently -07), which had 
>>>>>> previously completed WGLC when a few concerns were raised. The 
>>>>>> document currently:
>>>>>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
>>>>>> 2. Updates the preferred cipher-suite with a stronger cipher suite
>>>>>> 3. Updates RFC 4572.
>>>>>>
>>>>>> Item 1 seems to be generally agreeable, whereas items 2 and 3 are 
>>>>>> not. The chairs are hereby soliciting WG feedback on how to 
>>>>>> proceed based on the following choices:
>>>>>>
>>>>>> a) Proceed with publication of 4572-update-07 in its current form 
>>>>>> (i.e. covering all 3 items above)
>>>>>>
>>>>>> b) Remove item 2 from 4572-update, i.e. do not update the 
>>>>>> preferred cipher-suite
>>>>>>
>>>>>> c) Remove item 3 from 4572-update, i.e. do not indicate that this 
>>>>>> document constitutes an update to RFC 4572.
>>>>>>
>>>>>>
>>>>>> Note that choice a) is mutually exclusive with b) and c), but b) 
>>>>>> and c) are not mutually exclusive.
>>>>>>
>>>>>> Please let us know your preference wrt to the above no later than 
>>>>>> Friday October 14th.
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>        Flemming & Bo (MMUSIC chairs)
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>> .
>>>>
>>>
>>> _______________________________________________
>>> 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 Mon Oct 24 21:33:13 2016
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 5433112940E; Mon, 24 Oct 2016 21:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 JMSxYUEwMK17; Mon, 24 Oct 2016 21:33:10 -0700 (PDT)
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 BD503127735; Mon, 24 Oct 2016 21:33:09 -0700 (PDT)
X-AuditID: c1b4fb25-5405a9800000793b-d2-580ee0838b6f
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by  (Symantec Mail Security) with SMTP id E5.35.31035.380EE085; Tue, 25 Oct 2016 06:33:07 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0319.002; Tue, 25 Oct 2016 06:33:04 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Flemming Andreasen <fandreas@cisco.com>
Thread-Topic: Moving Forward on 4572-update (was Re: [MMUSIC] Rough concensus: Re: 4572-update: Consensus call on how to move forward)
Thread-Index: AQHSLnR1sB2Eo9RdiEK53xAcLSP2VaC4lNg5
Date: Tue, 25 Oct 2016 04:33:04 +0000
Message-ID: <32BBB414-85BA-484C-954D-EDC8620F26DF@ericsson.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com>, <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com>
In-Reply-To: <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkkeLIzCtJLcpLzFFi42KZGbHdQ7f5AV+EwbQHJhYbn05msZjfeZrd 4v0FXYsP638wWkxd/pjFgdVjyu+NrB5Llvxk8rh8/iOjx6ydT1gCWKK4bFJSczLLUov07RK4 MvbfnstU0GVW0TC5gbWB8ZF2FyMnh4SAicTWR3fZuhi5OIQE1jNK/G2exQLhLGaU2PG+ibGL kYODTcBCovufNogpIqAtMXWBBUgJM0jJvc2XwJqFBdoZJdqfzwBzRAQ6GCUurfjKBrJCRMBI 4uKlSywg3SwCqhK3VlmDhHkF7CW6tl1jBbGFBPIlLnbdYQSxOQVsJeY8ewoWZxQQk/h+ag0T iM0sIC5x68l8JoirBSSW7DnPDGGLSrx8/I8VosZA4v25+cwQtrbEsoWvmSF2CUqcnPmEZQKj yCwko2YhaZmFpGUWkpYFjCyrGEWLU4uTctONjPVSizKTi4vz8/TyUks2MQIj6OCW36o7GC+/ cTzEKMDBqMTDq+DDFyHEmlhWXJl7iFGCg1lJhHfubaAQb0piZVVqUX58UWlOavEhRmkOFiVx XrOV98OFBNITS1KzU1MLUotgskwcnFINjDGvP0c3/FBOWzL10JUXqTVlB/53tfbvyNtxSXFt 3YoL850n8t/8cZP/7Q1RvdX+MrVTlZhlIrgzWCa9Xnsg+E/zXf4/dbffi6u/yv/YEabSn+/X t61adkbhDI0D10ruvte3rO4+p2Ucd2z2s6WxU6R9f02t5eNUzzb+Pce30ufm/pzJVroSAUos xRmJhlrMRcWJALNSAaucAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/CrkfuZJ64ndIAGBZw9bnvtJMQ-Y>
Cc: Ben Campbell <ben@nostrum.com>, ART ADs <art-ads@ietf.org>, mmusic <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 04:33:12 -0000

Hi Flemming,

Any day but Monday works for me.

Regards,

Christer=20

Sent from my iPhone

> On 25 Oct 2016, at 7.01, Flemming Andreasen <fandreas@cisco.com> wrote:
>=20
> Hi Ben
>=20
> We will get a poll setup as soon as we understand any major constraints f=
rom the key participants.
>=20
> Thanks
>=20
> -- Flemming
>=20
>=20
>> On 10/21/16 4:49 PM, Ben Campbell wrote:
>> Hi Everyone, please accept my apologies for waiting this long to weigh i=
n.
>>=20
>> I think it's clear that multiple people are not happy with how we got to=
 this point. But assigning blame doesn't help us make progress on the draft=
. I propose that we get over that, and instead focus instead on how to move=
 forward. Email discussion doesn't seem to be helping. Maybe a call will.
>>=20
>> Flemming and/or Bo: Can you set up a Doodle poll to get Christer, Cullen=
, and other demonstratively  interested parties on a conference call? I wil=
l join if at all possible, but don't let scheduling around me stop a call f=
rom happening.
>>=20
>> Thanks!
>>=20
>> Ben.
>>=20
>>> On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:
>>>=20
>>> [fixing cc-list]
>>>=20
>>>> On 10/21/16 11:59 AM, Flemming Andreasen wrote:
>>>>=20
>>>>=20
>>>>> On 10/21/16 11:21 AM, Cullen Jennings wrote:
>>>>> I think that is a bad way to run a WG. All I asked for was a phone ca=
ll to discuss this so we could get the issues on the table and discuss what=
 is best. The chairs never even replied to my request for a WG call to disc=
uss this.
>>>> That is simply not true. You (and Christer) were explicitly asked to s=
etup a phone call on 10/6/16 to discuss this issue; a request that (like ma=
ny other others) went unanswered or required extensive prodding to get any =
attention.
>>>>=20
>>>>> The list discussions that ensued from this resulted in people other t=
han me sugesting possibilities that were much better than any of the three =
below -  none of which were considered in your consensus call.
>>>> I'm not sure what those proposals are, nor were they brought up in res=
ponse to the consensus call.
>>>>=20
>>>>> I don=92t plan to appeal this but I am considering if it=92s worth my=
 time to participate in this WG if we are not going to be willing to actual=
ly spend a short time to discuss possible solutions before taking a consens=
us call.  As input to that decisions, it would be really useful to know why=
 you refused to have a phone call on this topic and what your policy in gen=
eral is going to be toward discussions of proposed solutions to problems in=
 the future.
>>>> My position is that we will try our very best to get to not only conse=
nsus but to satisfy as many concerns as we possibly can. It does however re=
quire people to engage in a timely manner, and even when they don't, we sti=
ll do what we can, but at some point we need to move forward. As for the is=
sue at hand, it has been discussed extensively, and several changes were ma=
de to the draft to try and accommodate your requests.
>>>>=20
>>>> The one major remaining issue I believe you have is around whether thi=
s document updates RFC 4572. This has been discussed extensively on the wgc=
hairs list; a discussion I initiated to try and help address your concern. =
You may disagree with how that discussion concluded, but again, to try and =
alleviate your concerns, a note was added to 4572-update to make it clear t=
hat the document does not make existing 4572 implementations non-compliant =
with RFC 4572.
>>>>=20
>>>> I believe the chairs, authors, and the WG at large has done everything=
 that can reasonably be done to try and address your concerns, and at this =
point we need to move forward.
>>>>=20
>>>> Thanks
>>>>=20
>>>> -- Flemming (as MMUSIC co-chair)
>>>>=20
>>>>=20
>>>>=20
>>>>>=20
>>>>>> On Oct 19, 2016, at 6:43 AM, Flemming Andreasen <fandreas@cisco.com>=
 wrote:
>>>>>>=20
>>>>>> Hi
>>>>>>=20
>>>>>> Following up on the consensus call, we have received 5 responses in =
favor of option a) below, one neutral, and one objection. Looking at the do=
cument we have noted that backwards compatibility is handled by the current=
 text in the document and it also clearly states that it does not make curr=
ent RFC 4572 implementation non-compliant with RFC 4572. Since we have not =
heard of any technical problems with proposal a), nor seen any tangible pro=
gress on how to address the objection, we are hereby declaring rough consen=
sus on option a). We will proceed with the publication request for the curr=
ent draft while duly noting the "roughness" of the consensus based on the p=
ending objection as part of this.
>>>>>>=20
>>>>>> Thanks
>>>>>>=20
>>>>>>    Flemming & Bo (MMUSIC chairs)
>>>>>>=20
>>>>>>=20
>>>>>>> On 10/12/16 6:23 PM, Flemming Andreasen wrote:
>>>>>>> Greetings
>>>>>>>=20
>>>>>>> There has been quite a bit of discussion on draft-ietf-mmusic-4572-=
update (currently -07), which had previously completed WGLC when a few conc=
erns were raised. The document currently:
>>>>>>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
>>>>>>> 2. Updates the preferred cipher-suite with a stronger cipher suite
>>>>>>> 3. Updates RFC 4572.
>>>>>>>=20
>>>>>>> Item 1 seems to be generally agreeable, whereas items 2 and 3 are n=
ot. The chairs are hereby soliciting WG feedback on how to proceed based on=
 the following choices:
>>>>>>>=20
>>>>>>> a) Proceed with publication of 4572-update-07 in its current form (=
i.e. covering all 3 items above)
>>>>>>>=20
>>>>>>> b) Remove item 2 from 4572-update, i.e. do not update the preferred=
 cipher-suite
>>>>>>>=20
>>>>>>> c) Remove item 3 from 4572-update, i.e. do not indicate that this d=
ocument constitutes an update to RFC 4572.
>>>>>>>=20
>>>>>>>=20
>>>>>>> Note that choice a) is mutually exclusive with b) and c), but b) an=
d c) are not mutually exclusive.
>>>>>>>=20
>>>>>>> Please let us know your preference wrt to the above no later than F=
riday October 14th.
>>>>>>>=20
>>>>>>>=20
>>>>>>> Thanks
>>>>>>>=20
>>>>>>>       Flemming & Bo (MMUSIC chairs)
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> mmusic mailing list
>>>>>>> mmusic@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>>>>> .
>>>>>>>=20
>>>>>> _______________________________________________
>>>>>> mmusic mailing list
>>>>>> mmusic@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>>> .
>>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> mmusic mailing list
>>>> mmusic@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>=20
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>=20
>> .
>>=20
>=20


From nobody Mon Oct 24 22:08:42 2016
Return-Path: <ekr@rtfm.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 7A3721297E4 for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 22:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yECQVMBR8jei for <mmusic@ietfa.amsl.com>; Mon, 24 Oct 2016 22:08:38 -0700 (PDT)
Received: from mail-yb0-x229.google.com (mail-yb0-x229.google.com [IPv6:2607:f8b0:4002:c09::229]) (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 E2704129762 for <mmusic@ietf.org>; Mon, 24 Oct 2016 22:08:37 -0700 (PDT)
Received: by mail-yb0-x229.google.com with SMTP id 205so10286935ybz.5 for <mmusic@ietf.org>; Mon, 24 Oct 2016 22:08:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IICEGAGezAFHxFkHzWhZKvzX9GaTYKxXhnEMbU2Qpr8=; b=02JNcc32vmB/L4JNn3Q7eucS9P9TgwjtSRu8nHP5huyLb2PfzymIRvUsXTE+iMvc+P oAHysSx8XgeJXs4VNN6Eg/zMwMlH9V6bnjiY8dSdEOb+LYzjvKDNisHqAqdegbSOklHR Ho7gx7npiwZSy1xSiLqno9RQ+RxWbO0jwes2ygky2u4e+qnGE2a+ngau1Jto65c4a4wC 5VRwy0lzEWtANY9GDp1ExWX0pQEBa3HSpGTk5uK2dr61O29ZzDy7el3vXPmKDiJ8oSha DVzI6maRmN6NTX9yLNDsJ6Yo+MISCLAwZNqqrhUs7no/dkocPOY9dUwNPUqkjIncgV8p aY2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IICEGAGezAFHxFkHzWhZKvzX9GaTYKxXhnEMbU2Qpr8=; b=Ol4JhXP7mJ5c1NfI0BF/MiL3zE775mXBgiYD7xq9pe/JgIew8yByoJZj+kFvIwy0Ve XLmo4TmEV2QH4sbp/AnEkx5XSJIRgUbxkGHQsWZ6FIqX5rD4PYgiK0icLfQr9x2MCBXV kSp7XJ6Zbde6+lSTL1x0ZKW7jbGqH9vtfSbf/njMoQJyi5G0P5MwhDzQVsi5mMjo0LFU 0LUFjbqRRtWaUjTZcGsxgvEeep3croPCjsW7S8Wb5bEvtBLa6zObdnwuB1U0dLr643KN vtxI68z8zaiUza0k4YkA7tuTYUhcDV7ARTARHv8YX1E0FXtegbjKSyYFpB+3shaQU+zH 0Y/w==
X-Gm-Message-State: ABUngvcO1N0udbQHfdfcJBxXqxIGeHuysLzkWlI4cRnrSaxGnnnX7LWpxoGOM7MwuFfuzjXNK90wQdwnUvzk1A==
X-Received: by 10.37.246.15 with SMTP id t15mr20607065ybd.107.1477372117100; Mon, 24 Oct 2016 22:08:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.82.210 with HTTP; Mon, 24 Oct 2016 22:07:56 -0700 (PDT)
In-Reply-To: <32BBB414-85BA-484C-954D-EDC8620F26DF@ericsson.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <32BBB414-85BA-484C-954D-EDC8620F26DF@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 25 Oct 2016 16:07:56 +1100
Message-ID: <CABcZeBNKGK92=6moFbQ_4x1GuLoAZqQBrLZtY_AFnv6+iTnmyw@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=f403045da0a63e1ca7053fa980c8
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/8OYIeD3uItpgs5Fu4phXK45mnVs>
Cc: Flemming Andreasen <fandreas@cisco.com>, Ben Campbell <ben@nostrum.com>, ART ADs <art-ads@ietf.org>, mmusic <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 05:08:40 -0000

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

I am in Australia this week so next week would be easier. Otherwise, please
make it late Pacific time so that it's not too early.

-Ekr


On Tue, Oct 25, 2016 at 3:33 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi Flemming,
>
> Any day but Monday works for me.
>
> Regards,
>
> Christer
>
> Sent from my iPhone
>
> > On 25 Oct 2016, at 7.01, Flemming Andreasen <fandreas@cisco.com> wrote:
> >
> > Hi Ben
> >
> > We will get a poll setup as soon as we understand any major constraints
> from the key participants.
> >
> > Thanks
> >
> > -- Flemming
> >
> >
> >> On 10/21/16 4:49 PM, Ben Campbell wrote:
> >> Hi Everyone, please accept my apologies for waiting this long to weigh
> in.
> >>
> >> I think it's clear that multiple people are not happy with how we got
> to this point. But assigning blame doesn't help us make progress on the
> draft. I propose that we get over that, and instead focus instead on how =
to
> move forward. Email discussion doesn't seem to be helping. Maybe a call
> will.
> >>
> >> Flemming and/or Bo: Can you set up a Doodle poll to get Christer,
> Cullen, and other demonstratively  interested parties on a conference cal=
l?
> I will join if at all possible, but don't let scheduling around me stop a
> call from happening.
> >>
> >> Thanks!
> >>
> >> Ben.
> >>
> >>> On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:
> >>>
> >>> [fixing cc-list]
> >>>
> >>>> On 10/21/16 11:59 AM, Flemming Andreasen wrote:
> >>>>
> >>>>
> >>>>> On 10/21/16 11:21 AM, Cullen Jennings wrote:
> >>>>> I think that is a bad way to run a WG. All I asked for was a phone
> call to discuss this so we could get the issues on the table and discuss
> what is best. The chairs never even replied to my request for a WG call t=
o
> discuss this.
> >>>> That is simply not true. You (and Christer) were explicitly asked to
> setup a phone call on 10/6/16 to discuss this issue; a request that (like
> many other others) went unanswered or required extensive prodding to get
> any attention.
> >>>>
> >>>>> The list discussions that ensued from this resulted in people other
> than me sugesting possibilities that were much better than any of the thr=
ee
> below -  none of which were considered in your consensus call.
> >>>> I'm not sure what those proposals are, nor were they brought up in
> response to the consensus call.
> >>>>
> >>>>> I don=E2=80=99t plan to appeal this but I am considering if it=E2=
=80=99s worth my
> time to participate in this WG if we are not going to be willing to
> actually spend a short time to discuss possible solutions before taking a
> consensus call.  As input to that decisions, it would be really useful to
> know why you refused to have a phone call on this topic and what your
> policy in general is going to be toward discussions of proposed solutions
> to problems in the future.
> >>>> My position is that we will try our very best to get to not only
> consensus but to satisfy as many concerns as we possibly can. It does
> however require people to engage in a timely manner, and even when they
> don't, we still do what we can, but at some point we need to move forward=
.
> As for the issue at hand, it has been discussed extensively, and several
> changes were made to the draft to try and accommodate your requests.
> >>>>
> >>>> The one major remaining issue I believe you have is around whether
> this document updates RFC 4572. This has been discussed extensively on th=
e
> wgchairs list; a discussion I initiated to try and help address your
> concern. You may disagree with how that discussion concluded, but again, =
to
> try and alleviate your concerns, a note was added to 4572-update to make =
it
> clear that the document does not make existing 4572 implementations
> non-compliant with RFC 4572.
> >>>>
> >>>> I believe the chairs, authors, and the WG at large has done
> everything that can reasonably be done to try and address your concerns,
> and at this point we need to move forward.
> >>>>
> >>>> Thanks
> >>>>
> >>>> -- Flemming (as MMUSIC co-chair)
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>>> On Oct 19, 2016, at 6:43 AM, Flemming Andreasen <fandreas@cisco.co=
m>
> wrote:
> >>>>>>
> >>>>>> Hi
> >>>>>>
> >>>>>> Following up on the consensus call, we have received 5 responses i=
n
> favor of option a) below, one neutral, and one objection. Looking at the
> document we have noted that backwards compatibility is handled by the
> current text in the document and it also clearly states that it does not
> make current RFC 4572 implementation non-compliant with RFC 4572. Since w=
e
> have not heard of any technical problems with proposal a), nor seen any
> tangible progress on how to address the objection, we are hereby declarin=
g
> rough consensus on option a). We will proceed with the publication reques=
t
> for the current draft while duly noting the "roughness" of the consensus
> based on the pending objection as part of this.
> >>>>>>
> >>>>>> Thanks
> >>>>>>
> >>>>>>    Flemming & Bo (MMUSIC chairs)
> >>>>>>
> >>>>>>
> >>>>>>> On 10/12/16 6:23 PM, Flemming Andreasen wrote:
> >>>>>>> Greetings
> >>>>>>>
> >>>>>>> There has been quite a bit of discussion on
> draft-ietf-mmusic-4572-update (currently -07), which had previously
> completed WGLC when a few concerns were raised. The document currently:
> >>>>>>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
> >>>>>>> 2. Updates the preferred cipher-suite with a stronger cipher suit=
e
> >>>>>>> 3. Updates RFC 4572.
> >>>>>>>
> >>>>>>> Item 1 seems to be generally agreeable, whereas items 2 and 3 are
> not. The chairs are hereby soliciting WG feedback on how to proceed based
> on the following choices:
> >>>>>>>
> >>>>>>> a) Proceed with publication of 4572-update-07 in its current form
> (i.e. covering all 3 items above)
> >>>>>>>
> >>>>>>> b) Remove item 2 from 4572-update, i.e. do not update the
> preferred cipher-suite
> >>>>>>>
> >>>>>>> c) Remove item 3 from 4572-update, i.e. do not indicate that this
> document constitutes an update to RFC 4572.
> >>>>>>>
> >>>>>>>
> >>>>>>> Note that choice a) is mutually exclusive with b) and c), but b)
> and c) are not mutually exclusive.
> >>>>>>>
> >>>>>>> Please let us know your preference wrt to the above no later than
> Friday October 14th.
> >>>>>>>
> >>>>>>>
> >>>>>>> Thanks
> >>>>>>>
> >>>>>>>       Flemming & Bo (MMUSIC chairs)
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> 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
> >>>>> .
> >>>>>
> >>>>
> >>>> _______________________________________________
> >>>> 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
> >>
> >> .
> >>
> >
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">I am in Australia this week so next week would be easier. =
Otherwise, please make it late Pacific time so that it&#39;s not too early.=
<div><br><div>-Ekr</div><div><br></div></div></div><div class=3D"gmail_extr=
a"><br><div class=3D"gmail_quote">On Tue, Oct 25, 2016 at 3:33 PM, Christer=
 Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsso=
n.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">Hi Flemming,<br>
<br>
Any day but Monday works for me.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
Sent from my iPhone<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; On 25 Oct 2016, at 7.01, Flemming Andreasen &lt;<a href=3D"mailto:fand=
reas@cisco.com">fandreas@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Ben<br>
&gt;<br>
&gt; We will get a poll setup as soon as we understand any major constraint=
s from the key participants.<br>
&gt;<br>
&gt; Thanks<br>
&gt;<br>
&gt; -- Flemming<br>
&gt;<br>
&gt;<br>
&gt;&gt; On 10/21/16 4:49 PM, Ben Campbell wrote:<br>
&gt;&gt; Hi Everyone, please accept my apologies for waiting this long to w=
eigh in.<br>
&gt;&gt;<br>
&gt;&gt; I think it&#39;s clear that multiple people are not happy with how=
 we got to this point. But assigning blame doesn&#39;t help us make progres=
s on the draft. I propose that we get over that, and instead focus instead =
on how to move forward. Email discussion doesn&#39;t seem to be helping. Ma=
ybe a call will.<br>
&gt;&gt;<br>
&gt;&gt; Flemming and/or Bo: Can you set up a Doodle poll to get Christer, =
Cullen, and other demonstratively=C2=A0 interested parties on a conference =
call? I will join if at all possible, but don&#39;t let scheduling around m=
e stop a call from happening.<br>
&gt;&gt;<br>
&gt;&gt; Thanks!<br>
&gt;&gt;<br>
&gt;&gt; Ben.<br>
&gt;&gt;<br>
&gt;&gt;&gt; On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; [fixing cc-list]<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On 10/21/16 11:59 AM, Flemming Andreasen wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On 10/21/16 11:21 AM, Cullen Jennings wrote:<br>
&gt;&gt;&gt;&gt;&gt; I think that is a bad way to run a WG. All I asked for=
 was a phone call to discuss this so we could get the issues on the table a=
nd discuss what is best. The chairs never even replied to my request for a =
WG call to discuss this.<br>
&gt;&gt;&gt;&gt; That is simply not true. You (and Christer) were explicitl=
y asked to setup a phone call on 10/6/16 to discuss this issue; a request t=
hat (like many other others) went unanswered or required extensive prodding=
 to get any attention.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; The list discussions that ensued from this resulted in=
 people other than me sugesting possibilities that were much better than an=
y of the three below -=C2=A0 none of which were considered in your consensu=
s call.<br>
&gt;&gt;&gt;&gt; I&#39;m not sure what those proposals are, nor were they b=
rought up in response to the consensus call.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; I don=E2=80=99t plan to appeal this but I am consideri=
ng if it=E2=80=99s worth my time to participate in this WG if we are not go=
ing to be willing to actually spend a short time to discuss possible soluti=
ons before taking a consensus call.=C2=A0 As input to that decisions, it wo=
uld be really useful to know why you refused to have a phone call on this t=
opic and what your policy in general is going to be toward discussions of p=
roposed solutions to problems in the future.<br>
&gt;&gt;&gt;&gt; My position is that we will try our very best to get to no=
t only consensus but to satisfy as many concerns as we possibly can. It doe=
s however require people to engage in a timely manner, and even when they d=
on&#39;t, we still do what we can, but at some point we need to move forwar=
d. As for the issue at hand, it has been discussed extensively, and several=
 changes were made to the draft to try and accommodate your requests.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The one major remaining issue I believe you have is around=
 whether this document updates RFC 4572. This has been discussed extensivel=
y on the wgchairs list; a discussion I initiated to try and help address yo=
ur concern. You may disagree with how that discussion concluded, but again,=
 to try and alleviate your concerns, a note was added to 4572-update to mak=
e it clear that the document does not make existing 4572 implementations no=
n-compliant with RFC 4572.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I believe the chairs, authors, and the WG at large has don=
e everything that can reasonably be done to try and address your concerns, =
and at this point we need to move forward.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Thanks<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; -- Flemming (as MMUSIC co-chair)<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; On Oct 19, 2016, at 6:43 AM, Flemming Andreasen &l=
t;<a href=3D"mailto:fandreas@cisco.com">fandreas@cisco.com</a>&gt; wrote:<b=
r>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hi<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Following up on the consensus call, we have receiv=
ed 5 responses in favor of option a) below, one neutral, and one objection.=
 Looking at the document we have noted that backwards compatibility is hand=
led by the current text in the document and it also clearly states that it =
does not make current RFC 4572 implementation non-compliant with RFC 4572. =
Since we have not heard of any technical problems with proposal a), nor see=
n any tangible progress on how to address the objection, we are hereby decl=
aring rough consensus on option a). We will proceed with the publication re=
quest for the current draft while duly noting the &quot;roughness&quot; of =
the consensus based on the pending objection as part of this.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 Flemming &amp; Bo (MMUSIC chairs)<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; On 10/12/16 6:23 PM, Flemming Andreasen wrote:=
<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Greetings<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; There has been quite a bit of discussion on dr=
aft-ietf-mmusic-4572-update (currently -07), which had previously completed=
 WGLC when a few concerns were raised. The document currently:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. Clarifies the usage of multiple SDP &#39;fi=
ngerprint&#39; attributes<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. Updates the preferred cipher-suite with a s=
tronger cipher suite<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 3. Updates RFC 4572.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Item 1 seems to be generally agreeable, wherea=
s items 2 and 3 are not. The chairs are hereby soliciting WG feedback on ho=
w to proceed based on the following choices:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; a) Proceed with publication of 4572-update-07 =
in its current form (i.e. covering all 3 items above)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; b) Remove item 2 from 4572-update, i.e. do not=
 update the preferred cipher-suite<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; c) Remove item 3 from 4572-update, i.e. do not=
 indicate that this document constitutes an update to RFC 4572.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Note that choice a) is mutually exclusive with=
 b) and c), but b) and c) are not mutually exclusive.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Please let us know your preference wrt to the =
above no later than Friday October 14th.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Flemming &amp; Bo (M=
MUSIC chairs)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; ______________________________<wbr>___________=
______<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; mmusic mailing list<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf=
.org</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listin=
fo/mmusic" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailma=
n/<wbr>listinfo/mmusic</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; .<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; ______________________________<wbr>_______________=
__<br>
&gt;&gt;&gt;&gt;&gt;&gt; mmusic mailing list<br>
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org=
</a><br>
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/m=
music" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<w=
br>listinfo/mmusic</a><br>
&gt;&gt;&gt;&gt;&gt; .<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt;&gt;&gt; mmusic mailing list<br>
&gt;&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" r=
el=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listi=
nfo/mmusic</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt;&gt; mmusic mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinf=
o/mmusic</a><br>
&gt;&gt;<br>
&gt;&gt; .<br>
&gt;&gt;<br>
&gt;<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div>

--f403045da0a63e1ca7053fa980c8--


From nobody Tue Oct 25 02:01:16 2016
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 B693E129480 for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 02:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 xDmIN6UA7C-S for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 02:01:11 -0700 (PDT)
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 3A21A126B6D for <mmusic@ietf.org>; Tue, 25 Oct 2016 02:01:11 -0700 (PDT)
X-AuditID: c1b4fb25-14bff7000000793b-36-580f1f540f64
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by  (Symantec Mail Security) with SMTP id 74.AF.31035.45F1F085; Tue, 25 Oct 2016 11:01:09 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0319.002; Tue, 25 Oct 2016 11:01:08 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
Thread-Index: AQHSKq8ixsJ53smzZ0iYfg1cr+NRB6CxH5OAgAA8sICAAHDegIAAChaAgACYYoCAADzBAIAFSssA///g/oCAACK7oIAA/y0A
Date: Tue, 25 Oct 2016 09:01:07 +0000
Message-ID: <D434FAF3.11AF5%christer.holmberg@ericsson.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com> <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com> <D42E97C0.117A6%christer.holmberg@ericsson.com> <AAE65171-77D6-4100-BED6-70DCFF98798D@gmail.com> <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com> <D55D7C56-4618-4C75-A2A7-F731F4A1142D@gmail.com> <D42FB1C3.1184E%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B4BDC9F9A@ESESSMB209.ericsson.se> <0b8867ae-3480-3386-2fc1-d505caa1da59@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B4BDCA012@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BDCA012@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <DF7B95B87A8580479C9D30D4C56FCA20@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsUyM2K7vW6oPH+EwazX0hZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJWx/fZctoJtPBVrp1k1MP7n7GLk5JAQMJHY vWAjUxcjF4eQwHpGiRPr1rNAOIsZJVrnHWfuYuTgYBOwkOj+pw0SFxFoZpS4dn45C0i3sECM xK2Vf9hBbBGBWImrZ96zQth5Et+fLWEDsVkEVCV2/58OVsMrYC0xrf0VO8SC9ywSM7/NYQJJ cAr4SZy69YMZxGYUEJP4fmoNWJxZQFzi1pP5TBCnCkgs2XOeGcIWlXj5+B8ryHGiAnoSa+6H gZgSAkoS07amQXTqSdyYOoUNwraW2DDpOCOErS2xbOFrZohzBCVOznzCMoFRbBaSZbOQtM9C 0j4LSfssJO0LGFlXMYoWpxYn5aYbGeulFmUmFxfn5+nlpZZsYgRG1cEtv1V3MF5+43iIUYCD UYmHV8GHL0KINbGsuDL3EKMEB7OSCO8fYf4IId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rxmK++H CwmkJ5akZqemFqQWwWSZODilGhhVzy3V3dPG7bRz4xX2DPdYUXlbdmE2c791V5t/vdGx2qa1 4rK48MOQe/bXEoXCtmyafYhzW8QzdUXZg+k3RaULvq5O38rB+uWDceKmnx13I37/vMpi/u3n rfubOFb9qNnut/VXfEDZvO4jXfdFTY4e+xLy7a+qy59niTJf+MpqWd1ljDu35WxVYinOSDTU Yi4qTgQAHcCq6aYCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/P7NiDe0p_qpvqn78j-CRNtbzukc>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 09:01:16 -0000

Hi,

I=B9ve modified the WGLC pull request for draft-ietf-mmusic-sctp-sdp:

https://github.com/cdh4u/draft-sctp-sdp/pulls


The impacted ICE text now says:

"When an SDP offer or answer is sent, the rules in
   [I-D.ietf-mmusic-ice-sip-sdp] apply regarding when the proto value
   must match the transport protocol associated with the default
   candidate.

   If an endpoint switches between TCP-based and UDP-based candidates
   during a session the endpoint is not required to send an SDP offer in
   order to modify that proto value of the associated m- line.=B2

I guess the text in the second paragraph should also be put
draft-ice-sip-sdp, but I guess it doesn=B9t hurt to keep it also here.

Regards,

Christer






On 24/10/16 21:55, "mmusic on behalf of Christer Holmberg"
<mmusic-bounces@ietf.org on behalf of christer.holmberg@ericsson.com>
wrote:

>Hi,
>
>>> Maybe we, in draft-bfcpbis and draft-sctp-sdp simply could say: "the
>>>rules in ICE apply >>  regarding when the c/m- lines must match the
>>>default candidate".
>>>
>>> Then we'll deal with the issue in draft-ice-sip-sdp, and it won't stop
>>>progress of draft->> bfcpbis and draft-sctp-sdp.
>>
>> Seems like that would work. But of course they will still eventually
>>block on their=20
>> dependency to that draft.
>
>True. But, at least we'll get the drafts out of the WGs, IESG reviewed
>etc.
>
>Regards,
>
>Christer
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www.ietf.org/mailman/listinfo/mmusic


From nobody Tue Oct 25 02:34:55 2016
Return-Path: <ibc@aliax.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 C8EDA12947E for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 02:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aliax-net.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 tfEmO6CMFIxd for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 02:34:50 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74A73129571 for <mmusic@ietf.org>; Tue, 25 Oct 2016 02:26:07 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id b80so152037811wme.1 for <mmusic@ietf.org>; Tue, 25 Oct 2016 02:26:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aliax-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=JMKdrCY3CvZ7l/tHTtsBvacNxUzuTfOgjEVfe2JTynk=; b=WIBofYtaMxdLmZyDkK35rERPLe2W+l7X7GcJEC+d+xDSP6+fS/Ld0Y/umr3l1PNM7L pbrvltp3n7ldQL9VYrT4UXYzkhzbWNIxC+YRgtOkq6gfnUJzZQwqEnGjowhyQbSfXwwd QcoXop11dBY17r/1ImaqevwNMQ2R+xO3exTINW3sgP5P3ZbwEuIezOANSzouCVoa/ifd vMTMOLf+3i7QhupR4exCjNgtZVCWeAdmTGoo1uZy5M6xI7COu8gdteeRGQu11rN/bUEB 5B/gR9Q+ML+ZNr7qxXdulTmC5MVeUHdMA5jNpfMYaGAhXTYiDmYT7+Bn3E8vDFw6KE9I +y4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=JMKdrCY3CvZ7l/tHTtsBvacNxUzuTfOgjEVfe2JTynk=; b=GmcjLd2jTOjzvU1+MvD6uGSa+GAEmy372rtC2SjcZcEAQtoMw5KDwkU5vbS6NrDpVe c+dFm1TeHytAEEKSJl7BmB1QZspK/a9rU1fEXbzlxk8ISV+GnyYyyN1sy7B7cjV5QVti Wsa7HYJttf41ZGUKtU7+oxHE2Mtf7iR0MNKV+FL1KbcgD8ukQHYaiIAkkcYUmu7GdmOg G2iX3+iBSZceIs5X6Jl08yBLrBs/Bq+ysvnhyvVxizFllTbX3ncOu3Ng5Kn553GEKNRE LeO3v7FpuaWO+l5x3GLZeFKfd44wGu77NVuvB5KNNOHCGBIEISqQ0tMzzYqMcOatpAQd ZUGw==
X-Gm-Message-State: ABUngvfqzOyo61Ep5IS0Fgtt0pyw9mgl4/W3WcGqdKiiX4+9JL8Gb+/QzSPh6/rrdX7+G8I0varq9CYQO9wbMA==
X-Received: by 10.28.194.134 with SMTP id s128mr2242730wmf.26.1477387566024; Tue, 25 Oct 2016 02:26:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.134.25 with HTTP; Tue, 25 Oct 2016 02:25:45 -0700 (PDT)
In-Reply-To: <CAD5OKxte9UhFtgUjExBK_hedTUOWwZiMwzUbJSQxd9nAY+w1dg@mail.gmail.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <CALiegfn2wEnOtJB2XsAckedAOsDVBa-ZN0ht+mVcT+YxgTxzcA@mail.gmail.com> <CAD5OKxte9UhFtgUjExBK_hedTUOWwZiMwzUbJSQxd9nAY+w1dg@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Tue, 25 Oct 2016 11:25:45 +0200
Message-ID: <CALiegfkDn8ws-2_Sq_qBhLxkzsb9VjG_dAvhenZARaU4xWk7PQ@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/8G8Zv9qMiqGNZZvVKJMTO1_Fu7o>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 09:34:53 -0000

2016-10-25 0:23 GMT+02:00 Roman Shpount <roman@telurix.com>:
> 2. In cases where ICE is required and non-ICE answer will not be accepted=
,
> define a new transport tag ICE such as ICE/DTLS/SCPT.

Yes please. In fact, ICE is a (virtual) transport (which can use UDP,
TCP, SCTP or whatever behind the scenes), so it fits perfectly in
there.


--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>


From nobody Tue Oct 25 02:36:27 2016
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 CD5E7129571 for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 02:36:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 5OgRudi89OyB for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 02:36:24 -0700 (PDT)
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 666AF1293E3 for <mmusic@ietf.org>; Tue, 25 Oct 2016 02:36:24 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-8a-580f27966a7c
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by  (Symantec Mail Security) with SMTP id E1.F8.02551.6972F085; Tue, 25 Oct 2016 11:36:22 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0319.002; Tue, 25 Oct 2016 11:36:20 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
Thread-Index: AQHSLjdzj3awKXzlYk+bYItwcSt6eaC4DHMAgAC5HYCAADdCgA==
Date: Tue, 25 Oct 2016 09:36:20 +0000
Message-ID: <D43502BA.11B0E%christer.holmberg@ericsson.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <CALiegfn2wEnOtJB2XsAckedAOsDVBa-ZN0ht+mVcT+YxgTxzcA@mail.gmail.com> <CAD5OKxte9UhFtgUjExBK_hedTUOWwZiMwzUbJSQxd9nAY+w1dg@mail.gmail.com> <CALiegfkDn8ws-2_Sq_qBhLxkzsb9VjG_dAvhenZARaU4xWk7PQ@mail.gmail.com>
In-Reply-To: <CALiegfkDn8ws-2_Sq_qBhLxkzsb9VjG_dAvhenZARaU4xWk7PQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5A1248BA9D414D4DB5463436F868387A@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCIsWRmVeSWpSXmKPExsUyM2K7n+40df4Ig33PjCym77OxmLr8MYvF jAtTmR2YPc41vGf3WLLkJ5PHrSkFAcxRXDYpqTmZZalF+nYJXBl7j21gKtjJWrFndhNbA+MK li5GTg4JAROJd5/vsnYxcnEICaxnlFg28yALhLOYUeLxpDNMXYwcHGwCFhLd/7RBGkQE4iTu bZ/OBhJmFlCXuLo4CCQsLBAjcWvlH3aIkliJq2fes0LYThKz939nBLFZBFQlJv3vZAZp5RWw lphwJhRi0wQmiYOrr4P1cgoESkzb1AFmMwqISXw/tYYJxGYWEJe49WQ+E8TNAhJL9pxnhrBF JV4+/scKMlNUQE9izf0wiLCixMdX+xghWvUkbkydAnWxtcSUN+UQYW2JZQtfg03hFRCUODnz CcsERvFZSJbNQtI9C6F7FpLuWUi6FzCyrmIULU4tLs5NNzLWSy3KTC4uzs/Ty0st2cQIjLuD W37r7mBc/drxEKMAB6MSD6+CD1+EEGtiWXFl7iFGCQ5mJRHe/0r8EUK8KYmVValF+fFFpTmp xYcYpTlYlMR5zVbeDxcSSE8sSc1OTS1ILYLJMnFwSjUwZptw73pg+5H9s9Ad9yC3nroFiwL7 T3NccpEXf7jbz2+Rj5myp73DHV73J5xJDskdDKffWJ2cdynm/rbUg8tf3Wys/yk38+H6/89n 2V1jyEjNf7M7xid54SQ+Z6eTPJ9K62O+SPgUXo3h+mJf0rnzSuuiS3MlPu8N2jj3IXOF4KHT 2TsD30etUmIpzkg01GIuKk4EAOOGQRq3AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/By-E5CxxDStm9Fro8WF8HT6cUsM>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 09:36:26 -0000

Hi,

>>2. In cases where ICE is required and non-ICE answer will not be
>>accepted,
>> define a new transport tag ICE such as ICE/DTLS/SCPT.
>
>Yes please. In fact, ICE is a (virtual) transport (which can use UDP,
>TCP, SCTP or whatever behind the scenes), so it fits perfectly in
>there.

draft-sctp-sdp is in WGLC, so such must-use-ICE proto value should be
defined in a separate document. In addition, I assume it would also cover
other protocols than DTLS/SCTP.

In addition, we have added text in draft-sctp-sdp recommending against
usage of TCP to begin with (unless UDP doesn=B9t work), so I don=B9t think =
it
will be a problem for DTLS/SCTP.

Regards,

Christer



From nobody Tue Oct 25 03:22:55 2016
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 103641294C9; Tue, 25 Oct 2016 03:22:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147739097005.15220.16125708041095716046.idtracker@ietfa.amsl.com>
Date: Tue, 25 Oct 2016 03:22:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/vtwN8OnBYlyeirv_SAGSY8wCdiI>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-bundle-negotiation-35.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 10:22:50 -0000

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

        Title           : Negotiating Media Multiplexing Using the Session Description Protocol (SDP)
        Authors         : Christer Holmberg
                          Harald Tveit Alvestrand
                          Cullen Jennings
	Filename        : draft-ietf-mmusic-sdp-bundle-negotiation-35.txt
	Pages           : 56
	Date            : 2016-10-25

Abstract:
   This specification defines a new Session Description Protocol (SDP)
   Grouping Framework extension, 'BUNDLE'.  The extension can be used
   with the SDP Offer/Answer mechanism to negotiate the usage of a
   single address:port combination (BUNDLE address) for receiving media,
   referred to as bundled media, specified by multiple SDP media
   descriptions ("m=" lines).

   To assist endpoints in negotiating the use of bundle this
   specification defines a new SDP attribute, 'bundle-only', which can
   be used to request that specific media is only used if bundled.  The
   specification also updates RFC 3264, to allow usage of zero port
   values without meaning that media is rejected.

   There are multiple ways to correlate the bundled RTP packets with the
   appropriate media descriptions.  This specification defines a new
   Real-time Transport Protocol (RTP) source description (SDES) item and
   a new RTP header extension that provides an additional way to do this
   correlation by using them to carry a value that associates the RTP/
   RTCP packets with a specific media description.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation-35

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


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

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


From nobody Tue Oct 25 03:24:17 2016
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 705A1129463 for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 03:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 P5wgi2cd7lyn for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 03:24:14 -0700 (PDT)
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 2CF501293F9 for <mmusic@ietf.org>; Tue, 25 Oct 2016 03:24:14 -0700 (PDT)
X-AuditID: c1b4fb30-b87ff70000000cb2-ae-580f32cbd668
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by  (Symantec Mail Security) with SMTP id 4B.8D.03250.BC23F085; Tue, 25 Oct 2016 12:24:12 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0319.002; Tue, 25 Oct 2016 12:24:11 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: BUNDLE-35
Thread-Index: AQHSLqnsPP0zF3SZTUqnpUSMO9yr7A==
Date: Tue, 25 Oct 2016 10:24:09 +0000
Message-ID: <D4350F28.11B2F%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_D4350F2811B2Fchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNLMWRmVeSWpSXmKPExsUyM2K7qO4ZI/4Ig9kbVC2mLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujB8n7QvOc1Ys27CIqYFxHUcXIyeHhICJxI/+48xdjFwcQgLr GSVuvnjHAuEsZpTY3fmMqYuRg4NNwEKi+582SIOIgLrE1709zCBhYQFViX/z/SDCWhJvNqxg g7D1JFY9XApmswCVzNp/jhHE5hWwlnhxbz8TiM0oICbx/dQaMJtZQFzi1pP5TBD3CEgs2XOe GcIWlXj5+B8ryCpRoJlr7odBhBUldp5tZ4ZoTZDonX2RGWK8oMTJmU9YJjAKzUIydRaSsllI yiDiBhLvz81nhrC1JZYtfA1l60ts/HKWEcK2lng96TgjspoFjByrGEWLU4uTctONjPRSizKT i4vz8/TyUks2MQKj5OCW3wY7GF8+dzzEKMDBqMTDq+DDFyHEmlhWXJl7iFGCg1lJhHeCIX+E EG9KYmVValF+fFFpTmrxIUZpDhYlcV6zlffDhQTSE0tSs1NTC1KLYLJMHJxSDYzzD57r0r2b o3/4VyN3aPhU2c/9qr4CX1bxTT74gvW9BmfswuOfjDtUCn2MswSki3/KmNXmSE9oLfqTdsf1 zvLXdTssBToD1106mJlpckikyVd293euso9LV9jfs9zT31T/UfLGd8b3oRxfN7YuF768Qor7 FrO2X3iSupX3+Sfzf958I3duiqASS3FGoqEWc1FxIgAsZvc7jgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ovrYYMSN4a7HMPbLy0WGL0_MhEU>
Subject: [MMUSIC] Draft new version: BUNDLE-35
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 10:24:15 -0000

--_000_D4350F2811B2Fchristerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

I=92ve submitted a new version (-35) of BUNDLE.

The text now talks about =93associating RTP streams with m- lines=94 (inste=
ad of associating RTP packets).

Regards,

Christer

--_000_D4350F2811B2Fchristerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <ED29F1935780B542BE5C7AD4EA6D2016@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>I=92ve submitted a new version (-35) of BUNDLE.</div>
<div><br>
</div>
<div>The text now talks about =93associating RTP streams with m- lines=94 (=
instead of associating RTP packets).</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
</body>
</html>

--_000_D4350F2811B2Fchristerholmbergericssoncom_--


From nobody Tue Oct 25 05:04:57 2016
Return-Path: <eckelcu@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 1FF4B12954B for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 05:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.951
X-Spam-Level: 
X-Spam-Status: No, score=-14.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 dQ_hISDCrSXK for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 05:04:40 -0700 (PDT)
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 EC66C129533 for <mmusic@ietf.org>; Tue, 25 Oct 2016 05:04:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=22200; q=dns/txt; s=iport; t=1477397079; x=1478606679; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=jqBfYr6spI+dFcEsWN+xdKmk9P6XyhGHJe9th+ExXbY=; b=ADQTAC2VCDBV3KW9cSrNWAebFEfv6paXIDohssWPS5ZJjPm0q3kU9j7q eRzi4zsKN1F/RV599MUuy5VgwQji2B7W48j7ojVF+QGyr0HHzCIyVHVgi YsYPz+GicAgYlR/Oalu0Whq1C3Nm1EI0UoiC34YnQNXy8lWKWFfjY/pSx A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CCAQCcSQ9Y/5ldJa1cDgwBAQEBAgEBA?= =?us-ascii?q?QEIAQEBAYJ0PAEBAQEBHVh9B40uqz2CBxwBCoUwSgIagWE/FAECAQEBAQEBAWI?= =?us-ascii?q?ohGMBAQQBAQEgBEcbAgEIPwMCAgIlCxQRAgQBEohTDrRkjHoBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEXBYg6CIJQhF6CbSyCLwWUOIVeAYYpgwaGZ5ADkQgBHjYiPIN?= =?us-ascii?q?IfztyhWIHgSiBAAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.31,545,1473120000";  d="scan'208,217";a="339275428"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Oct 2016 12:04:39 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u9PC4dkm011149 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 25 Oct 2016 12:04:39 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 25 Oct 2016 07:04:38 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Tue, 25 Oct 2016 07:04:37 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
Thread-Index: AQHSKq8qtUcWGbh5CkG0U38XwL0WWaCxlOyAgAAIdYCAAKUYgIAAChaAgACYYoCAAAiFAIAFXigAgAAB3oCAAAFnAIAA7DWAgABUzoA=
Date: Tue, 25 Oct 2016 12:04:37 +0000
Message-ID: <DB860B88-836F-4034-8E4F-BFA0063C9AC8@cisco.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com> <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com> <D42E97C0.117A6%christer.holmberg@ericsson.com> <AAE65171-77D6-4100-BED6-70DCFF98798D@gmail.com> <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com> <D55D7C56-4618-4C75-A2A7-F731F4A1142D@gmail.com> <D42FB1C3.1184E%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B4BDC9F9A@ESESSMB209.ericsson.se> <0b8867ae-3480-3386-2fc1-d505caa1da59@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B4BDCA012@ESESSMB209.ericsson.se> <D434FAF3.11AF5%christer.holmberg@ericsson.com>
In-Reply-To: <D434FAF3.11AF5%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1b.0.161010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.237.131]
Content-Type: multipart/alternative; boundary="_000_DB860B88836F40348E4FBFA0063C9AC8ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/35mobfAQgUKOQmiR9FqpcPcYQdY>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 12:04:44 -0000

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

SGkgQ2hyaXN0ZXIsDQoNClRoaXMgc2VlbXMgbGlrZSBhIGdvb2QgYXBwcm9hY2ggdG8gbWUuIEkg
d2lsbCBzdWdnZXN0IHdlIGZvbGxvdyB0aGlzIHNhbWUgYXBwcm9hY2ggZm9yIGRyYWZ0LWlldGYt
YmZjcGJpcy1yZmM0NTgzYmlzIG9uIHRoZSBiZmNwYmlzIGxpc3QuDQoNCkNoZWVycywNCkNoYXJs
ZXMNCg0KT24gMTAvMjUvMTYsIDExOjAxIEFNLCAibW11c2ljIG9uIGJlaGFsZiBvZiBDaHJpc3Rl
ciBIb2xtYmVyZyIgPG1tdXNpYy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzptbXVzaWMtYm91bmNl
c0BpZXRmLm9yZz4gb24gYmVoYWxmIG9mIGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTxt
YWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPj4gd3JvdGU6DQoNCkhpLA0KDQpJ
wrl2ZSBtb2RpZmllZCB0aGUgV0dMQyBwdWxsIHJlcXVlc3QgZm9yIGRyYWZ0LWlldGYtbW11c2lj
LXNjdHAtc2RwOg0KDQpodHRwczovL2dpdGh1Yi5jb20vY2RoNHUvZHJhZnQtc2N0cC1zZHAvcHVs
bHMNCg0KDQpUaGUgaW1wYWN0ZWQgSUNFIHRleHQgbm93IHNheXM6DQoNCiJXaGVuIGFuIFNEUCBv
ZmZlciBvciBhbnN3ZXIgaXMgc2VudCwgdGhlIHJ1bGVzIGluDQogICBbSS1ELmlldGYtbW11c2lj
LWljZS1zaXAtc2RwXSBhcHBseSByZWdhcmRpbmcgd2hlbiB0aGUgcHJvdG8gdmFsdWUNCiAgIG11
c3QgbWF0Y2ggdGhlIHRyYW5zcG9ydCBwcm90b2NvbCBhc3NvY2lhdGVkIHdpdGggdGhlIGRlZmF1
bHQNCiAgIGNhbmRpZGF0ZS4NCg0KICAgSWYgYW4gZW5kcG9pbnQgc3dpdGNoZXMgYmV0d2VlbiBU
Q1AtYmFzZWQgYW5kIFVEUC1iYXNlZCBjYW5kaWRhdGVzDQogICBkdXJpbmcgYSBzZXNzaW9uIHRo
ZSBlbmRwb2ludCBpcyBub3QgcmVxdWlyZWQgdG8gc2VuZCBhbiBTRFAgb2ZmZXIgaW4NCiAgIG9y
ZGVyIHRvIG1vZGlmeSB0aGF0IHByb3RvIHZhbHVlIG9mIHRoZSBhc3NvY2lhdGVkIG0tIGxpbmUu
wrINCg0KSSBndWVzcyB0aGUgdGV4dCBpbiB0aGUgc2Vjb25kIHBhcmFncmFwaCBzaG91bGQgYWxz
byBiZSBwdXQNCmRyYWZ0LWljZS1zaXAtc2RwLCBidXQgSSBndWVzcyBpdCBkb2VzbsK5dCBodXJ0
IHRvIGtlZXAgaXQgYWxzbyBoZXJlLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoNCg0KDQoN
Cg0KT24gMjQvMTAvMTYgMjE6NTUsICJtbXVzaWMgb24gYmVoYWxmIG9mIENocmlzdGVyIEhvbG1i
ZXJnIg0KPG1tdXNpYy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzptbXVzaWMtYm91bmNlc0BpZXRm
Lm9yZz4gb24gYmVoYWxmIG9mIGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTxtYWlsdG86
Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPj4NCndyb3RlOg0KDQpIaSwNCg0KTWF5YmUg
d2UsIGluIGRyYWZ0LWJmY3BiaXMgYW5kIGRyYWZ0LXNjdHAtc2RwIHNpbXBseSBjb3VsZCBzYXk6
ICJ0aGUNCnJ1bGVzIGluIElDRSBhcHBseSA+PiAgcmVnYXJkaW5nIHdoZW4gdGhlIGMvbS0gbGlu
ZXMgbXVzdCBtYXRjaCB0aGUNCmRlZmF1bHQgY2FuZGlkYXRlIi4NCg0KVGhlbiB3ZSdsbCBkZWFs
IHdpdGggdGhlIGlzc3VlIGluIGRyYWZ0LWljZS1zaXAtc2RwLCBhbmQgaXQgd29uJ3Qgc3RvcA0K
cHJvZ3Jlc3Mgb2YgZHJhZnQtPj4gYmZjcGJpcyBhbmQgZHJhZnQtc2N0cC1zZHAuDQoNClNlZW1z
IGxpa2UgdGhhdCB3b3VsZCB3b3JrLiBCdXQgb2YgY291cnNlIHRoZXkgd2lsbCBzdGlsbCBldmVu
dHVhbGx5DQpibG9jayBvbiB0aGVpcg0KZGVwZW5kZW5jeSB0byB0aGF0IGRyYWZ0Lg0KDQpUcnVl
LiBCdXQsIGF0IGxlYXN0IHdlJ2xsIGdldCB0aGUgZHJhZnRzIG91dCBvZiB0aGUgV0dzLCBJRVNH
IHJldmlld2VkDQpldGMuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQptbXVzaWMgbWFpbGluZyBsaXN0DQpt
bXVzaWNAaWV0Zi5vcmc8bWFpbHRvOm1tdXNpY0BpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQptbXVzaWMgbWFpbGluZyBsaXN0DQptbXVzaWNAaWV0Zi5v
cmc8bWFpbHRvOm1tdXNpY0BpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vbW11c2ljDQoNCg==

--_000_DB860B88836F40348E4FBFA0063C9AC8ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <BD21DE7F4C6F5646927966EC687D2620@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpDb25zb2xhczsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBE
ZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0K
CXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0
Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO30NCmE6bGluaywgc3Bhbi5Nc29IeXBl
cmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNv
cmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRp
b246dW5kZXJsaW5lO30NCnNwYW4uYXBwbGUtc3R5bGUtc3Bhbg0KCXttc28tc3R5bGUtbmFtZTph
cHBsZS1zdHlsZS1zcGFuO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBl
cnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OkNhbGlicmk7DQoJY29sb3I6d2luZG93dGV4dDt9
DQpzcGFuLm1zb0lucw0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCgltc28tc3R5bGUt
bmFtZToiIjsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lOw0KCWNvbG9yOnRlYWw7fQ0KLk1z
b0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEw
LjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2lu
OjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3Jk
U2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT4NCjwvaGVhZD4NCjxib2R5IGJnY29sb3I9IndoaXRlIiBs
YW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3Jk
U2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+SGkgQ2hyaXN0ZXIsPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6Q2FsaWJyaSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
Q2FsaWJyaSI+VGhpcyBzZWVtcyBsaWtlIGEgZ29vZCBhcHByb2FjaCB0byBtZS4gSSB3aWxsIHN1
Z2dlc3Qgd2UgZm9sbG93IHRoaXMgc2FtZSBhcHByb2FjaCBmb3IgZHJhZnQtaWV0Zi1iZmNwYmlz
LXJmYzQ1ODNiaXMgb24gdGhlIGJmY3BiaXMgbGlzdC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTpDYWxpYnJpIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDYWxpYnJp
Ij5DaGVlcnMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+Q2hhcmxlczxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xp
ZCAjQjVDNERGIDQuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQ7bWFyZ2luLWxlZnQ6My43
NXB0O21hcmdpbi1yaWdodDowaW4iPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29s
YXM7Y29sb3I6YmxhY2siPk9uIDEwLzI1LzE2LCAxMTowMSBBTSwgJnF1b3Q7bW11c2ljIG9uIGJl
aGFsZiBvZiBDaHJpc3RlciBIb2xtYmVyZyZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1tdXNp
Yy1ib3VuY2VzQGlldGYub3JnIj5tbXVzaWMtYm91bmNlc0BpZXRmLm9yZzwvYT4gb24gYmVoYWxm
IG9mDQo8YSBocmVmPSJtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tIj5jaHJp
c3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29u
c29sYXM7Y29sb3I6YmxhY2siPkhpLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+ScK5dmUgbW9k
aWZpZWQgdGhlIFdHTEMgcHVsbCByZXF1ZXN0IGZvciBkcmFmdC1pZXRmLW1tdXNpYy1zY3RwLXNk
cDo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztj
b2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxhIGhyZWY9Imh0dHBzOi8vZ2l0aHViLmNvbS9j
ZGg0dS9kcmFmdC1zY3RwLXNkcC9wdWxscyI+aHR0cHM6Ly9naXRodWIuY29tL2NkaDR1L2RyYWZ0
LXNjdHAtc2RwL3B1bGxzPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6Ymxh
Y2siPlRoZSBpbXBhY3RlZCBJQ0UgdGV4dCBub3cgc2F5czo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6Ymxh
Y2siPiZxdW90O1doZW4gYW4gU0RQIG9mZmVyIG9yIGFuc3dlciBpcyBzZW50LCB0aGUgcnVsZXMg
aW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztj
b2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7IFtJLUQuaWV0Zi1tbXVzaWMtaWNlLXNpcC1zZHBdIGFw
cGx5IHJlZ2FyZGluZyB3aGVuIHRoZSBwcm90byB2YWx1ZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsg
bXVzdCBtYXRjaCB0aGUgdHJhbnNwb3J0IHByb3RvY29sIGFzc29jaWF0ZWQgd2l0aCB0aGUgZGVm
YXVsdDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFz
O2NvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsgY2FuZGlkYXRlLjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpi
bGFjayI+Jm5ic3A7Jm5ic3A7IElmIGFuIGVuZHBvaW50IHN3aXRjaGVzIGJldHdlZW4gVENQLWJh
c2VkIGFuZCBVRFAtYmFzZWQgY2FuZGlkYXRlczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsgZHVyaW5n
IGEgc2Vzc2lvbiB0aGUgZW5kcG9pbnQgaXMgbm90IHJlcXVpcmVkIHRvIHNlbmQgYW4gU0RQIG9m
ZmVyIGluPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29s
YXM7Y29sb3I6YmxhY2siPiZuYnNwOyZuYnNwOyBvcmRlciB0byBtb2RpZnkgdGhhdCBwcm90byB2
YWx1ZSBvZiB0aGUgYXNzb2NpYXRlZCBtLSBsaW5lLsKyPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNr
Ij5JIGd1ZXNzIHRoZSB0ZXh0IGluIHRoZSBzZWNvbmQgcGFyYWdyYXBoIHNob3VsZCBhbHNvIGJl
IHB1dDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFz
O2NvbG9yOmJsYWNrIj5kcmFmdC1pY2Utc2lwLXNkcCwgYnV0IEkgZ3Vlc3MgaXQgZG9lc27CuXQg
aHVydCB0byBrZWVwIGl0IGFsc28gaGVyZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPlJlZ2Fy
ZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7
Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj5DaHJpc3RlcjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpi
bGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7
Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj5PbiAyNC8xMC8xNiAyMTo1NSwgJnF1b3Q7bW11
c2ljIG9uIGJlaGFsZiBvZiBDaHJpc3RlciBIb2xtYmVyZyZxdW90OzxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj4mbHQ7PGEg
aHJlZj0ibWFpbHRvOm1tdXNpYy1ib3VuY2VzQGlldGYub3JnIj5tbXVzaWMtYm91bmNlc0BpZXRm
Lm9yZzwvYT4gb24gYmVoYWxmIG9mDQo8YSBocmVmPSJtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdA
ZXJpY3Nzb24uY29tIj5jaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb208L2E+Jmd0OzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJs
YWNrIj53cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpD
b25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0I1QzRE
RiA0LjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0O21hcmdpbi1sZWZ0OjMuNzVwdDttYXJn
aW4tcmlnaHQ6MGluIiBpZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05fQkxPQ0tRVU9URSI+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPkhpLDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItbGVmdDpzb2xpZCAjQjVDNERGIDQuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4w
cHQ7bWFyZ2luLWxlZnQ6My43NXB0O21hcmdpbi1yaWdodDowaW4iIGlkPSJNQUNfT1VUTE9PS19B
VFRSSUJVVElPTl9CTE9DS1FVT1RFIj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItbGVmdDpzb2xpZCAjQjVDNERGIDQuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQ7
bWFyZ2luLWxlZnQ6My43NXB0O21hcmdpbi1yaWdodDowaW4iIGlkPSJNQUNfT1VUTE9PS19BVFRS
SUJVVElPTl9CTE9DS1FVT1RFIj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+
TWF5YmUgd2UsIGluIGRyYWZ0LWJmY3BiaXMgYW5kIGRyYWZ0LXNjdHAtc2RwIHNpbXBseSBjb3Vs
ZCBzYXk6ICZxdW90O3RoZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj5ydWxlcyBpbiBJQ0UgYXBwbHkgJmd0OyZndDsmbmJz
cDsmbmJzcDtyZWdhcmRpbmcgd2hlbiB0aGUgYy9tLSBsaW5lcyBtdXN0IG1hdGNoIHRoZTxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJs
YWNrIj5kZWZhdWx0IGNhbmRpZGF0ZSZxdW90Oy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPlRo
ZW4gd2UnbGwgZGVhbCB3aXRoIHRoZSBpc3N1ZSBpbiBkcmFmdC1pY2Utc2lwLXNkcCwgYW5kIGl0
IHdvbid0IHN0b3A8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpD
b25zb2xhcztjb2xvcjpibGFjayI+cHJvZ3Jlc3Mgb2YgZHJhZnQtJmd0OyZndDsgYmZjcGJpcyBh
bmQgZHJhZnQtc2N0cC1zZHAuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Jsb2Nr
cXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNr
Ij5TZWVtcyBsaWtlIHRoYXQgd291bGQgd29yay4gQnV0IG9mIGNvdXJzZSB0aGV5IHdpbGwgc3Rp
bGwgZXZlbnR1YWxseTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj5ibG9jayBvbiB0aGVpcg0KPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPmRlcGVuZGVu
Y3kgdG8gdGhhdCBkcmFmdC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvYmxvY2tx
dW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2si
PlRydWUuIEJ1dCwgYXQgbGVhc3Qgd2UnbGwgZ2V0IHRoZSBkcmFmdHMgb3V0IG9mIHRoZSBXR3Ms
IElFU0cgcmV2aWV3ZWQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTpDb25zb2xhcztjb2xvcjpibGFjayI+ZXRjLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+UmVn
YXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xh
cztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPkNocmlzdGVyPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9y
OmJsYWNrIj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9y
OmJsYWNrIj5tbXVzaWMgbWFpbGluZyBsaXN0PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxhIGhyZWY9Im1haWx0bzptbXVz
aWNAaWV0Zi5vcmciPm1tdXNpY0BpZXRmLm9yZzwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PGEgaHJlZj0iaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMiPmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xh
cztjb2xvcjpibGFjayI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX188bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xh
cztjb2xvcjpibGFjayI+bW11c2ljIG1haWxpbmcgbGlzdDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48YSBocmVmPSJtYWls
dG86bW11c2ljQGlldGYub3JnIj5tbXVzaWNAaWV0Zi5vcmc8L2E+PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxhIGhyZWY9
Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljIj5odHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYzwvYT48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2
Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_DB860B88836F40348E4FBFA0063C9AC8ciscocom_--


From nobody Tue Oct 25 05:18:24 2016
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 BAFE4129637 for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 05:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 RSDUiIxghF5b for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 05:18:21 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (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 40289129532 for <mmusic@ietf.org>; Tue, 25 Oct 2016 05:18:21 -0700 (PDT)
Received: by mail-qk0-x22d.google.com with SMTP id d23so6941451qke.7 for <mmusic@ietf.org>; Tue, 25 Oct 2016 05:18:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YW+C/ghytaCvaadhkr+8PF/BNxuCaF+MmkEhU2Ctbbc=; b=tJugy3yGAc8hJYw3hxUz73ONsy2mEyb4OF76ytxsK87e2edQpDQbl+YO4/+N7uovpE HTsLPkoT1/A94BzUB40q4mR7xfs/9wEnzPGMeszjWys+z1cHvlOualCxVi0pcIAWcur0 HUVhgS/QUVd7mrn1sC/wfLtJ+9F24VCYU5xDF6ojTAG1+GmtiU3D705Ct/F5fL6cn8Zy i7+lCwdzb6++1p73HSMWjFUaMom4s/0LgCFPzsrG7UEjxZMS13qtYJ+k4Xci6fw5ogcv fUGBZkmmLEAGHA/1CbhXg8XnAzZemr5xLKtOmKXEAqQISpXxq3QYedeLWrg9AOWOqr4+ LVLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YW+C/ghytaCvaadhkr+8PF/BNxuCaF+MmkEhU2Ctbbc=; b=QI6xAUG8hV0Er7H4ID1mRnOsCqoQqmxMV/lXI8rLCnE0ipXnp0ZDrueDyoBQY/C2br wR93IAshIKc6oiu0VrKgotO/0tIj8G4pczIf3yziXpjcWU1NWaOG30k24n06+n5q4wPG 8qpdpD5VPZB+4Ra8pwVl196XgL/AaLLrGjJ4R9AEhMXaPo/l7RNhFGG12WfJZIBcdD5z 697oqcCSKH44KGNmweJudivhNdCqP6tEh3mkEwgHECW0P0wd2JSIQYAbtlt1TD1kr6qX CyZ98VJ2m1UKWodOQ5E0kz0FLYgpM2dWb874tG5K5d1xFz6FX59RmXlAq/eKlAiQlGmR ORZQ==
X-Gm-Message-State: ABUngvc8h3ET+OLSDmXBzmfFDlNMRfApbJGxQwXHBrTpQA0qrUnz6pvzd6UsujmJNCbnZw==
X-Received: by 10.233.235.67 with SMTP id b64mr10521679qkg.156.1477397899823;  Tue, 25 Oct 2016 05:18:19 -0700 (PDT)
Received: from mail-qk0-f171.google.com (mail-qk0-f171.google.com. [209.85.220.171]) by smtp.gmail.com with ESMTPSA id p63sm10928053qtd.35.2016.10.25.05.18.19 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Oct 2016 05:18:19 -0700 (PDT)
Received: by mail-qk0-f171.google.com with SMTP id z190so257781779qkc.2 for <mmusic@ietf.org>; Tue, 25 Oct 2016 05:18:19 -0700 (PDT)
X-Received: by 10.55.39.202 with SMTP id n193mr16686473qkn.252.1477397899049;  Tue, 25 Oct 2016 05:18:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.132.161 with HTTP; Tue, 25 Oct 2016 05:18:18 -0700 (PDT)
In-Reply-To: <fb2a8750-afce-a082-4f47-6ed9c54d9847@alum.mit.edu>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <CALiegfn2wEnOtJB2XsAckedAOsDVBa-ZN0ht+mVcT+YxgTxzcA@mail.gmail.com> <CAD5OKxte9UhFtgUjExBK_hedTUOWwZiMwzUbJSQxd9nAY+w1dg@mail.gmail.com> <fb2a8750-afce-a082-4f47-6ed9c54d9847@alum.mit.edu>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 25 Oct 2016 08:18:18 -0400
X-Gmail-Original-Message-ID: <CAD5OKxu81Hb4ExyWd2dKH2Vsa+=Qx4obMVtUiDDzHYgDLUprFw@mail.gmail.com>
Message-ID: <CAD5OKxu81Hb4ExyWd2dKH2Vsa+=Qx4obMVtUiDDzHYgDLUprFw@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=94eb2c0950eef70b60053faf804b
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/yGjEOJUsie2m4U1_FEFvKcYlWr8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 12:18:23 -0000

--94eb2c0950eef70b60053faf804b
Content-Type: text/plain; charset=UTF-8

On Mon, Oct 24, 2016 at 9:31 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> On 10/24/16 6:23 PM, Roman Shpount wrote:
>
>> My initial solution had two parts:
>>
>> 1. In cases where backwards compatibility with non-ICE endpoints is
>> required, require that ICE includes UDP candidates and uses UDP
>> candidate for default candidate. Essentially this considers UDP protocol
>> version and UDP candidate support required to implement and considers
>> TCP based protocol version and TCP ICE candidate support optional
>> extensions.
>>
>> 2. In cases where ICE is required and non-ICE answer will not be
>> accepted, define a new transport tag ICE such as ICE/DTLS/SCPT. In this
>> case no default candidate should be included. c= line should use
>> transport address IN IP4 127.0.0.1. m= line should use port 7 (discard).
>> In this case no additional re-INVITE should be sent when ICE nomination
>> process is completed. This should correspond to the normal use case for
>> WebRTC browsers.
>>
>
> How about:
>
> C=IN IP4 invalid
>
> 'invalid' is a syntactically valid FQDN and so can be used there, and we
> have precedent from anonymous.invalid to use it to signify an unusable
> address.
>
> It also occurs to me that with the expansion of TLDs, maybe somebody ought
> to reserve 'invalid' before somebody else reserves it to use it.
>

As far as I know, IN IP4 127.0.0.1 and m= line with port 7 are already used
by WebRTC enabled browsers to indicate that c= and m= line address should
be discarded. Unless there is a significant benefit in using 'invalid' TLD
in c= line, I do not see a reason to change the current implementations. I
think the main reason current implementations use  IN IP4 127.0.0.1 is
related to the fact that a lot of SDP end point implementations do not
support domain names in c= line.

Regards,
_____________
Roman Shpount

--94eb2c0950eef70b60053faf804b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure"><br></div></div><div class=3D"gmail_quote">On Mon, Oct 24, 2016 at 9:3=
1 PM, Paul Kyzivat <span dir=3D"ltr">&lt;<a href=3D"mailto:pkyzivat@alum.mi=
t.edu" target=3D"_blank">pkyzivat@alum.mit.edu</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gmail-">On 10=
/24/16 6:23 PM, Roman Shpount wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
My initial solution had two parts:<br>
<br>
1. In cases where backwards compatibility with non-ICE endpoints is<br>
required, require that ICE includes UDP candidates and uses UDP<br>
candidate for default candidate. Essentially this considers UDP protocol<br=
>
version and UDP candidate support required to implement and considers<br>
TCP based protocol version and TCP ICE candidate support optional<br>
extensions.<br>
<br>
2. In cases where ICE is required and non-ICE answer will not be<br>
accepted, define a new transport tag ICE such as ICE/DTLS/SCPT. In this<br>
case no default candidate should be included. c=3D line should use<br>
transport address IN IP4 127.0.0.1. m=3D line should use port 7 (discard).<=
br>
In this case no additional re-INVITE should be sent when ICE nomination<br>
process is completed. This should correspond to the normal use case for<br>
WebRTC browsers.<br>
</blockquote>
<br></span>
How about:<br>
<br>
C=3DIN IP4 invalid<br>
<br>
&#39;invalid&#39; is a syntactically valid FQDN and so can be used there, a=
nd we have precedent from anonymous.invalid to use it to signify an unusabl=
e address.<br>
<br>
It also occurs to me that with the expansion of TLDs, maybe somebody ought =
to reserve &#39;invalid&#39; before somebody else reserves it to use it.<br=
></blockquote><div><br></div><div>As far as I know, IN IP4 127.0.0.1 and m=
=3D line with port 7 are already used by WebRTC enabled browsers to indicat=
e that c=3D and m=3D line address should be discarded. Unless there is a si=
gnificant benefit in using &#39;invalid&#39; TLD in c=3D line, I do not see=
 a reason to change the current implementations. I think the main reason cu=
rrent implementations use =C2=A0IN IP4 127.0.0.1 is related to the fact tha=
t a lot of SDP end point implementations do not support domain names in c=
=3D line.</div><div><br></div><div>Regards,</div><div><div class=3D"gmail_s=
ignature">_____________<br>Roman Shpount</div></div><div>=C2=A0</div></div>=
</div></div>

--94eb2c0950eef70b60053faf804b--


From nobody Tue Oct 25 06:01:50 2016
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 6381A1294EF for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 06:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 zdmEu9NI2Ido for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 06:01:44 -0700 (PDT)
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 4384F1294B3 for <mmusic@ietf.org>; Tue, 25 Oct 2016 06:01:44 -0700 (PDT)
X-AuditID: c1b4fb25-5405a9800000793b-61-580f57b6e33e
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by  (Symantec Mail Security) with SMTP id 0E.96.31035.6B75F085; Tue, 25 Oct 2016 15:01:42 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0319.002; Tue, 25 Oct 2016 15:01:41 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
Thread-Index: AQHSKq8ixsJ53smzZ0iYfg1cr+NRB6CxH5OAgAA8sICAAHDegIAAChaAgACYYoCAADzBAIAFSssA///g/oCAACK7oIAA/y0A///++YCAAEQ/gA==
Date: Tue, 25 Oct 2016 13:01:41 +0000
Message-ID: <D435312F.11BDF%christer.holmberg@ericsson.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <D42E61A0.11767%christer.holmberg@ericsson.com> <405F15D5-FB4F-425D-A0E8-637F45EB0268@gmail.com> <D42E97C0.117A6%christer.holmberg@ericsson.com> <AAE65171-77D6-4100-BED6-70DCFF98798D@gmail.com> <CAD5OKxs_xWJEJt0-v0Cf2dDREqM4Cii6TvSqPrKU39oZsTRvYQ@mail.gmail.com> <D55D7C56-4618-4C75-A2A7-F731F4A1142D@gmail.com> <D42FB1C3.1184E%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B4BDC9F9A@ESESSMB209.ericsson.se> <0b8867ae-3480-3386-2fc1-d505caa1da59@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B4BDCA012@ESESSMB209.ericsson.se> <D434FAF3.11AF5%christer.holmberg@ericsson.com> <DB860B88-836F-4034-8E4F-BFA0063C9AC8@cisco.com>
In-Reply-To: <DB860B88-836F-4034-8E4F-BFA0063C9AC8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.147]
Content-Type: multipart/alternative; boundary="_000_D435312F11BDFchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCIsWRmVeSWpSXmKPExsUyM2K7k+62cP4Ig9O7tSw2zfrCZjF1+WMW ixUbDrBazLgwldmBxePv+w9MHlN+b2T1WLLkJ5PHrSkFASxRXDYpqTmZZalF+nYJXBltP76z FJz4wFix6ewF1gbG2a8Yuxg5OSQETCR+PHjO3MXIxSEksJ5R4vfpRlYIZzGjxIGzC9m6GDk4 2AQsJLr/aYPERUDic7e8YAHpFhaIkbi18g87iC0iECtx9cx7Vgi7TuLLqYtgNouAqkTj3KNg Nq+AtcSFX2ehFlxhlbj6oQNsEKeArcTGznNgRYwCYhLfT61hArGZBcQlbj2ZzwRxqoDEkj3n mSFsUYmXj/+xghwnKqAnseZ+GIgpIaAkMW1rGkRngsTU98tZINYKSpyc+YRlAqPILCRDZyEp m4WkDCKuJfHlxz42CFtRYkr3Q/ZZQBuYBTQl3jyshQhbS/zfsI0RWckCRo5VjKLFqcVJuelG xnqpRZnJxcX5eXp5qSWbGIFxeXDLb9UdjJffOB5iFOBgVOLhVfDhixBiTSwrrsw9xCjBwawk wvsqjD9CiDclsbIqtSg/vqg0J7X4EKM0B4uSOK/ZyvvhQgLpiSWp2ampBalFMFkmDk6pBsaU 3cua7raLJnG9UHswce/90n+O+eVTOqe/tY15cPq0LOekHZOWHbfcx5GUez7bQnu6W9u8E/WK rnmGtQ7m2bLHTnQtdbpbm/P4Xm3ynyuzv2i/k54RVHSbY25zXMGv9xnxE4RmHL73uDOjw7lK 2+9d+o5HO3IFFj1+pau2bLrKrsD3rg05604psRRnJBpqMRcVJwIAnFI9BMcCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/kXedivgxFXH9hTtgj3d2DUyJo8M>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 13:01:49 -0000

--_000_D435312F11BDFchristerholmbergericssoncom_
Content-Type: text/plain; charset="euc-kr"
Content-Transfer-Encoding: base64

SGksDQoNCkkganVzdCBoYWQgYSBjaGF0IHdpdGggUm9tYW4sIGFuZCBvdXIgc3VnZ2VzdGlvbiBp
cyB0byByZW1vdmUgZXZlbiBtb3JlIGdlbmVyaWMgSUNFIHN0dWZmIGZyb20gZHJhZnQtc2Z0cC1z
ZHAsIGJlY2F1c2UgaXQgc2hvdWxkIGJlIGFkZGVkIHRvIGRyYWZ0LWlldGYtbW11c2ljLWljZS1z
aXAtc2RwLg0KDQoNCk5FVyBURVhUOg0KDQotLS0tLQ0KDQoxMi4yLiAgSUNFIENvbnNpZGVyYXRp
b25zDQoNCiAgIFdoZW4gU0NUUC1vdmVyLURUTFMgaXMgdXNlZCB3aXRoIFVEUCBiYXNlZCBJQ0Ug
Y2FuZGlkYXRlcw0KICAgW0ktRC5pZXRmLWljZS1yZmM1MjQ1YmlzXSB0aGVuIHRoZSBwcm9jZWR1
cmVzIGZvciBVRFAvRFRMUy9TQ1RQDQogICBbU2VjdGlvbiA3XSBhcmUgdXNlZC4NCg0KICAgV2hl
biBTQ1RQLW92ZXItRFRMUyBpcyB1c2VkIHdpdGggVENQIGJhc2VkIElDRSBjYW5kaWRhdGVzIFtS
RkM2NTQ0XQ0KICAgdGhlbiB0aGUgcHJvY2VkdXJlcyBmb3IgVENQL0RUTFMvU0NUUCBbU2VjdGlv
biA4XSBhcmUgdXNlZC4NCg0KICAgVGhlIGdlbmVyaWMgSUNFIHJ1bGVzIGRlZmluZWQgaW4gW0kt
RC5pZXRmLW1tdXNpYy1pY2Utc2lwLXNkcF0gYXBwbHkNCiAgIGFsc28gdG8gU0NUUC1vdmVyLURU
TFMuIFRoZXJlZm9yZSwgaW1wbGVtZW50YXRpb25zIG11c3QgdHJlYXQgYWxsIElDRSBjYW5kaWRh
dGUgcGFpcnMgYXNzb2NpYXRlZCB3aXRoIGFuDQogICBTQ1RQIGFzc29jaWF0aW9uIG9uIHRvcCBv
ZiBhIERUTFMgYXNzb2NpYXRpb24gYXMgcGFydCBvZiB0aGUgc2FtZQ0KICAgRFRMUyBhc3NvY2lh
dGlvbi4gIFRodXMsIHRoZXJlIHdpbGwgb25seSBiZSBvbmUgU0NUUCBoYW5kc2hha2UgYW5kDQog
ICBvbmUgRFRMUyBoYW5kc2hha2UgZXZlbiBpZiB0aGVyZSBhcmUgbXVsdGlwbGUgdmFsaWQgY2Fu
ZGlkYXRlIHBhaXJzLA0KICAgYW5kIHNoaWZ0aW5nIGZyb20gb25lIGNhbmRpZGF0ZSBwYWlyIHRv
IGFub3RoZXIgd2lsbCBub3QgaW1wYWN0IHRoZQ0KICAgU0NUUCBvciBEVExTIGFzc29jaWF0aW9u
cy4gIElmIG5ldyBjYW5kaWRhdGVzIGFyZSBhZGRlZCwgdGhleSB3aWxsDQogICBhbHNvIGJlIHBh
cnQgb2YgdGhlIHNhbWUgU0NUUCBhbmQgRFRMUyBhc3NvY2lhdGlvbnMuDQoNCiAgIEluIGFkZGl0
aW9uLCB3aGVuIGFuIFNEUCBvZmZlciBvciBhbnN3ZXIgaXMgc2VudCwgdGhlIHJ1bGVzIGluDQog
ICBbSS1ELmlldGYtbW11c2ljLWljZS1zaXAtc2RwXSBhcHBseSByZWdhcmRpbmcgd2hlbiB0aGUg
cHJvdG8gdmFsdWUNCiAgICihsFVEUC9EVExTL1NDVFChsSBvciChsFRDUC9EVExTL1NDVFChsSkg
bXVzdCBtYXRjaCB0aGUgdHJhbnNwb3J0DQogICBwcm90b2NvbCBhc3NvY2lhdGVkIHdpdGggdGhl
IGRlZmF1bHQgY2FuZGlkYXRlLg0KDQogICBOT1RFOiBUaGUgdGV4dCBpbiB0aGUgcGFyYWdyYXBo
IGFib3ZlIG9ubHkgYXBwbGllcyB3aGVuIHRoZSB1c2FnZSBvZg0KICAgSUNFIGhhcyBiZWVuIG5l
Z290aWF0ZWQuICBJZiBJQ0UgaXMgbm90IHVzZWQsIHRoZSBwcm90byB2YWx1ZSBNVVNUDQogICBh
bHdheXMgcmVmbGVjdCB0aGUgdHJhbnNwb3J0IHByb3RvY29sIHVzZWQgYXQgYW55IGdpdmVuIHRp
bWUuDQoNCi0tLS0tDQoNCk5vdGUgdGhhdCBJIGFtIG5vdCB1c2luZyAyMTE5IHRlcm1pbm9sb2d5
LCBiZWNhdXNlIHRoZSBnZW5lcmljIElDRSBwcm9jZWR1cmVzDQphcmUgZXhwZWN0ZWQgdG8gYmUg
ZGVmaW5lZCBpbiBkcmFmdC1pZXRmLW1tdXNpYy1pY2Utc2lwLXNkcC4NCg0KUmVnYXJkcywNCg0K
Q2hyaXN0ZXINCg0KDQoNCg0KDQpGcm9tOiBDaGFybGVzIEVja2VsIDxlY2tlbGN1QGNpc2NvLmNv
bTxtYWlsdG86ZWNrZWxjdUBjaXNjby5jb20+Pg0KRGF0ZTogVHVlc2RheSAyNSBPY3RvYmVyIDIw
MTYgYXQgMTU6MDQNClRvOiBDaHJpc3RlciBIb2xtYmVyZyA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJp
Y3Nzb24uY29tPG1haWx0bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+PiwgInBreXpp
dmF0QGFsdW0ubWl0LmVkdTxtYWlsdG86cGt5eml2YXRAYWx1bS5taXQuZWR1PiIgPHBreXppdmF0
QGFsdW0ubWl0LmVkdTxtYWlsdG86cGt5eml2YXRAYWx1bS5taXQuZWR1Pj4sICJtbXVzaWNAaWV0
Zi5vcmc8bWFpbHRvOm1tdXNpY0BpZXRmLm9yZz4iIDxtbXVzaWNAaWV0Zi5vcmc8bWFpbHRvOm1t
dXNpY0BpZXRmLm9yZz4+DQpTdWJqZWN0OiBSZTogW01NVVNJQ10gZHJhZnQtaWNlLXNpcC1zZHA6
IG0tIGxpbmUgbWF0Y2hpbmcgZGVmYXVsdCBjYW5kaWRhdGUgaW4gU0RQIGFuc3dlcj8NCg0KSGkg
Q2hyaXN0ZXIsDQoNClRoaXMgc2VlbXMgbGlrZSBhIGdvb2QgYXBwcm9hY2ggdG8gbWUuIEkgd2ls
bCBzdWdnZXN0IHdlIGZvbGxvdyB0aGlzIHNhbWUgYXBwcm9hY2ggZm9yIGRyYWZ0LWlldGYtYmZj
cGJpcy1yZmM0NTgzYmlzIG9uIHRoZSBiZmNwYmlzIGxpc3QuDQoNCkNoZWVycywNCkNoYXJsZXMN
Cg0KT24gMTAvMjUvMTYsIDExOjAxIEFNLCAibW11c2ljIG9uIGJlaGFsZiBvZiBDaHJpc3RlciBI
b2xtYmVyZyIgPG1tdXNpYy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzptbXVzaWMtYm91bmNlc0Bp
ZXRmLm9yZz4gb24gYmVoYWxmIG9mIGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTxtYWls
dG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPj4gd3JvdGU6DQoNCkhpLA0KDQpJqfZ2
ZSBtb2RpZmllZCB0aGUgV0dMQyBwdWxsIHJlcXVlc3QgZm9yIGRyYWZ0LWlldGYtbW11c2ljLXNj
dHAtc2RwOg0KDQpodHRwczovL2dpdGh1Yi5jb20vY2RoNHUvZHJhZnQtc2N0cC1zZHAvcHVsbHMN
Cg0KDQpUaGUgaW1wYWN0ZWQgSUNFIHRleHQgbm93IHNheXM6DQoNCiJXaGVuIGFuIFNEUCBvZmZl
ciBvciBhbnN3ZXIgaXMgc2VudCwgdGhlIHJ1bGVzIGluDQogICBbSS1ELmlldGYtbW11c2ljLWlj
ZS1zaXAtc2RwXSBhcHBseSByZWdhcmRpbmcgd2hlbiB0aGUgcHJvdG8gdmFsdWUNCiAgIG11c3Qg
bWF0Y2ggdGhlIHRyYW5zcG9ydCBwcm90b2NvbCBhc3NvY2lhdGVkIHdpdGggdGhlIGRlZmF1bHQN
CiAgIGNhbmRpZGF0ZS4NCg0KICAgSWYgYW4gZW5kcG9pbnQgc3dpdGNoZXMgYmV0d2VlbiBUQ1At
YmFzZWQgYW5kIFVEUC1iYXNlZCBjYW5kaWRhdGVzDQogICBkdXJpbmcgYSBzZXNzaW9uIHRoZSBl
bmRwb2ludCBpcyBub3QgcmVxdWlyZWQgdG8gc2VuZCBhbiBTRFAgb2ZmZXIgaW4NCiAgIG9yZGVy
IHRvIG1vZGlmeSB0aGF0IHByb3RvIHZhbHVlIG9mIHRoZSBhc3NvY2lhdGVkIG0tIGxpbmUuqfcN
Cg0KSSBndWVzcyB0aGUgdGV4dCBpbiB0aGUgc2Vjb25kIHBhcmFncmFwaCBzaG91bGQgYWxzbyBi
ZSBwdXQNCmRyYWZ0LWljZS1zaXAtc2RwLCBidXQgSSBndWVzcyBpdCBkb2Vzbqn2dCBodXJ0IHRv
IGtlZXAgaXQgYWxzbyBoZXJlLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoNCg0KDQoNCg0K
T24gMjQvMTAvMTYgMjE6NTUsICJtbXVzaWMgb24gYmVoYWxmIG9mIENocmlzdGVyIEhvbG1iZXJn
Ig0KPG1tdXNpYy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzptbXVzaWMtYm91bmNlc0BpZXRmLm9y
Zz4gb24gYmVoYWxmIG9mIGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTxtYWlsdG86Y2hy
aXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPj4NCndyb3RlOg0KDQpIaSwNCg0KTWF5YmUgd2Us
IGluIGRyYWZ0LWJmY3BiaXMgYW5kIGRyYWZ0LXNjdHAtc2RwIHNpbXBseSBjb3VsZCBzYXk6ICJ0
aGUNCnJ1bGVzIGluIElDRSBhcHBseSA+PiAgcmVnYXJkaW5nIHdoZW4gdGhlIGMvbS0gbGluZXMg
bXVzdCBtYXRjaCB0aGUNCmRlZmF1bHQgY2FuZGlkYXRlIi4NCg0KVGhlbiB3ZSdsbCBkZWFsIHdp
dGggdGhlIGlzc3VlIGluIGRyYWZ0LWljZS1zaXAtc2RwLCBhbmQgaXQgd29uJ3Qgc3RvcA0KcHJv
Z3Jlc3Mgb2YgZHJhZnQtPj4gYmZjcGJpcyBhbmQgZHJhZnQtc2N0cC1zZHAuDQoNClNlZW1zIGxp
a2UgdGhhdCB3b3VsZCB3b3JrLiBCdXQgb2YgY291cnNlIHRoZXkgd2lsbCBzdGlsbCBldmVudHVh
bGx5DQpibG9jayBvbiB0aGVpcg0KZGVwZW5kZW5jeSB0byB0aGF0IGRyYWZ0Lg0KDQpUcnVlLiBC
dXQsIGF0IGxlYXN0IHdlJ2xsIGdldCB0aGUgZHJhZnRzIG91dCBvZiB0aGUgV0dzLCBJRVNHIHJl
dmlld2VkDQpldGMuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQptbXVzaWMgbWFpbGluZyBsaXN0DQptbXVz
aWNAaWV0Zi5vcmc8bWFpbHRvOm1tdXNpY0BpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vbW11c2ljDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQptbXVzaWMgbWFpbGluZyBsaXN0DQptbXVzaWNAaWV0Zi5vcmc8
bWFpbHRvOm1tdXNpY0BpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vbW11c2ljDQoNCg==

--_000_D435312F11BDFchristerholmbergericssoncom_
Content-Type: text/html; charset="euc-kr"
Content-ID: <1B888C2B9CD7094CAD06E225355E9963@ericsson.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PWV1Yy1rciI+DQo8L2hlYWQ+DQo8Ym9keSBzdHlsZT0id29yZC13
cmFwOiBicmVhay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1i
cmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7IGNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtc2l6ZTog
MTRweDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7Ij4NCjxkaXY+SGksPC9kaXY+
DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5JIGp1c3QgaGFkIGEgY2hhdCB3aXRoIFJvbWFuLCBh
bmQgb3VyIHN1Z2dlc3Rpb24gaXMgdG8gcmVtb3ZlIGV2ZW4gbW9yZSBnZW5lcmljIElDRSBzdHVm
ZiBmcm9tIGRyYWZ0LXNmdHAtc2RwLCBiZWNhdXNlIGl0IHNob3VsZCBiZSBhZGRlZCB0byBkcmFm
dC1pZXRmLW1tdXNpYy1pY2Utc2lwLXNkcC48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2
Pjxicj4NCjwvZGl2Pg0KPGRpdj5ORVcgVEVYVDo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8
ZGl2Pi0tLS0tPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+MTIuMi4gJm5i
c3A7SUNFIENvbnNpZGVyYXRpb25zPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj4mbmJz
cDsgJm5ic3A7V2hlbiBTQ1RQLW92ZXItRFRMUyBpcyB1c2VkIHdpdGggVURQIGJhc2VkIElDRSBj
YW5kaWRhdGVzPC9kaXY+DQo8ZGl2PiZuYnNwOyAmbmJzcDtbSS1ELmlldGYtaWNlLXJmYzUyNDVi
aXNdIHRoZW4gdGhlIHByb2NlZHVyZXMgZm9yIFVEUC9EVExTL1NDVFA8L2Rpdj4NCjxkaXY+Jm5i
c3A7ICZuYnNwO1tTZWN0aW9uIDddIGFyZSB1c2VkLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4N
CjxkaXY+Jm5ic3A7ICZuYnNwO1doZW4gU0NUUC1vdmVyLURUTFMgaXMgdXNlZCB3aXRoIFRDUCBi
YXNlZCBJQ0UgY2FuZGlkYXRlcyBbUkZDNjU0NF08L2Rpdj4NCjxkaXY+Jm5ic3A7ICZuYnNwO3Ro
ZW4gdGhlIHByb2NlZHVyZXMgZm9yIFRDUC9EVExTL1NDVFAgW1NlY3Rpb24gOF0gYXJlIHVzZWQu
PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj4mbmJzcDsgJm5ic3A7VGhlIGdlbmVyaWMg
SUNFIHJ1bGVzIGRlZmluZWQgaW4gW0ktRC5pZXRmLW1tdXNpYy1pY2Utc2lwLXNkcF0gYXBwbHk8
L2Rpdj4NCjxkaXY+Jm5ic3A7ICZuYnNwO2Fsc28gdG8gU0NUUC1vdmVyLURUTFMuIFRoZXJlZm9y
ZSwgaW1wbGVtZW50YXRpb25zIG11c3QgdHJlYXQgYWxsIElDRSBjYW5kaWRhdGUgcGFpcnMgYXNz
b2NpYXRlZCB3aXRoIGFuPC9kaXY+DQo8ZGl2PiZuYnNwOyAmbmJzcDtTQ1RQIGFzc29jaWF0aW9u
IG9uIHRvcCBvZiBhIERUTFMgYXNzb2NpYXRpb24gYXMgcGFydCBvZiB0aGUgc2FtZTwvZGl2Pg0K
PGRpdj4mbmJzcDsgJm5ic3A7RFRMUyBhc3NvY2lhdGlvbi4gJm5ic3A7VGh1cywgdGhlcmUgd2ls
bCBvbmx5IGJlIG9uZSBTQ1RQIGhhbmRzaGFrZSBhbmQ8L2Rpdj4NCjxkaXY+Jm5ic3A7ICZuYnNw
O29uZSBEVExTIGhhbmRzaGFrZSBldmVuIGlmIHRoZXJlIGFyZSBtdWx0aXBsZSB2YWxpZCBjYW5k
aWRhdGUgcGFpcnMsPC9kaXY+DQo8ZGl2PiZuYnNwOyAmbmJzcDthbmQgc2hpZnRpbmcgZnJvbSBv
bmUgY2FuZGlkYXRlIHBhaXIgdG8gYW5vdGhlciB3aWxsIG5vdCBpbXBhY3QgdGhlPC9kaXY+DQo8
ZGl2PiZuYnNwOyAmbmJzcDtTQ1RQIG9yIERUTFMgYXNzb2NpYXRpb25zLiAmbmJzcDtJZiBuZXcg
Y2FuZGlkYXRlcyBhcmUgYWRkZWQsIHRoZXkgd2lsbDwvZGl2Pg0KPGRpdj4mbmJzcDsgJm5ic3A7
YWxzbyBiZSBwYXJ0IG9mIHRoZSBzYW1lIFNDVFAgYW5kIERUTFMgYXNzb2NpYXRpb25zLjwvZGl2
Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+Jm5ic3A7ICZuYnNwO0luIGFkZGl0aW9uLCB3aGVu
IGFuIFNEUCBvZmZlciBvciBhbnN3ZXIgaXMgc2VudCwgdGhlIHJ1bGVzIGluPC9kaXY+DQo8ZGl2
PiZuYnNwOyAmbmJzcDtbSS1ELmlldGYtbW11c2ljLWljZS1zaXAtc2RwXSBhcHBseSByZWdhcmRp
bmcgd2hlbiB0aGUgcHJvdG8gdmFsdWU8L2Rpdj4NCjxkaXY+Jm5ic3A7ICZuYnNwOyihsFVEUC9E
VExTL1NDVFChsSBvciChsFRDUC9EVExTL1NDVFChsSkgbXVzdCBtYXRjaCB0aGUgdHJhbnNwb3J0
Jm5ic3A7PC9kaXY+DQo8ZGl2PiZuYnNwOyAmbmJzcDtwcm90b2NvbCBhc3NvY2lhdGVkIHdpdGgg
dGhlIGRlZmF1bHQgY2FuZGlkYXRlLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+Jm5i
c3A7ICZuYnNwO05PVEU6IFRoZSB0ZXh0IGluIHRoZSBwYXJhZ3JhcGggYWJvdmUgb25seSBhcHBs
aWVzIHdoZW4gdGhlIHVzYWdlIG9mPC9kaXY+DQo8ZGl2PiZuYnNwOyAmbmJzcDtJQ0UgaGFzIGJl
ZW4gbmVnb3RpYXRlZC4gJm5ic3A7SWYgSUNFIGlzIG5vdCB1c2VkLCB0aGUgcHJvdG8gdmFsdWUg
TVVTVDwvZGl2Pg0KPGRpdj4mbmJzcDsgJm5ic3A7YWx3YXlzIHJlZmxlY3QgdGhlIHRyYW5zcG9y
dCBwcm90b2NvbCB1c2VkIGF0IGFueSBnaXZlbiB0aW1lLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjwvZGl2Pg0KPGRpdj4tLS0tLTwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+Tm90
ZSB0aGF0IEkgYW0gbm90IHVzaW5nIDIxMTkgdGVybWlub2xvZ3ksIGJlY2F1c2UgdGhlIGdlbmVy
aWMgSUNFIHByb2NlZHVyZXM8L2Rpdj4NCjxkaXY+YXJlIGV4cGVjdGVkIHRvIGJlIGRlZmluZWQg
aW4gZHJhZnQtaWV0Zi1tbXVzaWMtaWNlLXNpcC1zZHAuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2
Pg0KPGRpdj5SZWdhcmRzLDwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+Q2hyaXN0ZXI8
L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8
L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9M
S19TUkNfQk9EWV9TRUNUSU9OIj4NCjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmk7IGZv
bnQtc2l6ZToxMXB0OyB0ZXh0LWFsaWduOmxlZnQ7IGNvbG9yOmJsYWNrOyBCT1JERVItQk9UVE9N
OiBtZWRpdW0gbm9uZTsgQk9SREVSLUxFRlQ6IG1lZGl1bSBub25lOyBQQURESU5HLUJPVFRPTTog
MGluOyBQQURESU5HLUxFRlQ6IDBpbjsgUEFERElORy1SSUdIVDogMGluOyBCT1JERVItVE9QOiAj
YjVjNGRmIDFwdCBzb2xpZDsgQk9SREVSLVJJR0hUOiBtZWRpdW0gbm9uZTsgUEFERElORy1UT1A6
IDNwdCI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+RnJvbTogPC9zcGFuPkNoYXJs
ZXMgRWNrZWwgJmx0OzxhIGhyZWY9Im1haWx0bzplY2tlbGN1QGNpc2NvLmNvbSI+ZWNrZWxjdUBj
aXNjby5jb208L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5EYXRl
OiA8L3NwYW4+VHVlc2RheSAyNSBPY3RvYmVyIDIwMTYgYXQgMTU6MDQ8YnI+DQo8c3BhbiBzdHls
ZT0iZm9udC13ZWlnaHQ6Ym9sZCI+VG86IDwvc3Bhbj5DaHJpc3RlciBIb2xtYmVyZyAmbHQ7PGEg
aHJlZj0ibWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSI+Y2hyaXN0ZXIuaG9s
bWJlcmdAZXJpY3Nzb24uY29tPC9hPiZndDssICZxdW90OzxhIGhyZWY9Im1haWx0bzpwa3l6aXZh
dEBhbHVtLm1pdC5lZHUiPnBreXppdmF0QGFsdW0ubWl0LmVkdTwvYT4mcXVvdDsgJmx0OzxhIGhy
ZWY9Im1haWx0bzpwa3l6aXZhdEBhbHVtLm1pdC5lZHUiPnBreXppdmF0QGFsdW0ubWl0LmVkdTwv
YT4mZ3Q7LA0KICZxdW90OzxhIGhyZWY9Im1haWx0bzptbXVzaWNAaWV0Zi5vcmciPm1tdXNpY0Bp
ZXRmLm9yZzwvYT4mcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzptbXVzaWNAaWV0Zi5vcmciPm1t
dXNpY0BpZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQi
PlN1YmplY3Q6IDwvc3Bhbj5SZTogW01NVVNJQ10gZHJhZnQtaWNlLXNpcC1zZHA6IG0tIGxpbmUg
bWF0Y2hpbmcgZGVmYXVsdCBjYW5kaWRhdGUgaW4gU0RQIGFuc3dlcj88YnI+DQo8L2Rpdj4NCjxk
aXY+PGJyPg0KPC9kaXY+DQo8ZGl2IHhtbG5zOm89InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206
b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6
d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8x
Mi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvVFIvUkVDLWh0bWw0MCI+DQo8bWV0YSBu
YW1lPSJUaXRsZSIgY29udGVudD0iIj4NCjxtZXRhIG5hbWU9IktleXdvcmRzIiBjb250ZW50PSIi
Pg0KPG1ldGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmls
dGVyZWQgbWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZv
bnQtZmFjZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAz
IDUgNCA2IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5v
c2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNv
bnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmlu
aXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21h
cmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJ
Zm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGlu
aw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRp
b246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1
bmRlcmxpbmU7fQ0Kc3Bhbi5hcHBsZS1zdHlsZS1zcGFuDQoJe21zby1zdHlsZS1uYW1lOmFwcGxl
LXN0eWxlLXNwYW47fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29u
YWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6Q2FsaWJyaTsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNw
YW4ubXNvSW5zDQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCW1zby1zdHlsZS1uYW1l
OiIiOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7DQoJY29sb3I6dGVhbDt9DQouTXNvQ2hw
RGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0
O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4w
aW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0
aW9uMTt9DQotLT48L3N0eWxlPg0KPGRpdiBiZ2NvbG9yPSJ3aGl0ZSIgbGFuZz0iRU4tVVMiIGxp
bms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OkNhbGlicmkiPkhpIENocmlzdGVyLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNh
bGlicmkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPlRoaXMg
c2VlbXMgbGlrZSBhIGdvb2QgYXBwcm9hY2ggdG8gbWUuIEkgd2lsbCBzdWdnZXN0IHdlIGZvbGxv
dyB0aGlzIHNhbWUgYXBwcm9hY2ggZm9yIGRyYWZ0LWlldGYtYmZjcGJpcy1yZmM0NTgzYmlzIG9u
IHRoZSBiZmNwYmlzIGxpc3QuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+Q2hlZXJzLDxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPkNoYXJsZXM8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTpDYWxpYnJpIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8Ymxv
Y2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0I1QzRERiA0LjVw
dDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0O21hcmdpbi1sZWZ0OjMuNzVwdDttYXJnaW4tcmln
aHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNr
Ij5PbiAxMC8yNS8xNiwgMTE6MDEgQU0sICZxdW90O21tdXNpYyBvbiBiZWhhbGYgb2YgQ2hyaXN0
ZXIgSG9sbWJlcmcmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzptbXVzaWMtYm91bmNlc0BpZXRm
Lm9yZyI+bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmc8L2E+IG9uIGJlaGFsZiBvZg0KPGEgaHJlZj0i
bWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSI+Y2hyaXN0ZXIuaG9sbWJlcmdA
ZXJpY3Nzb24uY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJs
YWNrIj5IaSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25z
b2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPkmp9nZlIG1vZGlmaWVkIHRoZSBXR0xD
IHB1bGwgcmVxdWVzdCBmb3IgZHJhZnQtaWV0Zi1tbXVzaWMtc2N0cC1zZHA6PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFz
O2NvbG9yOmJsYWNrIj48YSBocmVmPSJodHRwczovL2dpdGh1Yi5jb20vY2RoNHUvZHJhZnQtc2N0
cC1zZHAvcHVsbHMiPmh0dHBzOi8vZ2l0aHViLmNvbS9jZGg0dS9kcmFmdC1zY3RwLXNkcC9wdWxs
czwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xh
cztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj5UaGUgaW1wYWN0
ZWQgSUNFIHRleHQgbm93IHNheXM6PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj4mcXVvdDtXaGVu
IGFuIFNEUCBvZmZlciBvciBhbnN3ZXIgaXMgc2VudCwgdGhlIHJ1bGVzIGluPG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPiZu
YnNwOyZuYnNwOyBbSS1ELmlldGYtbW11c2ljLWljZS1zaXAtc2RwXSBhcHBseSByZWdhcmRpbmcg
d2hlbiB0aGUgcHJvdG8gdmFsdWU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7IG11c3QgbWF0Y2ggdGhl
IHRyYW5zcG9ydCBwcm90b2NvbCBhc3NvY2lhdGVkIHdpdGggdGhlIGRlZmF1bHQ8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+
Jm5ic3A7Jm5ic3A7IGNhbmRpZGF0ZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPiZuYnNwOyZu
YnNwOyBJZiBhbiBlbmRwb2ludCBzd2l0Y2hlcyBiZXR3ZWVuIFRDUC1iYXNlZCBhbmQgVURQLWJh
c2VkIGNhbmRpZGF0ZXM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTpDb25zb2xhcztjb2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7IGR1cmluZyBhIHNlc3Npb24gdGhl
IGVuZHBvaW50IGlzIG5vdCByZXF1aXJlZCB0byBzZW5kIGFuIFNEUCBvZmZlciBpbjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNr
Ij4mbmJzcDsmbmJzcDsgb3JkZXIgdG8gbW9kaWZ5IHRoYXQgcHJvdG8gdmFsdWUgb2YgdGhlIGFz
c29jaWF0ZWQgbS0gbGluZS6p9zxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+SSBndWVzcyB0aGUg
dGV4dCBpbiB0aGUgc2Vjb25kIHBhcmFncmFwaCBzaG91bGQgYWxzbyBiZSBwdXQ8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+
ZHJhZnQtaWNlLXNpcC1zZHAsIGJ1dCBJIGd1ZXNzIGl0IGRvZXNuqfZ0IGh1cnQgdG8ga2VlcCBp
dCBhbHNvIGhlcmUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj5SZWdhcmRzLDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xh
cztjb2xvcjpibGFjayI+Q2hyaXN0ZXI8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9y
OmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xh
cztjb2xvcjpibGFjayI+T24gMjQvMTAvMTYgMjE6NTUsICZxdW90O21tdXNpYyBvbiBiZWhhbGYg
b2YgQ2hyaXN0ZXIgSG9sbWJlcmcmcXVvdDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+Jmx0OzxhIGhyZWY9Im1haWx0bzpt
bXVzaWMtYm91bmNlc0BpZXRmLm9yZyI+bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmc8L2E+IG9uIGJl
aGFsZiBvZg0KPGEgaHJlZj0ibWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSI+
Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPC9hPiZndDs8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+d3JvdGU6PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6
YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNCNUM0REYgNC41cHQ7cGFkZGlu
ZzowaW4gMGluIDBpbiA0LjBwdDttYXJnaW4tbGVmdDozLjc1cHQ7bWFyZ2luLXJpZ2h0OjBpbiIg
aWQ9Ik1BQ19PVVRMT09LX0FUVFJJQlVUSU9OX0JMT0NLUVVPVEUiPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNv
bnNvbGFzO2NvbG9yOmJsYWNrIj5IaSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6
c29saWQgI0I1QzRERiA0LjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0O21hcmdpbi1sZWZ0
OjMuNzVwdDttYXJnaW4tcmlnaHQ6MGluIiBpZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05fQkxP
Q0tRVU9URSI+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29s
aWQgI0I1QzRERiA0LjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0O21hcmdpbi1sZWZ0OjMu
NzVwdDttYXJnaW4tcmlnaHQ6MGluIiBpZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05fQkxPQ0tR
VU9URSI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPk1heWJlIHdlLCBpbiBk
cmFmdC1iZmNwYmlzIGFuZCBkcmFmdC1zY3RwLXNkcCBzaW1wbHkgY291bGQgc2F5OiAmcXVvdDt0
aGU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztj
b2xvcjpibGFjayI+cnVsZXMgaW4gSUNFIGFwcGx5ICZndDsmZ3Q7Jm5ic3A7Jm5ic3A7cmVnYXJk
aW5nIHdoZW4gdGhlIGMvbS0gbGluZXMgbXVzdCBtYXRjaCB0aGU8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+ZGVmYXVsdCBj
YW5kaWRhdGUmcXVvdDsuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj5UaGVuIHdlJ2xsIGRlYWwg
d2l0aCB0aGUgaXNzdWUgaW4gZHJhZnQtaWNlLXNpcC1zZHAsIGFuZCBpdCB3b24ndCBzdG9wPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6
YmxhY2siPnByb2dyZXNzIG9mIGRyYWZ0LSZndDsmZ3Q7IGJmY3BiaXMgYW5kIGRyYWZ0LXNjdHAt
c2RwLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+U2VlbXMgbGlrZSB0
aGF0IHdvdWxkIHdvcmsuIEJ1dCBvZiBjb3Vyc2UgdGhleSB3aWxsIHN0aWxsIGV2ZW50dWFsbHk8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xv
cjpibGFjayI+YmxvY2sgb24gdGhlaXINCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj5kZXBlbmRlbmN5IHRvIHRoYXQgZHJh
ZnQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj5UcnVlLiBCdXQsIGF0
IGxlYXN0IHdlJ2xsIGdldCB0aGUgZHJhZnRzIG91dCBvZiB0aGUgV0dzLCBJRVNHIHJldmlld2Vk
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29s
b3I6YmxhY2siPmV0Yy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPlJlZ2FyZHMsPG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2si
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNvbnNv
bGFzO2NvbG9yOmJsYWNrIj5DaHJpc3RlcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+X19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+bW11c2lj
IG1haWxpbmcgbGlzdDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48YSBocmVmPSJtYWlsdG86bW11c2ljQGlldGYub3JnIj5t
bXVzaWNAaWV0Zi5vcmc8L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vbW11c2ljIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL21tdXNpYzwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvYmxvY2tx
dW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2si
Pl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2si
Pm1tdXNpYyBtYWlsaW5nIGxpc3Q8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTpDb25zb2xhcztjb2xvcjpibGFjayI+PGEgaHJlZj0ibWFpbHRvOm1tdXNpY0BpZXRm
Lm9yZyI+bW11c2ljQGlldGYub3JnPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48YSBocmVmPSJodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYyI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9tbXVzaWM8L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6Q29uc29sYXM7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L3NwYW4+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_D435312F11BDFchristerholmbergericssoncom_--


From nobody Tue Oct 25 06:02:50 2016
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 C5A01129642 for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 06:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5] 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 ibQxyjOdJvBm for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 06:02:44 -0700 (PDT)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42E17129620 for <mmusic@ietf.org>; Tue, 25 Oct 2016 06:02:40 -0700 (PDT)
Received: by mail-qt0-x236.google.com with SMTP id 23so9524634qtp.5 for <mmusic@ietf.org>; Tue, 25 Oct 2016 06:02:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4EqhGfyKD82vpgWRnWDSvRopkekrwUzoTbXCy3vN4Sg=; b=KsrOQ5SUSR90BfhQ4sFf6+w43VYDHQJDEAVQjPgeAbyE/2Urzx/bJozQzH7V0I0zuG EjMrLcLGmirv+MJJitaFjOs0DdWao+JlMXW6QmoNbpLgWNlJDU/3sgSYVsab6VY23ITC 57xCRIiPPDXe0vr83l6vR4ftVcfnSrifojSk9hJmUW07AspDhFnjiJWVzUBAU9gfSEH7 uQ+i++22LYh0qHmZcHRELF5i8gE6KmTPhtyB/0hgfM3FxBrkAX8oNxFR14XxC+N1J9zp 4olf/Zst6loN5KJcfqGAjIW5BHAwakZ/ddP+nHHIxJP552GWEtjfCKLscvxU6fxMDT38 jKoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4EqhGfyKD82vpgWRnWDSvRopkekrwUzoTbXCy3vN4Sg=; b=V2Hi1jcgrmyX9Tad+mvRFlfBYKLt/7Mf7eF6eux5cXggVvyBneW1T/vv8zXlNIdKy+ RGwUnGBn8CKxICaAhADyqvOeUbywh/h5bO/5ISBQ7wFJ8ZEncZvKKFdz4dDFONpWM/Db az26vr8s60DyGWhdCsaAkaHcX14QTFE1oxMsf2AHRuzdBkRIincUtx+jgHVrxYfRdorU ZCbmrrmkrxEG7IDBtNFsEohMRzTPZCRsvR1iRP2frFCrae1Oe5L5GcEEtI1kd8VwRLTh Kh1ecJB6rGucpj8dkg4CwGgvsSYdREi1np5Xo5X09Dhee17KB8OPQ/p2LWKW4aFJEoav 7ToA==
X-Gm-Message-State: ABUngvdWqbniDvRhWXlKyY1oow+4NOdYvgJvk14RpvFJAjSNqIEOk41if3PWNCM3s+sRmw==
X-Received: by 10.200.34.145 with SMTP id f17mr20081729qta.149.1477400559097;  Tue, 25 Oct 2016 06:02:39 -0700 (PDT)
Received: from mail-qk0-f180.google.com (mail-qk0-f180.google.com. [209.85.220.180]) by smtp.gmail.com with ESMTPSA id i185sm2885052qkc.39.2016.10.25.06.02.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Oct 2016 06:02:38 -0700 (PDT)
Received: by mail-qk0-f180.google.com with SMTP id n189so259311894qke.0; Tue, 25 Oct 2016 06:02:38 -0700 (PDT)
X-Received: by 10.55.79.213 with SMTP id d204mr21145271qkb.110.1477400558035;  Tue, 25 Oct 2016 06:02:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.132.161 with HTTP; Tue, 25 Oct 2016 06:02:37 -0700 (PDT)
In-Reply-To: <CABcZeBNKGK92=6moFbQ_4x1GuLoAZqQBrLZtY_AFnv6+iTnmyw@mail.gmail.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <32BBB414-85BA-484C-954D-EDC8620F26DF@ericsson.com> <CABcZeBNKGK92=6moFbQ_4x1GuLoAZqQBrLZtY_AFnv6+iTnmyw@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 25 Oct 2016 09:02:37 -0400
X-Gmail-Original-Message-ID: <CAD5OKxt7Z7ia6A4f1wM3K4Zit_sQDDvKRMgP4VHbqTfg8xZfCw@mail.gmail.com>
Message-ID: <CAD5OKxt7Z7ia6A4f1wM3K4Zit_sQDDvKRMgP4VHbqTfg8xZfCw@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Content-Type: multipart/alternative; boundary=001a114a9710741675053fb01fdf
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jxDWjeUbG_p1cGh09d8iTfZ5Z-I>
Cc: Ben Campbell <ben@nostrum.com>, mmusic <mmusic@ietf.org>, ART ADs <art-ads@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 13:02:49 -0000

--001a114a9710741675053fb01fdf
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi All,

Any reasonable time US Eastern works for me.

_____________
Roman Shpount

On Tue, Oct 25, 2016 at 1:07 AM, Eric Rescorla <ekr@rtfm.com> wrote:

> I am in Australia this week so next week would be easier. Otherwise,
> please make it late Pacific time so that it's not too early.
>
> -Ekr
>
>
> On Tue, Oct 25, 2016 at 3:33 PM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
>> Hi Flemming,
>>
>> Any day but Monday works for me.
>>
>> Regards,
>>
>> Christer
>>
>> Sent from my iPhone
>>
>> > On 25 Oct 2016, at 7.01, Flemming Andreasen <fandreas@cisco.com> wrote=
:
>> >
>> > Hi Ben
>> >
>> > We will get a poll setup as soon as we understand any major constraint=
s
>> from the key participants.
>> >
>> > Thanks
>> >
>> > -- Flemming
>> >
>> >
>> >> On 10/21/16 4:49 PM, Ben Campbell wrote:
>> >> Hi Everyone, please accept my apologies for waiting this long to weig=
h
>> in.
>> >>
>> >> I think it's clear that multiple people are not happy with how we got
>> to this point. But assigning blame doesn't help us make progress on the
>> draft. I propose that we get over that, and instead focus instead on how=
 to
>> move forward. Email discussion doesn't seem to be helping. Maybe a call
>> will.
>> >>
>> >> Flemming and/or Bo: Can you set up a Doodle poll to get Christer,
>> Cullen, and other demonstratively  interested parties on a conference ca=
ll?
>> I will join if at all possible, but don't let scheduling around me stop =
a
>> call from happening.
>> >>
>> >> Thanks!
>> >>
>> >> Ben.
>> >>
>> >>> On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:
>> >>>
>> >>> [fixing cc-list]
>> >>>
>> >>>> On 10/21/16 11:59 AM, Flemming Andreasen wrote:
>> >>>>
>> >>>>
>> >>>>> On 10/21/16 11:21 AM, Cullen Jennings wrote:
>> >>>>> I think that is a bad way to run a WG. All I asked for was a phone
>> call to discuss this so we could get the issues on the table and discuss
>> what is best. The chairs never even replied to my request for a WG call =
to
>> discuss this.
>> >>>> That is simply not true. You (and Christer) were explicitly asked t=
o
>> setup a phone call on 10/6/16 to discuss this issue; a request that (lik=
e
>> many other others) went unanswered or required extensive prodding to get
>> any attention.
>> >>>>
>> >>>>> The list discussions that ensued from this resulted in people othe=
r
>> than me sugesting possibilities that were much better than any of the th=
ree
>> below -  none of which were considered in your consensus call.
>> >>>> I'm not sure what those proposals are, nor were they brought up in
>> response to the consensus call.
>> >>>>
>> >>>>> I don=E2=80=99t plan to appeal this but I am considering if it=E2=
=80=99s worth my
>> time to participate in this WG if we are not going to be willing to
>> actually spend a short time to discuss possible solutions before taking =
a
>> consensus call.  As input to that decisions, it would be really useful t=
o
>> know why you refused to have a phone call on this topic and what your
>> policy in general is going to be toward discussions of proposed solution=
s
>> to problems in the future.
>> >>>> My position is that we will try our very best to get to not only
>> consensus but to satisfy as many concerns as we possibly can. It does
>> however require people to engage in a timely manner, and even when they
>> don't, we still do what we can, but at some point we need to move forwar=
d.
>> As for the issue at hand, it has been discussed extensively, and several
>> changes were made to the draft to try and accommodate your requests.
>> >>>>
>> >>>> The one major remaining issue I believe you have is around whether
>> this document updates RFC 4572. This has been discussed extensively on t=
he
>> wgchairs list; a discussion I initiated to try and help address your
>> concern. You may disagree with how that discussion concluded, but again,=
 to
>> try and alleviate your concerns, a note was added to 4572-update to make=
 it
>> clear that the document does not make existing 4572 implementations
>> non-compliant with RFC 4572.
>> >>>>
>> >>>> I believe the chairs, authors, and the WG at large has done
>> everything that can reasonably be done to try and address your concerns,
>> and at this point we need to move forward.
>> >>>>
>> >>>> Thanks
>> >>>>
>> >>>> -- Flemming (as MMUSIC co-chair)
>> >>>>
>> >>>>
>> >>>>
>> >>>>>
>> >>>>>> On Oct 19, 2016, at 6:43 AM, Flemming Andreasen <
>> fandreas@cisco.com> wrote:
>> >>>>>>
>> >>>>>> Hi
>> >>>>>>
>> >>>>>> Following up on the consensus call, we have received 5 responses
>> in favor of option a) below, one neutral, and one objection. Looking at =
the
>> document we have noted that backwards compatibility is handled by the
>> current text in the document and it also clearly states that it does not
>> make current RFC 4572 implementation non-compliant with RFC 4572. Since =
we
>> have not heard of any technical problems with proposal a), nor seen any
>> tangible progress on how to address the objection, we are hereby declari=
ng
>> rough consensus on option a). We will proceed with the publication reque=
st
>> for the current draft while duly noting the "roughness" of the consensus
>> based on the pending objection as part of this.
>> >>>>>>
>> >>>>>> Thanks
>> >>>>>>
>> >>>>>>    Flemming & Bo (MMUSIC chairs)
>> >>>>>>
>> >>>>>>
>> >>>>>>> On 10/12/16 6:23 PM, Flemming Andreasen wrote:
>> >>>>>>> Greetings
>> >>>>>>>
>> >>>>>>> There has been quite a bit of discussion on
>> draft-ietf-mmusic-4572-update (currently -07), which had previously
>> completed WGLC when a few concerns were raised. The document currently:
>> >>>>>>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
>> >>>>>>> 2. Updates the preferred cipher-suite with a stronger cipher sui=
te
>> >>>>>>> 3. Updates RFC 4572.
>> >>>>>>>
>> >>>>>>> Item 1 seems to be generally agreeable, whereas items 2 and 3 ar=
e
>> not. The chairs are hereby soliciting WG feedback on how to proceed base=
d
>> on the following choices:
>> >>>>>>>
>> >>>>>>> a) Proceed with publication of 4572-update-07 in its current for=
m
>> (i.e. covering all 3 items above)
>> >>>>>>>
>> >>>>>>> b) Remove item 2 from 4572-update, i.e. do not update the
>> preferred cipher-suite
>> >>>>>>>
>> >>>>>>> c) Remove item 3 from 4572-update, i.e. do not indicate that thi=
s
>> document constitutes an update to RFC 4572.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Note that choice a) is mutually exclusive with b) and c), but b)
>> and c) are not mutually exclusive.
>> >>>>>>>
>> >>>>>>> Please let us know your preference wrt to the above no later tha=
n
>> Friday October 14th.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Thanks
>> >>>>>>>
>> >>>>>>>       Flemming & Bo (MMUSIC chairs)
>> >>>>>>>
>> >>>>>>> _______________________________________________
>> >>>>>>> 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
>> >>>>> .
>> >>>>>
>> >>>>
>> >>>> _______________________________________________
>> >>>> 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
>> >>
>> >> .
>> >>
>> >
>>
>> _______________________________________________
>> 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
>
>

--001a114a9710741675053fb01fdf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi All,<div><br></div><div>Any reasonable time US Eastern =
works for me.</div></div><div class=3D"gmail_extra"><br clear=3D"all"><div>=
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">_________=
____<br>Roman Shpount</div></div>
<br><div class=3D"gmail_quote">On Tue, Oct 25, 2016 at 1:07 AM, Eric Rescor=
la <span dir=3D"ltr">&lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">=
ekr@rtfm.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div d=
ir=3D"ltr">I am in Australia this week so next week would be easier. Otherw=
ise, please make it late Pacific time so that it&#39;s not too early.<div><=
br><div>-Ekr</div><div><br></div></div></div><div class=3D"HOEnZb"><div cla=
ss=3D"h5"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue,=
 Oct 25, 2016 at 3:33 PM, Christer Holmberg <span dir=3D"ltr">&lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christer.holmb=
erg@ericsson.<wbr>com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">Hi Flemming,<br>
<br>
Any day but Monday works for me.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
Sent from my iPhone<br>
<div class=3D"m_5864946379813227998HOEnZb"><div class=3D"m_5864946379813227=
998h5"><br>
&gt; On 25 Oct 2016, at 7.01, Flemming Andreasen &lt;<a href=3D"mailto:fand=
reas@cisco.com" target=3D"_blank">fandreas@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Ben<br>
&gt;<br>
&gt; We will get a poll setup as soon as we understand any major constraint=
s from the key participants.<br>
&gt;<br>
&gt; Thanks<br>
&gt;<br>
&gt; -- Flemming<br>
&gt;<br>
&gt;<br>
&gt;&gt; On 10/21/16 4:49 PM, Ben Campbell wrote:<br>
&gt;&gt; Hi Everyone, please accept my apologies for waiting this long to w=
eigh in.<br>
&gt;&gt;<br>
&gt;&gt; I think it&#39;s clear that multiple people are not happy with how=
 we got to this point. But assigning blame doesn&#39;t help us make progres=
s on the draft. I propose that we get over that, and instead focus instead =
on how to move forward. Email discussion doesn&#39;t seem to be helping. Ma=
ybe a call will.<br>
&gt;&gt;<br>
&gt;&gt; Flemming and/or Bo: Can you set up a Doodle poll to get Christer, =
Cullen, and other demonstratively=C2=A0 interested parties on a conference =
call? I will join if at all possible, but don&#39;t let scheduling around m=
e stop a call from happening.<br>
&gt;&gt;<br>
&gt;&gt; Thanks!<br>
&gt;&gt;<br>
&gt;&gt; Ben.<br>
&gt;&gt;<br>
&gt;&gt;&gt; On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; [fixing cc-list]<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On 10/21/16 11:59 AM, Flemming Andreasen wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On 10/21/16 11:21 AM, Cullen Jennings wrote:<br>
&gt;&gt;&gt;&gt;&gt; I think that is a bad way to run a WG. All I asked for=
 was a phone call to discuss this so we could get the issues on the table a=
nd discuss what is best. The chairs never even replied to my request for a =
WG call to discuss this.<br>
&gt;&gt;&gt;&gt; That is simply not true. You (and Christer) were explicitl=
y asked to setup a phone call on 10/6/16 to discuss this issue; a request t=
hat (like many other others) went unanswered or required extensive prodding=
 to get any attention.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; The list discussions that ensued from this resulted in=
 people other than me sugesting possibilities that were much better than an=
y of the three below -=C2=A0 none of which were considered in your consensu=
s call.<br>
&gt;&gt;&gt;&gt; I&#39;m not sure what those proposals are, nor were they b=
rought up in response to the consensus call.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; I don=E2=80=99t plan to appeal this but I am consideri=
ng if it=E2=80=99s worth my time to participate in this WG if we are not go=
ing to be willing to actually spend a short time to discuss possible soluti=
ons before taking a consensus call.=C2=A0 As input to that decisions, it wo=
uld be really useful to know why you refused to have a phone call on this t=
opic and what your policy in general is going to be toward discussions of p=
roposed solutions to problems in the future.<br>
&gt;&gt;&gt;&gt; My position is that we will try our very best to get to no=
t only consensus but to satisfy as many concerns as we possibly can. It doe=
s however require people to engage in a timely manner, and even when they d=
on&#39;t, we still do what we can, but at some point we need to move forwar=
d. As for the issue at hand, it has been discussed extensively, and several=
 changes were made to the draft to try and accommodate your requests.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The one major remaining issue I believe you have is around=
 whether this document updates RFC 4572. This has been discussed extensivel=
y on the wgchairs list; a discussion I initiated to try and help address yo=
ur concern. You may disagree with how that discussion concluded, but again,=
 to try and alleviate your concerns, a note was added to 4572-update to mak=
e it clear that the document does not make existing 4572 implementations no=
n-compliant with RFC 4572.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I believe the chairs, authors, and the WG at large has don=
e everything that can reasonably be done to try and address your concerns, =
and at this point we need to move forward.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Thanks<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; -- Flemming (as MMUSIC co-chair)<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; On Oct 19, 2016, at 6:43 AM, Flemming Andreasen &l=
t;<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank">fandreas@cisco.co=
m</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hi<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Following up on the consensus call, we have receiv=
ed 5 responses in favor of option a) below, one neutral, and one objection.=
 Looking at the document we have noted that backwards compatibility is hand=
led by the current text in the document and it also clearly states that it =
does not make current RFC 4572 implementation non-compliant with RFC 4572. =
Since we have not heard of any technical problems with proposal a), nor see=
n any tangible progress on how to address the objection, we are hereby decl=
aring rough consensus on option a). We will proceed with the publication re=
quest for the current draft while duly noting the &quot;roughness&quot; of =
the consensus based on the pending objection as part of this.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 Flemming &amp; Bo (MMUSIC chairs)<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; On 10/12/16 6:23 PM, Flemming Andreasen wrote:=
<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Greetings<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; There has been quite a bit of discussion on dr=
aft-ietf-mmusic-4572-update (currently -07), which had previously completed=
 WGLC when a few concerns were raised. The document currently:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. Clarifies the usage of multiple SDP &#39;fi=
ngerprint&#39; attributes<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. Updates the preferred cipher-suite with a s=
tronger cipher suite<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 3. Updates RFC 4572.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Item 1 seems to be generally agreeable, wherea=
s items 2 and 3 are not. The chairs are hereby soliciting WG feedback on ho=
w to proceed based on the following choices:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; a) Proceed with publication of 4572-update-07 =
in its current form (i.e. covering all 3 items above)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; b) Remove item 2 from 4572-update, i.e. do not=
 update the preferred cipher-suite<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; c) Remove item 3 from 4572-update, i.e. do not=
 indicate that this document constitutes an update to RFC 4572.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Note that choice a) is mutually exclusive with=
 b) and c), but b) and c) are not mutually exclusive.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Please let us know your preference wrt to the =
above no later than Friday October 14th.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Flemming &amp; Bo (M=
MUSIC chairs)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; ______________________________<wbr>___________=
______<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; mmusic mailing list<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" target=3D"_=
blank">mmusic@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listin=
fo/mmusic" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailma=
n/l<wbr>istinfo/mmusic</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; .<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; ______________________________<wbr>_______________=
__<br>
&gt;&gt;&gt;&gt;&gt;&gt; mmusic mailing list<br>
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" target=3D"_blan=
k">mmusic@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/m=
music" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l<=
wbr>istinfo/mmusic</a><br>
&gt;&gt;&gt;&gt;&gt; .<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt;&gt;&gt; mmusic mailing list<br>
&gt;&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusi=
c@ietf.org</a><br>
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" r=
el=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>isti=
nfo/mmusic</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt;&gt; mmusic mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ie=
tf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinf=
o/mmusic</a><br>
&gt;&gt;<br>
&gt;&gt; .<br>
&gt;&gt;<br>
&gt;<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
<br></blockquote></div><br></div>

--001a114a9710741675053fb01fdf--


From nobody Tue Oct 25 07:02:53 2016
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 BE5F9129667 for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 07:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.632
X-Spam-Level: 
X-Spam-Status: No, score=-4.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.431, 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 GidhEesrcLBq for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 07:02:49 -0700 (PDT)
Received: from alum-mailsec-scanner-3.mit.edu (alum-mailsec-scanner-3.mit.edu [18.7.68.14]) by ietfa.amsl.com (Postfix) with ESMTP id 868361295BF for <mmusic@ietf.org>; Tue, 25 Oct 2016 07:02:09 -0700 (PDT)
X-AuditID: 1207440e-c63ff70000000b1c-bf-580f65e0c7e4
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id E5.20.02844.0E56F085; Tue, 25 Oct 2016 10:02:08 -0400 (EDT)
Received: from [192.168.1.110] (c-73-186-127-100.hsd1.ma.comcast.net [73.186.127.100]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id u9PE27ng026229 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Tue, 25 Oct 2016 10:02:07 -0400
To: mmusic@ietf.org
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <CALiegfn2wEnOtJB2XsAckedAOsDVBa-ZN0ht+mVcT+YxgTxzcA@mail.gmail.com> <CAD5OKxte9UhFtgUjExBK_hedTUOWwZiMwzUbJSQxd9nAY+w1dg@mail.gmail.com> <CALiegfkDn8ws-2_Sq_qBhLxkzsb9VjG_dAvhenZARaU4xWk7PQ@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <ad72f829-c441-0a34-fc31-a913fab2db64@alum.mit.edu>
Date: Tue, 25 Oct 2016 10:02:06 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CALiegfkDn8ws-2_Sq_qBhLxkzsb9VjG_dAvhenZARaU4xWk7PQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOIsWRmVeSWpSXmKPExsUixO6iqPsglT/CoOOngsXU5Y9ZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVsXPCBMaCCywVN571sDUwXmPuYuTkkBAwkfjS9omti5GLQ0jg MqPEj7NHWUASQgJvmSRmTA4GsYUFYiQObZzFBmKLCAhLzHj7F6phApPEwdXX2UESbAJaEnMO /Qdr5hWwl/j2bj3YBhYBVYnFRxrB4qICaRLb1+1mhqgRlDg58wlYnFMgUGLapg6wOcwCZhLz Nj9khrDlJZq3zmaewMg3C0nLLCRls5CULWBkXsUol5hTmqubm5iZU5yarFucnJiXl1qka6yX m1mil5pSuokREmZ8Oxjb18scYhTgYFTi4WUw4IsQYk0sK67MPcQoycGkJMrb+BkoxJeUn1KZ kVicEV9UmpNafIhRgoNZSYR3Xwp/hBBvSmJlVWpRPkxKmoNFSZxXbYm6n5BAemJJanZqakFq EUxWhoNDSYL3CkijYFFqempFWmZOCUKaiYMTZDgP0PB/YMOLCxJzizPTIfKnGHU5Fvy4vZZJ iCUvPy9VSpw3CaRIAKQoozQPbg4sPbxiFAd6S5g3F5gshHiAqQVu0iugJUxASwTjeUCWlCQi pKQaGPMMWngsmjoYba5/9JbSd0yaIJeT9/WIveWiFV8dq7+rmnxUPb179RYjpgdXr0XXx7H8 F7x98tnVf+9/yh7qOHz166VOfgsrFht/lm/hc+4aPLF4vHSrJT/7m59r6l3O/43kvbU6bHtf 8X2Dru+tutIxmxp+ZUel2J4yDVhvulLU0n1ZxVOFiUosxRmJhlrMRcWJACsvSYXqAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/RtUqDl57fx0Dpp3_BsVkq4ENAlc>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 14:02:51 -0000

On 10/25/16 5:25 AM, IÃ±aki Baz Castillo wrote:
> 2016-10-25 0:23 GMT+02:00 Roman Shpount <roman@telurix.com>:
>> 2. In cases where ICE is required and non-ICE answer will not be accepted,
>> define a new transport tag ICE such as ICE/DTLS/SCPT.
>
> Yes please. In fact, ICE is a (virtual) transport (which can use UDP,
> TCP, SCTP or whatever behind the scenes), so it fits perfectly in
> there.

+1

(But it would be quite disturbing to have ICE/DTLS/SCTP and have ICE 
decide to use SCTP as *its* underlying transport - effectively 
SCTP/ICE/DTLS/SCTP.)

	Thanks,
	Paul


From nobody Tue Oct 25 07:05:45 2016
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 64F4B1294EE for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 07:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tKXtrkjJJ473 for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 07:05:43 -0700 (PDT)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61BF512945E for <mmusic@ietf.org>; Tue, 25 Oct 2016 07:05:43 -0700 (PDT)
Received: from resomta-ch2-04v.sys.comcast.net ([69.252.207.100]) by resqmta-ch2-01v.sys.comcast.net with SMTP id z2KJbvzhjTaLwz2MIbpIzh; Tue, 25 Oct 2016 14:05:42 +0000
Received: from [192.168.1.110] ([73.186.127.100]) by resomta-ch2-04v.sys.comcast.net with SMTP id z2MHbP1Or5RRtz2MIb3iLZ; Tue, 25 Oct 2016 14:05:42 +0000
To: Roman Shpount <roman@telurix.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <CALiegfn2wEnOtJB2XsAckedAOsDVBa-ZN0ht+mVcT+YxgTxzcA@mail.gmail.com> <CAD5OKxte9UhFtgUjExBK_hedTUOWwZiMwzUbJSQxd9nAY+w1dg@mail.gmail.com> <fb2a8750-afce-a082-4f47-6ed9c54d9847@alum.mit.edu> <CAD5OKxu81Hb4ExyWd2dKH2Vsa+=Qx4obMVtUiDDzHYgDLUprFw@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <bec4255e-fe2c-1d4c-bebc-67cc81ffb559@alum.mit.edu>
Date: Tue, 25 Oct 2016 10:05:41 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxu81Hb4ExyWd2dKH2Vsa+=Qx4obMVtUiDDzHYgDLUprFw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfDopLm2Ogsnb+vx5GrUpKht8z14ZfGm0TQTov+vEDVnOYR5CPkZjAx/lbU94eVwO/QGOhLPShEx/YQ29BSOXbO5IUt94Wmi6FOFAgUCn/uDc5GyFXb5I XWUe185AhwDHeVdeOm5Bww5PWNhzX8SPBHFJgVnYe9HSZGNPKaxCFz2w/AoXBNx95+7w2yfgnH+Ca9YG3SXBMlQ9U9XQVqeV5Ho=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/IM7NJQJlDsrOQavuXJIQfro3wHI>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 14:05:44 -0000

On 10/25/16 8:18 AM, Roman Shpount wrote:
>
> On Mon, Oct 24, 2016 at 9:31 PM, Paul Kyzivat <pkyzivat@alum.mit.edu
> <mailto:pkyzivat@alum.mit.edu>> wrote:
>
>     On 10/24/16 6:23 PM, Roman Shpount wrote:
>
>         My initial solution had two parts:
>
>         1. In cases where backwards compatibility with non-ICE endpoints is
>         required, require that ICE includes UDP candidates and uses UDP
>         candidate for default candidate. Essentially this considers UDP
>         protocol
>         version and UDP candidate support required to implement and
>         considers
>         TCP based protocol version and TCP ICE candidate support optional
>         extensions.
>
>         2. In cases where ICE is required and non-ICE answer will not be
>         accepted, define a new transport tag ICE such as ICE/DTLS/SCPT.
>         In this
>         case no default candidate should be included. c= line should use
>         transport address IN IP4 127.0.0.1. m= line should use port 7
>         (discard).
>         In this case no additional re-INVITE should be sent when ICE
>         nomination
>         process is completed. This should correspond to the normal use
>         case for
>         WebRTC browsers.
>
>
>     How about:
>
>     C=IN IP4 invalid
>
>     'invalid' is a syntactically valid FQDN and so can be used there,
>     and we have precedent from anonymous.invalid to use it to signify an
>     unusable address.
>
>     It also occurs to me that with the expansion of TLDs, maybe somebody
>     ought to reserve 'invalid' before somebody else reserves it to use it.
>
>
> As far as I know, IN IP4 127.0.0.1 and m= line with port 7 are already
> used by WebRTC enabled browsers to indicate that c= and m= line address
> should be discarded. Unless there is a significant benefit in using
> 'invalid' TLD in c= line, I do not see a reason to change the current
> implementations. I think the main reason current implementations use  IN
> IP4 127.0.0.1 is related to the fact that a lot of SDP end point
> implementations do not support domain names in c= line.

It was only a thought, to avoid using magic numbers. I don't especially 
care.

In any case, 'c=IN IP4 FQDN' is a bit ill-conceived, since it shouldn't 
be necessary to commit to IP4 or IP6 when using an FQDN. It really ought 
to be 'c=IN IP FQDN'.

	Thanks,
	Paul


From nobody Tue Oct 25 07:12:52 2016
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 23FEB1295DF for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 07:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 J9fnQoa6ejrd for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 07:12:44 -0700 (PDT)
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 1D3B212963A for <mmusic@ietf.org>; Tue, 25 Oct 2016 07:12:41 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-67-580f68586c42
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by  (Symantec Mail Security) with SMTP id 3A.66.02551.8586F085; Tue, 25 Oct 2016 16:12:40 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.90]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0319.002; Tue, 25 Oct 2016 16:12:38 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
Thread-Index: AQHSLjdzj3awKXzlYk+bYItwcSt6eaC4DHMAgAC5HYCAAE02AIAAJHo/
Date: Tue, 25 Oct 2016 14:12:38 +0000
Message-ID: <E84835B7-8650-4D71-9B9A-E2C8D6C89146@ericsson.com>
References: <D42A7728.113D4%christer.holmberg@ericsson.com> <CALiegfn2wEnOtJB2XsAckedAOsDVBa-ZN0ht+mVcT+YxgTxzcA@mail.gmail.com> <CAD5OKxte9UhFtgUjExBK_hedTUOWwZiMwzUbJSQxd9nAY+w1dg@mail.gmail.com> <CALiegfkDn8ws-2_Sq_qBhLxkzsb9VjG_dAvhenZARaU4xWk7PQ@mail.gmail.com>, <ad72f829-c441-0a34-fc31-a913fab2db64@alum.mit.edu>
In-Reply-To: <ad72f829-c441-0a34-fc31-a913fab2db64@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDLMWRmVeSWpSXmKPExsUyM2J7oG5EBn+EwdOpChZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJVx5nY7Y8Fkjoq7O9MaGI+xdTFyckgImEj0 /P3M2sXIxSEksJ5RYuX5u2AJIYHFjBJLr5d0MXJwsAlYSHT/0wYxRQQ0JCZtVQMxmQXUJa4u DgIpFhaIkbi18g87iC0iECtx9cx7VgjbTWLzy+1MIOUsAqoS8zfUgIR5Bewlzt6fzw6x9AiT xJ/FW5lBEpwCDhKTj00B62UUEJP4fmoNE4jNLCAucevJfCaIiwUkluw5zwxhi0q8fPyPFaJG T+LG1ClsELa2xLKFr5khlglKnJz5hGUCo8gsJKNmIWmZhaRlFpKWBYwsqxhFi1OLi3PTjYz1 Uosyk4uL8/P08lJLNjEC4+Dglt+6OxhXv3Y8xCjAwajEw6vgwxchxJpYVlyZe4hRgoNZSYT3 Rhp/hBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXFes5X3w4UE0hNLUrNTUwtSi2CyTBycUg2Ma6d5 5t92mnvh6aU7S6L/HV6elh+txp3mtKIhIuXtafmM2Yn/J27N6tN3473o661y62ewSITipw23 w5fZSt67bpue0M+95/q548XKd4VCC2PSmqpfMF30WSqTcpHP1Klr9Z/H1Y7vTNmS889V7zu9 uuLnzNWr9U9niNhdmhOm3Rdkdid5q2iwEktxRqKhFnNRcSIAXhXVQH8CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/te8XknT3TLOcNbCqlhtztF3iC0M>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: m- line matching default candidate in SDP answer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 14:12:50 -0000

Hi,

The transport selection would be done based on the available candidates, an=
d I doubt there would be any SCTP candidates.

Regards,

Christer=20

Sent from my iPhone

> On 25 Oct 2016, at 17.02, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
>> On 10/25/16 5:25 AM, I=F1aki Baz Castillo wrote:
>> 2016-10-25 0:23 GMT+02:00 Roman Shpount <roman@telurix.com>:
>>> 2. In cases where ICE is required and non-ICE answer will not be accept=
ed,
>>> define a new transport tag ICE such as ICE/DTLS/SCPT.
>>=20
>> Yes please. In fact, ICE is a (virtual) transport (which can use UDP,
>> TCP, SCTP or whatever behind the scenes), so it fits perfectly in
>> there.
>=20
> +1
>=20
> (But it would be quite disturbing to have ICE/DTLS/SCTP and have ICE deci=
de to use SCTP as *its* underlying transport - effectively SCTP/ICE/DTLS/SC=
TP.)
>=20
>    Thanks,
>    Paul
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Tue Oct 25 08:57:31 2016
Return-Path: <fluffy@iii.ca>
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 CDEB21296E8 for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 08:57:29 -0700 (PDT)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jD6zo8-em-KJ for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 08:57:25 -0700 (PDT)
Received: from smtp106.iad3a.emailsrvr.com (smtp106.iad3a.emailsrvr.com [173.203.187.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92A1D1296E3 for <mmusic@ietf.org>; Tue, 25 Oct 2016 08:57:25 -0700 (PDT)
Received: from smtp6.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp6.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id A0676E0433; Tue, 25 Oct 2016 11:57:20 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp6.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id C2279E0117;  Tue, 25 Oct 2016 11:57:19 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from dhcp-10-155-84-50.cisco.com ([UNAVAILABLE]. [128.107.241.162]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.7); Tue, 25 Oct 2016 11:57:20 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_DD2CC421-28E8-460B-8469-4FAB7E3D8D10"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CAD5OKxt7Z7ia6A4f1wM3K4Zit_sQDDvKRMgP4VHbqTfg8xZfCw@mail.gmail.com>
Date: Tue, 25 Oct 2016 08:57:20 -0700
Message-Id: <765B4794-F3FC-4E3C-BCC3-80B5167CE489@iii.ca>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <32BBB414-85BA-484C-954D-EDC8620F26DF@ericsson.com> <CABcZeBNKGK92=6moFbQ_4x1GuLoAZqQBrLZtY_AFnv6+iTnmyw@mail.gmail.com> <CAD5OKxt7Z7ia6A4f1wM3K4Zit_sQDDvKRMgP4VHbqTfg8xZfCw@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FnEyXTV_3LXvz-SrBLFeJAi6_BM>
Cc: Ben Campbell <ben@nostrum.com>, mmusic <mmusic@ietf.org>, ART ADs <art-ads@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 15:57:30 -0000

--Apple-Mail=_DD2CC421-28E8-460B-8469-4FAB7E3D8D10
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


Next Thursday is bad for me but any other morning (pacific time) next =
week would work for me.=20

> On Oct 25, 2016, at 6:02 AM, Roman Shpount <roman@telurix.com> wrote:
>=20
> Hi All,
>=20
> Any reasonable time US Eastern works for me.
>=20
> _____________
> Roman Shpount
>=20
> On Tue, Oct 25, 2016 at 1:07 AM, Eric Rescorla <ekr@rtfm.com =
<mailto:ekr@rtfm.com>> wrote:
> I am in Australia this week so next week would be easier. Otherwise, =
please make it late Pacific time so that it's not too early.
>=20
> -Ekr
>=20
>=20
> On Tue, Oct 25, 2016 at 3:33 PM, Christer Holmberg =
<christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>> =
wrote:
> Hi Flemming,
>=20
> Any day but Monday works for me.
>=20
> Regards,
>=20
> Christer
>=20
> Sent from my iPhone
>=20
> > On 25 Oct 2016, at 7.01, Flemming Andreasen <fandreas@cisco.com =
<mailto:fandreas@cisco.com>> wrote:
> >
> > Hi Ben
> >
> > We will get a poll setup as soon as we understand any major =
constraints from the key participants.
> >
> > Thanks
> >
> > -- Flemming
> >
> >
> >> On 10/21/16 4:49 PM, Ben Campbell wrote:
> >> Hi Everyone, please accept my apologies for waiting this long to =
weigh in.
> >>
> >> I think it's clear that multiple people are not happy with how we =
got to this point. But assigning blame doesn't help us make progress on =
the draft. I propose that we get over that, and instead focus instead on =
how to move forward. Email discussion doesn't seem to be helping. Maybe =
a call will.
> >>
> >> Flemming and/or Bo: Can you set up a Doodle poll to get Christer, =
Cullen, and other demonstratively  interested parties on a conference =
call? I will join if at all possible, but don't let scheduling around me =
stop a call from happening.
> >>
> >> Thanks!
> >>
> >> Ben.
> >>
> >>> On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:
> >>>
> >>> [fixing cc-list]
> >>>
> >>>> On 10/21/16 11:59 AM, Flemming Andreasen wrote:
> >>>>
> >>>>
> >>>>> On 10/21/16 11:21 AM, Cullen Jennings wrote:
> >>>>> I think that is a bad way to run a WG. All I asked for was a =
phone call to discuss this so we could get the issues on the table and =
discuss what is best. The chairs never even replied to my request for a =
WG call to discuss this.
> >>>> That is simply not true. You (and Christer) were explicitly asked =
to setup a phone call on 10/6/16 to discuss this issue; a request that =
(like many other others) went unanswered or required extensive prodding =
to get any attention.
> >>>>
> >>>>> The list discussions that ensued from this resulted in people =
other than me sugesting possibilities that were much better than any of =
the three below -  none of which were considered in your consensus call.
> >>>> I'm not sure what those proposals are, nor were they brought up =
in response to the consensus call.
> >>>>
> >>>>> I don=E2=80=99t plan to appeal this but I am considering if =
it=E2=80=99s worth my time to participate in this WG if we are not going =
to be willing to actually spend a short time to discuss possible =
solutions before taking a consensus call.  As input to that decisions, =
it would be really useful to know why you refused to have a phone call =
on this topic and what your policy in general is going to be toward =
discussions of proposed solutions to problems in the future.
> >>>> My position is that we will try our very best to get to not only =
consensus but to satisfy as many concerns as we possibly can. It does =
however require people to engage in a timely manner, and even when they =
don't, we still do what we can, but at some point we need to move =
forward. As for the issue at hand, it has been discussed extensively, =
and several changes were made to the draft to try and accommodate your =
requests.
> >>>>
> >>>> The one major remaining issue I believe you have is around =
whether this document updates RFC 4572. This has been discussed =
extensively on the wgchairs list; a discussion I initiated to try and =
help address your concern. You may disagree with how that discussion =
concluded, but again, to try and alleviate your concerns, a note was =
added to 4572-update to make it clear that the document does not make =
existing 4572 implementations non-compliant with RFC 4572.
> >>>>
> >>>> I believe the chairs, authors, and the WG at large has done =
everything that can reasonably be done to try and address your concerns, =
and at this point we need to move forward.
> >>>>
> >>>> Thanks
> >>>>
> >>>> -- Flemming (as MMUSIC co-chair)
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>>> On Oct 19, 2016, at 6:43 AM, Flemming Andreasen =
<fandreas@cisco.com <mailto:fandreas@cisco.com>> wrote:
> >>>>>>
> >>>>>> Hi
> >>>>>>
> >>>>>> Following up on the consensus call, we have received 5 =
responses in favor of option a) below, one neutral, and one objection. =
Looking at the document we have noted that backwards compatibility is =
handled by the current text in the document and it also clearly states =
that it does not make current RFC 4572 implementation non-compliant with =
RFC 4572. Since we have not heard of any technical problems with =
proposal a), nor seen any tangible progress on how to address the =
objection, we are hereby declaring rough consensus on option a). We will =
proceed with the publication request for the current draft while duly =
noting the "roughness" of the consensus based on the pending objection =
as part of this.
> >>>>>>
> >>>>>> Thanks
> >>>>>>
> >>>>>>    Flemming & Bo (MMUSIC chairs)
> >>>>>>
> >>>>>>
> >>>>>>> On 10/12/16 6:23 PM, Flemming Andreasen wrote:
> >>>>>>> Greetings
> >>>>>>>
> >>>>>>> There has been quite a bit of discussion on =
draft-ietf-mmusic-4572-update (currently -07), which had previously =
completed WGLC when a few concerns were raised. The document currently:
> >>>>>>> 1. Clarifies the usage of multiple SDP 'fingerprint' =
attributes
> >>>>>>> 2. Updates the preferred cipher-suite with a stronger cipher =
suite
> >>>>>>> 3. Updates RFC 4572.
> >>>>>>>
> >>>>>>> Item 1 seems to be generally agreeable, whereas items 2 and 3 =
are not. The chairs are hereby soliciting WG feedback on how to proceed =
based on the following choices:
> >>>>>>>
> >>>>>>> a) Proceed with publication of 4572-update-07 in its current =
form (i.e. covering all 3 items above)
> >>>>>>>
> >>>>>>> b) Remove item 2 from 4572-update, i.e. do not update the =
preferred cipher-suite
> >>>>>>>
> >>>>>>> c) Remove item 3 from 4572-update, i.e. do not indicate that =
this document constitutes an update to RFC 4572.
> >>>>>>>
> >>>>>>>
> >>>>>>> Note that choice a) is mutually exclusive with b) and c), but =
b) and c) are not mutually exclusive.
> >>>>>>>
> >>>>>>> Please let us know your preference wrt to the above no later =
than Friday October 14th.
> >>>>>>>
> >>>>>>>
> >>>>>>> Thanks
> >>>>>>>
> >>>>>>>       Flemming & Bo (MMUSIC chairs)
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> mmusic mailing list
> >>>>>>> mmusic@ietf.org <mailto:mmusic@ietf.org>
> >>>>>>> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
> >>>>>>> .
> >>>>>>>
> >>>>>> _______________________________________________
> >>>>>> mmusic mailing list
> >>>>>> mmusic@ietf.org <mailto:mmusic@ietf.org>
> >>>>>> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
> >>>>> .
> >>>>>
> >>>>
> >>>> _______________________________________________
> >>>> mmusic mailing list
> >>>> mmusic@ietf.org <mailto:mmusic@ietf.org>
> >>>> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
> >>>
> >>> _______________________________________________
> >>> mmusic mailing list
> >>> mmusic@ietf.org <mailto:mmusic@ietf.org>
> >>> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
> >>
> >> .
> >>
> >
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org <mailto:mmusic@ietf.org>
> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
>=20
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org <mailto:mmusic@ietf.org>
> https://www.ietf.org/mailman/listinfo/mmusic =
<https://www.ietf.org/mailman/listinfo/mmusic>
>=20
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


--Apple-Mail=_DD2CC421-28E8-460B-8469-4FAB7E3D8D10
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; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D""><br class=3D""></div>Next Thursday is bad for =
me but any other morning (pacific time) next week would work for =
me.&nbsp;<div class=3D""><br class=3D""><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">On Oct 25, 2016, at 6:02 AM, 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"">Hi All,<div class=3D""><br class=3D""></div><div class=3D"">Any=
 reasonable time US Eastern works for me.</div></div><div =
class=3D"gmail_extra"><br clear=3D"all" class=3D""><div class=3D""><div =
class=3D"gmail_signature" =
data-smartmail=3D"gmail_signature">_____________<br class=3D"">Roman =
Shpount</div></div>
<br class=3D""><div class=3D"gmail_quote">On Tue, Oct 25, 2016 at 1:07 =
AM, Eric Rescorla <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:ekr@rtfm.com" target=3D"_blank" =
class=3D"">ekr@rtfm.com</a>&gt;</span> wrote:<br class=3D""><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><div dir=3D"ltr" class=3D"">I am in Australia =
this week so next week would be easier. Otherwise, please make it late =
Pacific time so that it's not too early.<div class=3D""><br =
class=3D""><div class=3D"">-Ekr</div><div class=3D""><br =
class=3D""></div></div></div><div class=3D"HOEnZb"><div class=3D"h5"><div =
class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Tue, =
Oct 25, 2016 at 3:33 PM, Christer Holmberg <span dir=3D"ltr" =
class=3D"">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" =
target=3D"_blank" class=3D"">christer.holmberg@ericsson.<wbr =
class=3D"">com</a>&gt;</span> wrote:<br class=3D""><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">Hi Flemming,<br class=3D"">
<br class=3D"">
Any day but Monday works for me.<br class=3D"">
<br class=3D"">
Regards,<br class=3D"">
<br class=3D"">
Christer<br class=3D"">
<br class=3D"">
Sent from my iPhone<br class=3D"">
<div class=3D"m_5864946379813227998HOEnZb"><div =
class=3D"m_5864946379813227998h5"><br class=3D"">
&gt; On 25 Oct 2016, at 7.01, Flemming Andreasen &lt;<a =
href=3D"mailto:fandreas@cisco.com" target=3D"_blank" =
class=3D"">fandreas@cisco.com</a>&gt; wrote:<br class=3D"">
&gt;<br class=3D"">
&gt; Hi Ben<br class=3D"">
&gt;<br class=3D"">
&gt; We will get a poll setup as soon as we understand any major =
constraints from the key participants.<br class=3D"">
&gt;<br class=3D"">
&gt; Thanks<br class=3D"">
&gt;<br class=3D"">
&gt; -- Flemming<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;&gt; On 10/21/16 4:49 PM, Ben Campbell wrote:<br class=3D"">
&gt;&gt; Hi Everyone, please accept my apologies for waiting this long =
to weigh in.<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; I think it's clear that multiple people are not happy with how =
we got to this point. But assigning blame doesn't help us make progress =
on the draft. I propose that we get over that, and instead focus instead =
on how to move forward. Email discussion doesn't seem to be helping. =
Maybe a call will.<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; Flemming and/or Bo: Can you set up a Doodle poll to get =
Christer, Cullen, and other demonstratively&nbsp; interested parties on =
a conference call? I will join if at all possible, but don't let =
scheduling around me stop a call from happening.<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; Thanks!<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; Ben.<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt;&gt; On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:<br =
class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt; [fixing cc-list]<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; On 10/21/16 11:59 AM, Flemming Andreasen wrote:<br =
class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt; On 10/21/16 11:21 AM, Cullen Jennings wrote:<br =
class=3D"">
&gt;&gt;&gt;&gt;&gt; I think that is a bad way to run a WG. All I asked =
for was a phone call to discuss this so we could get the issues on the =
table and discuss what is best. The chairs never even replied to my =
request for a WG call to discuss this.<br class=3D"">
&gt;&gt;&gt;&gt; That is simply not true. You (and Christer) were =
explicitly asked to setup a phone call on 10/6/16 to discuss this issue; =
a request that (like many other others) went unanswered or required =
extensive prodding to get any attention.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt; The list discussions that ensued from this resulted =
in people other than me sugesting possibilities that were much better =
than any of the three below -&nbsp; none of which were considered in =
your consensus call.<br class=3D"">
&gt;&gt;&gt;&gt; I'm not sure what those proposals are, nor were they =
brought up in response to the consensus call.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt; I don=E2=80=99t plan to appeal this but I am =
considering if it=E2=80=99s worth my time to participate in this WG if =
we are not going to be willing to actually spend a short time to discuss =
possible solutions before taking a consensus call.&nbsp; As input to =
that decisions, it would be really useful to know why you refused to =
have a phone call on this topic and what your policy in general is going =
to be toward discussions of proposed solutions to problems in the =
future.<br class=3D"">
&gt;&gt;&gt;&gt; My position is that we will try our very best to get to =
not only consensus but to satisfy as many concerns as we possibly can. =
It does however require people to engage in a timely manner, and even =
when they don't, we still do what we can, but at some point we need to =
move forward. As for the issue at hand, it has been discussed =
extensively, and several changes were made to the draft to try and =
accommodate your requests.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; The one major remaining issue I believe you have is =
around whether this document updates RFC 4572. This has been discussed =
extensively on the wgchairs list; a discussion I initiated to try and =
help address your concern. You may disagree with how that discussion =
concluded, but again, to try and alleviate your concerns, a note was =
added to 4572-update to make it clear that the document does not make =
existing 4572 implementations non-compliant with RFC 4572.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; I believe the chairs, authors, and the WG at large has =
done everything that can reasonably be done to try and address your =
concerns, and at this point we need to move forward.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Thanks<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; -- Flemming (as MMUSIC co-chair)<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt; On Oct 19, 2016, at 6:43 AM, Flemming Andreasen =
&lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank" =
class=3D"">fandreas@cisco.com</a>&gt; wrote:<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt; Hi<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt; Following up on the consensus call, we have =
received 5 responses in favor of option a) below, one neutral, and one =
objection. Looking at the document we have noted that backwards =
compatibility is handled by the current text in the document and it also =
clearly states that it does not make current RFC 4572 implementation =
non-compliant with RFC 4572. Since we have not heard of any technical =
problems with proposal a), nor seen any tangible progress on how to =
address the objection, we are hereby declaring rough consensus on option =
a). We will proceed with the publication request for the current draft =
while duly noting the "roughness" of the consensus based on the pending =
objection as part of this.<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt; Thanks<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; Flemming &amp; Bo (MMUSIC =
chairs)<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; On 10/12/16 6:23 PM, Flemming Andreasen =
wrote:<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Greetings<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; There has been quite a bit of discussion on =
draft-ietf-mmusic-4572-update (currently -07), which had previously =
completed WGLC when a few concerns were raised. The document =
currently:<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. Clarifies the usage of multiple SDP =
'fingerprint' attributes<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. Updates the preferred cipher-suite with =
a stronger cipher suite<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 3. Updates RFC 4572.<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Item 1 seems to be generally agreeable, =
whereas items 2 and 3 are not. The chairs are hereby soliciting WG =
feedback on how to proceed based on the following choices:<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; a) Proceed with publication of =
4572-update-07 in its current form (i.e. covering all 3 items above)<br =
class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; b) Remove item 2 from 4572-update, i.e. do =
not update the preferred cipher-suite<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; c) Remove item 3 from 4572-update, i.e. do =
not indicate that this document constitutes an update to RFC 4572.<br =
class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Note that choice a) is mutually exclusive =
with b) and c), but b) and c) are not mutually exclusive.<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Please let us know your preference wrt to =
the above no later than Friday October 14th.<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp;Flemming &amp; Bo =
(MMUSIC chairs)<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; ______________________________<wbr =
class=3D"">_________________<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; mmusic mailing list<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" =
target=3D"_blank" class=3D"">mmusic@ietf.org</a><br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer" =
target=3D"_blank" class=3D"">https://www.ietf.org/mailman/l<wbr =
class=3D"">istinfo/mmusic</a><br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt; .<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt; ______________________________<wbr =
class=3D"">_________________<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt; mmusic mailing list<br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" =
target=3D"_blank" class=3D"">mmusic@ietf.org</a><br class=3D"">
&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer" =
target=3D"_blank" class=3D"">https://www.ietf.org/mailman/l<wbr =
class=3D"">istinfo/mmusic</a><br class=3D"">
&gt;&gt;&gt;&gt;&gt; .<br class=3D"">
&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; ______________________________<wbr =
class=3D"">_________________<br class=3D"">
&gt;&gt;&gt;&gt; mmusic mailing list<br class=3D"">
&gt;&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank" =
class=3D"">mmusic@ietf.org</a><br class=3D"">
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/l<wbr =
class=3D"">istinfo/mmusic</a><br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt; ______________________________<wbr =
class=3D"">_________________<br class=3D"">
&gt;&gt;&gt; mmusic mailing list<br class=3D"">
&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank" =
class=3D"">mmusic@ietf.org</a><br class=3D"">
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/l<wbr =
class=3D"">istinfo/mmusic</a><br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; .<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;<br class=3D"">
<br class=3D"">
______________________________<wbr class=3D"">_________________<br =
class=3D"">
mmusic mailing list<br class=3D"">
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank" =
class=3D"">mmusic@ietf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/l<wbr =
class=3D"">istinfo/mmusic</a><br class=3D"">
</div></div></blockquote></div><br class=3D""></div>
</div></div><br class=3D"">______________________________<wbr =
class=3D"">_________________<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"">
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/<wbr =
class=3D"">listinfo/mmusic</a><br class=3D"">
<br class=3D""></blockquote></div><br class=3D""></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=_DD2CC421-28E8-460B-8469-4FAB7E3D8D10--


From nobody Tue Oct 25 09:17:01 2016
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 2D5D11297B8 for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 09:16:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 fwyviwDB3B_M for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 09:16:57 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 858A812973E for <mmusic@ietf.org>; Tue, 25 Oct 2016 09:16:57 -0700 (PDT)
Received: from [130.209.247.112] (port=50861 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1bz4PG-0002qC-4m; Tue, 25 Oct 2016 17:16:56 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <D4350F28.11B2F%christer.holmberg@ericsson.com>
Date: Tue, 25 Oct 2016 17:16:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A15F1471-4C66-4462-8BCA-01A79C5B0203@csperkins.org>
References: <D4350F28.11B2F%christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/y_3Yux6VZSa12_ZyNjtbFkZ4n6c>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: BUNDLE-35
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 16:16:59 -0000

Hi,

> On 25 Oct 2016, at 11:24, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> I=92ve submitted a new version (-35) of BUNDLE.
>=20
> The text now talks about =93associating RTP streams with m- lines=94 =
(instead of associating RTP packets).

I think this new text is good, and addresses most of my concerns. I just =
have a few details outstanding:

- Section 9.1, last paragraph: I suggest changing =93associate a =
received (S)RTP packet with=94 to =93associate the packets in a received =
SRTP stream with=94.

- Section 10.1, 1st paragraph: The second sentence (=93Disjoint BUNDLE =
groups will form multiple RTP sessions, one per BUNDLE group=94) is =
probably true, but depends on the RTP topology, since a middlebox could =
bridge the different BUNDLE groups together into a single RTP session. I =
suggest deleting this sentence.=20

- Section 10.2, 1st paragraph: At the end of the first sentence, you =
might cite RFC7656 for the definition of the term RTP Stream.

- Section 10.2, 7th paragraph: This seems correct, but I found the =
phrasing unclear. Something like the following might be clearer:

   The mapping from an SSRC to an identification-tag is carried in RTCP
   SDES packets or in RTP header extensions, as described in Section 14.
   Since a compound RTCP packet can contain multiple RTCP SDES packets,=20=

   and each RTCP SDES packet can contain multiple chunks, an RTCP packet
   can contain several SSRC to identification-tag mappings. The offerer
   and answerer maintain tables mapping RTP streams identified by SSRC,
   to =93m=3D=93 lines identified by the identification-tag. These =
tables are
   updated each time an RTP/RTCP packet containing one or more mappings=20=

   from SSRC to identification-tag is received. Note that the mapping=20
   from SSRC to identification-tag can change at any time during an RTP=20=

   session.

- Section 10.2, 8th paragraph: The last sentence might be clearer =
written =93Note that RTCP packets can report on multiple RTP streams=94. =
Also, the XML formatting is messed up in the middle of the paragraph.

- Section 14, 3rd paragraph: Suggest changing =93=85to associate =
received RTCP- and RTP packets with=85=93 to =93=85to associated each =
RTP stream with=85=94.

Colin



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





From nobody Tue Oct 25 10:17:58 2016
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 B260912985B; Tue, 25 Oct 2016 10:17:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Mirja Kuehlewind" <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147741587672.1323.3788097761711986441.idtracker@ietfa.amsl.com>
Date: Tue, 25 Oct 2016 10:17:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FVeOkO40ru4cyr1-42vvX4BV28g>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-mmusic-sdp-mux-attributes-14=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 17:17:57 -0000

Mirja KÃ¼hlewind has entered the following ballot position for
draft-ietf-mmusic-sdp-mux-attributes-14: No Objection

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


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


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



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

Two comments:

1) The category TDB is not fully clear to me. It says: "The attributes in
the TBD category have not been analyzed", but why? Can you further
explain?

2) Is the new registry for the Mux Category really needed? Is it expected
to (much) more categories in future?



From nobody Tue Oct 25 10:30:46 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A00BA1295AF; Tue, 25 Oct 2016 10:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 pu6t96lxHoWX; Tue, 25 Oct 2016 10:30:42 -0700 (PDT)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 4D22F12951A; Tue, 25 Oct 2016 10:30:39 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id w3so5133989ywg.1; Tue, 25 Oct 2016 10:30:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OxVU8QZRJHo0cZ8bewYb7W2UHQSlmg6aatvRO+Bbuqk=; b=HJsx8AUs+fX6+7ikKGNLtoovqgRNFB/TwWWRsLa9fBVH2NXQZgi+YvkCNtl4TUS01O LE2XzC1NH3i8QVqsCtmkJBoEGN7GEobS1/DF4ANCKITQphYUe2Zd65MWupphFCir4o2n gmyybSpdw2Vmsm3PwksIaEIUmYq6g/P/jVgpagOonDrYFjZg10uxBBtOpbFPKcnjt5Ts FETBKTokVJHiox+z+pxW3lgm67BxQztFH1qIfyiMMpKUtsZV6C1GhPoanJpn/znF877H 7U/WzP6d34XJLZI7AoKRg7WAelaAlmDdME5p56jzO7TyQxEskJHU0HrfpoOfwQJIGGD5 sNsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OxVU8QZRJHo0cZ8bewYb7W2UHQSlmg6aatvRO+Bbuqk=; b=cHqpWhjp3vVS1qUQqeoKmve39LGkiUW+zpSCXF+sWr0QNgJE4uTfoYXuX5uaJnRA12 F5BdzE8pbudDq2lbOvS3lHGQPWEo+CkeTEunOie6M0cz0rzm3XWVv7p+7JBlXkN//DQK GMsGh4AUoo7R+AceJR2MM8h/+zHHGVWSVAdQ7Ftl/9LsOME9KhJseKDhheogsKxhW3EQ WKAFQijmaDGsLN7U3LPmWHyfXZikY9EYtXGj5NU+PLv6LgjMO9zsH7HWI5q0jiXZU5iA FEFG0JDqDuuC47HuNspm7kZR+8Qo2XUo2z2FI+ppqolCmBJGtYjwUmWe7Y6d9I00NPOm uNjA==
X-Gm-Message-State: ABUngvdMiBa3bQUIILJc4L92KIHKia7A6NvQMHV7/rphbn+LQi5RsEUZXKBQinetWmFYZbY6mkoeIBD4nKLrDA==
X-Received: by 10.129.78.133 with SMTP id c127mr21226818ywb.172.1477416637520;  Tue, 25 Oct 2016 10:30:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.158.73 with HTTP; Tue, 25 Oct 2016 10:30:37 -0700 (PDT)
In-Reply-To: <147741587672.1323.3788097761711986441.idtracker@ietfa.amsl.com>
References: <147741587672.1323.3788097761711986441.idtracker@ietfa.amsl.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Tue, 25 Oct 2016 10:30:37 -0700
Message-ID: <CAMRcRGTEj-HwOvWtCi5orEKurMirOZLepG2sB1Ya7x-nJU7Pvg@mail.gmail.com>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
Content-Type: multipart/alternative; boundary=001a114dd180dd6162053fb3dd7f
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/7nYZ6eGpYjzcmevY4_IrdrRA1mA>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, The IESG <iesg@ietf.org>, mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-mmusic-sdp-mux-attributes-14=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 17:30:45 -0000

--001a114dd180dd6162053fb3dd7f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello Mirja ,

Thanks for the review. Please see inline for the response.

On Tue, Oct 25, 2016 at 10:17 AM, Mirja Kuehlewind <ietf@kuehlewind.net>
wrote:

> Mirja K=C3=BChlewind has entered the following ballot position for
> draft-ietf-mmusic-sdp-mux-attributes-14: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Two comments:
>
> 1) The category TDB is not fully clear to me. It says: "The attributes in
> the TBD category have not been analyzed", but why? Can you further
> explain?
>

[Suhas]: The category TBD serves 2 purposes.

Purpose 1: The WG decided to stop draft updates with new attribute analysis
towards the end of 2015 when it was decided to take the draft to the last
call. This was done so to keep the draft edits under control and not to
keep in a edit-loop forever when new SDP attributes popped up. All those
attributes that were added since then will get the category TBD in the IANA
registry and the individual drafts that define those attributes take on the
role of deciding the MUX category and the corresponding IANA updates.
An excerpt from Section 15.2 along the same lines below:
"

For the entries in the existing subregistries, under the "Session
   Description Protocol (SDP) Parameters" registry, that lack a value
   for the "Mux Category" in this specification will get a value of
   "TBD"

"


Purpose 2: There are few attributes in the current analysis of the draft
that are assigned the category TBD. A specific example is Section 5.54 (ITU
T.38). I have included the note below to explain in the section the reasons
why the WG decided the category as TBD.
"

NOTE: As per section 9.1 of [I-D.ietf-mmusic-sdp-bundle-negotiation],
   there exists no publicly available specification that defines
   procedures for multiplexing/demultiplexing fax protocols flows over a
   single 5-tuple.  Once such a specification is available, the
   multiplexing category assignments for the attributes in this section
   could be revisited.

"
Since we don't have a standard specification to define the mux/demux of Fax
protocols with RTP, the only category that made sense was TBD. This state
can be updated once such a spec is defined in the future. Similar reasoning
applies to other TBD attributes.

Please let me know if the above answers your concerns.



>
> 2) Is the new registry for the Mux Category really needed? Is it expected
> to (much) more categories in future?
>

[Suhas] -  We need the registry to list the currently defined Mux
Categories and also we do see there might be couple of more categories (if
not many) that might get defined in the future.


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

--001a114dd180dd6162053fb3dd7f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Mirja ,<div><br></div><div>Thanks for the review. Pl=
ease see inline for the response.</div><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Tue, Oct 25, 2016 at 10:17 AM, Mirja Kuehlewind <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:ietf@kuehlewind.net" target=3D"_blank=
">ietf@kuehlewind.net</a>&gt;</span> wrote:<br><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">Mirja K=C3=BChlewind has entered the following ballot=
 position for<br>
draft-ietf-mmusic-sdp-mux-<wbr>attributes-14: No Objection<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss-crit=
eria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/iesg/<=
wbr>statement/discuss-criteria.<wbr>html</a><br>
for more information about IESG DISCUSS and COMMENT positions.<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attri=
butes/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<=
wbr>doc/draft-ietf-mmusic-sdp-mux-<wbr>attributes/</a><br>
<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
COMMENT:<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
Two comments:<br>
<br>
1) The category TDB is not fully clear to me. It says: &quot;The attributes=
 in<br>
the TBD category have not been analyzed&quot;, but why? Can you further<br>
explain?<br></blockquote><div><br></div><div>[Suhas]: The category TBD serv=
es 2 purposes.=C2=A0</div><div><br></div><div>Purpose 1: The WG decided to =
stop draft updates with new attribute analysis towards the end of 2015 when=
 it was decided to take the draft to the last call. This was done so to kee=
p the draft edits under control and not to keep in a edit-loop forever when=
 new SDP attributes popped up. All those attributes that were added since t=
hen will get the category TBD in the IANA registry and the individual draft=
s that define those attributes take on the role of deciding the MUX categor=
y and the corresponding IANA updates.</div><div>An excerpt from Section 15.=
2 along the same lines below:</div><div>&quot;</div><div><pre style=3D"box-=
sizing:border-box;overflow:auto;font-family:&quot;pt mono&quot;,monaco,mono=
space;font-size:14px;padding:10px;margin-top:0px;margin-bottom:10.5px;line-=
height:1.214;color:rgb(0,0,0);word-break:break-all;word-wrap:break-word;bac=
kground-color:rgb(255,253,245);border:1px solid rgb(204,204,204);border-rad=
ius:4px">For the entries in the existing subregistries, under the &quot;Ses=
sion
   Description Protocol (SDP) Parameters&quot; registry, that lack a value
   for the &quot;Mux Category&quot; in this specification will get a value =
of
   &quot;TBD&quot;</pre></div><div>&quot;</div><div><br></div><div><br></di=
v><div>Purpose 2: There are few attributes in the current analysis of the d=
raft that are assigned the category TBD. A specific example is Section 5.54=
 (ITU T.38). I have included the note below to explain in the section the r=
easons why the WG decided the category as TBD.</div><div>&quot;</div><div><=
pre style=3D"box-sizing:border-box;overflow:auto;font-family:&quot;pt mono&=
quot;,monaco,monospace;font-size:14px;padding:10px;margin-top:0px;margin-bo=
ttom:10.5px;line-height:1.214;color:rgb(0,0,0);word-break:break-all;word-wr=
ap:break-word;background-color:rgb(255,253,245);border:1px solid rgb(204,20=
4,204);border-radius:4px">NOTE: As per section 9.1 of [I-D.ietf-mmusic-sdp-=
bundle-negotiation],
   there exists no publicly available specification that defines
   procedures for multiplexing/demultiplexing fax protocols flows over a
   single 5-tuple.  Once such a specification is available, the
   multiplexing category assignments for the attributes in this section
   could be revisited.</pre></div><div>&quot;</div><div>Since we don&#39;t =
have a standard specification to define the mux/demux of Fax protocols with=
 RTP, the only category that made sense was TBD. This state can be updated =
once such a spec is defined in the future. Similar reasoning applies to oth=
er TBD attributes.</div><div><br></div><div>Please let me know if the above=
 answers your concerns.</div><div><br></div><div>=C2=A0</div><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">
<br>
2) Is the new registry for the Mux Category really needed? Is it expected<b=
r>
to (much) more categories in future?<br></blockquote><div><br></div><div>[S=
uhas] - =C2=A0We need the registry to list the currently defined Mux Catego=
ries and also we do see there might be couple of more categories (if not ma=
ny) that might get defined in the future.</div><div>=C2=A0</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">
<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
</blockquote></div><br></div></div>

--001a114dd180dd6162053fb3dd7f--


From nobody Tue Oct 25 13:32:46 2016
Return-Path: <spencerdawkins.ietf@gmail.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 B825212987D; Tue, 25 Oct 2016 13:32:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147742756171.8565.11705230224719531567.idtracker@ietfa.amsl.com>
Date: Tue, 25 Oct 2016 13:32:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/X2_TEPv9heppLvS34U2MfXSPVA8>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] Spencer Dawkins' Yes on draft-ietf-mmusic-sdp-mux-attributes-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 20:32:42 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-mmusic-sdp-mux-attributes-14: Yes

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


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


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



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

This document is a work of art. Thank you folks for accepting the
challenge, because it's important.

I have a couple of observations, to go along with my Yes ballot. Please
do the right thing.

I know Mirja also pushed on the TBD category, but I find RFC 2119 "SHOULD
NOT" to be problematic.

   The attributes in the TBD category have not been analyzed under the
   proposed multiplexing framework and SHOULD NOT be multiplexed.
   
The point of SHOULD (NOT) is that you don't do this unless you understand
the risks, and in this case, it seems to me that you don't know the
risks. If you're determined to multiplex the TBD attribute "frommet=",
won't you have to do your own analysis? Wouldn't that mean you might make
assumptions ("it's IDENTICAL") that conflict with the analysis other
implementers are doing ("it's TRANSPORT")?

I could imagine a couple of approaches that might be helpful here.

Saying "MUST NOT be multiplexed" would avoid implementers doing their own
analysis and coming up with conflicting answers. Is it obvious why this
is "SHOULD NOT" instead of "MUST NOT"? In other words, who needs to
multiplex TBD attributes, and why?

Saying "cannot be assumed to be safe when multiplexed" probably captures
what I think you are saying. 

Would it be clearer if the category was called UNKNOWN?

In this text,

16.  Security Considerations

   This document does not add any new security considerations beyond the
   existing considerations in the RTP RFCs ([RFC3550] and [RFC3711])
   that are referenced by this specification.
   
I don't understand how the first paragraph ^^ and the third paragraph of
the section are compatible, because you're referring to issues described
in this specification. But if you delete the first paragraph, leaving
only 

   The primary security for RTP including the way it is used here is
   described in [RFC3550] and [RFC3711].

   When multiplexing SDP attributes with the category "CAUTION", the
   implementations should be aware of possible issues as described in
   this specification.

the security considerations would be consistent.



From nobody Tue Oct 25 14:51:30 2016
Return-Path: <adam@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9AF31293E8 for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 14:51:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.33
X-Spam-Level: 
X-Spam-Status: No, score=-2.33 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.431] 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 mbBJxm-tu6tA for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 14:51:25 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7888C12959D for <mmusic@ietf.org>; Tue, 25 Oct 2016 14:51:25 -0700 (PDT)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u9PLpJ9M031880 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 25 Oct 2016 16:51:21 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110] claimed to be Orochi.local
To: Peter Thatcher <pthatcher@google.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <CAJrXDUG8FJYswsssiJKZHUw+9oWcMGJ3n=qSOckhx=dhR=8nUQ@mail.gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <dc4720f2-a43c-8811-fc7d-eefebf2d7809@nostrum.com>
Date: Tue, 25 Oct 2016 16:51:18 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CAJrXDUG8FJYswsssiJKZHUw+9oWcMGJ3n=qSOckhx=dhR=8nUQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------1952766359FD7C3FFA6D067C"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3ZR2P_K0qveL9Wrch7r07UMJBjs>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-rid-07
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 21:51:29 -0000

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

Thanks for the comments!

On 9/1/16 17:01, Peter Thatcher wrote:
> 1.  The things added to an a=rid line are typically called 
> "restrictions" and "constraints".  But in one place they are called 
> "characteristics". Further, one of the "constraints" is "depend", 
> which isn't a restriction at all, and more like a characteristic.  So 
> which is it?   I think that it would make sense to call them generally 
> "characteristics" (or a similar word, like "properties") and say that 
> the most common use of these "characteristics" is "restrictions" or 
> "constraints".

These are two different concepts. Codec properties (which I'd called 
"characteristics" in a couple places, but changed to "properties" to be 
consistent) refer to a specific value that a codec has, while 
"restrictions" (which I'd called "constraints" in a few places, but 
changed to "restrictions" to be consistent) describes the value(s) that 
these property are allowed to assume.

You can think of it this way: a volume knob may be restricted to the 
range zero through five, but have the property of being set to three.

> 2.  Sometimes the text says "constrain" and "constraint", other times 
> "restrict" and "restriction".  Can we just pick one and use it 
> consistently?  I've "a=rid" is a "restriction identifier", then I'd 
> suggest we go with restrict/restriction, but I'd be fine either way.  
> As long as we're consistent around one set of words.

I've removed "constraint" completely (Bernard raises a good point that 
this is a terminology collision with W3C WebRTC specs) in favor of 
"restriction."

> 3.  There are a bunch of rules that end up saying to remove/discard a 
> line. Sometimes the text says to remove, sometimes to discard, and 
> sometimes even "discard and not include".  Can we pick one and be 
> consistent?  I'd prefer "discard and not include", or maybe just 
> "discard", both of which are more clear to me than "remove".

Sure, I've changed them all to "discard."

> 4.  There is a phrase which says "If the offerer wishes the answerer 
> to have the ability to specify a constraint, but does not wish to set 
> a value itself, it MUST ...".  Is it normal to write MUST sentence in 
> the form "if you want X, you MUST do Y?"  Isn't it more correct to say 
> "if you want X, you MAY do Y"?  It's the answerer of the empty 
> constraint that MUST interpret it a certain way, but there's no reason 
> that the offerer MUST set the empty constraint.  That's just one thing 
> it may choose to do.

I've just removed the normative term here, since I don't think it adds 
any clarity. The formulation is now: "If you want X, you do Y."

/a

--------------1952766359FD7C3FFA6D067C
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Thanks for the comments!<br>
      <br>
      On 9/1/16 17:01, Peter Thatcher wrote:<br>
    </div>
    <blockquote
cite="mid:CAJrXDUG8FJYswsssiJKZHUw+9oWcMGJ3n=qSOckhx=dhR=8nUQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">1.Â  The things added to an a=rid line are typically
        called "restrictions" and "constraints".Â  But in one place they
        are called "characteristics". Further, one of the "constraints"
        is "depend", which isn't a restriction at all, and more like a
        characteristic.Â  So which is it? Â  I think that it would make
        sense to call them generally "characteristics" (or a similar
        word, like "properties") and say that the most common use of
        these "characteristics" is "restrictions" or "constraints".</div>
    </blockquote>
    <br>
    These are two different concepts. Codec properties (which I'd called
    "characteristics" in a couple places, but changed to "properties" to
    be consistent) refer to a specific value that a codec has, while
    "restrictions" (which I'd called "constraints" in a few places, but
    changed to "restrictions" to be consistent) describes the value(s)
    that these property are allowed to assume.<br>
    <br>
    You can think of it this way: a volume knob may be restricted to the
    range zero through five, but have the property of being set to
    three.<br>
    <br>
    <blockquote
cite="mid:CAJrXDUG8FJYswsssiJKZHUw+9oWcMGJ3n=qSOckhx=dhR=8nUQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">2.Â  Sometimes the text says "constrain" and
        "constraint", other times "restrict" and "restriction".Â  Can we
        just pick one and use it consistently?Â  I've "a=rid" is a
        "restriction identifier", then I'd suggest we go with
        restrict/restriction, but I'd be fine either way.Â  As long as
        we're consistent around one set of words.</div>
    </blockquote>
    <br>
    I've removed "constraint" completely (Bernard raises a good point
    that this is a terminology collision with W3C WebRTC specs) in favor
    of "restriction."<br>
    <br>
    <blockquote
cite="mid:CAJrXDUG8FJYswsssiJKZHUw+9oWcMGJ3n=qSOckhx=dhR=8nUQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_default"
          style="font-family:arial,helvetica,sans-serif">3.Â  There are a
          bunch of rules that end up saying to remove/discard a line.Â 
          Sometimes the text says to remove, sometimes to discard, and
          sometimes even "discard and not include".Â  Can we pick one and
          be consistent?Â  I'd prefer "discard and not include", or maybe
          just "discard", both of which are more clear to me than
          "remove".Â  <br>
        </div>
      </div>
    </blockquote>
    <br>
    Sure, I've changed them all to "discard."<br>
    <br>
    <blockquote
cite="mid:CAJrXDUG8FJYswsssiJKZHUw+9oWcMGJ3n=qSOckhx=dhR=8nUQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_default"
          style="font-family:arial,helvetica,sans-serif">4.Â  There is a
          phrase which says "If the offerer wishes the answerer to have
          the ability to specify a constraint, but does not wish to set
          a value itself, it MUST ...".Â  Is it normal to write MUST
          sentence in the form "if you want X, you MUST do Y?" Â Isn't it
          more correct to say "if you want X, you MAY do Y"?Â  It's the
          answerer of the empty constraint that MUST interpret it a
          certain way, but there's no reason that the offerer MUST set
          the empty constraint.Â  That's just one thing it may choose to
          do.</div>
      </div>
    </blockquote>
    <br>
    I've just removed the normative term here, since I don't think it
    adds any clarity. The formulation is now: "If you want X, you do Y."<br>
    <br>
    /a<br>
  </body>
</html>

--------------1952766359FD7C3FFA6D067C--


From nobody Tue Oct 25 14:53:20 2016
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 24448129457; Tue, 25 Oct 2016 14:53:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147743239914.29338.4548103431158335131.idtracker@ietfa.amsl.com>
Date: Tue, 25 Oct 2016 14:53:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/s51CrAMrNAakkeYECtkNHxfxucU>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-rid-08.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Oct 2016 21:53:19 -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 of the IETF.

        Title           : RTP Payload Format Restrictions
        Authors         : Peter Thatcher
                          Mo Zanaty
                          Suhas Nandakumar
                          Bo Burman
                          Adam Roach
                          Byron Campen
	Filename        : draft-ietf-mmusic-rid-08.txt
	Pages           : 25
	Date            : 2016-10-25

Abstract:
   In this specification, we define a framework for specifying
   restrictions on RTP streams in the Session Description Protocol.
   This framework defines a new "rid" SDP attribute to unambiguously
   identify the RTP Streams within a RTP Session and restrict the
   streams' payload format parameters in a codec-agnostic way beyond
   what is provided with the regular Payload Types.

   This specification updates RFC4855 to give additional guidance on
   choice of Format Parameter (fmtp) names, and on their relation to the
   restrictions defined by this document.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-rid-08

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


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

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


From nobody Tue Oct 25 18:32:33 2016
Return-Path: <fluffy@iii.ca>
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 D4F601299DA for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 18:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EYBdiHE-_Dqy for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 18:32:25 -0700 (PDT)
Received: from smtp74.iad3a.emailsrvr.com (smtp74.iad3a.emailsrvr.com [173.203.187.74]) (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 1DB561294DA for <mmusic@ietf.org>; Tue, 25 Oct 2016 18:32:25 -0700 (PDT)
Received: from smtp26.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp26.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 637BAC01A2; Tue, 25 Oct 2016 21:32:19 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp26.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id C9D75C017A;  Tue, 25 Oct 2016 21:32:18 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.24.10.185] ([UNAVAILABLE]. [128.107.241.180]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.7); Tue, 25 Oct 2016 21:32:19 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <147742756171.8565.11705230224719531567.idtracker@ietfa.amsl.com>
Date: Tue, 25 Oct 2016 18:32:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A934910-073D-46A9-866C-EFA63956F3F3@iii.ca>
References: <147742756171.8565.11705230224719531567.idtracker@ietfa.amsl.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/KpPTeUAFtsrJUPGZWf-N6Di3Smg>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, The IESG <iesg@ietf.org>, mmusic@ietf.org
Subject: Re: [MMUSIC] Spencer Dawkins' Yes on draft-ietf-mmusic-sdp-mux-attributes-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 01:32:27 -0000

> On Oct 25, 2016, at 1:32 PM, Spencer Dawkins =
<spencerdawkins.ietf@gmail.com> wrote:
>=20
> Spencer Dawkins has entered the following ballot position for
> draft-ietf-mmusic-sdp-mux-attributes-14: Yes
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut =
this
> introductory paragraph, however.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> This document is a work of art. Thank you folks for accepting the
> challenge, because it's important.
>=20
> I have a couple of observations, to go along with my Yes ballot. =
Please
> do the right thing.
>=20
> I know Mirja also pushed on the TBD category, but I find RFC 2119 =
"SHOULD
> NOT" to be problematic.
>=20
>   The attributes in the TBD category have not been analyzed under the
>   proposed multiplexing framework and SHOULD NOT be multiplexed.
>=20
> The point of SHOULD (NOT) is that you don't do this unless you =
understand
> the risks, and in this case, it seems to me that you don't know the
> risks. If you're determined to multiplex the TBD attribute "frommet=3D",=

> won't you have to do your own analysis? Wouldn't that mean you might =
make
> assumptions ("it's IDENTICAL") that conflict with the analysis other
> implementers are doing ("it's TRANSPORT")?
>=20
> I could imagine a couple of approaches that might be helpful here.
>=20
> Saying "MUST NOT be multiplexed" would avoid implementers doing their =
own
> analysis and coming up with conflicting answers. Is it obvious why =
this
> is "SHOULD NOT" instead of "MUST NOT"? In other words, who needs to
> multiplex TBD attributes, and why?
>=20
> Saying "cannot be assumed to be safe when multiplexed" probably =
captures
> what I think you are saying. ''

Yes, I think your summary is about right here. For better or worse the =
logic of SHOULD was that a later spec that correctly classified them =
could put them in the right category. I don't know what would be the =
best (if any) change to make to the spec but I wanted to agree with your =
understanding.=20

>=20
> Would it be clearer if the category was called UNKNOWN?

We were trying to capture that it was not that future specs would not be =
able to figure out what to do with these, but more that this RFC had not =
classified them.=20

>=20
> In this text,
>=20
> 16.  Security Considerations
>=20
>   This document does not add any new security considerations beyond =
the
>   existing considerations in the RTP RFCs ([RFC3550] and [RFC3711])
>   that are referenced by this specification.
>=20
> I don't understand how the first paragraph ^^ and the third paragraph =
of
> the section are compatible, because you're referring to issues =
described
> in this specification. But if you delete the first paragraph, leaving
> only=20
>=20
>   The primary security for RTP including the way it is used here is
>   described in [RFC3550] and [RFC3711].
>=20
>   When multiplexing SDP attributes with the category "CAUTION", the
>   implementations should be aware of possible issues as described in
>   this specification.
>=20
> the security considerations would be consistent.

Works For Me ... i think the text that is there goes back to early =
boiler plate text we took from somewhere...=20

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


From nobody Tue Oct 25 20:15:15 2016
Return-Path: <spencerdawkins.ietf@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 0553912940C; Tue, 25 Oct 2016 20:15:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rVrZYGETp7lS; Tue, 25 Oct 2016 20:15:07 -0700 (PDT)
Received: from mail-yb0-x236.google.com (mail-yb0-x236.google.com [IPv6:2607:f8b0:4002:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF229129405; Tue, 25 Oct 2016 20:15:06 -0700 (PDT)
Received: by mail-yb0-x236.google.com with SMTP id d128so7129770ybh.2; Tue, 25 Oct 2016 20:15:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SwSEy2nFbmM4ItQdmabJNawLxaMpZ+7GbzueE/k2pGI=; b=Bx2a2Y/GSl5Z8/RziUcCJ1TQrGXABVWGK/hMKZw/NvxQR7n8Q2UwvSQ70dQmdgZpdl XVd/dAiOdN86BeAGQgKKz1DTPeReqrGw6GEmpzpCll6NKZZrgaGt4jxSwtMiPC7BOVxb m6Tk2XKN5Y+sbagsh05kACzX5iDo3/SSkQNiGJCb0cWeIwlRWP6PE3coi0rrthYZhdtj xF13z0WhlybTNYH9LXLB5lsxAYxh+Dtk6ekD+mN2x5r4chjpObcJONc4cPRkEbi1x6F0 EelOa/SsK5l7LErg1wfXRT3OCmtOfei9rRiR0oGOvmg85Ww+C8CO/Lo7cAW2mJ1oLpL5 ojXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SwSEy2nFbmM4ItQdmabJNawLxaMpZ+7GbzueE/k2pGI=; b=NAlZCXL37qOhVW/zV2RmQbs1eMzD9qMKys0Ue5CDOaOQsDbR+8Gvjg5LFnYXJT6IBN uos6o29jR+43bTmG9vQgbW1KjQ2gd2enCN1X5CcBANxEqkvmcU//sTk4qQXuNp+n2yqT /v4MWL7zeD2MeKZ/LRLcdf7U6OsmkhjuzK0uR05oPSekK59mdGEUwgSzADpSpNYEviT7 dU5l54iZCUWXuvZ3rvJ7IOLDH6TRC02vQNBLX8gNKaC/pIHQg3g+QJvZR4YNpcdbF/8M nw643QX1GvaCHof7CAHkqA+rTeMdtGGhZV6DVB4zDNhyCF58WTYYBNSutfxTBMToET8b /ZkA==
X-Gm-Message-State: ABUngvfwY7r4xljckhSxbRo6to0VYpqakbwH6ungHFE/y3EnTXLLQNT7qSIKc3SK0v7GHBw9MWd6veoP/JoUeg==
X-Received: by 10.37.76.136 with SMTP id z130mr3652815yba.12.1477451705930; Tue, 25 Oct 2016 20:15:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.36.16 with HTTP; Tue, 25 Oct 2016 20:15:05 -0700 (PDT)
In-Reply-To: <5A934910-073D-46A9-866C-EFA63956F3F3@iii.ca>
References: <147742756171.8565.11705230224719531567.idtracker@ietfa.amsl.com> <5A934910-073D-46A9-866C-EFA63956F3F3@iii.ca>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 25 Oct 2016 22:15:05 -0500
Message-ID: <CAKKJt-cTAAiFa-TTwB70oxo2ia25QGrBwFacJkarnOD=NEtqBQ@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: multipart/alternative; boundary=001a113e54701ad89e053fbc08d6
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/uMwhANTiyloJR1UqyZjX8Xu-3jY>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, The IESG <iesg@ietf.org>, mmusic@ietf.org
Subject: Re: [MMUSIC] Spencer Dawkins' Yes on draft-ietf-mmusic-sdp-mux-attributes-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 03:15:09 -0000

--001a113e54701ad89e053fbc08d6
Content-Type: text/plain; charset=UTF-8

Hi, Cullen,

On Tue, Oct 25, 2016 at 8:32 PM, Cullen Jennings <fluffy@iii.ca> wrote:

>
> > On Oct 25, 2016, at 1:32 PM, Spencer Dawkins <
> spencerdawkins.ietf@gmail.com> wrote:
> >
> > Spencer Dawkins has entered the following ballot position for
> > draft-ietf-mmusic-sdp-mux-attributes-14: Yes
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.
> html
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/
> >
> >
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > This document is a work of art. Thank you folks for accepting the
> > challenge, because it's important.
> >
> > I have a couple of observations, to go along with my Yes ballot. Please
> > do the right thing.
> >
> > I know Mirja also pushed on the TBD category, but I find RFC 2119 "SHOULD
> > NOT" to be problematic.
> >
> >   The attributes in the TBD category have not been analyzed under the
> >   proposed multiplexing framework and SHOULD NOT be multiplexed.
> >
> > The point of SHOULD (NOT) is that you don't do this unless you understand
> > the risks, and in this case, it seems to me that you don't know the
> > risks. If you're determined to multiplex the TBD attribute "frommet=",
> > won't you have to do your own analysis? Wouldn't that mean you might make
> > assumptions ("it's IDENTICAL") that conflict with the analysis other
> > implementers are doing ("it's TRANSPORT")?
> >
> > I could imagine a couple of approaches that might be helpful here.
> >
> > Saying "MUST NOT be multiplexed" would avoid implementers doing their own
> > analysis and coming up with conflicting answers. Is it obvious why this
> > is "SHOULD NOT" instead of "MUST NOT"? In other words, who needs to
> > multiplex TBD attributes, and why?
> >
> > Saying "cannot be assumed to be safe when multiplexed" probably captures
> > what I think you are saying. ''
>
> Yes, I think your summary is about right here. For better or worse the
> logic of SHOULD was that a later spec that correctly classified them could
> put them in the right category. I don't know what would be the best (if
> any) change to make to the spec but I wanted to agree with your
> understanding.


"Do the right thing" :-)


> >
> > Would it be clearer if the category was called UNKNOWN?
>
> We were trying to capture that it was not that future specs would not be
> able to figure out what to do with these, but more that this RFC had not
> classified them.


I'm pretty sure I'm stumbling over something that is less clear now than it
will be when the working group is using this framework (so, this makes
sense to me).


> >
> > In this text,
> >
> > 16.  Security Considerations
> >
> >   This document does not add any new security considerations beyond the
> >   existing considerations in the RTP RFCs ([RFC3550] and [RFC3711])
> >   that are referenced by this specification.
> >
> > I don't understand how the first paragraph ^^ and the third paragraph of
> > the section are compatible, because you're referring to issues described
> > in this specification. But if you delete the first paragraph, leaving
> > only
> >
> >   The primary security for RTP including the way it is used here is
> >   described in [RFC3550] and [RFC3711].
> >
> >   When multiplexing SDP attributes with the category "CAUTION", the
> >   implementations should be aware of possible issues as described in
> >   this specification.
> >
> > the security considerations would be consistent.
>
> Works For Me ... i think the text that is there goes back to early boiler
> plate text we took from somewhere...
>

Cool - and thanks for considering my comments.

Spencer

--001a113e54701ad89e053fbc08d6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Cullen,<div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Tue, Oct 25, 2016 at 8:32 PM, Cullen Jennings <span dir=3D"lt=
r">&lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank">fluffy@iii.ca</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"HOEnZb">=
<div class=3D"h5"><br>
&gt; On Oct 25, 2016, at 1:32 PM, Spencer Dawkins &lt;<a href=3D"mailto:spe=
ncerdawkins.ietf@gmail.com">spencerdawkins.ietf@gmail.com</a><wbr>&gt; wrot=
e:<br>
&gt;<br>
&gt; Spencer Dawkins has entered the following ballot position for<br>
&gt; draft-ietf-mmusic-sdp-mux-<wbr>attributes-14: Yes<br>
&gt;<br>
&gt; When responding, please keep the subject line intact and reply to all<=
br>
&gt; email addresses included in the To and CC lines. (Feel free to cut thi=
s<br>
&gt; introductory paragraph, however.)<br>
&gt;<br>
&gt;<br>
&gt; Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss=
-criteria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/i=
esg/<wbr>statement/discuss-criteria.<wbr>html</a><br>
&gt; for more information about IESG DISCUSS and COMMENT positions.<br>
&gt;<br>
&gt;<br>
&gt; The document, along with other ballot positions, can be found here:<br=
>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-=
attributes/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.=
org/<wbr>doc/draft-ietf-mmusic-sdp-mux-<wbr>attributes/</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
----------<br>
&gt; COMMENT:<br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
----------<br>
&gt;<br>
&gt; This document is a work of art. Thank you folks for accepting the<br>
&gt; challenge, because it&#39;s important.<br>
&gt;<br>
&gt; I have a couple of observations, to go along with my Yes ballot. Pleas=
e<br>
&gt; do the right thing.<br>
&gt;<br>
&gt; I know Mirja also pushed on the TBD category, but I find RFC 2119 &quo=
t;SHOULD<br>
&gt; NOT&quot; to be problematic.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0The attributes in the TBD category have not been analyzed =
under the<br>
&gt;=C2=A0 =C2=A0proposed multiplexing framework and SHOULD NOT be multiple=
xed.<br>
&gt;<br>
&gt; The point of SHOULD (NOT) is that you don&#39;t do this unless you und=
erstand<br>
&gt; the risks, and in this case, it seems to me that you don&#39;t know th=
e<br>
&gt; risks. If you&#39;re determined to multiplex the TBD attribute &quot;f=
rommet=3D&quot;,<br>
&gt; won&#39;t you have to do your own analysis? Wouldn&#39;t that mean you=
 might make<br>
&gt; assumptions (&quot;it&#39;s IDENTICAL&quot;) that conflict with the an=
alysis other<br>
&gt; implementers are doing (&quot;it&#39;s TRANSPORT&quot;)?<br>
&gt;<br>
&gt; I could imagine a couple of approaches that might be helpful here.<br>
&gt;<br>
&gt; Saying &quot;MUST NOT be multiplexed&quot; would avoid implementers do=
ing their own<br>
&gt; analysis and coming up with conflicting answers. Is it obvious why thi=
s<br>
&gt; is &quot;SHOULD NOT&quot; instead of &quot;MUST NOT&quot;? In other wo=
rds, who needs to<br>
&gt; multiplex TBD attributes, and why?<br>
&gt;<br>
&gt; Saying &quot;cannot be assumed to be safe when multiplexed&quot; proba=
bly captures<br>
</div></div>&gt; what I think you are saying. &#39;&#39;<br>
<br>
Yes, I think your summary is about right here. For better or worse the logi=
c of SHOULD was that a later spec that correctly classified them could put =
them in the right category. I don&#39;t know what would be the best (if any=
) change to make to the spec but I wanted to agree with your understanding.=
</blockquote><div><br></div><div>&quot;Do the right thing&quot; :-)</div><d=
iv>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt;<br>
&gt; Would it be clearer if the category was called UNKNOWN?<br>
<br>
</span>We were trying to capture that it was not that future specs would no=
t be able to figure out what to do with these, but more that this RFC had n=
ot classified them.</blockquote><div><br></div><div>I&#39;m pretty sure I&#=
39;m stumbling over something that is less clear now than it will be when t=
he working group is using this framework (so, this makes sense to me).</div=
><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt;<br>
&gt; In this text,<br>
&gt;<br>
&gt; 16.=C2=A0 Security Considerations<br>
&gt;<br>
&gt;=C2=A0 =C2=A0This document does not add any new security considerations=
 beyond the<br>
&gt;=C2=A0 =C2=A0existing considerations in the RTP RFCs ([RFC3550] and [RF=
C3711])<br>
&gt;=C2=A0 =C2=A0that are referenced by this specification.<br>
&gt;<br>
&gt; I don&#39;t understand how the first paragraph ^^ and the third paragr=
aph of<br>
&gt; the section are compatible, because you&#39;re referring to issues des=
cribed<br>
&gt; in this specification. But if you delete the first paragraph, leaving<=
br>
&gt; only<br>
&gt;<br>
&gt;=C2=A0 =C2=A0The primary security for RTP including the way it is used =
here is<br>
&gt;=C2=A0 =C2=A0described in [RFC3550] and [RFC3711].<br>
&gt;<br>
&gt;=C2=A0 =C2=A0When multiplexing SDP attributes with the category &quot;C=
AUTION&quot;, the<br>
&gt;=C2=A0 =C2=A0implementations should be aware of possible issues as desc=
ribed in<br>
&gt;=C2=A0 =C2=A0this specification.<br>
&gt;<br>
&gt; the security considerations would be consistent.<br>
<br>
</span>Works For Me ... i think the text that is there goes back to early b=
oiler plate text we took from somewhere...<br></blockquote><div><br></div><=
div>Cool - and thanks for considering my comments.</div><div><br></div><div=
>Spencer=C2=A0</div></div></div></div>

--001a113e54701ad89e053fbc08d6--


From nobody Tue Oct 25 21:11:18 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD221293F0; Tue, 25 Oct 2016 21:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YqisE3Xg3_ae; Tue, 25 Oct 2016 21:11:15 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (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 1406B12945C; Tue, 25 Oct 2016 21:11:15 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id h14so127267ywa.2; Tue, 25 Oct 2016 21:11:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iw92BNUy5Qx++bY3CRNFkBz1mR2sUAfzELZV5RrraLs=; b=KXj7Y5zxt5Ato3xr57ttSqRRtfh2G0X4tcF3atzrIhoS5Ixmgw0w+kOktW4OncVU0F Yu9kI/rLJvmY/rgz2oODUR9+JYDEazQAG4A886gkIob69+KSyoUz1CJsChQVinHwZJC3 yYvEa1Pt981uV9R6t7XYAyElD4Wlma9Lhc9PkH2xoaR2il1NdnS4LXnWNhmFfGHPMIq+ PtwLqq0apfcB0JPge+CyxBQzOtuY9mQsYofnC1qxbCi9ejK28tg1KjjUBxAite1OCpsx L55yjgUnNbU0Q4XZKeREq5A4nQwXjgi39IaJQbTO8LRZFxyXV0hFCV8sjtzNBkrSo89y ySwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iw92BNUy5Qx++bY3CRNFkBz1mR2sUAfzELZV5RrraLs=; b=m4ZUqHWULvRd6iLOqCkblqb3PW7RUsNdNuwjsGi4zYc0kpIcd1z5PqAkwMxtRXCrga bAImqiB+pe9KasVRs0cbbjSWjly2ghrvQSCQmExJpRQLSJbPpKWf+hnmYCFNWJVqku/F we4BuJa4i+ZZr/QYd45gy6+rRlK15vU20EgKr3aZqAYCr76ZdLIFUOFykKXsf24pwBbC oj+Lu2TOiLG9kzGWMYENDZQLK3y3ZaVvTXABhn26tmAh7yKxTRiRSbQ563RtdkIQ2XnC ObR/8MWZaIJWVe7rQMj2XHIeV6USr/WAbIVXIlfkok5zxNHoD5dy/MQKXC8dyAcQ6PjP cRpA==
X-Gm-Message-State: ABUngvcvjYhLseyBUU95KWEhBBOei7iCKjz/4xpnDbFGZq4PDwE4jRZnXBH2OohNHohn82pA/yXQESyJo5as/g==
X-Received: by 10.13.218.65 with SMTP id c62mr89256ywe.270.1477455074289; Tue, 25 Oct 2016 21:11:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.158.73 with HTTP; Tue, 25 Oct 2016 21:11:13 -0700 (PDT)
In-Reply-To: <CAKKJt-cTAAiFa-TTwB70oxo2ia25QGrBwFacJkarnOD=NEtqBQ@mail.gmail.com>
References: <147742756171.8565.11705230224719531567.idtracker@ietfa.amsl.com> <5A934910-073D-46A9-866C-EFA63956F3F3@iii.ca> <CAKKJt-cTAAiFa-TTwB70oxo2ia25QGrBwFacJkarnOD=NEtqBQ@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Tue, 25 Oct 2016 21:11:13 -0700
Message-ID: <CAMRcRGTaexMuirQS=O=YWOUb379iyrPxKvWdvdzSTseX=WOGsQ@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c080508e0179e053fbcd078
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/cwenYGWi_vTSXFJQWlOwb8OIkqU>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, The IESG <iesg@ietf.org>, Cullen Jennings <fluffy@iii.ca>, mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Spencer Dawkins' Yes on draft-ietf-mmusic-sdp-mux-attributes-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 04:11:17 -0000

--94eb2c080508e0179e053fbcd078
Content-Type: text/plain; charset=UTF-8

Thanks Spencer for the review and Thanks Cullen for the inputs.

Given the discussion above, I can update the security considerations
section as suggested by Spencer and generate a new version whenever it is
appropriate and just to double check on the outcome - the category TBD stay
as it is.

Spencer, please advise if i misunderstood anything

Ben, please let me know procedures on generating the next version.

Cheers
Suhas

On Tue, Oct 25, 2016 at 8:15 PM, Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Hi, Cullen,
>
> On Tue, Oct 25, 2016 at 8:32 PM, Cullen Jennings <fluffy@iii.ca> wrote:
>
>>
>> > On Oct 25, 2016, at 1:32 PM, Spencer Dawkins <
>> spencerdawkins.ietf@gmail.com> wrote:
>> >
>> > Spencer Dawkins has entered the following ballot position for
>> > draft-ietf-mmusic-sdp-mux-attributes-14: Yes
>> >
>> > When responding, please keep the subject line intact and reply to all
>> > email addresses included in the To and CC lines. (Feel free to cut this
>> > introductory paragraph, however.)
>> >
>> >
>> > Please refer to https://www.ietf.org/iesg/stat
>> ement/discuss-criteria.html
>> > for more information about IESG DISCUSS and COMMENT positions.
>> >
>> >
>> > The document, along with other ballot positions, can be found here:
>> > https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/
>> >
>> >
>> >
>> > ----------------------------------------------------------------------
>> > COMMENT:
>> > ----------------------------------------------------------------------
>> >
>> > This document is a work of art. Thank you folks for accepting the
>> > challenge, because it's important.
>> >
>> > I have a couple of observations, to go along with my Yes ballot. Please
>> > do the right thing.
>> >
>> > I know Mirja also pushed on the TBD category, but I find RFC 2119
>> "SHOULD
>> > NOT" to be problematic.
>> >
>> >   The attributes in the TBD category have not been analyzed under the
>> >   proposed multiplexing framework and SHOULD NOT be multiplexed.
>> >
>> > The point of SHOULD (NOT) is that you don't do this unless you
>> understand
>> > the risks, and in this case, it seems to me that you don't know the
>> > risks. If you're determined to multiplex the TBD attribute "frommet=",
>> > won't you have to do your own analysis? Wouldn't that mean you might
>> make
>> > assumptions ("it's IDENTICAL") that conflict with the analysis other
>> > implementers are doing ("it's TRANSPORT")?
>> >
>> > I could imagine a couple of approaches that might be helpful here.
>> >
>> > Saying "MUST NOT be multiplexed" would avoid implementers doing their
>> own
>> > analysis and coming up with conflicting answers. Is it obvious why this
>> > is "SHOULD NOT" instead of "MUST NOT"? In other words, who needs to
>> > multiplex TBD attributes, and why?
>> >
>> > Saying "cannot be assumed to be safe when multiplexed" probably captures
>> > what I think you are saying. ''
>>
>> Yes, I think your summary is about right here. For better or worse the
>> logic of SHOULD was that a later spec that correctly classified them could
>> put them in the right category. I don't know what would be the best (if
>> any) change to make to the spec but I wanted to agree with your
>> understanding.
>
>
> "Do the right thing" :-)
>
>
>> >
>> > Would it be clearer if the category was called UNKNOWN?
>>
>> We were trying to capture that it was not that future specs would not be
>> able to figure out what to do with these, but more that this RFC had not
>> classified them.
>
>
> I'm pretty sure I'm stumbling over something that is less clear now than
> it will be when the working group is using this framework (so, this makes
> sense to me).
>
>
>> >
>> > In this text,
>> >
>> > 16.  Security Considerations
>> >
>> >   This document does not add any new security considerations beyond the
>> >   existing considerations in the RTP RFCs ([RFC3550] and [RFC3711])
>> >   that are referenced by this specification.
>> >
>> > I don't understand how the first paragraph ^^ and the third paragraph of
>> > the section are compatible, because you're referring to issues described
>> > in this specification. But if you delete the first paragraph, leaving
>> > only
>> >
>> >   The primary security for RTP including the way it is used here is
>> >   described in [RFC3550] and [RFC3711].
>> >
>> >   When multiplexing SDP attributes with the category "CAUTION", the
>> >   implementations should be aware of possible issues as described in
>> >   this specification.
>> >
>> > the security considerations would be consistent.
>>
>> Works For Me ... i think the text that is there goes back to early boiler
>> plate text we took from somewhere...
>>
>
> Cool - and thanks for considering my comments.
>
> Spencer
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

--94eb2c080508e0179e053fbcd078
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Spencer for the review and Thanks Cullen for the in=
puts.=C2=A0<div><br></div><div>Given the discussion above, I can update the=
 security considerations section as suggested by Spencer and generate a new=
 version whenever it is appropriate and just to double check on the outcome=
 - the category TBD stay as it is.<div><br></div><div>Spencer, please advis=
e if i misunderstood anything</div><div><br></div><div>Ben, please let me k=
now procedures on generating the next version.</div></div><div><br></div><d=
iv>Cheers</div><div>Suhas</div></div><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On Tue, Oct 25, 2016 at 8:15 PM, Spencer Dawkins at IET=
F <span dir=3D"ltr">&lt;<a href=3D"mailto:spencerdawkins.ietf@gmail.com" ta=
rget=3D"_blank">spencerdawkins.ietf@gmail.com</a>&gt;</span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div dir=3D"ltr">Hi, Cullen,<div class=3D"gmail_=
extra"><br><div class=3D"gmail_quote"><div><div class=3D"h5">On Tue, Oct 25=
, 2016 at 8:32 PM, Cullen Jennings <span dir=3D"ltr">&lt;<a href=3D"mailto:=
fluffy@iii.ca" target=3D"_blank">fluffy@iii.ca</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><div class=3D"m_7710767749988814003HOEnZb"><div=
 class=3D"m_7710767749988814003h5"><br>
&gt; On Oct 25, 2016, at 1:32 PM, Spencer Dawkins &lt;<a href=3D"mailto:spe=
ncerdawkins.ietf@gmail.com" target=3D"_blank">spencerdawkins.ietf@gmail.com=
</a><wbr>&gt; wrote:<br>
&gt;<br>
&gt; Spencer Dawkins has entered the following ballot position for<br>
&gt; draft-ietf-mmusic-sdp-mux-attr<wbr>ibutes-14: Yes<br>
&gt;<br>
&gt; When responding, please keep the subject line intact and reply to all<=
br>
&gt; email addresses included in the To and CC lines. (Feel free to cut thi=
s<br>
&gt; introductory paragraph, however.)<br>
&gt;<br>
&gt;<br>
&gt; Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss=
-criteria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/i=
esg/stat<wbr>ement/discuss-criteria.html</a><br>
&gt; for more information about IESG DISCUSS and COMMENT positions.<br>
&gt;<br>
&gt;<br>
&gt; The document, along with other ballot positions, can be found here:<br=
>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-=
attributes/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.=
org/d<wbr>oc/draft-ietf-mmusic-sdp-mux-a<wbr>ttributes/</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
----------<br>
&gt; COMMENT:<br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
----------<br>
&gt;<br>
&gt; This document is a work of art. Thank you folks for accepting the<br>
&gt; challenge, because it&#39;s important.<br>
&gt;<br>
&gt; I have a couple of observations, to go along with my Yes ballot. Pleas=
e<br>
&gt; do the right thing.<br>
&gt;<br>
&gt; I know Mirja also pushed on the TBD category, but I find RFC 2119 &quo=
t;SHOULD<br>
&gt; NOT&quot; to be problematic.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0The attributes in the TBD category have not been analyzed =
under the<br>
&gt;=C2=A0 =C2=A0proposed multiplexing framework and SHOULD NOT be multiple=
xed.<br>
&gt;<br>
&gt; The point of SHOULD (NOT) is that you don&#39;t do this unless you und=
erstand<br>
&gt; the risks, and in this case, it seems to me that you don&#39;t know th=
e<br>
&gt; risks. If you&#39;re determined to multiplex the TBD attribute &quot;f=
rommet=3D&quot;,<br>
&gt; won&#39;t you have to do your own analysis? Wouldn&#39;t that mean you=
 might make<br>
&gt; assumptions (&quot;it&#39;s IDENTICAL&quot;) that conflict with the an=
alysis other<br>
&gt; implementers are doing (&quot;it&#39;s TRANSPORT&quot;)?<br>
&gt;<br>
&gt; I could imagine a couple of approaches that might be helpful here.<br>
&gt;<br>
&gt; Saying &quot;MUST NOT be multiplexed&quot; would avoid implementers do=
ing their own<br>
&gt; analysis and coming up with conflicting answers. Is it obvious why thi=
s<br>
&gt; is &quot;SHOULD NOT&quot; instead of &quot;MUST NOT&quot;? In other wo=
rds, who needs to<br>
&gt; multiplex TBD attributes, and why?<br>
&gt;<br>
&gt; Saying &quot;cannot be assumed to be safe when multiplexed&quot; proba=
bly captures<br>
</div></div>&gt; what I think you are saying. &#39;&#39;<br>
<br>
Yes, I think your summary is about right here. For better or worse the logi=
c of SHOULD was that a later spec that correctly classified them could put =
them in the right category. I don&#39;t know what would be the best (if any=
) change to make to the spec but I wanted to agree with your understanding.=
</blockquote><div><br></div></div></div><div>&quot;Do the right thing&quot;=
 :-)</div><span class=3D""><div>=C2=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<span>&gt;<br>
&gt; Would it be clearer if the category was called UNKNOWN?<br>
<br>
</span>We were trying to capture that it was not that future specs would no=
t be able to figure out what to do with these, but more that this RFC had n=
ot classified them.</blockquote><div><br></div></span><div>I&#39;m pretty s=
ure I&#39;m stumbling over something that is less clear now than it will be=
 when the working group is using this framework (so, this makes sense to me=
).</div><span class=3D""><div>=C2=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><s=
pan>&gt;<br>
&gt; In this text,<br>
&gt;<br>
&gt; 16.=C2=A0 Security Considerations<br>
&gt;<br>
&gt;=C2=A0 =C2=A0This document does not add any new security considerations=
 beyond the<br>
&gt;=C2=A0 =C2=A0existing considerations in the RTP RFCs ([RFC3550] and [RF=
C3711])<br>
&gt;=C2=A0 =C2=A0that are referenced by this specification.<br>
&gt;<br>
&gt; I don&#39;t understand how the first paragraph ^^ and the third paragr=
aph of<br>
&gt; the section are compatible, because you&#39;re referring to issues des=
cribed<br>
&gt; in this specification. But if you delete the first paragraph, leaving<=
br>
&gt; only<br>
&gt;<br>
&gt;=C2=A0 =C2=A0The primary security for RTP including the way it is used =
here is<br>
&gt;=C2=A0 =C2=A0described in [RFC3550] and [RFC3711].<br>
&gt;<br>
&gt;=C2=A0 =C2=A0When multiplexing SDP attributes with the category &quot;C=
AUTION&quot;, the<br>
&gt;=C2=A0 =C2=A0implementations should be aware of possible issues as desc=
ribed in<br>
&gt;=C2=A0 =C2=A0this specification.<br>
&gt;<br>
&gt; the security considerations would be consistent.<br>
<br>
</span>Works For Me ... i think the text that is there goes back to early b=
oiler plate text we took from somewhere...<br></blockquote><div><br></div><=
/span><div>Cool - and thanks for considering my comments.</div><span class=
=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div>Spencer=C2=A0</div>=
</font></span></div></div></div>
<br>______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
<br></blockquote></div><br></div>

--94eb2c080508e0179e053fbcd078--


From nobody Tue Oct 25 21:54:47 2016
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 E071A12950A; Tue, 25 Oct 2016 21:54:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.952
X-Spam-Level: 
X-Spam-Status: No, score=-14.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 tWcMCHvcf_6Y; Tue, 25 Oct 2016 21:54:44 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8B8D12945C; Tue, 25 Oct 2016 21:54:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7339; q=dns/txt; s=iport; t=1477457683; x=1478667283; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=7UjlAwcgzpeLBEOU+A25W4Wv9gR/yZfDRvu6ybBrv84=; b=bJVnTJvgYpjrTMtBBi/nmlWY+GWCRZwfIp6jxjoBnIheuTXsuupRzWkk CmRzrUoiKbNO6t9sH3SxsTaq6Ufe+HCyfLbh4GHuBKVkSNPEdlpN5HpDx Tn8RAP7UKy5NjVX34yTiqFULq20tki4+FXBGKMkxPcwL+RgZTF5Ycjo/N s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AsAQB/NhBY/4UNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgyoBAQEBAR1YKlONNZZ+lD+CBxwLhTFKAoF0PxQBAgEBAQEBAQF?= =?us-ascii?q?iKIRjAQEEAQEBIA8BBTAGCxAjAgIfBwICJzAGAQwGAgEBF4g5DrMgjHUBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEcgQeFNoF9CIFLhR4RAYMgglsFhiaTcIE7hG+GDIN?= =?us-ascii?q?igW5OhB+DF4YRhxmFb4QBHjZeg0yBViI0hj2CKQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.31,549,1473120000"; d="scan'208";a="166812827"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 26 Oct 2016 04:54:42 +0000
Received: from [10.24.21.139] ([10.24.21.139]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u9Q4sfFp021141; Wed, 26 Oct 2016 04:54:41 GMT
To: Ben Campbell <ben@nostrum.com>, Bo Burman <bo.burman@ericsson.com>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com>
Date: Wed, 26 Oct 2016 00:54:41 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/rNLCwplWcigTPAz1WN3qAIDuPoU>
Cc: ART ADs <art-ads@ietf.org>, mmusic <mmusic@ietf.org>
Subject: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 04:54:46 -0000

A Doodle poll is now available at

	http://doodle.com/poll/kxw4n9a2v7v3pe2y

We are looking at either Wednesday or Friday next week (November 2 or 
4), so please get your vote in pretty quickly if you are interested.

Thanks

-- Flemming


On 10/25/16 12:01 AM, Flemming Andreasen wrote:
> Hi Ben
>
> We will get a poll setup as soon as we understand any major 
> constraints from the key participants.
>
> Thanks
>
> -- Flemming
>
>
> On 10/21/16 4:49 PM, Ben Campbell wrote:
>> Hi Everyone, please accept my apologies for waiting this long to 
>> weigh in.
>>
>> I think it's clear that multiple people are not happy with how we got 
>> to this point. But assigning blame doesn't help us make progress on 
>> the draft. I propose that we get over that, and instead focus instead 
>> on how to move forward. Email discussion doesn't seem to be helping. 
>> Maybe a call will.
>>
>> Flemming and/or Bo: Can you set up a Doodle poll to get Christer, 
>> Cullen, and other demonstratively  interested parties on a conference 
>> call? I will join if at all possible, but don't let scheduling around 
>> me stop a call from happening.
>>
>> Thanks!
>>
>> Ben.
>>
>> On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:
>>
>>> [fixing cc-list]
>>>
>>> On 10/21/16 11:59 AM, Flemming Andreasen wrote:
>>>>
>>>>
>>>> On 10/21/16 11:21 AM, Cullen Jennings wrote:
>>>>> I think that is a bad way to run a WG. All I asked for was a phone 
>>>>> call to discuss this so we could get the issues on the table and 
>>>>> discuss what is best. The chairs never even replied to my request 
>>>>> for a WG call to discuss this.
>>>> That is simply not true. You (and Christer) were explicitly asked 
>>>> to setup a phone call on 10/6/16 to discuss this issue; a request 
>>>> that (like many other others) went unanswered or required extensive 
>>>> prodding to get any attention.
>>>>
>>>>> The list discussions that ensued from this resulted in people 
>>>>> other than me sugesting possibilities that were much better than 
>>>>> any of the three below -  none of which were considered in your 
>>>>> consensus call.
>>>> I'm not sure what those proposals are, nor were they brought up in 
>>>> response to the consensus call.
>>>>
>>>>> I donâ€™t plan to appeal this but I am considering if itâ€™s worth my 
>>>>> time to participate in this WG if we are not going to be willing 
>>>>> to actually spend a short time to discuss possible solutions 
>>>>> before taking a consensus call.  As input to that decisions, it 
>>>>> would be really useful to know why you refused to have a phone 
>>>>> call on this topic and what your policy in general is going to be 
>>>>> toward discussions of proposed solutions to problems in the future.
>>>> My position is that we will try our very best to get to not only 
>>>> consensus but to satisfy as many concerns as we possibly can. It 
>>>> does however require people to engage in a timely manner, and even 
>>>> when they don't, we still do what we can, but at some point we need 
>>>> to move forward. As for the issue at hand, it has been discussed 
>>>> extensively, and several changes were made to the draft to try and 
>>>> accommodate your requests.
>>>>
>>>> The one major remaining issue I believe you have is around whether 
>>>> this document updates RFC 4572. This has been discussed extensively 
>>>> on the wgchairs list; a discussion I initiated to try and help 
>>>> address your concern. You may disagree with how that discussion 
>>>> concluded, but again, to try and alleviate your concerns, a note 
>>>> was added to 4572-update to make it clear that the document does 
>>>> not make existing 4572 implementations non-compliant with RFC 4572.
>>>>
>>>> I believe the chairs, authors, and the WG at large has done 
>>>> everything that can reasonably be done to try and address your 
>>>> concerns, and at this point we need to move forward.
>>>>
>>>> Thanks
>>>>
>>>> -- Flemming (as MMUSIC co-chair)
>>>>
>>>>
>>>>
>>>>>
>>>>>> On Oct 19, 2016, at 6:43 AM, Flemming Andreasen 
>>>>>> <fandreas@cisco.com> wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> Following up on the consensus call, we have received 5 responses 
>>>>>> in favor of option a) below, one neutral, and one objection. 
>>>>>> Looking at the document we have noted that backwards 
>>>>>> compatibility is handled by the current text in the document and 
>>>>>> it also clearly states that it does not make current RFC 4572 
>>>>>> implementation non-compliant with RFC 4572. Since we have not 
>>>>>> heard of any technical problems with proposal a), nor seen any 
>>>>>> tangible progress on how to address the objection, we are hereby 
>>>>>> declaring rough consensus on option a). We will proceed with the 
>>>>>> publication request for the current draft while duly noting the 
>>>>>> "roughness" of the consensus based on the pending objection as 
>>>>>> part of this.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>     Flemming & Bo (MMUSIC chairs)
>>>>>>
>>>>>>
>>>>>> On 10/12/16 6:23 PM, Flemming Andreasen wrote:
>>>>>>> Greetings
>>>>>>>
>>>>>>> There has been quite a bit of discussion on 
>>>>>>> draft-ietf-mmusic-4572-update (currently -07), which had 
>>>>>>> previously completed WGLC when a few concerns were raised. The 
>>>>>>> document currently:
>>>>>>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
>>>>>>> 2. Updates the preferred cipher-suite with a stronger cipher suite
>>>>>>> 3. Updates RFC 4572.
>>>>>>>
>>>>>>> Item 1 seems to be generally agreeable, whereas items 2 and 3 
>>>>>>> are not. The chairs are hereby soliciting WG feedback on how to 
>>>>>>> proceed based on the following choices:
>>>>>>>
>>>>>>> a) Proceed with publication of 4572-update-07 in its current 
>>>>>>> form (i.e. covering all 3 items above)
>>>>>>>
>>>>>>> b) Remove item 2 from 4572-update, i.e. do not update the 
>>>>>>> preferred cipher-suite
>>>>>>>
>>>>>>> c) Remove item 3 from 4572-update, i.e. do not indicate that 
>>>>>>> this document constitutes an update to RFC 4572.
>>>>>>>
>>>>>>>
>>>>>>> Note that choice a) is mutually exclusive with b) and c), but b) 
>>>>>>> and c) are not mutually exclusive.
>>>>>>>
>>>>>>> Please let us know your preference wrt to the above no later 
>>>>>>> than Friday October 14th.
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>>        Flemming & Bo (MMUSIC chairs)
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>> .
>>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>
>> .
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Tue Oct 25 22:07:09 2016
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 81475129418 for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 22:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5] 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 C1CVXlCMQp1P for <mmusic@ietfa.amsl.com>; Tue, 25 Oct 2016 22:07:04 -0700 (PDT)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (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 CBCB91293EC for <mmusic@ietf.org>; Tue, 25 Oct 2016 22:07:03 -0700 (PDT)
Received: by mail-qk0-x230.google.com with SMTP id z190so273620885qkc.2 for <mmusic@ietf.org>; Tue, 25 Oct 2016 22:07:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8MLg7F9YN7T32HD9w/WqlO/8ku0W5mOUkWYy77XfUgY=; b=MbXTsJ3wwr8E3jWn/Su/p4ffsu2lRjdBNF/7f1CQ190yaIcjmwSMQPXE5nXO2SqyZV yiFCKtp7EDONrKalo/nVzr+8+0bkQ7b7TUY8bV5cLTkKWAYByRvSUTS9ri4a5tEqjnwW dV66BWXXlhKLtl70qEnf0e2/EyidmxyjKrp+JrkbYobZYOfD550Wa5TkajGc+7EEYkm7 Kntij4ZgfBs6Ua/u4HdRWic7YBBmbpxr7Ks9/fDUO4W9/AhMS29Rk6ku35+fcdzrKmcX P2MVgCMs9LO7+dK4qWz2vJPNKsTQ7X8tQre4cgHqALBlSNpMznH+Prp0AnFioK68cBUH r6uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8MLg7F9YN7T32HD9w/WqlO/8ku0W5mOUkWYy77XfUgY=; b=kedfE66lzVKuzCUTo7XMxyOYx1qOmR24ig0JIVP2uDP9M/y2E4YAXKRcU7/d/wMckB QQQk008II9rzeEUnCSC7/MULgdWtFETFVVNbpDCJRS21j7hEtGYUFB8PmPZP5brFB7RC 4UYPYMdqZlivwMZS/Bly2DjnlkWmM836yeBvHr5hzXoo206tQBggz4sYnXAUPbKl3plp iqXPAA/BjjVs1CCaOS5dRnmFIzy7r2eprCTzVTZjGVwwe7HJ7AuxHook6y6cUTOQWV59 T1AyVyY12THFejOpZrrKtbSF/wtRzDwXKGxOHbP3pWvz32PHpYxMtSrAM56ne7nUhDr8 HYKg==
X-Gm-Message-State: ABUngvf4C4SAV8+1e10kS/MShnJWQPMUHVIG9bgd9V/6QodaUJYJPPCCpeEJhfD3P6QnDg==
X-Received: by 10.55.148.3 with SMTP id w3mr21555695qkd.248.1477458422916; Tue, 25 Oct 2016 22:07:02 -0700 (PDT)
Received: from mail-qt0-f169.google.com (mail-qt0-f169.google.com. [209.85.216.169]) by smtp.gmail.com with ESMTPSA id j2sm121783qtb.46.2016.10.25.22.07.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Oct 2016 22:07:02 -0700 (PDT)
Received: by mail-qt0-f169.google.com with SMTP id g32so392036qta.2; Tue, 25 Oct 2016 22:07:02 -0700 (PDT)
X-Received: by 10.200.37.11 with SMTP id 11mr22751921qtm.12.1477458421998; Tue, 25 Oct 2016 22:07:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.132.161 with HTTP; Tue, 25 Oct 2016 22:07:01 -0700 (PDT)
In-Reply-To: <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com>
From: Roman Shpount <roman@telurix.com>
Date: Wed, 26 Oct 2016 01:07:01 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuaGC_+7furtohxcQrgrVCeqDf0SUDSgaSqhY7hs-insA@mail.gmail.com>
Message-ID: <CAD5OKxuaGC_+7furtohxcQrgrVCeqDf0SUDSgaSqhY7hs-insA@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Content-Type: multipart/alternative; boundary=001a114229c669eff1053fbd98d2
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/WD3O-_z5c3Qgebut2Wkz9XyeqVo>
Cc: Ben Campbell <ben@nostrum.com>, mmusic <mmusic@ietf.org>, ART ADs <art-ads@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 05:07:07 -0000

--001a114229c669eff1053fbd98d2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

What time zone is this?

Regards,

_____________
Roman Shpount

On Wed, Oct 26, 2016 at 12:54 AM, Flemming Andreasen <fandreas@cisco.com>
wrote:

> A Doodle poll is now available at
>
>         http://doodle.com/poll/kxw4n9a2v7v3pe2y
>
> We are looking at either Wednesday or Friday next week (November 2 or 4),
> so please get your vote in pretty quickly if you are interested.
>
> Thanks
>
> -- Flemming
>
>
> On 10/25/16 12:01 AM, Flemming Andreasen wrote:
>
>> Hi Ben
>>
>> We will get a poll setup as soon as we understand any major constraints
>> from the key participants.
>>
>> Thanks
>>
>> -- Flemming
>>
>>
>> On 10/21/16 4:49 PM, Ben Campbell wrote:
>>
>>> Hi Everyone, please accept my apologies for waiting this long to weigh
>>> in.
>>>
>>> I think it's clear that multiple people are not happy with how we got t=
o
>>> this point. But assigning blame doesn't help us make progress on the dr=
aft.
>>> I propose that we get over that, and instead focus instead on how to mo=
ve
>>> forward. Email discussion doesn't seem to be helping. Maybe a call will=
.
>>>
>>> Flemming and/or Bo: Can you set up a Doodle poll to get Christer,
>>> Cullen, and other demonstratively  interested parties on a conference c=
all?
>>> I will join if at all possible, but don't let scheduling around me stop=
 a
>>> call from happening.
>>>
>>> Thanks!
>>>
>>> Ben.
>>>
>>> On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:
>>>
>>> [fixing cc-list]
>>>>
>>>> On 10/21/16 11:59 AM, Flemming Andreasen wrote:
>>>>
>>>>>
>>>>>
>>>>> On 10/21/16 11:21 AM, Cullen Jennings wrote:
>>>>>
>>>>>> I think that is a bad way to run a WG. All I asked for was a phone
>>>>>> call to discuss this so we could get the issues on the table and dis=
cuss
>>>>>> what is best. The chairs never even replied to my request for a WG c=
all to
>>>>>> discuss this.
>>>>>>
>>>>> That is simply not true. You (and Christer) were explicitly asked to
>>>>> setup a phone call on 10/6/16 to discuss this issue; a request that (=
like
>>>>> many other others) went unanswered or required extensive prodding to =
get
>>>>> any attention.
>>>>>
>>>>> The list discussions that ensued from this resulted in people other
>>>>>> than me sugesting possibilities that were much better than any of th=
e three
>>>>>> below -  none of which were considered in your consensus call.
>>>>>>
>>>>> I'm not sure what those proposals are, nor were they brought up in
>>>>> response to the consensus call.
>>>>>
>>>>> I don=E2=80=99t plan to appeal this but I am considering if it=E2=80=
=99s worth my time
>>>>>> to participate in this WG if we are not going to be willing to actua=
lly
>>>>>> spend a short time to discuss possible solutions before taking a con=
sensus
>>>>>> call.  As input to that decisions, it would be really useful to know=
 why
>>>>>> you refused to have a phone call on this topic and what your policy =
in
>>>>>> general is going to be toward discussions of proposed solutions to p=
roblems
>>>>>> in the future.
>>>>>>
>>>>> My position is that we will try our very best to get to not only
>>>>> consensus but to satisfy as many concerns as we possibly can. It does
>>>>> however require people to engage in a timely manner, and even when th=
ey
>>>>> don't, we still do what we can, but at some point we need to move for=
ward.
>>>>> As for the issue at hand, it has been discussed extensively, and seve=
ral
>>>>> changes were made to the draft to try and accommodate your requests.
>>>>>
>>>>> The one major remaining issue I believe you have is around whether
>>>>> this document updates RFC 4572. This has been discussed extensively o=
n the
>>>>> wgchairs list; a discussion I initiated to try and help address your
>>>>> concern. You may disagree with how that discussion concluded, but aga=
in, to
>>>>> try and alleviate your concerns, a note was added to 4572-update to m=
ake it
>>>>> clear that the document does not make existing 4572 implementations
>>>>> non-compliant with RFC 4572.
>>>>>
>>>>> I believe the chairs, authors, and the WG at large has done everythin=
g
>>>>> that can reasonably be done to try and address your concerns, and at =
this
>>>>> point we need to move forward.
>>>>>
>>>>> Thanks
>>>>>
>>>>> -- Flemming (as MMUSIC co-chair)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> On Oct 19, 2016, at 6:43 AM, Flemming Andreasen <fandreas@cisco.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> Following up on the consensus call, we have received 5 responses in
>>>>>>> favor of option a) below, one neutral, and one objection. Looking a=
t the
>>>>>>> document we have noted that backwards compatibility is handled by t=
he
>>>>>>> current text in the document and it also clearly states that it doe=
s not
>>>>>>> make current RFC 4572 implementation non-compliant with RFC 4572. S=
ince we
>>>>>>> have not heard of any technical problems with proposal a), nor seen=
 any
>>>>>>> tangible progress on how to address the objection, we are hereby de=
claring
>>>>>>> rough consensus on option a). We will proceed with the publication =
request
>>>>>>> for the current draft while duly noting the "roughness" of the cons=
ensus
>>>>>>> based on the pending objection as part of this.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>>     Flemming & Bo (MMUSIC chairs)
>>>>>>>
>>>>>>>
>>>>>>> On 10/12/16 6:23 PM, Flemming Andreasen wrote:
>>>>>>>
>>>>>>>> Greetings
>>>>>>>>
>>>>>>>> There has been quite a bit of discussion on
>>>>>>>> draft-ietf-mmusic-4572-update (currently -07), which had previousl=
y
>>>>>>>> completed WGLC when a few concerns were raised. The document curre=
ntly:
>>>>>>>> 1. Clarifies the usage of multiple SDP 'fingerprint' attributes
>>>>>>>> 2. Updates the preferred cipher-suite with a stronger cipher suite
>>>>>>>> 3. Updates RFC 4572.
>>>>>>>>
>>>>>>>> Item 1 seems to be generally agreeable, whereas items 2 and 3 are
>>>>>>>> not. The chairs are hereby soliciting WG feedback on how to procee=
d based
>>>>>>>> on the following choices:
>>>>>>>>
>>>>>>>> a) Proceed with publication of 4572-update-07 in its current form
>>>>>>>> (i.e. covering all 3 items above)
>>>>>>>>
>>>>>>>> b) Remove item 2 from 4572-update, i.e. do not update the preferre=
d
>>>>>>>> cipher-suite
>>>>>>>>
>>>>>>>> c) Remove item 3 from 4572-update, i.e. do not indicate that this
>>>>>>>> document constitutes an update to RFC 4572.
>>>>>>>>
>>>>>>>>
>>>>>>>> Note that choice a) is mutually exclusive with b) and c), but b)
>>>>>>>> and c) are not mutually exclusive.
>>>>>>>>
>>>>>>>> Please let us know your preference wrt to the above no later than
>>>>>>>> Friday October 14th.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>>        Flemming & Bo (MMUSIC chairs)
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>>
>>>>>> .
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>
>>> .
>>>
>>>
>> _______________________________________________
>> 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
>

--001a114229c669eff1053fbd98d2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">What time zone is this?<div><br></div><div>Regards,</div><=
/div><div class=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gmail_=
signature" data-smartmail=3D"gmail_signature">_____________<br>Roman Shpoun=
t</div></div>
<br><div class=3D"gmail_quote">On Wed, Oct 26, 2016 at 12:54 AM, Flemming A=
ndreasen <span dir=3D"ltr">&lt;<a href=3D"mailto:fandreas@cisco.com" target=
=3D"_blank">fandreas@cisco.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">A Doodle poll is now available at<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://doodle.com/poll/kxw4n9a2v7v3p=
e2y" rel=3D"noreferrer" target=3D"_blank">http://doodle.com/poll/kxw4n9a<wb=
r>2v7v3pe2y</a><br>
<br>
We are looking at either Wednesday or Friday next week (November 2 or 4), s=
o please get your vote in pretty quickly if you are interested.<br>
<br>
Thanks<br>
<br>
-- Flemming<br>
<br>
<br>
On 10/25/16 12:01 AM, Flemming Andreasen wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi Ben<br>
<br>
We will get a poll setup as soon as we understand any major constraints fro=
m the key participants.<br>
<br>
Thanks<br>
<br>
-- Flemming<br>
<br>
<br>
On 10/21/16 4:49 PM, Ben Campbell wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi Everyone, please accept my apologies for waiting this long to weigh in.<=
br>
<br>
I think it&#39;s clear that multiple people are not happy with how we got t=
o this point. But assigning blame doesn&#39;t help us make progress on the =
draft. I propose that we get over that, and instead focus instead on how to=
 move forward. Email discussion doesn&#39;t seem to be helping. Maybe a cal=
l will.<br>
<br>
Flemming and/or Bo: Can you set up a Doodle poll to get Christer, Cullen, a=
nd other demonstratively=C2=A0 interested parties on a conference call? I w=
ill join if at all possible, but don&#39;t let scheduling around me stop a =
call from happening.<br>
<br>
Thanks!<br>
<br>
Ben.<br>
<br>
On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
[fixing cc-list]<br>
<br>
On 10/21/16 11:59 AM, Flemming Andreasen wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
On 10/21/16 11:21 AM, Cullen Jennings wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I think that is a bad way to run a WG. All I asked for was a phone call to =
discuss this so we could get the issues on the table and discuss what is be=
st. The chairs never even replied to my request for a WG call to discuss th=
is.<br>
</blockquote>
That is simply not true. You (and Christer) were explicitly asked to setup =
a phone call on 10/6/16 to discuss this issue; a request that (like many ot=
her others) went unanswered or required extensive prodding to get any atten=
tion.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The list discussions that ensued from this resulted in people other than me=
 sugesting possibilities that were much better than any of the three below =
-=C2=A0 none of which were considered in your consensus call.<br>
</blockquote>
I&#39;m not sure what those proposals are, nor were they brought up in resp=
onse to the consensus call.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I don=E2=80=99t plan to appeal this but I am considering if it=E2=80=99s wo=
rth my time to participate in this WG if we are not going to be willing to =
actually spend a short time to discuss possible solutions before taking a c=
onsensus call.=C2=A0 As input to that decisions, it would be really useful =
to know why you refused to have a phone call on this topic and what your po=
licy in general is going to be toward discussions of proposed solutions to =
problems in the future.<br>
</blockquote>
My position is that we will try our very best to get to not only consensus =
but to satisfy as many concerns as we possibly can. It does however require=
 people to engage in a timely manner, and even when they don&#39;t, we stil=
l do what we can, but at some point we need to move forward. As for the iss=
ue at hand, it has been discussed extensively, and several changes were mad=
e to the draft to try and accommodate your requests.<br>
<br>
The one major remaining issue I believe you have is around whether this doc=
ument updates RFC 4572. This has been discussed extensively on the wgchairs=
 list; a discussion I initiated to try and help address your concern. You m=
ay disagree with how that discussion concluded, but again, to try and allev=
iate your concerns, a note was added to 4572-update to make it clear that t=
he document does not make existing 4572 implementations non-compliant with =
RFC 4572.<br>
<br>
I believe the chairs, authors, and the WG at large has done everything that=
 can reasonably be done to try and address your concerns, and at this point=
 we need to move forward.<br>
<br>
Thanks<br>
<br>
-- Flemming (as MMUSIC co-chair)<br>
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Oct 19, 2016, at 6:43 AM, Flemming Andreasen &lt;<a href=3D"mailto:fandr=
eas@cisco.com" target=3D"_blank">fandreas@cisco.com</a>&gt; wrote:<br>
<br>
Hi<br>
<br>
Following up on the consensus call, we have received 5 responses in favor o=
f option a) below, one neutral, and one objection. Looking at the document =
we have noted that backwards compatibility is handled by the current text i=
n the document and it also clearly states that it does not make current RFC=
 4572 implementation non-compliant with RFC 4572. Since we have not heard o=
f any technical problems with proposal a), nor seen any tangible progress o=
n how to address the objection, we are hereby declaring rough consensus on =
option a). We will proceed with the publication request for the current dra=
ft while duly noting the &quot;roughness&quot; of the consensus based on th=
e pending objection as part of this.<br>
<br>
Thanks<br>
<br>
=C2=A0 =C2=A0 Flemming &amp; Bo (MMUSIC chairs)<br>
<br>
<br>
On 10/12/16 6:23 PM, Flemming Andreasen wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Greetings<br>
<br>
There has been quite a bit of discussion on draft-ietf-mmusic-4572-update (=
currently -07), which had previously completed WGLC when a few concerns wer=
e raised. The document currently:<br>
1. Clarifies the usage of multiple SDP &#39;fingerprint&#39; attributes<br>
2. Updates the preferred cipher-suite with a stronger cipher suite<br>
3. Updates RFC 4572.<br>
<br>
Item 1 seems to be generally agreeable, whereas items 2 and 3 are not. The =
chairs are hereby soliciting WG feedback on how to proceed based on the fol=
lowing choices:<br>
<br>
a) Proceed with publication of 4572-update-07 in its current form (i.e. cov=
ering all 3 items above)<br>
<br>
b) Remove item 2 from 4572-update, i.e. do not update the preferred cipher-=
suite<br>
<br>
c) Remove item 3 from 4572-update, i.e. do not indicate that this document =
constitutes an update to RFC 4572.<br>
<br>
<br>
Note that choice a) is mutually exclusive with b) and c), but b) and c) are=
 not mutually exclusive.<br>
<br>
Please let us know your preference wrt to the above no later than Friday Oc=
tober 14th.<br>
<br>
<br>
Thanks<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Flemming &amp; Bo (MMUSIC chairs)<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
.<br>
<br>
</blockquote>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
.<br>
<br>
</blockquote>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
<br>
.<br>
<br>
</blockquote>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote></div><br></div>

--001a114229c669eff1053fbd98d2--


From nobody Tue Oct 25 22:33:09 2016
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 B559112959F; Tue, 25 Oct 2016 22:33:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.951
X-Spam-Level: 
X-Spam-Status: No, score=-14.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 O_QE5mvZGfcj; Tue, 25 Oct 2016 22:33:05 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A641E12951A; Tue, 25 Oct 2016 22:33:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29289; q=dns/txt; s=iport; t=1477459985; x=1478669585; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=iORiPnnkRhVinValykb1wmO9I90vjNwEM/Apdq/aQRU=; b=LFkOyQ11WcwlWRa+sL6FJuSixZyrA2YW/uR2XmDxqLAvencOrJ/TMHXf wT9ZRIoJxl1dp9mZCk4+zgT6R2xgZAOx6fVjwIxMR4NlZlPq3f2APXbH9 oSr6xzl1+FGSDTYyGupO/ArQAh54I5fOZOJ7pGLTlxtKgmk0qF3GyIx4N 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AvAQBrPxBY/51dJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgyoBAQEBAR1YKlONNZZ+jHUUhCKDFIIHHAEKhTFKAoF1PxQBAgE?= =?us-ascii?q?BAQEBAQFiKIRjAQEEAQEBZQYLEAsYIAMEBycfEQYNBgIBAReIOQ7AFwEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBHYY9gX2BU4EFhBkRAYV7BYYmjhKFXoYqhRpyg2KBbk6?= =?us-ascii?q?EH4MXhhGHGYVvhAEeNl6CXW+BViI0hj2CKQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.31,549,1473120000";  d="scan'208,217";a="338455258"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Oct 2016 05:33:04 +0000
Received: from [10.24.21.139] ([10.24.21.139]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u9Q5X3lf018884; Wed, 26 Oct 2016 05:33:03 GMT
To: Roman Shpount <roman@telurix.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com> <CAD5OKxuaGC_+7furtohxcQrgrVCeqDf0SUDSgaSqhY7hs-insA@mail.gmail.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <f6346750-87ed-bc09-e571-bc06d8cd2f8d@cisco.com>
Date: Wed, 26 Oct 2016 01:33:02 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxuaGC_+7furtohxcQrgrVCeqDf0SUDSgaSqhY7hs-insA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------0A36C8A7723603D69A23EE6B"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/XnVK9pRsA4zGtxoAxU_wNKbj7xY>
Cc: Ben Campbell <ben@nostrum.com>, ART ADs <art-ads@ietf.org>, mmusic <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 05:33:08 -0000

This is a multi-part message in MIME format.
--------------0A36C8A7723603D69A23EE6B
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Eastern (assuming you see 10 AM, 11 AM and 12 PM)

On 10/26/16 1:07 AM, Roman Shpount wrote:
> What time zone is this?
>
> Regards,
>
> _____________
> Roman Shpount
>
> On Wed, Oct 26, 2016 at 12:54 AM, Flemming Andreasen 
> <fandreas@cisco.com <mailto:fandreas@cisco.com>> wrote:
>
>     A Doodle poll is now available at
>
>     http://doodle.com/poll/kxw4n9a2v7v3pe2y
>     <http://doodle.com/poll/kxw4n9a2v7v3pe2y>
>
>     We are looking at either Wednesday or Friday next week (November 2
>     or 4), so please get your vote in pretty quickly if you are
>     interested.
>
>     Thanks
>
>     -- Flemming
>
>
>     On 10/25/16 12:01 AM, Flemming Andreasen wrote:
>
>         Hi Ben
>
>         We will get a poll setup as soon as we understand any major
>         constraints from the key participants.
>
>         Thanks
>
>         -- Flemming
>
>
>         On 10/21/16 4:49 PM, Ben Campbell wrote:
>
>             Hi Everyone, please accept my apologies for waiting this
>             long to weigh in.
>
>             I think it's clear that multiple people are not happy with
>             how we got to this point. But assigning blame doesn't help
>             us make progress on the draft. I propose that we get over
>             that, and instead focus instead on how to move forward.
>             Email discussion doesn't seem to be helping. Maybe a call
>             will.
>
>             Flemming and/or Bo: Can you set up a Doodle poll to get
>             Christer, Cullen, and other demonstratively  interested
>             parties on a conference call? I will join if at all
>             possible, but don't let scheduling around me stop a call
>             from happening.
>
>             Thanks!
>
>             Ben.
>
>             On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:
>
>                 [fixing cc-list]
>
>                 On 10/21/16 11:59 AM, Flemming Andreasen wrote:
>
>
>
>                     On 10/21/16 11:21 AM, Cullen Jennings wrote:
>
>                         I think that is a bad way to run a WG. All I
>                         asked for was a phone call to discuss this so
>                         we could get the issues on the table and
>                         discuss what is best. The chairs never even
>                         replied to my request for a WG call to discuss
>                         this.
>
>                     That is simply not true. You (and Christer) were
>                     explicitly asked to setup a phone call on 10/6/16
>                     to discuss this issue; a request that (like many
>                     other others) went unanswered or required
>                     extensive prodding to get any attention.
>
>                         The list discussions that ensued from this
>                         resulted in people other than me sugesting
>                         possibilities that were much better than any
>                         of the three below -  none of which were
>                         considered in your consensus call.
>
>                     I'm not sure what those proposals are, nor were
>                     they brought up in response to the consensus call.
>
>                         I don’t plan to appeal this but I am
>                         considering if it’s worth my time to
>                         participate in this WG if we are not going to
>                         be willing to actually spend a short time to
>                         discuss possible solutions before taking a
>                         consensus call.  As input to that decisions,
>                         it would be really useful to know why you
>                         refused to have a phone call on this topic and
>                         what your policy in general is going to be
>                         toward discussions of proposed solutions to
>                         problems in the future.
>
>                     My position is that we will try our very best to
>                     get to not only consensus but to satisfy as many
>                     concerns as we possibly can. It does however
>                     require people to engage in a timely manner, and
>                     even when they don't, we still do what we can, but
>                     at some point we need to move forward. As for the
>                     issue at hand, it has been discussed extensively,
>                     and several changes were made to the draft to try
>                     and accommodate your requests.
>
>                     The one major remaining issue I believe you have
>                     is around whether this document updates RFC 4572.
>                     This has been discussed extensively on the
>                     wgchairs list; a discussion I initiated to try and
>                     help address your concern. You may disagree with
>                     how that discussion concluded, but again, to try
>                     and alleviate your concerns, a note was added to
>                     4572-update to make it clear that the document
>                     does not make existing 4572 implementations
>                     non-compliant with RFC 4572.
>
>                     I believe the chairs, authors, and the WG at large
>                     has done everything that can reasonably be done to
>                     try and address your concerns, and at this point
>                     we need to move forward.
>
>                     Thanks
>
>                     -- Flemming (as MMUSIC co-chair)
>
>
>
>
>                             On Oct 19, 2016, at 6:43 AM, Flemming
>                             Andreasen <fandreas@cisco.com
>                             <mailto:fandreas@cisco.com>> wrote:
>
>                             Hi
>
>                             Following up on the consensus call, we
>                             have received 5 responses in favor of
>                             option a) below, one neutral, and one
>                             objection. Looking at the document we have
>                             noted that backwards compatibility is
>                             handled by the current text in the
>                             document and it also clearly states that
>                             it does not make current RFC 4572
>                             implementation non-compliant with RFC
>                             4572. Since we have not heard of any
>                             technical problems with proposal a), nor
>                             seen any tangible progress on how to
>                             address the objection, we are hereby
>                             declaring rough consensus on option a). We
>                             will proceed with the publication request
>                             for the current draft while duly noting
>                             the "roughness" of the consensus based on
>                             the pending objection as part of this.
>
>                             Thanks
>
>                                 Flemming & Bo (MMUSIC chairs)
>
>
>                             On 10/12/16 6:23 PM, Flemming Andreasen wrote:
>
>                                 Greetings
>
>                                 There has been quite a bit of
>                                 discussion on
>                                 draft-ietf-mmusic-4572-update
>                                 (currently -07), which had previously
>                                 completed WGLC when a few concerns
>                                 were raised. The document currently:
>                                 1. Clarifies the usage of multiple SDP
>                                 'fingerprint' attributes
>                                 2. Updates the preferred cipher-suite
>                                 with a stronger cipher suite
>                                 3. Updates RFC 4572.
>
>                                 Item 1 seems to be generally
>                                 agreeable, whereas items 2 and 3 are
>                                 not. The chairs are hereby soliciting
>                                 WG feedback on how to proceed based on
>                                 the following choices:
>
>                                 a) Proceed with publication of
>                                 4572-update-07 in its current form
>                                 (i.e. covering all 3 items above)
>
>                                 b) Remove item 2 from 4572-update,
>                                 i.e. do not update the preferred
>                                 cipher-suite
>
>                                 c) Remove item 3 from 4572-update,
>                                 i.e. do not indicate that this
>                                 document constitutes an update to RFC
>                                 4572.
>
>
>                                 Note that choice a) is mutually
>                                 exclusive with b) and c), but b) and
>                                 c) are not mutually exclusive.
>
>                                 Please let us know your preference wrt
>                                 to the above no later than Friday
>                                 October 14th.
>
>
>                                 Thanks
>
>                                        Flemming & Bo (MMUSIC chairs)
>
>                                 _______________________________________________
>                                 mmusic mailing list
>                                 mmusic@ietf.org <mailto:mmusic@ietf.org>
>                                 https://www.ietf.org/mailman/listinfo/mmusic
>                                 <https://www.ietf.org/mailman/listinfo/mmusic>
>                                 .
>
>                             _______________________________________________
>                             mmusic mailing list
>                             mmusic@ietf.org <mailto:mmusic@ietf.org>
>                             https://www.ietf.org/mailman/listinfo/mmusic
>                             <https://www.ietf.org/mailman/listinfo/mmusic>
>
>                         .
>
>
>                     _______________________________________________
>                     mmusic mailing list
>                     mmusic@ietf.org <mailto:mmusic@ietf.org>
>                     https://www.ietf.org/mailman/listinfo/mmusic
>                     <https://www.ietf.org/mailman/listinfo/mmusic>
>
>
>                 _______________________________________________
>                 mmusic mailing list
>                 mmusic@ietf.org <mailto:mmusic@ietf.org>
>                 https://www.ietf.org/mailman/listinfo/mmusic
>                 <https://www.ietf.org/mailman/listinfo/mmusic>
>
>
>             .
>
>
>         _______________________________________________
>         mmusic mailing list
>         mmusic@ietf.org <mailto:mmusic@ietf.org>
>         https://www.ietf.org/mailman/listinfo/mmusic
>         <https://www.ietf.org/mailman/listinfo/mmusic>
>
>
>     _______________________________________________
>     mmusic mailing list
>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>     https://www.ietf.org/mailman/listinfo/mmusic
>     <https://www.ietf.org/mailman/listinfo/mmusic>
>
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


--------------0A36C8A7723603D69A23EE6B
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Eastern (assuming you see 10 AM, 11 AM and 12 PM)<br>
    <br>
    <div class="moz-cite-prefix">On 10/26/16 1:07 AM, Roman Shpount
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAD5OKxuaGC_+7furtohxcQrgrVCeqDf0SUDSgaSqhY7hs-insA@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div dir="ltr">What time zone is this?
        <div><br>
        </div>
        <div>Regards,</div>
      </div>
      <div class="gmail_extra"><br clear="all">
        <div>
          <div class="gmail_signature" data-smartmail="gmail_signature">_____________<br>
            Roman Shpount</div>
        </div>
        <br>
        <div class="gmail_quote">On Wed, Oct 26, 2016 at 12:54 AM,
          Flemming Andreasen <span dir="ltr">&lt;<a
              moz-do-not-send="true" href="mailto:fandreas@cisco.com"
              target="_blank">fandreas@cisco.com</a>&gt;</span> wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">A Doodle
            poll is now available at<br>
            <br>
                    <a moz-do-not-send="true"
              href="http://doodle.com/poll/kxw4n9a2v7v3pe2y"
              rel="noreferrer" target="_blank">http://doodle.com/poll/kxw4n9a<wbr>2v7v3pe2y</a><br>
            <br>
            We are looking at either Wednesday or Friday next week
            (November 2 or 4), so please get your vote in pretty quickly
            if you are interested.<br>
            <br>
            Thanks<br>
            <br>
            -- Flemming<br>
            <br>
            <br>
            On 10/25/16 12:01 AM, Flemming Andreasen wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              Hi Ben<br>
              <br>
              We will get a poll setup as soon as we understand any
              major constraints from the key participants.<br>
              <br>
              Thanks<br>
              <br>
              -- Flemming<br>
              <br>
              <br>
              On 10/21/16 4:49 PM, Ben Campbell wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                Hi Everyone, please accept my apologies for waiting this
                long to weigh in.<br>
                <br>
                I think it's clear that multiple people are not happy
                with how we got to this point. But assigning blame
                doesn't help us make progress on the draft. I propose
                that we get over that, and instead focus instead on how
                to move forward. Email discussion doesn't seem to be
                helping. Maybe a call will.<br>
                <br>
                Flemming and/or Bo: Can you set up a Doodle poll to get
                Christer, Cullen, and other demonstratively  interested
                parties on a conference call? I will join if at all
                possible, but don't let scheduling around me stop a call
                from happening.<br>
                <br>
                Thanks!<br>
                <br>
                Ben.<br>
                <br>
                On 21 Oct 2016, at 11:05, Flemming Andreasen wrote:<br>
                <br>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  [fixing cc-list]<br>
                  <br>
                  On 10/21/16 11:59 AM, Flemming Andreasen wrote:<br>
                  <blockquote class="gmail_quote" style="margin:0 0 0
                    .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    <br>
                    <br>
                    On 10/21/16 11:21 AM, Cullen Jennings wrote:<br>
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">
                      I think that is a bad way to run a WG. All I asked
                      for was a phone call to discuss this so we could
                      get the issues on the table and discuss what is
                      best. The chairs never even replied to my request
                      for a WG call to discuss this.<br>
                    </blockquote>
                    That is simply not true. You (and Christer) were
                    explicitly asked to setup a phone call on 10/6/16 to
                    discuss this issue; a request that (like many other
                    others) went unanswered or required extensive
                    prodding to get any attention.<br>
                    <br>
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">
                      The list discussions that ensued from this
                      resulted in people other than me sugesting
                      possibilities that were much better than any of
                      the three below -  none of which were considered
                      in your consensus call.<br>
                    </blockquote>
                    I'm not sure what those proposals are, nor were they
                    brought up in response to the consensus call.<br>
                    <br>
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">
                      I don’t plan to appeal this but I am considering
                      if it’s worth my time to participate in this WG if
                      we are not going to be willing to actually spend a
                      short time to discuss possible solutions before
                      taking a consensus call.  As input to that
                      decisions, it would be really useful to know why
                      you refused to have a phone call on this topic and
                      what your policy in general is going to be toward
                      discussions of proposed solutions to problems in
                      the future.<br>
                    </blockquote>
                    My position is that we will try our very best to get
                    to not only consensus but to satisfy as many
                    concerns as we possibly can. It does however require
                    people to engage in a timely manner, and even when
                    they don't, we still do what we can, but at some
                    point we need to move forward. As for the issue at
                    hand, it has been discussed extensively, and several
                    changes were made to the draft to try and
                    accommodate your requests.<br>
                    <br>
                    The one major remaining issue I believe you have is
                    around whether this document updates RFC 4572. This
                    has been discussed extensively on the wgchairs list;
                    a discussion I initiated to try and help address
                    your concern. You may disagree with how that
                    discussion concluded, but again, to try and
                    alleviate your concerns, a note was added to
                    4572-update to make it clear that the document does
                    not make existing 4572 implementations non-compliant
                    with RFC 4572.<br>
                    <br>
                    I believe the chairs, authors, and the WG at large
                    has done everything that can reasonably be done to
                    try and address your concerns, and at this point we
                    need to move forward.<br>
                    <br>
                    Thanks<br>
                    <br>
                    -- Flemming (as MMUSIC co-chair)<br>
                    <br>
                    <br>
                    <br>
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">
                      <br>
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        On Oct 19, 2016, at 6:43 AM, Flemming Andreasen
                        &lt;<a moz-do-not-send="true"
                          href="mailto:fandreas@cisco.com"
                          target="_blank">fandreas@cisco.com</a>&gt;
                        wrote:<br>
                        <br>
                        Hi<br>
                        <br>
                        Following up on the consensus call, we have
                        received 5 responses in favor of option a)
                        below, one neutral, and one objection. Looking
                        at the document we have noted that backwards
                        compatibility is handled by the current text in
                        the document and it also clearly states that it
                        does not make current RFC 4572 implementation
                        non-compliant with RFC 4572. Since we have not
                        heard of any technical problems with proposal
                        a), nor seen any tangible progress on how to
                        address the objection, we are hereby declaring
                        rough consensus on option a). We will proceed
                        with the publication request for the current
                        draft while duly noting the "roughness" of the
                        consensus based on the pending objection as part
                        of this.<br>
                        <br>
                        Thanks<br>
                        <br>
                            Flemming &amp; Bo (MMUSIC chairs)<br>
                        <br>
                        <br>
                        On 10/12/16 6:23 PM, Flemming Andreasen wrote:<br>
                        <blockquote class="gmail_quote" style="margin:0
                          0 0 .8ex;border-left:1px #ccc
                          solid;padding-left:1ex">
                          Greetings<br>
                          <br>
                          There has been quite a bit of discussion on
                          draft-ietf-mmusic-4572-update (currently -07),
                          which had previously completed WGLC when a few
                          concerns were raised. The document currently:<br>
                          1. Clarifies the usage of multiple SDP
                          'fingerprint' attributes<br>
                          2. Updates the preferred cipher-suite with a
                          stronger cipher suite<br>
                          3. Updates RFC 4572.<br>
                          <br>
                          Item 1 seems to be generally agreeable,
                          whereas items 2 and 3 are not. The chairs are
                          hereby soliciting WG feedback on how to
                          proceed based on the following choices:<br>
                          <br>
                          a) Proceed with publication of 4572-update-07
                          in its current form (i.e. covering all 3 items
                          above)<br>
                          <br>
                          b) Remove item 2 from 4572-update, i.e. do not
                          update the preferred cipher-suite<br>
                          <br>
                          c) Remove item 3 from 4572-update, i.e. do not
                          indicate that this document constitutes an
                          update to RFC 4572.<br>
                          <br>
                          <br>
                          Note that choice a) is mutually exclusive with
                          b) and c), but b) and c) are not mutually
                          exclusive.<br>
                          <br>
                          Please let us know your preference wrt to the
                          above no later than Friday October 14th.<br>
                          <br>
                          <br>
                          Thanks<br>
                          <br>
                                 Flemming &amp; Bo (MMUSIC chairs)<br>
                          <br>
                          ______________________________<wbr>_________________<br>
                          mmusic mailing list<br>
                          <a moz-do-not-send="true"
                            href="mailto:mmusic@ietf.org"
                            target="_blank">mmusic@ietf.org</a><br>
                          <a moz-do-not-send="true"
                            href="https://www.ietf.org/mailman/listinfo/mmusic"
                            rel="noreferrer" target="_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br>
                          .<br>
                          <br>
                        </blockquote>
                        ______________________________<wbr>_________________<br>
                        mmusic mailing list<br>
                        <a moz-do-not-send="true"
                          href="mailto:mmusic@ietf.org" target="_blank">mmusic@ietf.org</a><br>
                        <a moz-do-not-send="true"
                          href="https://www.ietf.org/mailman/listinfo/mmusic"
                          rel="noreferrer" target="_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br>
                      </blockquote>
                      .<br>
                      <br>
                    </blockquote>
                    <br>
                    ______________________________<wbr>_________________<br>
                    mmusic mailing list<br>
                    <a moz-do-not-send="true"
                      href="mailto:mmusic@ietf.org" target="_blank">mmusic@ietf.org</a><br>
                    <a moz-do-not-send="true"
                      href="https://www.ietf.org/mailman/listinfo/mmusic"
                      rel="noreferrer" target="_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br>
                  </blockquote>
                  <br>
                  ______________________________<wbr>_________________<br>
                  mmusic mailing list<br>
                  <a moz-do-not-send="true"
                    href="mailto:mmusic@ietf.org" target="_blank">mmusic@ietf.org</a><br>
                  <a moz-do-not-send="true"
                    href="https://www.ietf.org/mailman/listinfo/mmusic"
                    rel="noreferrer" target="_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br>
                </blockquote>
                <br>
                .<br>
                <br>
              </blockquote>
              <br>
              ______________________________<wbr>_________________<br>
              mmusic mailing list<br>
              <a moz-do-not-send="true" href="mailto:mmusic@ietf.org"
                target="_blank">mmusic@ietf.org</a><br>
              <a moz-do-not-send="true"
                href="https://www.ietf.org/mailman/listinfo/mmusic"
                rel="noreferrer" target="_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br>
            </blockquote>
            <br>
            ______________________________<wbr>_________________<br>
            mmusic mailing list<br>
            <a moz-do-not-send="true" href="mailto:mmusic@ietf.org"
              target="_blank">mmusic@ietf.org</a><br>
            <a moz-do-not-send="true"
              href="https://www.ietf.org/mailman/listinfo/mmusic"
              rel="noreferrer" target="_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <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>

--------------0A36C8A7723603D69A23EE6B--


From nobody Wed Oct 26 00:20:57 2016
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 DEF781293EB for <mmusic@ietfa.amsl.com>; Wed, 26 Oct 2016 00:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 r0K_nzSb59bN for <mmusic@ietfa.amsl.com>; Wed, 26 Oct 2016 00:20:51 -0700 (PDT)
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 98510129A33 for <mmusic@ietf.org>; Wed, 26 Oct 2016 00:20:41 -0700 (PDT)
X-AuditID: c1b4fb2d-5b107980000009f7-04-5810594746b9
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by  (Symantec Mail Security) with SMTP id C1.30.02551.74950185; Wed, 26 Oct 2016 09:20:39 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0319.002; Wed, 26 Oct 2016 09:20:37 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] Draft new version: BUNDLE-35 - Colin's comments
Thread-Index: AQHSL1lyUH8R3Vq1+EKuIfomZvAUwA==
Date: Wed, 26 Oct 2016 07:20:37 +0000
Message-ID: <D4362E14.11C83%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <2BBAD371A5AFD74CB60C3D447797A693@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphkeLIzCtJLcpLzFFi42KZGbE9XNc9UiDCoPW8lcXylycYLaYuf8zi wOQx7f59No8lS34yBTBFcdmkpOZklqUW6dslcGW0L3jNXHBbrOLgvduMDYyThLoYOTkkBEwk Tvzcz9bFyMUhJLCeUeLKg7WMEM4SRonnnz6ydjFycLAJWEh0/9MGaRARUJXYcfwfI0iYWUBd 4uriIBBTWMBVYtV6ERBTRMBNYu/hIIhiPYnpB3ewgNgsQI13r55jBbF5Bawlpt9/yghiMwqI SXw/tYYJxGYWEJe49WQ+E8RlAhJL9pxnhrBFJV4+/gd2iyjQzDX3wyDCihI7z7YzQ7QaSLw/ Nx/KtpZY/m0OI4StLbFs4WtmiLWCEidnPmGZwCg6C8m2WUjaZyFpn4WkfRaS9gWMrKsYRYtT i4tz042M9VKLMpOLi/Pz9PJSSzYxAuPm4JbfujsYV792PMQowMGoxMO7YC5/hBBrYllxZe4h RgkOZiURXosQgQgh3pTEyqrUovz4otKc1OJDjNIcLErivGYr74cLCaQnlqRmp6YWpBbBZJk4 OKUaGKt/N848ySdZsSj8yY3Sedf9L15/UeSqcfBWzOPavS+NWyX3vTW4tfxxq8d7/7Pzv9xU /R/+jN8i680OtqXlh30uaZ7cIrBHV8dYbJ7irKUq667eWOLPqPHJ3m11zMR/U9OandgMFG1F RS6dD5wxcY/Ot1gLEaUjgRb+JmqljmlL3I6qrN/MGqbEUpyRaKjFXFScCACBWaUHlwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2At303wdNfOuPdmif330BIfEZkY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: BUNDLE-35 - Colin's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 07:20:55 -0000

Hi Colin,

Thanks for your comments! See inline.

>>On 25 Oct 2016, at 11:24, Christer Holmberg
>><christer.holmberg@ericsson.com> wrote:
>>=20
>> I=B9ve submitted a new version (-35) of BUNDLE.
>>=20
>> The text now talks about =B3associating RTP streams with m- lines=B2
>>(instead of associating RTP packets).
>
>I think this new text is good, and addresses most of my concerns. I just
>have a few details outstanding:
>
>- Section 9.1, last paragraph: I suggest changing =B3associate a received
>(S)RTP packet with=B2 to =B3associate the packets in a received SRTP strea=
m
>with=B2.

I=B9ll fix as suggested.

I=B9ll also change Section 1, which still talks about associating RTP
packets with m- lines.


>- Section 10.1, 1st paragraph: The second sentence (=B3Disjoint BUNDLE
>groups will form multiple RTP sessions, one per BUNDLE group=B2) is
>probably true, but depends on the RTP topology, since a middlebox could
>bridge the different BUNDLE groups together into a single RTP session. I
>suggest deleting this sentence.

I=B9ll remove it.

>=20
>
>- Section 10.2, 1st paragraph: At the end of the first sentence, you
>might cite RFC7656 for the definition of the term RTP Stream.

I=B9ll add a reference.


>- Section 10.2, 7th paragraph: This seems correct, but I found the
>phrasing unclear. Something like the following might be clearer:
>
>   The mapping from an SSRC to an identification-tag is carried in RTCP
>   SDES packets or in RTP header extensions, as described in Section 14.
>   Since a compound RTCP packet can contain multiple RTCP SDES packets,
>   and each RTCP SDES packet can contain multiple chunks, an RTCP packet
>   can contain several SSRC to identification-tag mappings. The offerer
>   and answerer maintain tables mapping RTP streams identified by SSRC,
>   to =B3m=3D=B3 lines identified by the identification-tag. These tables =
are
>   updated each time an RTP/RTCP packet containing one or more mappings
>   from SSRC to identification-tag is received. Note that the mapping
>   from SSRC to identification-tag can change at any time during an RTP
>   session.


I=B9ll change as suggested.


>- Section 10.2, 8th paragraph: The last sentence might be clearer written
>=B3Note that RTCP packets can report on multiple RTP streams=B2.

I=B9ll change as suggested.

> Also, the XML formatting is messed up in the middle of the paragraph.

It looks ok in my editor :)

OTOH, I have changed editor recently, so there are lots of instances where
the XML does look a little messy.

>
>- Section 14, 3rd paragraph: Suggest changing =B3=8Ato associate received
>RTCP- and RTP packets with=8A=B3 to =B3=8Ato associated each RTP stream wi=
th=8A=B2.

I=B9ll change as suggested.

Pull request can be found at:

https://github.com/cdh4u/draft-sdp-bundle/pull/14


Regards,

Christer


From nobody Wed Oct 26 02:27:20 2016
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 E624E129A48; Wed, 26 Oct 2016 02:27:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147747402093.18859.13075688999230198596.idtracker@ietfa.amsl.com>
Date: Wed, 26 Oct 2016 02:27:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/VTkRtUMFvqmobdleX7SKK0-B2pI>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sctp-sdp-19.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 09:27:18 -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 of the IETF.

        Title           : Session Description Protocol (SDP) Offer/Answer Procedures For Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport.
        Authors         : Christer Holmberg
                          Roman Shpount
                          Salvatore Loreto
                          Gonzalo Camarillo
	Filename        : draft-ietf-mmusic-sctp-sdp-19.txt
	Pages           : 25
	Date            : 2016-10-26

Abstract:
   The Stream Control Transmission Protocol (SCTP) is a transport
   protocol used to establish associations between two endpoints.
   draft-ietf-tsvwg-sctp-dtls-encaps-09 specifies how SCTP can be used
   on top of the Datagram Transport Layer Security (DTLS) protocol,
   referred to as SCTP-over-DTLS.

   This specification defines the following new Session Description
   Protocol (SDP) protocol identifiers (proto values):'UDP/DTLS/SCTP'
   and 'TCP/DTLS/SCTP'.  This specification also specifies how to use
   the new proto values with the SDP Offer/Answer mechanism for
   negotiating SCTP-over-DTLS associations.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-sctp-sdp-19

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


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 Wed Oct 26 02:50:10 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 D108512940F; Wed, 26 Oct 2016 02:50:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147747540682.18851.267971327825992233.idtracker@ietfa.amsl.com>
Date: Wed, 26 Oct 2016 02:50:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/o_wJPhggsNLLgS41Kej-Tb3xfOQ>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] Stephen Farrell's No Objection on draft-ietf-mmusic-sdp-mux-attributes-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 09:50:07 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-mmusic-sdp-mux-attributes-14: No Objection

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


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


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



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


- 4.5 and 5.7: What if the different a=crypto lines
specify different strength ciphersuites? Wouldn't it be
better to pick the strongest or to say they MUST be the
same (as is done in 5.35)? If picking the first is the
right answer then maybe warn folks to not put a stronger
ciphersuite anywhere else?

- 5.36 vs. 5.39: It wasn't clear to me why these have
different rules - can you explain?



From nobody Wed Oct 26 02:54:11 2016
Return-Path: <mparisdiaz@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 66FD51294BC for <mmusic@ietfa.amsl.com>; Wed, 26 Oct 2016 02:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 NLppJCeQG3RN for <mmusic@ietfa.amsl.com>; Wed, 26 Oct 2016 02:54:05 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 726BA12940F for <mmusic@ietf.org>; Wed, 26 Oct 2016 02:54:05 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id 140so11044394wmv.0 for <mmusic@ietf.org>; Wed, 26 Oct 2016 02:54:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to; bh=jinr8qaohCWlUYwZQ+Tb4rV7b67/CiaWQj1uXlfxb98=; b=EN7lEn+boBCSXVA82w7aXKy3H7Ahw2gNMrkdty39AzCYFo9/TczCFIs2wfdxWrBO/h YiMlT6lvNLpkWa1fVsycMz3JvcjYzzrLed5+sQKWtzgifUcYB6k35GxRe8puctJ9pGIu O18NLGfGPPXzsYogePramI6e4LW3arbZnh6f5X9VuP/zdq6y+ASOQYMusfQ/UuIaerV2 4QFPcv4WPh+eBlVwWSDOqzasMJet3V8Wfq6Rx4gZ5tQU7BX1GOTj8P3052x339kYCbLC W+KiEA2Jh0nroiUEd/An7pdJ4VP+VIRsiCtRx5U7JfTZ2IMvCTDrKf+QCHB0OVVIt2GZ Xz3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=jinr8qaohCWlUYwZQ+Tb4rV7b67/CiaWQj1uXlfxb98=; b=RisSCzxAZJuWfg+ptTP2S1WwA9jDSpOAJHj2udWn11BtRdix0Ld3Eh92K1rRB+jLyn 7tMyeZ6Asw8MAwPikmKm9/OsagYDWq3m+k5UXGXQVm1oKNO9wKPCpV+QPFw3HrNbMVew ION8LLlJIRgN5dL54XkvjYNzbN5AkQj9rorutA+d5FLp6rzFcDNKNx1S21ibxyOmgeZY 4cNQg5fXxq1QjgGyx+zf7pSaFVnO+6Rv43yiZEXbNTH1uzalqFCp2W2hD22Yf0cL2epf 5AsPQqHFSdD0tO1sv1eX9Qs2sERDFsy1OFeKeob/b0mro9LGEsxxAFS1LObCIx1CnS81 Fa2g==
X-Gm-Message-State: ABUngvfYhYBbZMo9wBT9ggqH37hNIKmUdCg+L7thtzKi3cfIYZLpc2zqIphin5LvE4h89QsKeJVVccIDpnNVGQ==
X-Received: by 10.28.134.6 with SMTP id i6mr1847329wmd.100.1477475642924; Wed, 26 Oct 2016 02:54:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.55.5 with HTTP; Wed, 26 Oct 2016 02:54:02 -0700 (PDT)
From: =?UTF-8?Q?Miguel_Par=C3=ADs_D=C3=ADaz?= <mparisdiaz@gmail.com>
Date: Wed, 26 Oct 2016 11:54:02 +0200
Message-ID: <CAEn+E3jyfcYvqFm2e+DjhQMmZK4YquFgrdJja9rwFAV43SQ63g@mail.gmail.com>
To: mmusic <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary=001a11442998dc6498053fc19aed
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/WJOsfBwdoTliE16uJhh5KRp1cPY>
Subject: [MMUSIC] draft-ietf-mmusic-msid-15: wrong procedure
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 09:54:09 -0000

--001a11442998dc6498053fc19aed
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello,
while implementing msid support I have found a wrong description in
"Answerer processing of the Offer" [1]

If I am not wrong, the problem is that this step:

Signal to the user that a new MediaStreamTrack is available.

should be performed only for each media description in the offer, but *NOT*
for each "a=3Dmsid" attribute.
This would match with JSEP and PeerConnection specifications, where there
is only one event per MediaStreamTrack with a list of the related
MediaStreams.

Best!!

Refs
[1] https://tools.ietf.org/html/draft-ietf-mmusic-msid-15#section-3.2.2

--=20
Miguel Par=C3=ADs D=C3=ADaz
------------------------------------------------------------------------
Computer/Software engineer.
Researcher and architect in http://www.kurento.org
http://twitter.com/mparisdiaz
------------------------------------------------------------------------

--001a11442998dc6498053fc19aed
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello,<br></div><div>while implementing msid support =
I have found a wrong description in &quot;Answerer processing of the Offer&=
quot; [1]<br><br></div><div>If I am not wrong, the problem is that this ste=
p:<br><pre class=3D"gmail-newpage">Signal to the user that a new MediaStrea=
mTrack is available.<br></pre></div><div>should be performed only for each =
media description in the offer, but <b>NOT</b> for each &quot;a=3Dmsid&quot=
; attribute.<br></div><div>This would match with JSEP and PeerConnection sp=
ecifications, where there is only one event per MediaStreamTrack with a lis=
t of the related MediaStreams.<br></div><div><br></div><div>Best!!<br><br><=
/div>Refs<br>[1] <a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-m=
sid-15#section-3.2.2">https://tools.ietf.org/html/draft-ietf-mmusic-msid-15=
#section-3.2.2</a><br clear=3D"all"><div><div><br>-- <br><div class=3D"gmai=
l_signature"><div dir=3D"ltr">Miguel Par=C3=ADs D=C3=ADaz<br>--------------=
----------------------------------------------------------<br>Computer/Soft=
ware engineer.<br>Researcher and architect in <a href=3D"http://www.kurento=
.org" target=3D"_blank">http://www.kurento.org</a><br><a href=3D"http://twi=
tter.com/mparisdiaz" target=3D"_blank">http://twitter.com/mparisdiaz</a><br=
>------------------------------------------------------------------------<b=
r></div></div>
</div></div></div>

--001a11442998dc6498053fc19aed--


From nobody Wed Oct 26 02:54:49 2016
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 8126F12963B; Wed, 26 Oct 2016 02:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 5q1ziBRHLJa8; Wed, 26 Oct 2016 02:54:47 -0700 (PDT)
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 1548E12940F; Wed, 26 Oct 2016 02:54:46 -0700 (PDT)
X-AuditID: c1b4fb25-5405a9800000793b-99-58107d656b58
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by  (Symantec Mail Security) with SMTP id DF.64.31035.56D70185; Wed, 26 Oct 2016 11:54:45 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0319.002; Wed, 26 Oct 2016 11:54:44 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: SCTP-SDP-19
Thread-Index: AQHSL275bDyzmVPoS0emm/bufSdHMQ==
Date: Wed, 26 Oct 2016 09:54:43 +0000
Message-ID: <D43659C5.11CFF%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_D43659C511CFFchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuphkeLIzCtJLcpLzFFi42KZGbHdWze1ViDC4MoZeYvzO9czWUxd/pjF gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZrafPsxS85Kx4sfMFWwPjIY4uRk4OCQETidbNq5lA bCGB9YwS++8bdjFyAdlLGCV+LPzA1sXIwcEmYCHR/U8bpEZEQF3i694eZhCbWcBU4uGrNYwg tjBQfNX3JewQNToSt64sY4Ow9SQ+zbzHCmKzCKhKHJryAayGV8BaYsXSm2BzGAXEJL6fWsME MVNc4taT+UwQtwlILNlznhnCFpV4+fgfK8g5okAz19wPAzElBBQllvfLQXQmSFzsv8AEMV1Q 4uTMJywTGIVnIRk6C0nZLCRlEHEDiffn5jND2NoSyxa+hrL1JTZ+OcsIYVtLzDvUyYasZgEj xypG0eLU4qTcdCNjvdSizOTi4vw8vbzUkk2MwDg6uOW36g7Gy28cDzEKcDAq8fAumMsfIcSa WFZcmXuIUYKDWUmE91e1QIQQb0piZVVqUX58UWlOavEhRmkOFiVxXrOV98OFBNITS1KzU1ML UotgskwcnFINjLUneU1FJqVOYbjX5bOyxnzj9rNJkz8cyy+ZOff2uzP2r2faNYmKHxbafeDh p12dVhZX5sV9v9H/5ciluMPctSeMPc/dP6q0LuGL2Nt1x4JfT5Dl82F1k5bJX/TYfMPKtxun vslTOpJsfnTJk8CPDU8f1DNlr1ls4ddw68HP2x4phjo/0irvfX6pxFKckWioxVxUnAgAoTvH 2p8CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/pT_O24SvVv90drF7c7czgn0JjBE>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
Subject: [MMUSIC] Draft new version: SCTP-SDP-19
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 09:54:48 -0000

--_000_D43659C511CFFchristerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

Based on the WGLC comments, I=92ve submitted a new version (-19) of draft-s=
ctp-sdp.

Thanks to everyone who provided comments and participated in the discussion=
s! :)

Regards,

Christer

--_000_D43659C511CFFchristerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <09768F4E8DD1EF41BD648A7E541EA484@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>Based on the WGLC comments, I=92ve submitted a new version (-19) of dr=
aft-sctp-sdp.</div>
<div><br>
</div>
<div>Thanks to everyone who provided comments and participated in the discu=
ssions! :)</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
</body>
</html>

--_000_D43659C511CFFchristerholmbergericssoncom_--


From nobody Wed Oct 26 08:39:36 2016
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 2B15E129677 for <mmusic@ietfa.amsl.com>; Wed, 26 Oct 2016 08:39:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 tVOvX3cOpGA7 for <mmusic@ietfa.amsl.com>; Wed, 26 Oct 2016 08:39:31 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23E0412966E for <mmusic@ietf.org>; Wed, 26 Oct 2016 08:39:31 -0700 (PDT)
Received: from [130.209.247.112] (port=55343 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1bzQIZ-0001i7-VV; Wed, 26 Oct 2016 16:39:29 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <D4362E14.11C83%christer.holmberg@ericsson.com>
Date: Wed, 26 Oct 2016 16:39:27 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A987293-1DC3-47ED-BC78-E335026C7566@csperkins.org>
References: <D4362E14.11C83%christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/BRhrPSrAK4CQrQfqP_j9Bh7Wob8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: BUNDLE-35 - Colin's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 15:39:35 -0000

Hi,

> On 26 Oct 2016, at 08:20, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi Colin,
>=20
> Thanks for your comments! See inline.
>=20
>>> On 25 Oct 2016, at 11:24, Christer Holmberg
>>> <christer.holmberg@ericsson.com> wrote:
>>>=20
>>> I=C4=85ve submitted a new version (-35) of BUNDLE.
>>>=20
>>> The text now talks about =C5=82associating RTP streams with m- =
lines=CB=9B
>>> (instead of associating RTP packets).
>>=20
>> I think this new text is good, and addresses most of my concerns. I =
just
>> have a few details outstanding:
>>=20
>> - Section 9.1, last paragraph: I suggest changing =C5=82associate a =
received
>> (S)RTP packet with=CB=9B to =C5=82associate the packets in a received =
SRTP stream
>> with=CB=9B.
>=20
> I=C4=85ll fix as suggested.
>=20
> I=C4=85ll also change Section 1, which still talks about associating =
RTP
> packets with m- lines.
>=20
>=20
>> - Section 10.1, 1st paragraph: The second sentence (=C5=82Disjoint =
BUNDLE
>> groups will form multiple RTP sessions, one per BUNDLE group=CB=9B) =
is
>> probably true, but depends on the RTP topology, since a middlebox =
could
>> bridge the different BUNDLE groups together into a single RTP =
session. I
>> suggest deleting this sentence.
>=20
> I=C4=85ll remove it.
>=20
>>=20
>>=20
>> - Section 10.2, 1st paragraph: At the end of the first sentence, you
>> might cite RFC7656 for the definition of the term RTP Stream.
>=20
> I=C4=85ll add a reference.
>=20
>=20
>> - Section 10.2, 7th paragraph: This seems correct, but I found the
>> phrasing unclear. Something like the following might be clearer:
>>=20
>>  The mapping from an SSRC to an identification-tag is carried in RTCP
>>  SDES packets or in RTP header extensions, as described in Section =
14.
>>  Since a compound RTCP packet can contain multiple RTCP SDES packets,
>>  and each RTCP SDES packet can contain multiple chunks, an RTCP =
packet
>>  can contain several SSRC to identification-tag mappings. The offerer
>>  and answerer maintain tables mapping RTP streams identified by SSRC,
>>  to =C5=82m=3D=C5=82 lines identified by the identification-tag. =
These tables are
>>  updated each time an RTP/RTCP packet containing one or more mappings
>>  from SSRC to identification-tag is received. Note that the mapping
>>  from SSRC to identification-tag can change at any time during an RTP
>>  session.
>=20
>=20
> I=C4=85ll change as suggested.
>=20
>=20
>> - Section 10.2, 8th paragraph: The last sentence might be clearer =
written
>> =C5=82Note that RTCP packets can report on multiple RTP streams=CB=9B.
>=20
> I=C4=85ll change as suggested.
>=20
>> Also, the XML formatting is messed up in the middle of the paragraph.
>=20
> It looks ok in my editor :)
>=20
> OTOH, I have changed editor recently, so there are lots of instances =
where
> the XML does look a little messy.

I meant that the XML codes are appearing in the text version of the =
draft.

>> - Section 14, 3rd paragraph: Suggest changing =C5=82=C5=A0to =
associate received
>> RTCP- and RTP packets with=C5=A0=C5=82 to =C5=82=C5=A0to associated =
each RTP stream with=C5=A0=CB=9B.
>=20
> I=C4=85ll change as suggested.
>=20
> Pull request can be found at:
>=20
> https://github.com/cdh4u/draft-sdp-bundle/pull/14

Thanks.

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





From nobody Wed Oct 26 09:15:09 2016
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 AE2B212968F; Wed, 26 Oct 2016 09:15:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.331
X-Spam-Level: 
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oQQIf4NwrwCm; Wed, 26 Oct 2016 09:15:03 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B7CF1295F2; Wed, 26 Oct 2016 09:15:02 -0700 (PDT)
Received: from [10.10.1.2] ([162.216.46.64]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u9QGExmn029888 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 26 Oct 2016 11:15:00 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [162.216.46.64] claimed to be [10.10.1.2]
From: "Ben Campbell" <ben@nostrum.com>
To: "Suhas Nandakumar" <suhasietf@gmail.com>
Date: Wed, 26 Oct 2016 09:14:58 -0700
Message-ID: <C4D71CF6-9871-4B7B-916A-1D5318114A91@nostrum.com>
In-Reply-To: <CAMRcRGTaexMuirQS=O=YWOUb379iyrPxKvWdvdzSTseX=WOGsQ@mail.gmail.com>
References: <147742756171.8565.11705230224719531567.idtracker@ietfa.amsl.com> <5A934910-073D-46A9-866C-EFA63956F3F3@iii.ca> <CAKKJt-cTAAiFa-TTwB70oxo2ia25QGrBwFacJkarnOD=NEtqBQ@mail.gmail.com> <CAMRcRGTaexMuirQS=O=YWOUb379iyrPxKvWdvdzSTseX=WOGsQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.5r5263)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/7g0DLIqxiRetNJXAn10seSAwsbg>
Cc: mmusic-chairs@ietf.org, mmusic WG <mmusic@ietf.org>, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Cullen Jennings <fluffy@iii.ca>, The IESG <iesg@ietf.org>
Subject: Re: [MMUSIC] Spencer Dawkins' Yes on draft-ietf-mmusic-sdp-mux-attributes-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 16:15:06 -0000

On 25 Oct 2016, at 21:11, Suhas Nandakumar wrote:

> Thanks Spencer for the review and Thanks Cullen for the inputs.
>
> Given the discussion above, I can update the security considerations
> section as suggested by Spencer and generate a new version whenever it 
> is
> appropriate and just to double check on the outcome - the category TBD 
> stay
> as it is.
>
> Spencer, please advise if i misunderstood anything
>
> Ben, please let me know procedures on generating the next version.

Given that the telechat is tomorrow, and some other comments have 
already come in: I suggest addressing the comments via email, then 
submitting an update as soon after the telechat as is convenient.

Thanks!

Ben.

>
> Cheers
> Suhas
>
> On Tue, Oct 25, 2016 at 8:15 PM, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
>> Hi, Cullen,
>>
>> On Tue, Oct 25, 2016 at 8:32 PM, Cullen Jennings <fluffy@iii.ca> 
>> wrote:
>>
>>>
>>>> On Oct 25, 2016, at 1:32 PM, Spencer Dawkins <
>>> spencerdawkins.ietf@gmail.com> wrote:
>>>>
>>>> Spencer Dawkins has entered the following ballot position for
>>>> draft-ietf-mmusic-sdp-mux-attributes-14: Yes
>>>>
>>>> When responding, please keep the subject line intact and reply to 
>>>> all
>>>> email addresses included in the To and CC lines. (Feel free to cut 
>>>> this
>>>> introductory paragraph, however.)
>>>>
>>>>
>>>> Please refer to https://www.ietf.org/iesg/stat
>>> ement/discuss-criteria.html
>>>> for more information about IESG DISCUSS and COMMENT positions.
>>>>
>>>>
>>>> The document, along with other ballot positions, can be found here:
>>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/
>>>>
>>>>
>>>>
>>>> ----------------------------------------------------------------------
>>>> COMMENT:
>>>> ----------------------------------------------------------------------
>>>>
>>>> This document is a work of art. Thank you folks for accepting the
>>>> challenge, because it's important.
>>>>
>>>> I have a couple of observations, to go along with my Yes ballot. 
>>>> Please
>>>> do the right thing.
>>>>
>>>> I know Mirja also pushed on the TBD category, but I find RFC 2119
>>> "SHOULD
>>>> NOT" to be problematic.
>>>>
>>>>   The attributes in the TBD category have not been analyzed under 
>>>> the
>>>>   proposed multiplexing framework and SHOULD NOT be multiplexed.
>>>>
>>>> The point of SHOULD (NOT) is that you don't do this unless you
>>> understand
>>>> the risks, and in this case, it seems to me that you don't know the
>>>> risks. If you're determined to multiplex the TBD attribute 
>>>> "frommet=",
>>>> won't you have to do your own analysis? Wouldn't that mean you 
>>>> might
>>> make
>>>> assumptions ("it's IDENTICAL") that conflict with the analysis 
>>>> other
>>>> implementers are doing ("it's TRANSPORT")?
>>>>
>>>> I could imagine a couple of approaches that might be helpful here.
>>>>
>>>> Saying "MUST NOT be multiplexed" would avoid implementers doing 
>>>> their
>>> own
>>>> analysis and coming up with conflicting answers. Is it obvious why 
>>>> this
>>>> is "SHOULD NOT" instead of "MUST NOT"? In other words, who needs to
>>>> multiplex TBD attributes, and why?
>>>>
>>>> Saying "cannot be assumed to be safe when multiplexed" probably 
>>>> captures
>>>> what I think you are saying. ''
>>>
>>> Yes, I think your summary is about right here. For better or worse 
>>> the
>>> logic of SHOULD was that a later spec that correctly classified them 
>>> could
>>> put them in the right category. I don't know what would be the best 
>>> (if
>>> any) change to make to the spec but I wanted to agree with your
>>> understanding.
>>
>>
>> "Do the right thing" :-)
>>
>>
>>>>
>>>> Would it be clearer if the category was called UNKNOWN?
>>>
>>> We were trying to capture that it was not that future specs would 
>>> not be
>>> able to figure out what to do with these, but more that this RFC had 
>>> not
>>> classified them.
>>
>>
>> I'm pretty sure I'm stumbling over something that is less clear now 
>> than
>> it will be when the working group is using this framework (so, this 
>> makes
>> sense to me).
>>
>>
>>>>
>>>> In this text,
>>>>
>>>> 16.  Security Considerations
>>>>
>>>>   This document does not add any new security considerations beyond 
>>>> the
>>>>   existing considerations in the RTP RFCs ([RFC3550] and [RFC3711])
>>>>   that are referenced by this specification.
>>>>
>>>> I don't understand how the first paragraph ^^ and the third 
>>>> paragraph of
>>>> the section are compatible, because you're referring to issues 
>>>> described
>>>> in this specification. But if you delete the first paragraph, 
>>>> leaving
>>>> only
>>>>
>>>>   The primary security for RTP including the way it is used here is
>>>>   described in [RFC3550] and [RFC3711].
>>>>
>>>>   When multiplexing SDP attributes with the category "CAUTION", the
>>>>   implementations should be aware of possible issues as described 
>>>> in
>>>>   this specification.
>>>>
>>>> the security considerations would be consistent.
>>>
>>> Works For Me ... i think the text that is there goes back to early 
>>> boiler
>>> plate text we took from somewhere...
>>>
>>
>> Cool - and thanks for considering my comments.
>>
>> Spencer
>>
>> _______________________________________________
>> 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 Oct 26 10:13:34 2016
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 39F0D129BEF for <mmusic@ietfa.amsl.com>; Wed, 26 Oct 2016 10:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 IJJ56f7LxdmW for <mmusic@ietfa.amsl.com>; Wed, 26 Oct 2016 10:13:27 -0700 (PDT)
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 4F98E129BEA for <mmusic@ietf.org>; Wed, 26 Oct 2016 10:13:26 -0700 (PDT)
X-AuditID: c1b4fb30-b73ff70000000cb2-e0-5810e434de67
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by  (Symantec Mail Security) with SMTP id 1B.57.03250.434E0185; Wed, 26 Oct 2016 19:13:25 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0319.002; Wed, 26 Oct 2016 19:13:24 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] Draft new version: BUNDLE-35 - Colin's comments
Thread-Index: AQHSL1lyUH8R3Vq1+EKuIfomZvAUwKC6vgqAgAA6fyA=
Date: Wed, 26 Oct 2016 17:13:23 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BDF2B3F@ESESSMB209.ericsson.se>
References: <D4362E14.11C83%christer.holmberg@ericsson.com> <4A987293-1DC3-47ED-BC78-E335026C7566@csperkins.org>
In-Reply-To: <4A987293-1DC3-47ED-BC78-E335026C7566@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBLMWRmVeSWpSXmKPExsUyM2K7q67pE4EIg6XfpSyWvzzBaDF1+WMW ByaPaffvs3ksWfKTKYApissmJTUnsyy1SN8ugStj0dF9jAWTWCoOfGxia2BsYeli5OSQEDCR +HD2BpDNxSEksJ5R4unK++wQzhJGiT/Nr5i7GDk42AQsJLr/aYM0iAioSuw4/o8RJMwsoC5x dXEQSFhYwFWivXM3E0hYRMBNYu/hIIhqK4m31+aDrWIB6tzwbyIriM0r4Ctx9U0XmC0kUCTx 99pNZhCbU8BRYt2spYwgNqOAmMT3U2uYQGxmAXGJW0/mM0GcLCCxZM95ZghbVOLl43+sELaS xNrD21kgLtOUWL9LH6JVUWJK90N2iLWCEidnPmGZwCg6C8nUWQgds5B0zELSsYCRZRWjaHFq cVJuupGRXmpRZnJxcX6eXl5qySZGYHwc3PLbYAfjy+eOhxgFOBiVeHgfbBOIEGJNLCuuzD3E KMHBrCTCu/whUIg3JbGyKrUoP76oNCe1+BCjNAeLkjiv2cr74UIC6YklqdmpqQWpRTBZJg5O qQbGUm9u/vcOhzly6u9LBL/sSZ250kPn+019nwUyG/5mNoslH6/J5Q99mxl548UEr9CoreuU fmkKbvC0nPPIc6Ejz+IVIQFnAn6sbHKYalRu6mwkkxX53SOp4fQV1pDzlVtShOLeyJT0aVze Kax/dde9nqAbkRc3n16/i91g+cRdJzk4tr15tq1IiaU4I9FQi7moOBEA+SpyuosCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3wM3dUtl-F2iOKbz65lwvfof7Z4>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: BUNDLE-35 - Colin's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 17:13:29 -0000

SGksDQoNCj4+PiBBbHNvLCB0aGUgWE1MIGZvcm1hdHRpbmcgaXMgbWVzc2VkIHVwIGluIHRoZSBt
aWRkbGUgb2YgdGhlIHBhcmFncmFwaC4NCj4+IA0KPj4gSXQgbG9va3Mgb2sgaW4gbXkgZWRpdG9y
IDopDQo+PiANCj4+IE9UT0gsIEkgaGF2ZSBjaGFuZ2VkIGVkaXRvciByZWNlbnRseSwgc28gdGhl
cmUgYXJlIGxvdHMgb2YgaW5zdGFuY2VzIA0KPj4gd2hlcmUgdGhlIFhNTCBkb2VzIGxvb2sgYSBs
aXR0bGUgbWVzc3kuDQo+DQo+IEkgbWVhbnQgdGhhdCB0aGUgWE1MIGNvZGVzIGFyZSBhcHBlYXJp
bmcgaW4gdGhlIHRleHQgdmVyc2lvbiBvZiB0aGUgZHJhZnQuDQoNCkFhYWgsIEkgY2FuIHRoYXQu
IEkgd2lsbCBmaXggaXQuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg==


From nobody Wed Oct 26 15:47:20 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47321129594; Wed, 26 Oct 2016 15:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sdNUIaRKYpyz; Wed, 26 Oct 2016 15:47:12 -0700 (PDT)
Received: from mail-yb0-x234.google.com (mail-yb0-x234.google.com [IPv6:2607:f8b0:4002:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E0FB129457; Wed, 26 Oct 2016 15:47:12 -0700 (PDT)
Received: by mail-yb0-x234.google.com with SMTP id f97so8942425ybi.1; Wed, 26 Oct 2016 15:47:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hQyhf/EQyfyPszl/7Ijo3RKqpPEk9NW4SlqoEAwLuPw=; b=oP7pPDzDh7xKPRtFUdsQJIlqx63V3Oq2sky8hUha+31SBuAXHoDufF/KKIW9nMU/1l bdV2DvXvqPT8B9GPd+AyCcOgvO83x+Z0ByH0hXPQIFwBDCkASWhAWNf4ZoVB69JSyMtk RgrG83eoEi2jormbOIGeeuahpGK5DLng/cz59+4Olfhs1Sclus46RW3GFcHGJ9vJ16fu kmZk1y5RbCVldC6ebLS96rT2IAEUvX3QvBKYtcRCe6TnfisXHDiLXphQ6ooqxUu0v/Ds keu12Xk5Gl2IBFnI4eh7HcMZbI22KhoKcAmU0PxPxPnLxJo0eC63/sdV2uEd3C1GE0Ht TF4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hQyhf/EQyfyPszl/7Ijo3RKqpPEk9NW4SlqoEAwLuPw=; b=iai6jWgS9iTtz0P7qyLR9W7QlcOKtjOdc1wKotX0XCIWcWsaMx2Jw74yg/6eat27iA z7/RfIsNbqByEaLy3JsZCerCWgHxgdYHpcL7H7d7NkRYf019c0hWZ244uqStIEmiHK5L yJHarGSvXUfcUmAWr+FVF01ejKSt/wAaDyd2V5nT8bmb24PNBCi8sB2wVsJB1IzqPatk IebRDcMwbkGGaojY7m4Lu6PGvAVFIju+SpgOHbqJeNAYU/yc5630GZtU2RjsUfMmjlxp cBCOytCWL7LhoJyqwtvkZD/+ErK/8LVAZXgoTGuQ4OkC3xV8VGzyqcLwBLq2ff4nR2h2 ix9A==
X-Gm-Message-State: ABUngvcADjlIMuN6aRZNW18zQd4Kch43ZOvPMOF1hzkHcfz+UO8LoIPO0OfTavoaoigiQt6U7trbXKM6aG9F4Q==
X-Received: by 10.37.171.74 with SMTP id u68mr3720560ybi.191.1477522028831; Wed, 26 Oct 2016 15:47:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.158.73 with HTTP; Wed, 26 Oct 2016 15:47:08 -0700 (PDT)
In-Reply-To: <147747540682.18851.267971327825992233.idtracker@ietfa.amsl.com>
References: <147747540682.18851.267971327825992233.idtracker@ietfa.amsl.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Wed, 26 Oct 2016 15:47:08 -0700
Message-ID: <CAMRcRGRQYoVuurAuiy9tJFcJ_Kt3fR_4Cr9oStZiWcCNdvwGog@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=94eb2c184bb8ad34c8053fcc6758
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/5k6kt7wpEt00LySRIe5LrJvp48A>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, The IESG <iesg@ietf.org>, mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Stephen Farrell's No Objection on draft-ietf-mmusic-sdp-mux-attributes-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Oct 2016 22:47:14 -0000

--94eb2c184bb8ad34c8053fcc6758
Content-Type: text/plain; charset=UTF-8

Hello Stephen

    Thanks for the review . please see inline.

On Wed, Oct 26, 2016 at 2:50 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

> Stephen Farrell has entered the following ballot position for
> draft-ietf-mmusic-sdp-mux-attributes-14: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
>
> - 4.5 and 5.7: What if the different a=crypto lines
> specify different strength ciphersuites? Wouldn't it be
> better to pick the strongest or to say they MUST be the
> same (as is done in 5.35)? If picking the first is the
> right answer then maybe warn folks to not put a stronger
> ciphersuite anywhere else?
>


[Suhas]:  I did think about it some more and I am not sure the mux draft
opens up an vulnerability in this scenario.
For example, Even with the IDENTICAL category, the Offerer can include a
weak cipher in all the m=lines and thus force the Answerer to select the
weak one or have the Answerer reject the Offer. I am not sure if making it
iDENTICAL would help us guard against the wrong cipher selection.
.
In the TRANSPORT scenario, if the Answerer selected the m=line with a weak
cipher the Offerer has 2 options a) Don't include the weak cipher b) Do
another Offer/Answer with the modified list (with strong ciphers or
inactive media)

Please advise ..




>
> - 5.36 vs. 5.39: It wasn't clear to me why these have
> different rules - can you explain?
>
>
>
[Suhas] : It looks like both the fingerprint (Section 5.36) and
zrtp-hash(5.39) attributes have the same Multiplexing category of TRANSPORT
assigned and thus follow the same rules. Am i missing something here ?


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

--94eb2c184bb8ad34c8053fcc6758
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Stephen<div><br></div><div>=C2=A0 =C2=A0 Thanks for =
the review . please see inline.</div><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On Wed, Oct 26, 2016 at 2:50 AM, Stephen Farrell <span =
dir=3D"ltr">&lt;<a href=3D"mailto:stephen.farrell@cs.tcd.ie" target=3D"_bla=
nk">stephen.farrell@cs.tcd.ie</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">Stephen Farrell has entered the following ballot position for<br=
>
draft-ietf-mmusic-sdp-mux-<wbr>attributes-14: No Objection<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss-crit=
eria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/iesg/<=
wbr>statement/discuss-criteria.<wbr>html</a><br>
for more information about IESG DISCUSS and COMMENT positions.<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attri=
butes/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<=
wbr>doc/draft-ietf-mmusic-sdp-mux-<wbr>attributes/</a><br>
<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
COMMENT:<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
<br>
- 4.5 and 5.7: What if the different a=3Dcrypto lines<br>
specify different strength ciphersuites? Wouldn&#39;t it be<br>
better to pick the strongest or to say they MUST be the<br>
same (as is done in 5.35)? If picking the first is the<br>
right answer then maybe warn folks to not put a stronger<br>
ciphersuite anywhere else?<br></blockquote><div><br></div><div><br></div><d=
iv>[Suhas]: =C2=A0I did think about it some more and I am not sure the mux =
draft opens up an vulnerability in this scenario.=C2=A0</div><div>For examp=
le, Even with the IDENTICAL category, the Offerer can include a weak cipher=
 in all the m=3Dlines and thus force the Answerer to select the weak one or=
 have the Answerer reject the Offer. I am not sure if making it iDENTICAL w=
ould help us guard against the wrong cipher selection.=C2=A0</div><div>.=C2=
=A0</div><div>In the TRANSPORT scenario, if the Answerer selected the m=3Dl=
ine with a weak cipher the Offerer has 2 options a) Don&#39;t include the w=
eak cipher b) Do another Offer/Answer with the modified list (with strong c=
iphers or inactive media)</div><div><br></div><div>Please advise ..</div><d=
iv><br></div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<br>
- 5.36 vs. 5.39: It wasn&#39;t clear to me why these have<br>
different rules - can you explain?<br>
<br>
<br></blockquote><div>=C2=A0</div><div>[Suhas] : It looks like both the fin=
gerprint (Section 5.36) and zrtp-hash(5.39) attributes have the same Multip=
lexing category of TRANSPORT assigned and thus follow the same rules. Am i =
missing something here ?</div><div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
</blockquote></div><br></div></div>

--94eb2c184bb8ad34c8053fcc6758--


From nobody Thu Oct 27 00:58:35 2016
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 889CE129C7C; Thu, 27 Oct 2016 00:58:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147755511355.18924.1327824704496199161.idtracker@ietfa.amsl.com>
Date: Thu, 27 Oct 2016 00:58:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FiVQGsxEh5jeQyyog1c_JhmHHrM>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-bundle-negotiation-36.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 27 Oct 2016 07:58:33 -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 of the IETF.

        Title           : Negotiating Media Multiplexing Using the Session Description Protocol (SDP)
        Authors         : Christer Holmberg
                          Harald Tveit Alvestrand
                          Cullen Jennings
	Filename        : draft-ietf-mmusic-sdp-bundle-negotiation-36.txt
	Pages           : 57
	Date            : 2016-10-27

Abstract:
   This specification defines a new Session Description Protocol (SDP)
   Grouping Framework extension, 'BUNDLE'.  The extension can be used
   with the SDP Offer/Answer mechanism to negotiate the usage of a
   single address:port combination (BUNDLE address) for receiving media,
   referred to as bundled media, specified by multiple SDP media
   descriptions ("m=" lines).

   To assist endpoints in negotiating the use of bundle this
   specification defines a new SDP attribute, 'bundle-only', which can
   be used to request that specific media is only used if bundled.  The
   specification also updates RFC 3264, to allow usage of zero port
   values without meaning that media is rejected.

   There are multiple ways to correlate the bundled RTP packets with the
   appropriate media descriptions.  This specification defines a new
   Real-time Transport Protocol (RTP) source description (SDES) item and
   a new RTP header extension that provides an additional way to do this
   correlation by using them to carry a value that associates the RTP/
   RTCP packets with a specific media description.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation-36

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


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

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


From nobody Thu Oct 27 01:09:59 2016
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 2AB2E12946E; Thu, 27 Oct 2016 01:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 HsKi0JI4eUnr; Thu, 27 Oct 2016 01:09:56 -0700 (PDT)
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 E9CFC12945C; Thu, 27 Oct 2016 01:09:54 -0700 (PDT)
X-AuditID: c1b4fb30-f60a598000000cb2-4e-5811b6512c05
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by  (Symantec Mail Security) with SMTP id 10.A0.03250.156B1185; Thu, 27 Oct 2016 10:09:53 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0319.002; Thu, 27 Oct 2016 10:09:51 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: BUNDLE-36
Thread-Index: AQHSMCl9Urpf/0dYeU6mGz8iokc5Nw==
Date: Thu, 27 Oct 2016 08:09:50 +0000
Message-ID: <D43792B4.11DD5%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_D43792B411DD5christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjkeLIzCtJLcpLzFFi42KZGbHdWDdwm2CEwda3whbnd65nspi6/DGL A5PHkiU/mQIYo7hsUlJzMstSi/TtErgy/v2cwlhwV7Ti2IQp7A2MS4S6GDk5JARMJLbs38DU xcjFISSwnlHi8bMNLBDOEkaJzk+HWbsYOTjYBCwkuv9pgzSICKhLfN3bwwxiMwuYSjx8tYYR xBYWUJWYePwyG0SNlsTTpgnsELaexMcpX1hAbBagmi3Nk8BqeAWsJY4v6AWrYRQQk/h+ag0T xExxiVtP5jNBHCcgsWTPeWYIW1Ti5eN/YOeIAs1ccz8MIqwosfNsO9Q5CRJfL3cyQYwXlDg5 8wnLBEbhWUimzkJSNgtJGUTcQOL9ufnMELa2xLKFr6FsfYmNX84yQtjWEnOfPGREVrOAkWMV o2hxanFSbrqRkV5qUWZycXF+nl5easkmRmAsHdzy22AH48vnjocYBTgYlXh4H2wTiBBiTSwr rsw9xCjBwawkwqu3RTBCiDclsbIqtSg/vqg0J7X4EKM0B4uSOK/ZyvvhQgLpiSWp2ampBalF MFkmDk6pBsaOlshrJ4xfpp8KCHO29Td88nfL/tcT2+fUSKRX2b17nLlI9qDmI7E7lWu9Es64 /uqe1abL3Dx75QRRe/Y/Ky5xuPEcC1K+t4ZFzvTx+3tNfQ/vVj6e9HF1wjejLM/CVZ+f7eX/ mZCZzhyfZv4/RmYCl7vM8QRPscKVj/RvSV+X2bhcPkRaMkiJpTgj0VCLuag4EQAcnJKJoQIA AA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/T1hOdjqh_7EIj3fzmcVO6dlsNbA>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
Subject: [MMUSIC] Draft new version: BUNDLE-36
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 27 Oct 2016 08:09:58 -0000

--_000_D43792B411DD5christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

Based on Colin=92s comments, I=92ve submitted a new version (-36) of draft-=
bundle.

I STRONGLY ENCOURAGE interested parties to try to solve the SDES-in-RTP-hea=
der-extension security issue, because that=92s currently the ONLY major tec=
hnical open issue in BUNDLE.

The only major editorial open issue is Ekr=92s suggestion to =93downsize=94=
 the usage of =93shared address=94. I am looking into how/if that can be do=
ne without yet another a major re-write of the document.

It was also noted that BUNDLE and JSEP use different terminology for certai=
n things, and the MMUSIC/RTCWEB chairs were asked to think about whether so=
mething needs to be done about that.

I have tried to address the comments and issues that have been raised on th=
e list, but IF someone has raised issue(s) that have not been addressed, pl=
ease indicate that ASAP. AS SOON AS POSSIBLE.

Regards,

Christer

--_000_D43792B411DD5christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <A43933E025142346A7457CB745EE5B2A@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>Based on Colin=92s comments, I=92ve submitted a new version (-36) of d=
raft-bundle.</div>
<div><br>
</div>
<div>I STRONGLY ENCOURAGE interested parties to try to solve the SDES-in-RT=
P-header-extension security issue, because that=92s currently the ONLY majo=
r technical open issue in BUNDLE.</div>
<div><br>
</div>
<div>The only major editorial open issue is Ekr=92s suggestion to =93downsi=
ze=94 the usage of =93shared address=94. I am looking into how/if that can =
be done without yet another a major re-write of the document.</div>
<div><br>
</div>
<div>It was also noted that BUNDLE and JSEP use different terminology for c=
ertain things, and the MMUSIC/RTCWEB chairs were asked to think about wheth=
er something needs to be done about that.</div>
<div><br>
</div>
<div>I have tried to address the comments and issues that have been raised =
on the list, but IF someone has raised issue(s) that have not been addresse=
d, please indicate that ASAP. AS SOON AS POSSIBLE.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer&nbsp;</div>
</body>
</html>

--_000_D43792B411DD5christerholmbergericssoncom_--


From nobody Thu Oct 27 09:03:39 2016
Return-Path: <ietf@kuehlewind.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 23CD41295FA for <mmusic@ietfa.amsl.com>; Thu, 27 Oct 2016 09:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.333
X-Spam-Level: 
X-Spam-Status: No, score=-2.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VYmZkrElFVxK for <mmusic@ietfa.amsl.com>; Thu, 27 Oct 2016 09:03:31 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22D18129643 for <mmusic@ietf.org>; Thu, 27 Oct 2016 09:03:12 -0700 (PDT)
Received: (qmail 32559 invoked from network); 27 Oct 2016 17:56:30 +0200
Received: from nb-10510.ethz.ch (HELO ?82.130.103.143?) (82.130.103.143) by kuehlewind.net with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated);  27 Oct 2016 17:56:29 +0200
To: Suhas Nandakumar <suhasietf@gmail.com>
References: <147741587672.1323.3788097761711986441.idtracker@ietfa.amsl.com> <CAMRcRGTEj-HwOvWtCi5orEKurMirOZLepG2sB1Ya7x-nJU7Pvg@mail.gmail.com>
From: =?UTF-8?Q?Mirja_K=c3=bchlewind?= <ietf@kuehlewind.net>
Message-ID: <fefa06b9-75b1-2e58-6532-1a426f7fb69f@kuehlewind.net>
Date: Thu, 27 Oct 2016 17:56:24 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGTEj-HwOvWtCi5orEKurMirOZLepG2sB1Ya7x-nJU7Pvg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/XRP8-Qo-LVxL5zsTCBLNF1y1JQ4>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, The IESG <iesg@ietf.org>, mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-mmusic-sdp-mux-attributes-14=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 27 Oct 2016 16:03:37 -0000

Hi Suhas,

see below.

On 25.10.2016 19:30, Suhas Nandakumar wrote:
> Hello Mirja ,
>
> Thanks for the review. Please see inline for the response.
>
> On Tue, Oct 25, 2016 at 10:17 AM, Mirja Kuehlewind <ietf@kuehlewind.net
> <mailto:ietf@kuehlewind.net>> wrote:
>
>     Mirja KÃ¼hlewind has entered the following ballot position for
>     draft-ietf-mmusic-sdp-mux-attributes-14: No Objection
>
>     When responding, please keep the subject line intact and reply to all
>     email addresses included in the To and CC lines. (Feel free to cut this
>     introductory paragraph, however.)
>
>
>     Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>     <https://www.ietf.org/iesg/statement/discuss-criteria.html>
>     for more information about IESG DISCUSS and COMMENT positions.
>
>
>     The document, along with other ballot positions, can be found here:
>     https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/
>     <https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/>
>
>
>
>     ----------------------------------------------------------------------
>     COMMENT:
>     ----------------------------------------------------------------------
>
>     Two comments:
>
>     1) The category TDB is not fully clear to me. It says: "The attributes in
>     the TBD category have not been analyzed", but why? Can you further
>     explain?
>
>
> [Suhas]: The category TBD serves 2 purposes.
>
> Purpose 1: The WG decided to stop draft updates with new attribute analysis
> towards the end of 2015 when it was decided to take the draft to the last
> call. This was done so to keep the draft edits under control and not to keep
> in a edit-loop forever when new SDP attributes popped up. All those
> attributes that were added since then will get the category TBD in the IANA
> registry and the individual drafts that define those attributes take on the
> role of deciding the MUX category and the corresponding IANA updates.
> An excerpt from Section 15.2 along the same lines below:
> "
>
> For the entries in the existing subregistries, under the "Session
>    Description Protocol (SDP) Parameters" registry, that lack a value
>    for the "Mux Category" in this specification will get a value of
>    "TBD"
>
> "

I'm not sure I fully get this. There are other doc that will define a 
different value which are not finished yet but the parameter is already 
registered in the registry.

I guess I just would leave those open in this doc (not saying anything about 
them) and not define an own temporal category for those.

Probably you can just have a note in the iana section saying that for these 
parameter the category will be defined by other doc and should be left open 
for now.

>
>
> Purpose 2: There are few attributes in the current analysis of the draft that
> are assigned the category TBD. A specific example is Section 5.54 (ITU T.38).
> I have included the note below to explain in the section the reasons why the
> WG decided the category as TBD.
> "
>
> NOTE: As per section 9.1 of [I-D.ietf-mmusic-sdp-bundle-negotiation],
>    there exists no publicly available specification that defines
>    procedures for multiplexing/demultiplexing fax protocols flows over a
>    single 5-tuple.  Once such a specification is available, the
>    multiplexing category assignments for the attributes in this section
>    could be revisited.
>
> "
> Since we don't have a standard specification to define the mux/demux of Fax
> protocols with RTP, the only category that made sense was TBD. This state can
> be updated once such a spec is defined in the future. Similar reasoning
> applies to other TBD attributes.
>
> Please let me know if the above answers your concerns.

Still not sure if a TBD category makes sense but don't have a strong opinion, 
so please do whatever you think is the right thing to do.

>
>
>
>
>     2) Is the new registry for the Mux Category really needed? Is it expected
>     to (much) more categories in future?
>
>
> [Suhas] -  We need the registry to list the currently defined Mux Categories
> and also we do see there might be couple of more categories (if not many)
> that might get defined in the future.

This seems really vague for me. I would assume that you actually don't need a 
registry now and if there will be more categories defined in the future 
(which doesn't seem very likely) a new doc could still define a registry and 
update this RFC.

Mirja

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


From nobody Thu Oct 27 21:29:23 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F336129455; Thu, 27 Oct 2016 21:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_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=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 eek6qrVie3Qw; Thu, 27 Oct 2016 21:29:12 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7CEE126579; Thu, 27 Oct 2016 21:29:11 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id u124so69482845ywg.3; Thu, 27 Oct 2016 21:29:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/bmniGDcYAQNBTqr17xPyEpekM9UEUzMiDfkq8w9K3Q=; b=HcoxmXQf45pims7RjoYq0j1mTx/ryQ44RdCjVVK1BN/i7txE77xcIYfi4hUypLhWlr mBb/2LNe7TKdSKQZfpe25zWrtRXgz98IgJj7FBLVxV/AKEMldeSN9Jd4aNKqZuiKnd9A N9dKfSGoQGNhvgE2uJ4KOO4gOfZ6HOdWn2RopcFvYEG4DsZTXyXVgFd45OqyqR+c6SIo DAIU6fOzmaIM0mUlm8IYWFFJ5vkXx8uomzZ4jU/DedYqhqEceZjShTjwPsRxS1szLtq6 zwHtSvmlLEy/IzcP4LjHx/6+APVhOjum/YBPNP5OZODV8gNiaOeXb3pIk7vFja3ecIL2 c7Mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/bmniGDcYAQNBTqr17xPyEpekM9UEUzMiDfkq8w9K3Q=; b=BwNw9I+GjHx7W8A3PnJNyd8Avd6o/s8J3BN8Y4iU1dJ3jnX9c6brOiNauHXDAbEoVs FrVv2rQe2/3RJecZhXx2CZJN2lAVsSRshZbbg93U5urtasn2eBt+CtKiweF61Pg34DzZ wkGFU7oXH5/jElchoSnPjNAm6SDx1ZGIOEHBH188yGj2UO0W24zrp/k1bO+Dm8jzWKf4 B0mOtxXf2RVAB1QSuRq9s3ANePdF5qBUm+0tEWcuBaB0T4/qQAbLWlTGULK1Nov0NtkC 9EUiuldfMnKhPV26njO3vRhNbQfZYC+MNj9Syczgr2NxYNoorlVAO50hVKqGNb7p+Pbw onvg==
X-Gm-Message-State: ABUngvcuDG4pDztx6QH5TT6ClO3ZURGCbbl2BIjqhbhOCZPqrtRg/zk3gEaOTKHe9SZeN+ZLJIDwJgQp/lTsIQ==
X-Received: by 10.13.195.4 with SMTP id f4mr10057669ywd.249.1477628951013; Thu, 27 Oct 2016 21:29:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.158.73 with HTTP; Thu, 27 Oct 2016 21:29:10 -0700 (PDT)
In-Reply-To: <fefa06b9-75b1-2e58-6532-1a426f7fb69f@kuehlewind.net>
References: <147741587672.1323.3788097761711986441.idtracker@ietfa.amsl.com> <CAMRcRGTEj-HwOvWtCi5orEKurMirOZLepG2sB1Ya7x-nJU7Pvg@mail.gmail.com> <fefa06b9-75b1-2e58-6532-1a426f7fb69f@kuehlewind.net>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Thu, 27 Oct 2016 21:29:10 -0700
Message-ID: <CAMRcRGSmRLEPNjjSnPv_X3-HRNMq8vbDOzQtvXqB7RazrdHuVQ@mail.gmail.com>
To: =?UTF-8?Q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
Content-Type: multipart/alternative; boundary=001a114daeb4bc2bfb053fe54cb2
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/nwTljxpfk0GtMYKMy4ANSNpiTs0>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, The IESG <iesg@ietf.org>, mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-mmusic-sdp-mux-attributes-14=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 04:29:14 -0000

--001a114daeb4bc2bfb053fe54cb2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello Mirja

 Thanks for the responses. Please see inline.

Cheers
Suhas

On Thu, Oct 27, 2016 at 8:56 AM, Mirja K=C3=BChlewind <ietf@kuehlewind.net>
wrote:

> Hi Suhas,
>
> see below.
>
> On 25.10.2016 19:30, Suhas Nandakumar wrote:
>
>> Hello Mirja ,
>>
>> Thanks for the review. Please see inline for the response.
>>
>> On Tue, Oct 25, 2016 at 10:17 AM, Mirja Kuehlewind <ietf@kuehlewind.net
>> <mailto:ietf@kuehlewind.net>> wrote:
>>
>>     Mirja K=C3=BChlewind has entered the following ballot position for
>>     draft-ietf-mmusic-sdp-mux-attributes-14: No Objection
>>
>>     When responding, please keep the subject line intact and reply to al=
l
>>     email addresses included in the To and CC lines. (Feel free to cut
>> this
>>     introductory paragraph, however.)
>>
>>
>>     Please refer to https://www.ietf.org/iesg/stat
>> ement/discuss-criteria.html
>>     <https://www.ietf.org/iesg/statement/discuss-criteria.html>
>>     for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>>     The document, along with other ballot positions, can be found here:
>>     https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-a
>> ttributes/
>>     <https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-
>> attributes/>
>>
>>
>>
>>     ------------------------------------------------------------
>> ----------
>>     COMMENT:
>>     ------------------------------------------------------------
>> ----------
>>
>>     Two comments:
>>
>>     1) The category TDB is not fully clear to me. It says: "The
>> attributes in
>>     the TBD category have not been analyzed", but why? Can you further
>>     explain?
>>
>>
>> [Suhas]: The category TBD serves 2 purposes.
>>
>> Purpose 1: The WG decided to stop draft updates with new attribute
>> analysis
>> towards the end of 2015 when it was decided to take the draft to the las=
t
>> call. This was done so to keep the draft edits under control and not to
>> keep
>> in a edit-loop forever when new SDP attributes popped up. All those
>> attributes that were added since then will get the category TBD in the
>> IANA
>> registry and the individual drafts that define those attributes take on
>> the
>> role of deciding the MUX category and the corresponding IANA updates.
>> An excerpt from Section 15.2 along the same lines below:
>> "
>>
>> For the entries in the existing subregistries, under the "Session
>>    Description Protocol (SDP) Parameters" registry, that lack a value
>>    for the "Mux Category" in this specification will get a value of
>>    "TBD"
>>
>> "
>>
>
> I'm not sure I fully get this. There are other doc that will define a
> different value which are not finished yet but the parameter is already
> registered in the registry.
>
> I guess I just would leave those open in this doc (not saying anything
> about them) and not define an own temporal category for those.
>
> Probably you can just have a note in the iana section saying that for
> these parameter the category will be defined by other doc and should be
> left open for now.
>
>
>>
>> Purpose 2: There are few attributes in the current analysis of the draft
>> that
>> are assigned the category TBD. A specific example is Section 5.54 (ITU
>> T.38).
>> I have included the note below to explain in the section the reasons why
>> the
>> WG decided the category as TBD.
>> "
>>
>> NOTE: As per section 9.1 of [I-D.ietf-mmusic-sdp-bundle-negotiation],
>>    there exists no publicly available specification that defines
>>    procedures for multiplexing/demultiplexing fax protocols flows over a
>>    single 5-tuple.  Once such a specification is available, the
>>    multiplexing category assignments for the attributes in this section
>>    could be revisited.
>>
>> "
>> Since we don't have a standard specification to define the mux/demux of
>> Fax
>> protocols with RTP, the only category that made sense was TBD. This stat=
e
>> can
>> be updated once such a spec is defined in the future. Similar reasoning
>> applies to other TBD attributes.
>>
>> Please let me know if the above answers your concerns.
>>
>
> Still not sure if a TBD category makes sense but don't have a strong
> opinion, so please do whatever you think is the right thing to do.
>
>

[Suhas]: Since we had WG consensus on the TBD category for the attributes
that are not analyzed by this draft and for those lacking publicly
available specification, I am inclined to leave those as is.


>
>>
>>
>>
>>     2) Is the new registry for the Mux Category really needed? Is it
>> expected
>>     to (much) more categories in future?
>>
>>
>> [Suhas] -  We need the registry to list the currently defined Mux
>> Categories
>> and also we do see there might be couple of more categories (if not many=
)
>> that might get defined in the future.
>>
>
> This seems really vague for me. I would assume that you actually don't
> need a registry now and if there will be more categories defined in the
> future (which doesn't seem very likely) a new doc could still define a
> registry and update this RFC.
>
>

[Suhas]
 Section 15.2 and its sub-sections assign the multiplexing categories  to
several of the sub-registries in the IANA SDP Parameters registry. This is
done by adding a new column called 'Mux Category' to each of the
sub-registries in the SDP Parameters registry.
Having a registry defined to identify the names of these Multiplexing
categories ( as in Section 15.1) will ensure there is a formal place for
these names and formal rules to expand the category set in the future.



> Mirja
>
>
>>
>>
>>
>>     _______________________________________________
>>     mmusic mailing list
>>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/mmusic
>>     <https://www.ietf.org/mailman/listinfo/mmusic>
>>
>>
>>

--001a114daeb4bc2bfb053fe54cb2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Mirja<div><br></div><div>=C2=A0Thanks for the respon=
ses. Please see inline.</div><div><br></div><div>Cheers</div><div>Suhas</di=
v><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Oct 27,=
 2016 at 8:56 AM, Mirja K=C3=BChlewind <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:ietf@kuehlewind.net" target=3D"_blank">ietf@kuehlewind.net</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">Hi Suhas,<br>
<br>
see below.<span class=3D""><br>
<br>
On 25.10.2016 19:30, Suhas Nandakumar wrote:<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><span class=3D"">
Hello Mirja ,<br>
<br>
Thanks for the review. Please see inline for the response.<br>
<br>
On Tue, Oct 25, 2016 at 10:17 AM, Mirja Kuehlewind &lt;<a href=3D"mailto:ie=
tf@kuehlewind.net" target=3D"_blank">ietf@kuehlewind.net</a><br></span><div=
><div class=3D"h5">
&lt;mailto:<a href=3D"mailto:ietf@kuehlewind.net" target=3D"_blank">ietf@ku=
ehlewind.net</a>&gt;&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 Mirja K=C3=BChlewind has entered the following ballot positio=
n for<br>
=C2=A0 =C2=A0 draft-ietf-mmusic-sdp-mux-attr<wbr>ibutes-14: No Objection<br=
>
<br>
=C2=A0 =C2=A0 When responding, please keep the subject line intact and repl=
y to all<br>
=C2=A0 =C2=A0 email addresses included in the To and CC lines. (Feel free t=
o cut this<br>
=C2=A0 =C2=A0 introductory paragraph, however.)<br>
<br>
<br>
=C2=A0 =C2=A0 Please refer to <a href=3D"https://www.ietf.org/iesg/statemen=
t/discuss-criteria.html" rel=3D"noreferrer" target=3D"_blank">https://www.i=
etf.org/iesg/stat<wbr>ement/discuss-criteria.html</a><br>
=C2=A0 =C2=A0 &lt;<a href=3D"https://www.ietf.org/iesg/statement/discuss-cr=
iteria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/iesg=
/sta<wbr>tement/discuss-criteria.html</a>&gt;<br>
=C2=A0 =C2=A0 for more information about IESG DISCUSS and COMMENT positions=
.<br>
<br>
<br>
=C2=A0 =C2=A0 The document, along with other ballot positions, can be found=
 here:<br>
=C2=A0 =C2=A0 <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic=
-sdp-mux-attributes/" rel=3D"noreferrer" target=3D"_blank">https://datatrac=
ker.ietf.org/d<wbr>oc/draft-ietf-mmusic-sdp-mux-a<wbr>ttributes/</a><br>
=C2=A0 =C2=A0 &lt;<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mm=
usic-sdp-mux-attributes/" rel=3D"noreferrer" target=3D"_blank">https://data=
tracker.ietf.org/<wbr>doc/draft-ietf-mmusic-sdp-mux-<wbr>attributes/</a>&gt=
;<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 ------------------------------<wbr>--------------------------=
----<wbr>----------<br>
=C2=A0 =C2=A0 COMMENT:<br>
=C2=A0 =C2=A0 ------------------------------<wbr>--------------------------=
----<wbr>----------<br>
<br>
=C2=A0 =C2=A0 Two comments:<br>
<br>
=C2=A0 =C2=A0 1) The category TDB is not fully clear to me. It says: &quot;=
The attributes in<br>
=C2=A0 =C2=A0 the TBD category have not been analyzed&quot;, but why? Can y=
ou further<br>
=C2=A0 =C2=A0 explain?<br>
<br>
<br>
[Suhas]: The category TBD serves 2 purposes.<br>
<br>
Purpose 1: The WG decided to stop draft updates with new attribute analysis=
<br>
towards the end of 2015 when it was decided to take the draft to the last<b=
r>
call. This was done so to keep the draft edits under control and not to kee=
p<br>
in a edit-loop forever when new SDP attributes popped up. All those<br>
attributes that were added since then will get the category TBD in the IANA=
<br>
registry and the individual drafts that define those attributes take on the=
<br>
role of deciding the MUX category and the corresponding IANA updates.<br>
An excerpt from Section 15.2 along the same lines below:<br>
&quot;<br>
<br>
For the entries in the existing subregistries, under the &quot;Session<br>
=C2=A0 =C2=A0Description Protocol (SDP) Parameters&quot; registry, that lac=
k a value<br>
=C2=A0 =C2=A0for the &quot;Mux Category&quot; in this specification will ge=
t a value of<br>
=C2=A0 =C2=A0&quot;TBD&quot;<br>
<br>
&quot;<br>
</div></div></blockquote>
<br>
I&#39;m not sure I fully get this. There are other doc that will define a d=
ifferent value which are not finished yet but the parameter is already regi=
stered in the registry.<br>
<br>
I guess I just would leave those open in this doc (not saying anything abou=
t them) and not define an own temporal category for those.<br>
<br>
Probably you can just have a note in the iana section saying that for these=
 parameter the category will be defined by other doc and should be left ope=
n for now.<span class=3D""><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
Purpose 2: There are few attributes in the current analysis of the draft th=
at<br>
are assigned the category TBD. A specific example is Section 5.54 (ITU T.38=
).<br>
I have included the note below to explain in the section the reasons why th=
e<br>
WG decided the category as TBD.<br>
&quot;<br>
<br>
NOTE: As per section 9.1 of [I-D.ietf-mmusic-sdp-bundle-ne<wbr>gotiation],<=
br>
=C2=A0 =C2=A0there exists no publicly available specification that defines<=
br>
=C2=A0 =C2=A0procedures for multiplexing/demultiplexing fax protocols flows=
 over a<br>
=C2=A0 =C2=A0single 5-tuple.=C2=A0 Once such a specification is available, =
the<br>
=C2=A0 =C2=A0multiplexing category assignments for the attributes in this s=
ection<br>
=C2=A0 =C2=A0could be revisited.<br>
<br>
&quot;<br>
Since we don&#39;t have a standard specification to define the mux/demux of=
 Fax<br>
protocols with RTP, the only category that made sense was TBD. This state c=
an<br>
be updated once such a spec is defined in the future. Similar reasoning<br>
applies to other TBD attributes.<br>
<br>
Please let me know if the above answers your concerns.<br>
</blockquote>
<br></span>
Still not sure if a TBD category makes sense but don&#39;t have a strong op=
inion, so please do whatever you think is the right thing to do.<span class=
=3D""><br>
<br></span></blockquote><div><br></div><div><br></div><div><font color=3D"#=
0000ff">[Suhas]: Since we had WG consensus on the TBD category for the attr=
ibutes that are not analyzed by this draft and for those lacking publicly a=
vailable specification, I am inclined to leave those as is.</font></div><di=
v>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 2) Is the new registry for the Mux Category really needed? Is=
 it expected<br>
=C2=A0 =C2=A0 to (much) more categories in future?<br>
<br>
<br>
[Suhas] -=C2=A0 We need the registry to list the currently defined Mux Cate=
gories<br>
and also we do see there might be couple of more categories (if not many)<b=
r>
that might get defined in the future.<br>
</blockquote>
<br></span>
This seems really vague for me. I would assume that you actually don&#39;t =
need a registry now and if there will be more categories defined in the fut=
ure (which doesn&#39;t seem very likely) a new doc could still define a reg=
istry and update this RFC.<br>
<br></blockquote><div><br></div><div><br></div><div><font color=3D"#0000ff"=
>[Suhas]</font></div><div><font color=3D"#0000ff">=C2=A0Section 15.2 and it=
s sub-sections assign the multiplexing categories =C2=A0to several of the s=
ub-registries in the IANA SDP Parameters registry. This is done by adding a=
 new column called &#39;Mux Category&#39; to each of the sub-registries in =
the SDP Parameters registry.</font></div><div><font color=3D"#0000ff">Havin=
g a registry defined to identify the names of these Multiplexing categories=
 ( as in Section 15.1) will ensure there is a formal place for these names =
and formal rules to expand the category set in the future.</font></div><div=
><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Mirja<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 ______________________________<wbr>_________________<br>
=C2=A0 =C2=A0 mmusic mailing list<br>
=C2=A0 =C2=A0 <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@i=
etf.org</a> &lt;mailto:<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank"=
>mmusic@ietf.org</a>&gt;<br>
=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinf=
o/mmusic</a><br>
=C2=A0 =C2=A0 &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>list=
info/mmusic</a>&gt;<br>
<br>
<br>
</blockquote>
</blockquote></div><br></div></div>

--001a114daeb4bc2bfb053fe54cb2--


From nobody Thu Oct 27 22:11:45 2016
Return-Path: <martin.thomson@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 7AB351295F8; Thu, 27 Oct 2016 22:11:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 psYoGt7k3kVO; Thu, 27 Oct 2016 22:11:43 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (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 DFD84129503; Thu, 27 Oct 2016 22:11:42 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id 12so38205586qtm.3; Thu, 27 Oct 2016 22:11:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4LkEWtD+2E9FOdn3mWY0IOBzNirtX4haWCKkXiHQLA8=; b=Ar08Fk8k8EkPqSZpgkCO498fmTKZMyLY4+MGQ+I9S0C01Zi4KVYr9zVak7TvizFd1l TwtdpKhsimi5+OjsLQzcI4Mgfdy8eKLLSY2f26Guf1poSSE57IvZzAh76f7W4kLAkvHM 1vha15ZsccJ6kLwsoUT5e0XHozc6epUptLDlvXfv9z8ivWFmmbMD3kxNWp5OJ5kZQA+t 3wbKPdAAjLAX5nQfOx1RsiZUZ0qh2deXeHRz8ThbRljrQomA6JMdsy6PoNcd0XPlKB3m BPfXdq8TVnuQdHB/08Dn0Qfjmbi27r+vNy1rHFQimSC7k0R9YdmJiVWlhUNLLZYxwlif jBiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4LkEWtD+2E9FOdn3mWY0IOBzNirtX4haWCKkXiHQLA8=; b=heiiVAdkjGesfKx6jf1hxlHJ6oiC+Tgdj5xjxVwp4Jbyewvsu41OJfM+OrL58Mgr+s cplDuporDkYq58a/6cZxf/lYDJaCgPZJhPCdh3vY47RzjB4qd0dYqcDvGMlF5/yXDZqw TRNeS0zIgOIVDRyAtF18UmxbMt9nDuDQK9LHIiW6ByMNA1pWtobubqdz9XhNZoBrx7Ac QeMinAxaek4Cgt/k3wqIykv9k2z3+/LWvfjzNzsNd0mM1nYCNkQb0ZpqO/p59PgRRjMY tQdK3SbH/kjjpD3cvLaNNPUvsJu5HXh2raiRG1nOqWSv7qs+AJqOr9shd2NrSBn9Tw7m FKug==
X-Gm-Message-State: ABUngvfYx479qw/zactKq5koqKsNwojv9WCl/rVmAm5uRA9zloS3uKQCiFolA8moMnLLs8qz0K7iVXy3emWw/A==
X-Received: by 10.200.34.66 with SMTP id p2mr9661205qtp.107.1477631502081; Thu, 27 Oct 2016 22:11:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.85.7 with HTTP; Thu, 27 Oct 2016 22:11:41 -0700 (PDT)
In-Reply-To: <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 28 Oct 2016 16:11:41 +1100
Message-ID: <CABkgnnV7yU8Y1YhDSmm5hSbFSoVLhXvDnKOAs1otmnyf0s5RHw@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/mjR3lvTMvoz-HA-3A6YW-f_Mjp8>
Cc: Ben Campbell <ben@nostrum.com>, mmusic <mmusic@ietf.org>, ART ADs <art-ads@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 05:11:44 -0000

On 26 October 2016 at 15:54, Flemming Andreasen <fandreas@cisco.com> wrote:
> A Doodle poll is now available at
>
>         http://doodle.com/poll/kxw4n9a2v7v3pe2y
>
> We are looking at either Wednesday or Friday next week (November 2 or 4), so
> please get your vote in pretty quickly if you are interested.

These are awful times for me, though I would like to be involved.
It's not that long now until we will all be in the same room, is this
somehow urgent enough that we need to have a call?


From nobody Thu Oct 27 22:19:29 2016
Return-Path: <ekr@rtfm.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 53745129610 for <mmusic@ietfa.amsl.com>; Thu, 27 Oct 2016 22:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CrhH3XjJgYEU for <mmusic@ietfa.amsl.com>; Thu, 27 Oct 2016 22:19:25 -0700 (PDT)
Received: from mail-yb0-x22f.google.com (mail-yb0-x22f.google.com [IPv6:2607:f8b0:4002:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AECC129455 for <mmusic@ietf.org>; Thu, 27 Oct 2016 22:19:25 -0700 (PDT)
Received: by mail-yb0-x22f.google.com with SMTP id f97so31847275ybi.1 for <mmusic@ietf.org>; Thu, 27 Oct 2016 22:19:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KMweL7MKDQUtGx046Gb3KczIn2we1Hg4wLsrghAvl7c=; b=Hs5z3mzk/ab0CU/q8RlI9u9R5MeV4TTbpoWiNREgwBEV/gd1qBGlx6MdRGZTlJDMb+ nEgYK7hxq55uepnRrWGgXP7U/GqLTu1s5MB20r8xVqoF7ot63D+BYk10Rh8sOyvoRJJ/ lMN8/MDunDGY6ZinEP++kXivZKfQ/SrY0lIuEz5aiiCpdVVNFdqCZ3eojvTU61/QNYti iMSl3BMZH5ElpS7tU+JoK4sWz9rPjSGsDaisdmeIeH86Xyu0EabUOhRrlDGuAKdQddyz Kvr2fXUdPDnSIc28YkTwkyG0V2beUoIIgPAejoT+ND4zXmB0PGjJRYICKk4dBLBiiIo6 26eQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KMweL7MKDQUtGx046Gb3KczIn2we1Hg4wLsrghAvl7c=; b=Gah2LooJVVXBaXswCaQHHqVRyMXyNUV1qFQmDO0UBEEioWHFiKRibIvDp7fKwJgv7c RYcyK3CNUB/jhc9XsyFvM7zCx/H0nRZBGKstYDoZv26VHwiPTeC+FzHgpKyzUb+dL4uv YB0pRVXvXqmxDToIGroiwXhbmav1P+75Ow923/xKMV2avuRFAN/aq+og9Neyzp7EmxBl Ik4nRPu9kcsegToVFKmqdPqF6LJjSPwYxxOuiWOWd0rKgYVa0C+MF1DeYgfuZn55I8we ZaOzuetciCc3nplbnl+thI+eKH9favLAvkKL979fsuvsC0W8Iwv3bvbaBL7JQJgytYy0 jYhw==
X-Gm-Message-State: ABUngveGEsrqvkC7MV7sH6F17RUFvaqKXS9wmAgIuMV/eunpAuEdONTh/8U2xwvZMtiiFoFhj8/3LkGS4gDqJA==
X-Received: by 10.37.204.73 with SMTP id l70mr11247560ybf.161.1477631964928; Thu, 27 Oct 2016 22:19:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.82.210 with HTTP; Thu, 27 Oct 2016 22:18:44 -0700 (PDT)
In-Reply-To: <CABkgnnV7yU8Y1YhDSmm5hSbFSoVLhXvDnKOAs1otmnyf0s5RHw@mail.gmail.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com> <CABkgnnV7yU8Y1YhDSmm5hSbFSoVLhXvDnKOAs1otmnyf0s5RHw@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 28 Oct 2016 16:18:44 +1100
Message-ID: <CABcZeBMFeCkAxOaTPaMZytLmNpbprja5tF5D7RHrejSihN508Q@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c07f302613071053fe6001c
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/LtavE21kcPUeC_FokjlBiOI8exw>
Cc: Ben Campbell <ben@nostrum.com>, mmusic <mmusic@ietf.org>, ART ADs <art-ads@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 05:19:27 -0000

--94eb2c07f302613071053fe6001c
Content-Type: text/plain; charset=UTF-8

Dealing with this in Seoul seems like a reasonable suggestion

-Ekr


On Fri, Oct 28, 2016 at 4:11 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 26 October 2016 at 15:54, Flemming Andreasen <fandreas@cisco.com>
> wrote:
> > A Doodle poll is now available at
> >
> >         http://doodle.com/poll/kxw4n9a2v7v3pe2y
> >
> > We are looking at either Wednesday or Friday next week (November 2 or
> 4), so
> > please get your vote in pretty quickly if you are interested.
>
> These are awful times for me, though I would like to be involved.
> It's not that long now until we will all be in the same room, is this
> somehow urgent enough that we need to have a call?
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--94eb2c07f302613071053fe6001c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dealing with this in Seoul seems like a reasonable suggest=
ion<div><br></div><div>-Ekr</div><div><br></div></div><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote">On Fri, Oct 28, 2016 at 4:11 PM, Marti=
n Thomson <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.thomson@gmail.com"=
 target=3D"_blank">martin.thomson@gmail.com</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><span class=3D"">On 26 October 2016 at 15:54, Flem=
ming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com">fandreas@cisco.com=
</a>&gt; wrote:<br>
&gt; A Doodle poll is now available at<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://doodle.com/poll/kxw=
4n9a2v7v3pe2y" rel=3D"noreferrer" target=3D"_blank">http://doodle.com/poll/=
<wbr>kxw4n9a2v7v3pe2y</a><br>
&gt;<br>
&gt; We are looking at either Wednesday or Friday next week (November 2 or =
4), so<br>
&gt; please get your vote in pretty quickly if you are interested.<br>
<br>
</span>These are awful times for me, though I would like to be involved.<br=
>
It&#39;s not that long now until we will all be in the same room, is this<b=
r>
somehow urgent enough that we need to have a call?<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div>

--94eb2c07f302613071053fe6001c--


From nobody Fri Oct 28 01:32:25 2016
Return-Path: <ietf@kuehlewind.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 328B21295C9 for <mmusic@ietfa.amsl.com>; Fri, 28 Oct 2016 01:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.333
X-Spam-Level: 
X-Spam-Status: No, score=-2.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xVS9Zv40abgq for <mmusic@ietfa.amsl.com>; Fri, 28 Oct 2016 01:32:23 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 163CA12945C for <mmusic@ietf.org>; Fri, 28 Oct 2016 01:32:22 -0700 (PDT)
Received: (qmail 3340 invoked from network); 28 Oct 2016 10:24:58 +0200
Received: from nb-10510.ethz.ch (HELO ?82.130.103.143?) (82.130.103.143) by kuehlewind.net with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated);  28 Oct 2016 10:24:57 +0200
To: Suhas Nandakumar <suhasietf@gmail.com>
References: <147741587672.1323.3788097761711986441.idtracker@ietfa.amsl.com> <CAMRcRGTEj-HwOvWtCi5orEKurMirOZLepG2sB1Ya7x-nJU7Pvg@mail.gmail.com> <fefa06b9-75b1-2e58-6532-1a426f7fb69f@kuehlewind.net> <CAMRcRGSmRLEPNjjSnPv_X3-HRNMq8vbDOzQtvXqB7RazrdHuVQ@mail.gmail.com>
From: =?UTF-8?Q?Mirja_K=c3=bchlewind?= <ietf@kuehlewind.net>
Message-ID: <e7f7e348-895a-ec12-6b9f-a673b7c9c7b4@kuehlewind.net>
Date: Fri, 28 Oct 2016 10:24:52 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGSmRLEPNjjSnPv_X3-HRNMq8vbDOzQtvXqB7RazrdHuVQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/_Zt2ABVIxVTRI8SlypwMRE_6V9c>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, The IESG <iesg@ietf.org>, mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-mmusic-sdp-mux-attributes-14=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 08:32:24 -0000

Hi Suhas,

see below.

On 28.10.2016 06:29, Suhas Nandakumar wrote:
 >
 >             2) Is the new registry for the Mux Category really needed? Is it
 >         expected
 >             to (much) more categories in future?
 >
 >
 >         [Suhas] -  We need the registry to list the currently defined Mux
 >         Categories
 >         and also we do see there might be couple of more categories (if 
not many)
 >         that might get defined in the future.
 >
 >
 >     This seems really vague for me. I would assume that you actually don't
 >     need a registry now and if there will be more categories defined in the
 >     future (which doesn't seem very likely) a new doc could still define a
 >     registry and update this RFC.
 >
 >
 >
 > [Suhas]
 >  Section 15.2 and its sub-sections assign the multiplexing categories  to
 > several of the sub-registries in the IANA SDP Parameters registry. This is
 > done by adding a new column called 'Mux Category' to each of the
 > sub-registries in the SDP Parameters registry.
 > Having a registry defined to identify the names of these Multiplexing
 > categories ( as in Section 15.1) will ensure there is a formal place for
 > these names and formal rules to expand the category set in the future.

The formal place where these categories are explained is this RFC. This RFC 
could also talk about the opportunity or even process to expand this list in 
future. However, as long as it is not clear that any expansion will be really 
needed in future, I don't see a need for e registry.

That's my view point. Please consult your AD for final advise.

Mirja


From nobody Fri Oct 28 02:39:56 2016
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 E5F3F12943B; Fri, 28 Oct 2016 02:39:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E2Z79fPjX9gb; Fri, 28 Oct 2016 02:39:53 -0700 (PDT)
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 2D937129412; Fri, 28 Oct 2016 02:39:53 -0700 (PDT)
X-AuditID: c1b4fb30-b73ff70000000cb2-5d-58131ce564bd
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by  (Symantec Mail Security) with SMTP id D6.22.03250.5EC13185; Fri, 28 Oct 2016 11:39:51 +0200 (CEST)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.75) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 28 Oct 2016 11:39:49 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=mVi4ose2oGE6K1zN51EeuuuKx1YFHpGqd4s6wFWNtIo=; b=eDaNc/vNL12rkyWkx8SzZKASiQLoYunCKCz1+yGs22bvdhS3b622KOq/KgeqpDW6+phE4idOwQ+hbl6ExcPvT1XvJO/nffmge1g+twwno7z1GJuTvvJmA5Wi+m4ECG5okY/WUy2JcgZIdKcymTEr79c22/hMRxb+Dmzjw86Uye0=
Received: from AM5PR0701MB2577.eurprd07.prod.outlook.com (10.173.92.21) by AM5PR0701MB2577.eurprd07.prod.outlook.com (10.173.92.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.707.1; Fri, 28 Oct 2016 09:39:48 +0000
Received: from AM5PR0701MB2577.eurprd07.prod.outlook.com ([10.173.92.21]) by AM5PR0701MB2577.eurprd07.prod.outlook.com ([10.173.92.21]) with mapi id 15.01.0707.002; Fri, 28 Oct 2016 09:39:48 +0000
From: Bo Burman <bo.burman@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>, Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
Thread-Index: AQHSMNnZRxmfsHkjIUqaQdD7yF53LqC9U80AgABH9SA=
Date: Fri, 28 Oct 2016 09:39:48 +0000
Message-ID: <AM5PR0701MB2577F7A1A473CE2D5866365B8DAD0@AM5PR0701MB2577.eurprd07.prod.outlook.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com> <CABkgnnV7yU8Y1YhDSmm5hSbFSoVLhXvDnKOAs1otmnyf0s5RHw@mail.gmail.com> <CABcZeBMFeCkAxOaTPaMZytLmNpbprja5tF5D7RHrejSihN508Q@mail.gmail.com>
In-Reply-To: <CABcZeBMFeCkAxOaTPaMZytLmNpbprja5tF5D7RHrejSihN508Q@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=bo.burman@ericsson.com; 
x-originating-ip: [115.110.136.4]
x-ld-processed: 92e84ceb-fbfd-47ab-be52-080c6b87953f,ExtAddr
x-ms-office365-filtering-correlation-id: 8b72d52d-98d0-4afe-dd00-08d3ff165c15
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB2577; 7:iH2lE+0Bf3pvX+iIbStTSyS3c+4ft6RpBUi3IH58P+PF9+GvfPlYulOPL6q9BmWPC5V/suMlfOX+JhrR4cmouAVgMLWhVL8NouCTqFmvUMNyReZHPesJequrjzyPXWmXitrSOsmRC330JjaBPXN4S4pmq7bUH+WxPxFQGou7czST1qUiah2fVAH1TKTHtMhH+xWngZ3whRFvU3ixX47uxAHCHXs9P/V1ePBaW3L+qxKsro+XCUHfBOyXEBu2mqZbAvjmHYgTpKoZQZwcWocfJ/vFNfGPqlvGiKXZgQ5psUfSQjTWDD7XGvHbjUsV/KVe6OYU60KvVgL7trIfR9TP3UEteTdNv6yG91gidKa3rJE=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM5PR0701MB2577;
x-microsoft-antispam-prvs: <AM5PR0701MB25779E89C645F01925F15C488DAD0@AM5PR0701MB2577.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(60409825278598)(100405760836317)(95692535739014)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046);  SRVR:AM5PR0701MB2577; BCL:0; PCL:0; RULEID:; SRVR:AM5PR0701MB2577; 
x-forefront-prvs: 0109D382B0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(24454002)(199003)(377454003)(189002)(11100500001)(4001430100002)(101416001)(74316002)(93886004)(92566002)(5002640100001)(7846002)(50986999)(77096005)(15975445007)(2950100002)(7736002)(7906003)(10400500002)(3280700002)(76176999)(54356999)(8676002)(81156014)(2420400007)(81166006)(33656002)(2900100001)(7110500001)(5001770100001)(107886002)(189998001)(16236675004)(19300405004)(19625215002)(76576001)(15395725005)(97736004)(19617315012)(86362001)(19580395003)(19580405001)(15650500001)(66066001)(106356001)(105586002)(106116001)(68736007)(5660300001)(4326007)(10710500007)(2906002)(7696004)(19609705001)(87936001)(8936002)(9686002)(3846002)(6116002)(790700001)(586003)(3660700001)(102836003)(122556002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM5PR0701MB2577; H:AM5PR0701MB2577.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM5PR0701MB2577F7A1A473CE2D5866365B8DAD0AM5PR0701MB2577_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Oct 2016 09:39:48.6970 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2577
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Se0hTYRjG+XbOdo7W6Gub+ubMctCVUjOLEaO0og6JYH85I9BlJ5O8tWOi VmChkrPAW5rLpsjILsu1YWjmHykRXiuKZlmmc96GiQlqF9FyOwv87/e+z/O8fA98NCHpF/rT yWmZrDZNk6IQeZPV6uao3RMBUnXoolOqtIyVk8raoh5K+WDqDaWcebdb+cP8CyltvctIebvB QUZQTMWiRcg81w9SjNH4W8B8eDuLGP3zUZIpdxQSMaJT3qqzbEpyFqsNOZjgfb55bI7MqIzO vvninSgP5UfpkBcNOBwc9k5Kh7xpCTYj+DhsRi5BgjsR3J1f4xJIfIuA2Wt2Ee+qEoB1sswz rLiW5vpIV0SEt0Nty6A7LsNR8MrQ6L5L4AEEn/Q2wjVIcTUCx5KTdA0yrEcw1TMt4iMH4G9r j5tJvAWcda/dZ8U4AUoNFRT/KqsAih4n6BBNe+GTMPOScK0R9oWf3SaBiwnsBwOjtQK+HQZj 21uCZx9wOpaFvD8Oykv7KH4fBG/ajB6PCu4UV3k4Gix/LO4GgOsJaHxZiniBgdn6cSHP6dBU fd+zvwx5X/M9gTYEprIPnksBYHDWkLyQT8HAjSYh34aFhicFqATt1K96Oc/p8N3a62YxXg9d 1aOkfqU0gXeAuTWEtwRBRbGd4nk7FNTco1bv6xD1CPlwLHcmNSksLJjVJidyXHpacBqbaUUr 3629aTG0BTknIjsQppFirTiBlqglQk0Wl5PagYAmFDLxIblULRGf1eTkstr0eO2lFJbrQHKa VPiJ9z8cipXgJE0me4FlM1jtf1VAe/nnIfPnkzNi2fx1/aaQQbm0pDPCFnPxhN2QPTchT7my sW7B9xn3zTC14WpLc9evoKWWoYVISxwUMu2nr6qKO61l3e/3DVZuOxxZZDMdy1J9MdkC/UeO 9wfbJXT49EDqw7oA0dPJ7NbNxLnc+MJGNRMYd1QFZ4aPbF23ayR8fG9sok5Bcuc1e3YSWk7z D8gXBjBqAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wr1TLRXjamlGjkMSbqhjOLeW9zc>
Cc: Ben Campbell <ben@nostrum.com>, mmusic <mmusic@ietf.org>, ART ADs <art-ads@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 09:39:56 -0000

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

VGhpcyBpcyBkZWZpbml0ZWx5IHBvc3NpYmxlIOKAkyBNTVVTSUMgU2VvdWwgYWdlbmRhIGlzIG5v
dCBzZXQgaW4gc3RvbmUsIGJ1dCBwbGVhc2UgYmUgYXdhcmUgdGhhdCB0aGUgc2luZ2xlIE1NVVNJ
QyBzZXNzaW9uIGlzIG9ubHkgYW4gaG91ciBpbiB0b3RhbC4NCi9Cbw0KTU1VU0lDIGNvLWNoYWly
DQoNCkZyb206IG1tdXNpYyBbbWFpbHRvOm1tdXNpYy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhh
bGYgT2YgRXJpYyBSZXNjb3JsYQ0KU2VudDogZGVuIDI4IG9rdG9iZXIgMjAxNiAxMDo0OQ0KVG86
IE1hcnRpbiBUaG9tc29uIDxtYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20+DQpDYzogQmVuIENhbXBi
ZWxsIDxiZW5Abm9zdHJ1bS5jb20+OyBtbXVzaWMgPG1tdXNpY0BpZXRmLm9yZz47IEFSVCBBRHMg
PGFydC1hZHNAaWV0Zi5vcmc+OyBGbGVtbWluZyBBbmRyZWFzZW4gPGZhbmRyZWFzQGNpc2NvLmNv
bT47IEN1bGxlbiBKZW5uaW5ncyA8Zmx1ZmZ5QGlpaS5jYT47IENocmlzdGVyIEhvbG1iZXJnIDxj
aHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+DQpTdWJqZWN0OiBSZTogW01NVVNJQ10gRG9v
ZGxlIHBvbGwgW1JlOiBNb3ZpbmcgRm9yd2FyZCBvbiA0NTcyLXVwZGF0ZSAod2FzIFJlOiBSb3Vn
aCBjb25jZW5zdXM6IFJlOiA0NTcyLXVwZGF0ZTogQ29uc2Vuc3VzIGNhbGwgb24gaG93IHRvIG1v
dmUgZm9yd2FyZCldDQoNCkRlYWxpbmcgd2l0aCB0aGlzIGluIFNlb3VsIHNlZW1zIGxpa2UgYSBy
ZWFzb25hYmxlIHN1Z2dlc3Rpb24NCg0KLUVrcg0KDQoNCk9uIEZyaSwgT2N0IDI4LCAyMDE2IGF0
IDQ6MTEgUE0sIE1hcnRpbiBUaG9tc29uIDxtYXJ0aW4udGhvbXNvbkBnbWFpbC5jb208bWFpbHRv
Om1hcnRpbi50aG9tc29uQGdtYWlsLmNvbT4+IHdyb3RlOg0KT24gMjYgT2N0b2JlciAyMDE2IGF0
IDE1OjU0LCBGbGVtbWluZyBBbmRyZWFzZW4gPGZhbmRyZWFzQGNpc2NvLmNvbTxtYWlsdG86ZmFu
ZHJlYXNAY2lzY28uY29tPj4gd3JvdGU6DQo+IEEgRG9vZGxlIHBvbGwgaXMgbm93IGF2YWlsYWJs
ZSBhdA0KPg0KPiAgICAgICAgIGh0dHA6Ly9kb29kbGUuY29tL3BvbGwva3h3NG45YTJ2N3YzcGUy
eQ0KPg0KPiBXZSBhcmUgbG9va2luZyBhdCBlaXRoZXIgV2VkbmVzZGF5IG9yIEZyaWRheSBuZXh0
IHdlZWsgKE5vdmVtYmVyIDIgb3IgNCksIHNvDQo+IHBsZWFzZSBnZXQgeW91ciB2b3RlIGluIHBy
ZXR0eSBxdWlja2x5IGlmIHlvdSBhcmUgaW50ZXJlc3RlZC4NCg0KVGhlc2UgYXJlIGF3ZnVsIHRp
bWVzIGZvciBtZSwgdGhvdWdoIEkgd291bGQgbGlrZSB0byBiZSBpbnZvbHZlZC4NCkl0J3Mgbm90
IHRoYXQgbG9uZyBub3cgdW50aWwgd2Ugd2lsbCBhbGwgYmUgaW4gdGhlIHNhbWUgcm9vbSwgaXMg
dGhpcw0Kc29tZWhvdyB1cmdlbnQgZW5vdWdoIHRoYXQgd2UgbmVlZCB0byBoYXZlIGEgY2FsbD8N
Cg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1tdXNp
YyBtYWlsaW5nIGxpc3QNCm1tdXNpY0BpZXRmLm9yZzxtYWlsdG86bW11c2ljQGlldGYub3JnPg0K
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1z
b25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCglt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBjbTsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4
DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNv
LXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2Vy
aWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdp
bjo3MC44NXB0IDcwLjg1cHQgNzAuODVwdCA3MC44NXB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7
cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4N
CjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48
IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0
PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5
b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9
ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+VGhpcyBpcyBkZWZpbml0ZWx5IHBvc3Np
YmxlIOKAkyBNTVVTSUMgU2VvdWwgYWdlbmRhIGlzIG5vdCBzZXQgaW4gc3RvbmUsIGJ1dCBwbGVh
c2UgYmUgYXdhcmUgdGhhdCB0aGUgc2luZ2xlIE1NVVNJQyBzZXNzaW9uIGlzIG9ubHkgYW4gaG91
ciBpbiB0b3RhbC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWYiPi9CbzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZiI+TU1VU0lDIGNvLWNoYWlyPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xp
ZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMu
MHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
ZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IG1tdXNpYyBbbWFpbHRvOm1tdXNp
Yy1ib3VuY2VzQGlldGYub3JnXQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5FcmljIFJlc2NvcmxhPGJy
Pg0KPGI+U2VudDo8L2I+IGRlbiAyOCBva3RvYmVyIDIwMTYgMTA6NDk8YnI+DQo8Yj5Ubzo8L2I+
IE1hcnRpbiBUaG9tc29uICZsdDttYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+
Q2M6PC9iPiBCZW4gQ2FtcGJlbGwgJmx0O2JlbkBub3N0cnVtLmNvbSZndDs7IG1tdXNpYyAmbHQ7
bW11c2ljQGlldGYub3JnJmd0OzsgQVJUIEFEcyAmbHQ7YXJ0LWFkc0BpZXRmLm9yZyZndDs7IEZs
ZW1taW5nIEFuZHJlYXNlbiAmbHQ7ZmFuZHJlYXNAY2lzY28uY29tJmd0OzsgQ3VsbGVuIEplbm5p
bmdzICZsdDtmbHVmZnlAaWlpLmNhJmd0OzsgQ2hyaXN0ZXIgSG9sbWJlcmcgJmx0O2NocmlzdGVy
LmhvbG1iZXJnQGVyaWNzc29uLmNvbSZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtNTVVT
SUNdIERvb2RsZSBwb2xsIFtSZTogTW92aW5nIEZvcndhcmQgb24gNDU3Mi11cGRhdGUgKHdhcyBS
ZTogUm91Z2ggY29uY2Vuc3VzOiBSZTogNDU3Mi11cGRhdGU6IENvbnNlbnN1cyBjYWxsIG9uIGhv
dyB0byBtb3ZlIGZvcndhcmQpXTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5EZWFsaW5nIHdpdGggdGhpcyBpbiBTZW91bCBzZWVtcyBsaWtlIGEg
cmVhc29uYWJsZSBzdWdnZXN0aW9uPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj4tRWtyPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+T24gRnJpLCBPY3QgMjgsIDIwMTYgYXQgNDoxMSBQTSwgTWFydGluIFRo
b21zb24gJmx0OzxhIGhyZWY9Im1haWx0bzptYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20iIHRhcmdl
dD0iX2JsYW5rIj5tYXJ0aW4udGhvbXNvbkBnbWFpbC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwv
bzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xp
ZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44
cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiAyNiBPY3RvYmVy
IDIwMTYgYXQgMTU6NTQsIEZsZW1taW5nIEFuZHJlYXNlbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmZh
bmRyZWFzQGNpc2NvLmNvbSI+ZmFuZHJlYXNAY2lzY28uY29tPC9hPiZndDsgd3JvdGU6PGJyPg0K
Jmd0OyBBIERvb2RsZSBwb2xsIGlzIG5vdyBhdmFpbGFibGUgYXQ8YnI+DQomZ3Q7PGJyPg0KJmd0
OyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDs8YSBocmVmPSJodHRwOi8vZG9vZGxl
LmNvbS9wb2xsL2t4dzRuOWEydjd2M3BlMnkiIHRhcmdldD0iX2JsYW5rIj5odHRwOi8vZG9vZGxl
LmNvbS9wb2xsL2t4dzRuOWEydjd2M3BlMnk8L2E+PGJyPg0KJmd0Ozxicj4NCiZndDsgV2UgYXJl
IGxvb2tpbmcgYXQgZWl0aGVyIFdlZG5lc2RheSBvciBGcmlkYXkgbmV4dCB3ZWVrIChOb3ZlbWJl
ciAyIG9yIDQpLCBzbzxicj4NCiZndDsgcGxlYXNlIGdldCB5b3VyIHZvdGUgaW4gcHJldHR5IHF1
aWNrbHkgaWYgeW91IGFyZSBpbnRlcmVzdGVkLjxicj4NCjxicj4NClRoZXNlIGFyZSBhd2Z1bCB0
aW1lcyBmb3IgbWUsIHRob3VnaCBJIHdvdWxkIGxpa2UgdG8gYmUgaW52b2x2ZWQuPGJyPg0KSXQn
cyBub3QgdGhhdCBsb25nIG5vdyB1bnRpbCB3ZSB3aWxsIGFsbCBiZSBpbiB0aGUgc2FtZSByb29t
LCBpcyB0aGlzPGJyPg0Kc29tZWhvdyB1cmdlbnQgZW5vdWdoIHRoYXQgd2UgbmVlZCB0byBoYXZl
IGEgY2FsbD88bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PGJyPg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188
YnI+DQptbXVzaWMgbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOm1tdXNpY0BpZXRm
Lm9yZyI+bW11c2ljQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWM8L2E+PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwv
aHRtbD4NCg==

--_000_AM5PR0701MB2577F7A1A473CE2D5866365B8DAD0AM5PR0701MB2577_--


From nobody Fri Oct 28 06:23:27 2016
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 CAF20129517; Fri, 28 Oct 2016 06:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 bQRYHIQ_Bo0y; Fri, 28 Oct 2016 06:23:24 -0700 (PDT)
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 D54C31294F9; Fri, 28 Oct 2016 06:23:22 -0700 (PDT)
X-AuditID: c1b4fb3a-18c55980000078c6-71-581351489da0
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by  (Symantec Mail Security) with SMTP id AC.11.30918.84153185; Fri, 28 Oct 2016 15:23:21 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0319.002; Fri, 28 Oct 2016 15:23:17 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Bo Burman <bo.burman@ericsson.com>, Eric Rescorla <ekr@rtfm.com>, "Martin Thomson" <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
Thread-Index: AQHSMNnG/C24dxYqrUukZJjBpwhGbKC9MkYAgABI8QCAAHLIgA==
Date: Fri, 28 Oct 2016 13:23:16 +0000
Message-ID: <D4392BDB.120E1%christer.holmberg@ericsson.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com> <CABkgnnV7yU8Y1YhDSmm5hSbFSoVLhXvDnKOAs1otmnyf0s5RHw@mail.gmail.com> <CABcZeBMFeCkAxOaTPaMZytLmNpbprja5tF5D7RHrejSihN508Q@mail.gmail.com> <AM5PR0701MB2577F7A1A473CE2D5866365B8DAD0@AM5PR0701MB2577.eurprd07.prod.outlook.com>
In-Reply-To: <AM5PR0701MB2577F7A1A473CE2D5866365B8DAD0@AM5PR0701MB2577.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.9.160926
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_D4392BDB120E1christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFIsWRmVeSWpSXmKPExsUyM2K7tK5noHCEwdNZLBYbn05msZjfeZrd YsXrc+wW7y/oWnxY/4PR4tqZf4wWU5c/ZnFg95jyeyOrx85Zd9k9liz5yeRx+fxHRo9ZO5+w eEx+3MYcwBbFZZOSmpNZllqkb5fAldH29AZTwduoiitL1rM1MPYHdDFyckgImEismryZsYuR i0NIYD2jxJ9LF6CcJYwSx6//BXI4ONgELCS6/2mDNIgIFEtcvr2DBaSGWWAZo8SEW/OYQBxh gZmMEn/vX2MGcUQEZjFKTFnUyQ7R4iTxcV0TO8gkFgFVidXrY0DCvALWEodefGOD2NbJLNF9 /gcLSIJTIFFi0qENbCA2o4CYxPdTa5hAbGYBcYlbT+YzQdwtILFkz3lmCFtU4uXjf6wg80UF 9CTW3A+DCCtJ/NhwiQWiNUHi2cPnbBB7BSVOznzCMoFRdBaSqbOQlM1CUgYRN5B4f24+M4St LbFs4WsoW19i45ezjBC2tcTr0yeYkNUsYORYxShanFpcnJtuZKSXWpSZXFycn6eXl1qyiREY 4we3/LbawXjwueMhRgEORiUe3gQOoQgh1sSy4srcQ4wSHMxKIrws/sIRQrwpiZVVqUX58UWl OanFhxilOViUxHnNVt4PFxJITyxJzU5NLUgtgskycXBKNTDO0v04J71yYm9VX4Ns2C6HCWEP lizLMJQXuuHhJ804P+e8VudMUyWV+R7VMacCM9u8Wq06EmUTssK2hJ+XTfyyY/9Gvcmx6w6v k9ZZrhD86fx2iZ+/LJ7nOnosstbs27Jz17Vfj3RMVxcsNT77MrSjTTKnMbnNM5K/5+saQyuG s/eXaL9llFViKc5INNRiLipOBAA93SaF7QIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/cO1ZVG-g4kIEYd8QTgXDuf_4LEI>
Cc: Flemming Andreasen <fandreas@cisco.com>, Ben Campbell <ben@nostrum.com>, ART ADs <art-ads@ietf.org>, mmusic <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 13:23:26 -0000

--_000_D4392BDB120E1christerholmbergericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

Keep in mind that this would most likely not be a thing where the presenter=
 (me, I assume) shows a slide that people the comment on. It would mostly b=
e a =93behind the microphone argume=85 eeeh.. discussion=94 between a few p=
eople, so I wonder whether the WG session is the best place to discuss this=
.

Regards,

Christer

From: Bo Burman <bo.burman@ericsson.com<mailto:bo.burman@ericsson.com>>
Date: Friday 28 October 2016 at 12:39
To: Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtfm.com>>, Martin Thomson <mart=
in.thomson@gmail.com<mailto:martin.thomson@gmail.com>>
Cc: Ben Campbell <ben@nostrum.com<mailto:ben@nostrum.com>>, "mmusic@ietf.or=
g<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusic@ietf.org>>, ART A=
Ds <art-ads@ietf.org<mailto:art-ads@ietf.org>>, Flemming Andreasen <fandrea=
s@cisco.com<mailto:fandreas@cisco.com>>, Cullen Jennings <fluffy@iii.ca<mai=
lto:fluffy@iii.ca>>, Christer Holmberg <christer.holmberg@ericsson.com<mail=
to:christer.holmberg@ericsson.com>>
Subject: RE: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was R=
e: Rough concensus: Re: 4572-update: Consensus call on how to move forward)=
]

This is definitely possible =96 MMUSIC Seoul agenda is not set in stone, bu=
t please be aware that the single MMUSIC session is only an hour in total.
/Bo
MMUSIC co-chair

From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Eric Rescorla
Sent: den 28 oktober 2016 10:49
To: Martin Thomson <martin.thomson@gmail.com<mailto:martin.thomson@gmail.co=
m>>
Cc: Ben Campbell <ben@nostrum.com<mailto:ben@nostrum.com>>; mmusic <mmusic@=
ietf.org<mailto:mmusic@ietf.org>>; ART ADs <art-ads@ietf.org<mailto:art-ads=
@ietf.org>>; Flemming Andreasen <fandreas@cisco.com<mailto:fandreas@cisco.c=
om>>; Cullen Jennings <fluffy@iii.ca<mailto:fluffy@iii.ca>>; Christer Holmb=
erg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was R=
e: Rough concensus: Re: 4572-update: Consensus call on how to move forward)=
]

Dealing with this in Seoul seems like a reasonable suggestion

-Ekr


On Fri, Oct 28, 2016 at 4:11 PM, Martin Thomson <martin.thomson@gmail.com<m=
ailto:martin.thomson@gmail.com>> wrote:
On 26 October 2016 at 15:54, Flemming Andreasen <fandreas@cisco.com<mailto:=
fandreas@cisco.com>> wrote:
> A Doodle poll is now available at
>
>         http://doodle.com/poll/kxw4n9a2v7v3pe2y
>
> We are looking at either Wednesday or Friday next week (November 2 or 4),=
 so
> please get your vote in pretty quickly if you are interested.

These are awful times for me, though I would like to be involved.
It's not that long now until we will all be in the same room, is this
somehow urgent enough that we need to have a call?

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


--_000_D4392BDB120E1christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <C841D881B437A245BCA0EF67BB2C80B7@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>Keep in mind that this would most likely not be a thing where the pres=
enter (me, I assume) shows a slide that people the comment on. It would mos=
tly be a =93behind the microphone argume=85 eeeh.. discussion=94 between a =
few people, so I wonder whether the WG
 session is the best place to discuss this.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Bo Burman &lt;<a href=3D"mail=
to:bo.burman@ericsson.com">bo.burman@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday 28 October 2016 at 12:=
39<br>
<span style=3D"font-weight:bold">To: </span>Eric Rescorla &lt;<a href=3D"ma=
ilto:ekr@rtfm.com">ekr@rtfm.com</a>&gt;, Martin Thomson &lt;<a href=3D"mail=
to:martin.thomson@gmail.com">martin.thomson@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>Ben Campbell &lt;<a href=3D"mai=
lto:ben@nostrum.com">ben@nostrum.com</a>&gt;, &quot;<a href=3D"mailto:mmusi=
c@ietf.org">mmusic@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org=
">mmusic@ietf.org</a>&gt;, ART ADs &lt;<a href=3D"mailto:art-ads@ietf.org">=
art-ads@ietf.org</a>&gt;,
 Flemming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com">fandreas@cisc=
o.com</a>&gt;, Cullen Jennings &lt;<a href=3D"mailto:fluffy@iii.ca">fluffy@=
iii.ca</a>&gt;, Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@e=
ricsson.com">christer.holmberg@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: [MMUSIC] Doodle poll [=
Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update=
: Consensus call on how to move forward)]<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">This is definitely possible =96 MMUSIC Seoul agenda=
 is not set in stone, but please be aware that the single MMUSIC session is=
 only an hour in total.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">/Bo<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">MMUSIC co-chair<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> mmusic [<a href=3D"mailto:mmus=
ic-bounces@ietf.org">mailto:mmusic-bounces@ietf.org</a>]
<b>On Behalf Of </b>Eric Rescorla<br>
<b>Sent:</b> den 28 oktober 2016 10:49<br>
<b>To:</b> Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com">m=
artin.thomson@gmail.com</a>&gt;<br>
<b>Cc:</b> Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com">ben@nostrum.=
com</a>&gt;; mmusic &lt;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org<=
/a>&gt;; ART ADs &lt;<a href=3D"mailto:art-ads@ietf.org">art-ads@ietf.org</=
a>&gt;; Flemming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com">fandre=
as@cisco.com</a>&gt;;
 Cullen Jennings &lt;<a href=3D"mailto:fluffy@iii.ca">fluffy@iii.ca</a>&gt;=
; Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">c=
hrister.holmberg@ericsson.com</a>&gt;<br>
<b>Subject:</b> Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update=
 (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move f=
orward)]<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Dealing with this in Seoul seems like a reasonable s=
uggestion<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">-Ekr<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Fri, Oct 28, 2016 at 4:11 PM, Martin Thomson &lt;=
<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomso=
n@gmail.com</a>&gt; wrote:<o:p></o:p></p>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal">On 26 October 2016 at 15:54, Flemming Andreasen &lt;=
<a href=3D"mailto:fandreas@cisco.com">fandreas@cisco.com</a>&gt; wrote:<br>
&gt; A Doodle poll is now available at<br>
&gt;<br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"http://doodle.com/poll/kxw=
4n9a2v7v3pe2y" target=3D"_blank">http://doodle.com/poll/kxw4n9a2v7v3pe2y</a=
><br>
&gt;<br>
&gt; We are looking at either Wednesday or Friday next week (November 2 or =
4), so<br>
&gt; please get your vote in pretty quickly if you are interested.<br>
<br>
These are awful times for me, though I would like to be involved.<br>
It's not that long now until we will all be in the same room, is this<br>
somehow urgent enough that we need to have a call?<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D4392BDB120E1christerholmbergericssoncom_--


From nobody Fri Oct 28 06:43:40 2016
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 C1F1B12961D for <mmusic@ietfa.amsl.com>; Fri, 28 Oct 2016 06:43:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 0OfoLnQp5xcL for <mmusic@ietfa.amsl.com>; Fri, 28 Oct 2016 06:43:33 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (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 F11F51294E3 for <mmusic@ietf.org>; Fri, 28 Oct 2016 06:43:28 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id p16so36228913qta.0 for <mmusic@ietf.org>; Fri, 28 Oct 2016 06:43:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=nRTbaV5oi1cZXPX4hAjGB9YukmH6zMBk43XfXO6lQis=; b=T7FKJADb5e2kO5EhbpweSS0OxWwVqLXHV+bsMxSGZPUxdc/ek618uYBT/qvpUmv3OU fZKO2VObrqYDzisncSsBR2aOBtlKWoDL7r8NsGy8tQb3pow4s8PQD0TDCVyfj87xnbPy n0LUV42G/ymbr4iQOQ+J9/fsrg/TXxE2REf8AWCaeQ8BQgko8QREK0M9s6hpqvW1chcV cmFaM68B/ydLesYqm2GgBRTLFNu3PFDAATx6Uyk+fyRWMPDc9hpTHEqZFaowkZfsiWao PpHUduDOpZog7hbEhivIGBcpUZtEZtf1JN4Vt5317e86beGgLaWc1wuYyW8FaffbhqPX zCmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=nRTbaV5oi1cZXPX4hAjGB9YukmH6zMBk43XfXO6lQis=; b=hRp1ZxZ+zHKQrrS8nSOJUj5m4AD+rqm0h9UA8mLTbWc3PehjNNSm1G0sZ7ofM5azv8 tQQB25RMIOkZlstAGJy0c3IEp9ef8tXA8ZzoCE4D4Niyir44EbChYbhvDBd5NSJPpvyy p6AwRjV18vQbnl/M4skfRJ0fRNLigPT5uHNJIBvbeLeg63USNPZ41+7wnOdd4RnGllCF P6aKog9fuTYjj3cFTnaxXoGjOQ/FCiGBqWCLYcMc0JAKxc4EK2oJiogR9yUsgEaE/xuP MmmKTpTLB9zYxGlPAd6XGuhkloQWTvkuQeZD34C2t7IUb6YhqKSy50TuMlLUcjX1metr 5jlQ==
X-Gm-Message-State: ABUngvc+A8qR1rsxQUoEs0xRNR+js8lqfvf8FSrZXOS+DbYgzVTwnEET+tg153Ung9XquA==
X-Received: by 10.200.35.117 with SMTP id b50mr11566672qtb.38.1477662208053; Fri, 28 Oct 2016 06:43:28 -0700 (PDT)
Received: from mail-qk0-f180.google.com (mail-qk0-f180.google.com. [209.85.220.180]) by smtp.gmail.com with ESMTPSA id o34sm6235728qto.48.2016.10.28.06.43.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Oct 2016 06:43:27 -0700 (PDT)
Received: by mail-qk0-f180.google.com with SMTP id x11so38429449qka.1; Fri, 28 Oct 2016 06:43:27 -0700 (PDT)
X-Received: by 10.55.47.193 with SMTP id v184mr10373769qkh.259.1477662207447;  Fri, 28 Oct 2016 06:43:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.132.161 with HTTP; Fri, 28 Oct 2016 06:43:26 -0700 (PDT)
In-Reply-To: <D4392BDB.120E1%christer.holmberg@ericsson.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com> <CABkgnnV7yU8Y1YhDSmm5hSbFSoVLhXvDnKOAs1otmnyf0s5RHw@mail.gmail.com> <CABcZeBMFeCkAxOaTPaMZytLmNpbprja5tF5D7RHrejSihN508Q@mail.gmail.com> <AM5PR0701MB2577F7A1A473CE2D5866365B8DAD0@AM5PR0701MB2577.eurprd07.prod.outlook.com> <D4392BDB.120E1%christer.holmberg@ericsson.com>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 28 Oct 2016 09:43:26 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsY7+ZHtGJeX7YG=BBYTj4PxEBmgopGQ6u7Hrj2EEgT_Q@mail.gmail.com>
Message-ID: <CAD5OKxsY7+ZHtGJeX7YG=BBYTj4PxEBmgopGQ6u7Hrj2EEgT_Q@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c092094f939f3053fed0ad1
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/rKWip1E5lG6NLSCLpVecehsqrqY>
Cc: Ben Campbell <ben@nostrum.com>, mmusic <mmusic@ietf.org>, ART ADs <art-ads@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 13:43:39 -0000

--94eb2c092094f939f3053fed0ad1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

In general, the two opposing champions are Cullen (asking not to update the
required hash algorithm) and Martin (who asked to make SHA-256 the
requirement in the first place).

Can I suggest two of them to have a call and see if one can convince the
other? The group had its consensus call, but based on my discussion with
Christer, the draft authors do not particularly care either way regarding
mandatory hash function selection issue. If Martin and Cullen can agree on
the way forward regarding this, they can bring the result to the group and
I am sure we will accommodate it. If they cannot reach an agreement, then
we can look at other ways to resolve it.

Please note, that Chirster and I do feel strongly that the new draft should
be considered an update to RFC 4572, since it clarifies the multiple
fingerprint related issues. I do believe any of the 4572 implementations
should be compliant with the new draft in order to avoid interop issues.

Regards,

_____________
Roman Shpount

On Fri, Oct 28, 2016 at 9:23 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> Keep in mind that this would most likely not be a thing where the
> presenter (me, I assume) shows a slide that people the comment on. It wou=
ld
> mostly be a =E2=80=9Cbehind the microphone argume=E2=80=A6 eeeh.. discuss=
ion=E2=80=9D between a few
> people, so I wonder whether the WG session is the best place to discuss
> this.
>
> Regards,
>
> Christer
>
> From: Bo Burman <bo.burman@ericsson.com>
> Date: Friday 28 October 2016 at 12:39
> To: Eric Rescorla <ekr@rtfm.com>, Martin Thomson <martin.thomson@gmail.co=
m
> >
> Cc: Ben Campbell <ben@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>,
> ART ADs <art-ads@ietf.org>, Flemming Andreasen <fandreas@cisco.com>,
> Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <
> christer.holmberg@ericsson.com>
> Subject: RE: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was
> Re: Rough concensus: Re: 4572-update: Consensus call on how to move
> forward)]
>
> This is definitely possible =E2=80=93 MMUSIC Seoul agenda is not set in s=
tone, but
> please be aware that the single MMUSIC session is only an hour in total.
>
> /Bo
>
> MMUSIC co-chair
>
>
>
> *From:* mmusic [mailto:mmusic-bounces@ietf.org <mmusic-bounces@ietf.org>]=
 *On
> Behalf Of *Eric Rescorla
> *Sent:* den 28 oktober 2016 10:49
> *To:* Martin Thomson <martin.thomson@gmail.com>
> *Cc:* Ben Campbell <ben@nostrum.com>; mmusic <mmusic@ietf.org>; ART ADs <
> art-ads@ietf.org>; Flemming Andreasen <fandreas@cisco.com>; Cullen
> Jennings <fluffy@iii.ca>; Christer Holmberg <christer.holmberg@ericsson.
> com>
> *Subject:* Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update
> (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move
> forward)]
>
>
>
> Dealing with this in Seoul seems like a reasonable suggestion
>
>
>
> -Ekr
>
>
>
>
>
> On Fri, Oct 28, 2016 at 4:11 PM, Martin Thomson <martin.thomson@gmail.com=
>
> wrote:
>
> On 26 October 2016 at 15:54, Flemming Andreasen <fandreas@cisco.com>
> wrote:
> > A Doodle poll is now available at
> >
> >         http://doodle.com/poll/kxw4n9a2v7v3pe2y
> >
> > We are looking at either Wednesday or Friday next week (November 2 or
> 4), so
> > please get your vote in pretty quickly if you are interested.
>
> These are awful times for me, though I would like to be involved.
> It's not that long now until we will all be in the same room, is this
> somehow urgent enough that we need to have a call?
>
>
> _______________________________________________
> 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
>
>

--94eb2c092094f939f3053fed0ad1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">In general, the two opposing champions are Cullen (asking =
not to update the required hash algorithm) and Martin (who asked to make SH=
A-256 the requirement in the first place).<div><br><div>Can I suggest two o=
f them to have a call and see if one can convince the other? The group had =
its consensus call, but based on my discussion with Christer, the draft aut=
hors do not particularly care either way regarding mandatory hash function =
selection issue. If Martin and Cullen can agree on the way forward regardin=
g this, they can bring the result to the group and I am sure we will accomm=
odate it. If they cannot reach an agreement, then we can look at other ways=
 to resolve it.</div></div><div><br></div><div>Please note, that Chirster a=
nd I do feel strongly that the new draft should be considered an update to =
RFC 4572, since it clarifies the multiple fingerprint related issues. I do =
believe any of the 4572 implementations should be compliant with the new dr=
aft in order to avoid interop issues.</div><div><br></div><div>Regards,=C2=
=A0</div></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature">_____________<br>Ro=
man Shpount</div></div>
<br><div class=3D"gmail_quote">On Fri, Oct 28, 2016 at 9:23 AM, Christer Ho=
lmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.c=
om" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div>Hi,</div>
<div><br>
</div>
<div>Keep in mind that this would most likely not be a thing where the pres=
enter (me, I assume) shows a slide that people the comment on. It would mos=
tly be a =E2=80=9Cbehind the microphone argume=E2=80=A6 eeeh.. discussion=
=E2=80=9D between a few people, so I wonder whether the WG
 session is the best place to discuss this.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"m_1653414446714316750OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri;font-size:11pt;text-align:left;color:blac=
k;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADD=
ING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:me=
dium none;PADDING-TOP:3pt">
<span style=3D"font-weight:bold">From: </span>Bo Burman &lt;<a href=3D"mail=
to:bo.burman@ericsson.com" target=3D"_blank">bo.burman@ericsson.com</a>&gt;=
<br>
<span style=3D"font-weight:bold">Date: </span>Friday 28 October 2016 at 12:=
39<br>
<span style=3D"font-weight:bold">To: </span>Eric Rescorla &lt;<a href=3D"ma=
ilto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt;, Martin Thomson &=
lt;<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.tho=
mson@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>Ben Campbell &lt;<a href=3D"mai=
lto:ben@nostrum.com" target=3D"_blank">ben@nostrum.com</a>&gt;, &quot;<a hr=
ef=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a>&quot; &=
lt;<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a>=
&gt;, ART ADs &lt;<a href=3D"mailto:art-ads@ietf.org" target=3D"_blank">art=
-ads@ietf.org</a>&gt;,
 Flemming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_bl=
ank">fandreas@cisco.com</a>&gt;, Cullen Jennings &lt;<a href=3D"mailto:fluf=
fy@iii.ca" target=3D"_blank">fluffy@iii.ca</a>&gt;, Christer Holmberg &lt;<=
a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christer=
.holmberg@ericsson.<wbr>com</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: [MMUSIC] Doodle poll [=
Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update=
: Consensus call on how to move forward)]<br>
</div><div><div class=3D"h5">
<div><br>
</div>
<div>


<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_1653414446714316750WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">This is definitely possible =E2=80=93 MMUSIC Seoul =
agenda is not set in stone, but please be aware that the single MMUSIC sess=
ion is only an hour in total.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">/Bo<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">MMUSIC co-chair<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> mmusic [<a href=3D"mailto:mmus=
ic-bounces@ietf.org" target=3D"_blank">mailto:mmusic-bounces@ietf.<wbr>org<=
/a>]
<b>On Behalf Of </b>Eric Rescorla<br>
<b>Sent:</b> den 28 oktober 2016 10:49<br>
<b>To:</b> Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com" t=
arget=3D"_blank">martin.thomson@gmail.com</a>&gt;<br>
<b>Cc:</b> Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_b=
lank">ben@nostrum.com</a>&gt;; mmusic &lt;<a href=3D"mailto:mmusic@ietf.org=
" target=3D"_blank">mmusic@ietf.org</a>&gt;; ART ADs &lt;<a href=3D"mailto:=
art-ads@ietf.org" target=3D"_blank">art-ads@ietf.org</a>&gt;; Flemming Andr=
easen &lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank">fandreas@=
cisco.com</a>&gt;;
 Cullen Jennings &lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank">flu=
ffy@iii.ca</a>&gt;; Christer Holmberg &lt;<a href=3D"mailto:christer.holmbe=
rg@ericsson.com" target=3D"_blank">christer.holmberg@ericsson.<wbr>com</a>&=
gt;<br>
<b>Subject:</b> Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update=
 (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move f=
orward)]<u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Dealing with this in Seoul seems like a reasonable s=
uggestion<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-Ekr<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Fri, Oct 28, 2016 at 4:11 PM, Martin Thomson &lt;=
<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomso=
n@gmail.com</a>&gt; wrote:<u></u><u></u></p>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal">On 26 October 2016 at 15:54, Flemming Andreasen &lt;=
<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank">fandreas@cisco.com<=
/a>&gt; wrote:<br>
&gt; A Doodle poll is now available at<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://doodle.com/poll/kxw=
4n9a2v7v3pe2y" target=3D"_blank">http://doodle.com/poll/<wbr>kxw4n9a2v7v3pe=
2y</a><br>
&gt;<br>
&gt; We are looking at either Wednesday or Friday next week (November 2 or =
4), so<br>
&gt; please get your vote in pretty quickly if you are interested.<br>
<br>
These are awful times for me, though I would like to be involved.<br>
It&#39;s not that long now until we will all be in the same room, is this<b=
r>
somehow urgent enough that we need to have a call?<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><u></u><u></u></p>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div>
</div>
</div></div></span>
</div>

<br>______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
<br></blockquote></div><br></div>

--94eb2c092094f939f3053fed0ad1--


From nobody Fri Oct 28 07:44:14 2016
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 6520E129B09; Fri, 28 Oct 2016 07:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.331
X-Spam-Level: 
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] 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 md40tl0jAi-D; Fri, 28 Oct 2016 07:44:07 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CB71129B01; Fri, 28 Oct 2016 07:44:07 -0700 (PDT)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u9SEhvNI020582 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 28 Oct 2016 09:43:58 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: "Ben Campbell" <ben@nostrum.com>
To: "Roman Shpount" <roman@telurix.com>
Date: Fri, 28 Oct 2016 09:43:57 -0500
Message-ID: <E95B34C4-91EA-41FC-9EAC-D59C77A33C12@nostrum.com>
In-Reply-To: <CAD5OKxsY7+ZHtGJeX7YG=BBYTj4PxEBmgopGQ6u7Hrj2EEgT_Q@mail.gmail.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com> <CABkgnnV7yU8Y1YhDSmm5hSbFSoVLhXvDnKOAs1otmnyf0s5RHw@mail.gmail.com> <CABcZeBMFeCkAxOaTPaMZytLmNpbprja5tF5D7RHrejSihN508Q@mail.gmail.com> <AM5PR0701MB2577F7A1A473CE2D5866365B8DAD0@AM5PR0701MB2577.eurprd07.prod.outlook.com> <D4392BDB.120E1%christer.holmberg@ericsson.com> <CAD5OKxsY7+ZHtGJeX7YG=BBYTj4PxEBmgopGQ6u7Hrj2EEgT_Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5263)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/aJkzys8Fewsn1-NsflyT5doMUvQ>
Cc: Flemming Andreasen <fandreas@cisco.com>, ART ADs <art-ads@ietf.org>, mmusic <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 14:44:14 -0000

On 28 Oct 2016, at 8:43, Roman Shpount wrote:

> In general, the two opposing champions are Cullen (asking not to 
> update the
> required hash algorithm) and Martin (who asked to make SHA-256 the
> requirement in the first place).

If Martin is critical to this conversation, then the conversation should 
wait for him. But I agree with Christer that this is likely to be a 
behind-the-mike discussion. I half expect that to end with "interested 
parties please gather for a side meeting."

The point being: If a group call cannot happen prior to Seoul, then I 
strongly suggest interested parties arrange a side meeting there _prior_ 
to the MMUSIC meeting (currently scheduled Wednesday morning).

(I understand the AD is somewhat frustrated over the draft being stuck 
on this point ;-)  )


>
> Can I suggest two of them to have a call and see if one can convince 
> the
> other? The group had its consensus call, but based on my discussion 
> with
> Christer, the draft authors do not particularly care either way 
> regarding
> mandatory hash function selection issue. If Martin and Cullen can 
> agree on
> the way forward regarding this, they can bring the result to the group 
> and
> I am sure we will accommodate it. If they cannot reach an agreement, 
> then
> we can look at other ways to resolve it.

I highly encourage that in any case.


>
> Please note, that Chirster and I do feel strongly that the new draft 
> should
> be considered an update to RFC 4572, since it clarifies the multiple
> fingerprint related issues. I do believe any of the 4572 
> implementations
> should be compliant with the new draft in order to avoid interop 
> issues.
>

I take that to mean that if Martin and Cullen go off and decide the 
"updates" tag is not needed, you will be unhappy? If so, please try to 
participate in any such call.

> Regards,
>
> _____________
> Roman Shpount
>
> On Fri, Oct 28, 2016 at 9:23 AM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
>> Hi,
>>
>> Keep in mind that this would most likely not be a thing where the
>> presenter (me, I assume) shows a slide that people the comment on. It 
>> would
>> mostly be a â€œbehind the microphone argumeâ€¦ eeeh.. discussionâ€� 
>> between a few
>> people, so I wonder whether the WG session is the best place to 
>> discuss
>> this.
>>
>> Regards,
>>
>> Christer
>>
>> From: Bo Burman <bo.burman@ericsson.com>
>> Date: Friday 28 October 2016 at 12:39
>> To: Eric Rescorla <ekr@rtfm.com>, Martin Thomson 
>> <martin.thomson@gmail.com
>>>
>> Cc: Ben Campbell <ben@nostrum.com>, "mmusic@ietf.org" 
>> <mmusic@ietf.org>,
>> ART ADs <art-ads@ietf.org>, Flemming Andreasen <fandreas@cisco.com>,
>> Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <
>> christer.holmberg@ericsson.com>
>> Subject: RE: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update 
>> (was
>> Re: Rough concensus: Re: 4572-update: Consensus call on how to move
>> forward)]
>>
>> This is definitely possible â€“ MMUSIC Seoul agenda is not set in 
>> stone, but
>> please be aware that the single MMUSIC session is only an hour in 
>> total.
>>
>> /Bo
>>
>> MMUSIC co-chair
>>
>>
>>
>> *From:* mmusic [mailto:mmusic-bounces@ietf.org 
>> <mmusic-bounces@ietf.org>] *On
>> Behalf Of *Eric Rescorla
>> *Sent:* den 28 oktober 2016 10:49
>> *To:* Martin Thomson <martin.thomson@gmail.com>
>> *Cc:* Ben Campbell <ben@nostrum.com>; mmusic <mmusic@ietf.org>; ART 
>> ADs <
>> art-ads@ietf.org>; Flemming Andreasen <fandreas@cisco.com>; Cullen
>> Jennings <fluffy@iii.ca>; Christer Holmberg 
>> <christer.holmberg@ericsson.
>> com>
>> *Subject:* Re: [MMUSIC] Doodle poll [Re: Moving Forward on 
>> 4572-update
>> (was Re: Rough concensus: Re: 4572-update: Consensus call on how to 
>> move
>> forward)]
>>
>>
>>
>> Dealing with this in Seoul seems like a reasonable suggestion
>>
>>
>>
>> -Ekr
>>
>>
>>
>>
>>
>> On Fri, Oct 28, 2016 at 4:11 PM, Martin Thomson 
>> <martin.thomson@gmail.com>
>> wrote:
>>
>> On 26 October 2016 at 15:54, Flemming Andreasen <fandreas@cisco.com>
>> wrote:
>>> A Doodle poll is now available at
>>>
>>>         http://doodle.com/poll/kxw4n9a2v7v3pe2y
>>>
>>> We are looking at either Wednesday or Friday next week (November 2 
>>> or
>> 4), so
>>> please get your vote in pretty quickly if you are interested.
>>
>> These are awful times for me, though I would like to be involved.
>> It's not that long now until we will all be in the same room, is this
>> somehow urgent enough that we need to have a call?
>>
>>
>> _______________________________________________
>> 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
>>
>>


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


From nobody Fri Oct 28 08:08:06 2016
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 2800F12962D for <mmusic@ietfa.amsl.com>; Fri, 28 Oct 2016 08:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5] 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 gTPvEW3YACwG for <mmusic@ietfa.amsl.com>; Fri, 28 Oct 2016 08:08:02 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (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 B65F512967C for <mmusic@ietf.org>; Fri, 28 Oct 2016 08:08:01 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id n6so2614713qtd.1 for <mmusic@ietf.org>; Fri, 28 Oct 2016 08:08:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=d5dY6/4NQxaoG8OZgGOM9/Gu+nUwN5PHOZyLgSYavY4=; b=lm8endZD8kRS2fTYTNwPGwwmh39C2nES2kXQPDGS3pRoCYYyxKmAS1mAB2njtQawhf bA1+7+79tPs0jaPtKqDOuppvD6uWG565wtUfX5OWnhbPCD4Gh/70buc3gulfgjrOjTjv LSyLe1OufS26oz+4PzISGMxtngFkWs4xqcgCDvpI+OuVhVkrUc4w35rZWa5l2eFNReIC vMzaSc5Joq3egERK3jVoKBu07rjvlihmqp8GVb5z8pUHSA1nruA9hCwPj/II07ZzYL1U bbNmW803wm+UictaBDrt0u4KTzjHp1qofNVi7DDrUnRxITyaXT1lo6GlOzAQ+M7v2aHg Dkyg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=d5dY6/4NQxaoG8OZgGOM9/Gu+nUwN5PHOZyLgSYavY4=; b=glUmqACEEIav298LSck9LP3ol8CL6dITIiQuCHaKZ2Fs0kW9CL2TF3YdQSH+DA7kzZ jBTyc4NjEuDD2rT/xEI/9B8u8anSiq0AQDtGNr1AE6yts6V+QEzcsjZKd1Na+GrtR4nm IVAkMuItG4cp33TEyrpxFPkhWu4ohNkkVdgs3+bR8B1sbGm9/gFZ8/mnwBcRO6uywMha 99FtBJ9vZOr4SeY5uif7Juq3DEMy+2xM9m58r6dhOcYIP85J/QcAsIehkcUNVnIyu1mc uE/0gbZxKBvuk6Rr32i7ZMSMCrMmXAtUPAMBTQGZ+v+NJzW/JOj9jrp5t3uHofIfAjOI sp6w==
X-Gm-Message-State: ABUngvcz+PpesNKYIQQLC5gnyGsenUcpDQDIuw7XlJeoKb3LYhJN1NRsie8rZzspOnfeAQ==
X-Received: by 10.200.37.11 with SMTP id 11mr11816021qtm.12.1477667280733; Fri, 28 Oct 2016 08:08:00 -0700 (PDT)
Received: from mail-qk0-f181.google.com (mail-qk0-f181.google.com. [209.85.220.181]) by smtp.gmail.com with ESMTPSA id p13sm6445237qtp.20.2016.10.28.08.08.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Oct 2016 08:08:00 -0700 (PDT)
Received: by mail-qk0-f181.google.com with SMTP id o68so90042365qkf.3; Fri, 28 Oct 2016 08:08:00 -0700 (PDT)
X-Received: by 10.55.39.202 with SMTP id n193mr11318003qkn.252.1477667279939;  Fri, 28 Oct 2016 08:07:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.132.161 with HTTP; Fri, 28 Oct 2016 08:07:59 -0700 (PDT)
In-Reply-To: <E95B34C4-91EA-41FC-9EAC-D59C77A33C12@nostrum.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com> <CABkgnnV7yU8Y1YhDSmm5hSbFSoVLhXvDnKOAs1otmnyf0s5RHw@mail.gmail.com> <CABcZeBMFeCkAxOaTPaMZytLmNpbprja5tF5D7RHrejSihN508Q@mail.gmail.com> <AM5PR0701MB2577F7A1A473CE2D5866365B8DAD0@AM5PR0701MB2577.eurprd07.prod.outlook.com> <D4392BDB.120E1%christer.holmberg@ericsson.com> <CAD5OKxsY7+ZHtGJeX7YG=BBYTj4PxEBmgopGQ6u7Hrj2EEgT_Q@mail.gmail.com> <E95B34C4-91EA-41FC-9EAC-D59C77A33C12@nostrum.com>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 28 Oct 2016 11:07:59 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuRm2tedhBTh096M6N923P6UPmotH-RJOCoqSzGMgE5MQ@mail.gmail.com>
Message-ID: <CAD5OKxuRm2tedhBTh096M6N923P6UPmotH-RJOCoqSzGMgE5MQ@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=94eb2c0950ee51300c053fee3980
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/yA93uVCR8OsaHL0NgHvLffjLNcI>
Cc: Flemming Andreasen <fandreas@cisco.com>, ART ADs <art-ads@ietf.org>, mmusic <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 15:08:05 -0000

--94eb2c0950ee51300c053fee3980
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Essentially there are two issues:

1. Should we mandate the SHA-256
2. Should this be an update to RFC 4572

I do not care about mandating SHA-256. Christer updated the draft to
include this at Martin's request. Then he removed it at Cullen's request. I
would ask two of them to talk and try to come to an agreement.

I do care strongly about this document being an update to RFC 4572 and will
be unhappy if this tag is removed. RFC 4572 is ambiguous in regard to
multiple fingerprints. Two implementations can currently claim compliance
with RFC 4572 but fail to work with each other. I want this resolved and I
think this requires an update.

Regards,
_____________
Roman Shpount

On Fri, Oct 28, 2016 at 10:43 AM, Ben Campbell <ben@nostrum.com> wrote:

> On 28 Oct 2016, at 8:43, Roman Shpount wrote:
>
> In general, the two opposing champions are Cullen (asking not to update t=
he
>> required hash algorithm) and Martin (who asked to make SHA-256 the
>> requirement in the first place).
>>
>
> If Martin is critical to this conversation, then the conversation should
> wait for him. But I agree with Christer that this is likely to be a
> behind-the-mike discussion. I half expect that to end with "interested
> parties please gather for a side meeting."
>
> The point being: If a group call cannot happen prior to Seoul, then I
> strongly suggest interested parties arrange a side meeting there _prior_ =
to
> the MMUSIC meeting (currently scheduled Wednesday morning).
>
> (I understand the AD is somewhat frustrated over the draft being stuck on
> this point ;-)  )
>
>
>
>> Can I suggest two of them to have a call and see if one can convince the
>> other? The group had its consensus call, but based on my discussion with
>> Christer, the draft authors do not particularly care either way regardin=
g
>> mandatory hash function selection issue. If Martin and Cullen can agree =
on
>> the way forward regarding this, they can bring the result to the group a=
nd
>> I am sure we will accommodate it. If they cannot reach an agreement, the=
n
>> we can look at other ways to resolve it.
>>
>
> I highly encourage that in any case.
>
>
>
>> Please note, that Chirster and I do feel strongly that the new draft
>> should
>> be considered an update to RFC 4572, since it clarifies the multiple
>> fingerprint related issues. I do believe any of the 4572 implementations
>> should be compliant with the new draft in order to avoid interop issues.
>>
>>
> I take that to mean that if Martin and Cullen go off and decide the
> "updates" tag is not needed, you will be unhappy? If so, please try to
> participate in any such call.
>
> Regards,
>>
>> _____________
>> Roman Shpount
>>
>> On Fri, Oct 28, 2016 at 9:23 AM, Christer Holmberg <
>> christer.holmberg@ericsson.com> wrote:
>>
>> Hi,
>>>
>>> Keep in mind that this would most likely not be a thing where the
>>> presenter (me, I assume) shows a slide that people the comment on. It
>>> would
>>> mostly be a =E2=80=9Cbehind the microphone argume=E2=80=A6 eeeh.. discu=
ssion=E2=80=9D between a
>>> few
>>> people, so I wonder whether the WG session is the best place to discuss
>>> this.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>> From: Bo Burman <bo.burman@ericsson.com>
>>> Date: Friday 28 October 2016 at 12:39
>>> To: Eric Rescorla <ekr@rtfm.com>, Martin Thomson <
>>> martin.thomson@gmail.com
>>>
>>>>
>>>> Cc: Ben Campbell <ben@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org
>>> >,
>>> ART ADs <art-ads@ietf.org>, Flemming Andreasen <fandreas@cisco.com>,
>>> Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <
>>> christer.holmberg@ericsson.com>
>>> Subject: RE: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (w=
as
>>> Re: Rough concensus: Re: 4572-update: Consensus call on how to move
>>> forward)]
>>>
>>> This is definitely possible =E2=80=93 MMUSIC Seoul agenda is not set in=
 stone,
>>> but
>>> please be aware that the single MMUSIC session is only an hour in total=
.
>>>
>>> /Bo
>>>
>>> MMUSIC co-chair
>>>
>>>
>>>
>>> *From:* mmusic [mailto:mmusic-bounces@ietf.org <mmusic-bounces@ietf.org=
>]
>>> *On
>>> Behalf Of *Eric Rescorla
>>> *Sent:* den 28 oktober 2016 10:49
>>> *To:* Martin Thomson <martin.thomson@gmail.com>
>>> *Cc:* Ben Campbell <ben@nostrum.com>; mmusic <mmusic@ietf.org>; ART ADs
>>> <
>>> art-ads@ietf.org>; Flemming Andreasen <fandreas@cisco.com>; Cullen
>>> Jennings <fluffy@iii.ca>; Christer Holmberg <christer.holmberg@ericsson=
.
>>> com>
>>> *Subject:* Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update
>>>
>>> (was Re: Rough concensus: Re: 4572-update: Consensus call on how to mov=
e
>>> forward)]
>>>
>>>
>>>
>>> Dealing with this in Seoul seems like a reasonable suggestion
>>>
>>>
>>>
>>> -Ekr
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Oct 28, 2016 at 4:11 PM, Martin Thomson <
>>> martin.thomson@gmail.com>
>>> wrote:
>>>
>>> On 26 October 2016 at 15:54, Flemming Andreasen <fandreas@cisco.com>
>>> wrote:
>>>
>>>> A Doodle poll is now available at
>>>>
>>>>         http://doodle.com/poll/kxw4n9a2v7v3pe2y
>>>>
>>>> We are looking at either Wednesday or Friday next week (November 2 or
>>>>
>>> 4), so
>>>
>>>> please get your vote in pretty quickly if you are interested.
>>>>
>>>
>>> These are awful times for me, though I would like to be involved.
>>> It's not that long now until we will all be in the same room, is this
>>> somehow urgent enough that we need to have a call?
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>>
>
> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>

--94eb2c0950ee51300c053fee3980
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Essentially there are two issues:<div><br></div><div>1. Sh=
ould we mandate the SHA-256</div><div>2. Should this be an update to RFC 45=
72</div><div><br></div><div>I do not care about mandating SHA-256. Christer=
 updated the draft to include this at Martin&#39;s request. Then he removed=
 it at Cullen&#39;s request. I would ask two of them to talk and try to com=
e to an agreement.</div><div><br></div><div>I do care strongly about this d=
ocument being an update to RFC=C2=A04572 and will be unhappy if this tag is=
 removed. RFC 4572 is ambiguous in regard to multiple fingerprints. Two imp=
lementations can currently claim compliance with RFC 4572 but fail to work =
with each other. I want this resolved and I think this requires an update.<=
/div><div><br></div><div>Regards,</div><div><div class=3D"gmail_extra"><div=
><div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div>
<br><div class=3D"gmail_quote">On Fri, Oct 28, 2016 at 10:43 AM, Ben Campbe=
ll <span dir=3D"ltr">&lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_blan=
k">ben@nostrum.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><span class=3D"gmail-">On 28 Oct 2016, at 8:43, Roman Sh=
pount wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
In general, the two opposing champions are Cullen (asking not to update the=
<br>
required hash algorithm) and Martin (who asked to make SHA-256 the<br>
requirement in the first place).<br>
</blockquote>
<br></span>
If Martin is critical to this conversation, then the conversation should wa=
it for him. But I agree with Christer that this is likely to be a behind-th=
e-mike discussion. I half expect that to end with &quot;interested parties =
please gather for a side meeting.&quot;<br>
<br>
The point being: If a group call cannot happen prior to Seoul, then I stron=
gly suggest interested parties arrange a side meeting there _prior_ to the =
MMUSIC meeting (currently scheduled Wednesday morning).<br>
<br>
(I understand the AD is somewhat frustrated over the draft being stuck on t=
his point ;-)=C2=A0 )<span class=3D"gmail-"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Can I suggest two of them to have a call and see if one can convince the<br=
>
other? The group had its consensus call, but based on my discussion with<br=
>
Christer, the draft authors do not particularly care either way regarding<b=
r>
mandatory hash function selection issue. If Martin and Cullen can agree on<=
br>
the way forward regarding this, they can bring the result to the group and<=
br>
I am sure we will accommodate it. If they cannot reach an agreement, then<b=
r>
we can look at other ways to resolve it.<br>
</blockquote>
<br></span>
I highly encourage that in any case.<span class=3D"gmail-"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Please note, that Chirster and I do feel strongly that the new draft should=
<br>
be considered an update to RFC 4572, since it clarifies the multiple<br>
fingerprint related issues. I do believe any of the 4572 implementations<br=
>
should be compliant with the new draft in order to avoid interop issues.<br=
>
<br>
</blockquote>
<br></span>
I take that to mean that if Martin and Cullen go off and decide the &quot;u=
pdates&quot; tag is not needed, you will be unhappy? If so, please try to p=
articipate in any such call.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class=3D"gmail-=
h5">
Regards,<br>
<br>
_____________<br>
Roman Shpount<br>
<br>
On Fri, Oct 28, 2016 at 9:23 AM, Christer Holmberg &lt;<br>
<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christe=
r.holmberg@ericsson.com</a><wbr>&gt; wrote:<br>
<br>
</div></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div cla=
ss=3D"gmail-h5">
Hi,<br>
<br>
Keep in mind that this would most likely not be a thing where the<br>
presenter (me, I assume) shows a slide that people the comment on. It would=
<br>
mostly be a =E2=80=9Cbehind the microphone argume=E2=80=A6 eeeh.. discussio=
n=E2=80=9D between a few<br>
people, so I wonder whether the WG session is the best place to discuss<br>
this.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
From: Bo Burman &lt;<a href=3D"mailto:bo.burman@ericsson.com" target=3D"_bl=
ank">bo.burman@ericsson.com</a>&gt;<br>
Date: Friday 28 October 2016 at 12:39<br>
To: Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr=
@rtfm.com</a>&gt;, Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmai=
l.com" target=3D"_blank">martin.thomson@gmail.com</a><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
</blockquote>
Cc: Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_blank">b=
en@nostrum.com</a>&gt;, &quot;<a href=3D"mailto:mmusic@ietf.org" target=3D"=
_blank">mmusic@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org" ta=
rget=3D"_blank">mmusic@ietf.org</a>&gt;,<br>
ART ADs &lt;<a href=3D"mailto:art-ads@ietf.org" target=3D"_blank">art-ads@i=
etf.org</a>&gt;, Flemming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.co=
m" target=3D"_blank">fandreas@cisco.com</a>&gt;,<br>
Cullen Jennings &lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank">fluf=
fy@iii.ca</a>&gt;, Christer Holmberg &lt;<br>
<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christe=
r.holmberg@ericsson.com</a><wbr>&gt;<br>
Subject: RE: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was<b=
r>
Re: Rough concensus: Re: 4572-update: Consensus call on how to move<br>
forward)]<br>
<br>
This is definitely possible =E2=80=93 MMUSIC Seoul agenda is not set in sto=
ne, but<br>
please be aware that the single MMUSIC session is only an hour in total.<br=
>
<br>
/Bo<br>
<br>
MMUSIC co-chair<br>
<br>
<br>
<br></div></div>
*From:* mmusic [mailto:<a href=3D"mailto:mmusic-bounces@ietf.org" target=3D=
"_blank">mmusic-bounces@ietf.or<wbr>g</a> &lt;<a href=3D"mailto:mmusic-boun=
ces@ietf.org" target=3D"_blank">mmusic-bounces@ietf.org</a>&gt;] *On<br>
Behalf Of *Eric Rescorla<br>
*Sent:* den 28 oktober 2016 10:49<br>
*To:* Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com" target=
=3D"_blank">martin.thomson@gmail.com</a>&gt;<br>
*Cc:* Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_blank"=
>ben@nostrum.com</a>&gt;; mmusic &lt;<a href=3D"mailto:mmusic@ietf.org" tar=
get=3D"_blank">mmusic@ietf.org</a>&gt;; ART ADs &lt;<span class=3D"gmail-">=
<br>
<a href=3D"mailto:art-ads@ietf.org" target=3D"_blank">art-ads@ietf.org</a>&=
gt;; Flemming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com" target=3D=
"_blank">fandreas@cisco.com</a>&gt;; Cullen<br>
Jennings &lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank">fluffy@iii.=
ca</a>&gt;; Christer Holmberg &lt;christer.holmberg@ericsson.<br>
com&gt;<br></span>
*Subject:* Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update<div>=
<div class=3D"gmail-h5"><br>
(was Re: Rough concensus: Re: 4572-update: Consensus call on how to move<br=
>
forward)]<br>
<br>
<br>
<br>
Dealing with this in Seoul seems like a reasonable suggestion<br>
<br>
<br>
<br>
-Ekr<br>
<br>
<br>
<br>
<br>
<br>
On Fri, Oct 28, 2016 at 4:11 PM, Martin Thomson &lt;<a href=3D"mailto:marti=
n.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>&gt;<br>
wrote:<br>
<br>
On 26 October 2016 at 15:54, Flemming Andreasen &lt;<a href=3D"mailto:fandr=
eas@cisco.com" target=3D"_blank">fandreas@cisco.com</a>&gt;<br>
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
A Doodle poll is now available at<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://doodle.com/poll/kxw4n9a2v7v3p=
e2y" rel=3D"noreferrer" target=3D"_blank">http://doodle.com/poll/kxw4n9a<wb=
r>2v7v3pe2y</a><br>
<br>
We are looking at either Wednesday or Friday next week (November 2 or<br>
</blockquote>
4), so<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
please get your vote in pretty quickly if you are interested.<br>
</blockquote>
<br>
These are awful times for me, though I would like to be involved.<br>
It&#39;s not that long now until we will all be in the same room, is this<b=
r>
somehow urgent enough that we need to have a call?<br>
<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
<br>
<br>
</div></div></blockquote></blockquote><div class=3D"gmail-HOEnZb"><div clas=
s=3D"gmail-h5">
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
</div></div></blockquote></div><br></div></div></div>

--94eb2c0950ee51300c053fee3980--


From nobody Fri Oct 28 08:19:12 2016
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 C554F12944E; Fri, 28 Oct 2016 08:19:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 U5wlHupAF0Xw; Fri, 28 Oct 2016 08:19:07 -0700 (PDT)
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 CD6BA129407; Fri, 28 Oct 2016 08:19:06 -0700 (PDT)
X-AuditID: c1b4fb3a-18c55980000078c6-29-58136c699f58
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by  (Symantec Mail Security) with SMTP id 5B.14.30918.86C63185; Fri, 28 Oct 2016 17:19:05 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0319.002; Fri, 28 Oct 2016 17:19:03 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
Thread-Index: AQHSMNnG/C24dxYqrUukZJjBpwhGbKC9MkYAgABI8QCAAHLIgP//0UoAgAAQ6YCAAAa3gIAAJJ6w
Date: Fri, 28 Oct 2016 15:19:02 +0000
Message-ID: <6F61DD6B-FB1E-4604-B5A6-25BEE5C2852F@ericsson.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com> <CABkgnnV7yU8Y1YhDSmm5hSbFSoVLhXvDnKOAs1otmnyf0s5RHw@mail.gmail.com> <CABcZeBMFeCkAxOaTPaMZytLmNpbprja5tF5D7RHrejSihN508Q@mail.gmail.com> <AM5PR0701MB2577F7A1A473CE2D5866365B8DAD0@AM5PR0701MB2577.eurprd07.prod.outlook.com> <D4392BDB.120E1%christer.holmberg@ericsson.com> <CAD5OKxsY7+ZHtGJeX7YG=BBYTj4PxEBmgopGQ6u7Hrj2EEgT_Q@mail.gmail.com> <E95B34C4-91EA-41FC-9EAC-D59C77A33C12@nostrum.com>, <CAD5OKxuRm2tedhBTh096M6N923P6UPmotH-RJOCoqSzGMgE5MQ@mail.gmail.com>
In-Reply-To: <CAD5OKxuRm2tedhBTh096M6N923P6UPmotH-RJOCoqSzGMgE5MQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_6F61DD6BFB1E4604B5A625BEE5C2852Fericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHIsWRmVeSWpSXmKPExsUyM2K7h25mjnCEwdfPvBYbn05msZjfeZrd 4v0FXYsP638wWkxd/pjFYsaFqcwObB5Tfm9k9Viy5CeTx+XzHxk9Zu18wuJxa0pBAGsUl01K ak5mWWqRvl0CV8bSbcvZCpb2MlZc63nJ1sC4qKKLkZNDQsBE4vKxj2xdjFwcQgLrGSVat25n hXCWMEocuf4eyOHgYBOwkOj+pw3SICKgKvH3+2QmkBpmgWWMEhNuzQNzhAVmMkr8vX+NGcQR EZjFKDFlUSc7REuURPvDDUwgNgtQ+7v5XYwgNq+AvcSiuXuZINb9YZH4+3kKWIJTIFDi9PHJ rCA2o4CYxPdTa8CamQXEJW49mc8EcbiAxJI955khbFGJl4//sULUJEs0X/sKtUBQ4uTMJywT GIVnIWmfhaRsFpIyiLiBxPtz85khbG2JZQtfQ9n6Ehu/nGVEFl/AyL6KUbQ4tbg4N93ISC+1 KDO5uDg/Ty8vtWQTIzAWD275bbWD8eBzx0OMAhyMSjy8CRxCEUKsiWXFlbmHGCU4mJVEeL2y hSOEeFMSK6tSi/Lji0pzUosPMUpzsCiJ85qtvB8uJJCeWJKanZpakFoEk2Xi4JRqYEzIXKp5 9Paysz4TdFkDbwbo9og7njr7yPzhv81Rl7k9t2us37JUwcw4W+1H11mh526XUjfGz93XdTFw cxi/4TS+O3POOS2Y5XVZ/cJ2i8MvFppWfN+zVP1nv/qeNd0POVbO3c0XJXey3tJmXeWxw0W/ p2kKF2pOE9dZ2PZl4iu1Fw8VY66H3lZSYinOSDTUYi4qTgQA10qpV8ECAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/P_uXaRGLio-hxwadAVOjJjIKNB0>
Cc: Flemming Andreasen <fandreas@cisco.com>, Ben Campbell <ben@nostrum.com>, ART ADs <art-ads@ietf.org>, mmusic <mmusic@ietf.org>, Cullen Jennings <fluffy@iii.ca>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 15:19:11 -0000

--_000_6F61DD6BFB1E4604B5A625BEE5C2852Fericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

Just to clarify: even though I do want the  spec to be an update to 4572, I=
 am happy with the note saying that the spec does not make existing impleme=
ntations non-compliant with 4572.

Regards,

Christer

Sent from my iPhone

On 28 Oct 2016, at 18.08, Roman Shpount <roman@telurix.com<mailto:roman@tel=
urix.com>> wrote:

Essentially there are two issues:

1. Should we mandate the SHA-256
2. Should this be an update to RFC 4572

I do not care about mandating SHA-256. Christer updated the draft to includ=
e this at Martin's request. Then he removed it at Cullen's request. I would=
 ask two of them to talk and try to come to an agreement.

I do care strongly about this document being an update to RFC 4572 and will=
 be unhappy if this tag is removed. RFC 4572 is ambiguous in regard to mult=
iple fingerprints. Two implementations can currently claim compliance with =
RFC 4572 but fail to work with each other. I want this resolved and I think=
 this requires an update.

Regards,
_____________
Roman Shpount

On Fri, Oct 28, 2016 at 10:43 AM, Ben Campbell <ben@nostrum.com<mailto:ben@=
nostrum.com>> wrote:
On 28 Oct 2016, at 8:43, Roman Shpount wrote:

In general, the two opposing champions are Cullen (asking not to update the
required hash algorithm) and Martin (who asked to make SHA-256 the
requirement in the first place).

If Martin is critical to this conversation, then the conversation should wa=
it for him. But I agree with Christer that this is likely to be a behind-th=
e-mike discussion. I half expect that to end with "interested parties pleas=
e gather for a side meeting."

The point being: If a group call cannot happen prior to Seoul, then I stron=
gly suggest interested parties arrange a side meeting there _prior_ to the =
MMUSIC meeting (currently scheduled Wednesday morning).

(I understand the AD is somewhat frustrated over the draft being stuck on t=
his point ;-)  )



Can I suggest two of them to have a call and see if one can convince the
other? The group had its consensus call, but based on my discussion with
Christer, the draft authors do not particularly care either way regarding
mandatory hash function selection issue. If Martin and Cullen can agree on
the way forward regarding this, they can bring the result to the group and
I am sure we will accommodate it. If they cannot reach an agreement, then
we can look at other ways to resolve it.

I highly encourage that in any case.



Please note, that Chirster and I do feel strongly that the new draft should
be considered an update to RFC 4572, since it clarifies the multiple
fingerprint related issues. I do believe any of the 4572 implementations
should be compliant with the new draft in order to avoid interop issues.


I take that to mean that if Martin and Cullen go off and decide the "update=
s" tag is not needed, you will be unhappy? If so, please try to participate=
 in any such call.

Regards,

_____________
Roman Shpount

On Fri, Oct 28, 2016 at 9:23 AM, Christer Holmberg <
christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> wrot=
e:

Hi,

Keep in mind that this would most likely not be a thing where the
presenter (me, I assume) shows a slide that people the comment on. It would
mostly be a =93behind the microphone argume=85 eeeh.. discussion=94 between=
 a few
people, so I wonder whether the WG session is the best place to discuss
this.

Regards,

Christer

From: Bo Burman <bo.burman@ericsson.com<mailto:bo.burman@ericsson.com>>
Date: Friday 28 October 2016 at 12:39
To: Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtfm.com>>, Martin Thomson <mart=
in.thomson@gmail.com<mailto:martin.thomson@gmail.com>

Cc: Ben Campbell <ben@nostrum.com<mailto:ben@nostrum.com>>, "mmusic@ietf.or=
g<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusic@ietf.org>>,
ART ADs <art-ads@ietf.org<mailto:art-ads@ietf.org>>, Flemming Andreasen <fa=
ndreas@cisco.com<mailto:fandreas@cisco.com>>,
Cullen Jennings <fluffy@iii.ca<mailto:fluffy@iii.ca>>, Christer Holmberg <
christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>>
Subject: RE: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was
Re: Rough concensus: Re: 4572-update: Consensus call on how to move
forward)]

This is definitely possible =96 MMUSIC Seoul agenda is not set in stone, bu=
t
please be aware that the single MMUSIC session is only an hour in total.

/Bo

MMUSIC co-chair



*From:* mmusic [mailto:mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.o=
rg> <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>>] *On
Behalf Of *Eric Rescorla
*Sent:* den 28 oktober 2016 10:49
*To:* Martin Thomson <martin.thomson@gmail.com<mailto:martin.thomson@gmail.=
com>>
*Cc:* Ben Campbell <ben@nostrum.com<mailto:ben@nostrum.com>>; mmusic <mmusi=
c@ietf.org<mailto:mmusic@ietf.org>>; ART ADs <
art-ads@ietf.org<mailto:art-ads@ietf.org>>; Flemming Andreasen <fandreas@ci=
sco.com<mailto:fandreas@cisco.com>>; Cullen
Jennings <fluffy@iii.ca<mailto:fluffy@iii.ca>>; Christer Holmberg <christer=
.holmberg@ericsson.
com>
*Subject:* Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update

(was Re: Rough concensus: Re: 4572-update: Consensus call on how to move
forward)]



Dealing with this in Seoul seems like a reasonable suggestion



-Ekr





On Fri, Oct 28, 2016 at 4:11 PM, Martin Thomson <martin.thomson@gmail.com<m=
ailto:martin.thomson@gmail.com>>
wrote:

On 26 October 2016 at 15:54, Flemming Andreasen <fandreas@cisco.com<mailto:=
fandreas@cisco.com>>
wrote:
A Doodle poll is now available at

        http://doodle.com/poll/kxw4n9a2v7v3pe2y

We are looking at either Wednesday or Friday next week (November 2 or
4), so
please get your vote in pretty quickly if you are interested.

These are awful times for me, though I would like to be involved.
It's not that long now until we will all be in the same room, is this
somehow urgent enough that we need to have a call?


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



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




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


--_000_6F61DD6BFB1E4604B5A625BEE5C2852Fericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body dir=3D"auto">
<div>Hi,</div>
<div><br>
</div>
<div>Just to clarify: even though I do want the &nbsp;spec to be an update =
to 4572, I am happy with the note saying that the spec does not make existi=
ng implementations non-compliant with 4572.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer&nbsp;<br>
<br>
<div>Sent from my iPhone</div>
</div>
<div><br>
On 28 Oct 2016, at 18.08, Roman Shpount &lt;<a href=3D"mailto:roman@telurix=
.com">roman@telurix.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">Essentially there are two issues:
<div><br>
</div>
<div>1. Should we mandate the SHA-256</div>
<div>2. Should this be an update to RFC 4572</div>
<div><br>
</div>
<div>I do not care about mandating SHA-256. Christer updated the draft to i=
nclude this at Martin's request. Then he removed it at Cullen's request. I =
would ask two of them to talk and try to come to an agreement.</div>
<div><br>
</div>
<div>I do care strongly about this document being an update to RFC&nbsp;457=
2 and will be unhappy if this tag is removed. RFC 4572 is ambiguous in rega=
rd to multiple fingerprints. Two implementations can currently claim compli=
ance with RFC 4572 but fail to work with
 each other. I want this resolved and I think this requires an update.</div=
>
<div><br>
</div>
<div>Regards,</div>
<div>
<div class=3D"gmail_extra">
<div>
<div class=3D"gmail_signature">_____________<br>
Roman Shpount</div>
</div>
<br>
<div class=3D"gmail_quote">On Fri, Oct 28, 2016 at 10:43 AM, Ben Campbell <=
span dir=3D"ltr">
&lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_blank">ben@nostrum.com</a=
>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<span class=3D"gmail-">On 28 Oct 2016, at 8:43, Roman Shpount wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
In general, the two opposing champions are Cullen (asking not to update the=
<br>
required hash algorithm) and Martin (who asked to make SHA-256 the<br>
requirement in the first place).<br>
</blockquote>
<br>
</span>If Martin is critical to this conversation, then the conversation sh=
ould wait for him. But I agree with Christer that this is likely to be a be=
hind-the-mike discussion. I half expect that to end with &quot;interested p=
arties please gather for a side meeting.&quot;<br>
<br>
The point being: If a group call cannot happen prior to Seoul, then I stron=
gly suggest interested parties arrange a side meeting there _prior_ to the =
MMUSIC meeting (currently scheduled Wednesday morning).<br>
<br>
(I understand the AD is somewhat frustrated over the draft being stuck on t=
his point ;-)&nbsp; )<span class=3D"gmail-"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Can I suggest two of them to have a call and see if one can convince the<br=
>
other? The group had its consensus call, but based on my discussion with<br=
>
Christer, the draft authors do not particularly care either way regarding<b=
r>
mandatory hash function selection issue. If Martin and Cullen can agree on<=
br>
the way forward regarding this, they can bring the result to the group and<=
br>
I am sure we will accommodate it. If they cannot reach an agreement, then<b=
r>
we can look at other ways to resolve it.<br>
</blockquote>
<br>
</span>I highly encourage that in any case.<span class=3D"gmail-"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Please note, that Chirster and I do feel strongly that the new draft should=
<br>
be considered an update to RFC 4572, since it clarifies the multiple<br>
fingerprint related issues. I do believe any of the 4572 implementations<br=
>
should be compliant with the new draft in order to avoid interop issues.<br=
>
<br>
</blockquote>
<br>
</span>I take that to mean that if Martin and Cullen go off and decide the =
&quot;updates&quot; tag is not needed, you will be unhappy? If so, please t=
ry to participate in any such call.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div class=3D"gmail-h5">Regards,<br>
<br>
_____________<br>
Roman Shpount<br>
<br>
On Fri, Oct 28, 2016 at 9:23 AM, Christer Holmberg &lt;<br>
<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christe=
r.holmberg@ericsson.com</a><wbr>&gt; wrote:<br>
<br>
</div>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div class=3D"gmail-h5">Hi,<br>
<br>
Keep in mind that this would most likely not be a thing where the<br>
presenter (me, I assume) shows a slide that people the comment on. It would=
<br>
mostly be a =93behind the microphone argume=85 eeeh.. discussion=94 between=
 a few<br>
people, so I wonder whether the WG session is the best place to discuss<br>
this.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
From: Bo Burman &lt;<a href=3D"mailto:bo.burman@ericsson.com" target=3D"_bl=
ank">bo.burman@ericsson.com</a>&gt;<br>
Date: Friday 28 October 2016 at 12:39<br>
To: Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr=
@rtfm.com</a>&gt;, Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmai=
l.com" target=3D"_blank">martin.thomson@gmail.com</a><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
</blockquote>
Cc: Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_blank">b=
en@nostrum.com</a>&gt;, &quot;<a href=3D"mailto:mmusic@ietf.org" target=3D"=
_blank">mmusic@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org" ta=
rget=3D"_blank">mmusic@ietf.org</a>&gt;,<br>
ART ADs &lt;<a href=3D"mailto:art-ads@ietf.org" target=3D"_blank">art-ads@i=
etf.org</a>&gt;, Flemming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.co=
m" target=3D"_blank">fandreas@cisco.com</a>&gt;,<br>
Cullen Jennings &lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank">fluf=
fy@iii.ca</a>&gt;, Christer Holmberg &lt;<br>
<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christe=
r.holmberg@ericsson.com</a><wbr>&gt;<br>
Subject: RE: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was<b=
r>
Re: Rough concensus: Re: 4572-update: Consensus call on how to move<br>
forward)]<br>
<br>
This is definitely possible =96 MMUSIC Seoul agenda is not set in stone, bu=
t<br>
please be aware that the single MMUSIC session is only an hour in total.<br=
>
<br>
/Bo<br>
<br>
MMUSIC co-chair<br>
<br>
<br>
<br>
</div>
</div>
*From:* mmusic [mailto:<a href=3D"mailto:mmusic-bounces@ietf.org" target=3D=
"_blank">mmusic-bounces@ietf.or<wbr>g</a> &lt;<a href=3D"mailto:mmusic-boun=
ces@ietf.org" target=3D"_blank">mmusic-bounces@ietf.org</a>&gt;] *On<br>
Behalf Of *Eric Rescorla<br>
*Sent:* den 28 oktober 2016 10:49<br>
*To:* Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com" target=
=3D"_blank">martin.thomson@gmail.com</a>&gt;<br>
*Cc:* Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_blank"=
>ben@nostrum.com</a>&gt;; mmusic &lt;<a href=3D"mailto:mmusic@ietf.org" tar=
get=3D"_blank">mmusic@ietf.org</a>&gt;; ART ADs &lt;<span class=3D"gmail-">=
<br>
<a href=3D"mailto:art-ads@ietf.org" target=3D"_blank">art-ads@ietf.org</a>&=
gt;; Flemming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com" target=3D=
"_blank">fandreas@cisco.com</a>&gt;; Cullen<br>
Jennings &lt;<a href=3D"mailto:fluffy@iii.ca" target=3D"_blank">fluffy@iii.=
ca</a>&gt;; Christer Holmberg &lt;christer.holmberg@ericsson.<br>
com&gt;<br>
</span>*Subject:* Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-upda=
te
<div>
<div class=3D"gmail-h5"><br>
(was Re: Rough concensus: Re: 4572-update: Consensus call on how to move<br=
>
forward)]<br>
<br>
<br>
<br>
Dealing with this in Seoul seems like a reasonable suggestion<br>
<br>
<br>
<br>
-Ekr<br>
<br>
<br>
<br>
<br>
<br>
On Fri, Oct 28, 2016 at 4:11 PM, Martin Thomson &lt;<a href=3D"mailto:marti=
n.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>&gt;<br>
wrote:<br>
<br>
On 26 October 2016 at 15:54, Flemming Andreasen &lt;<a href=3D"mailto:fandr=
eas@cisco.com" target=3D"_blank">fandreas@cisco.com</a>&gt;<br>
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
A Doodle poll is now available at<br>
<br>
&nbsp; &nbsp; &nbsp; &nbsp; <a href=3D"http://doodle.com/poll/kxw4n9a2v7v3p=
e2y" rel=3D"noreferrer" target=3D"_blank">
http://doodle.com/poll/kxw4n9a<wbr>2v7v3pe2y</a><br>
<br>
We are looking at either Wednesday or Friday next week (November 2 or<br>
</blockquote>
4), so<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
please get your vote in pretty quickly if you are interested.<br>
</blockquote>
<br>
These are awful times for me, though I would like to be involved.<br>
It's not that long now until we will all be in the same room, is this<br>
somehow urgent enough that we need to have a call?<br>
<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
<br>
<br>
</div>
</div>
</blockquote>
</blockquote>
<div class=3D"gmail-HOEnZb">
<div class=3D"gmail-h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br=
>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</blockquote>
</body>
</html>

--_000_6F61DD6BFB1E4604B5A625BEE5C2852Fericssoncom_--


From nobody Fri Oct 28 08:20:24 2016
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 21456129407; Fri, 28 Oct 2016 08:20:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.331
X-Spam-Level: 
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] 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 yl00HYTkAibQ; Fri, 28 Oct 2016 08:20:16 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D32B2124281; Fri, 28 Oct 2016 08:20:16 -0700 (PDT)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u9SFKA4u023853 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 28 Oct 2016 10:20:11 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: "Ben Campbell" <ben@nostrum.com>
To: "Mirja =?utf-8?q?K=C3=BChlewind?=" <ietf@kuehlewind.net>
Date: Fri, 28 Oct 2016 10:20:10 -0500
Message-ID: <E12F4BE2-DD6E-4787-88C1-8E36DCB16EB0@nostrum.com>
In-Reply-To: <e7f7e348-895a-ec12-6b9f-a673b7c9c7b4@kuehlewind.net>
References: <147741587672.1323.3788097761711986441.idtracker@ietfa.amsl.com> <CAMRcRGTEj-HwOvWtCi5orEKurMirOZLepG2sB1Ya7x-nJU7Pvg@mail.gmail.com> <fefa06b9-75b1-2e58-6532-1a426f7fb69f@kuehlewind.net> <CAMRcRGSmRLEPNjjSnPv_X3-HRNMq8vbDOzQtvXqB7RazrdHuVQ@mail.gmail.com> <e7f7e348-895a-ec12-6b9f-a673b7c9c7b4@kuehlewind.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5263)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MkR7PIaLRK6aN0FtbUVy_15b8YA>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, The IESG <iesg@ietf.org>, mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-mmusic-sdp-mux-attributes-14=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 15:20:18 -0000

On 28 Oct 2016, at 3:24, Mirja KÃ¼hlewind wrote:

> Hi Suhas,
>
> see below.
>
> On 28.10.2016 06:29, Suhas Nandakumar wrote:
>  >
>  >             2) Is the new registry for the Mux Category really 
> needed? Is it
>  >         expected
>  >             to (much) more categories in future?
>  >
>  >
>  >         [Suhas] -  We need the registry to list the currently 
> defined Mux
>  >         Categories
>  >         and also we do see there might be couple of more categories 
> (if not many)
>  >         that might get defined in the future.
>  >
>  >
>  >     This seems really vague for me. I would assume that you 
> actually don't
>  >     need a registry now and if there will be more categories 
> defined in the
>  >     future (which doesn't seem very likely) a new doc could still 
> define a
>  >     registry and update this RFC.
>  >
>  >
>  >
>  > [Suhas]
>  >  Section 15.2 and its sub-sections assign the multiplexing 
> categories  to
>  > several of the sub-registries in the IANA SDP Parameters registry. 
> This is
>  > done by adding a new column called 'Mux Category' to each of the
>  > sub-registries in the SDP Parameters registry.
>  > Having a registry defined to identify the names of these 
> Multiplexing
>  > categories ( as in Section 15.1) will ensure there is a formal 
> place for
>  > these names and formal rules to expand the category set in the 
> future.
>
> The formal place where these categories are explained is this RFC. 
> This RFC could also talk about the opportunity or even process to 
> expand this list in future. However, as long as it is not clear that 
> any expansion will be really needed in future, I don't see a need for 
> e registry.
>
> That's my view point. Please consult your AD for final advise.

I understand that the working group thinks that the chance that new 
categories will come up is high enough that they prefer to define the 
registry (and more importantly, the registration policy) in advance. I 
agree that this is a borderline case, and reasonable people could go 
either way. I don't think we should overrule the working group consensus 
this late in the process.

Thanks!

Ben.



From nobody Fri Oct 28 08:22:10 2016
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 6CD2B12944E; Fri, 28 Oct 2016 08:22:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w-3bCAKPtn9f; Fri, 28 Oct 2016 08:22:06 -0700 (PDT)
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 5359D124281; Fri, 28 Oct 2016 08:22:06 -0700 (PDT)
X-AuditID: c1b4fb3a-18c55980000078c6-4a-58136d1c6d79
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by  (Symantec Mail Security) with SMTP id B8.74.30918.C1D63185; Fri, 28 Oct 2016 17:22:04 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0319.002; Fri, 28 Oct 2016 17:22:02 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
Thread-Topic: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
Thread-Index: AQHSMNnG/C24dxYqrUukZJjBpwhGbKC9MkYAgABI8QCAAHLIgP//0UoAgAAQ6YCAACwrog==
Date: Fri, 28 Oct 2016 15:22:03 +0000
Message-ID: <79B12FF1-98FE-4719-BC53-39C186A7216F@ericsson.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com> <CABkgnnV7yU8Y1YhDSmm5hSbFSoVLhXvDnKOAs1otmnyf0s5RHw@mail.gmail.com> <CABcZeBMFeCkAxOaTPaMZytLmNpbprja5tF5D7RHrejSihN508Q@mail.gmail.com> <AM5PR0701MB2577F7A1A473CE2D5866365B8DAD0@AM5PR0701MB2577.eurprd07.prod.outlook.com> <D4392BDB.120E1%christer.holmberg@ericsson.com> <CAD5OKxsY7+ZHtGJeX7YG=BBYTj4PxEBmgopGQ6u7Hrj2EEgT_Q@mail.gmail.com>, <E95B34C4-91EA-41FC-9EAC-D59C77A33C12@nostrum.com>
In-Reply-To: <E95B34C4-91EA-41FC-9EAC-D59C77A33C12@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCIsWRmVeSWpSXmKPExsUyM2K7k65MrnCEQc9bfYuNTyezWMzvPM1u 8f6CrsWH9T8YLaYuf8xiMePCVGYHNo8pvzeyeixZ8pPJ4/L5j4wes3Y+YfG4NaUggDWKyyYl NSezLLVI3y6BK+Ps8ymsBet0Ks5tPc7awPhfuYuRk0NCwESi4cE/5i5GLg4hgfWMElO7XrBD OEsYJebdusTSxcjBwSZgIdH9TxukQURASeJ581YWkBpmgZWMEkd+3QFzhAVmMkr8vX8NbJSI wCxGiSmLOtkhWsIk9h7YyQxiswioSnQv+Q9m8wrYS7T2HwGzhQS2skj0PBMCsTmB4tfuTWQF sRkFxCS+n1rDBGIzC4hL3HoynwnibgGJJXvOM0PYohIvH/9jhagxkHh/bj4zhK0tsWzha6hd ghInZz5hmcAoMgvJqFlIWmYhaZmFpGUBI8sqRtHi1OLi3HQjI73Uoszk4uL8PL281JJNjMC4 Orjlt9UOxoPPHQ8xCnAwKvHwJnAIRQixJpYVV+YeYpTgYFYS4fXKFo4Q4k1JrKxKLcqPLyrN SS0+xCjNwaIkzmu28n64kEB6YklqdmpqQWoRTJaJg1OqgdEn80G89fIDvxekSmcy8HuXBfA+ 3Xp8y8OAScrcR/la7kWWXNsqcHblcc2sz0pzpRqTp/2dHSho1t3IX87g+V1JeL96bNxh7XhT K4utCkKtT6yP8+Qtk2Et7/Dhq0i+1dt3+KLaUxXTzF67rFdLpuur2a05FTMrKu7E9KCFVg05 zy94FyTNUmIpzkg01GIuKk4EACodl6qnAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/BFbgDjKETDw9kjIiNi43-C0UDI8>
Cc: Flemming Andreasen <fandreas@cisco.com>, ART ADs <art-ads@ietf.org>, Cullen Jennings <fluffy@iii.ca>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 15:22:08 -0000

Hi,

I was going to suggest a side meeting, but forgot.

When would people be available? Sunday? Monday?=20

Tuesday is pretty full with sessions I assume most of the affected parties =
will attend.

Regards,

Christer=20

Sent from my iPhone

> On 28 Oct 2016, at 17.44, Ben Campbell <ben@nostrum.com> wrote:
>=20
>> On 28 Oct 2016, at 8:43, Roman Shpount wrote:
>>=20
>> In general, the two opposing champions are Cullen (asking not to update =
the
>> required hash algorithm) and Martin (who asked to make SHA-256 the
>> requirement in the first place).
>=20
> If Martin is critical to this conversation, then the conversation should =
wait for him. But I agree with Christer that this is likely to be a behind-=
the-mike discussion. I half expect that to end with "interested parties ple=
ase gather for a side meeting."
>=20
> The point being: If a group call cannot happen prior to Seoul, then I str=
ongly suggest interested parties arrange a side meeting there _prior_ to th=
e MMUSIC meeting (currently scheduled Wednesday morning).
>=20
> (I understand the AD is somewhat frustrated over the draft being stuck on=
 this point ;-)  )
>=20
>=20
>>=20
>> Can I suggest two of them to have a call and see if one can convince the
>> other? The group had its consensus call, but based on my discussion with
>> Christer, the draft authors do not particularly care either way regardin=
g
>> mandatory hash function selection issue. If Martin and Cullen can agree =
on
>> the way forward regarding this, they can bring the result to the group a=
nd
>> I am sure we will accommodate it. If they cannot reach an agreement, the=
n
>> we can look at other ways to resolve it.
>=20
> I highly encourage that in any case.
>=20
>=20
>>=20
>> Please note, that Chirster and I do feel strongly that the new draft sho=
uld
>> be considered an update to RFC 4572, since it clarifies the multiple
>> fingerprint related issues. I do believe any of the 4572 implementations
>> should be compliant with the new draft in order to avoid interop issues.
>>=20
>=20
> I take that to mean that if Martin and Cullen go off and decide the "upda=
tes" tag is not needed, you will be unhappy? If so, please try to participa=
te in any such call.
>=20
>> Regards,
>>=20
>> _____________
>> Roman Shpount
>>=20
>> On Fri, Oct 28, 2016 at 9:23 AM, Christer Holmberg <
>> christer.holmberg@ericsson.com> wrote:
>>=20
>>> Hi,
>>>=20
>>> Keep in mind that this would most likely not be a thing where the
>>> presenter (me, I assume) shows a slide that people the comment on. It w=
ould
>>> mostly be a =93behind the microphone argume=85 eeeh.. discussion=94 bet=
ween a few
>>> people, so I wonder whether the WG session is the best place to discuss
>>> this.
>>>=20
>>> Regards,
>>>=20
>>> Christer
>>>=20
>>> From: Bo Burman <bo.burman@ericsson.com>
>>> Date: Friday 28 October 2016 at 12:39
>>> To: Eric Rescorla <ekr@rtfm.com>, Martin Thomson <martin.thomson@gmail.=
com
>>>>=20
>>> Cc: Ben Campbell <ben@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>=
,
>>> ART ADs <art-ads@ietf.org>, Flemming Andreasen <fandreas@cisco.com>,
>>> Cullen Jennings <fluffy@iii.ca>, Christer Holmberg <
>>> christer.holmberg@ericsson.com>
>>> Subject: RE: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (w=
as
>>> Re: Rough concensus: Re: 4572-update: Consensus call on how to move
>>> forward)]
>>>=20
>>> This is definitely possible =96 MMUSIC Seoul agenda is not set in stone=
, but
>>> please be aware that the single MMUSIC session is only an hour in total=
.
>>>=20
>>> /Bo
>>>=20
>>> MMUSIC co-chair
>>>=20
>>>=20
>>>=20
>>> *From:* mmusic [mailto:mmusic-bounces@ietf.org <mmusic-bounces@ietf.org=
>] *On
>>> Behalf Of *Eric Rescorla
>>> *Sent:* den 28 oktober 2016 10:49
>>> *To:* Martin Thomson <martin.thomson@gmail.com>
>>> *Cc:* Ben Campbell <ben@nostrum.com>; mmusic <mmusic@ietf.org>; ART ADs=
 <
>>> art-ads@ietf.org>; Flemming Andreasen <fandreas@cisco.com>; Cullen
>>> Jennings <fluffy@iii.ca>; Christer Holmberg <christer.holmberg@ericsson=
.
>>> com>
>>> *Subject:* Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update
>>> (was Re: Rough concensus: Re: 4572-update: Consensus call on how to mov=
e
>>> forward)]
>>>=20
>>>=20
>>>=20
>>> Dealing with this in Seoul seems like a reasonable suggestion
>>>=20
>>>=20
>>>=20
>>> -Ekr
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>> On Fri, Oct 28, 2016 at 4:11 PM, Martin Thomson <martin.thomson@gmail.c=
om>
>>> wrote:
>>>=20
>>> On 26 October 2016 at 15:54, Flemming Andreasen <fandreas@cisco.com>
>>> wrote:
>>>> A Doodle poll is now available at
>>>>=20
>>>>        http://doodle.com/poll/kxw4n9a2v7v3pe2y
>>>>=20
>>>> We are looking at either Wednesday or Friday next week (November 2 or
>>> 4), so
>>>> please get your vote in pretty quickly if you are interested.
>>>=20
>>> These are awful times for me, though I would like to be involved.
>>> It's not that long now until we will all be in the same room, is this
>>> somehow urgent enough that we need to have a call?
>>>=20
>>>=20
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>=20
>>>=20
>=20
>=20
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Fri Oct 28 08:28:33 2016
Return-Path: <fluffy@iii.ca>
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 9F70412967D for <mmusic@ietfa.amsl.com>; Fri, 28 Oct 2016 08:28:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LP6-XwLpBu-g for <mmusic@ietfa.amsl.com>; Fri, 28 Oct 2016 08:28:30 -0700 (PDT)
Received: from smtp106.iad3a.emailsrvr.com (smtp106.iad3a.emailsrvr.com [173.203.187.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BDFC129606 for <mmusic@ietf.org>; Fri, 28 Oct 2016 08:28:30 -0700 (PDT)
Received: from smtp22.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp22.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id A43E6A0284; Fri, 28 Oct 2016 11:28:24 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp22.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 32EABA00D9;  Fri, 28 Oct 2016 11:28:24 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.253] (d75-159-45-76.abhsia.telus.net [75.159.45.76]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.7); Fri, 28 Oct 2016 11:28:24 -0400
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CAD5OKxuRm2tedhBTh096M6N923P6UPmotH-RJOCoqSzGMgE5MQ@mail.gmail.com>
Date: Fri, 28 Oct 2016 09:24:58 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <B703A957-C140-4082-BC81-39B161FDEDED@iii.ca>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com> <CABkgnnV7yU8Y1YhDSmm5hSbFSoVLhXvDnKOAs1otmnyf0s5RHw@mail.gmail.com> <CABcZeBMFeCkAxOaTPaMZytLmNpbprja5tF5D7RHrejSihN508Q@mail.gmail.com> <AM5PR0701MB2577F7A1A473CE2D5866365B8DAD0@AM5PR0701MB2577.eurprd07.prod.outlook.com> <D4392BDB.120E1%christer.holmberg@ericsson.com> <CAD5OKxsY7+ZHtGJeX7YG=BBYTj4PxEBmgopGQ6u7Hrj2EEgT_Q@mail.gmail.com> <E95B34C4-91EA-41FC-9EAC-D59C77A33C12@nostrum.com> <CAD5OKxuRm2tedhBTh096M6N923P6UPmotH-RJOCoqSzGMgE5MQ@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>, Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.3226)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/G8o2TRTY40SIedJFuSvcGrT7viI>
Cc: Flemming Andreasen <fandreas@cisco.com>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 15:28:31 -0000

> On Oct 28, 2016, at 9:07 AM, Roman Shpount <roman@telurix.com> wrote:
>=20
> I would ask two of them to talk and try to come to an agreement.

I=E2=80=99m happy to talk to Martin and a time that is more sane for him =
and we can report back to the WG.=20


From nobody Fri Oct 28 09:00:24 2016
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 E7907129644 for <mmusic@ietfa.amsl.com>; Fri, 28 Oct 2016 09:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.952
X-Spam-Level: 
X-Spam-Status: No, score=-14.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 ux8nKdFWzLa1 for <mmusic@ietfa.amsl.com>; Fri, 28 Oct 2016 09:00:14 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43D5E129461 for <mmusic@ietf.org>; Fri, 28 Oct 2016 09:00:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1118; q=dns/txt; s=iport; t=1477670414; x=1478880014; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=5yCyeoqtoSkUAKSDNc5H1b2Aqgl7jSZXkHIWKYoQGb8=; b=XLkojkDXVei+sAootfv55yOVMLllVt/6lDtxNJxSIw7YO71e6BAjacD0 6dCYSY/IaBhF2KwHGWmhpo7njJHn08fFbzoIrjhQNPry9biEXj2ybe0T0 b9e9cCed7XJxOk4SB7GK3wQipzZ/4m17nGVsbq2jEye6eOVRp8X2Kp9K2 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DdAQA3dRNY/4oNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgyoBAQEBAR+BAlONNpZ+kjCCD4IHhiMCgX4/FAECAQEBAQEBAWI?= =?us-ascii?q?ohGMBAQQjDwEFNgsQCw4KAgIfBwICVwYBDAYCAQGIULEGjGUBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEfgQeFNoF9CIJQh0uCWwEEmhiQJ4FuiASGEocehXGEAR42X4NPgVc?= =?us-ascii?q?iNIdzAQEB?=
X-IronPort-AV: E=Sophos;i="5.31,410,1473120000"; d="scan'208";a="167891013"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Oct 2016 16:00:13 +0000
Received: from [10.98.149.196] (bxb-fandreas-8813.cisco.com [10.98.149.196]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u9SG0BLJ008693; Fri, 28 Oct 2016 16:00:12 GMT
To: Cullen Jennings <fluffy@iii.ca>, Roman Shpount <roman@telurix.com>, Martin Thomson <martin.thomson@gmail.com>
References: <729820D1-4135-4B75-AC85-379A5314CEC7@nostrum.com> <e13f65d8-51cb-e7d4-3c35-a07950daf158@cisco.com> <893bb9c2-5731-511f-0e65-c4490d5bde79@cisco.com> <CABkgnnV7yU8Y1YhDSmm5hSbFSoVLhXvDnKOAs1otmnyf0s5RHw@mail.gmail.com> <CABcZeBMFeCkAxOaTPaMZytLmNpbprja5tF5D7RHrejSihN508Q@mail.gmail.com> <AM5PR0701MB2577F7A1A473CE2D5866365B8DAD0@AM5PR0701MB2577.eurprd07.prod.outlook.com> <D4392BDB.120E1%christer.holmberg@ericsson.com> <CAD5OKxsY7+ZHtGJeX7YG=BBYTj4PxEBmgopGQ6u7Hrj2EEgT_Q@mail.gmail.com> <E95B34C4-91EA-41FC-9EAC-D59C77A33C12@nostrum.com> <CAD5OKxuRm2tedhBTh096M6N923P6UPmotH-RJOCoqSzGMgE5MQ@mail.gmail.com> <B703A957-C140-4082-BC81-39B161FDEDED@iii.ca>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <fc423584-d814-08e1-2588-489ce980b379@cisco.com>
Date: Fri, 28 Oct 2016 12:00:11 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <B703A957-C140-4082-BC81-39B161FDEDED@iii.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/JT_eQF0e1SP7fm_3MSHzi4Z-Olg>
Cc: Ben Campbell <ben@nostrum.com>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Doodle poll [Re: Moving Forward on 4572-update (was Re: Rough concensus: Re: 4572-update: Consensus call on how to move forward)]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 16:00:23 -0000

Ok - let's proceed that way as the first step then. When will the two of 
you talk and when will you report back to the WG ?

Assuming that will happen by early next week, I would still like to have 
a call scheduled for later next week to ensure progress, and it seems 
everybody except Martin is available Friday at 10 AM Eastern, so that is 
when we will schedule it.

Best case scenario will be that all is resolved before then and we can 
cancel the call; worst case we will use the call to prep for further 
discussion in Seoul. Since Martin is a major stakeholder and not able to 
participate Friday, there will of course not be any decisions made in 
the Friday meeting (which in any case would be subject to mailing list 
confirmation)

Thanks

-- Flemming (with chair hat on)



On 10/28/16 11:24 AM, Cullen Jennings wrote:
>> On Oct 28, 2016, at 9:07 AM, Roman Shpount <roman@telurix.com> wrote:
>>
>> I would ask two of them to talk and try to come to an agreement.
> Iâ€™m happy to talk to Martin and a time that is more sane for him and we can report back to the WG.
>
> .
>


From nobody Sun Oct 30 14:51:03 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 E584A129493; Sun, 30 Oct 2016 14:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.798
X-Spam-Level: 
X-Spam-Status: No, score=-5.798 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_MED=-2.3, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 bcMqYWik1brj; Sun, 30 Oct 2016 14:51:00 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFF821293FF; Sun, 30 Oct 2016 14:51:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C4C48BE2E; Sun, 30 Oct 2016 21:50:58 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9iiqyaukfNtP; Sun, 30 Oct 2016 21:50:57 +0000 (GMT)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id BA73BBE2C; Sun, 30 Oct 2016 21:50:56 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1477864257; bh=yl2MoO5dA6pW5alZVdWT3Iju0k7wxIXJVkJiOe8oh0M=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=IWET5joOSCoKXkP7+neSWQmaAoD3VwJytR5Di2EF017rialRd4KVDu1bvJU0Ey4Nn JyqSA9CVobkmZhgPBUHVDA7e4A3G5Df25aHtd0RoWGuxVpVC/qNmrutVRW8tHRO84I aqVDbhcSVKWIJROJzRRZYgQl5jv00UZvF2tlKtEk=
To: Suhas Nandakumar <suhasietf@gmail.com>
References: <147747540682.18851.267971327825992233.idtracker@ietfa.amsl.com> <CAMRcRGRQYoVuurAuiy9tJFcJ_Kt3fR_4Cr9oStZiWcCNdvwGog@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <09c0816b-40b2-a3ea-cbdb-265eca5d66cc@cs.tcd.ie>
Date: Sun, 30 Oct 2016 21:50:57 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGRQYoVuurAuiy9tJFcJ_Kt3fR_4Cr9oStZiWcCNdvwGog@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms080203000307070208090004"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/vPldRUcdDYXdm4ZZm-oOQCgEkCk>
Cc: mmusic-chairs@ietf.org, draft-ietf-mmusic-sdp-mux-attributes@ietf.org, The IESG <iesg@ietf.org>, mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Stephen Farrell's No Objection on draft-ietf-mmusic-sdp-mux-attributes-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Oct 2016 21:51:02 -0000

This is a cryptographically signed message in MIME format.

--------------ms080203000307070208090004
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

On 26/10/16 23:47, Suhas Nandakumar wrote:
> Hello Stephen
>=20
>     Thanks for the review . please see inline.
>=20
> On Wed, Oct 26, 2016 at 2:50 AM, Stephen Farrell <stephen.farrell@cs.tc=
d.ie>
> wrote:
>=20
>> Stephen Farrell has entered the following ballot position for
>> draft-ietf-mmusic-sdp-mux-attributes-14: No Objection
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut thi=
s
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.h=
tml
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/=

>>
>>
>>
>> ----------------------------------------------------------------------=

>> COMMENT:
>> ----------------------------------------------------------------------=

>>
>>
>> - 4.5 and 5.7: What if the different a=3Dcrypto lines
>> specify different strength ciphersuites? Wouldn't it be
>> better to pick the strongest or to say they MUST be the
>> same (as is done in 5.35)? If picking the first is the
>> right answer then maybe warn folks to not put a stronger
>> ciphersuite anywhere else?
>>
>=20
>=20
> [Suhas]:  I did think about it some more and I am not sure the mux draf=
t
> opens up an vulnerability in this scenario.
> For example, Even with the IDENTICAL category, the Offerer can include =
a
> weak cipher in all the m=3Dlines and thus force the Answerer to select =
the
> weak one or have the Answerer reject the Offer. I am not sure if making=
 it
> iDENTICAL would help us guard against the wrong cipher selection.
> .
> In the TRANSPORT scenario, if the Answerer selected the m=3Dline with a=
 weak
> cipher the Offerer has 2 options a) Don't include the weak cipher b) Do=

> another Offer/Answer with the modified list (with strong ciphers or
> inactive media)
>=20
> Please advise ..

It's less an issue of creating a vulnerability as it is of
making it easier for people to end up in a situation where
they think they have better security than is in fact the
case. I think experience shows that disallowing differences
of that kind is a good plan. But I could understand if it
was the case that allowing such discrepancies made it easier
to get interop in some cases. I don't know if that latter
is the case.


>=20
>=20
>=20
>=20
>>
>> - 5.36 vs. 5.39: It wasn't clear to me why these have
>> different rules - can you explain?
>>
>>
>>
> [Suhas] : It looks like both the fingerprint (Section 5.36) and
> zrtp-hash(5.39) attributes have the same Multiplexing category of TRANS=
PORT
> assigned and thus follow the same rules. Am i missing something here ?
>=20

In the ZRTP case you have a MUST and level =3D=3D M. In the other
there's no MUST and it has level =3D=3D B. At this point I forget
what those level things mean though;-)

S.

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


--------------ms080203000307070208090004
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjEwMzAy
MTUwNTdaMC8GCSqGSIb3DQEJBDEiBCAyID+SVf8c8EgOgQgizvBtRkPWxif180e9j+/zNGPk
3zBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQBIxbS5/MC/+c3zxZyUVLvWUCD6P22Isa3LI3imyY4a2T24olsRRcv1
TJ9xq1VLNuIz8JWCRk+2opRFWkPrI5g2op/o4X7IXD9sUBQgeyKfJjXr2d3U2GNRe/cs/3VS
yHU5rtFwRJ1oBfWoUOsOQIff/Js1I5TtxlQTRC3kSnn/yngcLPUZwejTZ2pXg1DOGtIY4yjz
OZ2t+G6fdBXvDSpRYdB6xvn7yWBql602HDLZ/DicOYntKKwRNkMO0cCYRvX/0j6ASTJ4tlXd
rUq1jsGMfL5UR8z8C1xrh8J814Bk9Hxv6GNrkwjzKf+iarMWcF3Cmj0dHIi3e/nRA1+JpBKx
AAAAAAAA
--------------ms080203000307070208090004--


From nobody Mon Oct 31 06:08:48 2016
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 065B412955C; Mon, 31 Oct 2016 06:08:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147791932602.32409.450054598548580570.idtracker@ietfa.amsl.com>
Date: Mon, 31 Oct 2016 06:08:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/V_jYi_Ofv-XbrqS6-ssZ5KgI2CE>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-dtls-sdp-15.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 31 Oct 2016 13:08:46 -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 of the IETF.

        Title           : Using the SDP Offer/Answer Mechanism for DTLS
        Authors         : Christer Holmberg
                          Roman Shpount
	Filename        : draft-ietf-mmusic-dtls-sdp-15.txt
	Pages           : 25
	Date            : 2016-10-31

Abstract:
   This document defines the SDP offer/answer procedures for negotiating
   and establishing a DTLS association.  The document also defines the
   criteria for when a new DTLS association must be established.  The
   document updates RFC 5763 and RFC 7345, by replacing common SDP
   offer/answer procedures with a reference to this specification.

   This document defines a new SDP media-level attribute, 'dtls-id'.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-dtls-sdp-15

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


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

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


From nobody Mon Oct 31 09:32:16 2016
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 41BE11298BB for <mmusic@ietfa.amsl.com>; Mon, 31 Oct 2016 09:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.721
X-Spam-Level: 
X-Spam-Status: No, score=-3.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SNf_R5pGBaSk for <mmusic@ietfa.amsl.com>; Mon, 31 Oct 2016 09:32:12 -0700 (PDT)
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 6B1DD1298BA for <mmusic@ietf.org>; Mon, 31 Oct 2016 09:32:02 -0700 (PDT)
X-AuditID: c1b4fb3a-dafff700000078c6-cf-581771ff1915
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by  (Symantec Mail Security) with SMTP id 0B.E1.30918.FF177185; Mon, 31 Oct 2016 17:32:00 +0100 (CET)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.69) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 31 Oct 2016 17:31:59 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Fe9V9EDjX7L7So2fBMbUFHbKE3bbpNP0ArX6fIFbO6Y=; b=Ga2QPCIZuYoVW/jEr/L7t2RsV5KR5JNVaLd3m2R/8BzQY95F7hRsF6SF4e/6S2pfO0/U5ObQCmx8NdQIG1ZSoGrqAKpG9Jqe04YRDQyxqllKEKPoShixdxSojOFFVj+6/gBylI5dAv5aTukAsDvAFQ92skLpgYE7eZEoUS2plQY=
Received: from AM5PR0701MB2577.eurprd07.prod.outlook.com (10.173.92.21) by AM5PR0701MB2580.eurprd07.prod.outlook.com (10.173.92.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.707.1; Mon, 31 Oct 2016 16:31:58 +0000
Received: from AM5PR0701MB2577.eurprd07.prod.outlook.com ([10.173.92.21]) by AM5PR0701MB2577.eurprd07.prod.outlook.com ([10.173.92.21]) with mapi id 15.01.0707.002; Mon, 31 Oct 2016 16:31:58 +0000
From: Bo Burman <bo.burman@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Adam Roach <adam@nostrum.com>, Flemming Andreasen <fandreas@cisco.com>, mmusic <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Simulcast draft review needed
Thread-Index: AQHSFStWb6FE3qSufkKBbiAjPcIix6Cwki4AgAJFRYCAEB7SkA==
Date: Mon, 31 Oct 2016 16:31:58 +0000
Message-ID: <AM5PR0701MB257763DE72242AC119E131D48DAE0@AM5PR0701MB2577.eurprd07.prod.outlook.com>
References: <105f1c1e-63b0-e250-663f-b8981bad960e@cisco.com> <70816640-d76a-c84d-e0f8-9baf820d943b@nostrum.com> <ed77b9dd-a004-b816-5226-428760cf97e9@ericsson.com>
In-Reply-To: <ed77b9dd-a004-b816-5226-428760cf97e9@ericsson.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=bo.burman@ericsson.com; 
x-originating-ip: [192.176.1.87]
x-ld-processed: 92e84ceb-fbfd-47ab-be52-080c6b87953f,ExtAddr
x-ms-office365-filtering-correlation-id: 01b1c66d-ed1c-48b3-2983-08d401ab6f4b
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB2580; 7:8QdaZ9YBEUfldmStkcMNK06Rw6AlgJ+oL002qorTF4TNiqQ6XzKYrqVLoeCqgvwCZxKBJoutERbpUCW03poOskEilGwHzcl+/MSBEsraHM0ypqwH5iQjHDp0IAflDmBZehfSgnKZQ1HULsbVk8xtrR29Gb6Q5kO2n2Iku6cjvbE0CuSY/+VsTTzV8LAAc0fAb5CMrLevNMmazoa0DzYRNtwnKS5QBfO/RA8UNQuq/p0l4jYIYcIgbWIwxwI7Ng270J76rwYKhXEhYeEvRdo17P6tWybOr3YNVjW2gvAhoQPUZnOLqnQv4s+qxxB5ovdWqIMZRHZb4zcEzpwAF+vycTn4LSvukaFtv/UrVDWpCvs=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM5PR0701MB2580;
x-microsoft-antispam-prvs: <AM5PR0701MB2580959FF5D49514EE1488BF8DAE0@AM5PR0701MB2580.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(192374486261705)(95692535739014); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001);  SRVR:AM5PR0701MB2580; BCL:0; PCL:0; RULEID:; SRVR:AM5PR0701MB2580; 
x-forefront-prvs: 01128BA907
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(377424004)(189002)(199003)(24454002)(13464003)(5002640100001)(122556002)(106116001)(68736007)(345774005)(9686002)(8936002)(105586002)(86362001)(106356001)(3660700001)(101416001)(87936001)(3280700002)(76576001)(66066001)(33656002)(19580405001)(19580395003)(54356999)(76176999)(11100500001)(50986999)(5660300001)(586003)(189998001)(10400500002)(7736002)(7846002)(107886002)(305945005)(77096005)(15975445007)(92566002)(2900100001)(2906002)(81166006)(81156014)(4001150100001)(5001770100001)(97736004)(7696004)(2950100002)(74316002)(3846002)(102836003)(8676002)(6116002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM5PR0701MB2580; H:AM5PR0701MB2577.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2016 16:31:58.2763 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2580
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Se0hTcRTH++3ezetodFvqThahg0Atly+aDAnThCEEQkJqRY78oeaTe1VS goTKTE0Lp+mcTW35bqLlI7FoS6SHpaU9yVQUsiRFfJXLaHd3Qf99zjnfc76/c/hRhLRE6E4l p2dhJl2TKheJyeqY3gjfLYwsxm+uITB4YLPBKXhx1De4ommGDCXUWmunUG00/hKodQ9mySgi ThySgFOTczBz4FC8OGm0p0aY+SbiXON8qSgfjSiLkDMFdBD0PuwXFSExJaVNCDbWFxzBUwRV G3qSC0j6GgG/L1oEfKVKAF19Q05cv12mLw7nWER7gaFvAnEiF1qPYPljIeIKO+hAmGzX2htc bIb6K3dInsOgYHLOpqFsFnvhbaGMS0voeFiz9Ah5syYEi5/rnTiNMx0K63P2dyPaDdaftws4 JmgZfJo1CPh9aDAOjBA8u8K3mT9CXh8L5Tde2scA7QHGzZ28JASqim865Eeh0vSY4GyBbiBg ccTgKKjBULok4jkDVpamCH7OCagZjOLTAwiGTCk874bxL92In1MggrHh74i/FYamu5cdJ3GH ifGr6Dry0f23As8K+FChFfG8Dxrr5wmd/Szb4Vn1LFmHyFbkymKWTUsMCFBgJvkMy2akK9Jx Vhey/RHzfauqD5m/HrYgmkLyrZLMk7IYqVCTw+amWRBQhNxF0pZmS0kSNLl5mMk4zWSnYtaC dlGkXCY52DJ5XEonarJwCsaZmPlXFVDO7vmoLGW5UfdOK3gU3VxWUj77vnmDvTeJEzK7dC1T lZ5+2Jt4ktjsfVY6v3Bkz+qLcTwlXcvrb/OHsJpXt0anK4RmL2RVRSq7O6IvjViVHaoVz590 nWnMLbK19pSqMXa4xHzsfK2vcr9J8aP5QnhgZd1tj8Wg1fLBbdmdhrhpyWs5ySZp/H0IhtX8 BdMA3X0fAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/DYNiL0MNb_rHWHm6O2VNNEtxFHw>
Subject: Re: [MMUSIC] Simulcast draft review needed
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 31 Oct 2016 16:32:15 -0000

Hi Adam,

Thank you for the review and for good comments! I'm in the process of makin=
g edits to the upcoming version of the draft (to be submitted before deadli=
ne). Please see my responses inline below.

Cheers,
/Bo (as individual)

> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Magnus Westerl=
und
> Sent: den 21 oktober 2016 11:53
> To: Adam Roach <adam@nostrum.com>; Flemming Andreasen <fandreas@cisco.com=
>; mmusic <mmusic@ietf.org>
> Subject: Re: [MMUSIC] Simulcast draft review needed
>=20
> Thanks Adam,
>=20
> We will work on a update to meet the deadline where we will make our best=
 to incorporate your feedback. My read
> through indicates that they are reasonable comments. And first after havi=
ng thought through them and attempted
> implementing them will I know if there some issues with them.
> So a follow up after implementing the changes.
>=20
> Cheers
>=20
> Magnus
>=20
> Den 2016-10-20 kl. 01:12, skrev Adam Roach:
> > On 9/22/16 18:44, Flemming Andreasen wrote:
> >> Please note that we also have the simulcast draft
> >>
> >> https://www.ietf.org/id/draft-ietf-mmusic-sdp-simulcast-05.txt
> >>
> >> to go along with this, and we really need some reviews of that one
> >> too. If you have some time to review it, please do so and send your
> >> comments to the list (incl. "looks good").
> >
> > I'm one of the dedicated volunteers who agreed to review this document.
> > I apologize for the delay in providing feedback.
> >
> > In general, this document looks to be in really good shape. I have a
> > handful of comments, some editorial, and some minor technical. I don't
> > see any major technical issues. The largest issue I have is that one
> > of the examples contravenes the recommendations in avtext-rid, and is
> > consequently likely to cause interop failures.
> >
> >
> > Technical:
> >
> > Section 4, REQ-1.2 -- it's not clear to me how this requirement is met.
> > The current mechanism does not allow implementations to determine
> > which streams are part of a single simulcast media source by looking
> > at the RTP/RTCP in isolation. The SDP must be used in concert with the
> > RTP/RTCP information. This requirement needs to be either removed or cl=
arified.
[BoB] That is actually true. Good catch. I believe this requirement to be a=
 remnant from the time we had ideas of including a "structured" ID in the R=
TP packets. I don't know to what extent this requirement is still desirable=
, but I'm personally open to remove it. The now used RtpStreamId actually h=
as no specific value restrictions apart from the security considerations ex=
pecting them to be opaque, which I interpret as it could be possible to re-=
introduce RtpStreamId structuring that would satisfy REQ-1.2.

> >
> > Section 6.3.2, paragraph 3, states: "The answerer MUST NOT add any
> > alternative SCID that were not present in the offer." This seems like
> > an odd restriction on SCID in the send direction. It is not reasonable
> > for the offerer to know how many Simulcast Formats a single Simulcast
> > Stream that the other end can send might be expressed in.
> > Functionally, this is the same as saying that the offerer gets to
> > choose how many PTs the answer is allowed to contain, which is a new
> > (and presumably
> > unnecessary) restriction. The minimal change to fix this issue would
> > be to add "in the receive direction" to the sentence I quote.
[BoB] OK. Would this be acceptable: "The answerer MUST NOT add any alternat=
ive SCID in send direction in the answer that were not present in the offer=
 receive direction"?

> >
> > I'm sure the conversation happened after -05 was published, but to
> > make sure it doesn't get lost: we're not supporting declarative use,
> > so section 6.4 should be removed.
[BoB] OK, good. I did not remove it, but changed content of 6.4 to basicall=
y say the same as mmusic-rid section 7; not defined for declarative SDP, bu=
t can be addressed by additional specification in the future.

> >
> > The most complicated SDP example (Figure 6, on page 20) uses
> > nonoverlapping RIDs for the two different video media sections. This
> > implies that the RID space is globally unique in some way. In
> > practice, RIDs are scoped to be unique only within a single media secti=
on.
> > Implementors are likely to incorrectly infer from this example that
> > RIDs need to be unique even between media sections, which can lead to
> > interop failures. Please adjust the example so that the RIDs in the
> > second media section start over at 1 rather than resuming where the
> > first video section left off.
[BoB] No problem. Done.

> >
> >
> > Editorial:
> >
> > In the terminology section, the second sentence of the definition of
> > Simulcast Streams (starting "Decoding a dependent stream...") is
> > difficult to parse and difficult to understand. Assuming I did
> > eventually understand what it's saying, I don't think it necessary or
> > helpful, and can probably be removed rather than fixed.
[BoB] Agree. Removed.

> >
> > The first comma in the definition of Simulcast Format should be a colon=
.
[BoB] Thanks.

> >
> > Section 3 should also mention the use case in which the media switch
> > does not have access to the media contents, as in the type of
> > conferences that PERC is being designed for.
[BoB] OK. Added.

> >
> > Section 3.2 should contain commas around the phrase "for example" in
> > the second sentence of the first paragraph.
[BoB] OK

> >
> > The prose in section 6.1 seems to suffer from the lack of a formal
> > term for the construct that the ABNF calls "sc-alt-list." For example,
> > the third paragraph says "each SCID is separated by a semicolon."
> > That's inaccurate and confusing: the syntax clearly indicates that
> > SCIDs are indicated by commas, and the "sc-alt-list" construct is
> > separated by semicolons. I think the smallest change we can make to
> > fix this is to say "each _stream_ is separated by as semicolon", but
> > that's a bit unsatisfying. I think it would be better to define an
> > English term for this "sc-alt-list" thing and use it where appropriate.
[BoB] I discussed this with Magnus, went through the entire text and tried =
to consistently reflect that a simulcast stream (separated by semicolon and=
 thus effectively an "sc-alt-list") can be expressed as having one or more =
simulcast formats (separated by comma), and that each simulcast format is i=
dentified/represented by the SCID.

> >
> > This missing terminology shows up again in the fourth paragraph of
> > section 6.2: the construct "The number of (non-alternative, see above)
> > SCID..." is awkward and hard to follow. If we define a term that means
> > this "sc-alt-list" thing, it should be used here. If we don't, then I
> > again suggest using the term "stream" rather than "(non-alternative,
> > see
> > above) SCID".
[BoB] Changed according to the above.

> >
> > In the seventh paragraph of section 6.2 (starting "A simulcast
> > stream..."), the sentence "...such 'related' formats MUST NOT be
> > defined as SCID and listed..." needs to have something like "having the=
ir own"
> > inserted, to read: "...such 'related' formats MUST NOT be defined as
> > having their own SCID and listed..."
[BoB] OK

> >
> > The following paragraph contains a sentence fragment that can be
> > turned into a sentence by changing "...each of which can be
> > individually prefixed..." to "...each can be individually prefixed..."
[BoB] OK

> >
> > The final paragraph of section 6.3.2 contains a comma preceded by a
> > space. This comma should be removed.
[BoB] OK

> >
> > Section 8 should clearly indicate that the technique described in the
> > third paragraph is out of scope for this document, and that additional
> > specification would be necessary to implement simulcast in a multicast
> > context.
[BoB] OK. Done.

> >
> > /a
> >
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www.ietf.org/mailman/listinfo/mmusic
> >
>=20
>=20
> --
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=E4r=F6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Mon Oct 31 12:07:39 2016
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 D5467129A56 for <mmusic@ietfa.amsl.com>; Mon, 31 Oct 2016 12:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.018
X-Spam-Level: 
X-Spam-Status: No, score=-16.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, 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 vu-2PWsmfc5S for <mmusic@ietfa.amsl.com>; Mon, 31 Oct 2016 12:07:38 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BF2B129A5B for <mmusic@ietf.org>; Mon, 31 Oct 2016 12:07:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=247; q=dns/txt; s=iport; t=1477940856; x=1479150456; h=to:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=EVey3rNW5O0my+TLbFKK3X08+K67kKCf2cD6K+vhYKE=; b=iCHMdRitpbl5aa26Ak1g4+S1Wm68QR1HShOt3p8hNlfg0jnFazaMk0Ew WwyH6Eik9ZkaMBVOuq4hEB6UTzW4UOHd/rwV65+sOWNi0uM83y/7GO3z7 B8K/Ii9/Ne8cMqoM7LDPvKTRZmaYKHxM3Mp3ag2n/u3v5p/nhPdNznOHY 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DwAgBklBdY/5RdJa1aGwEBAQMBAQEJA?= =?us-ascii?q?QEBgyoBAQEBAR9YAydTjTaiUIEjhDYtWIIPggcohXEBAYIcPxQBAgEBAQEBAQF?= =?us-ascii?q?iKIUMFXYCJgJfDQgBAYhQDqBEj3GMbgEBAQEGAQEBAR4FgQeFNoF9CIobglwBB?= =?us-ascii?q?JoYi0yEBV+BWAEVhG2DF4YSkRMeNmCFLiI0AYgIAQEB?=
X-IronPort-AV: E=Sophos;i="5.31,428,1473120000"; d="scan'208";a="342431291"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Oct 2016 19:07:36 +0000
Received: from [10.98.149.196] (bxb-fandreas-8813.cisco.com [10.98.149.196]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u9VJ7Zi6030454 for <mmusic@ietf.org>; Mon, 31 Oct 2016 19:07:36 GMT
To: mmusic <mmusic@ietf.org>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <e6e79b6a-de7b-7356-c847-7df158d8a1dd@cisco.com>
Date: Mon, 31 Oct 2016 15:07:35 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/NiIeQYzO5Rqt4yXax3ltrPj0Q00>
Subject: [MMUSIC] MMUSIC Agenda for IETF97 - Seoul
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 31 Oct 2016 19:07:39 -0000

Greetings

The draft agenda for the MMUSIC meeting in Seoul has now been uploaded to:

https://www.ietf.org/proceedings/97/agenda/agenda-97-mmusic-00.txt

Please let the chairs know if you have any comments.

Thanks

     Flemming & Bo


From nobody Mon Oct 31 15:01:43 2016
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 5582D1299BE; Mon, 31 Oct 2016 15:01:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147795130134.23286.12554601013437636603.idtracker@ietfa.amsl.com>
Date: Mon, 31 Oct 2016 15:01:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/w4-2aUjmEAGoaQXDewDV9DCvBHM>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-trickle-ice-sip-06.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 31 Oct 2016 22:01:41 -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 of the IETF.

        Title           : A Session Initiation Protocol (SIP) usage for Trickle ICE 
        Authors         : Emil Ivov
                          Thomas Stach
                          Enrico Marocco
                          Christer Holmberg
	Filename        : draft-ietf-mmusic-trickle-ice-sip-06.txt
	Pages           : 38
	Date            : 2016-10-31

Abstract:
   The Interactive Connectivity Establishment (ICE) protocol describes a
   Network Address Translator (NAT) traversal mechanism for UDP-based
   multimedia sessions established with the Offer/Answer model.  The ICE
   extension for Incremental Provisioning of Candidates (Trickle ICE)
   defines a mechanism that allows ICE agents to shorten session
   establishment delays by making the candidate gathering and
   connectivity checking phases of ICE non-blocking and by executing
   them in parallel.

   This document defines usage semantics for Trickle ICE with the
   Session Initiation Protocol (SIP).


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-06

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


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

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


From nobody Mon Oct 31 15:04:03 2016
Return-Path: <thomass.stach@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 0522312942F for <mmusic@ietfa.amsl.com>; Mon, 31 Oct 2016 15:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 8PTGbpXaUKuE for <mmusic@ietfa.amsl.com>; Mon, 31 Oct 2016 15:03:59 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DAD4129428 for <mmusic@ietf.org>; Mon, 31 Oct 2016 15:03:59 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id n67so254755918wme.1 for <mmusic@ietf.org>; Mon, 31 Oct 2016 15:03:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=eorR8WInWo7AacsBUYzOHuBteUTFlG+dz6ptGkSuRMc=; b=Iv70gReVwidzCKE76vzjuNmqwIdp4ZVuUhsNLuauuwsW/wblqy/UM2kWtHoTBaqDCy iuvGo0FTZKATrPWRQgGt1kEY6ocHCDcofVHuVHrvmQZ5MGySWF87A3aGtoRLDPkyHMFQ PcI7MJKVy74cMgg+PUd0NMr8wffMwKymNB4sph88ejtCnObYGZ30rMKCJvmqi+lzDwiO dai9DC9N3DEV4SqwVAqy1b4YdIaWtLhi3+Rp/06btUkkh7QZS9kbbbHyu3W6VhD/Tsgy s6Bg8QgYiXmOP65RPGEYtjJI963/jdb9xfecbu1hrb53wwpB3BT2nGoPAqQTVj9WH+zz S82g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=eorR8WInWo7AacsBUYzOHuBteUTFlG+dz6ptGkSuRMc=; b=W4vj/gvpFD17pBEU5E4wfMszInF6k9ZSby/ov7NIO+UhVNIwHGQ2qddRzzb/Q3Q0xq CZimQFR6TEUhhfZdui3zSzi4hSJc42Rm50hQZ3TEIxJDIy8Kl6am3uJX0QG2W64jLwfB SX6aUM+TU+u6xIMlFdPir8lLelosi8EX2FLSJwHIzSD0YjHT1T+cW9jkl8s7cqWI1PKG 4m3743jaHMmRWxUJUUxHIF5UHxOZdl8SQjRZiHjG8SLfUWZn7Rm4w4eZaMeTzYfuF9YH uazlLOt2a6kvm7APSMn5+RWp7Fu30D2KnyzG3hrAJKFloPg6l9NH+hUzPb86b4vRELTs i42g==
X-Gm-Message-State: ABUngvcoYN0xwzYerh3gIRlpK1s/h8j7mL3YHY1vvPIu0Hngj9lGZA4vVEpVbKy2TDpJKA==
X-Received: by 10.28.107.129 with SMTP id a1mr11701406wmi.90.1477951437622; Mon, 31 Oct 2016 15:03:57 -0700 (PDT)
Received: from [192.168.2.111] (d91-130-252-149.cust.tele2.at. [91.130.252.149]) by smtp.googlemail.com with ESMTPSA id za1sm32208720wjb.8.2016.10.31.15.03.56 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 31 Oct 2016 15:03:56 -0700 (PDT)
To: MMUSIC <mmusic@ietf.org>
References: <147795130167.23286.3563021281892604964.idtracker@ietfa.amsl.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <5ad26a2f-e766-d682-f73f-29f63aeb689a@gmail.com>
Date: Mon, 31 Oct 2016 23:03:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <147795130167.23286.3563021281892604964.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/1U9ZU3We5Xd7pMEyNFXqrh-WzSY>
Subject: Re: [MMUSIC] New Version Notification for draft-ietf-mmusic-trickle-ice-sip-06.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 31 Oct 2016 22:04:01 -0000

All,

changes from draft-ietf-mmusic-trickle-ice-sip-05 include the following:

    o  considered further comments from Christer Holmberg

    o  editorial comments on section 3 addressed

    o  moved section 3.1 to section 10.1 and applied some edits

    o  replaced the term "previously sent candidates" with "currently
       known and used candidates".

Regards
Thomas


On 2016-10-31 23:01, internet-drafts@ietf.org wrote:
> A new version of I-D, draft-ietf-mmusic-trickle-ice-sip-06.txt
> has been successfully submitted by Thomas Stach and posted to the
> IETF repository.
>
> Name:		draft-ietf-mmusic-trickle-ice-sip
> Revision:	06
> Title:		A Session Initiation Protocol (SIP) usage for Trickle ICE
> Document date:	2016-10-31
> Group:		mmusic
> Pages:		38
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-mmusic-trickle-ice-sip-06.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-06
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-trickle-ice-sip-06
>
> Abstract:
>     The Interactive Connectivity Establishment (ICE) protocol describes a
>     Network Address Translator (NAT) traversal mechanism for UDP-based
>     multimedia sessions established with the Offer/Answer model.  The ICE
>     extension for Incremental Provisioning of Candidates (Trickle ICE)
>     defines a mechanism that allows ICE agents to shorten session
>     establishment delays by making the candidate gathering and
>     connectivity checking phases of ICE non-blocking and by executing
>     them in parallel.
>
>     This document defines usage semantics for Trickle ICE with the
>     Session Initiation Protocol (SIP).
>
>                                                                                    
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>


From nobody Mon Oct 31 16:54:56 2016
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 180E0129462; Mon, 31 Oct 2016 16:54:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147795809509.23237.14733066395113839139.idtracker@ietfa.amsl.com>
Date: Mon, 31 Oct 2016 16:54:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jmW0zSzf67IBC6ohbnti1gJPDqs>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-simulcast-06.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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, 31 Oct 2016 23:54:55 -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 of the IETF.

        Title           : Using Simulcast in SDP and RTP Sessions
        Authors         : Bo Burman
                          Magnus Westerlund
                          Suhas Nandakumar
                          Mo Zanaty
	Filename        : draft-ietf-mmusic-sdp-simulcast-06.txt
	Pages           : 34
	Date            : 2016-10-31

Abstract:
   In some application scenarios it may be desirable to send multiple
   differently encoded versions of the same media source in different
   RTP streams.  This is called simulcast.  This document describes how
   to accomplish simulcast in RTP and how to signal it in SDP.  The
   described solution uses an RTP/RTCP identification method to identify
   RTP streams belonging to the same media source, and makes an
   extension to SDP to relate those RTP streams as being different
   simulcast formats of that media source.  The SDP extension consists
   of a new media level SDP attribute that expresses capability to send
   and/or receive simulcast RTP streams.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-sdp-simulcast-06

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


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/

